One of the things I feared most when I had my first real job was that I was going to be exposed as a complete fraud.

Yes, I had a degree. That degree had a grand total of 9 credit hours specifically to fire protection, which statistically is more than roughly 90% of our industry starts out with.

But, see, the problem was… that I knew nothing.

I knew this.

But my fear was that when I made my first phone call to someone on the other line, they’d quickly know this too.

​And that all came in the form of my first ‘code call.’

THE CODE CALL
We used the term code call, I don’t know what you might call it, but it’s just a touchpoint check in with the AHJ to be sure that (1) we’re on the right track with applicable codes and standards, and (2) that we coordinate jurisdictional needs.

What good is a set of engineering bid plans, if we halfhazardly threw an FDC in the wrong spot? Or the fire alarm control panel? If we referenced the wrong codes? If we stipulated too low of a hydraulic safety factor? If we located the hose connections on the wrong landings?

The answer is no good at all. If we’re not helping clarify and coordinate the needs of the project with the jurisdiction, then we, as consultants, are simply getting in the way and making things more difficult than they need to be.

IMPOSTER SYNDROME
​Back to that phone call.

How long would it take for the person on the other line to realize that I knew very nearly absolutely nothing about fire protection?

That if they asked one clarifying question, it would call my bluff and I’d have no escape? Ten seconds? Twenty seconds? It wasn’t an irrational fear, nor was it overwhelming.

I made that call. And more after it. And I did make a fool of myself. I once asked “do you require duct detectors to be located on the supply side, return side, or per code?”

The response: “Why would it be anything other than per code?”

Ope. Game’s up. I have no idea. Time to pack the bags and find a new career.

 
All drama aside, I survived. Sometimes failed. I learned. I slowly grew to understand the purpose behind our list of questions.

Who were these people I was calling?

That’s half the game. Sometimes it’s a Fire Marshal. Sometimes it’s a plan review as part of the building department. Or fire department. Sometimes it’s the volunteer combination of Fire Chief/Marshal/Inspector/Reviewer.

Sometimes they were the nicest people I’ve ever met. Sometimes hostile. Just goes with the territory.

I’ve had jurisdictions that wouldn’t pick up the phone unless I called from a local area code. And I’ve had others apologize because they wouldn’t be able to run a flow test for me until Monday morning. (I had called on a Friday. At 4:45pm). 

Diatribe aside, I’d like to share the list of questions that I ask – (1) – so you can critique and help us all improve upon the list of questions – and (2) – so that future generations of inexperienced callers might not have to suffer the imposter syndrome that I did with those first few calls.

WHO IS THIS FOR?
Here is my developed list of questions that I would ask today for a code call. This is very specifically used for consultants to coordinate requirements with AHJs before a bid set is issued.

Why isn't this used for contractors? Would I ask this when doing shop drawings?

No; I might coordinate FDC types and locations. Coordinate standpipes. Coordinate some fire alarm or waterflow questions. However, a designer at the shop drawing stage is not the person to determine the scope. They can and should coordinate, but not determine scope.

A consultant's role is to determine the scope, so principally these questions are supposed to happen before bids ever take place. These do have cost impacts.

MY LIST OF QUESTIONS (AND NOTES)
Below it is a very short  context for why I ask the question. Code basis can wait for now. This is long enough as is.

What I ask from you is what you would tweak?

If you’re an AHJ, how can I better ask the question?

How can I better clarify the intent of the question?
 
OPEN-RESOURCE FOR CODE CALLS
We’re actively working on an open and free tool just for code calls. Some time ago we tried a spinoff code call database, but the enthusiasm for jurisdictions to volunteer information wasn’t something that we could get to scale.

So I’d like to try this from a different angle.

My hope is that, if we construct this open tool right, and educate around the process in the open, it could be a tremendous resource for both designers and AHJs to meet in the middle and have coordinated projects that meet the needs of each jurisdiction.

Easier and better results, every time.

So, here’s the list of questions that I would ask today, almost like a script.

My own personal notes are italicized below each question.
 
BRIEF INTRO
Thanks for taking my call. I’m Joe Meyer, designing the [project] at [address]. It’s going to have [fire alarm/sprinkler/standpipe system(s)], and I’d like to ask you a few questions to make sure we’re coordinated with your department. Should take about five minutes. Is that OK?
  → Note: If the time isn’t good, or they’d prefer an email, I’d go that route instead.
 
APPLICABLE CODES & STANDARDS
1. Great. Your website says you’ve adopted the [2012/2015/2018/2021/2024 IBC or NFPA 101], is that correct?
  → Note: Doing the research ahead of time is key. Without it, it makes the listener feel like they’re doing the work.
 
2. Do you adopt any specific editions of NFPA standards like NFPA 13, 14, or 72, or just whichever edition is referenced by your building code?
  → Note: Many people don’t know this, but IBC Chapter 35 and NFPA 101 Appendix D or E will actually list which editions of NFPA standards are referenced. Some jurisdictions will adopt very specific editions, which is why I like to ask the question here.

Following questions noted with an asterisk (*) are only asked if necessary.

FIRE ALARM*
3. For fire alarm, we intend to locate the main control panel in [front entry/main electrical room/a back of house area]. If we do so, do you require an annunciator panel at the building’s front entry?
  → Note: For small buildings with one main entry where the FACU is located near the entry, no annunciator is usually needed. For larger or more complex buildings, when we might not want the FACU at the front entry, having an annunciator at the front is a very reasonable need.
 
4. Does the fire alarm monitoring require a listed Central Station Service, or is standard code-required monitoring, like a supervising station, acceptable?
  → Note: Jurisdictions that require a listed Central Station service usually know what it is, and will recognize that it’s required. It’s more expensive and carries more stringent requirements than a normal supervising station, which is a code-minimum requirement.
 
DUCT DETECTION*
5. When duct detectors are needed, do you simply require locations to be per [the IMC/NFPA 90A], or do you require duct detectors to be located in specific locations, like the supply or return side of units in the ductwork?
  → Note: This is a question I could use help with. A simple ‘per code’ answer is wanted here, but some jurisdictions have insisted on locating duct detectors on the supply-side of units, or return-side, or both. If the jurisdiction has a specific requirement, I’d like to know that now rather than be surprised later, but most usually don’t, and as a result, it’s a lame question to ask in those cases.
 
6. Do you require duct detectors to initiate an alarm signal, or is it OK to have those report a supervisory signal to the fire alarm control panel?
  → Note: NFPA 72 allows duct detectors to initiate a supervisory signal, because they’re more prone to nuisance alarms than other devices. An alarm signal usually results in a truck rolling up to the building each time. Jurisdictions that are familiar with this topic are usually more than happy to have duct detectors on supervisory rather than alarm.
 
7. When a duct detector activates, can it shut down just that unit or do you require all units to be shutdown?
  → Note: To my understanding, this is just a preference. Not a huge deal either way unless we’re talking about a massive building or building complex where all units shutting down would be very uncomfortable and problematic.
 
SECURITY / KNOX BOX
8. Do you require a Knox Box?
  → Note: There’s likely a code path for this, but it’s not something I’ve hunted down to date. Most jurisdictions can readily answer this.
 
9. Is the Knox Box required to tie to the fire alarm system?
  → Note: These can be monitored by the fire alarm system. Most jurisdictions don’t require them to be monitored, but some will in areas that have higher crime rates.
 
FIRE SUPPRESSION - FIRE DEPARTMENT CONNECTION*
10. Do you mandate a maximum distance from a fire department connection to a nearest hydrant?
  → Note: Some jurisdictions care, others less so. There’s (to my knowledge) not a mandated distance, but some jurisdictions will require as close as 50 ft and others as far away as 400 ft.
 
11. Can the FDC be mounted on the building’s street-facing exterior wall, or does it have to be located remotely from the building?
  → Note: As a designer, my strong preference is to have the FDC on the building to save cost, protect the pipe from freezing, protect the pipe from mechanical damage, keep it clear from snow, and keep it easier to inspect, maintain, or repair. Operationally, depending on the building and the site, some departments are not going to want to send firefighters to the building face and would rather have a remote connection for some applications.
 
12. What type of FDC do you use [Dual-Inlet 2-1/2” / 4” Storz / 5” Storz]?
 
13. Do you require locking caps on the FDC?
  → Note: Some jurisdictions will have locking caps to prevent people from shoving debris, trash, or other ‘items’ into FDCs, and to prevent theft of the caps. Many areas have no need for locking caps.
 
BACKFLOW*
14. What type of backflow preventer do you require [double check, double check detector, RPZ, or RPZ detector]? We [will/will not] have antifreeze or chemical additives in the system.
  → Note: Some jurisdictions, like fire departments, may not want to answer this because it’s under the building or water department. But most are familiar with the requirements anyways. Some places require RPZs for everything fire protection (like an Illinois state mandate). By code, RPZs are required if an antifreeze system is used, or if chemical additives are added to the system (such as corrosion inhibitors like Vapor Pipe Shield).
 
15. We intend to locate the backflow inside the building. Is this acceptable?
  → Note: This is a designer preference for longevity of the backflow, protection from damage and tampering, protection from freezing, service, maintenance, and cost. Some owners may want the floor space or jurisdictions might require it to be outside (though I don’t know why).
 
16. [If a double check is allowed, allowed to be inside, and there is only a single zone] We intend to use a backflow preventer that’s listed for a vertical orientation. Is it acceptable to install it vertically?
  → Note: RPZs have to be horizontal. If we have single-zone systems, designers generally prefer to use a ‘shotgun’ approach and save floor space. This is usually fine.
 
HYDRAULICS*
17. Do you mandate a safety factor for fire sprinkler systems?
  → Note: This is a topic that is book-worthy. NFPA 13 has no mandate other than to account for seasonal and daily fluctuation. It could be argued that a safety factor is implicit within NFPA 13. But to save everyone’s time and scrutiny, a simple 5 PSI or 10% safety factor tends to be common practice. Too high a safety factor isn’t necessarily a good thing because it could lead to needing a fire pump that introduces many new points of failure or could add unnecessary cost to a system.
 
18. Does your department conduct flow tests, can we conduct a flow test, or are those done by the water department?
  → Note: This is just practice-based by jurisdiction. Some don’t allow flow tests at all and use water modeling (California).
 
INSPECTOR'S TEST*
19. [If there are only wet systems] We usually locate the inspector’s test at the riser, which NFPA 13 allows for wet systems. Do you require it to be located remotely?
  → Note: If this is a dry or pre-action system, then the inspector’s test must be remote. If it’s wet, it’s allowed to be at the riser. That said, some jurisdictions have a preference which we’d want to accommodate here.
 
WATERFLOW*
20. Do you want a horn/strobe, or electric bell on the outside of the building for waterflow?
  → Note: Just a jurisdictional preference. Either of these are easier to accommodate than a water motor gong which had been the tradition for some time.
 
21. Is exterior access required for the sprinkler riser room?
  → Note: These are usually on the outside of the building since the water service entry cannot go more than 10 ft underneath the building without open trenches, per NFPA 13, but sprinkler riser rooms don’t always have an exterior door.
 
SITE
22. Just a few more questions. Do you require a post-indicating valve? There are no code mandates for one.
  → Note: Some jurisdictions want them, many don’t care. Just an opportunity to coordinate it early here.
 
23. Is Fire Flow ok to be determined using the International Fire Code Appendix B, or do you have some other method to calculate it?
  → Note: Fire Flow is wildly misunderstood and falls through the cracks of design scope. As a result, many jurisdictions don’t pay attention to it or aren’t familiar with it. If they don’t know or don’t care, Appendix B is a fine approach to use.
 
FIRE PUMP*
24. We have a fire pump on this project. Do you consider the electric power supply to be Reliable or not?
  → Note: NFPA 70 has specifics on how power is considered to be reliable or not. There are formal definitions, but it’s up to the AHJ on whether they consider the power utility at the site to be reliable or not. If it’s a point of contention or needing clarification, it’s worth spending time here because the cost to go from an electric fire pump to a diesel or add a generator can be substantial.
 
STANDPIPES*
25. We intend to have a [wet/dry manual/semi-automatic/automatic] standpipe system for this building, using [Class I 2½” / Class II / Class III] hose connections.
  → Note: In sticky projects using dry standpipes or high-rises, the type needs to be coordinated. In basic non-high-rise situations, a wet manual system is fairly straightforward, so it’s not a question as much as a coordination point.
 
26. We intend to locate hose connections on the floor level landings of stairs. Is that acceptable?
  → Note: The IBC and NFPA 14 have jogged back and forth on this, but they now correlate on the main-floor-level landings of stairways for hose connections. AHJs are permitted to require intermediate-level landings in both the IBC and NFPA 14, though, so it’s an important coordination point.
 
Thank you SO much for your time. Any questions for me, or anything else you feel I should have asked?


YOUR TURN
Alright - it's all out there - what would you tweak?

If you’re an AHJ, how can I better ask the question?

How can I better clarify the intent of the question?

What am I missing? Would absolutely love your commentary below. Your input can make this new collaborate tool much more helpful and hopefully impactful for the industry as we launch it and hopefully move things forward.

See you in the comments ↓↓

- Joe 

By Jocelyn Sarrantonio, PE | Technical Director at MeyerFire

NEW N^1.85 GRAPH PAPER
This time of year in many parts of the US, the kids are heading back to school and parents are gleefully filling their bags with all of their required school supplies.

It seems to be an appropriate time to also publish our own “school supply” for fire protection engineers: a new clean version of the N^1.85 graph paper. You can download it here:

If you took the new course released this week, FX131: Water Supply Evaluation, you may have already seen the new tool and understand why it is valuable.

For everyone else, N^1.85 graph paper is a very specific tool that helps us evaluate water supplies for fire protection.

USE OF THE GRAPH
There is a Water Supply Analysis tool in the MeyerFire toolkit that will also display water supply data nicely, but this is a blank graph that you can use for your analysis. The graph paper is a visual and analytical tool that helps evaluate the characteristics of your water supply, extrapolate to evaluate the fire flow available, visually see if the water supply can accommodate a particular demand, and estimate safety factors.

The graph is useful if you’re in the beginning stages of a project and answering a lot of “what-if” type questions, without having to calculate exponents over and over again, and it’s also helpful in the later stages of a project, when performing and evaluating sprinkler system hydraulic calculations.

The graph is special because it’s based on the flow value in the Hazen-Williams formula, which is raised to the 1.85 exponent. I’ve never tried to do this in Excel but there are lots of forums which make it seem awkward or impossible to work with uncommon exponents. So that’s why most of us rely on a few of the online tools out there, the Toolkit, or our hard copy graph paper we have tucked away.

If you’ve been in the fire protection industry a while, or even if you just started, someone may have handed you a heavily photocopied blank N^1.85 graph that you may have stuck in a binder or folder somewhere. I still have mine from when I first started! Back then I would literally plot my water supply with a pencil and mark off the sprinkler system demand to evaluate water supplies during a project.

One of the curiosities I have every time I run a main drain or see one run is how much flow the system is actually discharging.

From the amount of discussion and inquiries one of our tools has generated, I know many of you are curious about it, too.
 
HOW MUCH DOES THE MAIN DRAIN ACTUALLY FLOW?
For one – if we knew with some certainty how much flow came through the main drain, then we could actually complete a backflow forward-flow test entirely just by opening up the main drain all the way.

That’s the theory, at least, that I’ve heard some people point to as to why they don’t provide another fixed means of forward flow.

For a lower hazard system; say a system whose greatest challenge is still Light Hazard – it’s not unfathomable that a fully-open 2-inch main drain could flow at least the system demand (which might be as low as 120 gpm for a minimum quick response (QR) reduction area and 30% overage, no hose allowance included).

Even for an Ordinary Hazard Group 2 system using a QR area reduction and 30% overage, the system flow may still be in the 220-250 gpm range. Would a fully open 2-inch main drain be enough to handle it?
​
Or what if that main drain was upsized to 2-1/2 inches?
 
This piques the curiosity, right?
 
IS FORWARD-FLOW ACHIEVABLE THROUGH A MAIN DRAIN? IF SO, WHEN?
It would be very nice to have an idea if forward flow was achievable for some of these lighter-weight systems just through the main drain.
 
The Drain Flow Estimator

We introduced a tool we called the Drain Flow Estimator tool a while back (https://www.meyerfire.com/blog/a-new-fire-sprinkler-test-drain-flow-calculator), which was built to estimate the maximum possible flow from an inspector’s test or a main drain.

That tool only uses one calculation: discharging water through an open orifice:

Let’s say we have a very large water storage tank and poke a hole in the side of it near the bottom. How fast does water drain from the tank?

We have a formula for that. It’s Q = 29.84 C d^2 √p.

That is, we have a flow (gpm) that is constrained by the type of opening (C, the discharge coefficient), the diameter of the opening (d, in inches), and the total system pressure at the opening (p).

​We use this regularly when we conduct fire hydrant flow tests. The equation translates pitot pressure to how much flow comes out of the opening. We took measurement inaccuracy into account and built this out into its complete tool for converting pitot pressures to flows (https://www.meyerfire.com/blog/new-pitot-to-flow-rate-converter-with-precision).

THE PROBLEM
​Here’s the problem with using only that equation to estimate flow from a main drain – it’s the maximum possible flow.
​
Now, it meets the need that we had for building the tool—to estimate the maximum possible flow so that we could size drains appropriately (hint: don’t run an inspector’s test or main drain to a janitor’s sink).

It serves its purpose of estimating the maximum possible flow.

However, the Drain Flow Estimator tool doesn’t provide a realistic amount of flow through the main drain or inspector’s test and drain, only the maximum.

That’s problematic if we want to know the actual flow through a Test and Drain or a Main Drain, as discussed earlier.

Why is it the maximum and not actual?

#1 PIPE CONSTRICTION
That is, we’re not accounting for the pipe's constriction between the opening and the riser, the friction loss within the riser itself, the loss through the elbows along that path, or the constriction at the valve opening.

#2 TYPE OF PRESSURE
Another thing we’re not really considering is the type of pressure that’s measured. When we take a pitot pressure measurement, we insert a tube into the centerline of the water flow.

The pressure measurement taken from a pitot gauge accounts for the static pressure of the water (the normal pressure that is exerted in all directions) and the velocity pressure caused by the forward motion of the water.

​That’s what a pitot gauge is measuring—the total pressure.

​A gauge on a riser does not measure total pressure; it measures normal pressure. That is, it doesn’t matter if the water is standing still or moving at 20 feet per second. The gauge is only measuring the pressure that runs perpendicular to the pipe in the normal direction.

#3 LOCATION OF PRESSURE
The last source of error is where the pressure is measured.

For a hydrant flow test, we measure the pitot pressure immediately after the hydrant opening. We use the formula and convert it to a flow, knowing the pressure right at that opening.

If we instead use this same formula for an open orifice but add a pressure upstream at the riser, then we’re using a higher pressure than what will be available downstream at the opening of the main drain.

If we want to know the maximum possible flow, that’s probably fine. That’s the extreme case.

But if we want to know the actual flow through the drain, then that’s problematic; it’s another source of error.
 
BUILD A TOOL THAT CAPTURES ACTUAL?
So, how would we construct a tool that estimates the actual flow through a main drain?

Well, in theory, we could work an iterative loop like this:

1. Assume a pitot pressure right at the opening of the main drain (the 45-degree elbow discharging to the outside, for instance).
2. Translate the pitot pressure to a flow based on the characteristics of the opening.
3. Knowing the flow through the opening, we could calculate the friction loss as we move upstream through the main drain.
   1. We will gain pressure as we move upstream, just as in a hydraulic calculation.
   2. This would require an estimated C-factor for the pipe, knowledge of how the main drain is routed, and information about the pressure loss at a main drain valve.
4. At the point where the drain connects to the riser, we could determine the pressure at that intersection, and we still know the flow.
5. We calculate the friction loss going upstream through the riser until we reach the riser pressure gauge.
   1. We would need to have an estimated C-Factor for the pipe and know the routing of the riser.
6. Now, we would have a total pressure where the gauge is located.
7. We also know the velocity of the water movement in the riser, which we can use to translate our total pressure into the normal pressure, which is what the gauge is reading.
8. We would compare the estimated normal pressure calculated to the actual normal pressure in our real-world test.
   1. If our estimated pressure at the riser is too high, we restart our loop and assume a lower initial pitot pressure.
   2. If our estimated pressure at the riser is too low, we restart our loop and assume a higher initial pitot pressure.
9. We iterate this loop until we’re close enough for our needed accuracy.

 
As a result of this process, we would have an iterated, balanced supply-side hydraulic calculation that estimates the flow coming through the main drain.
 
If you love the math or the theoretical exercise – weigh in on your take. Open to ideas on this.

DOWNSIDE & POTENTIAL MISUSE
Now that’s great Joe, so go ahead and build it (typed in sarcastic voice font).

We can build it (and probably will because I’m curious). If we do, I’d want to go out to a parking lot and validate this in the real world 30 different ways (looking at you Fire Sprinkler Podcast).

But beyond that, there’s a fundamental issue with a calculator like this – it’s still an estimated amount of flow based on a pressure measurement at the riser but with the flow coming out downstream some distance later.

AN ESTIMATE BUT NOT REALITY
It’s not a measure of the actual flow through the opening; it’s only a calculated estimate.

The downside of not being a measurement is that if there’s some wrong assumption—say a C-factor or number of elbows or whatnot—then we introduce inaccuracy.

But it's probably hard to detect. What if we have some type of pipe constriction that we can’t see from the outside? Say there’s a large rock or dirt buildup, or the coupon that was cut for the main drain tap is actually smaller than it should be.

That constriction would throttle the actual flow down but maintain the same or higher pressure upstream at the gauge.

That is – it would look like it’s flowing more water than it actually is.

The advantage of measuring the actual flow out of a main drain is that we know with some certainty what the flow is achieving and not an estimate.

Fundamentally, I know of two quick(er) ways to measure the flow, even for a main drain.

There’s the bucket test, in which you flow into a large 55-gallon drum and time how long it takes to fill it up. Divide your bucket size by the time it takes to fill up, and you then have your average flow.
​

​Then there’s the pitot measurement. Connect a test hose with an adapter to the main drain, measure the pitot pressure, and convert it to a flow.

​Either way, you could measure the flow coming from the opening. That’s far more accurate, of course, than a tool that estimates and incorporates a handful of assumptions.
 
THE UTILITY?
Is this kind of tool, that provides a theoretical balanced supply-side flow with the supporting math and documentation, something that would be of interest?

Do you see the harm in having an estimate doing more harm than good here?

Do you ever use a main drain for forward flow on less hazardous systems, and if so, do you verify what that flow is?

Curious on your thoughts about this as a challenge in the lens of trying to create helpful resources and not circumvent or obstruct good practices.

As always, appreciate you being here and being part of the community.

​- Joe

Have you specified or encountered a specification that asks for the pipe to be "as high as possible" in areas with exposed structure?

If so, does that mean we want to pipe through the open web of a structural joist?

THEORY VERSUS REAL-WORLD
This might be the most classic design versus real-world installation conundrum. Just because something might be possible doesn't necessarily mean it will fit. 

Well, for some years now, I've asked people I respect how they determine whether a pipe can go into the joist.

SHOULD WE ROUTE IN OPEN WEB JOISTS?
We might first want to ask whether we should put the pipe in the open web joist, to begin with.

If the joists are shallow, not going to be aligned, or will they be interrupted by solid beams and the end of each bay? In those cases, then the pipe really shouldn't be up there anyway.

But, assuming we do have some depth to open-web joists, and the joists will be aligned (giving us an open and continuous path to hang the pipe), we still need to know if the pipe will fit.

LENGTH OF PIPE THAT WILL FIT
The answer from an novice consultant might be - well of course it'll fit. Just cut the length of the pipe down so that it'll fit up there.

But where do we draw that line? If we have hundreds of feet of pipe run in an open-structure area, it's going to be a labor and materials nightmare if we have to use 6-ft long sticks of pipe the whole way down. Additional fittings, additional hangers (if we want a hanger on each stick of pipe), additional labor... major cost impact.

If we can use cut lengths of 10'-6" (half of a full-length 21-ft stick of pipe), then maybe that cost impact isn't as bad.

CALCULATED APPROACHES
In asking around, I've found three different calculated methods of determining whether a pipe will fit (mathematically) to slip up and into open web joists.

Those three methods, as I can best identify, is a calculated simple method using exponential relationships of the joist depth and gap-between joists (I called it the Simplified Formula, please inform me of a source if you know it). This is the second calculation.

The third was originally credited to AFSA's Ed Miller from the 1990's, which I've identified third in the list and seems to generally be the most-conservative of the three calculated concepts.

And the main concept is a purely diagrammatical calculated approach based on the visual. The concept is that the slope of the pipe just as it slips past the joist on the right is calculated, the rise of the pipe is calculated and compared against the available open height in the space (can the height of the left-end of the pipe fit underneath an upper-chord?).

SKETCHED APPROACH
Of course, we can always draft or model up an example and see it for ourselves, but my hope in creating this tool is to shed some light on the practicality of putting pipe up into the joists and help see that relationship come together.

​Below is the tool:

TOOLKIT
If you like tools like this - you should check out our Toolkit and MeyerFire University (which includes the Toolkit). Plenty more practical tools for everyday use for the fire protection professional.

YOUR TAKE
Where do you land on this?

Have you used any of these methods before, or do you have your own?

Do you know where these originated, and if so, point me in the right direction so I can credit the right source?

​Comment below - would love to know your thoughts on the topic and where you see something like this helping.

This week we have progress and are continuing the effort to create an open, easy-to-edit and easy-to-digest basic sprinkler specification.

The first week we touched on the need and developed the general criteria. Last week we expanded on the feedback and introduced equipment to the spec.

This week we’ve adapted the specification based on feedback from you (thank you!) and are adding in the ‘means’ portion of the specification.

THE GOAL OF A SPEC
Our goal here is to have a simple baseline specification that answers the most critical questions which a specification should resolve, and otherwise stay out of the way. A great specification should:

• Be clear, unambiguous, and concise
• Address key questions for the scope of work
• Be clear about owner expectations that exceed code minimum
• Not include redundant, extra, unenforceable, or extraneous information

OUR INTENT
This specification is not intended to replace consultant’s own customized specifications that are well thought out, intentional, relevant, and updated.

They are intended to be a free, easy-access alternative to stand in for specifications that are boilerplate, don’t answer critical questions, or haven’t been updated in twenty years.
 
Based on your feedback, this week’s updates include references to water storage tank, using an imperative tone, cleaning up portions of the system, adding standpipe and dry system references, and incorporating your comments.

Don't forget to comment below on the questions we posed. I am very grateful for your input and willingness to push the industry ahead, as always!

​- Joe

Last week I posted the start of an open specification and asked for feedback - and boy did you all not disappoint!

If you haven't read that post, it's where to start. We laid out a few ground rules about what we're trying to achieve.

I genuinely appreciate the review, the comments, and the emails. I'm very encouraged by what we'll be able to build together that can improve things for all of us.

Who knew putting together specifications could be so fun? Joking - sort of.

As you're able to skim through this updated draft, which now includes Part 1 (General) and Part 2 (Products), here are some of the areas worth paying attention in a little more detail:

#1 - CHANGED SECTION NUMBER
We've updated the specification section number to reflect that this isn't just a wet-pipe specification; it's intended to consolidate many pages of redundancy into our main goal; a concise, easy-to-read and easy-to-edit specification.

#2 - NOTE TO NOT FALL BELOW CODE MINIMUM
There's a line added under C in the "1.1 DESCRIPTION OF WORK" that reads "at no time shall work be less than the applicable codes and standards listed below. Proposed alternatives, discrepancies, or questions shall be addressed by written Request for Information."

My goal here is twofold; one is that we're protecting the consultant and enabling the contractor to push back in written form. 

At the end of the day, we need a code-compliant system. The days of turning a cheek or intentionally being above code because a PE said so should be over. 

The concept with this inclusion in the specification is that if the contractor sees something (anywhere) that is less than code, then they have an avenue to have it addressed formally and an opportunity to clean it up in the project.

On the opposite side, the consultant has some relief in that they're clearly not advocating or instructing the contractor to fall below code unless it's in approved written process (such as an approved code-alternative).

I hope this to be a win-win opportunity for code-compliance at the end of the day. Like the others - curious on your take.

#3 - OPTION FOR PROFESSIONAL ENGINEER TO BE AN FPE OR "KNOWLEDGEABLE AND EXPERIENCED" IN FIRE PROTECTION
There's a tangible value to being a Fire Protection Engineer (informally an "FPE") specifically. An over-generalization would be that the Engineer has taken the time to study and pass the Fire Protection P.E. Exam, which itself is no small feat. 

With that effort and focus (which often takes months of preparation even for seasoned Engineers) there's a line in the sand that speaks to that individual 'owning' fire protection as a key area of focus and effort. 

Being an Engineer who passed the Fire Protection P.E. Exam doesn't make someone more knowledgeable (outside of learning many new facets while studying) nor better than another Engineer, but it does reflect a certain level of dedication to the fire protection field specifically.

That said, we as an industry have far fewer Fire Protection Engineers than Professional Engineers in other disciplines (my at least an order of 10-to-1), so mandating that all shop drawings be performed by or under the purview of a Fire Protection Engineer can be impractical.

It's a bigger discussion point for sure, but I've modified the specifications to either call for an FPE specifically, or to mandate a Registered Professional Engineer "who is knowledgeable and has experience in the field of Fire Protection."

I'd be curious on your take with this as well.

#4 - MOVED QUALIFICATIONS TO 1.5 QUALITY ASSURANCE
More of a practical shift here, we had a few requests to move the licensing and qualifications to the Quality Assurance section in 1.5 and out of the Submittal section of 1.4. Seems to make more sense here.

#5 - ADDED PART 2 FOR PRODUCTS
Since last week we've also drafted Part 2 where we cover Products. This should add a little more 'meat on the bone' and probably queue up plenty of contention points. 

Let me know what you like and what specifically you would change - all for building a better industry. Click below to view, and thank in advance for helping bring to life a needed resource!

One of the frustrating aspects of bidding a fire sprinkler job in North America is when you're reviewing a job and the specifications that accompany it are simply terrible - boilerplate, don't actually provide any useful information, are conflicting, include irrelevant content, or clearly haven't been updated in decades (list no longer manufactured products).

One of the ideas we kicked around a couple weeks ago was essentially an "open source" specification. One that we build and curate together and post for open use.

This is the first-stab at what "Part I" of an open, basic fire sprinkler specification might look like.

SECTION I OF THREE
Typical specifications include three parts:

1. Conditions: where the scope is described, applicable criteria is communicated, and the 'what is supposed to be done' is addressed.
2. Equipment: what equipment and products are permitted, and what are not.
3. Execution: in what ways must the work be performed.

OUR GOAL
From our collaborations, posts and discussions thus far, we're all really wanting something that is:

1. Helpful: actually provides information the contractor is needing to price a job.
2. Concise: as short as possible, so that it's easier to read and easier to edit. Don't duplicate requirements from other standards (such as NFPA 13), but simply defer back to them. We also want to limit the number of sections (again for simplicity, easy to navigate).
3. Clear: the specifications need to be easy to navigate and explicit in what is being required.
4. Timely: we don't want antiquated methods or products that aren't feasible or achievable.

There are other goals too, but those seem to be the reoccurring themes.

We explicitly do not intend for this specification to replace consultant's who already update and care for the industry. The beauty of consulting is providing unique value to your clients - this is absolutely not intended to be the only specification available. 

Rather, we would hope that it could help provide a baseline open-source template where specifications could at least be of this quality level.

YOUR INPUT
Where we could really use help here is reviewing this initial (very very first) attempt at Part I a basic open spec. 

I have highlighted GREEN and BLUE areas where a specific selection needs to be made (one or the other).

I have highlighted YELLOW additional alternatives which may be less common than a typical, mid-size commercial job.

​All portions of this specification would be editable, though the highlighted areas would be of particular concern to change and update job-to-job.

Take a look, and let us know your thoughts. If you've been long-frustrated about the prevalence of terrible specifications - then this just might be your opportunity to help us clean up the practice:

Part II, which comes next, identifies equipment and products that are allowed or not.

Part III speaks to the execution of the work - that is, any restrictions on what needs to be achieved.

THANK YOU
Just want to say a big thank you in advance for helping us really impact the industry in a positive way. I and many others very much appreciate it!

​- Joe

HOW DO WE FIX BAD SPECIFICATIONS?
Last week I touched on a concept of using large language models to instantly review a series of specifications.
Thanks for the comments! I’ll write up the step-by-step and incorporate that in a how-to video for posting here and on YouTube.

A special shout out to Kimberly Olivas, Brian Gerdwagen and Casey Milhorn on their comments in that thread – very helpful and insightful.

The discussion brings me back to two questions I may have inadvertently skipped right over –

1. Do we, as an industry, want to fix bad specifications?
2. If we do, and Pre-Bid RFIs are a luxury of the past, then what is the best way to go about improving bad specifications?

A PROBLEM WE CARE TO FIX?
If part of a bidding contractor’s value proposition is using their expertise to sort through bad specifications and give an advantage; either in exclusions or clarifications, or change orders later in the process due to inaccuracies, scope not meeting code, or scope gaps.

In other words, based on a bidding contractor’s position – there might not be any incentive for them to play their cards for competitors to see through the Pre-Bid RFI process other than a smoother project experience for the owner.

A bidding contractor is not a representative of the owner; the consultant is. Ultimately the consultant is responsible for protecting and supporting the owner – which is why they were hired in the first place.

Perhaps many contractors don’t look at it that bluntly – but I can understand the sentiment not to tip a hand at project issues when it could mean losing a bid.

WHAT’S THE ANSWER?
If Pre-Bid RFIs are not the cure-all in today’s pace of estimating – and contractors are not incentivized to be correcting consultant issues – then do we care to actually fix it?

For estimators – are bad specifications purely an annoyance for you – or do they cause issues on your projects?

Would you prefer that specifications actually be well written?

I’m not being facetious – I’d love to know your take on this.

ALTERNATIVE APPROACHES
If better specifications (and plans) are something we deem better for the industry – and we collectively want better plans and specifications – what is the approach to get there?

More specifically, how do we encourage those who don’t really care about fire protection to put a little more effort into their plans and specifications?

This was last week’s idea:

• Use AI (ChatGPT or other) to instantly review specifications for contractors to submit Pre-Bid RFIs that clarify the scope

Here are some alternative from-the-hip ideas that I’d love to kick around with you and see if you find any of these might be viable:

IDEA #1: PUBLISH AN OPEN MICROSOFT WORD FILE BASIC FIRE PROTECTION SPECIFICATION

• Community-created/reviewed
• Easy to read, easy to edit
• Free/Open
• Benefits: easy to access, eliminates excuse for costly specification programs
• Drawbacks: apathy (those who don’t care may still not use freely-accessible content)

IDEA #2: CREATE AN AI TOOL FOR CONSULTANTS TO QC THEIR OWN SPECIFICATIONS

• Basically an AI quality-control tool
• Free or low-cost
• Benefits: fast, easy to use
• Drawbacks: would be mostly mechanical in nature – AI wouldn’t be good at discerning scope compared to plans or the rest of the project. Also, apathy (see above).

IDEA #3: PROMOTE OR CREATE A LOW-COST SPECIFICATION GENERATOR

• Even easier to edit
• Low cost
• Uses today’s products and quickly generates an editable format
• Benefits: fast, easy to use, requires little effort
• Drawbacks: some cost involved

IDEA #4: HAVE A FORMAL THIRD-PARTY REVIEW PROCESS (A GROUP) FOR SPECIFICATIONS

• Real people (estimators and/or manufacturers) who would do reviews of specifications for improvements to a specification template
• Would be more of a ‘one-time’ review process, not project-specific
• Could involve NDAs to protect consultant’s work
• Benefits: real people helping improve templates overall. Would be an easy-to-access and formalized way of having multiple parties review specifications to improve overall quality. Real people helping real people.
• Drawbacks: requires time, labor, and possibly some cost - depending on the demand.

IDEA #5: PUBLIC HUMILIATION

• Going from a human-positive to human-negative approach: simply collect and post examples of bad documents/specifications in a way for everyone to learn from (but without identifying the people or companies that created them).
• Benefits: it may actually encourage real action
• Drawbacks: not fun, not an industry-building environment, can get negative quickly

IDEA #6: YOUR IDEAS

• What’s your take? How would you improve the process? What do you like or not like?

 
Do you (1) think this is a problem that should be fixed, and (2) what concepts do you think could make a difference?
 
Comment below – would love to foster a deeper discussion on how we might solve this problem before skipping ahead and creating something that might not be impactful.

One of the things that frustrates me to no end about our industry are bad specifications.

If you want to skip the story and dive right to the end – my ask today is that you comment below on what you would want an automated tool to check for when it reviews a set of specifications?

In other words, what issues have you found in specifications in the past that you would want an ideal tool to check for?

I’M GUILTY, TOO
Before I dive deeper and sound preachy, I have two disclaimers:

1. I am not above making poor specifications and I’m confident that I’ve issued bad specifications as a consultant – so I’m absolutely not above the violators I harp on here - and
2. If you are a consultant and care about the quality of your work output (true quality – as in doing quality work that helps foster a smooth project) – let me be clear that this is not directed at you. If you care to improve your work quality over time, you’re clearly not in the camp that I’m talking about today. The bad offenders, honestly, don't care - and it shows in their work.

WHAT MAKES A BAD SPECIFICATION?
What makes a bad fire protection specification?

The most dangerous is probably direction which would not meet code minimum. Ambiguity or conflicting information makes bidding difficult. Mandating things which don’t exist for the rest of the industry (such as velocity limitations in hydraulic calculations) can be unnerving and increase cost unnecessarily. Some of the most obvious parts of a bad specification are mandates for products or manufacturers that no longer exist.

The goal of a good specification is the same as the plans – clear, unambiguous communication of what is included and not included in a scope of work.

LITTLE RECOURSE
After a project is awarded, a contractor naturally has very little leverage to change the scope of work.
Perhaps there are cost-savings options that may be asked of a contractor.

Perhaps there’s a change in the project that opens up opportunities to revisit early design decisions.

But essentially, after contract award, there’s not a whole lot of leverage against complying with a bad set of specifications.

How do we address bad sets of bid documents in our industry?

If it’s life threatening and/or egregious, perhaps we could turn people into the governing boards. But how often is that done? How useful is it to permanently burn a bridge for reporting someone that may not even have any consequence?

The answer from those I speak with is almost never.

Consultants who don’t care about fire protection continue to issue plans and specifications, mostly the same as they always have, with little concern or incentive to change.

OUR INITIATIVE
Part of creating the community here is recognizing that uplifting everyone makes our industry better.

More knowledgeable contractors mean better detailed design and installations.

More knowledgeable plan review and inspectors means better policing and better final results across the board.

More knowledgeable consultants means that projects flow smoother, owners get what they need, and projects are more timely and on-budget.

Part of our responsibility here is to uplift the industry by sharing best practices and making helpful information & tools available that help us all do work better.

We have the educational piece (MeyerFire University), we have shorthand tools and cheatsheets. I write posts here. I have ideas in the works on helping improve access to basic, quality sets of specifications.

But what about now - as in today?

What is the best possible way to actually address a bad set of specifications that will get in the way of a smooth project?
 
PRE-BID RFIs
In my opinion, the most underutilized and best way to help foster a smooth project is challenging the scope before bid with a pre-bid RFI.

Pre-Bid RFIs (Request for Information) is a documented way to ask questions about the scope of a project before it is bid.
These can give an opportunity for a consultant to check their work, check their assumptions, give an opportunity to make a change if necessary, or give a chance to clarify an aspect of the scope.

Consultants can choose to play ball – help clarify the job on what should and shouldn’t be included. They can make changes if necessary, and allow bidders to bid apples-to-apples.

Contractors can also choose not to play – perhaps double down on the (incorrect) mantra of “this is the contractor’s responsibility to determine”, or something similar.

In either case, whether answered or not, Pre-Bid RFIs give the bidders either the information they seek or have greater permission (leverage?) to do as they see fit regarding the scope of the project.
 
SO MORE WORK FOR ME, JOE?
Crafting a good pre-bid RFI historically isn’t the easiest thing, though.

First – the writer has to digest enough of the project to write something coherent and competent – meaning they need to spend time looking through everything.

Second – pre-bid RFIs can sometimes have the presumption that a contractor is causing issues before they’re even on the job. This all comes down to the tone, silly as it might sound. If the pre-bid RFI is accusatory, that’s one thing. But if it’s written to help streamline a smooth project for everyone – then that’s a win for everyone.

Third – and perhaps the reason that pre-bid RFIs don’t happen as often as they should, is simply time. Bid days are time crunches. There’s a lot on the line. Going out of your way to clarify a project when you’re already on a time crunch can be tough.

This is the piece I’d like to help solve, and I think we can with some of your input.
 
THE CONCEPT
What if we had an automated tool that read a set of specifications and generated a helpful, appropriate, Pre-Bid RFI for your project?

While you’re reviewing the specifications and putting together your estimate, you do a 3-step copy and paste into ChatGPT (or something similar) that checks a whole host of specification issues and writes a Pre-Bid RFI for you?

You could have the time savings (huge), but also have AI do the work for checking for the 30 or 50 or 80 things that have been issues in the past – all stemming from specifications.

How convenient would that be?
 
If we could take the onus off of reporting bad players to state boards and instead focused on finding clean, appropriate, and easy ways to help make a project smoother for everyone – without adding any time burden – well that would be nothing short of awesome.
 
What I want to do from here is write a prompt and a step-by-step that I can share back with you all, that incorporates your list of grievances.

Essentially – everyone then has access to an easy way to gut-check specifications and get a custom-written Pre-Bid RFI out of it.

I need your input though to make it as useful for you as possible:
 
WHAT DO YOU NEED FROM ME JOE?
What I would love your input on is your answer to the following:

What have you seen in a specification that was clearly wrong which negatively impacted your project?

What have you found in a specification that makes bidding difficult, isn’t code compliant, or hurts the project?

I’m looking to create a list of checks that AI can do, for you, when it only has access to a project’s specification.

Comment below and let me know your thoughts – and in the next few weeks I’ll test and share a prompt and provide instructions back with you on how to use it. ​

Last week I worked error propagation for a pitot measurement to flow rate conversion.

Because it's a measurement, there is a natural level of precision that we can only estimate that depends on the precision level of each of our measuring points (our tools).

Yet, we (maybe just I) often overlooked the concept of measurement error. In this tool (below), I've incorporated the error propagation to suggest a range for the result instead of what we typically express as a near-certain test measurement.

So, now, you can convert a pitot pressure into a flow rate and immediately get the error tolerance based on the tools you've used and measurements you've taken. Hardly any additional work.

While it may sound trivial, knowing what amount of tolerance we are actually achieving in a test measurement could be the difference between a test pass or test failure - especially in regards to fire pump testing.

Check out the tool below, and let me know what you think! It has an IP and SI version built in (I'm finally catching on).

If you're a member of MeyerFire University this will be added to the iOS and Android app automatically. 

Thanks and have a great rest of your week!

​- Joe