data integrity

Core meaning

Data integrity commonly refers to the degree to which data is complete, accurate, consistent, and reliable across its entire lifecycle. In industrial and regulated manufacturing environments, it describes the trustworthiness of data used to plan, execute, monitor, and release production and quality activities.

It focuses on whether data correctly reflects what actually happened and whether it can be relied on for decisions, records, and investigations.

Key characteristics in manufacturing systems

Data integrity in operations and manufacturing IT/OT systems typically involves:

– **Accuracy**: Data correctly represents the underlying event or measurement (for example, a temperature reading matches the actual process temperature within defined limits).
– **Completeness**: All required data is captured (for example, every batch step has a timestamp, operator, and result recorded).
– **Consistency**: Data values and formats align across systems and over time (for example, the same batch ID and result in MES, historians, and quality systems).
– **Attributability**: It is clear who or what created, modified, or approved data (for example, user accounts tied to individuals, system IDs tied to specific equipment).
– **Traceability**: The history of data creation, changes, and usage can be reconstructed (for example, audit trails, version history, and event logs).
– **Timeliness**: Data is recorded at the time of the activity or within a defined, controlled delay.
– **Protection from loss or corruption**: Technical and procedural controls prevent unauthorized change, deletion, or distortion (for example, backups, access controls, and integrity checks).

How the term is used in real workflows

In regulated and industrial operations, data integrity is discussed when:

– Designing or validating **MES, LIMS, historians, and ERP integrations**, to ensure that data is not altered, dropped, or misaligned between systems.
– Configuring **equipment interfaces** (PLCs, SCADA, edge gateways) so that sensor data, setpoints, and results are reliably captured and reconciled.
– Establishing **electronic batch records** and quality records to ensure that the documented history of a batch or lot is trustworthy.
– Setting up **user management, access control, and audit trails** to link actions to specific users or systems.
– Performing **deviations, investigations, and root cause analysis**, where the reliability of logs and records directly affects conclusions.

In these contexts, data integrity is treated as a property of both the technical design (architecture, interfaces, storage) and the operational controls (procedures, governance, and training).

Boundaries and exclusions

Data integrity:

– **Includes**: How data is captured, transformed, stored, transmitted, retrieved, and retired across OT and IT systems and manual processes.
– **Includes**: Controls that prevent or detect unauthorized or unintended data creation, modification, or deletion.
– **Does not inherently include**: Overall system security or cybersecurity strategy, although security controls strongly influence data integrity.
– **Does not equal**: Data quality projects focused only on analytics normalization or reporting aesthetics; data integrity is about trustworthy, faithful records of operations.

Common confusion and related terms

– **Data integrity vs data quality**: Data quality often addresses usefulness for reporting or analytics (for example, standardized codes, completeness for KPIs). Data integrity focuses on whether records truthfully and reliably represent actual events and can be trusted in audits, releases, and investigations. In regulated environments, data integrity is usually treated as more fundamental.
– **Data integrity vs system validation**: System validation assesses and documents that a computerized system does what it is intended to do. Data integrity is one of the properties expected from a properly validated system but is not the same as validation itself.
– **Data integrity vs cybersecurity**: Cybersecurity protects systems and data from malicious or unauthorized access. Data integrity overlaps with this domain but also covers non-malicious issues such as configuration errors, interface mapping mistakes, and uncontrolled manual edits.

Site context: data integrity in MES and equipment integration

When integrating MES with special process equipment and other OT systems, data integrity considerations typically include:

– Ensuring **unambiguous mapping** between equipment signals, tags, or data points and MES data structures (for example, operations, parameters, and materials).
– Designing **interfaces and edge gateways** so that data is not lost during communication outages, buffering, or protocol translation.
– Preserving **original source data** (for example, raw values and timestamps from equipment) alongside any calculated or summarized values in MES or historians.
– Implementing **audit trails and event logs** that show when data was collected, transferred, or modified, and by which system or user.
– Coordinating **time synchronization** across PLCs, data historians, MES, and ERP so that sequences of events can be reconstructed accurately.

In this setting, discussions of data integrity often drive choices between direct equipment integration, use of gateways, or relying on procedural/manual data capture where automated capture is not feasible or would impose excessive validation burden.