A semantic common model for product data in the water industry

Abstract

The issue of interoperability in the Architecture, Engineering, and Construction (AEC) industry represents a challenge on a scale that spans across the project life cycle. This is predominant in the infrastructure sector that usually comprises a more versatile Operations and Maintenance (O&M) phase in comparison with the buildings sector. To this end, an important stage in the information life cycle is the asset information capture and validation during product procurement at the O&M phase. The water industry in the United Kingdom relies on Product Data Templates (PDTs) to fulfil such task, which is usually an error prone manual process. This paper presents an ongoing research, which investigates the application of Semantic Web Technologies (SWT) for improving product data exchange during product procurement at the O&M phase for the water industry in the United Kingdom (UK). Therefore, focus group sessions with industry experts were held to discuss current inefficiencies and solution requirements. Based on these results, a semantic common model named Asset Specification Ontology (ASO) was developed to capture and validate asset information during product procurement at the O&M phase. The common model (ontology) is based on available technologies, namely Web Ontology Language (OWL) and Shapes Constraint Language (SHACL). This gives the advantage of semantically rich data which can be linked and queried in a meaningful way to facilitate the exchange and validation of water industry assets’ data. The uniqueness of this paper is manifested in the issue it tackles, as efficient product procurement, and hence, data exchange in the water industry is an industrial challenge that is seldom researched. Results from the focus group sessions showed that information exchange within the UK water industry is impeded due to the lack of structured and semantic data. However, for a robust semantic interoperability, there needs to be a robust semantic data infrastructure, which would require semantic mappings from standards to product properties, from standards to other standards, and from standards to dictionaries. These conclusions were further supported by the common model, which was created from existing schemas, standards, and dictionaries. Generally, this paper recommends a common model/product library for phase-specific product data exchange in the water industry.

A Traceability Framework to Enable Circularity in the Built Environment

“…PDTs can also help to ensure the quality and safety of products by providing information about their designing and manufacturing processes. Such information can be used to identify potential hazards and risks associated with a product, as well as to monitor compliance with relevant regulations and standards [106]. PDTs become product template sheets (PDSs) when they are used as a basis for creating a specific product template for a particular product [107].…”

Concept for Enriching NISO-STS Standards with Machine-Readable Requirements and Validation Rules

“…In civil engineering, managing and exchanging information is a non-trivial task due to the complex nature of construction projects and the involvement of numerous stakeholders (Alani et al, 2021;Tomczak et al, 2022). These stakeholders in the Architecture, Engineering, Construction, and Operations (AECO) industry put their priority on ensuring compliance with standards, regulatory documents, and other requirements (Beach et al, 2015).…”