buildingSMART International What is IDM and MVD by Bjørn K Stangeland buildingSMART Norge medlemsmøte 25 th September 2009

2 Multiple BIM authoring tools Exchange/sharing between domains and within a domain Architect/ Structural (In reality separate domains) Electrical domain Thermal domain HVAC domain Process: Collision detection Courtesy: German IAI for Building Services

IDM – Information Delivery Manual Courtesy: Lars C Christensen Process Map (PM) Task I (Software A) - produce Task II (Software B + C) - consume Exchange Requirements(ER)

PM and ER’s Task II (Software B + C) - consume Skills needed to define (and understand) Process Maps and Exchange Requirements (ER’s): Domain Expert (not IFC experts and software engineers!) Courtesy: Dianne Davis, AEC Infosystems What information (the I in BIM) do person A need from person B - and when - to do a specific task. Define the “task“ and “why/when” the exchange is to occur: PM What information do I need (mandatory) and what would I like to have if I could get it (and what does I not want)

Example: Energy simulation Process Map (PM) (When does exchange of which information between processes need to occur and why?) Task II (Software B + C) - consume Weather data ER (In format Xyz ….) Building Envelope ER (Requirements like U-values, space boundaries etc.) Building Usage ER (Thermal loads, schedules etc.)

Where to in the IFC schema (binding) can we find the relevant entities to use to support ER’s this “type” of process. For the TECHNICAL people (developers) MVD – Model View Definition What information that’s mandatory and optional (and unwanted) is defined in the Exchange Requirement(s)!! MVD has the scope of identifying what is relevant between “applications types”. Where information defined in multiple ER’s may found be in the same MVD. Typical: Early stage and detailed designed building envelope for energy analysis

“ The optimist proclaims that we live in the best of all possible worlds, and the pessimist fears this is true” James Branch Cabell