Changes in MasterSpec

I opened the first quarter 2013 MasterSpec sections today and discovered that manufacturers and product names have been omitted from Part 2 - Products.

Editor notes say to double click on the link. This takes me to “Spec Agent”. What to do when I get there? Apparently I am supposed to call each manufacturer and figure out what product meets my needs.

As a spec writer, I do not have time to research every manufacturer for every product.

The value of a MasterSpec subscription has been the Evaluations which includes research and comparative charts for products so I can make an informed selection.

Thus, I was wondering if Discussion Forum participants had comments regarding this change.

Yes, I would like to hear some opinion on this. Has Masterspec been losing it’s quality? I would say that if they omit manufacturers and evaluations they have lost their advantage as a good research tool.

Actually I’ve always believed that one reason so many horrible specs are issued is because too many specifiers are not researching their products to find out if they even meet the project-specific requirements.

MasterSpec started out in an industry based on speculative office buildings. They provided a template from which to delete, or edit out, extraneous ‘stuff’ which was okay for spec editors. The other guys provided a template from which spec writers, real spec writers, could insert pertinant information and leave out the extraneous ‘stuff.’ The problem our industry has created is that the spec editors don’t know what ‘stuff’ is extraneous so they leave it in. So much for the 4Cs.

Is this a stupid step for MasterSpec? Probably. They will no longer be the Kleenex of the industry. Is it a positive step for our industry? I believe so, especially if people start using BIM as it is meant to be. If we can get specification software to the point where we can extract information from the BIM for inclusion in our specs, then as a team we can embed the right products into the BIM. If we only input the products that are correctly selected for the project-specific applications, our documents will have meaning and our spec writers should be able to generate specs that are, in fact, project specific.

What a concept.

This is the reason I’ve always preferred SpecText over MasterSpec. As a Specifier, not a spec tech, I’ve advocated doing the research for the project, not using “the stuff we used the last time” or “the typical stuff” I’m sometimes directed to use when asking my client (the designer) what he wants to use in each instance. Fortunately, the above direction is usually given over the phone so my client does not see the slow boil those phases often generate.
Perhaps there will come a time when young architects and other professionals who should know better will stop referring to MasterFormat as MasterSpec; and will actually know the difference.

This leans to a custom solution for every project, but it also presents a challenge for the corporate specifier in that the research time increased for creating and maintaining the corporate masters. Many companies do not maintain (yes, Ken, we do know of one) a spec department and only update their masters every once in a while (usually in the “years” time frame). Then the teams put together the specification. Not ideal and wrought with issues, but many firms operate that way. Ones with spec departments may maintain a corporate master and some actually base it on MasterSpec (I know of one). They look at it as a good starting point and then modify it to their corporate needs. By them totally eliminating that part, they have made that part fall upon the firm to allow more time to maintain and research further than they had before. This also holds true with the project. Having a good consistant starting point is crucial in maintaining quality. The problem is that with the custom for every project method means more time spent and in these times, that lower fees do not equate to allowing more time.

The change in MasterSpec is primarily one of form, not content. The manufacturers and products are still there, and the accompanying Evaluations documents have not changed.

As I understand the objective, the new function gives users dynamic information that can be maintained up to date (by ARCOM) since it is stored and accessed remotely rather than residing in the specification document.

It is relatively simple to select some or all of the listed products using the Paragraph Builder function, so this change in approach is unlikely to have a substantial effect on the selections made by specifiers.

There may be a question whether this feature is practical for the user. I personally find it cumbersome & time-consuming, and wish ARCOM had made its use optional. As with SpecAgent, many will likely find this approach terribly annoying.

And, if you choose to add a manufacturer not on the list, be very VERY careful. What you add cannot be deleted or changed. So don’t make a typo: “Arnstrong” will be forever just that. And yes, we contacted MasterSpec to ask if it could be deleted and they responded “no”.

It was bad enough with the hyperlinks that had to either be removed, and/or have the font color changed and the underlining removed. This is, IMHO, even more irritating.

Lynn: I assume you’re aware that if an error is made in Paragraph Builder, you can simply uncheck the box to deselect the entry, then create a new entry for selection. The incorrect version will remain, but need not be selected for use in a spec.

Sounds like they’re making it more complicated, rather than easier.
What ever happened to the “K.I.S.S.” principle along with, as Ken mentioned, the 4Cs.

I agree Richard. KISS. In fact that should be a lesson for everyone. I just saw a poll done on Durability+Design about specs:

In general, which choice best describes the quality of architectural specifications today?

Answers Votes
Well-written complements to design drawings 19%
Overlooked pieces that lack the technical information needed 56%
Satisfactory 22%
Other (comment) 4%

We should all learn from these responses. Architects and specifiers. Arcom, too. They need to get specifiers, architects and others into the loop with what they need to provide in product.

MasterSpec has their MARC (MasterSpec Architectural Advisory Committee) that meets quarterly. Sometimes MasterSpec management listens, sometimes it doesn’t. When I visited on occasion, I heard many committee members complain about having MPI shoved down our throats. Too bad. There were complaints about having SpecAgent shoved down our throats. Too bad.

I couldn’t use a MasterSpec Section without heavily editing it. I have never used their lists of manufacturers even when I was generating spec masters for a/e firms. Real specs don’t work that way.

If you don’t like it, vote with your feet. MasterSpec isn’t the only game in time. I’m not sure that it’s still the best game in town. If it suits you, find someone else that is more responsive. ARCOM will get the message as soon as their subscribers leave, not before. Sort of like what’s happening all over the architectural community. Remember when GM was pushing “What’s good for GM is good for America?”

Lead, follow, or get out of the way.

Ken: the Masterspec sections were developed to be “heavily edited” – their original intent was to be a deletion type spec, rather than Spec Text of the day, which was a fill-in-the-blank type spec. I’ve heard people complain that each type is “too hard”, but someone always complains about everything. And yes, real firms do work that way. I’ve used Masterspec as the basis of firm masters for three firms now, but revised to reflect the firm practice.
The spec world is migrating from Word-processing documents to data base documents and Masterspec is slowly picking their way into their market. The dynamic updating is certainly part of it, but that will allow users to eventually screen products based on multiple critiera. If you’ve looked at the latest versions of LEED, we’re going to have to list products based on a whole variety of things: EPD, HPD, Cradle to Cradle and god only knows what else. There isn’t any way to do that except in a non-linear fashion.
as for MPI – I think its the only way to specify pain – and was one of the ones of advocated for it. there is a lot of room for disagreement in this business – and Arcom tries to accommodate as many people as possible. I’m not switching to another system anytime soon…

MPI is a pain for sure!

Anne: Freudian slip? “I think its the only way to specify pain”? LOL! I agree with you that any spec system is designed to be heavily edited prior to using it. I also agree that real firms do work that way. I, however, feel that Masterspec is way behind with the database curve. They still base everything with their word-processing documents. As far as databasing specs, the only one I know of is BSD with Speclink. That, too needs a lot of modification to become a corporate master. It, too, has it’s pluses and minuses. The competition in the databasing systems is slim. Can anyone really tell me all the players in the database systems available?

BTW, I like MPI, too. It allows me to find the data and the options quickly.

I have been losing the appeal of Arcom with there slow pace of updates and the fact that the specs they provide have turned into large verbose sections. I am finding that this is much of the opinion of the users of the specs. While they are necessary, they have turned into the CYA document and the users know it. I have said that they have turned into the best door stop we can provide the contractor’s trailer. To many times we are dealing with nothing but substitutions and part of the issue is what we write as much as what the contractor bids. The poll above shocked me some, the amount is what surprised me. To find that only 19% found them acceptable is an issue, even with an adhoc survey.

Who is to blame? I really think all of us. All the spec systems and ourselves. Sheldon Wolf (and others) have given great presentations concerning this very topic. Spec systems need to reflect what the end user will need. As Anne also put it, there will be others that totally disagree with me…

I would agree with Margaret that “the stuff we used the last time” is often used as a crutch by designers and it is frustrating to deal with this mentality. However there area also a lot of times in my work where matching an institutional standard dictates that we use the stuff we used the last time.

This can lead to a different issue because there is a tendency (when deadlines are bearing down on you) to simply match the previous spec and not research to make sure the product still exists or to make sure the product number/code has not changed. I am not sure any one program is any better suited than another to help with this requirement. In the end, sometimes there is no substitution for doing your homework.

As for paragraph deletion type vs. paragraph selection specifications: I have used both over the years and I personally prefer the Speclink approach I use currently to the old masterspec I used years ago. Of course everyone is different and I am comparing something I use to today to something I used years ago so it is admittedly a biased observation. just my 2 cents.

I have no patience for people who think they can subscribe to a guide specification provider and not still have to research, think, and work hard to produce a decent project manual.

How would it make any architect feel if you said, Hey, we just purchased Time Saver Standards - youll never have to waste time detailing anything ever again!

It is really an insult, most often inadvertent, to think anyone can write good specs as long as they have the latest program to do it with.

With a certain spec-by-numbers system, I have to re-write and re-format everything to make it correct and readable. The few conveniences it offers do not make up for the poor writing. If a client tells me I have to use it, I just charge more and we are both happy. Concise? Yes it is concise, but so is the end product of a Pekingese.

As for MASTERSPEC, the writing is far better, sometimes over-done, but displaying greater research effort. The Evaluations alone are a knowledge resource that is worth the subscription price. As such it is like a good encyclopedia. You still have to be the author, but you have a lot more good information to work with. Although not by any means perfect, it reveals its creators greater understanding of what specifying is and what it requires.

I agree with the statement “I have no patience for people who think they can subscribe to a guide specification provider and not still have to research, think, and work hard to produce a decent project manual.”

In the case of a consultant, such as structural engineer, generic master specifications provide relatively little benefit. The consultant will typically have more knowledge of the products and related code requirements than the author of the master who must spread his effort over a greater number of sections.

The big issues for consultants is formatting their sections to look like the architect’s (remember each architect is different) and coordinating with project wide requirements such as LEED or submittals.

I gave up the “look like the architect’s” battle years ago. Some consultants couldn’t get it right, and even though I had a couple of macros that worked near-miracles on their sections, I had too many more important things to take care of than consistent format.

The content is what’s important, and as long as the fonts and margins are reasonable (most are) I take what I get. I’m more concerned about needless content (stuff that’s in the bidding requirements, conditions of the contract, and Division 01), and that battle continues.

I began using MasterSpec in 1978 and had the pleasure of serving on the MasterSpec Architectural Review Committee several years ago. The primary knock on it then was at
That it was too verbose. Compared to the product offered today, it was way too verbose. The current trend leans toward offering more “narrow scope” sections which will require less editing (see what has happened with toilet partitions). The Paragraph Builder is a significant step toward a database spec which should be better at keeping the list of manufacturers currents (think of the ICI to Akzo Nobel to PPG transitions occurring in less than 5 years).

Generating specs for a project is hard work no matter where you start. You have to edit by addition and deletion, verifying that what you keep is still current (not that it will still be current when that particular product is actually installed). For most products, the last spec can be used, but when an error creeps it, it can be a doozy. I was recently looking at some office masters for a firm that does mostly car dealerships. Their spec for carpet should ave been fo carpet tile, but it was a pretty detailed spec for aixminster carpet.

The efficient specifier is not doctrinaire about the source of the content, but seeks to understand the project’s requirements and edit the source material accordingly. Source material that is dynamic and rigorously current is critical to the process. The development and evolution of SpecAgent and Paragraph Builder are examples of was in which ARCOM is addressing this issue,

JP, my thoughts exactly on Arcom’s narrowscoping of sections, and even article’s within the sections over the past several years - should help many users avoid the old problems of too easily leaving manufacturer’s in the spec who do not make the very narrow group of products finally chosen after editing all the requirements. Plus it is a huge step toward BIM connectivity.

Anne, I agree that there will always be some users who will complain no matter what is being done. Yes Ken even MARC members at times, as in the case of the MPI example, but Arcom is doing what will best serve the majority of users. There will be some who don’t understand, some who do understand but choose to go another direction with that spec section - that is fine - and perhaps some who partly understand and misjudge.

I will also join with Anne and Alan in saying I’ve worked for several firms that use MS as their base documents and yes real firms do deal with sometimes long lists of manufacturers, and of course we tailor them down for the region and project needs! (which will get easier with Paragraph Builder). I don’t understand how users who have this complaint would not have the same exact complaint with any guide spec system that names manufacturers. You have to research if you write specs. You have to modify the guide spec text, it is a GUIDE spec. You have to use the tools as intended and not fight the tools, and then the real benefit will become more fully realized. If you over-rely on past projects, trouble is not far down the road. Where is this implication that using MasterSpec means relying on past projects though - those to me seem to be polar opposite ways to produce specs.

In doing this latest change that started this thread, Arcom has made available a powerful solution that allows products to be filtered by your design choices, and it sounds to me like they are at the same time fully addressing the old complaint that out of business manufacturers are not removed and names are not updated quickly enough, by implementing Paragraph Builder.

By the way there are TWO database spec systems available for interacting with Arcom MasterSpec content. http://www.specware.info/ (See the two on the right.) Both of them have come light years from the old way of managing customized office masters. BSD has I believe the longest history in databasing specs, but my experience there is limited to demo versions because the firms I was with were previously committed to other solutions; I can say that my peers who have used it (SpecLink) were enthusiastic.

Before I go further, let me mention that I’m just a spec writer for a large A/E firm and I have no dog in any fight here, i.e. no one is paying me to say any of this. I just might have some unique insight from working at a variety of firm sizes and business models for producing specs, and I’ve worked on guide specs and software in the past. I’m not trying to toot my own horn, just hoping to help clear up misunderstandings that abound on this thread.

As product innovation and marketplace changes continue to abound, Arcom is doing something about it. Paint is one good example, for which they are sometimes misjudged. I congratulate Arcom on their ongoing work to incorporate the wealth of non-proprietary reliable info that MPI brings, and the recent announcement in one trade journal I ran across that they will be integrating with MPI in Paragraph Builder. Our firm customizes the office master spec sections for painting to simplify adding specific products, if needed going beyond MPI, and including some recent code changes and best practices we’ve learned. Does that mean I should complain that Arcom is making more changes in this area for fear I can’t update the office master? No, I look forward to seeing their innovation and adapting as needed to take advantage of the new tools.

Without MPI we would be lost in a sea of ever-changing and non-equivalent information, with nothing to believe in except the firm handshake, sudden look in the eye and easy smile of a rep. To even begin to accomplish what MPI has, one would have to collect and peruse thousands of pages of product literature and compare test reports, but forget about the testing methods and info being consistent. Days or weeks of research would be needed to produce the same quality of specifications without MPI, or you would have to abandon ensuring “apples to apples” and rely primarily on what reps tell you, and later respond to the school of hard knocks and update your master over many years - but then the products change again and you must start over!

MPI is EASY to use for specifications if you subscribe at www.specifypaint.com for research information. If you haven’t, you just don’t have any idea what all you are missing. You can research by coating SYSTEM, not just by approved products as found at their basic site www.paintinfo.com. Once you have access to the specifier’s full information, vast info is at your fingertips if you follow the systems evaluations links (you can tell I’m a Classic Site user), or you can go without the evaluations and just look at the systems only if you are already familiar. And if you use the new site with Decision Tree I really don’t understand how it could be any easier. There is even now an agreement where MPI will become integrated into the new Paragraph Builder and some manufacturers will offer Product MasterSpec like sections in the new system. If you don’t have a specifypaint subscription you are not totally in the dark because the editor notes and supporting documents in MasterSpec provide much of the info you need. Some people may be tripped up if they don’t understand that this is one of those sections you’d better edit as 3-2-1. It just makes sense to choose the substrates and the coating systems for only those substrates, then review the products, and then the administrative requirements. If you still have problems with paint specifications it might not be MPI’s fault, they can’t do everything - the specifier still has to know which paint manufacturers are reputable and present in their region, and sometimes choose between multiple options of similar products based on what the project requires.

For anyone who thinks of specs as a CYA document while they are producing them, that is all they will ever be, filled with junk you thought you might need, not useful for bidding and construction, making all the truly necessary text less and less defensible. Some firms have been too accepting of understaffing of technical people. That is more the problem than guide spec systems. If you don’t have people on staff who really know contracts and how a building goes together and doesn’t leak, you will have legal and constructability and liability problems. BS specs are just the beginning, no guide spec system will help, and just wait 'til you try BiM without understanding what the elements are that you are drawing based on incorrect and proprietary products and then using that 2 right specks!

Of course we hope for much better from most of those who frequent this discussion forum.

I’m sure I’ve covered too wide a range of issues and made everybody mad somewhere or other…