Comparison of the LOX classification system across countries.
We present an exploratory analysis of the geometric accuracy of digital twins generated for existing infrastructure using point clouds. The Level of Geometric Accuracy is a vital specification to measure the twinning quality of the resulting twins. However, there is a lack of a clear definition of the Level of Geometric Accuracy for twins generated in the operation and maintenance stage, especially for structural health monitoring purposes. We critically review existing industry applications and twinning methods. To highlight the technical challenges with creating high-fidelity digital replicas, we present a case study of twinning a bridge using real-world point clouds. We do not provide conclusive methods or results but envisage potential twinning strategies to achieve the desired geometry accuracy. This chapter aims to inform the future development of a geometric accuracy-based evaluation system for use in twinning and updating processes. Since a major barrier for a fully automated twinning workflow is the lack of rigorous interpretation of ‘geometric accuracy’ outside design environments, it is imperative to develop comprehensive standards to guide practitioners and researchers in order to achieve model certainty. As such, this chapter also aims to educate all stakeholders in order to minimise risk when drafting contracts and exchanging digital deliverables.
- digital twin
- geometric accuracy
- point clouds
- structural health monitoring
In the wake of the Notre Dame Cathedral fire, digital scans collected by Dr. Andrew Tallon  offer the hope for future restoration. One question raised is, what Level of Geometric Accuracy (LOGA) can the reconstructed digital replica achieve with respect to the physical asset? In the Architecture, Engineering and Construction (AEC) sector, operation and maintenance (O&M) costs can range between 60 and 80% of total life cycle costs, which is three times greater than the cost of design and construction . This demonstrates the significance of implementing intelligent asset documentation and structural health monitoring (SHM) approaches for existing built assets. Laser scanning has been widely used to document and monitor existing conditions of real-world assets in the form of point clouds [3, 4]. A point cloud is an unstructured low-level digital representation, which by itself does not contain any meaningful information of the documented asset. A ‘twinning’ process is utilised to convert the low-level data into a high-level digital representation in a structured format, namely, a geometric Digital Twin (gDT) . The gDT can be further enriched with other information, such as semantic meanings, texture, materials, damage, energy use, maintenance data and so forth from its physical twin using IoT technologies , to form an information enriched model over time, namely, a ‘digital twin’ (DT). ‘Geometric accuracy’ is a vital indicator that guides and describes the degree of spatial accuracy of the resulting twin. It is conventionally deemed as the Represented Accuracy  that denotes the standard deviation range to be achieved once the point cloud is twinned into a geometric model. Twinning a real-world asset is an interpretive process, where geometric accuracy largely depends on a modeller’s experience and discretion . While in their unstructured state, point clouds contain more geometric details than a resulting gDT created from the point cloud. Therefore, the resulting ‘best-fit’ gDTs are highly unlikely to be as accurate as the measured data (e.g., a point cloud) at the end of the twinning process . This is also true for the automated methods since there is a trade-off between the achieved geometric accuracy and the quantity of information used for describing existing constructive objects in arbitrary shapes . This occurs because the process of twinning involves simplifications to create polygon- or mesh-based primitives so that it ‘smooths’ discontinuities and gaps in point clouds . This means that almost every object is approximated in order to transform point-cloud-based descriptors (in non-parametric formats) into parametric primitives . Figure 1 illustrates a series of components for a bridge asset where the point cloud is converted into bespoke gDT elements. However, since point clouds often contain defects, such as varying point density  and occlusions , it is difficult or often not feasible to achieve a desired LOGA for resulting gDTs . When these conditions occur, what are realistic expectations for a modeller or of an automated method with regard to representing the reality and meeting the required accuracies for SHM?
Numerous specifications termed as LOX (e.g. Level of Development and Level of Detail) have been developed to guide practitioners and researchers when creating digital models . What do the LOX mean? How to measure whether the specifications were met? What is the best practice approach to reflect when the employer requires ‘1 cm accuracy’ or ‘every element to be within a half centimetre’? This chapter explores these questions, aiming (1) to provide a critical review of existing specifications and twinning implementations, (2) to identify technical twinning challenges, and (3) to inform the establishment of a geometric-accuracy-based evaluation system for twinning and updating.
2.1 Existing LOX
The term ‘LOD’ was initially introduced by Vico Software . Ambiguity of defining LOD stems largely from the fact that the American Institute of Architects (AIA) later adopted this concept and kept the acronym LOD but changed it to mean ‘Level of Development’ rather than ‘Level of Detail’ . It was then superseded by the document AIA G202™ , which defines five progressively detailed levels of completeness: LOD100–LOD500. Based on the AIA protocols, the BIMForum  released another LOD specification, which was identical to those published in the AIA’s Digital Practice Documents , but with two exceptions. First, a new LOD was designated as LOD350. Second, the LOD500 was removed from the specification. The geometric requirements of gDT elements of LOD300, LOD350, and LOD400 are defined in the same way in terms of accuracy. However, this BIMForum document does not elaborate on what is implied by ‘accurate’ or how to measure it. Bolpagni [20, 21, 22] summarised the history of the LOX classification system in Table 1. Various new classification systems have been developed to accompany and complement the BIMForum’s LOD specification. For example, New Zealand proposed a LOD specification that contains five maturity levels , each of which is a sum of different aspects that define the geometry and information of gDT elements. Among these, Level of Detail (LOD) and Level of Accuracy (LOA) do not specify any quantitative standards. Royal Institution of Chartered Surveyors  proposed a concept of building survey detail accuracy banding, which defines accuracies to be achieved for different surveyed features when an employer requires a customised geometric accuracy and confidence level. This banding, however, is tailored for designing building settings consisting of cuboids defined by length, width, and height. Similarly, Abualdenien and Borrmann  introduced a multi-LOD meta scheme, taking into account the geometric uncertainties by assigning quantitative fuzziness in cm. Again, the usefulness of this scheme in describing the twinning quality is unknown. To this end, Banfi  and Banfi et al.  proposed a new Grades of Generation (GoG) protocol for twinning highly complex historic structures from point clouds. LOGA was defined as the error resulting between the reconstructed objects and the point clouds using metrics such as the mean distance, median distance, and standard deviation. The USIBD specifications  were the first to provide the means to report twinning results of existing building conditions (from point clouds) based on standard deviation (stdev). It articulates the ‘accuracy’ as well as the five different LOAs (Figure 2) by which to represent real-world out-of-plumb geometries. Specifically, the Measured Accuracy represents the stdev range that is to be achieved to acquire a point cloud, regardless of the method used. In contrast, the Represented Accuracy represents the stdev range that is to be achieved when a point cloud is twinned. This guideline, however, does not indicate how to achieve and how to measure the Measured Accuracy and Represented Accuracy. As shown, various acronyms are used across countries and organisations. These acronyms are either identical or interchangeable, making them very challenging to be understood or adopted.
|Country/region||Document||Year||LOX||Whole gDT||gDT element||Geometric data/info||Non-geometric data/info|
|Australia||CRC||2009||Object Data Levels/Level of Detail||√||√||√|
|USA||Department of VA||2010||Level of Development||√||√||√|
|USA||Vico Software||2011||Level of Detail||√||√||√||√|
|Australia||NATSPEC||2011||Level of Development||√||√||√|
|Hong Kong||HKIBIM||2011||Level of Detail||√||√||√|
|USA||NYC DDC||2012||Model Level of Development/Level of Development||√||√||√||√|
|Penn State University||2012||Level of Development||√||√||√|
|USC||2012||Level of Detail||√||√|
|US Army Corps of Engineers (USACE)||2012||Level of Development||√||√||√|
|Singapore||BCA||2013||Level of Detail||√||√||√|
|UK||PAS 1192–2||2013||Level of Model Definition||√||√||√|
|Level of Model Detail||√||√|
|Level of Model Information||√||√|
|UK||CIC BIM Protocol||2013||Level of Detail||√||—||—||—|
|Germany||BMVBS||2013||Level of Development||√||√||√|
|Canada||AEC||2014||Level of Development||√||√|
|France||Le Moniteur||2014||Level of Detail/Level of Development||√||√||√|
|Australia||BCPP||2014||Level of Development||√||√||√|
|Level of Detail||√||√|
|Level of Accuracy||√||√||√|
|Level of Information||√||√|
|Level of Coordination||—||—||—||—|
|China||CBC||2014||Level of Detail||√||√||√||√|
|Belgium||ABEB-VBA||2015||Level of Development||√||√||√|
|Germany||D&R||2015||Level of Development||√||√|
|USA||BIMForum||2015||Level of Development||√||√||√|
|Associated Attribute Information||√||√|
|UK||NBS BIM Toolkit||2015||Level of Detail||√||√|
|Level of Information||√||√|
|UK||AEC (UK)||2015||Level of Definition|
Level of Information
Grade/Level of Detail
2.2 Industry applications
Leading software vendors provide advanced commercial twinning solutions, which are currently semi-automated processes at best. ClearEdge3D Edgewise software can automatically extract geometric features for industrial constructive elements and basic architectural elements using cross-sections in user-cropped regions followed by fitting 3D shapes from a library of preloaded features [28, 29]. This means, the current practice can achieve a high degree of automation of twinning if the resulting geometries are assumed to be generic or pre-defined. However, in the context of SHM, this assumption is unrealistic if a millimetre twinning accuracy is required. Twinning arbitrary geometries using point clouds is quite challenging . Most authoring tools are designed to model orthogonally, or along local coordinate axes. They employ the use of rigid-body parameters to design construction elements by defining cross-sectional shapes, length, width and height parameters, whereas in the real world, as-is components are often warped, off-plumb, or contain deflections . While finite element analysis and multi-physics engines can be used to predict elastic and plastic distortions in materials , current digitization workflows that produce parametric objects cannot capture distortion such as bowing in a beam or welding distortion in steel frames. Errors are introduced when the as-is geometries are twinned as being plumb and subjected to rigid-body physics . In this case, geometry deviation analysis is important because unfitted geometries would potentially reduce the reliability of the gDT to be used for structural analysis and defect detection for SHM purposes. Current authoring applications are not capable of carrying out geometry deviation analysis for point clouds. The actual geometry deviation analysis requires third-party middleware software to interpret and investigate. FARO BuildIT Construction  is the most recent verification software for dimensional quality control (QC) process. Measured data collected from laser scanners can be compared against a gDT to analyse geometric deviations (Figure 3). However, it is worth noting that the nature and origin of a deviation is not identified in the analysis directly. Specifically, the analysis itself is often in the form of a ‘heat map’, where deviations are plotted in colours that correspond to a specific magnitude and direction from a perfect state (i.e. 0 mm deviation). However, point clouds contain voids and sparse measurements, which as directly classified deviations. These false positive measurements make it difficult to interpret the deviation analysis results. Users must manually inspect datasets to observe and detect gross errors or missing components. Currently, there are no available automated solutions for this in existing middleware. In addition, once deviations are identified through deviation analysis and manual interpretation, users must also manually apply changes to update the authoring gDTs. This is currently a large challenge since there is very little research into automated updating of gDT from point clouds [35, 36].
2.3 Existing research methods
Automated methods have been proposed to streamline the twinning process (Table 2) [37, 38]. However, user intervention was still required for some crucial steps . Zhang et al.  and Laefer and Truong-Hong  produced gDTs for bridges and industry plants, but without a geometric deviation assessment. Anil et al.  were among the pioneers who discussed in depth the problem of geometric deviation. They suggested using minimum Euclidean distance and thresholding  as metrics to evaluate the fitting quality (CAD model against point clouds). The deviation analysis at macro level (for the whole structure) was performed using a commercial software application (i.e. Polyworks v9). Bonduel et al.  suggested assessing the twinning results at both macro and micro levels. They used CloudCompare to analyse the deviations between a point cloud and a manually generated building floor gDT. They also discussed the achieved represented accuracy using LOAs provided by USIBD. Then, Hausdorff distance was proposed to measure the fitting deviation of a mesh-based building gDT reconstructed from a synthetic point cloud . Thomson and Boehm  suggested using Euclidean distance and area difference based on the width and length, and angular difference to measure the fitting quality of walls. Although these measurements can assess elementwise quality, they are tailored for generic building walls in cuboid shapes. Similarly, Valero et al.  assessed fitting deviations of individual furniture objects and walls using orientation, dimension, positioning, and sizing metrics, assuming these objects consist of planar surfaces. Lu et al.  proposed an automated fitting method to twin bridge components. They gauged the fitting accuracy using Cloud-to-Cloud (C2C) distance metrics—a similar metric used by Shirowzhan et al. . However, the geometric deviation evaluation was performed only at the macro level. NURBS-based methods [27, 39, 49, 50] were employed to reconstruct geometric surfaces for building, industry plant, and historic building elements. Note that the generation of compound pipes requires user intervention to group a set of cylindrical segments followed by automatically fitting surfaces . Likewise, highly complex historic structures require manual surface generation, although extremely high twinning accuracy was reported . Point-to-surface distance metrics were used to evaluate the fitting quality [39, 49]. In contrast, Barazzetti  used the commercial package Geomagic Studio to evaluate the fitting accuracy of the NURBS curves through a progressive densification (i.e. multi-resolution) approach. As shown, there is no fully automatic method to produce geometrically highly accurate twins for existing assets. Also, more comprehensive evaluation metrics need to be established for assessing twinning quality.
|Point cloud authenticity real (R) or synthetic (S)||Manual (×)/automated (√) twining process||Structure completeness||LOGA assessment availability||Manual (×)/automated (√)|
|Micro (I)/macro (A) levels|
|LODGA assessment method/metrics|
|||R||×||×||√||×||A||Minimum Euclidian distance and thresholding|
|||R||√||×||√||√||I||Centroid Euclidean distance, area difference (width and length), angular difference|
|||R||√||√||√||√||A/I||Plane fitting/orientation/dimensional error, positioning/sizing error|
|||R||×||×||√||√||A||Mean point-surface distance|
|||R||√||×||√||×||I||Cylinder radius and orientation|
|||R||√||√||√||×/√||A/I||Control points and point-to-gDT|
3. Case study
Previous sections have discussed that twinning existing assets using point clouds is restricted by current software tools which are limited in their ability to represent out-of-plumb conditions and non-rigid formations. It is also restricted by the limits of the data itself. This section discusses this problem in detail through a case study.
Laser scanning can sample an object’s surface as it exists with highly accurate spatial measurements in the form of 3D points. If the documented object is not straight or plumb, the scanner can capture its geometric status. Theoretically, a terrestrial laser scanner such as the FARO Focus 3D X330  has a ranging error of ±2 mm at 10 m, equating to a systematic measurement error at around of 1σ at 10 m. However, the measured accuracy is affected by many factors, including the standard deviation of the sensor, registration methods, material type being scanned, low temperature, bad weather, and strong sunlight . The overall twinning error can be expressed as a combination of three primary sources of error:
where is the ranging error associated with the laser scanner, is the measured error introduced during scanning and registration, and is the represented error resulting from the process of scan-to-gDT. It is important to specify the error associated with each source independent of each other since they are assumed to be mutually exclusive. In this chapter, we only focus on discussing the represented error , which is independent of the sensor, or parameters of the documented object, or scanning and registration methods. It is related to the manner with which the measured point cloud is being transformed into the outcome, i.e. a gDT and describes the extent the gDT matches the acquired points.
As mentioned earlier, existing authoring software packages are by nature orthographic modelling tools. The challenge with using these software packages becomes how to represent a structure’s up-to-date conditions. To complicate matters further, the as-weathered, as-damaged, or as-deviated information of existing assets further increases the representation difficulty. Fitting deviations will be generated and propagated if these conditions are represented in an over-simplified fashion. In addition, sparseness, hidden, or concealed conditions are often encountered in point clouds, making it difficult or impossible to twin constructive objects with certainty. Thus, is the accumulated error from the geometric deviations and the propagation of data uncertainty.
Figure 4 demonstrates current efforts on parametric bridge design . The essential feature for bridges is the horizontal and vertical alignments, which control the parametric relationships and dependencies between assembly systems and all components. The deck cross-sections are then driven by the bridge alignment curves. They are profiles that are used in conjunction with the alignment to derive the overall 3D shape of the bridge deck.
When SHM and retrofit planning is being performed, accurate as-is condition data is required regardless of the availability of the as-designed parametric information. Point clouds can depict the as-is geometries of an asset using thousands of data points. However, maintaining the dimensional accuracy and geometric fidelity of a given bridge point cloud is challenging because the usefulness of topological and geometric constraints is limited to very simple geometric shapes and spatial relationships. As-is geometries do not exhibit a parametric pattern with respect to the initial primitives used to create the as-designed model. Figure 5 illustrates the non-orthogonal geometries of a real-world bridge point cloud cannot be fitted using generic shapes, such as cuboids, in an orthogonal fashion. The modelled slabs do not follow the point cloud and produce fitting deviations when they are joined at sharp angles (Figure 5a). These deviations become smaller if the cross-sections are outlined with as-is 2D shapes. However, the bridge gDT does not necessarily close better and become manifold as the fitting quality is improved at the expense of broken or clashing connections (Figure 5b). This is especially true when twinning point clouds of pipes with sags, beams and columns with welding distortion or walls that are skewed. Adjacent components do not fit to properly watertight connections unless they are joined at right angles. For example, Figure 6 illustrates part of a piping system generated using point clouds. The local deviation is reduced from 30 to 1 mm when watertight connections are not used. Given the challenge with the mediation of non-parametric real-world deviations to parametric model primitives, modellers are often forced to leave objects ‘slightly off-axis’ or perform ‘unnatural shape editing’ by eliminating or ignoring as many overlapping and joint warnings as possible in order to match the points.
When facing occlusions and damage conditions, the geometric accuracy has a reliance on human perception followed by inferring the hidden information based on assumptions. For example, a bearing plays an important role in a bridge, but its surface is less than 1% of that of the deck slab and has a complex composition. These characteristics make it difficult to be fully captured by a laser sensor (Figure 7a). In addition, point clouds need to be down sampled before feeding into in-memory-system-based authoring tools or automated algorithms that cannot handle huge datasets. The down sampling is often performed using a third-party processing software application, which applies generic filters to evenly down sample the points without considering local geometric context. While this is certainly helpful and creates beneficial data compression, the resulting datasets often lose information along the way (i.e. sparse areas or smaller objects will have little to measurements). Thus, only a few points are retained for the bearing surface which does not provide enough information to support the twinning task and result in geometry uncertainties (Figure 7b). The interpretation of bearing shapes largely depends on modeller’s knowledge and discretion, which could introduce connection problems (e.g., clashing/gaps) (Figure 7c). Uncertainty increases when working with point clouds containing skewness and noise (Figure 7d and e). Although methods have been suggested to work under occlusions and sparseness [5, 55], the certainty of the resulting models is rarely investigated.
Figure 8 shows an example of a bridge where little-to-no measurements were captured in the girder areas due to a limited line of sight . Like many existing works, both the manual and the automated method inferred specific girder profiles and produced gDTs with detailed dimensions using engineering knowledge. Then, Cloud-to-Cloud (C2C) distance could be used  to compute the deviation between the point clouds sampled from the manually generated gDTs (Manual) and the automated ones (Auto), and the real point clouds (Real):
where is the estimated distance between a compared point cloud (i.e. Manual or Auto) and a reference point cloud (i.e. Real). Non-trivial fitting deviations occurred and raised the overall macro-level deviation (C2CAuto—12.5 cm and C2CManual—5.7 cm) . These significant fitting deviations were due to the occluded areas, as no measurements were available to compare against, resulting in an incorrect gDT from a geometric accuracy standpoint. This solution is straightforward since it does not take the modelling uncertainties into account. It simply takes uncertain areas as errors. Figure 9 illustrates that the fitting deviation was drastically reduced by approximately 70% (C2CAuto—4.2 cm) if we replace the complete girder profiles with unclosed mesh-based gDTs while other parts remain unchanged. Yet still, the improved accuracy only aligns with USIBD’s LOA 20 (lower range: 15 mm, and upper range: 5 cm, at 2σ) , corresponding to a relatively low accuracy standard. USIBD provides different represented accuracy levels, but it does not specify how to measure it. For example, we can only use a couple of reference points to estimate the accuracy. It is the averaged fraction between pair reference-point distances in the registered scan data and the corresponding pair on-site or gDT point distances:
where M is the number of investigated pair-wise distance. Then, it is possible to acquire that aligns with a higher LOA in USIBD. By contrast, unlike , C2C is an estimation using thousands of calculated points. Therefore, the resulting C2C-based accuracy is almost surely not going to achieve an expected ‘high accuracy’ level (e.g., ±10 mm or USIBD’s LOA 30 onwards). The C2C comparison between the Auto and Real revealed that points sampled from bottom flanges of girders were well matched with the original points while the mismatched points were mainly from the central part of the deck slab where points were not evenly distributed. This is attributed to the undulating-surfaces of the gDT generated using the proposed ConcaveHull alpha-shape algorithm (Figure 9). Local indentations or bumps are generated when alpha value is too small to smooth out the surface affected by unavoidable noise, raising the fitting deviations. However, optimising the alpha value is difficult because an indentation, for instance, could be due to a defect or a hole but could also due to localised sparse and unevenly distributed points. In addition, although the ConcaveHull alpha-shape algorithm can describe slab geometries in a 2D space, it oversimplifies a 3D space.
4. Prospective twinning methods and deviation analysis
The analysis provided in the previous section demonstrates that real-world conditions are seldom orthogonal and perfect, rendering it extremely difficult to perform high-fidelity twinning with a geometric accuracy on the millimetre scale. Commonly used representation models include but are not limited to: implicit representation such as mathematical formula-based methods , Boundary Representation such as polygon- and mesh-based methods , Constructive Solid Geometry , Swept Solid Representation , and NURBS representation [49, 50]. Depending on the nature of defects, the as-damaged geometries may be represented in different ways. Figure 10 illustrates the vision of the concept of an as-damaged bridge gDT implemented for the inspection work. The method proposed by Hüthwohl et al.  can be used to integrate superficial defects such as cracks, efflorescence, corrosion, and slight spalling [Figure 10a—(3) and (4)] to the affected element using the back-project technology  (Figure 10b). In contrast, major defects, such as severe spalling, cavity and pothole [Figure 10a—(1) and (2)], are significantly different in geometry compared to their surrounding healthy (i.e. good condition) surfaces. The method proposed by Lu et al.  can be used to represent healthy elements; however, it cannot describe the unhealthy areas precisely, due to the extrusion-based twinning nature. Finer representation, such as mesh-based and NURBS-based twinning techniques , can be employed to handle the geometry complexity of significant defects in a precise manner (Figure 10b). The more variable the defect, the greater the geometric twinning needs to rely on non-parametric representation such as mesh format. One promising solution to produce a gDT that takes the as-damage information into account is to first detect unhealthy areas , followed by twinning these unhealthy areas using finer twinning techniques based on their type and size. However, the mesh polygon resolution should not degrade the rendered presentation. This requires an intelligent a priori scheme to resample the point clouds based on the geometric complexity of a sampled surface [61, 62].
Construction elements with different scales may require different twinning techniques. For example, extrusions could be efficient for twinning slab segments; however, they cannot be directly applied to bearings. This means a gDT is highly likely to contain more than one data representation type in order to balance its resolution and the LOGA, which very few works have covered in depth. In addition, as previously mentioned, occlusions and sparseness increase the uncertainty of the resulting gDT. These problems require a more intuitive geometric deviation analysis system. The macro-level deviation analysis can provide an overview of the twinning quality whereas it does not reflect a detailed comparison at the component- or feature-level. Therefore, the dimensional QC system of geometric deviation analysis should consist of both macro- and micro-level analysis. The former, can be used to quickly localise uncertain areas, or areas with major deviations (Figures 8 and 9) while the latter can provide detailed deviation analysis at the component-level, indicating a more meaningful LOGA of specific elements. Table 3 shows an example of the C2C-based geometric deviation analysis of five bridge gDTs using an automated twinning method. The micro-level numerical indications show that the deck slab takes the bigger part of the overall deviation whereas the other components such as pier caps, piers, and girders take the smaller part. Specifically, for all these bridges except Bridge 7, the deviations stemming from deck slabs are 2.9, 3.2, 2.1, and 1.5 times bigger than that of the averaged value for the remaining components, respectively. Bridge 7 initially appears misleading since the slab deviations are only 48.8% of that of its girders. However, these abnormal deviations are due to significant occlusions in the raw data. The distribution of the deviations is not necessarily proportional to the LOGA. This can be demonstrated through the coverage area of components. The deck slab takes most of the sampled surface compared to that of the pier caps and piers, which are much smaller in size and in covered area. Specifically, pier caps, piers, and girders take 12, 10.4, 7.2, 31.7, and 15.6% of the overall sampled surface of each bridge, respectively. This means although the absolute twinning accuracy of smaller components is higher than larger ones, their relative accuracy is not necessarily better. A deviation analysis system that combines both macro- and micro-level information can better interpret the twinning accuracy.
|C2C (cm)||Macro  (bridge wise)||Micro (element wise)|
|Bridge 1||4.3||Deck slab||Pier cap 1||Pier cap 2||Pier cap 3||Pier 11||Pier 12||Pier 13||Pier 21||Pier 22||Pier 23||Pier 31||Pier 32||Pier 33||—||—||—||—||—||—||—|
|Area||88.0%||2.2% × 3||0.6% × 9||—||—||—||—||—||—||—|
|Bridge 4||9.4||Deck slab||Pier 11||Pier 12||Pier 13||Pier 14||Pier 15||Pier 16||Pier 21||Pier 22||Pier 23||Pier 24||Pier 25||Pier 26||—||—||—||—||—||—||—|
|Area||89.6%||1%||0.8% × 4||1%||1%||0.8% × 4||1%||—||—||—||—||—||—||—|
|Bridge 6||4.6||Deck slab||Pier 11||Pier 12||Pier 21||Pier 22||Pier 31||Pier 32||—||—||—||—||—||—||—||—||—||—||—||—||—|
|Area||92.8%||1.2% × 6||—||—||—||—||—||—||—||—||—||—||—||—||—|
|Bridge 7||12.5||Deck slab||Pier||Girder 11||Girder 12||Girder 13||Girder 14||Girder 15||Girder 16||Girder 17||Girder 18||Girder 19||Girder 21||Girder 22||Girder 23||Girder 24||Girder 25||Girder 26||Girder 27||Girder 28||Girder 29|
|Area||54.2%||6.2%||2.1% × 9||2.3% × 9|
|Bridge 9||5.6||Deck slab||Pier 11||Pier 12||Pier 21||Pier 22||Pier 31||Pier 32||—||—||—||—||—||—||—||—||—||—||—||—||—|
|Area||84.4%||2.6% × 6||—||—||—||—||—||—||—||—||—||—||—||—||—|
This chapter presents an exploratory analysis of the LOGA of geometric twinning for existing assets using point clouds. Twinning existing assets for monitoring the structural health is a daunting task since the as-is geometric conditions can differ from the designed status due to geometric anomalies, physical damages, deflections, and the complexity, ambiguities, and defects in the measured point cloud data. Section 2.1 reviews existing LOX systems that lack a clear elaboration on geometry accuracy. They share the same acronym but do not necessarily carry the same meaning. They are tailored for basic assumptions made in the design phase or at the beginning of a generative process, making them useless to interpret the as-is geometries of gDTs delivered for SHM purposes. Section 2.2 reviews on industry applications and reveals that there remains a gap between the accuracy requirements placed on gDTs and the capabilities of underlying twinning processes. Specifically, there are practical limitations of authoring tools with respect to the context of orthogonal (i.e. idealised parametric primitives) and real-world deviations (i.e. non-parametric data formats such as point clouds and meshes). Their ability to twin or capture non-rigid-body deformations is extremely limited. Likewise, limitations are also revealed for the deviation evaluation tools with respect to geometric accuracy interpretations. Despite the growing state of the art (Section 2.3), a fully automated twinning and updating process is still in its infancy. A major bottleneck for complete automation of the workflow is the definition of LOGA of the documented asset that covers all geometric deviations and data uncertainties. This requires a development of comprehensive LOGA-based evaluation metrics for gDTs generated in the post-construction stage. The case study (Section 3) demonstrates the technical challenges of the twinning process. High-fidelity twinning within millimetre-level geometric accuracy is challenging to achieve because each step introduces errors. This requires in-depth research on the level of the model certainty. LOGA is closely related to the tools, techniques, and process used to represent the specific object being documented. In the end, the twinning method and LOGA depend highly on what the gDT will be used for (Section 4), on the specific needs and goals of the project, and what kind of metadata is required when providing information about the geometric accuracy.
Parameterising point cloud data results in a loss of geometric accuracy along with a decrease of model certainty. This requires practitioners and researchers to effectively communicate the LOGA through a universal consensus before developing, evaluating, and using gDTs. Until there is a consensus and a universal system for describing geometric accuracy of gDTs, the following recommendations are provided. In the case where geometric accuracy requirements are very strict, such as in the O&M stage, it may be useful to store and link the initial as-is captured data along with the resulting gDT. The purpose for this is two-fold. First, it allows for an end-user to view the initial dataset that was used to create the gDT, for conducting its own unique accuracy or structural analysis. Storing the initial raw point cloud data will provide a level of confidence to an end-user when they use the geometric information from a gDT. It also alleviates some of the burden placed on individuals who create the gDT to provide a subjective global accuracy figure (which can have legal impacts depending on end-use of such gDTs). Secondly, linking the initial data capture avoids loss of geometric data. Since point cloud data contains much rawer geometric information than a resulting surface-based or solid-based gDT, data fidelity can be preserved. As twinning processes and algorithms continue to develop and improve (both in accuracy but also in computational efficiency) it will be possible to build, update, manage, and exploit gDTs in a progressive manner.
This research work is supported by the National Sciences and Engineering Research Council (NSERC), Mitacs and Edge Architects Ltd. and Cambridge Trimble Fund. We would like to thank them for their support. We also acknowledge Faro Technologies for their in-kind support, provision of sample point cloud data and access to BuildIT Construction software. Any opinions, findings, and conclusions or recommendations expressed in this work are those of the authors and do not necessarily reflect the views of the stakeholders who have supported this research.