ASSET INFORMATION

MANAGEMENT USING LINKED

DATA FOR THE LIFE-CYCLE OF

ROADS

IALCCE 2018 Ghent, Belgium

Daan Alsem & Sander Stolk (INTERLINK)

INTERLINK PROJECT

IALCCE 20182

o Client: CEDR – Conference of European Directors of Roads

o Objective: define, link, manage infra asset information

• For roads

• Using Linked Data approach and Semantic

• WebAlign with parallel standardisation initiatives, bSI, OGC, national

• Share best practice between NRAs

o Period: August 2016 – Autumn 2018

o Deliverable: European Road Object Type Library (EUROTL)

o Tested in three test cases: Nordic countries, Germany, Netherlands

www.roadotl.eu

TNO – ROD – RHDHV – AEC3 – Trimble – Semmtech – ii – p&b4.0

30 October 2018

RESEARCH APPROACH

IALCCE 20183

1. Data Analysis & Survey needs & solutions

2. Three National Test Cases (NL, DE, Nordic)

3. Basic European Road OTL

• General principles: Modelling & Linking Guide

• Abstracted from national test cases

• Applied in test cases

4. Roadmap: How to start

30 October 2018

IALCCE 20184

System strategy

prepared or revised

NR

A C

apit

al

Pro

ject

s

Prioritise funding

The Typical As-Is Condition for the Business Processes involving Information Flow through the Life-Cycle of Road Infrastructure Assets

(assuming higher BIM-maturity countries, outsourced maintenance operations with fixed-term contracts, design-and-build construction contracts, and all assets owned by the NRA)

NR

A

NR

A M

aint

enan

ce

Prepare feasibility

study

Wo

rks

Cont

ract

or

NR

A’s

Sp

ecia

list

Con

sult

ants

/

Sup

plie

rs

Need identified for capital

works

Prepare options report and select preferred option

Prepare preliminary

design

Complete statutory processes

(planning, etc.)

Prepare contracts &

procure contractor

Monitor and approve design,

construction and commissioning

Receive as-built records

Identify contract

opportunity

Asset information

received

Assets inspected

and surveyed

Asset information verified and

supplemented

Asset information reformatted to meet information

requirements

New assets handed over

Asset management database(s)

NRA’s project database(s)

Selected asset information

Closeout and final account

Prepare tender

design and bid price

Manage detailed design

Construct and

commission scheme

Collate as-built records

Handover, closeout and final account

Contractor’s project

database(s)

Commence services

Prepare contributions to

NRA’s activities at each stage

Funding approval

Apply for funding approval at each stage

Business case and funding application

Stage gate intermediate

process Outsource selected activities

End services

NRA consultants’ and suppliers’

databases

NRA requirements Consultant

deliverables

Quality, contractual and commercial documentation (bi-directional)

As-built records, health &

safety file

Inspection and maintenance strategy prepared or revised

Asset information requirements

Asset accepted for addition to inventory

Final information requirements (based on updated

department best practice)

Maintenance type?

Apply for routine or emergency

funding, or advise capital works

Expenditure review

feedback loop

Funding approval

Funding application or capital

works advice

Determine most economic

management system for asset type

NR

A N

etw

ork

O

per

atio

ns

Monitor traffic using physical

systems

Thir

d P

arti

es (l

ocal

an

d re

gion

al

auth

orit

ies,

uti

lity

com

pani

es, e

tc.)

Commence engagement

Advise requirements at each stage and approve interfaces with assets

Engage with third-parties

End engagement

Authorities’ databases

NRA proposals

Third-party requirements and approvals

Resulting network

effectiveness

Intelligent transport control centre with decision making system and database

Manage traffic using

communications systems

Pavement and bridge management systems

Other asset types

Predictive

Reactive

Closeout and final account

Prepare fixed-term contracts

& procure contractors

Monitor and approve

maintenance

Receive as-maintained

records

Updated asset information with inspection and maintenance records

Mai

nten

ance

Co

ntra

cto

r

Identify contract

opportunity

Prepare bid price

Review existing asset information, resurvey assets, and supplement if necessary

Maintain assets

Collate as-maintained

records

Handover, closeout and final account

Contractor’s project

database(s)

Network operations strategy prepared or revised

Tender requirements and tender

submissions

Organisation information

requirements

Initial information requirements (based on department best practice)

Apply for operations

funding or advise capital works

Initial information requirements (based on department best practice)

Final information requirements

(based on updated

department best practice)

Predominantly a document based-system with silo databases and inconsistent information requirements

UNDERSTANDING THE

INDUSTRY’S NEEDS

18 October 2018

Preliminary Needs Statements

Literature review

Interviews

Surveys

Analysis

Final Needs Statements

IALCCE 20185

INDUSTRY’S NEEDS AND NEXT

STEPS

o Needs statements, e.g.

• Publish information requirements

• Gather information through life cycle using best available structure & format

• Use open standards for GIS, BIM, systems engineering

• Work towards a digital twin Information management functionality based on use

cases

o Recommendations to NRAs

• Linked data & standardisation – active contribution, sharing, open

• Capital works and maintenance contracts – validate, certify, scale

• Project and asset managers – start small – top five

• Learn from each other – UK, DE, NL, NO, SE, FI

o Recommendations to Supply chain

• Software companies – extension to LD/SW

• Engage with INTERLINK consortium

30 October 2018

OTL OBJECT TYPE LIBRARY

IALCCE 20186

• Library of standardised object types with their specification:

• Highway

• Bridge

• Viaduct

• ………….

CEDR-INTERLINK video on the European Road OTL

30 October 2018

IALCCE 20187

WHY LINKED DATA / SEMANTIC

WEB?

o (Open) Data: data common denominator in life-cycle and over supply-chain;

data liberated from applications

o Linked: data from multiple sources connected

oWeb: based on common, powerful, complete, distributed W3C technology

oSemantic: adding meaning to data to make it computer interpretable;

automatic data verification and reasoning

LD / SW is a powerful (the only?) technology that can help to meet the business needs

30 October 2018

EUROTL EUROPEAN ROAD OTL

IALCCE 20188

oA network of harmonised and linked existing standards and OTLs for Road

Asset Management Data

oThe EUROTL is a set of recommendations for National Road Authorities

oTested in three test cases: Nordic, Germany, Netherlands

oAfter the project, road authorities can:

• Gradually evolve from document- to data-driven, in a hybrid solution

• Make OTLs and their datasets uniform using Modelling & Linking Guide

• Reuse standards and OTLs from the EUROTL and connect to national OTLs

30 October 2018

KEY IDEA

oNo more „Mother-of-all-Models“

oDistributed „hybrid“ approach

➢Linking existing open resources from BIM, GIS & Semantic Worlds (OTLs)

• For Data Structures (linked data, non-linked data)

• For Data (linked data, non-linked data, documents)

IALCCE 20189 30 October 2018

EUROTL WITH CORE

(SIMPLIFIED)

IALCCE 201810 30 October 2018

IALCCE 201811

HOW NRAS CAN USE THE

EUROTL

1. Do your own test case using INTERLINK results

2. Use M&LG to (re)model internal OTLs

3. Re-use OTL(s) that are part of EUROTL

4. Share national OTLs for reuse by others

5. Define best practice

6. Harmonise

7. Standardise: prescribe the use of a part of the EUROTL

National

European

30 October 2018

IALCCE 201812

THREE TEST CASES: PROVE

ADDED VALUE AND FEASIBILITY

oNRA test cases and data

• Nordic (Sweden & Norway) – Trimble, Triona

• Germany – AEC3, interactive instruments, planen bauen 4.0

• The Netherlands – RHDHV, TNO, Semmtech

oTest case-based definition of EUROTL requirements (bottom-up)

o Demonstrate that business needs can be met with INTERLINK Approach

oUse existing commercially-available software

oHelp NRAs and industry to understand implementation

30 October 2018

IALCCE 201813

GERMAN CASE – BRIDGE IN

HAMBURG

oThree perspectives

• Traditional approach

• BIM pilot study (BIM4INFRA2020)

• INTERLINK Approach

oPilot

• Detailed engineering

info requirements

• Open standards

IFC

ASB-ING

30 October 2018

IALCCE 201814

GERMAN CASE – BRIDGE IN

HAMBURG

oDetailed model

oBuildings objects (IFC Bridge not yet standardised)

oRDF not efficient for 3D

oTool from buildingSmart

oGerman road classification system used for asset information management

Model in Revit

Export to IFC (67 MB)

Filter to IFC without 3D (64 KB)

Convert to ifcOWL

Link with ASB-ING

Widerlager (ASB-Ing)

30 October 2018

IALCCE 201815

GERMAN CASE – BRIDGE IN

HAMBURG

o Improve ease of information handover to existing databases

o Link inspection records to bridge objects (e.g. condition rating)

oQuery objects by ASB-ING class in triple store

oVisualise in IFC viewer (Desite)

30 October 2018

IALCCE 201816

VISION FOR ASSET

INFORMATION MANAGEMENT:

KEEP IT SIMPLE AND STANDARD

oData should be liberated and shared

oBig-mama, Mother-of-all-Models doesn‘t exist: Combine existing (open)

standards in separate modules, with road network model as a core

oThe actual ICT landscape is hybrid and will be so for a long time

o Linked Data technology is the glue

oDevelop your OTLs from the bottom up and reuse where possible

o Link to existing standards and OTLs as much as possible

30 October 2018

IALCCE 201817

ROADMAP FOR YOUR

ORGANISATION

1. Choose strategically for data-orientation using open data standards

2. Accept multiple formats / levels of information and use linked data as

glue

3. Select your modelling (& linking) guide, pref. harmonised with business

partners, KISS

4. Define your network of OTLs, pref. harmonised with business partners

• Select, develop, implement your separate OTLs; starting small, reuse

where possible

30 October 2018

EUROTL

o High level Object Type Library

o Based on existing OTLs (AM4INFRA, RWS OTL, OKSTRA,..)

o Contains:

• Activities (inspection, maintainance, realisation, replacement)▪ Agent(organisation)

▪ Entity of conditions, documents and objects: baseline objects, physical object, Geometry, Functions, requirements

• Lifecycle phases

• Locations (lineair referencing)

o Available as a start OTL

o for harmonisation to standardisation

IALCCE 201818 30 October 2018

IALCCE 201819

CURRENT STATE OF THE

PROJECT

oProject nearly finished: final report publicly available in November 2018

• Modelling & Linking Guide

• EUROTL core, its ontologies, fully documented

• Linked standards:

✓INSPIRE - Road Network, incl. GeoSPARQL and GML

✓ifcOWL, ISO linear referencing

✓AM4INFRA taxonomy

✓SOSI, CoClass, ASB-ing, OKSTRA, COINS

oNational projects in Norway, Netherlands, Ireland, Sweden

oCEN TC442-WG4-TG3: standardise M&LG

oHow about building SMART: buildingSMART special distinction award 2018

30 October 2018

IALCCE 201820

SUGGESTIONS FOR JOINT

EFFORTS

o Just-do-it on a small scale, learning by doing

• Experiment with Linked Data / Semantic Web

• Share knowledge and experiences

o Leadership

• Shared vision on asset information management

• Collaboration between public – industry – academia

• National Proof of Concept project, demonstrating added value & feasibility

• Share, harmonise, standardise modular OTLs

oStay in touch with European / international developments

• CEDR BIM group

• Learn from / influence Building Smart, OGC, CEN, ISO, …

• INTERLINK partners

30 October 2018

CONCLUSIONS

1. Asset data should be liberated

2. Mother-of-all-Models doesn‘t exist: Make use of existing standards

3. Hybrid approach is the future

4. Linked Data is the glue

5. Bottom-up model development and reuse

Stay informed: www.roadotl.eu

IALCCE 201821 30 October 2018

with video & open available reports