Evaluating Ventilation Infrastructure: Simplicity Explained

One of the more interesting challenges we've encountered while introducing LUNOS across Canada has very little to do with airflow, heat recovery, or ventilation performance.

More often, the challenge involves helping people reconcile a ventilation system that looks very different from the systems they've spent their careers designing, reviewing, installing, and operating.

The reaction is understandable. For most professionals working in the building industry today, ventilation is viewed through a framework shaped by decades of codes, standards, education, and professional practice. Regardless of whether a project uses corridor pressurization, centralized air handling equipment, make-up air systems, exhaust shafts, or ducted heat recovery ventilation, the common thread is that ventilation has traditionally been associated with building-wide infrastructure.

As a result, certain expectations naturally develop. Ventilation systems are expected to include distribution networks, centralized equipment, mechanical spaces, balancing procedures, and the other components that have historically been used to deliver ventilation performance.

LUNOS challenges those expectations, not because it changes the objectives of ventilation, but because it changes where and how those objectives are achieved. It does so, however, in specific conditions — not across all building types or all applications. LUNOS is a suite-level system, through-wall, ductless, and decentralized, designed for buildings where centralized infrastructure is impractical, absent, or being supplemented. In those conditions, the same ventilation objectives are met through a fundamentally different architecture. That difference is where the conversation usually begins, and where the expectations shaped by decades of centralized practice can make a straightforward system appear incomplete.

The professional expectations described above did not emerge arbitrarily. They are the product of a framework that developed logically, layer by layer, over decades.

The National Building Code of Canada evolved alongside centralized ducted systems because those were the systems being built. Testing standards followed the same architecture. Engineering and technical education was built around what the code required and what the industry specified. Inspection and approval processes developed around what those programs produced. Each layer reinforced the one before it — not through oversight, but because the systems being regulated, taught, and reviewed were the same systems being installed on every project.

The result is a professional formation that runs deeper than habit or preference. Building professionals were trained within a regulatory and educational framework shaped around centralized architecture. The questions they ask when evaluating a ventilation system — questions about duct sizing, static pressure, balancing procedures, and mechanical room allocation — are not the wrong questions. They are the right questions for the systems those frameworks were built around. When a system arrives that doesn't carry that infrastructure, the questions don't automatically update. The framework does what frameworks do: it looks for what it was trained to find.

This is what makes the challenge less about persuasion and more about orientation. The professionals who encounter LUNOS and reach for ducted metrics are not making an error in reasoning. They are applying a well-developed framework to a system that sits outside its reference architecture. The gap is not in their competence. It is in the alignment between the framework they're using and the system they're evaluating.

Over time, complexity became familiar. And familiarity, in a technical discipline, becomes the baseline against which everything new is measured.

When professionals encounter LUNOS for the first time, the conversation rarely centres on whether fresh air should be delivered to the desired space or whether stale air should be removed. Those objectives are universally understood. The discussion almost always focuses on something else — how those objectives are being achieved without much of the infrastructure traditionally used to support them.

A professional reviewing a decentralized ventilation strategy is often being asked to evaluate something that does not align with the reference architecture they have spent years designing, reviewing, or operating. The ventilation objectives remain unchanged, but the means of achieving them can appear unfamiliar. And within a framework that has treated ventilation performance and centralized infrastructure as inseparable, unfamiliar reads as incomplete.

This is something we have encountered repeatedly while working with engineers, architects, housing providers, building officials, and regulatory organizations across Canada. In many cases, the challenge is not explaining ventilation performance. The challenge is explaining why a system capable of delivering that performance can look so different from what people have historically expected to see.

The question is not whether ventilation is occurring.

The question is why so much of the familiar infrastructure is absent.

LUNOS meets CSA C439 cold-climate requirements — verified by a Canadian government research body — sustaining airflow and recovering heat at −25°C over a continuous 72-hour period. No inline duct heaters. No centralized distribution infrastructure. The performance is there. The infrastructure professionals expect to see alongside it is not.

That distinction is the heart of what this article is describing. Ventilation has two components that the industry has long treated as inseparable: the performance objective, and the infrastructure historically used to achieve it. In buildings where LUNOS is the right fit, those two things can be separated — and understanding that separation is what allows the system to be evaluated accurately.

The performance objectives themselves are unchanged — fresh air supplied, stale air removed, heat recovered, indoor air quality maintained. LUNOS meets those objectives through paired, through-wall units operating at the suite level, without the distribution networks, air handling equipment, or building-wide balancing infrastructure of centralized systems. The objectives are identical. The architecture is entirely different.

Once that separation is made clearly, evaluating ventilation infrastructure without the familiar ductwork, mechanical rooms, and balancing dampers stops reading as incompleteness. It reads as a different architecture — one that achieves the same performance intent through a different means. Evaluating LUNOS against the infrastructure expectations of centralized systems is not a performance evaluation. It is an architecture comparison. And the two are not the same thing.

This distinction is examined in detail across our Cold-Climate Ventilation Series and in our article Decentralized Ventilation Compliance: Performance vs. Distribution, which addresses how centralized architectural assumptions appear within testing frameworks and compliance review, and what that means for evaluating decentralized systems accurately.

If you are working through how decentralized ventilation fits within your project's compliance, design, or evaluation framework, we welcome the conversation. The questions that come up most often in these discussions — about airflow verification, cold-climate performance, CSA C439 compliance, and retrofit feasibility — are addressed throughout the Lunos Canada technical library, and our team is available to work through project-specific questions directly.