The NAAB is the governing body for colleges and universities and developed requried curricula for architectural programs. The link below will take you to the current draft. Note that there is ABSOLUTELY ZERO mention of specifications in section A.4, which seems to me a complete and egregious oversight. If you feel so compelled, it would be good for all the spec writers to send in comments about this and ask that “specifications” be added in A.4.
I have sent mine
Me, too!
I don’t think that the absence of the word specifications is so much the point as the asbsence of contract documents of which specifications would be an important part. What about the procurement process? What about the administration of construction contracts? None of these are included.
This just documents what has always been true of schools of architecture (in contrast to community colleges and technical schools) - they do not include the creation of contract documents and their administration as part of the curriculum. Though not stated in this document, I believe learning that part of the profession is left to be accomplished during internship in the office.
Pretty ironic that the great majority of the people in an architect’s office spend the majority of their time with tasks that are not included in the curriculum of schools of architecture.
I took an opportunity to read the criteria for the Student Performance Criteria, and it doesnt say Construction Documents per se. However, The instruction of putting together those construction documents (including specs) can be construed in item B6.
“Comprehensive Design: Ability to understand, and to produce a comprehensive architectural project that integrates the following SPC: A2; A3; A4; A5; A8; B1; B2; B3; B4; B5; B7; B8; and B9.”
A4 deals with Technical Documentation, and for a complete building design for an architectural project, the graphics (drawings) and the text (specs) must work together.
It would be better if it was spelled out. (Requiring the info we go through in the typical CDT Prep Course would be a start) Yes the verbiage is weak and this important exposure to the nuts and bolts of design can be overlooked. But a comprehensive program using this criteria will include it, if only in an introductory form.
I am a proponent of a graduate being able to go to work productively right out of school; but then I’m a product of the technical schools not a design school. There has to be a middle road to provide the education to make an emerging professional (graduate) productive in producing documents that can be built, yet allow for the freedom for creativity in design.
Trying to construe the criteria to get to say what you would like doesn’t really get you anywhere. I don’t think schools are going to look at this criteria and try to figure how they can get the preparation of construction documents out of it.
These criteria, which I had never seen before, just illustrates the major obstacles involved in getting subjects such as construction documents, procurement process, administering construction contracts to be covered in the curriculums of schools of architecture.
I would be interested in hearing from those who have made or know of those who have made inroads into the schools of architecture (in contrast to community colleges and technical schools) in terms of any of these subjects.
Ron: What has been your experience at Arizona State? Though quite a few years ago, I taught specifications at the University of Colorado - that consisted of one class session a year in the professional practice course - in other words, the students learned that there was such a thing.
It is interesting to look at the proposed changes in comparison to the current 2004 edition.
Proposed 2009 Edition: A.4. Technical Documentation: Ability to make technically clear drawings and models illustrating the assembly of materials, systems, and components appropriate for a building design.
Current 2004 Edition: Technical Documentation: Ability to make technically precise drawings and write outline specifications for a proposed design.
The background of this particular critera is not contract documents but rather to describe the proposed design in some detail - what we would probably call Design Development drawings and outline specifications. Based on the lack of the use of the words contract documents or contract drawings and current edition of this criteria, I would submit that A.4 Technical Documentation is not intended to deal with contract documents at all, but rather design development documentation.
Interesting to note that at least outline specifications are mentioned in the current edition but deleted in the proposed edition.
This is the comment that I sent in to NAAB:
I do not find anything in the conditions for accreditation about the architects roles and responsibilities in the preparation of contract documents, the administration of the procurement process, or the administration of the construction contract. I believe that these activities represent approximately 70 percent of typical full service architectural service agreements. The majority of the professional staff in an architects office spend a majority of their time at these tasks. Not all of these people are graduates of schools of architecture but a great many of them are. Those responsible for leading and managing these tasks are usually graduates of schools of architecture.
I would assume that the reason that these responsibilities are not included in the conditions for accreditation is that graduates are supposed to be taught these responsibilities during their internship after graduating. I do not know how far back this traditional division of architectural education goes, but I would assume that it is long before our current sophisticated contractual relationships under multiple project delivery systems. I would question the validity of that division in todays world.
Learning the principles of the procurement process, the preparation of contract documents (drawings and specifications), and the administration of construction contracts as an intern in an office is a hit and miss operation. You may be lucky enough to be in an office where people know and understand the principles and have a good program to teach them. In many others you are just taught to do it the way that office does it without any education in the basic principles. The office may have good, mediocre, or bad practices in these areas. I have had considerable experience teaching these subjects within offices (from medium-sized regional offices to large multi-office international firms). A very common reaction from the students is: This is great, this is the first time someone has taught me the why of what we do. Before I have only been told to do it this way.
It would seem reasonable that the curriculum of schools of architecture should have at least some material that would include at least an introduction to the basic principles of these roles and responsibilities. I am not proposing an extensive detailed program of how to do it as might be found in a community college or technical school, but rather one that just covers the basic principles. I am talking about things like:
o who the parties are and what their responsibilities are under the various project delivery methods
o what are the basic documents used (general conditions, contract forms, etc.)
o what are the elements of contract documents and what type of information goes where
o what formats are used
o what are procurement requirements
o who has what responsibilities during the construction stage of a project
o basics of how changes are made, submittal process, field observations, project closeout
o etc.
It would seem like these basics could be accomplished in a one-year course. This would have the advantage of covering everyone with an architectural education.
If this type of subject matter cannot be included in the curriculum, I believe that requiring getting some structured education in these areas should be a requirement of internship. This would not necessarily cover architectural graduates who do not seek registration as an architect. I realize that this comment should really be addressed to NCARB rather than NAAB. Such structured education is available in the CSI education programs; in particular the basic Construction Documents Technology (CDT) program. This type of education can be provided in-house by larger firms and is available on a continuing basis by CSI and CSI chapters so that it is available to everyone. This would ensure that interns do receive some proper education on the basic principles of these subjects.
Thank you for your consideration of my comments.
As an instructor at a major university (I teach a specifications course) I can report that this criteria is very carefully scrutinized and implemented by the university. My course is offered because of the word “specifications” in the current criteria. Eliminating the word “specifications” will likely result in the class not being offered at all, which would be a shame. Every student that has taken my class leaves with light bulb over head in full blaze. I encourage all on the list to lobby fervently for the inclusion of the word “specifications” within the criteria. We need to let these folks know how important this subject is, and the value in teaching it to budding architects, CMs, and engineers.
Guest-- pleae convey your thoughts and experience to the NAAB. It is vital that they see and come to understand exactly what you said. Thanks
See “CSI Comments on NAABs Decision” on the CSI Blog for the Institute’s response to NAAB.
Comments that I sent to NAAB about a month ago were also sent to CSI and posted on a Blog entry there. CSI’s posting is more focused on specifications and construction documents, my contribution touches on broader issues.
As noted in that posting, I was able to “bootleg” a course into the curriculum as an elective by crosslisting it both as an upperdivision course open to architecture majors and a continuing education course open to others (primarily those who were signed up for the CDT exam). There were incredible benefits to having such a diverse class. The were times when the students just could not believe something I was trying to tell them, but my observations would then be backed by at least two others.
To me, this is a very positive situation and one I hope NAAB reacts too in a correct manner! If they do, then I think there is a need for the initiation of a suitable and continuig effort for us to provide the best input, insight and actual “teaching” effort into the programs [keep the pressure “on”]-- not all are endowed with the likes of Mr. Jordan as creative instructors.
Stopping wrong action is one thing; providing proper follow-up shows true interst and dedication and a willingnness to make better!!
Great News!!!
If you’ve received your CSI Weekly you already know that NAAB has decided to retain “specifications” in its accreditation criteria-- in direct reaction to the response received from CSI National and many,many members.
This is a victory even though some may call it “small”.
Part of this is the fact that spec writers when acting in unison and common cause can bring change or challenge wrong-headedness.
We need to do this-- like this-- more often.
Thanks to all who responded. You did a very good deed for spec writers yet to come who may come by some academic effort [ah, yet another area of concern that we need to address!]
It has been over two years since we discussed this subject and I want to bring forth my experience with the NAAB team that just completed its visit to Taliesin, The Frank Lloyd Wright School of Architecture.
Only the masters program is accredited, so that was the only program reviewed by the team. During the team’s out-brief (unfortunately, I was teaching a CDT seminar and could not attend), they identified that Student Performance Criteria A.4, Technical Documentation, was not met. Since I teach the CDT at Taliesin, I was a little miffed, so I spoke with the Dean about it.
To my surprise, it was not that what I taught was insufficient, but that specifications and building assemblies were not integrated in the design studio enough!
Thus, NAAB has gone from deleting specifications to requiring its integration in the design studio–what a change!
As a result, I’m working with the professor who oversees the comprehensive design studio to have students prepare outline specifications for the project and thoroughly investigate wall and roof assemblies.
It’s time to get your comments in again!
The NAAB Conditions for Accreditation is up for public comment again. No big changes with regard to specifications requirements (aside from the proposal that “write” be changed to “prepare”) but I would like to encourage all on this forum to send comments in to strengthen the language - something along the lines of “understand the relationship between General Conditions, General Requirements, and Contract Documents.” and maybe a requirement beyond “outline” specifications - how about just simply “specifications?”
Please get your comments in before the June 24 deadline!
On a related but different topic, the NCARB recently posted information on the upcoming transition to version 5 of the architectural registration exam (ARE 5.0). This new version will first be offered in 2016.
It will consist of 6 divisions, one of which is Project Development & Documentation. In this division there is a separate section called “project manual and specifications”, which includes 3 objectives:
Identify and prioritize components required to write, maintain, and refine project manual.
Identify and prioritize components required to write, maintain and refine project specifications.
Coordinate specifications with construction documentation.
Other than the third objective, where “construction documentation” should be “drawings”, it is good that NCARB at least recognizes the existence of specifications and that testing for a familiarity with them is necessary in order to become licensed as an architect.
Dave, I agree that it is good that NCARB is recognizing specifications. However; it is somewhat disheartening to see that they don’t understand that the Project Specifications are integral to the Project Manual, as indicated in the first two items.
Margaret, I don’t see that there is a conflict between the first two objectives. As we all know, the project manual consists of more than just specifications. Now whether they really understand that subtlety is another issue, as you note. At least they didn’t call it a “book spec” which is more than I can say for some licensed professionals.
I note that NCARB doesn’t actually expect an architect to actually WRITE specifications or Project Manuals, just to “Identify and prioritize components required” to do so.
What the ??
I do like that architects are required to coordinate specifications with “construction documentation” - which I take to mean “drawings.”