buildingSMART International
What is IDM and MVD
by
Bjørn K Stangeland
buildingSMART Norge medlemsmøte
25th September 2009
Multiple BIM authoring tools
Exchange/sharing between domains and within a domain
Electrical
domain
Architect/
Structural
(In reality separate domains)
HVAC
domain
Process:
Collision
detection
Thermal
domain
Courtesy: German IAI for Building Services
IDM – Information Delivery Manual
Process Map (PM)
Task I (Software A) - produce
Task II (Software B + C) - consume
Courtesy: Lars C Christensen
PM and ER’s
Skills needed to define (and understand) Process Maps and Exchange
Requirements (ER’s): Domain Expert (not IFC experts and software engineers!)
Task II (Software B + C) - consume
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)
Courtesy: Dianne Davis, AEC Infosystems
Example: Energy simulation
Building Envelope ER
Building Usage ER
(Thermal loads, schedules etc.)
(Requirements like U-values, space
boundaries etc.)
Task II (Software B + C) - consume
Process Map (PM)
Weather data ER
(When does exchange of which
information between processes need to
occur and why?)
(In format Xyz ….)
MVD – Model View Definition
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)
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