In addition to this fine discussion forum, I also participate in a code-related forum. Well, just recently, someone started a thread on construction documents and whether or not should building officials or plans examiners have any say where things are placed. The discussion quickly focused on specifications.
I added my “2 cents’ worth,” but I thought you guys might be interested in it, too–if not to post, at least for grins and giggles.
Thanks for this link, Ron. Most of the projects I prepare specs for are in jurisdictions that don’t accept specs for review. The main reason that I hear is that they digitize the documents and it is too expensive to digitize the project manual. Based on my indirect interaction with the people that do the review, I would say that they know little or nothing about how construction docs are supposed to be organized and why. They are focused on how they can most easily get the information they need for their review. I have seen instances where a reviewer’s demands reduces the usefulness of the documents for pricing and construction as well as increase the possibility of errors and omissions.
What was explained to me was that they had to microfiche the files and that was expensive.
I am also of the belief that they are under time pressure to get the reviews done that they do not have the time to go looking through another manual for the information. It is better if they have a set of drawings that had certain information that they required clearly where they need it. What I have done in the past is to create a door hardware schedule on the drawings that gave them the basic information that they are looking for and then the spec followed up with the technical information. Is it duplication? Yes. Does it solve the issue of no spec submitted? Yes.
That’s a concept… Maybe do drawings the way they were done when they were respected 100+ years ago. Oh wait, then the contractor couldn’t hire college kids that don’t know anything about construction or sub-contractors that got things done right without trying to screw the client.
Ha, ha, ha! Ken, smaller? I am having the exact opposite problem. Larger plans to where they match line a simple box and then don’t put any information on the drawing. And I mean none. No dimensions, anything. I have seen details without a single note or dimension.
The project specifications are consistent with the definition of construction documents located in the IBC. A Project manual is consistent with standard practice.
The Building department has a legal obligation to retain copies of the construction documents.
Thus I do not see how the building department can use the argument regarding the cost of making copies. If this is a real burden they have the ability to adjust their fee structure but I suggest that when faced with having to do this they will find the additional costs to be nominal.
Could it be that the building department is acting illegally when they refuse to consider specifications as a part of the construction documents?
We once received a rather thick folded drawing from a manufacturer that resembled the packaging for a king size sheet set purchased at a department store.
When opened and unfolded, this turned out to be a full scale plan drawing for a nuclear medicine procedure room. The idea being that the contractor merely unfolded this and every slab penetration and expansion bolt location was there in full size.
This was back in the day where almost everything came and went by FAX. Using this plan submittal as inspiration, we wondered if you could draw a full size wall section, feed it into the fax and send it to the Contractor, All they would need to do would be to lay out the continually unspooling FAX at the project site.
Notations would be provided like: “turn right 90 degrees” or “3’-0” door here".
Using “I’ve never seen a workman carrying a spec book” as justification for putting specification information on the drawings is specious at best. In this context, at least, the worker really doesn’t matter. What’s important is that the specifications and drawings are binding on the contractor. After all, its not the individual worker who will be held responsible if the work fails to comply with code.
How the contractor chooses to assure that an individual worker performs the work, and whether he or she is carrying the drawings, the specs, or Gideons Bible, should be of no concern to the a/e, or the code official. The fact that the project manual is often used to prop open the jobsite trailer door doesnt minimize its importance, its relevance, or its contractual authority.
Likewise, its silly to dismiss specifications just because some a/es produce lousy and worthless written documents when they dont follow the principles of good practice. Putting it all on the drawings as you all are pointing out isnt the answer. Itll be interesting to hear how many code officials attend Rons seminars in Indy.
Perhaps one day Code officials will reject applications because the specs are wrong.
Maybe if more officials did their jobs right and required accurate specs that actually pertain to the project, Owners and Designers would start appreciating the importance of specs.
I had a project manager come to me to pass on a comment from the contractor. He said our drawings made it impossible to build the building without looking at the specifications.
I said “Thank you.” That might of been the biggest professional compliment I had received in a while.
I purposely have designed our keynotes to be as general as possible where appropriate. Need to know the thickness of the roof membrane? Don’t go looking at the drawings, it’s in the spec (unless of course there are two different thicknesses, then I’ll distinguish.)
Perhaps we should form an organization that would present these issues and prospective solutions on our behalf to the International Code Council (ICC).
It strikes me as odd that lawyers can read specs but can’t read drawings, and that plan examiners can read drawings but can’t read specs, but both depend on each other for full understanding of contract requirements.