Table 8. Summarizes respondents’... | Emerald Publishing

Table 8.

Summarizes respondents’ definitions of DT

Respondent	Section	Definition of DT
R1	1.0	Views DT as a tool to improve workflow, enhance visualization and collaboration, support maintenance planning and enable PdM, while noting challenges with formats and standards
R2	1.0	Sees DT as a way to integrate and visualize data from multiple systems to optimize operations, reduce error reports and enhance customer interaction – highlighting the need for quality-assured data, proper infrastructure and seamless information flow from project to operation
R3	1.0	Believes a true DT must include data and sensors. They highlight its potential to improve maintenance planning, centralize scattered data, enhance stakeholder understanding, support onboarding and scale property management, while emphasizing the need for better data quality, BIM handling and change management
R4	1.0	Describes DT primarily as visualization tools without built-in intelligence, used to display sensor and control system data. They note the potential for integrating BIM and showing component relationships, but emphasize challenges in defining value and fully utilizing data-driven capabilities
R5	1.0	Defines the DT mainly as a tool for tracking spatial placement and surfaces, emphasizing its current role in visualization. While they envision future integration of AI and sensor data, their present use focuses on managing spatial information
R6	2.0	Views the DT as a methodology, a way of working to create a digital counterpart of a physical asset by integrating data from different system silos to enable improved analysis and management. Visualization is part of it, but not the core definition
R7	2.0	Finds it difficult to define a DT, especially distinguishing it from advanced BIM or three-dimensional models. However, they believe that real DT must include data and sensors to qualify
R8	2.0	Offers a conceptual view of DT, defining them as the integration of three data types: issue reports, object data and product data, necessary for lifecycle analysis and PdM. They emphasize that maintaining and updating these data sets forms the core of a DT
R9	2.0	Sees the DT as a centralized digital representation of a building that collects and structures data from sources like BIM and sensors. It is used to visualize spatial information, display real-time data and support troubleshooting by linking issues to physical locations and systems

Respondent	Section	Definition of DT
R1	1.0	Views DT as a tool to improve workflow, enhance visualization and collaboration, support maintenance planning and enable PdM, while noting challenges with formats and standards
R2	1.0	Sees DT as a way to integrate and visualize data from multiple systems to optimize operations, reduce error reports and enhance customer interaction – highlighting the need for quality-assured data, proper infrastructure and seamless information flow from project to operation
R3	1.0	Believes a true DT must include data and sensors. They highlight its potential to improve maintenance planning, centralize scattered data, enhance stakeholder understanding, support onboarding and scale property management, while emphasizing the need for better data quality, BIM handling and change management
R4	1.0	Describes DT primarily as visualization tools without built-in intelligence, used to display sensor and control system data. They note the potential for integrating BIM and showing component relationships, but emphasize challenges in defining value and fully utilizing data-driven capabilities
R5	1.0	Defines the DT mainly as a tool for tracking spatial placement and surfaces, emphasizing its current role in visualization. While they envision future integration of AI and sensor data, their present use focuses on managing spatial information
R6	2.0	Views the DT as a methodology, a way of working to create a digital counterpart of a physical asset by integrating data from different system silos to enable improved analysis and management. Visualization is part of it, but not the core definition
R7	2.0	Finds it difficult to define a DT, especially distinguishing it from advanced BIM or three-dimensional models. However, they believe that real DT must include data and sensors to qualify
R8	2.0	Offers a conceptual view of DT, defining them as the integration of three data types: issue reports, object data and product data, necessary for lifecycle analysis and PdM. They emphasize that maintaining and updating these data sets forms the core of a DT
R9	2.0	Sees the DT as a centralized digital representation of a building that collects and structures data from sources like BIM and sensors. It is used to visualize spatial information, display real-time data and support troubleshooting by linking issues to physical locations and systems

Source(s): Authors’ own work