Drawings and specifications often have many references requiring coordination with the owner. While that makes sense for some things, for example, location of grommets or selection of paint color (as long as it doesn't include non-standard colors), it doesn't work for quantities. The reason, of course, is that during bidding, the bidders have no direct contact with the owner, and even if they did, I'm sure owners would not appreciate a barrage of calls from various contractors and subcontractors, all trying to obtain information that should have been in the documents. If I were the owner, I'd be on the phone, asking the architect why in blue blazes those questions had not been addressed in the bidding documents.
Directions to the contractor, requiring coordination of various items, appear to make more sense, except for the fact that the AIA conditions of the contract make the contractor responsible for coordination of the entire project,
15 March 2013
26 February 2013
Loose products and equipment should be NIC
While it may seem like a good idea to specify every last item necessary for a complete, ready-to-use building, specifying loose items - those that are merely set in place - in the construction contract incurs needless expense for the owner.
In most cases, the owner is better off buying loose items directly from suppliers, with installation provided either by the supplier or by the owner's employees. Going through a contractor adds labor cost and at least one markup for overhead and profit; additional markups will be added by each subcontractor involved.
In most cases, the owner is better off buying loose items directly from suppliers, with installation provided either by the supplier or by the owner's employees. Going through a contractor adds labor cost and at least one markup for overhead and profit; additional markups will be added by each subcontractor involved.
11 February 2013
National Engineers Week, CSI style
The Minneapolis –St. Paul Chapter, CSI, is participating in National Engineer’s Week by hosting a “Teach In” at Robbinsdale Middle School in Robbinsdale, Minnesota.
On February 20, CSI members will enter the 6th grade classroom of Robbinsdale Middle School teacher Todd Norholm to give interactive presentations on basic engineering principles and how they apply to construction. Students will receive instruction and build small structures using gumdrops and toothpicks. When completed, the students will have constructed their own geodesic spheres.
On February 20, CSI members will enter the 6th grade classroom of Robbinsdale Middle School teacher Todd Norholm to give interactive presentations on basic engineering principles and how they apply to construction. Students will receive instruction and build small structures using gumdrops and toothpicks. When completed, the students will have constructed their own geodesic spheres.
29 November 2012
Product information "security"
Among the specifier's most common frustrations is the requirement to login before getting product information. Just this morning, I tried to get information about metal panels from a well-known manufacturer's website, and was kicked out. Apparently, I had registered some time in the past, because when I went through the registration process, I was told that my e-mail address already was in use. That forced me to either set up a new account, and risk forgetting yet another password, or to go through the "forgot my password" routine. I chose the latter option, with the intent of using a simple, non-secure password I use for all such websites, something like "password".
I was surprised when an e-mail popped into my inbox almost instantly, as most websites have some delay, and some can take a day or more. Do you think all those requests get sent to some poor soul who has to validate them? The response from this manufacturer did offer bring bit of levity to an otherwise dreary morning of grinding out specs for two projects. The temporary password was - get this - x=H=)Xarq%+z+U. Good grief, that looks good enough to protect nuclear launch codes!
I was surprised when an e-mail popped into my inbox almost instantly, as most websites have some delay, and some can take a day or more. Do you think all those requests get sent to some poor soul who has to validate them? The response from this manufacturer did offer bring bit of levity to an otherwise dreary morning of grinding out specs for two projects. The temporary password was - get this - x=H=)Xarq%+z+U. Good grief, that looks good enough to protect nuclear launch codes!
01 October 2012
Comments to Clients; the project manual
What are specifications? Why are they important?
Most people have some understanding of what drawings are, and how they are used in construction. However, it takes more than drawings to build a building. Along with the drawings, on nearly every project, we issue a project manual. Many people are unaware of the project manual, and I suspect most who have seen one don't pay much attention to it, for a couple of reasons. First, the project manual for a typical project will have two volumes, each one being two to four inches thick - enough to scare off all but the most curious. Second, it is not light reading, with countless pages of what appears to be highly technical mumbo-jumbo, full of strange acronyms and unknown terms, written in a style clearly not meant for entertainment. Obviously, few would be interested in the project manual!
But without it, the building can't be built. The project manual and the drawings are complementary - that is, they work together. Each needs the other, each serves a specific purpose, and each is used to show specific information that is not shown in the other. In the construction contract, they are treated as a single document.
Most people have some understanding of what drawings are, and how they are used in construction. However, it takes more than drawings to build a building. Along with the drawings, on nearly every project, we issue a project manual. Many people are unaware of the project manual, and I suspect most who have seen one don't pay much attention to it, for a couple of reasons. First, the project manual for a typical project will have two volumes, each one being two to four inches thick - enough to scare off all but the most curious. Second, it is not light reading, with countless pages of what appears to be highly technical mumbo-jumbo, full of strange acronyms and unknown terms, written in a style clearly not meant for entertainment. Obviously, few would be interested in the project manual!
But without it, the building can't be built. The project manual and the drawings are complementary - that is, they work together. Each needs the other, each serves a specific purpose, and each is used to show specific information that is not shown in the other. In the construction contract, they are treated as a single document.
12 April 2012
Not all details are equal
I recently followed this link in the NRCA SmartBrief: "Modular construction could boost efficiency of construction projects." It led to an article titled "Construction officials pushing prefab revival", which touts the advantages of modular construction. The opening paragraph acknowledges the "technique [is] hundreds of years old" but modular design may be a foreign concept today.
Modular dimensioning has been with us for a long time, and is almost inescapable for some things; masonry units are modular, and partitions rely on modular dimensions for framing and sheathing. And, although they're not modular in the same sense, many products at least come in standard sizes. In each case, the consistent properties make these products easier to know and to use.
Modular dimensioning has been with us for a long time, and is almost inescapable for some things; masonry units are modular, and partitions rely on modular dimensions for framing and sheathing. And, although they're not modular in the same sense, many products at least come in standard sizes. In each case, the consistent properties make these products easier to know and to use.
06 April 2012
What happened to the bidding period?
In the good old days, not all that long ago, the architect's work was divided into a few neat phases: schematic design (SD), design development (DD), construction documents (CD), bidding or negotiation, and construction.
In theory, the requirements of each phase are completed before moving on to the next. In practice, it seems we have strayed from the true path.
When I started my present job, more than fifteen years ago, projects progressed through the phases in a fairly linear manner. We didn't issue many addenda, and the ones we did issue were short. Since then, schedules have shrunk, and the separation between phases has blurred. We now do full specs at DD, even though they have little value because many decisions have not been made, and some design issues remain unresolved until the CDs are issued - or beyond. Addenda are common, and lager; I occasionally see one that is half the size of one of the project manual volumes, accompanied by many drawing sheets.
In theory, the requirements of each phase are completed before moving on to the next. In practice, it seems we have strayed from the true path.
When I started my present job, more than fifteen years ago, projects progressed through the phases in a fairly linear manner. We didn't issue many addenda, and the ones we did issue were short. Since then, schedules have shrunk, and the separation between phases has blurred. We now do full specs at DD, even though they have little value because many decisions have not been made, and some design issues remain unresolved until the CDs are issued - or beyond. Addenda are common, and lager; I occasionally see one that is half the size of one of the project manual volumes, accompanied by many drawing sheets.
Subscribe to:
Posts (Atom)