1. Developing an IDM Information Delivery Manual Part 1. Industry Workgroup Training, Creating IDMs Alliance NA 2010 Dianne Davis, NA-IDM Coordinator Jan Karlshøj, International IDM Coordinator

2. Define Industry Need Assemble a Working Group Develop the IDM Consensus Review Assemble Technical Workgroup Develop MVD Software Implementation NBIMs Balloting Process Certification & Testing Maintain and Update Creating the National BIM Standard

3. You can’t automate what you don’t understand Each day information is exchanged by teams, but in different ways and with different content for the same purpose. Based upon a paper-centric process, email, phone, RFI’s This isn’t a process which can take advantage of BIM and automation. Current Business Processes

4. Developing the NBIM Standard Two Primary Activities Industry Experts Information Delivery Manual (IDM) Industry Experts Information Delivery Manual (IDM) Develop Project Summary Assemble Workgroup Develop IDM Submit for Consensus Review Update and ready for MVD development Software Implementers Model View Definition (MVD) Software Implementers Model View Definition (MVD) Create or reuse Information Concepts Develop Model View Definition Compare MVD to IDM Generate schema for software implementation Software Vendor Implementation Testing and Certification Focus of IDM

5. Workgroup Charge Define the area of interest (Example: BIM-GIS) Assemble Workgroup: The workgroup is composed of experts in the area/s of interest, the construction/lifecycle domain being considered, the current state of work – Additional support – IDM technical expertise, information technology applications and standards expertise, and process mapping exchange The context is defined through the use case and development of one or more process maps that identify where the exchanges take place in the project lifecycle and who are the actors and applications that are the senders and recipients of the exchange(s).

6. Architect Engineer An IDM is an Information Exchange Specification for BIM – Defines an industry user need – Based upon well defined processes with repeatable outcomes – Aimed at exchange of computer interpretable information – Uses a general method of development, but details are buildingSMART specific – Informs industry users of NBIMS capability and best practices Purpose of the IDM Activity

7. 7 A Conceptual Framework: Connecting IDM/MVD, Standards and Software Coherent framework for diverse but related models – RM-ODP - Reference model: Open Distributed Processing (ISO 10746-1) Enables separation of concerns to match stakeholders interests 2-way traceability from Business requirements to implementation Better control of development iterations Better business control of IT implementations and hence more business satisfaction RM-ODP does not replace IDM and MVD

8. 8 RM-ODP Viewpoints: IDM, MVD and Testing ComputationalComputational EnterpriseEnterprise TechnologyTechnology EngineeringEngineering The purpose, scope and policies for the community that will use the information system: business rules, requirements expressed as use cases Functional decomposition of the system into objects suitable for distribution Information handled by the system and constraints on the use and interpretation of that information: UML, Semantics Infrastructure required to support distribution System hardware & software elements Open System InformationInformation

9. Successful Communication In order to have a successful communication process All parties must know why the information is needed and for what outcome – The sending part must know what, when, and how information is to be delivered – The receiving part must know what to receive, when, what to do with it (outcome) and what to return – This requires mutual agreements on when the information is available, how it can be used and the expected level of detail

10. 10 ODP Viewpoints What the system is for organisational rules for how the package fits into the business How it works functionality as a set software components; inter-component and external communications, display services How to put it together Package name, system requirements Computational Enterprise Technology Engineering Open System What the system is about - things it understands – text, graphic, multi-media objects, fonts etc Information

11. IDM Has Three Parts A Business Use Case – Plain English Narrative The Process Maps – Show in BPNM the workflow and information exchanges The Information Exchange Requirements – Specific BIM-based and referenced information necessary for the exchange to meet the needs of the business use case

12. An IDM Information Exchange… An IDM Exchange Requirement defines: WHO is requesting information WHY in relation to a process or decision WHEN phase of a project or building lifecycle WHAT information is to be exchanged WHO is receiving the information HOW it is to be delivered and received This requires mutual agreements on when the information is available, how it can be used, and the expected level of detail Utilizes OmniClass to support activity

13. 1. An IDM Business Use Case Narrative The business use case is a narrative description of an industry process to be addressed in the IDM. The use case provides the scope, context, rationale, level of detail (LoD), and projected outcome for BIM use within a project or a building lifecycle activity. The working group scope defines the boundaries for the business use case.

14. The process model defines all of the required activities and sets them into a logical sequence. 14 page guide supporting Business Process Modeling Notation (BPMN) use in IDM creation 2. The IDM Process Map

15. OmniClass Phases Define Verticals OmniClass Disciplines Define Horizontal Swimlanes Exchange Requirement

16. 3. Information Exchange Requirements Defines the specific information to a BIM object, element level for the exchanges identified in the process map. Industry experts are required to understand the BIM integrated and related information needed for the process The requirements includes information, representation, and delivery. If the capability to manage delivery does not exist in BIM then a new software capability is defined.

17. ArchitectEngineerArchitectEngineer Information Delivery Manuals (IDM) are Use Cases and define Information Exchanges for BIM. The Information Delivery Manual is global and defines the sub-sets of information required for BIM-based exchange of information within a project team and throughout the building lifecycle. This information exchange between team members is based upon North American data standards & IFC OmniClass tables support WHO, WHY, WHEN, HOW, WHAT, and WHO of a Use Case Example BIM Use Cases Supported by Bsa IDMs RequestorProvider BIM Data MICROSOFT CORPORATION Information Exchange Agreement Space ValidationCosting SchedulingCOBie 3. Information Exchange Requirements

18. Aligns NBIMS Use Cases with BIM Data Developed by AEC Infosystems, Inc