Aspirating Smoke Detection Design: What NFPA 72 Requires and Where VESDA Projects Go Wrong
Meta Description: How aspirating smoke detection is designed: NFPA 72 sampling port spacing and transport time, ASPIRE pipe network modeling, airflow supervision, and coordination with sprinklers and clean agent.
A spot smoke detector waits for smoke to drift to it. An aspirating smoke detector (ASD) goes and gets it, pulling air through a network of pipes and sampling holes to a central detection chamber that can sense smoke at a fraction of the density a spot detector needs. That is why ASD, including VESDA systems, shows up in data halls, clean rooms, telecom facilities, museums, and high-ceiling spaces where early warning matters more than anything else. It is also why these systems fail in a particular way: the detector is rarely the problem. The pipe network is.
The design is the pipe network
An ASD system is a detector, a run of small-bore pipe, and a set of sampling holes drilled at calculated diameters and positions. Smoke has to travel from the hole to the detector fast enough, and in enough concentration, to trigger an alarm. Change the pipe length, add a fitting, or move a hole, and the airflow balance changes with it.
That is why manufacturers require the pipe network to be modeled in their design software (ASPIRE, for VESDA) before installation, and why the modeled result, not a rule of thumb, is the basis of design. The output reports hole sizes, airflow at each hole, and the transport time from the most remote hole to the detector. A layout that looks fine on a plan can fail that calculation.
What NFPA 72 requires
The air-sampling provisions sit in the initiating device chapter of NFPA 72, in the edition adopted by the AHJ at the project location. Four points drive most submittals.
Listed equipment, installed per the manufacturer's design. The detector must be listed for the application, and the pipe network must be designed and installed within the limits of the manufacturer's listing and design software.
Sampling ports are treated like detectors for spacing. Each sampling port is placed using the spacing rules for spot-type smoke detectors, adjusted for ceiling height, beams, and airflow, unless a performance-based design justifies something different.
Transport time is capped. NFPA 72 limits how long smoke may take to travel from the most remote sampling port to the detector. The limit is 120 seconds, and the ASPIRE report has to show the network meets it.
The system must supervise itself. Airflow faults and pipe problems (a blocked or broken pipe, a filter going bad) must report as trouble. Alarm thresholds must also be mapped to the fire alarm system's alarm and supervisory inputs so the detector's output means what the sequence of operations says it means.
Where the space is a data center, NFPA 75 governs protection of information technology equipment, and for telecommunications facilities NFPA 76 applies. Both recognize aspirating detection, and both put extra weight on the system being right the first time, since these spaces cannot be shut down for retesting.
Where projects go wrong
Holes placed where the air does not go. In a data hall, airflow is engineered: supply air, return air, hot and cold aisle containment. A sampling hole in a stagnant corner or in fast supply air is a hole that dilutes or misses smoke. Holes belong in the return path or above the equipment where smoke will actually travel, and that is a coordination problem with the mechanical design, not a drafting one.
Pipe routing that ignores everyone else. ASD pipe competes for the same ceiling and underfloor space as sprinkler mains, cable tray, ductwork, and structure. Routing it after the other trades have claimed their space is how a balanced pipe network becomes a long, fitting-heavy one that no longer passes the transport time check. Modeling ASD in the coordination model early keeps the pipe short.
Unclear release sequences. ASD is often the first stage of a clean agent or pre-action release, with its alert, action, and fire thresholds tied to cross-zoned release. If the sequence of operations does not say which threshold does what, the installer guesses, and the AHJ finds out at acceptance testing.
Power and battery left out. The detector draws standby and alarm current that has to be in the battery calculation for the panel that powers it. It is a small number that is easy to forget and expensive to correct after the drawings are stamped.
No access for maintenance. Filters, pipe end caps, and test points need to be reachable. A network routed through an inaccessible space will be tested once and then neglected.
Keep the calculation and the drawings aligned
The ASPIRE report is a submittal document, and it describes one specific layout. Every field change, such as a relocated hole, an extra tee, or a shortened run, has to go back into the model and the report, or the stamped drawings stop matching what was calculated. This is the same version discipline that holds for sprinkler hydraulic calculations, and it is the first thing a careful AHJ reviewer checks.
How ProTech CDS approaches projects like this
We design aspirating smoke detection systems, including VESDA, with the pipe network modeled and verified in ASPIRE, coordinated with the sprinkler, mechanical, and structural models in Revit, and tied into the fire alarm sequence of operations. We deliver on a white-label basis, so the package reaches the AHJ under your firm's title block. Project files and submittal status are managed at lockin.protechcds.com. The full scope of our VESDA and aspirating smoke detection design service is on the services page.
Need aspirating smoke detection designed, calculated, and coordinated into your model? Contact ProTech CDS to discuss your project's scope, read about the VESDA design service, or start a submittal at lockin.protechcds.com.