PSI - Issue 84

Adriana Marra et al. / Procedia Structural Integrity 84 (2026) 661–668

665

model, facilitating data management, querying, and traceability. The final structure of the database is organized into several tables that represent the various information components outlined in the Guidelines. These tables are interconnected by unique identification codes (see Fig. 3a). Specifically, the Asset Manager Structure ID connects the Census and Element Detail tables, facilitating centralized management of comprehensive data related to the structure and its components. The Asset Manager Component ID (Local) field links the Element Detail and Inspection tables, enabling the connection of each structural element with inspections performed over time. Additionally, the Inspection table has been linked to the Defect Code table through the Defect Type field. This connection automatically associates the defect type with anomaly description and the relative weights, as required by the regulatory frameworks. The creation of structured relationships between the different tables enabled to take advantage of the Lookup features offered by the NocoDB platform (see Fig. 3b). These features are useful for automatically compiling recurring information (e.g., defect codes, G weight, anomaly description), which helps reduce redundancy and minimize the risk of compilation errors. Additionally, formula fields were implemented to automatically calculate derived indicators, such as the relative defect index obtained by combining the values of G, k1, and k2 according to formulas specified by the regulations. This process led to the definition of a coherent, relational, and easily queryable information environment, which serves as the starting point for semi-automatic BrIM model updates and dynamic assessment of the elements' defect level and the structural and foundation AC.

Fig. 3. (a) Diagram of the relationships between tables in the NocoDB relational database. (b) View of Inspection form.

3.2. BrIM model validation and optimization

The second phase of the workflow involved verifying and optimizing the structure's BrIM model, previously created with Autodesk Revit to represent the bridge's geometric and structural characteristics, as well as to facilitate its analysis and understanding. This step aimed to ensure the full interoperability between the model and the relational database and to align the information structure with the IFC Guidelines for Bridges and Viaducts (GdL IFC Bridge Italia 2020). This operation was crucial for exporting the BrIM model according to the IFC standard and aligning the modeled elements with the digitized data in the tables. First, the geometric and semantic consistency of the modeled elements was checked with respect to the IFC classes and subclasses provided for infrastructure works, through systematic mapping of the components and their attributes. This process helped identify inconsistencies in the original