The past seven days have been a very exciting time with the launch of CodeCalls.org. If you missed last week's article, here's more about it.
This week's post is a quick one with an ask. Feedback In short, CodeCalls.org is a free database that brings together jurisdictions and designers to help clarify the parts of code that are not always written in ordinances. Jurisdictions can get what they need for operations while designers get a little more clarity and help in meeting local guidelines. I've heard from many this past week about how they'd love to see this come together, and I greatly appreciate the input and encouragement. I've also heard a couple concerns that I'm optimistic we can incorporate as we learn and grow while working on this. Viability Our first goal is making sure the project is viable. Essentially we have to prove to ourselves that we will be able to provide enough valuable content that both designers and jurisdictions benefit. We're doing this by going all in on the State of Indiana. If we get things to work there, we feel comfortable that we can learn and expand into other areas. I have a quick ask this week - if you have worked in Indiana, or know of people who do, could you put us in touch? My email is [email protected], my co-founder Chris' email is [email protected], or if you got this post via email you can just reply directly to it. I'd love to have a quick conversation about how we can make the experience easy and that the benefits of helping will far outweigh the task of reaching out. I see that as the only way we can get this project rolling and I'd be thrilled to have that conversation. Thanks in advance, and have a great week! Today is a very big day for me. I am finally launching the start of an idea I've had and brainstormed and discussed and revisited for a number of years now. Finally. I could not be more excited about it. Ever since the COVID-19 pandemic began impacting the world around us I've been pressed to rethink my own operations and what I'm contributing to the world. Articles, design content, PE Prep, and trying to find ways to help the knowledgebase of the fire protection community is good, but I started the website around the idea of impacting the community in a real and tangible way. Today's new project is the start of what I hope could be a major positive impact for AHJs, designers, and installers. What is it? A Code Call Database. What is CodeCalls.org? CodeCalls.org is a free website that is bringing together local jurisdictions, fire protection designers, engineers, and installers to clarify and collaborate local code requirements. We're taking the areas of code in fire protection design that need local input, and helping jurisdictions get what they need to help first responders do their work. When we're done, we plan to have a searchable, filterable database where you can find local requirements based on a project's ZIP code, city or county name. Where to Start? Indiana! There tens of thousands of jurisdictions in the United States alone, how is all this data going to come together? First, we're starting with our test case. If you work in the State of Indiana or have contacts who do, pay close attention today. Our Goal is to gather jurisdictional requirements for 70% of Indiana's population by May 8th. That's in 30 days. Why Indiana?
Indiana has a healthy mixture of urban, suburban and rural jurisdictions, so it presents a great test case to validate the concept. If we get enough momentum for Indiana, we feel confident in pursuing the project for larger coverage. If we find that we can get enough momentum to clarify requirements for Indiana, then we feel that the project could be viable to expand to new areas beyond Indiana and beyond just the United States, too. Why a 70% Coverage Goal? In order for the database to work, the user experience has to be great. Both for jurisdictions and for designers & installers. We feel that if we can cover jurisdictions that account for at least 70% of the area's population, that we'll have enough data for a great user experience and a very helpful resource. Is it Free? Yes, the database will always be free for anyone to access. We're funding the development efforts as a joint project by MeyerFire.com and BuildingCode.Blog. Why Should I Help? If you're an engineer, designer or installer, why should you contribute? For one - this is a way to clarify local requirements that will help in more fair and consistent bidding. Second - we'll thank you by crediting your contribution with a link from the local listing directly to your company's website. If someone is looking for a local contractor or design outfit, they can search a ZIP code and immediately have contact information to you, the person who they know is already familiar with the local requirements. If you're a jurisdiction, why should you contribute? Simple - get your needs met. Are you tired of providing the same plan-review comments? Tired of answering the same basic questions in phone calls and emails? This platform is an easy way to clarify the gray areas of code and simply make your requirements more clear to those who are seeking them. I Have Some Information for Some Areas in Indiana. How Can I Help? You can contribute information for jurisdictions you're familiar with here. We'll thank you with a promotional link to your company's website and help get the information verified by the jurisdiction. See The New Site! Click here or the link below to check out the new project. Let us know what you think by commenting or emailing me at [email protected]. Would love to hear feedback on how we can make this helpful and accessible. First - last week I put together a draft PDF cheatsheet for fire alarm design in elevators. Lots of great response to that tool. One major flub on my part - I didn't actually link to it. Here's an actual working hyperlink (fingers crossed). K-Factor & Pressure Versus Area & Density One of the hand calculations I do frequently when laying out sprinkler systems is comparing the k-factor, minimum pressures, and resulting flow for the sprinkler. It comes up all the time with residential-style, extended coverage, special application, and storage sprinklers. Many hydraulic calculation programs do this comparison automatically. That being said, it is important to understand and compare the minimum flow from sprinklers for a hydraulic calculation. Reducing unnecessary flow from a sprinkler reduces the total calculated flow from a system, which has major impacts on pipe sizing for some branch lines, cross mains, feed mains, and even the underground service size. Driver #1: K-Factor and Minimum Pressure There are two drivers for the actual minimum flow that must come from a fire sprinkler. The first driver is the K-Factor and Minimum Pressure. This equation is Q = k√P
Wow a lot has changed in a week. We're holding on fine here, but I hope you and your family are safe and healthy wherever you are. Now back to more fun things like fire protection - After last week's debut of fire sprinkler requirements for elevators, I had a couple emailed requests for a fire alarm version. I love the idea and put some time into reviewing and organizing the requirements on the fire alarm side. This first iteration is a draft, and if you're well versed in this arena I'd love for you to take a look and let me know what you think. Feel free to email me directly at [email protected], or comment on it here. In the upcoming week I plan to incorporate ASME A17.1 and it's impact on the fire alarm side of accounting for elevators, hence the big [DRAFT] watermark on this PDF. Click on the image below to get a PDF copy of the Fire Alarm Elevator Cheatsheet: If you know anyone that could benefit from this content, please consider forwarding them a link. Hope you have a safe and healthy rest of your week! Thanks for reading. While it is a basic question, the code path is somewhat complex. When does an elevator require fire sprinkler protection? Today I'm exploring the code requirements for elevator sprinkler protection under the International Building Code (IBC) and NFPA 13. Here's a free PDF cheatsheet for navigating these requirements. To download, just hover over the image and click print or export. A special thanks to Philip Valdez who sent over the suggestion to put this one together. I hope you find it helpful! If you don't already get these free tools to your inbox, subscribe here. If you're having trouble viewing the image below, view it in your browser here. If you've found this helpful, consider sharing it with a friend or colleague. As always you can subscribe and get more free tools like this at www.meyerfire.com/subscribe.
Thanks & have a great rest of your week! Last spring I created a beta test tool for soffit obstructions to sprinklers. It was fairly basic using the dimensional rules for a soffit against a wall for a standard-spray pendent or upright sprinkler. Thanks to some feedback and more input on this tool, I'm happy to debut it with new features. I've added code references from the 2007 to 2019 editions of NFPA 13, the different style sprinklers, and an updated visual diagram. This tool is useful when there's a dropped soffit against a wall to determine whether the sprinkler will throw sufficiently underneath the soffit. In the coming weeks I'll break out a code path for determining when each of these tools are used. For now, if you're familiar with the NFPA 13 Sections for Obstructions Against Walls then you'll recognize this tool's quick usefulness. This tool stems from the Figures (b) and (c) for Obstructions Against Walls found in NFPA 13 Section 8.6.5.1.2 for Standard Spray Sprinklers, 8.8.5.1.2 and 8.9.5.1.4 for Extended Coverage Sidewall and Pendent/Uprights, and Sections 8.10.6.1.2 and 8.10.7.1.4 for Residential Sidewalls and Pendent/Uprights. Interested in getting access to every tool? Get the Toolkit here. Know someone that might be interested in this tool? Send them a link! It's greatly appreciated. Have a great week! Things around here are always busy. The past few weeks have been no exception. With feedback from some Apple users, field-users, and those without Microsoft Excel - I've heard your pleas! We now have every single tool from The MeyerFire Toolkit now available online to subscribers! You can see the complete list of tools at www.MeyerFire.com - just hover over the "Tools" list. Now, you don't need Excel or a Microsoft operating system - access the quick tools you need from anywhere, anytime. Not a Toolkit subscriber? Join on here. Licenses are now multi-user so you can share these tools with your whole team. SFPE Atlanta March 10th & 11th If you're attending SFPE Atlanta's regional conference on March 10th & 11th - let me know! I'll be there for John Frank's daylong session on updates with the Fire Protection PE Exam. He's the longtime leader of SFPE's Online PE Review Course and we'll be doing some collaboration in preparation for the computer-based changes to the PE Exam in 2020. NFSA Annual Conference April 29th - May 1st If you'll be in Phoenix for NFSA's National Conference - check us out! I'll be teaming with the voice of the fire sprinkler industry - Fire Sprinkler Podcast's Chris Logan to speak on New Media in Fire Protection. In Phoenix we'll be dissecting what we've learned while starting up different media in the industry, what projects we're working on now, and what ways we all can capitalize on new opportunities in the media space. That presentation is set for Wednesday April 29th. Making the Jump - The New Consulting Practice For all those who have reached out on LinkedIn about my (relatively) recent jump into starting my own design practice - thank you!! Things have been very busy with a healthy amount of fire sprinkler shop drawing design & consulting work. If you have interest in following the work I'm doing as part of that endeavour, follow my updates here: https://www.linkedin.com/company/meyerfire/. There's a fresh video on a recent all-BIM sprinkler design. If we're not yet connected on LinkedIn, consider doing so. It's GREAT to hear from and chat with other passionate people about the fire protection industry and it's something I really enjoy.
As always, thanks & have a great rest of your week! While being located geographically in the middle of the United States, it may not seem like seismic bracing would be a major concern. After all, we don’t have the frequency of intense earthquake movement that covers news headlines like the west coast experiences. Despite the (fortunately) absent frequency, the New Madrid fault line runs near Memphis, Tennessee up to the bootheel of Missouri. [Note: Yes, we Missouri-folk actually describe a portion of the state as a “bootheel”. When you say it aloud, though, you have to add a little twang.] Back to seismic – this fault line has the potential for very strong seismic activity just as much as portions of California and the Pacific Northwest. As a result, seismic bracing is common for us in southeastern Missouri, in St. Louis, and even into central Missouri and southwestern Illinois. As we move away from the fault line, at some point, seismic movement would be less severe – even to the extent that bracing isn’t necessary. Where is that point? How do we determine when seismic bracing is necessary for fire suppression systems? Today’s article is covering just that. It’s an exercise I practice commonly as I essentially live on the boundary of where seismic is and is not required by code. International Building Code References ASCE 7 Seismic bracing has roots in NFPA 13. As is the case between a “code” and a “standard”, however, NFPA 13 as a standard only tells us how to design and install the system. Code tells us when and where systems and components are required. The International Building Code Section 1613 for Earthquake Loads requires that “every structure… including nonstructural components that are permanently attached to structures and their supports… shall be designed and constructed to resist the effects of earthquake motions in accordance with ASCE 7”. [2015 Edition 1613.1] There are a few exceptions, most notably detached one- and two-family dwellings in some areas. ASCE 7 Requirements Based on Seismic Design Category ASCE 7, Chapter 13 (2010 Edition), for Seismic Design Requirements for Nonstructural Components, states: ASCE 7 Chapter 13 addresses Seismic Design Requirements for Non-Structural Components. Its scope covers the minimum design criteria for nonstructural components (like fire suppression systems) that are attached to the structure. ASCE 7 Chapter 13 suggests that seismic bracing is required for all structures, unless they meet an exemption. Section 13.1.4 specifically lists exemptions from seismic design requirements. These Exemptions include:
Additionally, ASCE 7 Section 11.7 states that Seismic Design Category A need only comply with Section 1.4 (not Chapter 13). So What is a Seismic Design Category? A Seismic Design Category is a “classification assigned to a structure based on its Risk Category and the severity of the design earthquake ground motion at the site.” (ASCE 7 Chapter 11 Definitions) In short, it’s a classification on the entire structure, ranging from A (least risk) to F (greatest severity). Seismic Design Category A structures encompass buildings of ordinary occupancy located on sites with stiff soils and have little risk of experiencing earthquakes. Seismic Design Category F, on the contrary, are required to remain functional following a strong earthquake, such as hospitals and emergency communication centers, and are located very close to major active faults. What Impacts Seismic Design Category? Several contributing factors are combined to give the seismic design category. They principally include:
Structures that are of high importance following an earthquake, such as a hospital, are of greater importance and carry a higher risk category. Soil conditions greatly impact the ability of the building to response to motion. Stiff soil or rock conditions generally allow the building to better respond to an earthquake. Loose soil, or soft clay don’t give buildings the ability to move with the ground, and therefore create worse seismic reaction forces within the building. Lastly, and probably the most obvious, the building’s proximity to a major fault line. The closer to a fault line, the greater the seismic forces from an earthquake event for the same earthquake. How to Determine Seismic Design Category? The International Building Code Section 1613 allows the Seismic Design Category to be determined either by IBC 1613 or ASCE 7. The International Building Code Section 1613 details the step-by-step process to determine the Seismic Design Category. This involves using data from site soil testing, the Risk Category, and earthquake severity parameters from provided maps. ASCE 7 has similar provisions in Chapter 11, detailing similar inputs of Risk Category, Mapped Response Parameters, and site conditions. In practice, however, there are third-party tools that help make this process much easier. Here are a few available, for free online:
With the Risk Category, Address, and Site Information, a Seismic Design Category can be quickly determined for a building. These reports also give important design parameters that will be used for Seismic Calculations for the design of the system. What if I Don’t Know The Site Class? With new construction, structural foundation design requires geotechnical testing and reports which give these values. The structural engineer will assess the report, and typically place the building’s Seismic Design Category in their front-sheet notes or in structural specifications. This isn’t the case with interior remodels or work within existing buildings. No soil testing is done and sometimes no structural work is done. When this is the case, the International Building Code requires a Site Class D to be used (IBC 1613.3.2). This could be made more conservative by the building official if geotechnical data determines that Site Class E or F soils are present at the site. So Does My Building Require Seismic Design? Back to the original question – once we know the Seismic Design Category, it’s easy to determine where fire suppression systems require seismic design. If the Seismic Design Category is A or B, then Seismic Design Criteria does not apply. If the Seismic Deign Category is C, D, E, or F – then Seismic Design Criteria applies. Under this later scenario, all the requirements of NFPA 13 for Seismic Design now become an enforceable requirement for the system design. Here’s a summary of the code path: Summary
Seismic Design Criteria for Fire Suppression Systems depends upon the Seismic Design Category for the Building. This Seismic Design Category incorporates the importance of the building, it’s proximity to seismic fault lines, and soil conditions at the site. While the determination path through codes & standards might not be as clear as other system requirements, seismic design is nonetheless a crucial component for the performance of a fire suppression system and an important consideration in the design of the system. Like this article? Consider subscribing here. Already subscribed? Consider sharing with a colleague who might benefit from this. We love to poke fun at millennials. It’s like the holy grail of tradition. “Kids coming out of school these days – you know? It’s ridiculous. They want twice the pay and half the work of when I came out of school. They don’t want to learn. They’re lazy. There’s not enough talent. There’s not enough interest. They don’t work hard.” Ever heard that before? How about this one - “Young people think they know everything, and are always quite sure about it.” Yeah – that last quote wasn’t exactly about millennials – Aristotle wrote it in the 4th Century BC. Every young generation is clearly, obviously, unexplainably worse than the one before it. Right? I mean criticizing the next generation has been going on for all human existence. I’m sure cavemen used to scorn at how the young have no eagerness to strike rocks anymore… But Millennials. Millennials are so… entitled. Yikes. Yeah – I wrote it. Entitled. The worst label of all. That E word. So Entitled. Millennials are so entitled that they don’t even own their own issues; those are of course caused by Boomer parenting. [see the half a million search results for “millennial poor parenting” on Google]. I mean clearly millennials are like the worst young generation we’ve ever seen? Right? Back Off Another Joe/Millennial Soapbox OK. So maybe the problem isn’t that bad. Maybe I exaggerate a little. Maybe I write too much in the third person considering my age technically qualifies me as a millennial. And yes, maybe I do also blame my parents for all my nonsensical fears (thunderstorms and sinkholes, come on Mom!). I was probably accused of being entitled a couple years into my post-college career. I felt good about the work I was doing, felt like I was understanding the curve, and I am sure it was showing in my attitude. A couple big project issues plus a bad annual review and I was quickly sized back to reality. But entitlement doesn’t go away easily. It was around that time that some coworkers went to a career fair at an area state college. One of the college students (a junior) inquired about the company. He got the normal pitch on working culture, opportunity, training and the whole bit. He then asked about management positions. After laughing it off my coworker realized the student was serious. He was looking for a management position as a quasi-21-year-old with zero real world experience! After returning to work and sharing the disbelief, it’s easy to see entitlement in others when at that same time I probably couldn’t see it in myself. I did get over it though. It wasn’t through shame or being a “company guy” or bad annual reviews. It was by starting my own side-hustle. Takeaways from the Art Shop I had always enjoyed creating sketches. During college I had a few architectural studio courses where we learned architectural sketching traditions. I enjoyed drawing and took some of those lessons to open a small art shop online. That experience brought so many positive perspectives into my life. It started with only one sale in the first two months of opening. It was a wonderful feeling. Then one good review led to another sale in month three. In month four I had two sales. Month five I doubled again. With each touchpoint I worked on improving the customer experience. I learned quickly to be responsive to customers. I learned how to deal with unsatisfied customers – which meant putting frustrations aside and owning-up to every misstep. I learned how taxation is theft (ok not really – but it is a major downer). Probably one of the most important things I learned from the basic art shop is that I had to take ownership of the work result. It never mattered how hard I tried to draw. If I created something that offered no value to others, it wouldn’t sell and had no value. That’s the real-world economy. People pay for value. How was I to bring value to a customer? How could I improve the value I offered? How could my presentation and correspondence be improved to help convey value? I thought about all of those things, constantly. That also began slowly translating to the workplace. Just because I put in effort – if the end result was incomplete, sloppy or just wrong – then I was not producing value. The essence of entitlement is believing that showing up is enough. It’s not. The value we provide for the world is our all-in engagement with doing great work. Employee vs. Ownership Perspective Starting that art side-hustle slowly and fundamentally changed my perspective about business and serving people. As I see it – there exists an Employee and an Ownership mentality. An Employee mentality asks – “why doesn’t our company pay for X?”, “they underpay everyone here”, “they never pay for good software”, and on and on. The Ownership perspective is looking holistically at the business. “How can we better serve our clients?” “How can we improve work culture?” “How can we improve productivity?” An Ownership mentality links personal responsibility to their work and representing a brand. I didn’t have to have a stake in a company to begin to develop that perspective. Businesses exist to make money. If businesses didn’t make money for a long period of time, then they fold and cease to exist. That’s reality, and that’s not a bad thing either. But just adopting an Ownership perspective brings about a world of possibilities. Company limitations don't become obstructions - they just become a problem that needs a creative solution. That art business grew, and grew and grew. Just three years in I sold over 600 pieces in a year. Wild. Especially for an ameateur artist who's dayjob is being and engineer. That shop still exists at www.etsy.com/shop/artbyjosephdalton. There’s not much time into it anymore now that the fire protection content is top priority – but I’m so thankful I started that shop because the lessons it taught has been invaluable. Want to change your perspective? Start that side hustle you’ve always wanted. It just might unlock a fresh way of looking at the world. Enjoy this article? Here are other career-related articles: Being Deliberate About Your Future Does Your Job Title Matter? Knowledge is Not Just in Education Fahrenheit 451 & The Thirst for Knowledge Heartache of Failure in Life Safety Design Enjoy this? Consider sharing with a friend.
Last week we explored when duct-detectors are required under the International Mechanical Code (IMC). While the IMC is the most commonly-applied standard in the United States, it's not the only standard that dictates terms for duct detectors. Many international projects under NFPA 5000 or government facilities under Unified Facilities Criteria (UFC) pull in smoke detection requirements from NFPA 90A. This week's post covers a cheatsheet for duct-detection requirements under NFPA 90A. Selfishly I've been wanting a quick go-to when covering fire alarm design, and now I'll have a copy for the two most common standards. Around here we laminate cardstock color prints for these cheatsheets. If you'd be interested in purchasing a set of cheatsheets, let me know by commenting here. If there's enough interest I'll set up something in our store.
Thanks & have a great week! |
ALL-ACCESSSUBSCRIBEGet Free Articles via Email:
+ Get calculators, tools, resources and articles
+ Get our PDF Flowchart for Canopy & Overhang Requirements instantly + No spam
+ Unsubscribe anytime AUTHORJoe Meyer, PE, is a Fire Protection Engineer out of St. Louis, Missouri who writes & develops resources for Fire Protection Professionals. See bio here: About FILTERS
All
ARCHIVES
July 2024
|