1. IDBE Position statement Leif
Leif Granholm
Tekla / Trimble buildings
Senior Vice President / BIM Ambassador

2. Position statement Leif
Promote implementation and use of existing standards (IFC, xxxGML) in a non stovepipe fashion
Promote a “multi kernel” system archictecture where application code has direct access to standards based data without conversion, i.e. BIM softwares implement GeoSpatial standards and vice versa.
focus use case based on specific interoperability needs
Introduce new web technologies to facilitate interoperability (Semantic we, Linked Data, Web of Data)

3. Instance level linking
With instance level linking I mean that instead of creating rigid schemas (IFC, CityGML…) with fixed concepts and relationships between them, we use links to create relationships between any types or object instances in any data set.

4. Converting IFC models to Linked Data
Enable instance-level interoperability with cross-model linking implemented with Linked Data technologies
IFC
Linked Data
Identity
GUID
URI
Schema
EXPRESS
OWL
Data
Step File (Part21)
RDF
Access -
HTTP
Query language
SPARQL
Keep the most valuable part of IFC: the conceptual schema
Add modern, widely-used technologies

5. Principles of linking Links at two levels
Model-level links
Instance-level links
Linkset generation activities
Models is based on another  latter is used as a reference model to the former
Models share the same space  clash checking
Linksets at both ends
Links can be created by both parties
Maintain clear ownership of linksets
Public linksets
The links created by one party can often be utilized by another
Rich linksets
The original models are left untouched
Linksets should contain simple links, requests, acknowledgements, and conflicts
Independent linkset utilization
Linksets should be utilized independently by both parties
The impact of a change should be analyzed by both parties using their own expertize

6. Why RDF? – Linking at different levels
Native 1
Native 2
IFC 1
IFC 2
RDF 1
RDF 2
Links between native ids
- location
- access
- structure
Links between IFC GUIDs
+ structure
Links between URIs
+ location
+ access
Native 1
Native 2
IFC 1
IFC 2
RDF 1
RDF 2
Links between native ids
- location
- access
- structure
Links between IFC GUIDs
+ structure
Links between URIs
+ location
+ access
Native 1
Native 2
IFC 1
IFC 2
RDF 1
RDF 2
Links between native ids
- location
- access
- structure
Links between IFC GUIDs
+ structure
Links between URIs
+ location
+ access
Native 1
Native 2
IFC 1
IFC 2
RDF 1
RDF 2
Links between native ids
- location
- access
- structure
Links between IFC GUIDs
+ structure
Links between URIs
+ location
+ access

7. Emerging linked data of building and construction
Building and Construction Materials
Building Policies
Geographic data
Energy
Performance
of Buildings

8. Ambiguous modeling, different phases
Detailing
Engineering
Architectural
Leif Granholm

9. Reference model principle
Application capable of presenting and using native objects and objects in foreign schemas (IFC)simulaneously
Foreign information not bulk converted to native schema.
Native objects
IFC objects
(retained in IFC format)
Leif Granholm

10. Intra discipline workflow Intelligent object converter
Application functionality
-business logic
-create relationships
Leif Granholm

11. System architecture diagram
New Information consumption:
Mobile apps
Web apps
Machines, robots, drones etc.
New Information consumption:
Mobile apps
Web apps
Machines, robots, drones etc.
New Information consumption:
Mobile apps
Web apps
Machines, robots, drones etc.
New Information consumption:
Mobile apps
Web apps
Machines, robots, drones etc.
Open formats
IFC
CityGML
GML
KML
Publishing platform:
Trimble connect
AD 360
Nemetcheck BIM+
Bentley Projectwise
Publishing platform:
Trimble connect
AD 360
Nemetcheck BIM+
Bentley Projectwise …
Existing desktop applications
Existing desktop applications
Existing desktop applications
Existing desktop applications
Existing desktop applications
Existing desktop applications