Specification Station
It’s the station stop that no one wants to get off at. But as an engineer, you’re gonna have to deal with specifications eventually. So today, let’s take a quick five minutes to briefly go over specs.
SPEC 86 75 30.09
SPECIFICATION STATION
PART 1 GENERAL
1.1 PURPOSE
As a companion to the contract drawings, the specifications provide the textual information needed to build the project. You could have a s*** ton of notes on your drawings, but it usually more practical and more a** covering to put together a comprehensive spec book.
1.2 FORMAT
Different agencies may have their own standard specification formats. But generally, specs are formatted in the same way as this blog post. We usually see the MasterFormat system for spec numbering. This example uses 86 75 30.09, which is a song lyric formatted into a nonsense spec number. Specs are also usually broken into three parts: general, products, and execution.
1.3 PROGRAMS
There are different programs that allow you to manage your specifications. I’m only familiar with using SpecsIntact, but I’m aware there are other ones out there. These programs can allow you to manage your inputs, create submittal registers, and perform QC checks on your specifications.
PART 2 PRODUCTS
2.1 START FROM SCRATCH
Saying this may instigate an angry mob. It can be super tempting to use a spec from a previous project. The work was already done by someone else in the past, so why repeat it? Well, the issue is that not all projects are the same. Old project specs could be using outdated templates, superseded references, and site specific inputs. A blank spec template is intended to provide you with the framework to control the inputs. Start with the blank template and just use the old spec to help inform your inputs.
2.2 READ THE DANG THING
I know the spec book probably has zero stars on your goodreads. But you’ve gotta read it. And if you ignored my advice about starting from scratch, you better look over every inch of that thing. Might feel like an obvious tip, but I’ve looked at so many specs that have obviously not been read through. Like why are you talking about airfield pavement markings? Are you planning on landing a plane on this twelve space parking lot?
2.3 KEEP RECEIPTS
Programs like SpecsIntact aren’t the best for recording when or why changes were made. Make sure you’re keeping records of inputs from discipline lead and maintaining good version control.
2.4 STEP INTO THE CONTRACTOR’S SHOES
You need to think about how the spec book will read to the contractor. The time you think you’re saving by cutting corners on your specs now will most likely bite you in the a** during construction later with an onslaught of RFIs. You can help make it easier for the contractor by:
a) CROSS REFERENCING: Clearly reference the relevant specs in the drawings. Do things like adding the spec number and titles to your notes sheet or if you have multiple concrete specs, clearly indicate which structure uses which spec.
b) USING CONSISTENT LANGUAGE: If you call it a joist in the drawings, call it a joist in the specs. Coordinate the language so it’s perfectly clear what the spec is in reference to. You sure as f*** don’t want the contractor to get a tension connector that’s A36 when you designed it for A572 because the spec required interpretation.
c) CUTTING OUT EXTRANEOUS INFO: If there are irrelevant sections in your spec, you’re doing it wrong. Make sure the language that’s included in your spec is relevant to your project. Having a thick a** spec book that no normal human being could possibly read will not make your project more successful.
2.5 USE THE QUALITY CONTROL FUNCTIONS
SpecsIntact publishes quality control reports. Help yourself out and look at them. It’s much easier to address the quality control issues of unreferenced standards, unaddressed inputs, etc. as you go along. If you save that s*** to the end, you’re going to hate yourself later.
PART 3 EXECUTION
3.1 SET MINI GOALS AND REWARDS
I don’t think specs are anyone’s favorite task. Let’s be real, they f***ing suck. So to get through them, you’re going to want to set some mini goals and rewards. If you push through these two specs sections before lunch, you’re going to treat yourself to a nice post-lunch walk. Set your goals small and achievable to keep yourself feeling accomplished and motivated. And switch up your rewards. It could be your favorite cup of tea, a stretching break, your favorite candy bar from the vending machine, a hot gossip session with your coworker, 5 minutes of scrolling through instagram, or whatever floats your boat.
3.2 SET SCREEN COLORS
Looking at a white screen all day while you work out these specs can be tough on your eyeballs. If you’re going long haul with a big spec book, set your screen colors to minimize eye fatigue. A nice grey or black background will help you get through those specs a little easier.
3.3 SPLURGE ON THE PRINT OUT
I love the environment as much as the next guy, but sometimes printing out a spec is 100% worth it. If you’re managing the whole spec book on a huge project, it’s hard to imagine that you’re actually going to be able to stare at your screen for a hundred plus spec sections. So you print out two or three spec sections, find a comfy spot to curl up, and go through some of them on paper. It’s a simple way to make your job a little easier on yourself by decreasing your screen time and shaking up the monotony by allowing yourself to change up your environment. And then you use the paper as scrap and recycle it when you’re done.
--End of Section--