CSI Specifying Practice Group

user-pic
Vote 0 Votes

CSI's Specifying Practice Group will hold its inaugural meeting January 7, 2010 at 3:00 PM eastern time. To attend the meetings, just join the group. The group is intended for those that read and write specifications and everyone affected by specifications. The range of topics will include:

 

  • How technology influences content, production, and delivery
  • Disasters and responses to practical experience
  • Tools, techniques, and tips worth sharing
  • Just what drives product selection, exactly
  • Exponential marketplace advancements
  • Learning to forget what no longer applies

 

While thinking about specific topics to bring to the group I shared some ideas with CSI staff. To be sure the ideas were on target with the goals of the group. The two ideas were of immediate interest: MasterFormat™ 2004 and the impact it has made; and a Photo Log to learn from built examples of the good, the bad, and the ugly. I intended the Photo Log to involve contribution by group member, so it is not really appropriate for the inaugural meeting. Initially we will explore MasterFormat's impact.

 

Here are some of the other ideas that may appear in the months ahead. I would like to know what your thoughts about these may be and what other topics you would like to suggest.

 

Outline Specs - Useful or Not: How are outline specs developed and used and are there alternatives?

 

Managing Design and Spec Data: What data are needed and how is the information best collected and communicated?

 

Implementing SectionFormat™ 2008: What is the impact and must it be universal?

Seismic Requirements - Beyond the Building Frame: What does the code affect besides the building frame?

 

Out with the Old; In with the New: What standard, code, product, or method has changed significantly?

 

How to get Spec'd - A Peek Behind the Architect's Curtain: What mysterious methods are used to specify products?

 

It May be Green, But is It Durable: How do you balance the choices?

What Can You Expect of a Specifier: Is it more than a technical spec or project manual?

 

And the Goal Is...Satisfy the Owner: What does it take for repeat business for the entire team?

 

Where are the Manufacturers: What happens after visiting the website, filling out the form and leaving a message?

 

That is a year's worth of topics, all subject to change, pending your opinions. So let me know what you think.

 

I hope to meet you on-line to share our thoughts and experiences and learn from each other to better the industry. If you haven't already, just join the group, and then, join the meeting.

 

No TrackBacks

TrackBack URL: http://www.conspectusinc.com/cgi-sys/cgiwrap/conspec/managed-mt/mt-tb.cgi/5

4 Comments

| Leave a comment

David... thanks for creating this group... in the last few years I was beginning to wonder what happened to the "specifications" in CSI!! I like your list of topics. Unfortunately I will not be able to participate in the "meeting" on Thursday due to another meeting (with client... make money). In response to your first topic, I find outline specs helpful (if read by client) since outline specs are typically more "user-friendly" (sizewise) and help to start the dialogue necesssary to development of subsequent specifications. Looking forward to a productive and stimulating group. Steve Andros

Steve,

Thank you for the comments. I was thrilled to have this opportunity from CSI. I believe it may stimulate some good conversation about timely, relevant topics. I am glad to hear you like the initial proposed list. I am anxious to learn what the group will think to add at our first meeting.

I learned from CSI that over 150 have joined the practice group and about 50 signed up for the first meeting. The presentation will be recorded so you can watch for the posting on CSI's website.

Thanks again for creating this group. One of your suggested topics for this group was something like "Who is the spec for? and your answer was "The Owner". Project Specifiers would agree, but product specifiers too often have personal success as their objective, and Project Specifiers keep them at arms length. I wrote product and system specs for over 30 years, and found that long term trust relationships were easily developed if I maintained focus on The Owner. I once wrote a flat non-competitive spec for my competitors system, and instantly gained trust from the Project Specifier. My competitor was right for the job, and I could only foul things up if I tried to intercede.

There's a natural barrier between a Project Specifier and sales persons trying to specify products and/or systems. The barrier can best be lowered by specifying what's best for the owner.

Harris, thank you for the comments. I appreciate learning from different points of view. My hope is that the practice group will provide a forum to exchange ideas and points of view.

When we are asked to help with a product specification, one of our first questions is, "Who are your best competitors?" Then we suggest that the new product spec name the competition. This is where the resistance starts.

The manufacturer wants to maintain a proprietary stance, after all he is paying for the spec. We try to explain that if the spec is fair and sets a reasonable bar, then the manufacturer has an opportunity to name the own competition rather than relying on the whim of the design team. What could be better than controlling the competition?

Helping the design team by providing a spec that includes the manufacturer's knowledge about alternative equivalent products will be remembered. Service is what will stand out, always. Designers and specifiers will remember who provides the best help and will be faithful to those that do. Directing the specifier to a competitors product because it is right for the job will ensure the manufacturer will be the first one called the next time.

Leave a comment

About this Entry

This page contains a single entry by David Stutzman published on December 22, 2009 8:36 PM.

SPie - Specifier's Properties Information Exchange was the previous entry in this blog.

Simple Collaboration Tools are Key is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.