research board about home

 
Integrating CAD and Databases - Conclusion

CSRF Newsletters

 By Robert W. Johnson, AIA, FCSI, CCS, CCCA

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

Information

A/E

Owner

Manager

Contractor

Supplier

Code Official

Lender

Assemblies

****

****

****

****

****

****

****

Building Code

****

****

 

****

****

****

****

Components

****

****

 

****

****

****

****

Constructed Conditions

 

 

****

 

 

 

 

Construction Details

****

****

****

****

****

****

 

Furniture & Equipment

 

****

****

 

 

 

 

Maintenance Instructions

 

 

****

 

****

 

 

Material & Method Costs

****

 

 

****

****

 

 

Operation Instructions

 

 

****

 

****

 

 

Specified Product Data

****

****

****

****

****

****

****

Installed Product Data

 

 

****

 

 

 

 

Shop Drawings

****

 

****

****

****

 

 

Space Usage

 

 

****

 

 

 

 

Specifications

****

****

****

****

****

****

****

Systems

****

****

****

****

****

 

****

Systems & Assemblies Cost

****

****

 

****

****

 

 

Time Schedule

****

****

 

****

****

 

****

Zoning

****

****

 

 

 

****

****

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:

  • Specifications ñ How many and what systems do we use? Are they sufficient? Do we need more or fewer? Is our technical database of adequate quality?
  • Specification Systems ñ Preliminary project descriptions, outline specifications, extended notes (sheet specs), shortform specifications, full construction specifications?
  • Information Databases ñ What types of information do we use? What additions would be beneficial? What is the quantity and quality of the information? What information is available from others?
  • Types of Information ñ Manufacturers and products, original costs, operation and maintenance costs, specifications, details, operation and maintenance?
  • Reference Details ñ Do the details reflect good practice? Are they applicable to our practice? Are they coordinated with our specifications?
  • What is the order of our priorities ñ Construction documents, construction costs, construction schedule, facilities management, specification systems, information databases? We should work on the areas of highest priority first. You can't do it all at once.

Classification Systems

  • What are the objects on our CAD drawings? Are they pieces of equipment, installation methods, components, assemblies, systems, some of each? How do we organize or classify the CAD objects so that we can find them in our library?
  • How do we categorize our database information? What systems do we use now? Are they appropriate? Will they work with CAD objects? What classification system(s) should be used to integrate CAD objects with information databases we use?

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

MasterFormat

UniFormat

1     General Requirements

A    Substructure

2     Site Construction

B    Shell

3     Concrete

C    Interiors

4     Masonry

D    Services

5     Metals

E    Equipment & Furnishings

6     Wood and Plastics

F    Other Building Construction

7     Thermal and Moisture Protection

G    Building Sitework

8     Doors and Windows

 

9     Finishes

 

10    Specialties

 

11    Equipment

 

12    Furnishings

 

13    Special Construction

 

14    Conveying Systems

 

15    Mechanical

 

16    Electrical

Z    General

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

Information

MasterFormat

UniFormat

Assembly Data, Performance & Specifications

 

********

Assembly CAD Objects

 

********

Costs ñ Detailed Materials & Methods

********

 

Costs ñ Systems & Assemblies

 

********

Equipment Data, Performance, & Specifications

********

 

Equipment CAD Objects

********

 

Installation Method Data, Performance, & Specifications

********

 

Installation Method CAD Objects

********

 

Material Data, Performance, & Specifications

********

 

Material CAD Objects

********

 

Preliminary Project Descriptions

 

********

Product Data

********

 

Reference Details

 

********

Specifications ñ Outline

********

 

Specifications ñ Full

********

 

System Data, Performance, & Specifications

 

********

System CAD Objects

 

********

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.

MasterFormat™
04810.A Face Brick
07511.A10 Base Flashing
07511.D30 Tapered Roof Insulation
   
UniFormat™
A1010.D Spread Footing
B2010.A Exterior Wall Assembly
B2010.C10 Exterior Wall Framing

 


Existing Integration Efforts

Besides the advancements in the power and process engineering area described above, there are other more general efforts currently under way.

  • Industry Alliance for Interoperability (IAI) (http://iaiweb.lbl.gov/) ñ An alliance of A/Es, vendors, organizations, manufacturers to create data standards for the building industry. IAI is developing Industry Foundation Classes (IFC) based on object-oriented technology for sharing intelligent information throughout the building life cycle.
  • CAD Software ñ Software with virtual 3-D modeling with object oriented technology has been available for sometime with Microstation TriForma (http://www.bentley.com/products/triforma/) and AutoCAD Architectural Desktop (http://www3.autodesk.com/adsk/section/0,400019-123112,00.html) as prominent examples. Revit (http://www.revit.com/) is a relatively new program that displays information in three interrelated forms or windows simultaneously ñ 3-D, 2-D, and database. Revisions in any one of the windows changes the information in the other two.
  • AecXML (http://www.aecxml.org) ñ A movement is currently underway to facilitate communication of information across software programs in the design and construction industry by means of a new language with the following mission: "aecXML is an XML-based language used to represent information in the Architecture, Engineering and Construction (AEC) industry. This information may be resources such as projects, documents, materials, parts, organizations, professionals or activities such as proposals, design, estimating, scheduling and construction. It is intended to be used as an XML namespace and to facilitate information exchange of AEC data on the Internet."
We have yet to see the completion of these and other efforts into integrated off-the-shelf software programs to allow us to easily integrate CAD and databases of information, but they will be coming in the foreseeable future. Exactly what form they will be in or who will provide them is still to be seen.

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.

 
Home |  About |  Board |  Research |  WebFormat™ |  Contact Us |  Newsletters
Publications |  News Releases |  Related Sites |  Search