# BIM-GIS-Based Approach for Quality Management Aligned with ISO 9001
## 5 Results
### Linking Quality Inspection Results to the BIM Model  
After the inspection, the recorded data were synchronized from QFieldCloud and retrieved in QGIS. The synchronization procedure consisted of updating the local storage while turning off the cloud layer to ensure the correct project version was selected. Details of this process are provided in Figure A6. The updated inspection layer was then exported to an Excel spreadsheet in XLSX format, preserving the structure of the attribute data for integration into the BIM model. This export required the definition of a sheet name and file name, which remain fixed to allow consistent data linkage in future synchronizations. The configuration steps and resulting file are shown in Figure A7. The integration into the BIM environment was carried out through a Dynamo routine composed of five sequential steps: (1) Inspection form data import, (2) Creation of shared parameters, (3) Creation and assignment of cube family, (4) Filling cubes parameters, and (5) Filling walls parameters. Figure 11 presents the complete routine, which will be executed according to the order given by the numbers. Step (1) begins with the import of the XLSX file generated in QGIS, which contains the completed inspection records. The file is read from the computer's local storage, and the data are parsed into three separate lists: the names of the attributes, the geographic coordinates of the inspection points, and the corresponding attribute values. The coordinate values are then reformatted to align with the Revit coordinate system, ensuring consistency between GIS and BIM environments. In step (2), a set of shared parameters is created within the BIM model. These parameters are labeled according to the fields defined in the digital inspection form and will serve as the repository for the incoming data. Step (3) involves generating and placing a generic Revit family configured as a cube at each inspection point. These cube instances are positioned using only the X and Y coordinates, while the Z coordinate is set to a fixed elevation. This simplification was necessary because the inspection form does not include height information, and the method is based on a two-dimensional plan view. As a result, the cube positions reflect the horizontal location of each inspected element, but not its vertical placement within the building. This may lead to overlaps in cases where elements share the same X and Y position at various heights (for example, beams and walls aligned vertically). To address the risk of data duplication, the routine includes a sub-process that automatically deletes  
Figure 11: Entire Dynamo routine, organized in five steps. any previously placed cubes before generating new ones. This ensures that every update reflects only the most recent inspection data. The spatial distribution of the cube instances across the floor plan is shown in Figure A8. In step (4), the attribute values are written into the shared parameters of each cube, effectively associating the inspection data with the corresponding spatial location. Intersections between the cubes and wall elements are then identified. Two mapping lists are generated based on these intersections: one for the cubes and one for the walls. Finally, in step (5), the inspection values stored in the cube instances are transferred to the corresponding wall elements through the intersection mapping. As a result, each wall included in the inspection process receives the attribute data collected in the field, stored as shared parameters within the BIM model. As each wall progresses through its respective inspection phases, the parameters stored in the BIM model are progressively updated. These records reflect the specific status of each control activity performed in the field. Figure 12 illustrates a Revit properties panel displaying the quality parameters assigned to a wall element after completing all control phases.