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:
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. YOUR INPUT NEEDED Here are the key areas I'd love to hear from you about as we take the next step in building the specification:
THE 'SPEC GENERATOR' IDEA One of the ideas we threw out initially along with an open-specification was a new specification generator. The basic concept is that you'd play a game of "20 Questions" and in less than a minute you'd have a fully-edited specification. Most contractors I speak don't believe that specification editing actually takes any time at all - mostly because they're used to reading copy/paste boilerplate specification. But consultants know that a well-edited, accurate specification can take hours on each project between selection, making the edits, QC, formatting, and updates. Depending on how many people are involved in the process and how complex the job is, this sometimes takes 2-4 hours just in specification editing. The concept we're working on in parallel with this is a basic specification generator that does the editing for you, and provides meaningful tips on editing along the way. My intent is to pop this right into MeyerFire University with the other tools there about as soon as we're done with the open-spec. Here's a short video on the concept: 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
Chris Miller
5/15/2024 01:23:30 pm
1. Firestopping should refer to division 7. Ever project does it differently, but all the requirements should be in one place. I believe firestopping should be installed by each trade as part of their full and complete work.
James Art, FPE
5/15/2024 02:31:08 pm
Chris,
Casey Milhorn
5/15/2024 04:15:50 pm
If you are creating an open source, free to use spec, I would consider having the spec items in BLACK and questions in BLUE ITALICS as you will have a lot of variables based on geography, local licensing, local applicable code, local amendments to codes/standards, etc.... OR the spec generator idea, but I would definitely charge for that feature. That sounds really awesome. Comments are closed.
|
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
September 2024
|