Conclusion Smoke control systems are complex combinations of mechanical, electrical, architectural, and fire protection components. If not properly designed and managed, they can become a problem to implement and can be very costly. Further, it may be nearly impossible to get the system to properly function if there is not a close collaboration between the architect, the mechanical engineer, and the fire protection engineer.
The complexities of modern buildings have created circumstances well beyond the capabilities of classical modeling approaches. An exceptional effort is needed to make sure design teams do not break their budget while creating an effective system that is functional, robust, and approvable.
DOS AND DO NOTS
Do involve the project stakeholders as early in the process as possible. This should include the architect, owner, fire protection engineer/life safety consultant, mechanical/electrical engineer, and contractor. It is important for the mechanical engineer and fire protection engineer to work in concert. Perhaps most importantly, the authority having jurisdiction (AHJ) should be involved at the appropriate time, especially if computer modeling will be utilized. Presenting a Fire Engineering Design Brief that summarizes the proposed smoke control approach, types of modeling, number/nature of design fire scenarios, expected model outputs, and pass/fail criteria can go a long way in establishing a positive relationship and avoiding surprise requirements/requests after all the modeling has been completed.
Do choose a smoke control approach appropriate for the application. This author was retained during construction of a project where the contractor was attempting to achieve a pressure differential between two large-volume spaces. The pressurization method was the wrong approach for this building, and achieving the pressures proved unfeasible. One should involve a fire protection engineer or smoke-control-savvy mechanical engineer and create the right game plan from the beginning.
Do not spend a lot of time creating complex computer models too early in the design process. The design will change. Programming will be updated. Horizontal openings will move, grow, and multiply. One should hold on the computer modeling until the schematic design is finalized. A relatively stable BIM model can be used to import the geometry into a fire modeling program instead of building it painstakingly by hand.
Do use defendable and appropriate design fire scenarios. National Fire Protection Association (NFPA) 101, Life Safety Code, lists eight scenarios that are required to be considered for performance-based design. Along with design fire locations, the maximum size and characteristics of the design fire are important. Just because fire test data may be available for a burning chair, is that a severe-case fire for the space in question? Documentation of these assumptions and inputs tie in to the aforementioned Fire Engineering Design Brief to be presented to the AHJ early on for its buy-in.
Do not put all the exhaust in one place. Even if the exhaust volume satisfies the hand calculations, providing all 200,000 cfm in one corner of the atrium will probably not be effective for a design fire in distant locations. Firstly, concentrated exhaust can create plugholing, where the exhaust is so strong it pulls fresh air in through the smoke layer and therefore renders the system useless. Secondly, if smoke is required to be pulled long distances across a ceiling, it entrains more air and creates more smoke, so the original design exhaust volume may prove inadequate. Distribute exhaust inlet locations as broadly as possible to create an even exhaust scheme. Computational fluid dynamics (CFD) modeling illuminates these issues.
Do look and plan ahead for the testing and inspection process. If possible engage the commissioning agent during the design phase to coordinate and communicate the design of the system, establishing a commissioning plan in the process. It is important to define not only what is being tested, but also the schedule, order, and the pass/fail criteria.
Brian Kuhn Jr., PE, LEED Green Associate, is a fire protection engineer and life safety consultant with Simpson Gumpertz & Heger based in the firm’s Boston headquarters. His primary interests and capabilities are in the fields of computer fire, smoke and egress modeling, structural fire protection, and code consulting for various occupancies. Kuhn works with architects, structural engineers, and building scientists on a variety of fire and life safety building performance issues. He has a master’s degree in fire protection engineering and a bachelor’s degree in mechanical engineering, both from Worcester Polytechnic Institute. He can be reached via e-mail at bdkuhn@sgh.com.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
JSESSIONID
session
The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
__cf_bm
30 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gat
1 minute
This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites.
_gat_UA-
1 minute
A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to.
_gid
1 day
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
CONSENT
2 years
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
ADV_u_id
3 months 8 days
Unique customer identifier used to track unique ad views and interactions with some ads.
loc
never
AddThis sets this geolocation cookie to help understand the location of users who share the information.
OAGEO
session
OpenX sets this cookie to avoid the repeated display of the same ad.
OAID
1 year
Cookie set to record whether the user has opted out of the collection of information by the AdsWizz Service Cookies.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.