If you specify that the manufacturer’s data must be on site - then what? I’ve seen thousands of “trunk libraries” estimators carry, dumping portions on the foreman at a particular jobsite. How are they to be used? Are they even in the worker’s native language?
Sheldon answered some of how to get around screwy wording on data sheets - out here (in warm sunny and not very wealthy CA) we generally use the catch-all “unless otherwise specified” and thdn try…as difficult as it is…to ensure we “fix” what the manufacturer has screwed up in their product data.
But, man, what a can 'o worms if an assembly/part/material is shipped in from China (or wherever) and there’s a slight variation - specifically, one that requires ANOTHER change in the manufacturer’s “recommendations”. Reject the material? Knock out a change order (whoops - who will take the hit if the price goes up - or down?).
I won’t drag that out.
Anne made a very important point - “how are we going to enforce this?”
She may implement procedures that cover that issue…but on most jobs, it’s anarchy.
When I was on the “interpretive” end of specification, I rarely saw ANY enforcement.
I DID see things like:
“comply with” specific results: “bla bla” per ASTM D90245098275"
“install at (insert a measurement of some kind here)”
"Apply (insert thickness, or “at manufacturer’s recommended spread rate) over properly prepared surface.”
Uhhhh - is a “properly prepared surface” the result of procedures on the manufacturer’s data sheet? The MPI manual? A clause in your master? Because if that “properly…” specifies a single method of preparation, the sub did it and it didn’t work - who eats the crow? The sub performed as specified.
Anne’s short note is the tactical nuke that deals with the other examples. There IS nobody enforcing except on high-end projects where the owner is willing to pay for inspections/field quality control (most are not aware it’s available; I’ve been in many meetings where owners - and many design professionals - seem surprised that what’s written down doesn’t automatically occur). Heck, they usually don’t even know field QA processes can be performed.
Playing the combined roles of contractor and sub now - I’ll have my guys/gals do whatever they normally do to make something look/perform (for 365 days at least…nah, strike that, I don’t want to even get into warranties) well enough to pass a punchlist walkthrough.
But am I going to hand them data sheets, specs and test equipment, have them interpret data in the field, take measurements and create reports?
Are you kidding?
It doesn’t make the slightest bit of difference what I (back in my own shoes) put in Part 3 unless I have verification requirements as well. Otherwise I might as well not waste the ink.
Anne again: “I typically organize my documents by stating what I want the end result to be, and then stating how I’m going to verify that end result.”
Yep - specify results, not methods (how many times has this been beaten into our skulls…yet I still see method specs, or some sort of unworkable combination) and notify bidders that you WILL be verifying those results.
That’s the game changer. Placement of it is less important.