LOC presentation 2020: Future of openBIM standards

The next generation of open data
standards in construction
Léon van Berlo
Leon.vanBerlo@buildingSMART.org
+31 6 423 674 65
©2020 buildingSMART International, Ltd., All Rights Reserved

What are standards?
What kind of standards do we have?

Digitalization of paper documents
Doing the same, but digital
02
03
04
01
PDF, ZIP,
etc

Syntactical interoperability
Making sure documents can be read by computers,
but computers don’t really understand what is in them.
02
03
04
01
PDF, ZIP,
etc
HTML, PDTs,
XML, JSON,
etc

Semantic interoperability
and computers understand the content.
02
03
04
01
PDF, ZIP,
etc
HTML, PDTs,
XML, JSON,
etc
IFC, BCF,
ETIM,
Uniclass, etc

Linked Semantic Data
Linking and creating relations between semantic data
definitions over multiple domains
02
03
04
01
OWL, OTL,
bSDD
PDF, ZIP,
etc
HTML, PDTs,
XML, JSON,
etc
IFC, BCF,
ETIM,
Uniclass, etc

02
03
04
01

Data standards &
agreements

Data standards &
agreements
Communicating about
the data
(process)
Access to
the data
(APIs)

Information
Delivery
Specification
BCF Topics
Data standards &
agreements
Communicating about
the data
bSDD API
openCDE API
File serialisations
(json, RDF, xml, spf)
…….
Access to
the data
(APIs)

Information
Delivery
Specification
BCF Topics
Common & Integrating parts:
Common API
Query language
Quality assurance
Deployment Tools
bSDD API
openCDE API
BCF API
File serialisations
(json, RDF, xml, spff, etc)

buildingSMART technical roadmap
• Usability
• Predictability
• Reliability

buildingSMART technical roadmap
• Usability
• Predictability
• Reliability
• Transparency
• Traceability

Desired situation
• One interoperable IFC
• Multiple file serializations
• Filtering / querying (partial data sets)
• API access
• Extendable
• Multi domain interoperability “by design”
• Ecosystem
• Validation tools
• Meta standards (IDS, BCF, etc)
• Certification that provides guarantees

Desired situation
• Predictable development
• Transparent, traceable
• Standards roadmap (for example: “10 principles of IFC”)
• Automated & transparent quality assurance
• Low threshold for implementation (mainstream modelling techniques, high quality documentation, etc)
• Semantic harmonisation / connection
• With bSDD
• With national / use-case specific standards
• With other domains (Geo)
•  bSDD

Example topics
• Use-case based implementations  generic IFC implementations
• Demarcated files  open ended datasets (extendable)
• Strong link to STEP/EXPRESS  generic modelling techniques
• Growing monolithic agreement  modularity
• Ascending release cycle times  LTS base + shorter releases for modules
• Waiting for updates (surprise!)  public/transparent development (with
ability to check and contribute)
• High threshold for connecting your standard  lower threshold for usage

The main issue
• Usability
• Predictability
• Reliability
• Transparency
• Traceability

The main issue
• Usability
• Predictability
• Reliability
• Transparency
• Traceability
Technology influenced
Organisation (culture) influenced

“Language
independent”

UML
SysML
OWL
EXPRESS
XSD
JSON
Linked Lists, Selects, etc

“split” between shared base and modules (extensions)

IFC5
IFC5.x

IFC5 3 – 5 years stability
IFC5.x 1-3 years stability

Root, spatial structure, recourses, etc
Entities (classifications), PSets, etc

02
03
04
01
IFC

Materials, Geometry, Topology, etc
Spatial structure, Root classes, etc
Building, Road, Rail, Bridge, etc
Uniclass, Omniclass, Coclass, NL-Sfb, etc
BAM, Turner, HS2, anyone..

IfcRoot, IfcProduct, etc..

IfcRail, IfcRoad, IfcBuilding, etc..

Omniclass, CoClass, NL-Sfb, etc

Omniclass, CoClass, NL-Sfb, etc
BAM, Turner, John, etc

IFC

IFC5.x
IfcClassificationReference
IfcProperty
IfcMaterial
IFC5

Examples:
#123 = IFCCLASSIFICATIONREFERENCE($,'16.11','FUNDATIE
VOETEN’,#456,http://bsdd.buildingsmart.org/nlsfb/16/10/);
#789 = IFCPROPERTYSINGLEVALUE('Renovation Status',$,IFCLABEL('New’),$,
http://bsdd.buildingsmart.org/aaa/bb/);
#101 = IFCMATERIAL (‘concrete’, https://services.buildingsmart.org/bsdd/Volker/ccc/ddd)

Language
independent
semantic data
model (XMI)
XSD
XML
OWL
RDF/TTL/..
EXPRESS
STEP
JSON

Language
independent
semantic data
model (XMI)
XSD
XML
OWL
RDF/TTL/..
EXPRESS
STEP
JSON
HDF5
(binary)
Etc..

Language
independent
semantic data
model (XMI)
XSD
XML
OWL
RDF/TTL/..
EXPRESS
STEP
JSON
HDF5
(binary)
Etc..
Development
Automated ‘extracts’

“Biggest leap in the roadmap”

IFC Schema
PSet definitions
Documentation
Translations
IFC Extensions
IFC Extensions
IFC Extensions
Single tool
IFC Schema
PSet definitions
Documentation
Translations
IFC Extensions
IFC Extensions
IFC Extensions
Multiple contributions in parallel
EXPRESS/
HTML
Single person/tool

Continues Integration / deployment

xmi
IFC
Documentation
github.com/buildingSMART
xmi
Maintenance tools
(papyrus, EA, etc)
changelog

xmi
.exp
.xsd
OWL
HTML
.pot
bSDD
json
.png
(diagrams)
IFC
Documentation
github.com/buildingSMART
Quality
checks
xmi
Maintenance tools
(papyrus, EA, etc)
changelog
Change
log

“10 principles of IFC”
https://github.com/buildingSMART/NextGen-IFC/wiki/Ten-principles-for-a-future-IFC
• Follows contemporary approaches and standards
• Favors simplicity over complexity
• Has no single-purpose definitions
• Strives for interoperability and has no competing modeling paradigms
• Appropriateness
• Versatility
• Clarity
• A reduced implementation effort for (a) authoring (b) importing
• Harmonious and consistent
• Modularity

Other topics
• Licensing
• Quality assurance
• Culture change
• Ecosystem (use-case management, validation services, IFC Toolkit, etc)

2000 - 2005:
“Connecting islands while
new islands keep appearing”

2005 - 2010:
“Dynamic coordination workflows”

2010 - 2015:
“The cloud and the
Common data environment”

2015 - 2020:
“Linked data”

2020 - ….
“API orchestration and
Computational design”

Whatever concept for communication, coordination, collaboration or integration…..
All of them require:
- Agreements on what we mean with things
- Agreements on how to exchange things
- Agreements on how to find and access things

- Agreements on what we mean with things  Semantic Data standards (“when is it a room or a hallway?”)
- Agreements on how to exchange things  Syntax standards (“do you want XML or JSON?”)
- Agreements on how to find and access things  Meta data and API standards (“what do you have?”)

- Semantic Data standards (“when is it a room or a hallway?”)  IFC
- Syntax standards (“do you want XML or JSON?”)  ifcSPFF, ifcXML, ifcJSON, ifcOWL
- Meta data and API standards (“what do you have?”)  BCF, IDS, openCDE APIs
Even the newest technologies around APIs, computational design, digital twins, etc, all need this backbone of
information to be able to operate

Want to contribute?
Leon.vanBerlo@buildingSMART.org
(seriously, I’m Dutch, we like direct communication: just email me)
https://www.buildingsmart.org/about/technical-roadmap/

LOC presentation 2020: Future of openBIM standards

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à LOC presentation 2020: Future of openBIM standards

Similaire à LOC presentation 2020: Future of openBIM standards (20)

Plus de Léon Berlo

Plus de Léon Berlo (20)

Dernier

Dernier (20)

LOC presentation 2020: Future of openBIM standards

Notes de l'éditeur