![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
CSRF Newsletters
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This is a continuation of this discussion from the Fall/Winter 2000 issue which included a historical perspective on information systems, drawings, and specifications from the 1950s through the 1990s. The conclusion was that in the past we have always thought about drawings, specifications, and construction information as separate domains and that a significant portion of our efforts have been to coordinate these separate repositories of information. The current question is where are we on the road to the integration of this information? Information Systems |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
What is the type of information we require? This depends upon what role we play in the process and what our responsibilities are. The following are some typical examples for a few of the participants: Exhibit A
Our vision is the integration of separate documents and systems of information into one system with all the information we are looking for within one document. Our vision is almost reality but there is not a simple answer yet. Although the basic technology and tools exist, standard operating systems are not yet readily available and utilized. One exception to this is in the area of process engineering where an international standard (ISO 10303) called STEP (Standard for the Exchange of Product Model Data) (http://cic.nist.gov/plantstep/stepinfo/step_def.htm) is used for the exchange of information. STEP is a worldwide effort to develop a mechanism for the exchange and sharing of engineering data using neutral industrial data definitions, representation, and language to enable product data sharing between software applications throughout a product life cycle. PlantSTEP (http://cic.nist.gov/plantstep/) is a consortium of companies that own, design, build, operate and maintain process plants and companies that supply equipment, materials and information technology for the process and construction industries. PlantSTEP develops and supports implementation of data exchange standards based on ISO/STEP to enable concurrent engineering, design, construction, and operation of large facilities by allowing full information sharing among all project contributors. Preparing for the Future We must remember the old lesson of "Garbage in, Garbage out!" We can computerize specifications, reference details, information systems, and integrated drawing and specification systems, but we are still dependent upon the quality of the data. If the data is not of high quality, we will only get into deeper trouble faster. We need to understand the systems we are dealing with:
Classification Systems
There are currently two classification systems in common use for design and construction in North America - MasterFormat and UniFormat. The following table provides the basic breakdown of the two formats at the first level. Exhibit B
We must analyze our databases of information and the CAD objects we are dealing with to decide how to organize the data. MasterFormat is organized on the basis of materials and methods of construction. UniFormat is organized on the basis of elements, systems, and assemblies. The two systems are therefore appropriately used for the organization of different types of information as suggested by the following table: Exhibit C
CAD Objects This is a new and different world and requires a change in mind set from dealing with lines. It will take time and effort for everyone to adjust to think and operate in terms of objects in contrast to lines. It is not easy for us to make our minds think in a basically different way. Actually operating in a fundamentally different way is much more difficult than just talking about it. It is my opinion that keynoting is one method to help facilitate this change in mindset. Keynoting requires us to classify objects on drawings and directly relate to other databases of information. Keynoting is often thought of only in terms of MasterFormat, but the concept also works with other classification systems such as UniFormat.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Keynoting can therefore be used for any type of object on drawings.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Existing Integration Efforts Besides the advancements in the power and process engineering area described above, there are other more general efforts currently under way.
RTKL Efforts At RTKL, we have working to more closely coordinate our CAD drawings with our specifications. We have had a list of terminology with associated keynote designators to be used on drawings to facilitate using the same terminology on the drawings and specifications. We have now put this list into a database format and added a field for coordination of information between the drawings and the specifications. This master list is edited by the project architect/engineer for the project with sections and terms deleted and added as required for the project. Notes are placed on the CAD screen from the edited project database. New items unique to the project are documented once in the database for consistent placement on the drawings. Items deleted from the master database are no longer available for placement on the drawings. Only notations included in the database may be placed on the project drawings providing for the control of notations on a set of project drawings by documentation in one location, the project terminology data base. The coordination window provides for drawing/specification information location window ñ what information is in the specifications, and what information should be added about the items on the drawings. In the above example, the specifications state foundation insulation thickness is as indicated on drawings, so thickness should be included with the notation. This program also reads CAD files to create a list of all the terms placed on CAD drawings. This provides for the automatic creation of legends on each sheet for a project using keynoting. It can also provide a checklist of all terms on a set of CAD drawings for coverage in the specifications or a cost estimate. This program has the potential to do the first basic editing of a master specification database to only retain material relating to subjects included on the project CAD drawings. The Future We will soon be able to integrate CAD and other information on a day-to-day basis using standard operating systems in a much more integrated fashion. Our normal means of transmitting information to others will be much different. Instead of coordinated separate documents, we will be using integrated documents. The secret to a smooth transition will be the possession of comprehensive, accurate, and coordinated separate information from which to create the integrated information.
About the author: Robert W. Johnson, AIA, FCSI, CCS is a Past President of CSI, a Director of CSRF and Vice President and Director of Technical Resources at RTKL Associates, Inc. He can be reached at rjohnson@bal.rtkl.com. The CSRF newsletter is published for SPECTEXT® subscribers and others involved in design and construction. To obtain your copy of Creating a Common Language®, please contact the CSRF Support Center by telephone at 1-877- SPECTXT or 410-838-7561 or you may e-mail us at supportcenter@csrf.org © Copyright 2007, The Construction Sciences Research Foundation, Inc. Updated January 12, 2007. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||