PM-3 Material Selection, Specification and Procurement
| Business needs: | ||||||||||||||||||||||||||||||||
|
The material selection and procurement/purchasing processes are
currently not very well standardized. The thousands of product
manufacturers each produce their own product data publications, usually
deliberately unique so as to distinguish themselves from their
competition. Attempts to standardize construction product data have
mostly failed due to the extreme decentralization of production and
reluctance of manufacturers to cede control of their data to central
database organizations.
The recent growth of Internet product information sites has not improved the situation at all, because the only method of search is by keyword, which seldom provides enough information to make an intelligent selection within a reasonable time frame. In addition, there are few software tools that attempt to provide assistance in material selection, mostly because the process is so data-intensive and third-party management of the data is too expensive to be practical. E-commerce in the construction industry is hampered by the myriad ways different manufacturers index or identify similar or identical products. This is more of a problem in construction than in retail or consumer industries because construction is custom work and competitive bidding/pricing is required on each project more often than not. Lack of a standardized way to state product requirements requires unique, custom-prepared documents for each bid or pricing event. Expected Benefits: Material specification, selection and procurement processes cross over all disciplines of architecture, engineering and construction. All the current software products that implement parts of these processes will benefit from an analysis of the overall process. At the micro level, individual applications should be able to use the analysis to improve their capabilities. At a slightly higher level, they should be able to more effectively exchange information with related applications. At the highest level, new software tools that utilize standardized product information would improve the overall process, lessen the time required, and improve accuracy. E-commerce would be greatly facilitated by this standardization. Purchasers would more easily find equivalent products, increasing competition and allowing smaller organizations to compete more effectively. For the IAI, this project should draw the interest of the many new companies involved in business-to-business commerce via the Internet. |
||||||||||||||||||||||||||||||||
|
Solution: |
||||||||||||||||||||||||||||||||
|
The PM domain has conducted a small test to identify the fit (or lack
of fit) of the existing IFCs to product information and specification
data. This preliminary investigation showed that exchange of such data
would have to be through use of property sets defined by the user or
data developer. To make such an approach feasible a standard set of
terminology must be used. The Overall Construction Classification
System (OCCS), the development of which is being spearheaded by CSI, is
one possible set of terminology that could be used.
Several aecXML Working Groups intend to develop standardized data identifiers ("tags") for many of the items of information covered by this project's scope. These Working Groups include: "Catalogs" (for Product Information), "Procurement," and "Design, Specification, Schedule, Cost." aecXML constitutes both "data structure" and a data portion (the names of tags). The data structure proposed by the working groups should correspond to the Ifc property set structure. The data portion should be coordinated with a standard set of terminology. |
||||||||||||||||||||||||||||||||
|
Scope of work: |
||||||||||||||||||||||||||||||||
|
In Scope: |
||||||||||||||||||||||||||||||||
One of the processes not yet supported by the model is the Material
Selection-Specification-Procurement process. Although the generic IFC
data structures allow any type of data to be incorporated, the static
(predefined) IFCs do not include the detailed material property
information necessary to perform the following tasks:
|
||||||||||||||||||||||||||||||||
|
Out-of scope: |
||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||
| Supporting Activities | ||||||||||||||||||||||||||||||||
|
aecXML Working Groups "Catalogs," "Procurement," "Design, Specification, Schedule, Cost": Preliminary analysis consisting of initial set of tags developed for aecXML.
OCCS Development Committee: The OCCS project includes development of data that would be ideal for use in the portion of the model contemplated by this project. Progress on this project would significantly reduce the time frame for this IAI project. |
||||||||||||||||||||||||||||||||
| Project addresses | ||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||
| Remarks | ||||||||||||||||||||||||||||||||
| THIS PROJECT HAS BEEN INTEGRATED INTO IFC2x2 (Release May 2003) | ||||||||||||||||||||||||||||||||

