Give industrial data its operating meaning

Model how the operation actually works

Core represents industrial behavior and relationships, rather than relying on tag names alone. Equipment has specifications and changing states; processes depend on upstream and downstream conditions; materials move, combine and separate. These relationships determine how records can be interpreted and used.

The same record can support multiple applications. Equipment, material and inspection records may contribute to quality investigation, maintenance and energy analysis, each using its own professional methods.

Which site and business records can be used

Inputs are not limited to sensors. Select real-time and historical states, equipment specifications and configuration, production batches and quality tests, maintenance records, and relevant orders, schedules and costs for the task. Sources may include equipment and controls, existing platforms, databases and exported files.

Check interfaces, coverage and permissions. High-frequency signals may need edge processing. Suitable soft sensors can estimate some unmeasured states, but estimates are not measurements, and software cannot repair incorrect wiring or faulty instruments.

Define what similarly named data actually means

An energy value may be a cumulative meter reading or interval consumption; temperature may refer to different components and sampling methods. A data dictionary records names, units, boundaries and sampling meaning. Consistent definitions support aggregation, comparison and model use while retaining source-system information.

Put related records in the right time window

Arrival time is not necessarily the time an event occurred in the process, nor does it necessarily identify the same material batch. During ongoing operation, retain source, sampling and processing times, and relate records through material flow, equipment response or business cycles. Current load, later quality results and earlier actions can then be compared in sequence.

Show data quality alongside the records

Missing or stale records, or changes in units, affect calculations. Retain these conditions with the source data so users can see its coverage. If a key input is absent, obtain site records or narrow the analysis. Update calculations after reconnection, keeping estimates distinct from measurements.

Reuse facts and calculations across applications

Data definitions, object relationships and shared calculation methods provide reusable building blocks. Task-specific models and applications use those blocks while retaining the units, operating conditions and dependencies needed for their results.

Customers and partners can add their own models and applications. Existing data platforms can continue to hold and supply records; useful information does not have to be duplicated into a new database before it can be used.

For your deployment