Transcript Building SMART Alliance

Alliance NA
Developing an IDM
Information Delivery Manual
Part 1. Industry Workgroup Training, Creating IDMs
2010
Dianne Davis, NA-IDM Coordinator
Jan Karlshøj, International IDM Coordinator
Creating the National BIM Standard
•
•
•
•
•
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
Current Business Processes
• 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.
Developing the NBIM Standard
Two Primary Activities
Industry Experts
Software Implementers
Information Delivery Manual (IDM)
Model View Definition (MVD)
•
•
•
•
Develop Project Summary
Assemble Workgroup
Develop IDM
Submit for Consensus
Review
• Update and ready for MVD
development
Focus of
IDM
• Create or reuse Information
Concepts
• Develop Model View
Definition
• Compare MVD to IDM
• Generate schema for
software implementation
• Software Vendor
Implementation
• Testing and Certification
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).
Purpose of the IDM Activity
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
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
7
RM-ODP Viewpoints: IDM, MVD and Testing
Enterprise
The purpose, scope and policies for the
community that will use the information
system: business rules, requirements
expressed as use cases
Information
Information handled by the system
and constraints on the use and
interpretation of that information:
UML, Semantics
Technology
System hardware & software
elements
8
Computational
Open
System
Functional decomposition of the
system into objects suitable for
distribution
Engineering
Infrastructure required to support
distribution
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
What the system is for
organisational rules for how the
package fits into the business
What the system is about
- things it understands –
text, graphic, multi-media
objects, fonts etc
Enterprise
Computational
Information
Technology
How to put it together
Package name, system
requirements
10
Open
System
ODP Viewpoints
How it works
functionality as a set
software components;
inter-component and
external
communications,
display services
Engineering
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
An IDM Information Exchange…
An IDM Exchange Requirement defines:
MICROSOFT CORPORATION
Information Exchange
Agreement
Requestor
Provider
BIM Data
MICROSOFT CORPORATION
Information Exchange
Agreement
Requestor
Provider
BIM Data
MICROSOFT CORPORATION
Information Exchange
Agreement
Requestor
Provider
BIM Data
• 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
1. An IDM Business Use Case Narrative
MICROSOFT CORPORATION
Information Exchange
Agreement
Requestor
Provider
BIM Data
MICROSOFT CORPORATION
Information Exchange
Agreement
Requestor
Provider
BIM Data
MICROSOFT CORPORATION
Information Exchange
Agreement
Requestor
Provider
BIM Data
• 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.
2. The IDM Process Map
• 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
OmniClass Phases
Define Verticals
Exchange Requirement
OmniClass Disciplines Define
Horizontal Swimlanes
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.
3. Information Exchange Requirements
Example BIM Use Cases Supported by Bsa IDMs
MICROSOFT CORPORATION
MICROSOFT CORPORATION
Information Exchange
Agreement
Information Exchange
Agreement
Space Validation
Requestor
Costing
Provider
Requestor
Provider
BIM Data
BIM Data
Architect
•
•
MICROSOFT CORPORATION
MICROSOFT CORPORATION
Information Exchange
Agreement
Information Exchange
Agreement
COBie
Requestor
Scheduling
Provider
BIM Data
Requestor
Provider
BIM Data
•
Engineer
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
Aligns NBIMS Use Cases with BIM Data
Developed by AEC Infosystems, Inc