Digital twin without quality telemetry: Why projects fail

Digital twin projects often fall short of expected ROI due to poor data quality. Insufficient attention to semantic models, timestamp accuracy, quality flags, and data ownership turns the twin into a source of flawed decisions.

Why 'data exists' doesn't mean 'data is usable': Bridging the gap between raw data and business value

Digital twins promise production optimization, predictive maintenance, and accelerated innovation. However, up to 75% of projects fail to deliver the expected Return on Investment (ROI) due to weak data layers. The core issue isn't merely the absence of data, but its unsuitability for use. Raw data from IoT devices, even in vast quantities, doesn't automatically translate into value without proper structure and context.

Poor data quality is the Achilles' heel for digital twins. Fragmented sources, inconsistent or incomplete data, and delays in data pipelines all contribute to the twin becoming little more than a static model with limited decision-making value. The volume of data generated annually is expected to double from 2021 to 2026, a trend that could exacerbate the situation as data quality typically degrades with increasing volume.

Semantic model: The foundation that defines data meaning

A semantic model is critically important for providing context to IoT data and ensuring its interoperability. Without clear definitions, units of measurement, and relationships between entities, data remains a collection of numbers, unsuitable for modeling and analysis. For example, 'temperature 25' without specifying units (°C or °F) or location (room, engine) is meaningless for a digital twin.

Standards like Microsoft Azure Digital Twins' Digital Twins Definition Language (DTDL) allow for creating custom models to describe entities in the physical environment, defining their properties, components, and relationships. DTDL is based on JSON-LD and is language-agnostic, promoting model reuse and scalability. The Digital Twin Consortium also emphasizes the importance of semantic interoperability for successful digital twin development.

Timestamp accuracy and synchronization: When 'almost simultaneous' ruins analytics

Accurate and synchronized timestamps are fundamental for correct event analysis and reality replication in a digital twin. Inaccurate or unsynchronized timestamps lead to incorrect correlations, erroneous conclusions, and the inability to reconstruct event sequences. In industrial environments, network instability can disrupt clock synchronization, making timestamps unreliable. Even battery-powered IoT devices can drift up to one second per day without regular NTP synchronization.

For distributed IoT systems, it's critical to use time synchronization protocols such as Network Time Protocol (NTP) or Precision Time Protocol (PTP) to ensure millisecond accuracy. Without this, for instance, in energy monitoring systems, simultaneous readings from different sensors might be interpreted as time-separated, leading to incorrect calculations and decisions.

Data quality flags: Trusting numbers or blind faith?

Metadata about the quality of each measurement, known as data quality flags, is indispensable for assessing the reliability of information flowing into the digital twin. These flags can indicate states such as 'sensor faulty,' 'data missing,' 'out of range,' 'stale,' or 'calibration overdue.' The absence of such indicators forces digital twin models to use incorrect data, leading to flawed predictions and decisions.

For example, in industrial systems, OPC UA quality codes are used to denote data status. Quality flags help identify issues like duplicates, calculation errors, date problems, or significant deviations from previous values. Monitoring data freshness is also crucial: a device that has stopped sending data might be more significant than one sending an anomalous value.

Ownership and acceptance criteria: Who is responsible for data quality and what is considered 'sufficient'?

Technical solutions for data quality are doomed to fail without clearly defined organizational roles and responsibilities. The absence of a clear data owner, responsible for data quality, and vague data acceptance criteria lead to unaccountability and ignored problems. In the context of IoT, Data Governance must encompass device registries, schema versions, location hierarchy, asset mapping, data storage, access control, and quality thresholds.

Legal aspects of data ownership are also complex, as digital twins integrate data from multiple stakeholders, including developers, manufacturers, and data providers. It's crucial to define these issues early in the project, documenting them in contracts, to avoid unpleasant surprises. Without this, even the most sophisticated technology can become an 'empty shell.'

Investing in telemetry quality: From cost to strategic advantage

Investing in a quality telemetry model is not an additional expense but a critical condition for the success of a digital twin project. Organizations with robust data collection systems and high-quality operational data can implement digital twins faster and achieve greater accuracy in their virtual models. Poor data quality increases implementation costs and can limit the accuracy of optimization recommendations.

Digital twin projects that account for the cost of rectifying poor data have a more honest budget and a correct work sequence. Companies with significant data governance in their digital twins reduce time-to-market by up to 50% and improve product quality by 25%. This underscores that data quality is a key factor in transforming a digital twin into a strategic advantage.

Practical checklist for assessing telemetry readiness for a digital twin

CriterionYes/NoComment
Is there a formalized semantic model for all data sources?
Are units of measurement and ranges defined for each parameter?
Is timestamp synchronization ensured with millisecond accuracy (or according to scenario requirements)?
Is each measurement accompanied by a data quality flag?
Are clear roles and responsibilities for data quality defined (data ownership)?
Are there acceptance criteria for data entering the digital twin?
Are there mechanisms for data validation and cleansing before use in the twin?
Is regular data quality auditing performed?
Is there an action plan in case of poor data detection?
Does the team understand the impact of poor data on business decisions?

The AZIOT platform provides tools for building flexible semantic models, integrating data from diverse sources with support for precise timestamps and validation mechanisms. This allows CTO/data lead teams to focus on the business logic of digital twins, minimizing risks associated with telemetry quality. Intecracy solutions and inbase.com.ua solutions.

The success of a digital twin depends on the foundation upon which it is built. This foundation is a high-quality telemetry model. Ignoring this aspect will inevitably lead to project stagnation, turning potential benefits into significant losses. Invest in data quality today to ensure the reliability and value of your digital twin tomorrow.

Source list

  1. context-clue.comWhy Digital Twin Projects Fail And How to Fix the Data Layer
  2. hopara.ioSolving Telemetry Data Visualization Challenges in Digital Twins
  3. itbrief.co.ukDon't allow bad data to ruin your digital twin plans
  4. mdpi.com
  5. ericsson.com
  6. ceur-ws.org
  7. upc.edu
  8. xenonstack.comUnderstanding Microsoft Azure Digital Twin Platform and Its Benefits