We have completed specification of the Model View Definitions (MVDs) necessary for implementation of the specified IDM functionality. We are using the MVD and Concept definition approach to modularize the exchange specification, to facilitate implementation and testing. Documentation of the MVD are complete. The definition of test files for implementers are now being prepared.
This project is sponsored by the Charles Pankow Foundation and Precast/Prestressed Concrete Industry and undertaken in collaboration with National Institute of Building Sciences, buildingSMART Alliance, Georgia Institute of Technology, Technion-Israel Institute of Technology and Digital Alchemy.
A committee of the Precast/Pre-stressed Concrete Institute (PCI) advised by Georgia Tech are developing a national BIM standard to support the critical information exchanges surrounding precast concrete. The precast pieces include stemmed deck members, flat deck members, beams, columns, load bearing walls and spandrels, piles, and architectural facades, plus others. Multiple business cases have been identified, addressing design-bid-build, design-build and precast as lead contractor modes of project delivery. The lifecycle phases include architectural design and construction modeling, structural engineering of precast, fabrication level detailing and manufacture planning, through to logistics and erection. These results are incorporated in a completed Information Delivery manual (IDM). The Exchange Requirements have been defined to allow functional specification of the information needs for geometry, properties, level of detail, reinforcing and prestressing, structural information and other semantic issues that define the needs of various exchanges. Model View Definitions (MVDs) have been specified for the data exchanges defined in the IDM. This has led to the specification of about 130 specific bindings to the IFC (Industry Foundation Class) entities, grouped into small modules called Concepts. These bindings have been documented and posted on an open website for implementers, called IFC Solutions Factory. Currently, test files for testing the MVDs are being prepared, to test both import and export exchanges. The advisory team expects to work with relevant software companies and to outline a validation process for the resulting implementations. A necessary component of this work is to identify and specify objects and relationships that are missing from the current IFC schema but are needed to cover all precast concrete objects and structures. These necessary IFC extensions have been defined and adapted as needed for implementation in the upcoming 2.x4 IFC release, to be released this quarter.
Meeting -Implementation of PCI National BIM Standard – Phase 2, March 28, 2012
4th Meeting of PCI National BIM Standard – PCI Convention, Salt Lake City, UT
October 15, 2011
Read More: AECbytes Article
Initial steps at implementation of the Precast National BIM standards was demonstrated at the PCI Convention, chaired by Georgia Tech. The three hour session involved the demonstration by four different companies, demonstrating interoperability among six different software applications. These included Nemetschek Vectorwork, Nemetschek Scia Engineer, Structureworks, Tekla, Structureworks Plant Manager, and Structureworks PartTracker. The workflow included architectural modeling in Vectorworks that passed a simple precast model to a structural analysis package. Scia Engineer. Scia analyzed the model and modified it, passing it back to Vectorworks. Vectorworks then passed the model to both Structureworks and Tekla, two fabrication-level modelers. They showed how the model could be imported and made into editable objects, then detailed the model in slightly different ways. The details includes some rebar and connection informaiton, as well as slab detailing, addressing both hollowcore and doubletee slab beams. They both passed on their models to plant management systems. Tekla passed its model to Scia Plant Manager, while Structureworks passed its model to its own Parttracker system. Also shown was the exporting to alternatively support editing (as needed for passing the design from architect to detail rand clash detection and project coordination. The demonstration was documented in an AECbytes Article. This demo will be followed up with future expanded demos at the PCI upcoming events in 2012.
CURRENT STEP AT THE STANDARD DEVELOPMENT PROCESS