Professional Documents
Culture Documents
Hagedorn 2023 Bim Enabled Infrastructure Asset Ma
Hagedorn 2023 Bim Enabled Infrastructure Asset Ma
Abstract: The paper proposes a solution for a Building Information Modeling (BIM)-enabled Infrastructure Asset Management System (AMS)
for road owners. The approach provides asset managers with a strategy for the dynamic use of Information Containers for Linked Document
Delivery (ICDDs), considering the requirements of stakeholders across domains in the operational phase. The state of the art shows how in-
formation management can be carried out utilizing information containers employing Semantic Web technologies Resource Description Frame-
work (RDF), SPARQL, and R2RML. The key output is developing a web-based platform that implements ICDD containers for asset
management. Existing AMS are integrated by using SQL data mapped to RDF-based ontology data in the container. The use of existing
domain-specific ontologies for infrastructure in combination with the linkage of domain knowledge to a three-dimensional BIM model is a
step beyond the state of the art and practice in the construction industry. Linking inside the container allows for querying data across several
information models and ontology-based data to create stakeholder-specific data views. The approach was demonstrated in two use cases. The first
was related to the visual inspection of a concrete bridge. The detection of damage and the process of communicating the damage to a contractor
charged with the repair were described. The second use case was related to a road pavement and demonstrated how decision-making about
maintenance activities can be supported using cross-domain information containers. DOI: 10.1061/(ASCE)CP.1943-5487.0001051. This work
is made available under the terms of the Creative Commons Attribution 4.0 International license, https://creativecommons.org/licenses/by/4.0/.
Introduction pavements across the globe are aging and are being subjected to
higher loads, faster speeds, and extreme weather impacts such as
There are several challenges facing asset managers and owners of floods, heat, and so forth, that can cause rapid deterioration. Asset
transportation infrastructure, such as road networks. Bridges and Management Systems (AMS) that store and allow for easy retrieval
of high-quality data are critical to managing risks and making in-
formed decisions. Recent developments in internet-of-things (IoT)
1
Research Assistant, Chair of Computing in Engineering, Dept. of Civil and sensor technologies provide an opportunity for asset managers
and Environmental Engineering, Ruhr Univ. Bochum, Universitaetsstrasse to move toward resilient networks and to make decisions that min-
150, Bochum 44801, Germany. ORCID: https://orcid.org/0000-0002-6249
imize cost and environmental impact. Efficient and safe transpor-
-243X. Email: philipp.hagedorn-n6v@ruhr-uni-bochum.de
2
Research Assistant, Chair of Computing in Engineering, Dept. of Civil
tation infrastructure is the basic prerequisite for social progress.
and Environmental Engineering, Ruhr Univ. Bochum, Universitaetsstrasse Planning, construction, operation, and maintenance of infrastruc-
150, Bochum 44801, Germany (corresponding author). ORCID: https:// ture requires a significant commitment of both economic and hu-
orcid.org/0000-0001-5907-7609. Email: liu.liu-m6r@ruhr-uni-bochum.de man resources. AMS are used worldwide to estimate the required
3
Professor, Chair of Computing in Engineering, Dept. of Civil and maintenance measures for assets based on their current and future
Environmental Engineering, Ruhr Univ. Bochum, Universitaetsstrasse conditions and dependence on financial resources and objective cri-
150, Bochum 44801, Germany. ORCID: https://orcid.org/0000-0002-2729 teria (Aktan et al. 2019). The ISO 55000ff standards (ISO 2014)
-7743. Email: koenig@inf.bi.rub.de provide an overarching multi-industry approach to asset manage-
4
President, Infrastructure Management Consultants GmbH, Bellerives- ment (AM). One of the critical aspects of AM required to make
trasse 209, Zurich 8008, Switzerland. ORCID: https://orcid.org/0000-0001
good decisions is the evaluation of current conditions based on in-
-5453-1841. Email: rade.hajdin@imc-ch.com
5
Project Engineer, Infrastructure Management Consultants GmbH,
spection and monitoring.
Landsknechtweg 28, Mannheim 68163, Germany. ORCID: https://orcid Although periodic inspections are ubiquitous in managing road
.org/0000-0002-3688-9687. Email: tim.blumenfeld@imc-de.com networks, the requirements and methods differ across agencies and
6
Managing Director, Steinbeis Transfer Center (IMV), Willy-Andreas- regions. Bridge inspection largely comprises visual assessment
Allee 19, Karlsruhe 76131, Germany. Email: markus.stoeckner@h-ka.de combined with some simple basic measurement techniques. In cases
7
Project Engineer, iC consulenten, Schönbrunner Strasse 297, Vienna in which the results of inspections are not conclusive, in-depth in-
1120, Austria. Email: m.billmaier@ic-group.org vestigation or even maintenance intervention can be triggered. To
8
Managing Partner, iC consulenten, Schönbrunner Strasse 297, Vienna collect data about road surfaces, high-speed measuring systems
1120, Austria. Email: k.grossauer@ic-group.org have been used for about 20 years with laser technology and skid
9
Manager, InGEO Consulting, Bastiaanpoort 8, Delft 2611MC,
resistance measurement equipment. Based on the results of the in-
Netherlands. Email: kgavin@ingeoconsulting.com
Note. This manuscript was submitted on January 27, 2022; approved on spections, suitable maintenance measures must be selected consid-
June 20, 2022; published online on September 29, 2022. Discussion period ering constraints regarding traffic, accidents, and environmental
open until February 28, 2023; separate discussions must be submitted for and natural hazards. The derivation of technical measures, as well
individual papers. This paper is part of the Journal of Computing in Civil as their execution schedules, essentially is based on an analysis of
Engineering, © ASCE, ISSN 0887-3801. the severity and extent of current and forecasted deterioration.
1 3
Process analysis and concept development Use Case and Validation
Use Case 1
Identify workflow for Define task- and process- Conceptualize ICDD
Propose
transportation driven data flow for platform for workflow and
research questions
infrastructure operation information containers data management
Use Case 2
2
System architecture and implementation
realize the identified work processes and data flows. Process Analysis and Concept Development
The layered system architecture of the platform is presented and
the software implementation is conducted in Step 2. This software The overview of the general abstracted work process and data flow
architecture is a common architecture pattern, and was used in this in infrastructure asset management in Fig. 2 takes into account four
paper to provide an extendable and reusable implementation of the major aspects: the stakeholders, the processes, the data, and the en-
individual components. The resulting implementation enables the compassing web-based platform as the data management solution.
Asset
Fulfills requirements?
No Yes
approved
Receive order
unapproved
Contractor
Execute work Delivery
Container
Realization
ICDD Infrastructure Asset Management Platform
transfer
Existing
Container
relational
storage
database Retrieved datasets BIM model Documents Semantic data
Fig. 2. Overview of the involved stakeholders, the abstract work process, and generated data for the use of information containers in the ICDD
Infrastructure Asset Management Platform.
Asset Management and details of the previous content can be tracked. In addition, the
The traffic authority is responsible for the AM to ensure safe and contractor’s works also are recorded in this container as requested
reliable infrastructure by employing the management group and the documents. The resulting Requirement container will be handed over
operational engineering group. The main technical tasks in infra- via the ICDD platform to the contractor by receiving the order.
structure asset management focus on inspection and on planning The contractor uses the Requirement container for retrieving the
and executing maintenance based on the condition of the infrastruc- technical documentation of the infrastructure and as a template for
ture. The abstracted work process is performed by several stakehold- capturing the requested data. Adding the requested information
ers (Fig. 2). First, the manager plans tasks based on the available from the contracted task into the Requirement container, this con-
infrastructure data. Engineers provide the technical requirements tainer is transitioned into a Delivery container. This transition im-
and data needs of the planned task related to national standards. plies that the contractor modifies the Requirement container with
Then the commissioning can be prepared. After contractors receive all information included as a template container and adds each
the order, they can execute the work and deliver the requested or piece of the required information into the container during the work
updated data back to the operating engineers. The engineers verify process. After successfully integrating the data, this container can
the quality of the work executed and data delivered against the re- be delivered to the operating engineers for approval. The same con-
quirements, and finally approve the work if the requirements are tainer is reused, and thus is only annotated with metadata (suitabil-
fulfilled. The data generated during the process are provided or ity and status) to embody the data flow in the overall workflow.
exchanged in the form of information containers. After delivering the required documents and information into
the container, it can be approved by the receiving operating engi-
neers. Certain data can be selected and integrated into the existing
Defining Task- and Process-Driven Data for relational database, which can be used for the review of the infra-
Information Containers structure information and as a basis for future maintenance tasks.
An information container can be used to bundle and link different This paper introduces two use cases to demonstrate the application
types of data and documents (ISO 2018). The generic structure of of the Asset information container for planning maintenance tasks
the containers consists of an index.rdf file and three predefined and to present the data exchange using Requirement container and
folders—Ontology resources, Payload documents, and Payload Delivery container for a bridge inspection. The use cases were real-
triples—that are distributed in a ZIP archive (ISO 2020). The in- ized by providing an ICDD platform implementation.
dex.rdf file describes the container and its contents, including the
respective metadata. The ontology resources folder is used to store Utilizing an ICDD Platform for Asset Information
employed ontologies. The mandatory container ontologies Con- Management
tainer.rdf, Linkset.rdf, and ExtendedLinkset.rdf according to ISO To facilitate sharing, exchange, and visualization of data between
21597-1 (ISO 2020), and ExtendedDocument.rdf according to different stakeholders in information containers, an information sys-
FAIRsharing.org (2021) must be included. These ontologies provide tem called ICDD Infrastructure Asset Management Platform is
the class and property definitions to specify and link documents implemented. To track the work process for a container concerning
within the container. Depending on the scope of the container, uti- information management, the platform enables setting the container
lized domain ontologies also are declared in this folder. The Payload status according to the ISO 19650-1 (ISO 2018) status codes and
documents folder is used to store all defined documents, e.g., 3D- workflows. The user access to the container can be determined de-
object models, images, reports, and so forth. The Payload triples pending on the relationship between the logged-in user role and
folder is used to store the links collected in the related linkset file the project. Functions for visualization, creation, manipulation, and
and to store all RDF-based data sets, which are instances of domain deletion of the container content are provided. Data querying within
ontologies. the container and data integration from an existing relational data-
In the work process depicted in Fig. 2, the data and the connec- base is implemented. A detailed description of the system architec-
tion between data and process are shown as containers and dashed ture of the proposed platform is presented in the following section.
lines, respectively. The manager can access and query the available
infrastructure data from existing relational databases connected to
the 3D-object model for task planning inside the Asset information System Architecture of the ICDD Platform
container. The planning data for a maintenance task can be col-
lected directly in the Asset information container by the asset man- The system architecture of the asset management platform is split
agers. The data exchange points and the related data scope are into five layers with different functional scopes (Fig. 3). The foun-
defined as a part of the task requirements. An information delivery dation is the data layer consisting of two data stores. The user
manual based on ISO 29481-1 (ISO 2016) can be used. The level of and project database is conceptualized as a relational database stor-
detail of the data exchanged at each point must be defined. In this ing users, projects, and the relation of projects to a container with
Onto-
Rules dotNetRDF
r2rml4net logies
Business
Downloaded from ascelibrary.org by Carlos Andres Rua Machado on 11/03/23. Copyright ASCE. For personal use only; all rights reserved.
Data Access
Entity Framework Core ICDD Framework
Layer
Data
Layer User and Project
Container Storage
Database
additional metadata. The container storage is file-based storage, in 1192-2:2013 (BSI 2013) and indicates the use or type of informa-
which container payload and RDF-based data are deposited. The tion. A set of predefined labels from PAS 1192-2:2013 is imple-
data from the container storage is processed using the IIB.ICDD mented into the platform. These labels include coordination,
framework on the data access layer. This library provides the con- information, internal review, construction approval, manufacture,
tainer payload data at runtime and RDF-based data in in-memory Project Information Model (PIM) authorization, AIM authoriza-
triple stores for accessing, transacting, and querying data inside tion, costing, tender, contractor design, manufacture procurement,
containers. The framework handles ICDD containers that are valid construction, AM inspection, and AM maintenance. The suitabil-
according to ISO 21597-1 (ISO 2020). The transactions are referred ity is extended with another label, Requirements container, which
back to the file-based containers using writer classes for disposing specifies a container for modeling exchange information require-
of the in-memory triple stores and releasing memory resources. ments. Therein, requested documents can be added into the pay-
The service layer provides user-related data to implement a load, setting the property requested to true for this special
token-based authorization in the service layer. These tokens can document. These documents do not have a file stored in the pay-
be used by any web-based user interface. Together with the project load documents folder, but need to be filled by the receiving stake-
service, the access rights to projects and containers are assigned. holder after the suitability has changed. When the suitability has
Projects have members, and these members have access to the con- changed, documents can be supplied for the placeholder file meta-
tainers included in the projects, which in turn means that each con- data. The property requested then is set to false if the uploaded file
tainer is allocated to a project. matches the requested metadata for mime-type and file extension.
On the service layer, access to projects, containers, container meta- With this concept, links between payload documents also can be
data, contents of the container (as payload or RDF data sets), linksets, defined in the requirements container so that the files uploaded
and the querying and validating services are provided. At the infor- afterward are linked directly, as required by a client.
mation management level, the services provide project and container On the business logic layer of the system architecture, the data
management according to ISO 19650-1 (ISO 2018). The implemen- flow from the data access layer to the representation layer is man-
tation of this standard contributes to the successful implementation of aged, and input from the user interfaces in the representation layer
the asset information model (AIM). Thus, each container receives a is processed. Therefore, processors are implemented to fulfill cer-
status from the status codes (work in progress, shared, published, and tain tasks with input data and user interactions and provide the ap-
archived) of the standard. The archived status encompasses the jour- plication programming interface (API) and the user interface with
nal of changes in the container but does not allow any change of in- the required data. The processors access and distribute data to cli-
formation. However, each archived container can be updated to the ents throughout the services and the data access layer. Every proc-
next version, in which the status is work in progress, and changes can essor is related to the Container processor because all of them
be made in this version. The versions of containers are linked to each retrieve or send container-related data. Additionally, functionalities
other using the previous version predicate of the container description are provided for particular payload contents in containers. One of
defined by ISO 21597-1 (ISO 2020). The container claims additional these functions is the processing of IFC-based building models.
metadata as a set of recipients inherited from the project members, a Building models first are converted into a WebGL format to be
revision number, and suitability. The suitability is adapted from PAS shown within the web user interface afterward using the xBIM
mapping. These are converted into RDF to be queryable within the In this use case, the condition of bridge elements is assessed using
container context, and then stored in the container for exchange. the German guideline ASBING. The detected damage of an element
To realize this connector, first, the container schema is supple- is recorded with an image related to the respective IFC object. An
mented with a subtyping of the ct:ExternalDocument class from IDM is defined for data exchange between different stakeholders in
ISO 21597-1 (ISO 2020). The specialized class is denoted exdoc: the inspection process. Fig. 4 shows a BPMN diagram. This formali-
ExternalDatabase and documented in an extension ontology for zation of processes within the scope of IDM particularly supports
ICDD containers (FAIRsharing.org 2021). The external database understanding complex workflows of BIM model exchanges be-
class provides the necessary information to connect a container to tween several stakeholders. The process typically contains detailed
a MSSQL or other database specifying a connection string. To re- tasks for each stakeholder and the respective data exchange points.
trieve data from the relational database, the R2RML mapping lan- In this case, the process has just two data exchanges using the in-
guage (Das et al. 2012) is utilized. R2RML is well researched and formation container. The container content must be defined as an
defines either automatically generated basic mapping algorithms or exchange requirements model for each data exchange. The opera-
creates user-defined mappings (Hazber et al. 2016). In the platform tion engineer prepares the commissioning of the inspection with the
concept, both basic mapping of the full database and the user-defined necessary documents concerning the bridge structure. This informa-
mappings are envisaged. Therefore, the exdoc:ExternalDatabase tion is collected in the ER1_requirement_container. The contractor
class can have zero or one mapping file attached using the database uses this container as a template, and changes its name to ER2_
Mapping object, which references a mapping file stored inside the delivery_container with status “Work in progress” and changes
container as a ct:Document individual and provided in a RDF-based the suitability from “Suitable for requirement” to “Suitable for in-
syntax. If no mapping file is defined, basic mapping is executed. In spection.” These changes can be realized simply on the ICDD plat-
either case, the resulting generated RDF triples are stored within a form. Then, the inspection information as required can be added into
payload triples file and can be accessed using SPARQL or SHACL. the ER2_delivery_container. As a result, the ER2_delivery_
User-defined R2RML mappings are defined according to the W3C container with the aggregated data is delivered. The operation en-
recommendation (Das et al. 2012). The R2RML-based retrieval of gineer verifies the deliverables against the technical and exchange
RDF data from relational databases in the platform context is per- requirements. The verified information can be filtered by the engi-
formed using the r2rml4net NuGet package. neer for specific tasks, e.g., maintenance planning.
On the presentation layer, two possible user interfaces are imple- The configuration of the requirement container and the delivery
mented. A representational state transfer (REST) API is provided, container related to the use case is displayed in Fig. 5. Regarding
which conforms to the DIN SPEC 91391-2 (DIN 2019) specifica- the type and the usage of the data, the documents are stored in the
tions. Höltgen et al. (2021) demonstrated the API for the management three container folders as defined in the ICDD standard. In
of ICDD containers, contents, and linksets. Moreover, the web user addition to the ontologies required by ISO 21597 and the ICDD
interface provides a graphical user interface for all provided function- platform, the domain-specific ontologies also are considered in the
alities in the business layer and service layer. Additionally, the web folder Ontology resources for executing RDFS reasoning in the
user interface is equipped with an IFC viewer that becomes the start- container to further process the data with SPARQL and SHACL.
ing point for creating queries in the container related to selected IFC For the use case, the container employs three existing domain ontol-
objects without the user needing much prior knowledge of SPARQL. ogies for capturing semantic data (Fig. 6).
Both representations are secured using token-based authentication In addition to the structure model BridgeModel.ifc for a BIM-
and access the same data sources so that users can work in the same enabled inspection, the operation engineer provides the prede-
project or container in several client applications. fined document templates [REQ]DamagePlacement.ifc and [REQ]
Overall, the layered architecture allows for extensibility, which DamageImage.jpg with the requested attribute as placeholders in
enables different clients and front ends to be combined with each ER1_requirement_container. Using the requested attribute, the infor-
other on the basis of the REST API provided, and thus to be usable mation requirements can be defined digitally, fulfilling the process of
from any client software or even different AMS. information delivery and information approval both in practice and
for the ideal process according to ISO 19650. The contractor can
use the container template to deliver information and complete the
Use Cases ER2_delivery_container. The required documents for the damage
description can be uploaded into the container. If more damages
To visualize, exchange, and integrate AM data for inspection and were captured, all related documents should be uploaded regard-
maintenance based on the proposed ICDD platform, this section in- ing the requirements of the defined template files in the Payload
troduces two use cases. The first use case simulates a visual bridge documents folder.
inspection by an external contractor. The focus is on creating, col- Semantic data are captured in Turtle files in the Payloads triples
lecting, and exchanging the relevant data between the external and folder according to the defined domain ontologies. Links between
ER1_ ER2_
ICDD
requirement_ delivery_
container container
Operational engineer
Start
Request the
Prepare the No
Request inspection Check result result
commissioning improvement
Downloaded from ascelibrary.org by Carlos Andres Rua Machado on 11/03/23. Copyright ASCE. For personal use only; all rights reserved.
Traffic authority
End
fulfills requirement? Yes Select relevant
data
Object Model /
Database
IFC
Model AMS
Fig. 4. Process diagram of the visual bridge inspection with data exchange.
Fig. 5. Content of the requirement and delivery containers for the visual bridge inspection.
IFC elements, images, and semantic data are specified in RDF files clarifies which data are associated with each other. These data form
as so-called linksets. All linkset files included in the two containers the connective elements that are contained as components or instan-
are summarized in Fig. 7, providing the link description and the ces in the aforementioned documents. They then are linked using
document containing the linked elements. The link description the link type Directed1toNLink that defines a direction via exactly
one from-link element and a set of to-link elements defined by the mapping rules for exporting data between relational databases
ISO 21597-2. and RDF-based payload triples are defined in the R2RML mapping
language. The alignment between attributes of the Condition table
and the classes and properties of the EUROTL ontology is defined as
Use Case 2: Pavement Maintenance Plan shown in Fig. 9.
This use case demonstrates how decision-making can be supported To generate the container for this use case in Step 5, all contents
with the help of cross-domain information containers. Steps 1–7 in are provided in Fig. 10. When the relational database is registered
Fig. 8 show the establishment of an information container with as the payload document RIDatabase using the extdoc:External
available data from an existing asset management database linked DatabaseLink class and the mapping rule is declared as RIDatabase.
to road object models and the generation of an appropriate main- mappings.ttl and referred to the database link, the condition data
tenance plan. Step 1 defines the scope of the generated information can be integrated automatically into the container as payload triples
container. For example, an asset manager can use the information RIDatabase.instances.ttl using the defined mapping. The connec-
container to request the current condition of pavement road sections tion of lane sections from the database to respective IFC elements
linked to the respective elements in a 3D model. Based on the re- is created and stored in the linkset file Ls_ifc_RIDatabase.rdf.
sult, they can plan the maintenance based on the geometry of the To query and filter the relevant data to create the maintenance plan,
affected elements and the historical pavement data from the data- the SPARQL query language can be used, and queries can be ex-
base considering time planning and cost estimation of the mainte- ecuted in the platform on the aggregated container data as Step 6. By
nance work to be executed. reviewing the query result, the asset manager generates the main-
A relational database RoadInformationDatabase (RIDatabase) is tenance program, for example, for the queried road sections in criti-
cal surface conditions, and incorporates the respective data into the
set up consisting of seven database tables based on the German
information container in Step 7. These data are collected in the
NWSIB database for state-specific road maintenance. It contains
Maintenance.instances.ttl file. These instances of the planned pro-
four main information components: road section data, construction
gram also are linked with the related IFC elements. The links then
project data in connection with the road network information, in-
are recorded in the linkset file Ls_ifc_maintenance.rdf. As the last
spection data in connection with the condition information, and the
step, Step 8, the asset manager can import the relevant result back to
maintenance plan in connection with the planned pavement works.
the original database, an approach for which was introduced by Liu
The pavement condition assessment with four key indicators (fric-
et al. (2022) and which will be implemented into the platform in the
tion, evenness, rut depth, and crack width) available from the Con- future.
dition table (Fig. 9) is the focused of Step 2. These condition data
are recorded as instances of an appropriate domain ontology. In the
same manner, the data of the maintenance plan must be acquired Validation
using a domain ontology regarding the database table the Mainte-
nanceplan table of the RIDatabase. Considering both aspects, the Using the web user interface of the ICDD platform, stakeholders can
EUROTL ontology is employed to capture the numerical values of create, edit, view, and delete container contents using the applied
the condition and the planned maintenance data as Step 3. In Step 4, functions as shown in Fig. 11. The user interface includes three main
Domain Mapping
ontology rules Information
Container
(3) Select
domain ontology
(1) Define (4) Define mapping (5) Generate ICDD (6) Query (7) Integrate (8) Import data
use case rules container existing data new data into database
(2) Identify
related DB-data
Database
(DB)
Fig. 8. Process diagram of the maintenance plan creation using information container.
rdfs:domain
prov:generatedAtTime
eurotl:hasCondition prov:atLocation
rdfs:range rdfs:range
eurotl: schema:minValue
EUROTL
LocationByCoordinates schema:maxValue
eurotl:
rdf:label
Downloaded from ascelibrary.org by Carlos Andres Rua Machado on 11/03/23. Copyright ASCE. For personal use only; all rights reserved.
LocationGeographicalName
Ontology Class
eurotl:Condition prov:value
Object Property DataTypeProperty
Fig. 9. Overview of the proposed mapping between the condition table of the RIDatabase and the respective classes of the EUROTL ontology.
components for the interaction between the user and the system.
In the Explorer component, the structure of the container is pre-
sented. The document content is represented in the Content compo-
nent, e.g., the elements and structure of an IFC model, images, or
RDF-based triples. Domain ontologies, RDF-based triples, docu-
ments, and linkset files can be added to the container from the nav-
igation bar. SPARQL queries can be executed on the entire container
data. The output of the results is provided as a table or in the stand-
ardized SPARQL Query Results JSON Format. In the Properties/
IFC viewer component, the user can switch between the metadata
of documents and the integrated IFC viewer, which provides loading
multiple models combined into a federated model and selecting
elements directly per partial model.
Fig. 11. Interface of ICDD platform comprising the example container ER2_Delivery_Container for the visual bridge inspection use case.
Ontology
Ontology
E
S bot:Building bot:Element rdfs: prov:Activity prov:Organization
subClassOf
rdfs:domain rdfs:range rdfs:domain rdfs:range
bot:hasElement eurotl:
brot:Bridge prov:wasAssociatedWith
InspectionActivity
1 Links of Ls_element_inspection.rdf
Inspections.instances.ttl
elements:
Instances from
inspections:
substructure Inspection2020
prov:wasAssociatedWith
1 Links of Ls_ifc_element.rdf elements: elements: elements:
crossBeamWest crossBeamMiddle crossBeamEast
inspections:
elements: elements: EngineerOfficBridge
Downloaded from ascelibrary.org by Carlos Andres Rua Machado on 11/03/23. Copyright ASCE. For personal use only; all rights reserved.
mainBeamNorth mainBeamSouth
elements: elements:
abutmentWest abutmentEast Ontology Class Object Property
elements: elements: 1
Instances
Instantiation
foundationWest foundationEast Links related to
linkset file
Fig. 12. The relationship between the bridge model and instanced in ER1_Requirement_Container.
are carried by a grid consisting of two main beams and three cross In addition, a virtual layer over the pavement structure in the lon-
beams. The bridge substructure elements described previously are gitudinal direction was defined with element lengths of 100 m as a
considered to demonstrate the visual bridge inspection use case. homogeneous section for the condition assessment.
The topological representations of structure elements are described The condition data for the 100 m homogeneous sections are
using BOT as shown in Fig. 12. The whole bridge structure was recorded in the RIDatabase with the numerical values of friction,
typed both as a bot:Building and a brot:Bridge to be able to use the evenness, rut depth, and crack width. The database is connected to
generic topology hierarchy from BOT and to provide a more spe- the information container as a payload document (Fig. 13). The
cific classification of the structure using BROT explicitly. Further mapping rules RIDatabase.mappings.ttl are defined using EUROTL
classifications of BOT individuals can be inferred through the to export the data from the database into the container. Fig. 14 shows
alignment between BOT and BROT as provided by Hamdan and an example of R2RML mapping rules for converting the data of
Scherer (2020). The metadata of the inspection with the execution column crackwidth from condition table of the RIdatabase into in-
year and the assigned contractor are collected as instances of stances of the class eurotl:condition with the related pavement sec-
classes from the ontologies EUROTL and PROV. The links defined tion as a spatial object. Fig. 15 shows the imported data set of one
in the use case description are created between these instances and pavement section represented in triples as a result. The whole onto-
the elements of the IFC model. logical data are captured as triples in the RIDatabase.instances.ttl,
The contractor collects the condition of the nine elements defined which then are linked with the homogeneous section of the IFC
as BOT instances. Based on the German ASBING ontology, each model.
element possesses three condition grades considering traffic safety, Combined with the IFC model, the stakeholder can select
stability, and durability on a scale from 0 (no influence) to 4 (re- the pavement sections with critical values of the condition indi-
newal is to be initiated). In this inspection use case, all elements of cators. Based on the query result, the pavement sections requiring
the substructure are assessed as having no influence on traffic safety maintenance can be determined. The recommended work, year,
and Grade 1 or 2 for stability and durability without the relevant and cost are recorded in the maintenance plan linked to the sec-
need of maintenance, until the main beam at the south side has dam- tions. Fig. 16 demonstrates a query to filter the sections with
age such as concrete cracking or spalling. It then receives a Grade 3 a value of crack width of more than 3 mm through the SPARQL
for both conditions and needs to be maintained shortly. The re- query. As a result, the two end sections between 800 and 1,000 m
spective damage will be captured within the IFC model Damage- are returned and highlighted in the IFC model (Fig. 13). After
Placement.ifc for the localization and in an image DamageImage. a review of the IFC model, the maintenance plan can be made
jpg for visual assessment afterward. The IFC elements that are in a for the related sections with the required information using
Stability grade 3 state can be selected as shown in the IFC viewer in EUROTL.
Fig. 11 and linked to create a maintenance plan. Moreover, the
model with the damage location is shown in the IFC viewer.
Discussion
Use Case 2: Pavement Maintenance Plan
When using BIM for infrastructure operations, practical engineering
For planning the pavement maintenance based on the BIM model, a challenges must be overcome. BIM still is not adopted widely in the
limited road section with a length of approximately 1,000 m was transportation infrastructure domain. BIM models mostly are cre-
modeled. This road model contains only one direction and one lane ated during the design and construction phase but are not carried
without a terrain model. The underlying alignment of the road was forward to the operational phase to maintain the existing physical
built from an alignment element straight line. Because the current assets (Bazán et al. 2020). Thus, it is demanding to bridge the gap
export of ifcAlignment in IFC 4x3 is not provided in the modeling between current engineering practice and the optimal BIM usage
application, the model was exported in IFC 4 without alignment over the asset life cycle. Moreover, it is difficult to establish tech-
elements. The road cross section consists of four layers: asphalt nologies such as BIM model servers and RDF triple stores adjacent
surface course, asphalt base course, base layer, and antifrost layer. to existing organizational AMS, even if using BIM delivers more
Fig. 13. ICDD platform with the query result as a table and the filtered pavement sections highlighted in the IFC viewer.
added value for the organization. On the other hand, it is challenging storage of the BIM model and allow the linkage with further data as
to establish a relation between the vast amounts of existing data, a first step. The asset manager can create information containers
especially road network data, the BIM model, and related data syn- regarding the defined workflows without influencing the existing
chronously. Therefore, the use of information containers based on AMS. After the advanced system for combining BIM and intercon-
Semantic Web technologies can provide a solution for the temporary nected RDF data in a RDF triple store is established, the information
container can be used for the data exchange and data visualization Using the developed solution, aggregated data from different
to overcome the difficulty of accessing the database as an external domains also can be made usable for other cross-domain use cases,
stakeholder. e.g., to perform combined maintenance for a road section and sev-
Therefore, the most important benefit of the information con- eral bridges on the network together in one or more federated con-
tainer is to provide an open standardized data exchange format, in tainers. This is especially useful to align the competencies and
which data content also can be verified using the SHACL rule lan- responsibilities of different planners from different disciplines.
guage. The data exchange and the demand for a standardized data Moreover, this paper shows how the reuse of established domain
model still is one important impediment to BIM adoption in trans- ontologies can be beneficial for AM and also can provide a com-
portation infrastructure (Costin et al. 2018). The presented ICDD mon basis for cross-country and cross-language AM. In addition,
platform facilitates the creation, manipulation, and exchange of condition assessment rule sets for asset information containers can
ICDD-conform information containers between different stake- be developed using the SHACL rule language. By combining rules
holders in a project or asset context. Relevant standards have been with regularly updated data sets, e.g., through inspections or in-
incorporated into the platform. The generic data structure of the tegration of data from existing relational databases, the presented
information container makes the collection and linkage of extended ICDD platform can function as an up-to-date dashboard for mon-
information and documents with different types outside the BIM itoring infrastructure conditions, as shown in Use case 2.
model possible.
Even so, the generic concept requires a mapping of original data
structures into ontologies (as shown with the IFC model converted Conclusion
into LBD). Beyond a certain point, one single ontology is not able to
This paper shows the use of information containers, Semantic Web
cover all aspects of a data model, so alignments between ontologies
technologies, and domain-related ontologies as schemas in a web-
need to be defined and terminology has to be added. Although a
based platform for infrastructure asset management. A concept and
large number of central, general ontologies for AEC have been es-
a methodical approach were developed, and a web-based platform
tablished, there is a lack of a comprehensive overview of existing
was implemented, demonstrated, and validated in two different use
ontologies, their application, and interfaces with other ontologies.
cases. The investigated use cases are related to common activities
Based on the implemented ICDD concept, information contain-
of visual bridge inspection and road pavement maintenance plan-
ers also can be used for different life-cycle phases. Especially for
ning. Existing ontologies from the AM domain were reviewed and
the construction phase, in which the BIM model is established and used in ICDD containers in the proposed ICDD platform. Existing
the amount of information and documents increases intensively, AMS and their relational databases were considered in the ap-
providing a structured data package without restrictions on the data proach and connected to the information container. Thus, the infor-
type can improve the digitization of the construction documenta- mation container can access and evaluate data from the database
tion. At the end of a construction project, the as-built model with within a container and can be linked to IFC models and instances of
related information and documents can be handed over as a whole ontology data to provide a cross-domain queryable AIM. SPARQL
data package, which also simplifies the data integration into the queries can be executed on an aggregated data set of the container in
AMS. However, the use of ICDD information containers as a data an in-memory triple store. In the use cases, these SPARQL queries
structure and an exchange medium is only an intermediate step for were utilized to retrieve road sections or bridge elements that relate to
overcoming the file-based data exchange issues and establishing areas of interest for inspection or maintenance (e.g., damaged sec-
the vision of a fully remote access of linked building data in triple tions). The results of this paper answer the aforementioned research
stores, as proposed by Pauwels et al. (2022). The platform develop- questions.
ment prototype presented here offers the possibility that users can Information containers are suitable for describing, updating, and
generate queries and rules and execute these on containers for their processing data across the asset life cycle in a flexible and efficient
purposes. The creation of SPARQL queries on LBD requires knowl- way. The use of information containers for the management of PIM
edge of the syntax and semantics of the query language on the one and AIM is predetermined by standardization (ISO 2018). Informa-
hand and the queried data set on the other hand. This knowledge tion containers support information delivery according to IDM.
cannot be assumed for application in the engineering context. Query They also entail the systematic assembling, structuring, and ex-
templates and rule sets must be prepared accordingly and filled with change of data, which facilitates data management for transportation
parameters, e.g., from the IFC model, so that efficient use is possible. infrastructure operational activities combined with the BIM model.
Although the platform already allows the storage and import/export In this research, ICDD containers according to ISO 21597-1 (ISO
of SPARQL queries, as well as the creation of SHACL shapes in a 2020) were used to maintain IFC models and accompanying hetero-
knowledge base, the major challenge is actually creating this content geneous asset data, which were linked together inside these contain-
according to requirements for the application domains. ers using Semantic Web technologies. These technologies enable
declared for the process steps and are tracked throughout the work- are available in a repository or online in accordance with funder data
flow. These annotations are used to compose Asset information retention policies. The data generated for this paper is provided by
containers, Requirements containers, and Delivery containers. Hagedorn et al. (2022).
Considering the challenge of connecting existing asset man-
agement systems to BIM models, we demonstrated that an existing
database can be embedded in a container. An extension of the con- Acknowledgments
tainer schema is presented to allow setting up the connection to a
relational database. The content of the database can be integrated The authors gratefully acknowledge CEDR (Conference of Eur-
into the container using the R2RML specification for converting all opean Directors of Roads) and FFG (Austrian Research Promo-
database entries or a subset of database entries defined by R2RML tion Agency) for funding this research. The authors thank the
mappings. These mappings can convert data from the database into consortia of the projects AMSFree and BIM4AMS for their col-
RDF data using domain-specific ontologies so that these entries can laboration on the research of BIM-based AM concepts for roads
be linked to the IFC model afterward. The import of specific data and bridges.
from the database was demonstrated in Use case 2. In addition, the
data inside the information containers can be accessed in the scope
of the original AMS, which is possible in this approach through the References
implemented REST API. The integration of RDF data into existing
AASHTO. 2013. Transportation asset management guide: A focus on
SQL databases for a bidirectional data exchange was investigated
implementation. Washington, DC: AASHTO.
by Liu et al. (2022), and will be considered for future extensions of Aktan, A. E., I. Bartoli, and S. G. Karaman. 2019. “Technology leverag-
the presented platform. ing for infrastructure asset management: Challenges and opportunities.”
A system architecture was designed and implemented into a Front. Built Environ. 5 (May): 61. https://doi.org/10.3389/fbuil.2019
web-based platform in this paper. The system architecture comprises .00061.
components for the general platform implementation (i.e., user au- Bazán, Á., M. G. Alberti, A. Arcos Álvarez, and J. A. Trigueros. 2020.
thentication, access rights, project management) and components to “New perspectives for BIM usage in transportation infrastructure
handle the information containers. The core of the implementation projects.” Appl. Sci. 10 (20): 7072. https://doi.org/10.3390/app
relies on the ICDD framework, which also is provided decoupled 10207072.
Beckett, D., T. Berners-Lee, E. Prud’hommeaux, and G. Carothers. 2014.
from the whole platform. The ICDD framework implements func-
“RDF 1.1 Turtle: Terse RDF Triple Language: W3C Recommendation
tions to create, read, update, and export ICDD containers. Moreover, 25 February 2014.” Accessed January 26, 2022. https://www.w3.org
it enables further processing of IFC models, handling of SHACL /TR/turtle/.
and SPARQL requests, and providing the R2RML processor for the Beetz, J., J. van Leeuwen, and B. de Vries. 2009. “IfcOWL: A case of trans-
integration of external data from relational databases into the con- forming EXPRESS schemas into ontologies.” Artif. Intell. Eng. Des.
tainer. Altogether, these functions are provided behind a unified ser- Anal. Manuf. 23 (1): 89–101. https://doi.org/10.1017/S0890060409
vice layer that can be accessed via the REST API and the web user 000122.
interface in the presentation layer. This implemented web-based Berners-Lee, T. 2006. “Linked data.” Accessed April 9, 2018. https://www
platform enables executing the identified workflow for the mainte- .w3.org/DesignIssues/LinkedData.html.
nance of transportation infrastructures using ICDD containers. Biswas, S., et al. 2021. “CoDEC: Connected data for road infrastructure
asset management.” In Proc., IOP Conf. Series: Materials Science
Nevertheless, several improvements of the presented system for
and Engineering, 012002. Bristol, UK: IOP Publishing.
AM processes are conceivable and will lead to future research di- Bonduel, M., J. Oraskari, P. Pauwels, M. Vergauwen, and R. Klein. 2018.
rections. Firstly, the role of standardized domain ontologies was “The IFC to linked building data converter: Current status.” In Proc.,
highlighted in this paper, but efforts need to be made in particular 6th Linked Data in Architecture and Construction Workshop (LDAC),
to find and align existing ontologies and provide a high proportion 34–43. Aachen, Germany: CEUR Workshop Proceedings.
of semantic information in a language-independent way. For AM, BSI (British Standards Institution). 2013. Specification for information
the connection to geometric information is helpful for linear struc- management for the capital/delivery phase of construction projects us-
tures such as roads and bridge structures. Thus, research needs to ing building information modelling. PAS 1192-2:2013. London: BSI.
investigate how to better locate information both semantically and Calvi, G. M., M. Moratti, G. J. O’Reilly, N. Scattarreggia, R. Monteiro, D.
Malomo, P. M. Calvi, and R. Pinho. 2019. “Once upon a time in Italy:
geographically using geometric representation and preserve these
The tale of the Morandi Bridge.” Struct. Eng. Int. 29 (2): 198–217.
relationships between geometry and semantics for all stakeholders. https://doi.org/10.1080/10168664.2018.1558033.
In addition, maintenance processes in AM often require the updat- Chancey, D., E. Conrad, C. S. Dossick, C. R. Dubler, J. Fortune, D. M.
ing of geometric representations or the placement of geometric ob- Knight, and J. I. Messner. 2017. National building information model-
jects, such as drill cores or other test bodies, which can be automated ing guide for owners. Washington, DC: National Institute of Building
in the future. Especially for the use of different domain models in Sciences.
Schneider, G. 2019. “Automated ontology matching in the architecture, en- logical knowledge base for concrete bridge rehabilitation project man-
gineering and construction domain—A case study.” In Proc., 7th Linked agement.” Autom. Constr. 121 (Jan): 103428. https://doi.org/10.1016/j
Data in Architecture and Construction Workshop (LDAC). Aachen, .autcon.2020.103428.
Germany: CEUR Workshop Proceedings. Zimmerman, K. A., and P. V. Ram. 2015. “Pavement management’s role
Solla, M., V. Pérez-Gracia, and S. Fontul. 2021. “A review of GPR appli- in an asset management world.” In Proc., 9th Int. Conf. on Managing
cation on transport infrastructures: Troubleshooting and best practices.” Pavement Assets (ICMPA9). Blacksburg, VA: Virginia Tech Univ.
Remote Sens. 13 (4): 672. https://doi.org/10.3390/rs13040672. Libraries.