Comprehensive thematic analysis showing themes, strategic elements, verbatim quotes and conclusion
| Theme | Strategic element | Verbatim quote (R#) | Conclusion |
|---|---|---|---|
| Predictive maintenance | Condition-based maintenance | “You might also talk about that you can somehow change not based on service intervals but look at whether there are behaviors that start to change if an elevator vibrates abnormally…” (R3) | Predictive maintenance requires moving beyond fixed intervals to condition-based strategies |
| Sensor-driven anomaly detection | “If a sensor hasn’t given any value in 48 h… then we should start raising the alarm.” (R4) | Algorithms and sensor data are key for early fault detection | |
| Operational priority | “But keeping track of your components and their condition is probably the most important thing.” (R9) | Maintenance planning must prioritize component condition monitoring | |
| Machine learning for forecasting | “There’s a machine learning model for every building.” (R4) | Advanced analytics will enable proactive maintenance and resource optimization | |
| Organizational readiness | Need for anchoring in operations | “The managers in operations need to kind of understand the point and understand the benefit of this.” (R6) | Operational buy-in is critical for DT success |
| Business case for management buy-in | “Who can make a good business case out of this. And show the CEO and management that this delivers.” (R6) | Clear ROI communication is needed to secure leadership support | |
| Current siloed structure | “Now in our organization we are very much driven by specialist knowledge…” (R1) | Organizational silos hinder integrated DT strategies | |
| Cross-functional teams forming | “We have a team of 12 people. We are essentially very much requirements analysts, project managers, IT architects.” (R3) | Teams exist but need a clearer structure and mandate | |
| Iterative learning and management support | “We have with management the mindset that we do some testing […] not prove everything at once.” (R5) | Management must support incremental and test-driven approaches | |
| Competence development | Need for new roles | “We needed to have someone who is a digital twin, BIM manager.” (R9) | Specialized roles are essential for DT implementation |
| Skills gap in traditional roles | “But these people who have worked with CAD for many years don’t have those skills.” (R9) | Upskilling is required to bridge traditional and digital competencies | |
| Early-stage skill enhancement | “In the early stages […] you need a little more of a domain architect.” (R8) | Architectural and strategic skills are needed early in projects | |
| Internal technical expertise | “We have some guy who sits around and knocks code all the time with our data lake, a real computer nerd.” (R9) | Technical skills exist but are concentrated in a few individuals | |
| Hiring for digital skills | “I think we definitely need to hire some people who have these skills, initially.” (R5) | Organizations recognize the need for new digital competencies | |
| Structured data | Interoperability requirement | “The Three databases need to talk to each other.” (R8) | Data integration is critical for lifecycle analysis and predictive maintenance |
| Importance of structured data | “As long as it’s well-structured data… Then it’s pretty easy to show it.” (R4) | Structured data enables visualization and analytics | |
| Pragmatic approach to data quality | “We say that it is better to map a little that you verify and know is correct than to map everything.” (R9) | Focus on verified core data before scaling DT | |
| Need for aggregation and efficient architecture | “There will be a lot of data, which means we have to build cubes of it to be able to consume it quickly.” (R4) | Scalable data architecture is necessary for real-time insights | |
| Data maturity challenge | “It’s unstructured data. Which you can get help with using AI to structure.” (R2) | AI can assist in structuring legacy data, but foundational work is needed | |
| Long-term vision | Future-oriented planning | “Start small, I would say. And don’t beat the drum.” (R7) | Gradual scaling and pilot projects are preferred over “big bang” approaches |
| Vision of AI integration | “You’ll have a little AI agent that you tell things to.” (R9) | AI-driven decision support is seen as a future enabler for DT | |
| Expectation of structured benefits | “Now we want this and we have seen these benefits. And figure out a business case for this.” (R7) | Clear economic justification is essential for scaling DT | |
| Scalability needs | “How do you keep track of this maintenance? You can’t have 1.2 million square meters in Excel files.” (R7) | Large-scale DT adoption requires robust digital infrastructure | |
| Visionary perspective | “And somewhere up there at the top there’s like being able to use AI. And deep learning to perform smart analyses in different ways.” (R2) | Long-term vision includes AI and advanced analytics for efficiency |
| Theme | Strategic element | Verbatim quote (R#) | Conclusion |
|---|---|---|---|
| Predictive maintenance | Condition-based maintenance | “You might also talk about that you can somehow change not based on service intervals but look at whether there are behaviors that start to change if an elevator vibrates abnormally…” (R3) | Predictive maintenance requires moving beyond fixed intervals to condition-based strategies |
| Sensor-driven anomaly detection | “If a sensor hasn’t given any value in 48 h… then we should start raising the alarm.” (R4) | Algorithms and sensor data are key for early fault detection | |
| Operational priority | “But keeping track of your components and their condition is probably the most important thing.” (R9) | Maintenance planning must prioritize component condition monitoring | |
| Machine learning for forecasting | “There’s a machine learning model for every building.” (R4) | Advanced analytics will enable proactive maintenance and resource optimization | |
| Organizational readiness | Need for anchoring in operations | “The managers in operations need to kind of understand the point and understand the benefit of this.” (R6) | Operational buy-in is critical for |
| Business case for management buy-in | “Who can make a good business case out of this. And show the | Clear | |
| Current siloed structure | “Now in our organization we are very much driven by specialist knowledge…” (R1) | Organizational silos hinder integrated | |
| Cross-functional teams forming | “We have a team of 12 people. We are essentially very much requirements analysts, project managers, | Teams exist but need a clearer structure and mandate | |
| Iterative learning and management support | “We have with management the mindset that we do some testing […] not prove everything at once.” (R5) | Management must support incremental and test-driven approaches | |
| Competence development | Need for new roles | “We needed to have someone who is a digital twin, | Specialized roles are essential for |
| Skills gap in traditional roles | “But these people who have worked with | Upskilling is required to bridge traditional and digital competencies | |
| Early-stage skill enhancement | “In the early stages […] you need a little more of a domain architect.” (R8) | Architectural and strategic skills are needed early in projects | |
| Internal technical expertise | “We have some guy who sits around and knocks code all the time with our data lake, a real computer nerd.” (R9) | Technical skills exist but are concentrated in a few individuals | |
| Hiring for digital skills | “I think we definitely need to hire some people who have these skills, initially.” (R5) | Organizations recognize the need for new digital competencies | |
| Structured data | Interoperability requirement | “The Three databases need to talk to each other.” (R8) | Data integration is critical for lifecycle analysis and predictive maintenance |
| Importance of structured data | “As long as it’s well-structured data… Then it’s pretty easy to show it.” (R4) | Structured data enables visualization and analytics | |
| Pragmatic approach to data quality | “We say that it is better to map a little that you verify and know is correct than to map everything.” (R9) | Focus on verified core data before scaling | |
| Need for aggregation and efficient architecture | “There will be a lot of data, which means we have to build cubes of it to be able to consume it quickly.” (R4) | Scalable data architecture is necessary for real-time insights | |
| Data maturity challenge | “It’s unstructured data. Which you can get help with using | ||
| Long-term vision | Future-oriented planning | “Start small, I would say. And don’t beat the drum.” (R7) | Gradual scaling and pilot projects are preferred over “big bang” approaches |
| Vision of | “You’ll have a little | AI-driven decision support is seen as a future enabler for | |
| Expectation of structured benefits | “Now we want this and we have seen these benefits. And figure out a business case for this.” (R7) | Clear economic justification is essential for scaling | |
| Scalability needs | “How do you keep track of this maintenance? You can’t have 1.2 million square meters in Excel files.” (R7) | Large-scale | |
| Visionary perspective | “And somewhere up there at the top there’s like being able to use | Long-term vision includes |
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.