Presentation by Leif Granholm

1. What is BIM?
1

2. BIM Graphics to objects och geometry
Drawings are graphics (appearance important)
A BIM consists of objects
that may contain geometry
and/or attributes
(structure important)
2

3. BIM – From Modeling to Management
Objects describing building
Functional objects Physical objects Logical objects Abstract objects
Objects describing process
• Schedules • Work
• Resources • Approvals
• Costs • RFI:s
• Quality assurance • Submittals
• Tasks • …
DRUM - Distributed information management

4. BIM is about sharing structured data
[Date]
4

5. BIM today
5

6. BIM today
Mostly Lone BIM, models used to produce documents
and Visualizations
Information flow in process document based (electronic
or paper)
Contracts based on documents
Models transferred between parties on an ad-hoc basis,
as support for documents.
Transfer of models file based, native proprietary format
(DGN, RVT, DWG…) or standard format (IFC)
No established collaboration workflows
[Date]
6

7. BIM today
Disciplin specific models
– Architectural (masses, spaces, building parts, doors, windows,
interior finishing) Revit, ArchiCAD, Bentley Archtecture,
Vectorworks, Allplan)
– Structural (load bearing structures, foundations, piling,
cladding…) Tekla Structures, Revit Structure, Bentley Structure
– Mechanical (Electrical, Piping, Ventilation, Heating…) Tevit MEP,
Magicad, DDS, CADDuct, QuickPEN
Phase specific models (design, detailing, fabrication,
erection)
[Date]
7

8. Architectural model
[Date]
8

9. Structural Model
[Date]
9

10. Mechanical model
[Date]
10

11. Mechanical model
[Date]
11

12. BIM and openBIM adoptation
BIM
openBIM
Dynavoice Magic Sub-8
The Building Information Modelling Summit

13. Model based collaboration
13

14. Model based collaboration today, applications
Clash detection
Coordination
Energy calculations
Quantities
Model viewing complementing drawings
Quality control/rule checking
[Date]
14

15. Model based collaboration today, methods
Transfer of models between parties mainly file based
– Native formats (DWG, RVT, DGN…)
– Standardized open format (IFC)
Some model server based solutions (EPM, Eurostep)
Content of files not established or well defined
Work in progress to define IDM:s (Information delivery
manuals) and MVD:s (model view definitions) by
buildingSMART and others
[Date]
15

16. Model based collaboration today, methods
Varying methods for export
– Sharing directly same files as author is using for production
– Using manual export from native files
– Manual selection of exported objects
– Manual setting of conversion rules (layers, object type selection,
presentation etc)
– Using macros or plugins to do the above
– Server of service based solutions
Two main methods in receiving files
– Converting files to native objects when reading
– Retaining files in original format for use as reference (reference
model principle) [Date]
16

17. Integrating models
17

18. Integrating models
Using same software functionality on information from
different disciplines and softwares
Applications
– Viewing, understanding the project
– Clash detection
– Coordination
– Construction management
– Scheduling
– Quantities
– Safety planning, temporary structures
[Date]
18

19. Several SW applications available
Both functionalities in discipline specific softwares and
special softwares
Autodesk Navisworks
Solibri
Bentley ProjectWise/ISM/Navigator
Tekla BIMsight
Large number of smaller local applications
[Date]
19

20. Approaches to integration
Two main approaches
– Software capable of opening native files
– Export of native information using standard formats (IFC)
Most softwares use both approaches
– Native primary: Navisworks, Bentley
– Standard primary: Solibri, Tekla BIMsight
[Date]
20

21. Clash Detection
Using software functionality and (solid)geometry to detect
where objects collide
Detecting Hard clashes and soft clashes
– Hard means actual static geometry of objects clash (occupy
same space
– Soft clash means the objects are too close to each other for
installation, operation or maintenance, also called clearance
clash
[Date]
21

22. Clash detection in practice
Three phases
– Preparation, selecting objects/models to check and specifying
rules
– Performing the actual geometrical check
– Processing and managing found clashes
Early clash detection functions only for hard clashes
– In manually coordinated/uncoordinated projects typically tens of
thousands found
Today more elaborate functions to specify rules
Future of clash checking more proactive role as part of
model based coordination
[Date]
22

23. Model based coordination future Example –
Penetration Request
Mechanical designer and
structural designer can
see their local and all
foreign models
– MEP local + Structural IFC
– Structural local + MEP IFC
Penetration request
– MEP designer creates
request = reservation object
+ status information
– Structural designer approves
request and creates
penetration with reservation
object
Process
– Requests transferred
between designers
separately from Mechanical
or structural model
– Approvals of penetrations
– Changes after approvals

24. buildingSMART
24

25. buildingSMART
International standardization organization
Owns and develops the IFC standard
Works for interoperability between different software
applications in Construction industry (OpenBIM)
Tekla participates very actively
25

27. Three buildingSMART Standards
BIM is about sharing structured data.
• IFC – “Information for Construction” ISO/PAS 16739-2005
– Includes designs, processes, resources, participants.
– IFC STEP files and IFC XML files define portable file structures.
• IDM – “Information Delivery Manuals” ISO/FDIS 29491-1:2009
– How specific required information exchanges can be documented.
• IFD – “International Framework Dictionary” ISO 12006-3:2007
– Catalogues terms and concepts.
– Includes multiple languages

28. IFC… Electrical Elements
transformers, motors, generators,
switches, protective devices,
Shape (explicit) power and communication outlets
panels, cubicles
Sanitary Elements
Shape (extrusions) WC’s, urinals, baths, bidets, traps
beams, pipes, ducts, walls etc. gulleys
Shape (topology)
line representations for pipe, duct, etc. Fire Protection Elements
sprinklers, hose reels, hydrants,
wet/dry rising mains
Building Elements
wall, door, window, roof, stairs, etc.
Furniture
inc. system furniture
HVAC Equipment
chillers, fans, pumps, boilers,
Relations Between Elements
coils, cooling towers, heaters, holes, chases, voids, zones
heat exchangers, etc..
Structural analysis:
Spaces, Space Structure structural members, boundary
space, storey, part, building, site conditions, connections, supports,
loads, etc.

29. Controls, Instruments
… and … sensor, actuator, controller,
gauge, meter
Systems
piping, ducting, cable, structural
Grids
Lighting
fittings, rendering, photo-
accurate Draughting
lighting
Manholes
manholes, inspection chambers,
Holes and Bases
access chambers, meter chambers,
holes, sleeves, packing, framing,
valve chambers
upstands, vibration isolation
Time Series Accessories
time related events
brackets, drop rods, steel sections,
bracket assemblies, screws, bolts etc.
Constraints
rules, specifications, requirements Pump Set
[Physical
Association]
Luminaires
[Spatial Association]
trigger conditions Asset Management Boiler
Preheater
Valves
maintenance history, inventories Air Handli ng Unit
Environmental Impact
embodied energy, CO2

30. …and 30
Actors Geographical Elements
people, organizations, addresses Name
Tit le
Name
Title
features, contours, regions
Na me Name Name
Title Tit le Ti tle
Costing
cost planning, estimates, budgets,
Na me
Tit le
Name
Ti tle
Na me
Title
Name
Tit le
Coordinate Mapping
whole life geodetic, cartesian
Help
Work Plans and Schedules request, action, permit, warranty,
inc. nested schedules, resource allocation operation
Orders Zones, Compartments
work orders, change orders, fire, workstation, rising ducts,
purchase orders shafts
External Data Structural Elements
members, profiles, rebars,
OCCS properties,
joints, features, surface
Classification
Uniclass
Connectivity
Associated Documents services, structure, building

31. BIM system architecture
31

32. Current Centralized Concept
Downstream
application
data
transform
ation Downstream
application
Authoring Basic assumptions:
software
• IFC based model server is
“Master”.
IFC model instance • IFC model is basically one
logical model created and
updated by several
applications.
• Any application can
technically read and write
any data.
Authoring
software DRUM - Distributed information management

33. New OpenBIM Concept
Native data
(Master)
Native data
(Master)
BIM software
BIM software
Basic assumptions:
• Master data in applications
The ”Cloud” (native proprietary format)
• Applications publish a part of their
data as IFC
• Only the application that has
created and owns data can
change it No roundtrip
Native data • IFC model is a collection
(Master) (combination) of discipline
BIM software specific models that coexist
throughout the project management
DRUM - Distributed information

34. Actual BIM model structure
Architectural Structural MEP design
spaces general design
MEP
Architectural Structural fabrication
building parts in situ concrete
detailing MEP
Architectural production
detailing Structural
precast
Architectural concrete det.
production
Structural
steel detailing
[Date]
Structural Models coexist throughout the Project
site production 34

35. OpenBIM Concept Client
Each participating client
is one instance of logical
database in specific BIM
BIM BIM software
User User
Native multiuser
functionality between BIM
users of one system
(client) with fully shared
information (roundtrip),
also across organizations
Native data
(Master)
Two level collaboration,
BIM software
tight (roundtrip)
integration within one
logical model, loose (no
roundtrip) integration
BIM BIM between clients
User User
DRUM - Distributed information management

36. ”Cloud” functionality
Transaction based communication
– Subscribing to published IFC datasets with incremental updates
– Any client can subscribe to any data published by another
application
– Current situation transferred initially and after that changes only, as
they are published
– Workflow type of action transactions with (semi)automatic routing
– F.ex MEP engineer needs penetrations through structures and
requests these from architect and/or structural engineer
Managing and publishing metadata of and from
participating models
Creating, managing and publishing relationships between
objects in the participating models
DRUM - Distributed information management

37. DRUM project
Native data
(Master)
Native data
(Master)
BIM software
BIM software
DRUM aim:
• Perform research and create
The ”Cloud” foundation to define standard for
interface between “Cloud” and
clients
• Standard creates markets for
“Cloud” functionality
Native data implementations and Client
(Master)
functionality
BIM software
DRUM - Distributed information management

38. DRUM - Transaction based information sharing and distributed
information management
Budget 2 M€
Industrial Parties:
– Tekla (leader)
– Skanska
– Solibri
– Progman (MagiCAD)
– Logica (ERP)
– MAP (ArchiCAD dealer)
Research parties
– Aalto university
– Georgia Tech
BuildingSMART International Conference 2011
Integrated Construction for Sustainable Build

39. DRUM - Transaction based information sharing
and distributed information management
Original project idea:
Create ”GSM” (Mobile network) for
construction industry
BuildingSMART International Conference 2011
Integrated Construction for Sustainable Build

40. Thank You!