Unless you're tuned in as an AHJ yourself, you've likely made a few "code calls" to a code authority and asked a litany of questions to make sure your project's design meets the local requirements.
I'm not even sure if the term "code call" is a common term, but I've heard it enough that I suspect you already know what I'm talking about regardless of where you call home.
I enjoy this process now, but I didn't always. Fresh out of school I'm pretty sure I was visibly shaking the time I first made a code call. I was sure that within seconds my cover would be blown and it would be all too obvious that I had no idea what I was talking about. Despite my awkwardness (I make a good engineer, right??) nothing went sour and since then I've slowly learned and repeated many many times.
There was even one of my favorite code calls that I made about an elementary school to coordinate local fire alarm requirements. It was only right after the call late on a Friday afternoon that I found out that the fire marshal I just spoke with was hired onto our team and was starting the following Monday. They say fire protection is a small world, right? He turned out to be one of the most knowledgeable people I know and one of my favorite people to work alongside.
The Joys & Pains of Code Calls
Code calls also come in many different flavors.
Sometimes I'm just shocked by how friendly and helpful code authorities are. I once made a call at 15 minutes till 5pm on a Friday to a small town in Arkansas, thinking I would just leave a voicemail. After my questions, I asked if the department conducted flow tests, and while he said they did, he apologized that because of a prior commitment he couldn't do it then but would be happy to do it first thing Monday morning. I almost fell out of my chair. Very helpful and caring people in this field.
On the contrary, sometimes the hardest part about a code call is just finding the right person to speak with who is actually responsible for plan review of fire protection systems and getting a few minutes of their time. Not to pick on New York City because I love the people there and speak with a handful of you regularly, but if you're trying to get a hold of someone to verify or coordinate a few particulars of your system... well... good luck! Maybe it's because they knew I can't stand the Yankees.
I also sometimes get AHJs who simply say all they do is 'per code' and they aren't interested in talking specifics. The whole point of the call is filling in the gaps where a code or standard does not direct but rather defers decisions to the AHJ.
Want a siamese fire department connection with national thread, or a Storz-type? Either way is code compliant. As an engineer I can make either way work.
Is a wall-mounted FDC permissible, or does it need to be freestanding? Either location is compliant, but NFPA 13 says the location needs to be coordinated with the AHJ.
What I've gathered and refined over hundreds of code calls is my cheatsheet I currently use today. Just like the design cheatsheet, if you're using the Toolkit you can quickly highlight categories for your record keeping.
What's even better about this tool, though, is that you can quickly fill in the content (while on the call) and then right after save as a PDF and email to the AHJ themselves. Want them to have a record of the call and a quick way to verify your notes? Great! You now have a logged code call and the AHJ has an opportunity to review your notes.
The process of calling, taking notes, and composing the email used to take close to an hour total. This tool alone brings that total time to about 15-20 minutes. That's three-quarters of an hour you could save on every job you make the call!
A Radical Big-Picture Concept
One of my longer big-picture ideas to help the industry is to beta test and, if successful, open up a larger code-call database. I envision this as a database that brings designers and code authorities together to make local requirements clear and help jurisdictions get installations that reflect their preferences and mandates.
Want to know what hydraulic safety factor is required for sprinkler systems in Springfield, Illinois? Great - a quick query in the database reveals that and a clean list of other local requirements.
Want to know what type and location for FDC's that Tucson, Arizona requires? Great, we'd have that too.
This would clearly have a huge value for designers and engineers - but what I'm really curious about is how to incentivize code authorities to take the survey or help us populate the database. If you're an AHJ, email me (firstname.lastname@example.org) or comment below about whether you'd be open to the idea of making your local requirements public in a database.
I would have to think that AHJ input would only help local authorities get installations that match their needs - but I also know that getting action out of anyone is only possible with mutual benefit and sometimes incentives.
Just like the Design Cheatsheet posted a couple weeks ago, this form is integrated into the updated version of the MeyerFire Toolkit ready for download today. Below is a blank and filled-in template.
If you're already a Toolkit user, you can download the code call cheatsheet today by logging in here. If you're not using the Toolkit, you might consider joining in on what's quickly becoming what some consider the best tool for fire sprinkler design under $200. See more about it here.
The Questions on My List
The current code call checklist I use today has had items added and scratched over years of finding out what's important and what questions always get the same answers.
That being said, there's no real one defined list that matches everyone's preferences. What questions do you ask that you feel are important to the design that's not explicit in code? Comment below.
Join the Cause
Our line of work in helping save lives and property is extremely important, but you already know that. This site is built to help you excel in fire protection. If you're not already subscribed to these free weekly resources & articles, you can do so here for free.
First - thank you for such a warm response to last week's article on a major and thorny topic of using sprinklers alongside glazing in rated assemblies. I genuinely appreciate and am motivated by so many thoughtful people in our industry.
As I mentioned last week, below is a link to the original article with the new PDF summary. It compares rated window assemblies, use of closely-spaced sprinklers for atrium enclosures, and the use of window sprinklers across many important categories.
If you find this useful, please consider sharing with others who also may be interested in the content. If you're not already subscribed, you can get this and many other similar resources for fire protection design, inspection, review, & engineering by subscribing, for free, here.
Thanks & have a great weekend!
Please don't take me to be an elitist.
I know what you’re thinking – yeah, right – this chump is from St. Louis and he’s not full of himself!?
It’s true I was raised in and have since circled back to St. Louis, Missouri. If you've heard of St. Louis it's probably because we're the most dangerous city in Missouri, or the Midwest, or the world or something. It's really not that bad if you don't have kids or go outside after sunset.
The other knock on St. Louis is that we're secretly wishing we were Chicago and, in terms of self-inflated ego, consider ourselves the last city on the East Coast.
Yeah that's also true.
While I am proud of our baseball team and beer production, please don't take me to be an elitist.
For instance, if you and I are talking fire protection and you use any of the following common wrong terms, I won't correct you. I don't even see a need to correct any of these terms, but I do find it interesting that several slightly incorrect phrases have been so pervasive in the fire protection industry.
Here’s my top list of misnomers in fire protection:
6. "Semi-Recessed" Sprinklers
I mentioned that I don't try and correct terms. The "semi-recessed" sprinkler is the reason I don't.
I had some very knowledgeable and technical counterparts in a prior role that were driven a little crazy with the term "semi-recessed".
A sprinkler can be concealed (only coverplate showing), can be fully-exposed pendent, or it can be recessed (deflector located closer to the ceiling as to show less).
If you consider a concealed sprinkler to be "fully-recessed," then I understand the logic that gets us to the "semi-recessed" designation.
However, some read "semi-recessed" a redundant term along the lines of "we want this partially exposed, but only partially." Putting the semi- is asking for partial of the partial.
5. Goose Necks
“Fire sprinkler return bend” is not as much fun as saying "goose neck," yet the two terms are synonymous for fire sprinkler systems. Of any of the odd or misappropriated terms in fire protection this one is the least offensive and is technically not even a misnomer.
That being said, three sticks of pipe and a couple elbows off a pipe outlet just doesn't scream goose to me...
The Goose Neck, also known as a fire sprinkler return bend.
4. Everything Is Awesome... and apparently is a Fire Wall
I enjoy working with architects. I do, and I'm not just saying that because my mortgage depends upon their continued blessing.
One requirement I'm convinced is part of the architect licensing is to call any rated separation a “Fire Wall.”
Fire Barrier, Fire Partitions, Smoke Barrier? Nope.
If it's not a rated wall that extends through the entire building and allows structural collapse on either side, it's probably not a Fire Wall and is more than likely a Fire Barrier. If it’s a separation wall in I-1 or some residential occupancies, tenant space separation, corridor walls, elevator lobbies, or egress balconies it may even only be a Fire Partition.
3. Spelling the "E" word
I never won a spelling bee as a child, but I'm confident enough I don't often run spellcheck.
My run as an ever-confident fire protection engineer ended when a peer review from another firm pointed out my incorrect spelling of "escutcheon". I'd like to pretend it was a one-off instance, but the misspelling was in a standard detail I had created and had been using for a couple years. Swing and a miss.
Es-cutch-eon: a flat piece of metal for protection or covering around a hole or void. And a tough one to spell.
2. Fully-Sprinkled Building
Your preschooler's dream: a fully-sprinkled building.
This one can be a little hard to spot, but did you notice there’s an “er” missing in this term?
When it happens I just imagine raining sprinkles through a building. Sounds tasty, but have you ever tried sprinkles plain? Not good.
1. Sprinkler Head
Lastly, this is the big one.
In the origins of fire sprinkler systems, a "sprinkler head" was a designation to the device that forced water distribution at the tip of the system.
Over 100 years later the fire sprinkler is still around, but the sprinkler has since adapted to the name "sprinkler" in lieu of "sprinkler head".
A sprinkler head.
Need evidence? It takes NFPA 13, the leading authority on fire sprinkler systems, 22 chapters before even mentioning the term "sprinkler head", and even then uses the term in talking about cabinet installation for nitrate film protection. Hardly a reining endorsement or common usage of the term.
In fact, Chapter 22 is the only chapter that even uses the term "sprinkler head". All other references are to the "sprinkler" or "fire sprinkler" throughout the entire standard.
What's the beef with using the term "sprinkler head"? Well, sprinklers don't have heads. They have frames and deflectors, but no heads. Besides, a whole lot of peeping “heads” throughout a building would just be creepy.
Hollywood already does our industry enough disservice, we don't need people thinking there's heads in the sprinklers, right?
Have you come across any of these? What are your pet peeves? Comment here.
Do you get these free articles by email? Subscribe here if not.
Not all code revisions are more conservative.
The 2018 Edition of NFPA 101 has updated the long-held occupant load factor of 100 sqft per person to 150 sqft per person. If you don’t live in the life safety arena, this change allows the calculated occupant load for a business space to be notably less, thereby requiring less exit width, stair width, potentially the number of exits, and other means of egress requirements.
The 1934 Building Exit Code first incorporated the density of 100 sqft per person, which was based upon a 1922 recommendation from the Building Exit code committee. It has since carried through over eight decades of code revisions and has lasted through many differences in office design.
Concentrated Business Use Introduced in 2015
The Life Safety Code introduced the Occupant Load Factor for “Concentrated Business Use” at 50 sqft per person in the 2015 Edition.
The goal with determining occupant loads has always been to provide the means of egress for a maximum probable number of occupants, and the introduced higher density was intended to address higher-density spaces than would normally be expected in a business occupancy. Annex material in NFPA 101 states that this should be applied where occupant concentrations are maximized, such as business call centers, trading floors, or data processing centers.
Modern open office concepts have changed the way we congregate and occupy buildings
Challenges with High Occupant Loads
This 2015 Edition change, according to testimony in committee hearings for 2018, has brought increased scrutiny and sometimes higher occupant loads to business occupancies by review authorities.
Increased occupant loads impact egress capacity, additional exiting, and can be very difficult to achieve higher occupant loads in existing buildings. Without additional horizontal exiting or plumbing fixtures, many existing office buildings cannot accommodate redesigns under higher occupant loads.
Open office concepts have also introduced new challenges. Collaborative spaces are sometimes being reviewed as assembly, even though these small rooms are intended and often used by the same people that are no longer at their workstations. The occupant load could effectively double-count the same occupant for two different work areas.
While terminology for the collaboration rooms is not entirely defined, modern office buildings are often labeling these as huddle rooms, quiet rooms, focus rooms, enclave rooms, or other owner-specific terms. These type spaces appear to meet the intent for the new collaborative room load factors identified below.
Collaboration rooms, often labeled as huddle, quiet, focus, or enclave rooms, are often used for smaller group activities by people who otherwise occupy the open office space. These smaller spaces function differently than traditional conference rooms.
Researching New Load Factors
The NFPA Fire Protection Research Foundation sought to study the appropriateness of the business occupant load factor for modern buildings in 2012.
Two studies stemmed from their initiative; a WPI Student Research project studies office building designs, modern changes in the workplace, and occupancy impacts of flexible employee scheduling and telecommuting. This study suggested it would be reasonable to increase the load factor to 150 sqft per person.
The second study, by Gilbert Group at the University of Canterbury in Spain, found average load factors for modern office buildings averaged 181 sqft per person. Both studies summarized that the 100 sqft per person occupant load was considered conservative.
Further testimony in the committee hearings suggested that at least ten research studies on office buildings conducted since 1935 have indicated that the Occupant Load Factor for businesses was conservative at 100 sqft per person.
The research, motions, and resulting voting brought a few major changes to the 2018 Edition of NFPA 101. Business use occupant load factor has increased from 100 sqft to 150 sqft per person; the “Concentrated Business Use” load factor has remained from the 2015 edition; and lastly small collaboration rooms and large collaboration rooms (with a threshold at 450 sqft) are given occupant load factors of 30 sqft and 15 sqft per person, respectively:
NFPA 101 Updates to Business Occupancies by Year
While the discussion above considers the process for NFPA 101 Changes, the International Building Code has similar provisions for the 2018 Edition for Business Occupant Load Factors as well as definitions of net and gross floor areas (Table 1004.1.2 and Chapter 2 Definitions, respectively).
Lastly, occupant loads of 50 people or more in a single space would still consider the space to be assembly and not a business occupancy. Large presentation rooms, training areas, or lecture halls can quickly introduce assembly occupancy requirements that are unaffected by these changes.
Find this article helpful? Subscribe for free or forward to a friend.
Get Free Articles via Email:
+ Get calculators, tools, resources and articles
+ Get our PDF Flowchart for Canopy & Overhang Requirements instantly
+ No spam
+ Unsubscribe anytime
Get access to every tool, the downloadable Toolkit, Sprinkler Database, Daily Post-a-Question and more:
Joseph Meyer, PE, is a Fire Protection Engineer in St. Louis, Missouri. See bio on About page.