Another dumb ?, How many specwriters prepare MEP sections?

As a former structural department head, I can sympathize with John: some structural engineers pay attention to architecture, but not all. On the other hand, I have known all too many architects who have no clue as to engineering requirements, structural or otherwise. Requests for 6 floor slabs (with no beams) spanning 30 plus spring to mind, plus the addition or relocation of slab openings just before the CDs are issued for bid. Lets not forget the relocation of columns without mentioning it to the engineer. Of course, these events occurred in the days before BIM: that could never happen now (ha).

Allowing no room for mechanical, electrical and plumbing in ceiling cavities is another memory that hold firmly, if not fondly.

It is indeed a two-way matter. And the need for interdisciplinary considerations to accommodate reality is essential to minimize and resolve conflicts.

A long, long list of shortcomings of project architects would be relatively easy to generate. My education at least was strong on interdisciplinary fundamentals. I recall without fondness structural engineering classes, including one term being taught by T.Y. Lin. I hated the algebra but at least learned the concepts well enough to be able to adequately converse with structural engineers, and also mechanical, electrical, civil and landscape consultants.

From what I keep hearing about Integrated Project Delivery, collaboration is at the heart of this latest, sure-fire cure to bumbling design and construction. Indeed, those successful projects I have experienced had a great deal of collaboration, collegialty and just plain playing well with others. Having experienced the good stuff, it’s difficult to tolerate those who don’t think beyond the narrow confines of their discipline.

Please pardon the snide comments if they don’t apply.

“Snide”? I didn’t notice. then again I have a sign in my office that states “Sarcasm is one more free service offered” so I may have a high tolerance.

In any case: I agree that collaboration is a key to success. There are others factors of course, but IMHO collaboration is paramount.

The sales pitch for IPD is indeed collaboration, but the key to that is someone has to run the collaboration, and too often the architects let that task go to the contractor. And that’s the problem.

A boss many years ago always insisted on writing the meeting minutes, because he thought that whoever controlled the meeting minutes controlled the information flow on the project. Instead of seeing the minutes as a tedious task, he saw them as a way of focusing the project in the direction he thought it should go, and he was very effective.

Architects have to stop being so scared of liability and take on some responsibilities for focusing and directing the information. I’ve worked on sucessful IPD projects, and the best of them are run by the architects because they actually do see multiple sides to a question. The projects that end up being run by the contractor is certainly bottom dollar driven, but also less collaborative. However, as we all know, when you teach a class (or run a meeting) you have to have more information and a greater understanding of the scope of all the questions in order to answer questions and deal with the other folks in the meetings, and not all architects want to do that much addtional work.

Architects have been giving away the store for a long time, or letting others take it from them. I love the argument for not sharing the model - “It might have a mistake” - which I assume means we have never issued drawings or specfications with mistakes. Contractors have again done a great job of taking on those things architects are afraid of, further reducing the value of the architect. About all that’s left is space planning and drawing pretty pictures, and hoping the engineers can make it work.

Anne:

YOU LET OUT THE BIG SECRET ABOUT MEETING MINUTES!

When I did Construction Contract Administration (CA), I always prepared and distributed the minutes. You are absolutely correct: s/he who controls the minutes, controls the project record.

I was successful in preparing meeting minutes, and received more than a few compliments, because of two big things: the minutes were accurate and they were fair (honest). Inaccurate and unfair minutes destroy the credibility of the one keeping notes. I believe many conflicts were headed off because it was clear from how the meeting minutes were recorded that the CA guy (me) would be truthful and fair. And I would hold firm on issues as necessary to assert the design team’s interests.

And a third thing was how they were organized. I listed each topic and assigned a number representing the meeting number when the issue was first discussed and then a sequential number was added for the order in which it came up at the meeting. And some keywords were included to readily identify the subject.

For example, the second item discussed at meeting no. 4, regarding gypsum board finish, would be “4-2 - Gypsum Board Finish.” The issue would retain this number forever. When resolved, it would be dropped from discussion. But it might come back later, such as at Contract Closeout, and the same number and keywords would be used. This way, it was easy to recall and read the thread of discussion.

This was not burdensome. I had to fly from the Bay Area to Los Angeles each week (a horrible culture shock) to attend the jobsite meeting. I already knew the status of at least 80 percent of the issues and actually prepared a draft of that week’s meeting minutes while on the plane, before the meeting started.

The meeting minutes were prepared as a summary of the discussion rather than a transcript, and included follow-up actions to be taken. The meetings ran efficiently and stayed on topic, without suppressing valid discussion. The parties were very collaborative and colleagial (yep, even without formal “partnering”!) and that made this process work out so well.

The project was at UCLA in the early 1980’s and this format was adopted at that time by the University for all of its projects. Lucky guess on my part regarding the format and procedures. I have no idea if it has continued.

(This was not a project without major problems. Winter rains washed out the end of one of building sites, resulting in about $120k (1982 dollars) of additional grading costs and a 63 day extension of the contract completion date. Yet, the de facto partnering plus a substantial change order to accelerate construction resulted not only in making up the time but delivering half of the project 4-months earlier than the original completion date and the other half 6-weeks early, yielding student housing rents for the University that more than made up for the additional costs.)

To make this appropriate to this discussion thread, the meetings involved all aspects of the project, including architectural, landscape architecture and civil, structural, plumbing, HVAC and electrical engineering disciplines. Being able to converse in the languages of the various designers and trades (while not claiming to be an expert in any of them except perhaps the architectural stuff) was a great benefit. I was blessed from early in my career to be involved in CA where I learned to play nice with (most) contractors.

Going back to the original topic. I work in a firm that only does Engineering specs & I don’t touch any decision-making on MEP or Structural. The design engineer or SME always does a review/edit/markup. If as an independent you have a good enough relationship with those folks then I say go for it. But that communication can be the most time-consuming aspect even from where I’m sitting – that really varies with each individual SME. Some require constant followup/nagging and others ask for drafts way before any deadlines and are diligent. The other consideration is the subject matter itself. On a recent project my Structural Engineer & I went back & forth several times before we had a Section on Crane Rail we were both happy with. Collaboration in new areas can suck up a lot of time.

For 2+ years, I was an in-house specifications writer for an E-A firm and prepared (“wrote”?) MEP specifications, as well as architectural. The challenge was to take technical content, editted by the responsible engineers, and format it coherently (i.e., according to SectionFormat). I contributed specifications writing principles and procedures, including contractual considerations (i.e, Division 01 ooordination and provisions consistent with the General Conditions of the Contract).

Just as with specifications for other design disciplines, this sometimes involved taking non-conforming manufacturer’s specifications and occasionally disjointed text from project engineers and creating suitable specifications. The initial efforts were very time-consuming while subsequent projects went much smoother. Education of the engineers … similar to teaching a CDT exam preparation course … helped greatly.

Since I had some knowledge and experience with MEP designs, communication was facilitated. At the same time, I had to learn what is important to these design disciplines. I learned, for example, how complex electrical demolition can be, compared to selective architectural demolition.

I think it is possible for architecturally-oriented specifications writers to work with engineering disciplines, landscape architects and specialty designers to jointly achieve clear, correct, concise and complete specifications … given enough time and energy in the bidding & contract documents production budget.

Karen, you have a unique position and can offer perspective which architecturally-orient specifiers such as I need to consider. Thank you for contributing.

@ John… oh there is PLENTY of coordination to contract terms etc. :wink: [plus, most of our clients have their own GCs which just makes things even more interesting.]
I think the biggest issue is building up trust between yourself and the SME – once you have that established, “writing” specs with engineers can be very rewarding & an opportunity to learn a great deal, as you suggest.
I love concrete even MORE now than I did in my archi-school/Kahn days. The material is not only honest, but complex.