# Presentation: 670979

## IAI Blueprint for the Start of the 21st Century

- <date/time>

***IAI Blueprint for the Start of the 21******st****** Century***

- IAI Technical Advisory Group

- Dr. Vladimir Bazjanac, TAG Leader

## Work Behind This Report

**Hundreds of hours of contributors’ time**
**Teleconferences **
**17 teleconferences since April 1, 2000**
**Brainstorming**
**Brainstorming session in Berkeley, CA September 6-8, 2000**
**E-mail exchange**
**Content-rich e-mail discussion of topics**** **
**Supporting documents**
**Posted on the TAG FTP site**

- TAG                                                                                                                                               vb:25/10/2000

## Road Map Issues Addressed

**Impact of the “projects” mode of operation**
**Technical decision making environment that supports projects**
**Model areas in immediate need of development**

- TAG                                                                                                                                               vb:25/10/2000

## Technical Decision Making 

- <date/time>

***Technical Decision Making****** ***

- Dr. Vladimir Bazjanac, US
- Prof. Richard Junge, DE
- Mr. Arto Kiviniemi, FI
- Dr. Kent Reed, US
- Dr. Alastair Watson, UK

## The IFC Object Data Model

- Kernel

** ****The model architecture is in place**

- TAG                                                                                                                                               vb:25/10/2000

## The IFC Object Data Model

- Kernel

** ****The model architecture is in place**

** **
** ****Centralized resources from the**
**  ****International Council**
** ****Centralized resources from IAI Chapters**
** ****Contributed resources from member**
**  ****organizations and individuals**
** **

** ****Development based on the “proposal/approval” principle**
** ****Proposals from domains**
** ****Approvals by various IAI bodies**
** ****ITM as the final technical authority**

- TAG                                                                                                                                               vb:25/10/2000

## Forces Shaping IFC Extensions

**vision**

**extended**
**IFCs**

**previous**
**IFCs**

**data exchange**
**needs**

**new technology**

**user experience**

**implementation**
**experience**

**user**
**investment**

**vendor**
**investment**

- TAG                                                                                                                                               vb:25/10/2000

## The New World of the IAI

**The IAI *****has changed***** to project-based development of the IFC object data model**
**Real-life conditions for projects**
**Project must fit some *****real business plan***
**Substantial funding for each project**
**Impact of that decision: Projects now have control over**
**Funding-related decisions**
**Day-to-day technical decision making**
**How work is done**

- TAG                                                                                                                                               vb:25/10/2000

## Extension Schemata

**Projects responsible for**
**Development of the particular domain extension**
**Integration with the IFC core model**
**Implementation in a real-life software application**

- TAG                                                                                                                                               vb:25/10/2000

## Impact on Domains

**Projects now control internally**
**What is done**
**How it is done**
**Development and delivery time table**
**Staffing**
**Related expenditure**

- TAG                                                                                                                                               vb:25/10/2000

## Project Deliverables to the IAI

**Require only what is reasonable from the project point of view**
**Extension schemata (EXPRESS)**
**Schemata documentation (html)**
**Implementation guide**
**Placement of project scope in the overall building “life-cycle” process**

- TAG                                                                                                                                               vb:25/10/2000

## What Projects Need From The IAI

**Swift outside-of-project decision making (when needed)**
**Swift response to questions**
**Prompt action upon request**
**No distraction with issues irrelevant to the project**
**No outside meddling and interference**
**Direct access to information**
**Direct access to decision making**
**A well informed outside-of-project environment**

- TAG                                                                                                                                               vb:25/10/2000

## Current International Structure

**projects’**
**requirements/**
**impact??**

** ****Projects cannot wait**

** ****How can anyone tell projects what, how and when to do something?**

- TAG                                                                                                                                               vb:25/10/2000

## New International Structure

**IAI leadership and promotion:**
-  Public leadership
-  Vision of interoperability
-  New IAI projects
-  Implementation of IFCs
-  Deployment of IFC software

**Technical decision making**
**regarding:**
-  IFC development/maintenance
-  Quality control
-  Model review
-  Implementation

- TAG                                                                                                                                               vb:25/10/2000

## Evolution to Meet Project Needs

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**new **
**group**

**BUSINESS DOMAIN**

**new **
**role**

**USG**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**IC**

**International Council:**
** ****Chapter representation**
** ****International business cooperation**
** ****Public leadership**
** ****Promotion of vision**
** ****IFC promotion**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**ExCom**

**Executive Committee:**
** ****Day-to-day business of IC**
** ****Administrative tasks for IC**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITF**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**ITM**

**International Technical Forum:**
** ****Chapter technical representation**
** ****Inter-chapter technical forum**
** ****Promotion of  new projects**
** ****Promotion of IFC implementation**
** ****Promotion of software deployment**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**Product Manager(s)**

**Product Manager:**
** ****Responsible for coordination of**
**  ****extension schemata development**
** ****Coordinates inter-project technical**
**  ****work**
** ****Provides**
**  ****inter-project administrative support**
** ****Supports review of extension**
**  ****schemata**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**MSG**

**Modeling Support Group:**
** ****Modeling expertise in EXPRESS**
** ****Day-to-day modeling and core**
**  ****integration support**
** ****Maintenance of the model core**
** ****Quality control**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**ISG**

**Implementation Support Group:**
** ****Forum for implementers’ issues **
** ****Day-to-day support of IFC**
**  ****implementation in software**
** **
** ****Administers compliance testing**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**TAG**

**Technical Advisory Group:**
** ****Broad overview**
** ****Independent technical expertise**
**  ****and guidance**
** ****Advice on global technical**
**  ****developments relevant**
**  ****to the IAI**

- TAG                                                                                                                                               vb:25/10/2000

## Roles in the New Structure

**IC**

**ExCom**

**ITM**

**MSG**

**ISG**

**Product Manager(s)**

**TAG**

**PAG**

**Project****1**

**Leader****1**

**Project****2**

**Leader****2**

**Project****n**

**Leader****n**

**TECHNICAL DOMAIN**

**USG**

**BUSINESS DOMAIN**

**PAG**

***Projects***** Advisory Group:**
** *****Industry***** expertise and advice**
** ****Technical expertise**
**  ****and advice (product/process**
**  ****modeling, IFC, STEP,**
**  ****etc.)**
** ****Software development**
**  ****expertise and advice**
** ****Quality control**

- TAG                                                                                                                                               vb:25/10/2000

## PAG Is Not TAG

**PAG**
**Supports projects**
**Represents AEC/FM and its software industries’ point of view**
**Focus on specific project-related issues**
**Issues primarily defined by its constituency**
**TAG**
**Supports the entire IAI**
**Represents a global view**
**Deals with a wide variety of technical issues**
**Issues often defined by its members**

- TAG                                                                                                                                               vb:25/10/2000

## PAG membership

**Appointed experts**
**Project leaders (ex-officio)**
**Product managers (ex-officio)**
**Technical group leaders or their representatives (ex-officio)**

- TAG                                                                                                                                               vb:25/10/2000

## PAG Make-Up

***Non-negotiable***** requirement: *****committed***** time**
**Initially**
**Candidates submitted by ex-officio members**
**Members elected from submitted candidates *****by consensus***** of ex-officio members**
**Group charter drafted by ex-officio members**
**Afterward**
**New members proposed and elected by PAG members**
**Group leader elected by PAG members**
**PAG mode of operation decided by PAG members**
**Group charter adjusted/modified and approved by PAG members**

- TAG                                                                                                                                               vb:25/10/2000

## PAG Economics

**Costs**
**Contributed (no cash outlay): *****members’ time *****(and anything else)**
**Reimbursable (if accepted by projects and/or IAI International):**
**	****(a) *****travel***** (air and ground transportation)**
**	****(b) *****lodging***
**	****(c) organizers’ *****meeting costs***
**Sources of reimbursement**
**Projects**
**IAI International**
**A combination of the two**

- TAG                                                                                                                                               vb:25/10/2000

## Project-Focused Responsibilities

**Cooperation with Product Manager and other projects**
**Projects, Product Manager**
**Participation in the resolution of conflict**
**Projects ****(input from: Product Manager, PAG, MSG, ISG,TAG)**
**Quality control of the project**
**Projects ****(input from: Product Manager, PAG, MSG,**** ****ISG,TAG)**
**Review management**
**Projects ****(coordinated by Product Manager)**

- TAG                                                                                                                                               vb:25/10/2000

## Product-Focused Responsibilities

**Detection of differences in approach**
**PAG ****(input from: Product Manager,**** ****projects)**
**Conflict resolution in the representation of the same data across projects**
**PAG ****(facilitated by Product Manager, input from:**** ****MSG, ISG,TAG)**
**Identification/resolution of other commonalities/ conflict**
**Product Manager/PAG ****(input from: projects,**** ****MSG, ISG,TAG)**
**Assurance of model consistency**
**MSG ****(input from: Product Manager,**** ****TAG)**
**Quality control of the product**
**Product Manager ****(input from: PAG, MSG, projects,**** ****ISG,TAG)**

- TAG                                                                                                                                               vb:25/10/2000

## Other Technical Responsibilities

**Assurance of broad global usability**
**PAG, ISG, TAG**
**Decisions about the content of future core(s)**
**Decisions regarding***** content *****by consensus of all groups, decisions regarding content***** implementation *****by MSG**

- TAG                                                                                                                                               vb:25/10/2000

**Questions about this part?**

- TAG                                                                                                                                               vb:25/10/2000

## Harmonization With STEP

- <date/time>

***Harmonization With STEP***

- IAI Technical Advisory Group

## Contributors to This Report

**TAG members:**
**     ****Dr. Vladimir Bazjanac, LBNL, US****	****	****Dr.Ing. Thomas Liebich, AEC 3, DE**
**     ****Mr. David Chassin, PNNL, US****	****	****	****Dr. Patrice Poyet, CSTB, FR**
**     ****Mr. Robin Drogemuller, CSIRO, AU****	****	****Dr. Kent Reed, NIST, US**
**     ****Prof. Chuck Eastman, Georgia Tech, US****	****Mr. Richard See, Microsoft, US**
**     ****Mr. Jim Forester, MarinSoft, US****	****	****Mr. Nikolay Shulga, Spatial, US**
**     ****Mr. Julian Fowler, PDT Solutions, UK****	****	****Dr. Väino Tarandi, EuroSTEP, SW**
**     ****Dr.Ing. Wolfgang Haas, Haas+Partner, DE****	****Dr. Paul Teicholz, Stanford, US**
**     ****Dr. John Kunz, CIFE, US****	****	****	****Mr. Jeffrey Wix, Wix Consulting, UK**

- TAG                                                                                                                                               vb:25/10/2000

## STEP and IFCs

**In common**
**The use of EXPRESS modeling language**
**STEP physical file (Part 21) exchange format**
**Different**
**Data model architecture**
***How***** EXPRESS is used**
**A few STEP Parts are adapted for use in IFCs**
**No ANDOR types in IFCs**
**Attributes deemed not necessary dropped from IFC definitions**
**“****Ifc” prefix added to all names in the IFC object data model**

- TAG                                                                                                                                               vb:25/10/2000

## IFC Relationship to ISO 10303

**Based on STEP**
**Some data specifications “borrowed” from STEP**
**“****Borrowed” specification *****modified***** structurally and semantically to fit the IFC modeling approach**
**Appropriate designation for the current IFCs**
**Consistent with STEP**
**Some data specifications “borrowed” from STEP *****without***** modifications**
**“****Borrowed” specification clearly identified as such**
**Possible common IFC and STEP geometry code**
**STEP compatible**
**Use STEP architecture and methodology, *****or***
**Interoperable with some STEP Application Protocols**

- TAG                                                                                                                                               vb:25/10/2000

## STEP Compatible IFCs

**Use STEP architecture and methodology**
**Re-engineer IFCs as one or more APs**
**Re-engineer IFCs as extensions to STEP Integrated Resources (IRs)**
**Interoperability not guaranteed**
**Make IFCs interoperable with some STEP APs**
**“****Interoperable” needs definition**
**Define operations necessary to preprocess a STEP exchange file to make it available via IFCs, and vice-versa**

- TAG                                                                                                                                               vb:25/10/2000

## Implications of “STEP Compatible”

**Re-engineer IFCs as one or more STEP APs and/or extensions to STEP IRs**
**Complete change of IFC architecture**
**Completely new/different IFC object data model**
**Define operations necessary to preprocess a STEP exchange file to make it available via IFCs, and vice-versa**
**The necessary mapping would be very difficult to accomplish**
**Does not make IFCs themselves any more “STEP compatible”**

- TAG                                                                                                                                               vb:25/10/2000

## Implications of “STEP Consistent”

**Remove the “Ifc” prefix from names of entities in the IFC object data model that originate in STEP**
**Reuse of STEP “2****nd**** Edition” Parts 41, 42 and 43**
**Reintroduce ANDOR**
**Reintroduce multiple inheritance**
**Implementers can easily circumvent any problems that may result**
**Reintroduce *****Representation_item.name***
**Give a “name” attribute to most geometry objects**
**Ask STEP to extend Part 42**
**Include the IFC way of representing profiles**
**Extend the way swept solids and surfaces are defined by profiles**
**Copyright**
**The reuse of parts of ISO standards is likely to be viewed by ISO as a copyright infringement**
**Negotiate an agreement in advance**
**Much greater effect on implementers than on modelers**

- TAG                                                                                                                                               vb:25/10/2000

## TAG Recommendation

**Move from “STEP based” to “STEP *****consistent*****”**
**Plan it for the next “platform” release**
**Get implementers to “buy in”**

- TAG                                                                                                                                               vb:25/10/2000

## Benefits of “Step Consistent”

**Code reuse**
**Much less work CAD vendors that need to implement both STEP an IAI models**
**Less work for MSG**
**Only IAI-specific constructs need to be documented and maintained**
**STEP packaged libraries**
**Can reduce the cost of implementation**
**Dual capabilities**
**By implementing one (IFCs or STEP) developers acquire the other (STEP or IFCs)**
**Other CAD/engineering developers may join implementation by getting “two for one”**

- TAG                                                                                                                                               vb:25/10/2000

## Additional Benefits

**Increased motivation for AEC/FM suppliers to develop IFC-based product definitions**
**A unified model for building/site-work/civil projects**
**End users will benefit from a single environment for data integration**
**Gain of additional expertise (from STEP)**
**IAI and STEP communities would be more conducive to working together**
**Less duplication of effort**
**Common business goals**
**Faster integration with other tangentially associated industries (ship and plant building)**

- TAG                                                                                                                                               vb:25/10/2000

## Drawbacks of “Step Consistent”

**Changes to definition of geometry**
**Effect on software applications that already have implemented IFC geometry**
**Changes to some of the IFC modeling practice (use of ANDOR, reintroduction of dropped attributes, no “Ifc” prefix)**
**Without IFC<=> STEP mapping, loss of upward/ downward compatibility with previous IFC releases**
**STEP origin of parts of the IFC object data model**
**Less control of data model development**
**Need to extend/modify the data model**
**Possible dependence on STEP Part developers**
**Time and cost to modify the model and software**

- TAG                                                                                                                                               vb:25/10/2000

## Upward/Downward Compatibility

**The use of EXPRESS-X may solve some of the problems**
**Do not worry about downward compatibility**
**Leave it to software applications and market forces**
***Consider***** upward compatibility when making modeling decisions**

- TAG                                                                                                                                               vb:25/10/2000

## Supporting Documents

**TAG ftp site on ‘iaiweb’**
**     ****\International\Technical\Groups\TAG\Documents**
**harmonization_e-mail_discussion_summary.txt**
**STEP_compatibility_of_IFC.doc**
**IAI_blueprint_for_21st_century.ppt**
**    ****\International\Technical\Groups\TAG\TAG_telecon_notes**
**TAG telecon notes dated between July 27 and October 19, 2000**
**Also available on the Web (after November 3)**
**	****http://eetd.lbl.gov/btd/iai/TAG/documents**
**harmonization_e-mail_discussion_summary.txt**
**STEP_compatibility_of_IFC.doc**
**IAI_blueprint_for_21st_century.ppt**

- TAG                                                                                                                                               vb:25/10/2000

**Questions about this part?**

- TAG                                                                                                                                               vb:25/10/2000

## First Things First

- <date/time>

***First Things First***

- IAI Technical Advisory Group

## Contributors to This Report

**TAG members:**
**     ****Dr. Vladimir Bazjanac, LBNL, US****	****	****Dr.Ing. Thomas Liebich, AEC 3, DE**
**     ****Mr. David Chassin, PNNL, US****	****	****	****Dr. Patrice Poyet, CSTB, FR**
**     ****Mr. Robin Drogemuller, CSIRO, AU****	****	****Dr. Kent Reed, NIST, US**
**     ****Prof. Chuck Eastman, Georgia Tech, US****	****Mr. Richard See, Microsoft, US**
**     ****Mr. Jim Forester, MarinSoft, US****	****	****Mr. Nikolay Shulga, Spatial, US**
**     ****Mr. Julian Fowler, PDT Solutions, UK****	****	****Dr. Väino Tarandi, EuroSTEP, SW**
**     ****Dr.Ing. Wolfgang Haas, Haas+Partner, DE****	****Dr. Paul Teicholz, Stanford, US**
**     ****Dr. John Kunz, CIFE, US****	****	****	****Mr. Jeffrey Wix, Wix Consulting, UK**

**  ****Additional contributors:**
**     ****Dr. Francois Grobler, CERL, US**
**     ****Mr. Jan Karlshøj, CarlBro, DK**
**     ****Mr. Arto Kiviniemi, VTT, FI**
**     ****Dr. Alastair Watson, Leeds University, UK**

- TAG                                                                                                                                               vb:25/10/2000

## What One Can Do With IFCs Now

**Building geometry definitions pretty much complete**
**Exchange of *****objects with***** *****geometry***** among IFC-compatible CAD applications**
**Exchange between applications that generate geometry and some *****downstream***** applications that need building geometry data**
**Exchange of some *****rudimentary***** data other than geometry (architecture, HVAC, project management, FM, etc.) among downstream applications**
**Abundant opportunities to mine the exchange of geometry**

- TAG                                                                                                                                               vb:25/10/2000

## What One Cannot Do Yet

**Exchange *****rich***** data sets among downstream applications**
***Fully***** support e-Commerce needs**
**Use a *****stream***** of applications to exclusively support multidisciplinary industry tasks with IFCs**
**Use an IFC project model as the main and complete *****repository***** of project information**

- TAG                                                                                                                                               vb:25/10/2000

## The Status of IFCs

**IFC**
**object **
**data**
**model**

**codes and**
**standards**

**facilities**
**management**

**architecture**

**cost**
**estimating**

**construction**

**engineering**

**lighting**

**program-**
**ming**

**site**
**planning**

**structural**

**HVAC**

**electrical**

**catalogues**

**simulation**

**commis-**
**sioning**

**procure-**
**ment**

**wiring**

**value**
**engineering**

**civil**

**fire**
**protection**

- TAG                                                                                                                                               vb:25/10/2000

## Example: An IFC Building

** ****Procurement of equipment**
**  ****and furnishings**
**   ****e-Catalogues**
**   ****B2B**

** ****2-D drawings**
** ****Native use of 2-D CAD**
**  ****drawings**
** ****Legacy drawings**

** ****Reinforced concrete**
** ****Structural calculations**
** ****Steel bar details**

** ****Electrical engineering**
** ****Load calculations**
** ****Wiring diagrams**

** ****Civil engineering**
** ****Planning of excavation**

- TAG                                                                                                                                               vb:25/10/2000

## Criteria for Filling Model Gaps

**Get the “biggest bang for the buck”**
**Develop areas that will spur the development of other areas**
**Develop areas that will bring interoperability to the largest number of existing industry software applications**
**Develop schemata that are likely to be implemented in leading industry software**
**First things first: Provide interoperability for “upstream” and “midstream” applications**
**Interoperable “front” and “midstream” applications will spur the development of interoperable “downstream” software**

- TAG                                                                                                                                               vb:25/10/2000

## Consult the Enterprise Model

## Follow Process Modeling

**spatial**
**coordination**

** ****spaces**
** ****walls**
** ****windows**
** ****doors**
** ****ceilings**
** ****roofs**

** ****beams**
** ****columns**
** ****slabs**
** ****frames**
** ****foundations**
** ****piles**

** ****pipes**
** ****ducts**
** ****cables**
** ****cable carriers**
** ****equipment**

** ****support**

**building designer**

**structural**
**designer**

**services designer**

**building contractor**

**sub-contractor**

- TAG                                                                                                                                               vb:25/10/2000

## Follow Process Modeling

**spatial**
**coordination**

** ****spaces**
** ****walls**
** ****windows**
** ****doors**
** ****ceilings**
** ****roofs**

** ****beams**
** ****columns**
** ****slabs**
** ****frames**
** ****foundations**
** ****piles**

** ****pipes**
** ****ducts**
** ****cables**
** ****cable carriers**
** ****equipment**

** ****support**

**building designer**

**structural**
**designer**

**services designer**

**building contractor**

**sub-contractor**

** ****reflected**
** ****ceiling**
** ****plan**

** ****ceiling layout**

** ****pipes**
** ****ducts**
** ****cables**
** ****diffusers**
** ****lights**
** ****PA boxes**
** ****sprinkler heads**
** ****sensors**
** ****alarms**

** ****beams**
** ****columns**

** ****ceiling layout**

** ****requirements**
** ****approvals**

**building contractor**

**building designer**

**sub-contractor**

**sub-sub-contractor**

**structural**
**designer**

**services designer**

- TAG                                                                                                                                               vb:25/10/2000

## Model Processes

- TAG                                                                                                                                               vb:25/10/2000

## Create the Matrix

## Need for New Model Functionality

**Enable e-Commerce**
**Enable the use of 2-D drawings **
**Enable complex structural calculations**
**Enable electrical design and wiring**
**Enable civil engineering for buildings**

- TAG                                                                                                                                               vb:25/10/2000

## Data Exchange: IFCs and XML

**conceptual**
**model**

**IFCs:**
**consistent**
**schemata**

**data exchange**

**STEP**
**IRs**

**Part 21**

- IAI

**conceptual**
**model**

**data exchange**

**XML**

**?**

**conceptual**
**model**

**conceptual**
**model**

**information**
**schema**

**information**
**schema**

**information**
**schema**

- TAG                                                                                                                                               vb:25/10/2000

## Data Exchange: IFCs and XML

**conceptual**
**model**

**IFCs:**
**consistent**
**schemata**

**data exchange**

**STEP**
**IRs**

**Part 21**

- IAI

**conceptual**
**model**

**data exchange**

**XML**

**?**

**conceptual**
**model**

**conceptual**
**model**

**information**
**schema**

**information**
**schema**

**information**
**schema**

**conceptual**
**model**

**conceptual**
**model**

**Harmonize conceptual models:**
** “****XML” projects should be like other IAI projects**
** ****Use IFCs where they are available**
** ****Contribute to the definition of the missing**
**  ****IFCs**
** ****Be part of a product**** **
** ****Extend the IFC object data model with e-Commerce concepts**

- TAG                                                                                                                                               vb:25/10/2000

## e-Commerce Topics

## Extensions to the IFC Model

**New extension schemata**
**Electrical**
**Civil**
**Completion of started/existing extensions**
**All extension schemata currently under development**
**Structural schemata**
**Additions to existing and inclusion in new schemata**
**CDS (2-D drawings)**
**e-Commerce definitions**

- TAG                                                                                                                                               vb:25/10/2000

## The Ten Million Dollar Question

**How to stimulate new projects that will develop new IFC extension schemata in these areas?**

- TAG                                                                                                                                               vb:25/10/2000

## Remember the IAI Mission

**Quote from Prof. Chuck Eastman:**
**	****“****The only benefits of a building model, at any scale, are applications that can populate instance data, can exchange data between tasks.”**

- TAG                                                                                                                                               vb:25/10/2000

## The Rule of “3”

**Types of data exchange**

**IFC**
**object     **
**data**
**model**

- TAG                                                                                                                                               vb:25/10/2000

## The Rule of “3”

**Types of data exchange**

**IFC**
**object     **
**data**
**model**

**IFC**
**object     **
**data**
**model**

**IFC**
**object     **
**data**
**model**

**app 1**

**app 1**

**app 2**

**app 1**

**app 2**

**app 3**

** ****One application: *****testing***

** ****Two applications:**
**   *****direct exchange***

** ****Three applications:**
**  ****minimum set for *****interoperability***

- TAG                                                                                                                                               vb:25/10/2000

## Applying the Rule of “3”

**  **

**IFC**
**object     **
**data**
**model**

**CAD 1**

**CAD 3**

**CAD 2**

** ****Int*****ra*****-disciplinary (similar)**
**  ****applications:**

** ****Int*****er*****-disciplinary (dissimilar)**
**        ****applications:**

**IFC**
**object     **
**data**
**model**

**CAD**

**cost**

**HVAC**

**   ****Interoperability among**

**IFCs are about ****“*****B******3******B*****”**

- TAG                                                                                                                                               vb:25/10/2000

## Right Answer to a Good Question

**If someone asks what to do to participate**
**Ask what is the most used professional software in their business**
**Then, ask them to talk to that software’s developer and *****formulate, fund and do***** a project that will make it possible to make that software IFC compatible**
**If they do not know what that software may be, get the answer from**
**TAG and/or MSG**
**Their chapter’s Technical Coordinator**

- TAG                                                                                                                                               vb:25/10/2000

## The Next Two-Three Years

**Adjust the technical decision making process to the needs of projects**
**Develop the next “platform”**
**Harmonize with STEP**
**Add new functionality to the model**
**support of e-Commerce**
**2-D drawings**
**Stimulate new projects that will enable**
**“****Mission-critical” professional software to be IFC compatible**
**Interoperability within AEC/FM industry processes**
**Mine the gold at hand**
**Seamless import/export of building geometry**

- TAG                                                                                                                                               vb:25/10/2000

## The Next Two-Three Years

**Adjust the technical decision making process to the needs of projects**

***virtually no cost***

**  ****Develop the next “platform”**
**  ****Harmonize with STEP**
**  ****Add new functionality to the model**
**  ****support of e-Commerce**
**  ****2-D drawings**

***centrally funded***

**  ****Stimulate new projects that will enable**
**“****Mission-critical” professional software to be IFC compatible**
**Interoperability within AEC/FM industry processes**
**  ****Mine the gold at hand**
**Seamless import/export of building geometry**

***critical***

- TAG                                                                                                                                               vb:25/10/2000

## Food for Thought and Action

**STEP copyright**
**Negotiate an agreement with ISO *****in advance***
**The IFC object data model is in the open now**
**Choose licensing model**
**Look at OpenSource licensing**

- TAG                                                                                                                                               vb:25/10/2000

## Cooperation with Others

**Current liaison relationships with**
**TC 184/SC 4 (STEP)**
**TC 59**
**Potentially very beneficial future liaisons with**
**The Object Management Group (****OMG****)**
**Product Life-Cycle Support (****PLCS****)**
**World Wide Web Consortium (****W3C****)**

- TAG                                                                                                                                               vb:25/10/2000

## What’s Next for This Report?

**Continue the discussion within TAG**
**Start and support a *****constructive IAI-wide***** *****discussion *****of main issues**
**Draft a written document**
**Six-week IAI-wide review period**
**Post the document on the public web pages**

- TAG                                                                                                                                               vb:25/10/2000

**Thank you!**

**Questions?**

- TAG                                                                                                                                               vb:25/10/2000