Information Delivery Manual

THIS
IS
OUR
TEAM
Ahmed Gamal Abdel
Gawad Aboulmaaty
AHMED
GAMAL
Marwa Mohamed
Abdalla
MARWA
MOHAMED
👪Abdelrahman Fathy
Abdelhalim Aly
A.RAHMAN
FATHY
Ibrahim Mohamed
Ibrahim Saad
IBRAHIM
MOHAMED
2

3
IDM OVERVIEW
01
PROCESS MAPS & ER
02
IDM vs MVD
03
IDM/MVD DEVELOPMENT
04

buildingSMART
STANDARDS
6
▸ buildingSMART standards,
as the most important part
of openBIM standards,
mainly includes five basic
standards.

buildingSMART
STANDARDS
7
▸ The names and functions of these five basic standards are
briefly summarized one by one in Table

Data, Information &
Knowledge
9
▸ Data is a set of representation of
plain and raw facts.
▸ Information is a data with meaningful
messages, or data after processing.
▸ Knowledge is information processed
in the mind of individual that can be
gathered through experience or
study.

▸ The formal method developed and propagated
by buildingSMART to establish Model View
Definitions as a standard requirement for
exchanging model data within the construction
industry.
10
What Is IDM?

▸ IDM is an ISO standard intended to "facilitate
interoperability between software applications
used in the construction process, to promote
digital collaboration between actors in the
construction process and to provide a basis for
accurate, reliable, repeatable and high-quality
information exchange" (ISO 29481-1:2010)
11
What Is IDM?

▸ It is necessary for all participants in the
organization to know which and when different
kind of information has to be communicated.
The issue is even more important when digital
tools are applied, since most industry tools
have a very low threshold of tolerance when it
comes to the ability to interpret digital data.
12
Why IDM?

▸ It is important to state that in order to make an
information delivery manual operational it has
to be supported by software. The main purpose
of an information delivery manual is to make
sure that the relevant data are communicate in
such a way they can be interpreted by the
software at the receiving side.
13
Why IDM?

▸ According to NBIMS, the “aim of the
Information Delivery Manual (IDM)
(buildingSMART Processes) and
Model View Definition (MVD) is to
specify exactly which information is
to be exchanged in each exchange
scenario and how to relate it to the
IFC model."
14
Why IDM?

It will specify:
▸ Where a process fits and why it is
relevant.
▸ Who are the actors creating,
consuming and benefitting from
the information.
15
Why IDM?

It will specify:
▸ What is the information created and
consumed.
▸ How the information should be
supported by software solutions.
16
Why IDM?

▸ Doing this will make IFC more closely
reflect real project needs and
accelerate the use of BIM in real
projects. It will also help to realize
integrated project information as the
key driver to the process improvement
set as a goal for the AEC/FM industry
by many industry commentators.
17
Why IDM?

▸ The IDM benefits both BIM users and
software solution providers.
▸ Solution providers and software users
means need to know which IFC
components are important for their
purpose.
18
IDM Benefits

▸ Software users need to know so that they
can be sure that IFC meets their needs.
▸ It provides an easy to understand, plain
language description of building
construction processes, the requirements
for information to be provided to enable
processes to be carried out successfully
and the expected end results of the
processes.
19
IDM for BIM Users

This will help to:
▸ Make information exchange between
project participants more reliable.
▸ Improve information quality.
▸ Improve decision making.
▸ Do a BIM project far more effectively.
20
IDM for BIM Users

▸ Solution providers need to know to make
sure they implement the right components
AND meet the needs of their users
▸ It identifies and describes the detailed
functional breakdown of processes and the
IFC capabilities needing to be supported for
each functional part in terms.
21
IDM for BIM
Solution Providers

This will help to:
▸ Respond better to user needs.
▸ Guarantee quality of information exchange .
22
IDM for BIM
Solution Providers

IDM — Process Standard
23
▸ IDM is a method for capturing and
specifying the whole process and
information flow during building life
cycle, which aims to ensure relevant
data is exchanged in a way that can
be interpreted by the recipient
software.

24
▸ The construction and maintenance of
buildings involves many different
participants, knowing what
information needs to be
communicated among them and
when it is communicated is
important.

25
▸ IDM can facilitate this information
communication process by making
full use of business process
modelling notation (BPMN) and
templates for Exchange
Requirements

Requirement & Goal
▸ Standardize on information needed for
specific tasks within the building lifecycle.
▸ Development based upon open data
standards used by all.
▸ Provides requirements to software
companies.
26
IDM — Requirements & Goal

To improve the construction process:
▸ Information must be available when it is
needed.
▸ Quality of information needs to be
appropriate.
27
IDM — Improving the
Construction Process

Process Map
29
▸ Defines all of the required
activities and sets them into
a logical sequence.
▸ The connection between
exchange requirements and
a business process is
captured within a 'process
map‘.

Process Map
30
▸ Describes the flow of
activities for a particular
business process.
▸ Enables understanding of
the configuration of
activities that make it work,
the actors involved, the
information required,
consumed and produced.

Exchange Requirement
31
▸ A set of information that
needs to be exchanged to
support a particular
business requirement at a
particular stage of a project.
▸ Provides a description of the
information in non technical
terms.

32
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.

33
An IDM Exchange Requirement
defines:
▸ WHAT information is to be
exchanged.
▸ WHO is receiving the
information.
▸ HOW it is to be delivered and
received.

34
▸ This requires mutual
agreements on when the
information is available, how
it can be used, and the
expected level of detail.

35
▸ 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.

Functional Part
36
▸ A unit of information, or a
single information idea,
used by solution providers
to support an exchange
requirement.
▸ A functional part is a
complete schema in its own
right as well as being a
subset of the full standard
on which it is based.

Business Case (Rules)
37
▸ The business use case is a
narrative description of an
industry process to be
addressed in the IDM.

38
▸ 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.

39
▸ Constraints that may be
applied to a set of data used
within a particular process.
▸ Used to vary the result of
using a schema without
having to change the
schema itself e.g. localizing
an international standard.

Verification Tests
40
▸ Testing software to verify
the accuracy of their
support for exchange
requirements.

2
PROCESS MAPS
& EXCHANGE
REQUIREMENTS

43
▸ IDM Process Mapping
o Definition & Importance
o Process Map objects
o Process Map report
▸ IDM Exchange Requirements
o Definition & components
o Example: Detailed Exchange Requirements for
bridges
Preview

44
o It defines the (tasks) activities that exist within a business process, and sets them
into a logical sequence.
o This sequence is driven by the dependency of one process on the information that
is provided to it by one or more other processes.
o It is NOT time based and should not be confused with scheduling of tasks as may be
represented in a GANTT chart or PERT diagram.
o Identify the exchange requirements that support the activities within the process.
What is a Process map?

45
o The start and end events in the business process.
o Events at which information exchange occurs
o Decisions in the business process.
What is a Process map?
(It identifies)

47
Structural
Engineer
A Pool represents a Participant in a
Process.
It is also acts as a graphical
container for a set of processes
performed by the participant that
can be described in sequence.
1) Actors
StructuralEngineer
Steelstr.
Designer
Claddingstr.
Designer
A Lane is a partition within a Pool
that extends over its entire
length. Lanes are used to
organize processes.
Representing sub-actors or
departments of an organization.
Process Map Components

48
2.1) Processes
Processes may be either ‘compound’ meaning
that they can be broken down further into
smaller sub-processes or ‘atomic’ meaning that
further breakdown is not possible.
Design
Columns
Design
rafters
Design
bracing
mem.
Design
Footings
Design Built-
Up Sections
Atomic process
Design
Sections
+
collapsed process
expanded process

2.2) Process Markers

50
3) Connections
Architectural
Engineer
StructuralEngineer
preliminary
Structural system
optimization
Preliminary
Design
Final
Design1. Sequence
flow
(Defined for a single actor, can be
used across lanes but not across
pools, defines workflow for an actor)
X
2. Message Flow
(Defined between actors, used to
pass a message or info)

51
Architectural
Engineer
StructuralEngineer
preliminary
Structural system
optimization
Preliminary
Design
Final
Design
Architectural
Concept 3. Association
connection
1
3) Connections

4) Artefacts
Data Objects
1
Exchange
Requirements
Ex: Code Regulations
Ex: er_exchange_space_model
[sketch]
Relevant information needed
between two or more processes.
General information needed that
isn’t considered as an ER.
52

5.1) Events
53
An event is
something that
“happens” during the
course of a business
process.

5.2) Event triggers
54

55
5.2) Event triggers

6.1) Gateways
56
A Gateway is used to control the divergence and convergence of Sequence Flow.

6.2) Gateways
57
e.g. Precast or in-
situ? based on
district rules book for
site occupation.
e.g. design
alternatives based on
data from arch.

6.2) Gateways

Exercise

Exercise
• At which stage of BIM do we
have asset management?
• What is meant by routing &
permitting?
• Why the asset manger is
producing two different ER
(Retrofit & GIS models)?

1) Header Section
2) Specification of Processes
3) Specification of Data Objects
4) Specification of Exchange
Requirements
Process Map Report

5) Specification of Coordination Point
Gateways
6) Diagrams & mapping
Process Map Report

63
o An exchange requirement represents the connection between process and data.
IFC
What is an Exchange
Requirement (ER) ?

64
Form/template
IFC

65
Form/template
IFC

66
ER Form/template
(Functional Part)
IFC

67
ER Form/template
(Functional Part)
IFC

68
Example: ifcBridge
ER template
Process PartData Model
+o An exchange
requirement represents
the connection between
process and data.

69
Example: ifcBridge
Different models
for different
Exchange
requirements.

Example: ifcBridge
01-01 Site
71

72
Example: ifcBridge
03-01 Span

73
Example: ifcBridge
06-01 Abutment

74
Exchange
Requirement
Example 2:
Exchange
Requirements for
Road Design to
QTO (Calculation)

75
Example 2: Exchange Requirements for Road Design to QTO (Calculation)

76

77

Integrated Process
Overview
79

Overview of the
IDM/MVD Method
81

Exchange Requirements
Model
85

Model View
Definition (MVD)
86
▸ Model View Definitions are subsets of the
IFC Model Specification.
▸ MVD provides the specification for IFC
based data exchange implementation.

Concepts
88
▸ Concepts are independent from any IFC Model View Definition.
▸ IFC Model View Definition is created by choosing (or defining) a group of
concepts and defining their relationships.
▸ In our integrated IDM-MVD process Exchange/Generic/General
Concepts (independent of IFC) are color-coded with blue and MVD
Concepts (bound to an IFC schema) with orange.
▸ Blue concepts should be separate from Orange concepts to allow reuse
of Blue concepts if the underlying IFC model specification changes.

MVD Concepts
89
▸ Reusable definitions of commonly useful packages of information are
identified in the Exchange Requirements Model as Exchange Concepts.
▸ The technical solution for exchanging them in software (bound to IFC
model entities) is MVD Concepts.
▸ Avoid overly fine-grained production of views at an attribute level.
▸ Modularize MVD and allow for their reusability and testing.

2-MVD Diagrams
102
▸ MVD diagram defines the scope of data to be exchanged about a top level
‘Variable Concept’.
▸ MVD Concepts define a way to realize the Exchange Concept in software
data exchange.
▸ The top level concepts generally correspond between ERM and MVD
diagrams, but occasionally some additional top-level concepts may be
introduced in the MVD for software implementation purposes.
▸ For each Exchange Concept in the ERM, there will be one or more MVD
concepts which define a way to exchange the data defined in that concept
in software.
▸ MVD diagrams are targeted at software developers, especially people
writing software code.

Implementation Guidance of
Concepts
107

3.2-MVD Concept
Description
111

Large Concepts vs
Small Concepts
119
▸ For software users the capabilities of IFC implementations are
easier to understand if static concepts have a large scope.
▸ For implementations large concepts can be problematic
because even software created for the same purpose is very
different and a large concept may be discriminating.

IDM/MVD
INTEGRATED
DEVELOPMENT
4

▸ Phase 1: IDM Development
▸ Phase 2: MVD Development
▸ Phase 3: Software Implementation/Certification
▸ Phase 4: Deployment and BIM Validation
124
IDM/MVD Development

Model view definition primarily is created
to support software developers in terms
of what portion of the IFC schema is
required to be implemented in their
software.
One of the deliverables of the MVD
development process is the mvdXML files.
125
MVD Development

mvdXML
It is an XML format used to publish the concepts and associated rules of
an MVD in computer-interpretable way.
126

Importance of mvdXML
▸ Support automated validation of IFC data sets for BIM validation and
software certification.
▸ Generate documentation for specific model views and the IFC
specification itself.
▸ Support software vendors providing filtering of IFC data based on model
views.
127

mvdXML Structure
mvdXML is the only single valid root element. The mvdXML element defines
two main sub elements:
▸ Templates: a list of reusable concept templates; ConceptTemplate.
▸ Views: a list of model view definitions; ModelView.
128

mvdXML Structure
ConceptTemplate defines a query-like graph, starting from an applicable root
entity, following attribute and entity links, down to the individual attributes,
which contains all schema information for a particular unit of functionality
130

mvdXML Structure
ConceptTemplate starts with its applicable entity the root of this unit
of functionality then the attribute(s) used for expressing the unit of
functionality are declared, then the type of the attribute, in case of an
entity type, it can have own attribute definitions again.
131

mvdXML Structure
ModelView element describes how the Concept Templates are
used in a View. The Roots element contains a list of
ConceptRoots.
133

mvdXML Structure
ConceptRoot references a specific IFC entity, e.g. IfcSite with the
attribute applicableRootEntity. And also implements one or many
ConceptTemplate.
134

mvdXML Structure
The Concepts element contains the concepts specified for a certain
ConceptRoot, each Concept has a mandatory reference a
ConceptTemplate.
135

mvdXML Structure
▸ Every Concept refers to a ConceptTemplate as its basic structure.
▸ The purpose of splitting Concept Templates from Concept usages is you
can define a generic concept by defining a template and apply it to
different scenarios.
136

mvdXML Structure
A Concept also has a tree of logical expressions. Individual TemplateRule
are grouped under a TemplateRules element and are logically interpreted
by the @operator attribute.
138

mvdXML Structure
A TemplateRule represents an instantiation of a rule with specified
parameters. The @RuleID used in the Parameters of the template rule
serves as a reference to the @RuleID of an AttributeRule or EntityRule at
the referenced ConceptTemplate.
139

mvdXML Structure
Parameters attribute is a string that defines the constraints applied on the
referenced AttributeRule and takes the form “{RuleID[metric]}={Value}” .
each expression can be grouped and combined through AND, OR and XOR
logic.
140

mvdXML Development
using IfcDoc
The IfcDoc tool was developed by
buildingSMART International to
improve the consistent and
computer-interpretable definition of
Model View Definitions (MVD) as true
subsets of the IFC Specification with
enhanced definition of concepts.
141

Software Certification
▸ The “IFC Certification 3.0” describes the certification of IFC
interfaces for software products using the IFC schema. It is based
on a new cloud-documentation platform known as the “b-Cert
platform”.
▸ The MVD implemented by the software must be accepted by the
standardization process of bSI before certification starts.
143

Software Certification
Before mvdXML certification testing was based on
combination of :
- MVD Diagrams XML
- Concept level Implementation Guidance documents
- Business Rules.
144

b-Cert Certification Process
▸ MVD specific certification.
▸ Type of certification: import/export.
▸ Certificate and Logo
145

Export:
Test files are created based on test
instructions that are provided by the
Software Certification (SC) team.
Software developers are set to create
the export test case within their own
applications. The created IFC export
files are then uploaded to the
certification platform and validated
both automatically and manually.
146

Import:
Calibration files are provided as pre-
validated IFC files by the certification
team. The participating software
developers import them into their
applications, checks for the expected
results and fill out manual check items.
147

BIM Validation
An important aspect of success in the deployment phase is the
availability of third party BIM Data Validation services. These will
enable end users to upload building models and validate
conformance to requirements in a selected IDM/MVD.
In order to check models, text-based requirements and rules
have to be converted to computer-executable rule-sets.
148

Validation Approaches
▸ Programming
Methods
▸ Schema-based
Methods
149

Programming Methods
Hard-coding rules into high-level
imperative programming languages
such as C++ and Java is currently the
most widely used approach for
checking models that is also commonly
implemented in commercial checking
platforms. The Solibri Model Checker
(SMC) .
150

Schema-based Methods
The EXPRESS language provides schema-level
constraint mechanisms such as WHERE and UNIQUE
rules to restrict instance models.
However EXPRESS is not actually popular languages
even among software engineers.
151

mvdXML-based Validation
▸ All the previous methods cannot provide an open and low-cost rule checking
environments. MvdXML is currently the only open standard dedicated for
model view definition and IFC validation.
152

mvdXML-based Validation
▸ IfcDoc
▸ XbimXplorer
▸ simpleBIM
153

Research Efforts
▸ IDM/MVD Modularity
▸ MVD Generation
▸ MVD Readability
▸ MVD Validation Algorithm
154

IDM Configurator
Yonsei University
IDMs and MVDs are hard to share and modify for reuse.
The goal of the IDM configurator is to provide an integrated environment that links
various individual software applications to enable users to develop, share, and reuse
BEPs, EIRs, IDMs, and MVDs.
155

MVDLite
156
A Light-weight Representation of Model View Definition with Fast Validation for BIM Applications
In mvdXML, MVD validation algorithms all have similar implementations based on
graph traversal:
▸ For each rule, finding the root entity set.
▸ Taking one root entity each time, and expanding the root entity to find all the
subgraphs that match a ConceptTemplate structure.
▸ Checking all subgraphs to find whether there exists a subgraph that satisfies
the rule statement.

MVDLite
157
Usually, the IFC model of a real project typically exceeds millions of nodes, with
hundreds of megabytes of data. The efficiency of graph-traversal-based MVD
validation on large scale models is problematic.

MVDLite
158

MVDLite
159

160
▸ Information Delivery Manuals: General Overview
https://slideplayer.com/slide/5769904/
▸ Developing an IDM Information Delivery Manual, Part 1. Industry Workgroup
Training, Creating IDMs
https://slideplayer.com/slide/10435745/
▸ OpenBIM: An Enabling Solution for Information Interoperability
https://www.mdpi.com/2076-3417/9/24/5358
▸ EPISODE 24: UNDERSTANDING MODEL USES, BIMThinkSpace.com
https://www.bimthinkspace.com/2015/09/episode-24-understanding-
model-uses.html
▸ BIMDictionary.com
https://bimdictionary.com/
▸ Information Delivery Manual (IDM), theBIMhub.com
https://thebimhub.com/2013/10/25/information-delivery-manual-
idm/#.Xg9YuUczbIU
References (IDM Overview) 📖

161
▸ THE IFC-BRIDGE PROJECT–André Borrmann1, et al- European Conference
on Computing in Construction- July 2019
▸ BIM Guideline- Detailed Exchange Requirements- SeeBridge project, by
Burcu Esen Barutcu. 2017.
▸ Information Delivery Manual-Guide to Components and Development
Methods-building SMART.2010
▸ Quick Guide to Business Process Modeling Notation (BPMN) 2007
References (Process Maps & ER) 📖

162
▸ Building Information Modeling Technology Foundations and Industry
Practice (Chapter 6: Process-Based Definition of Model Content) - Andre
Bormann, Markus Konig, Christian Koch & Jakob Beets Eds.
▸ https://www.blis-project.org/IAI-MVD/
▸ “An Integrated Process for Delivering IFC Based Data Exchange” by:
buildingSMART International , BLIS Consortium/Richard See,
buildingSMART international/Jan Karlshoej , buildingSMART alliance/
Dianne Davis.
References (IDM vs MVD) 📖

163
▸ Building Information Modeling Technology Foundations and Industry Practice (Chapter
5) - Andre Bormann, Markus Konig, Christian Koch & Jakob Beets Eds.
▸ Advances in Informatics and Computing in Civil and Construction Engineering, Ivan
Mutis and Timo Hartmann, Proceedings of the 35th CIB W78 2018 Conference: IT in
Design, Construction, and Management
▸ https://technical.buildingsmart.org/standards/mvd/mvdxml/
▸ https://www.buildingsmart.org/standards/bsi-standards/information-delivery-
manual/
▸ https://www.researchgate.net/publication/271823060_Interoperable_validation_for_I
FC_building_models_using_open_standards
▸ https://technical.buildingsmart.org/resources/ifcdoc/
▸ https://github.com/buildingSMART/IfcDoc/wiki/IfcDoc-User-Guide
▸ https://www.researchgate.net/publication/332826128_Information_Delivery_Manual_
IDM_Configurator_Previous_Efforts_and_Future_Work
▸ https://deepai.org/publication/mvdlite-a-light-weight-representation-of-model-
view-definition-with-fast-validation-for-bim-applications
References (Integrated Development) 📖

164
THANKS!
Any questions?
You can find us at LinkedIn:
linkedin.com/in/aGaabdelgawad/
linkedin.com/in/abdelrahman-fathe-192025151
linkedin.com/in/ibrahim5aad
linkedin.com/in/marwa-ebeid-7a2394140
😉
and many more...

Information Delivery Manual

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Information Delivery Manual

Similaire à Information Delivery Manual (20)

Plus de Ahmed Gamal Abdel Gawad

Plus de Ahmed Gamal Abdel Gawad (15)

Dernier

Dernier (20)

Information Delivery Manual