Service

Industrial data governance

We give plant data a naming scheme, an owner and access rules. The same signal carries the same name in every system, and who can see or change what is clearly defined.

Let's talk about your project → What we deliver

Our clients

Siemens
Anadolu Isuzu
BSH
Tofaş
Toyotetsu
Martur
Turkcell
Vodafone
Doğadan
Pakmaya
Bross
Abdi İbrahim
Nobel İlaç
Plastimak
Dalgıç Kalıp
Barbaros Motor
Magneti Marelli
Rözmaş
Sanel

Industrial data governance is the set of rules that decides how plant data is named, who owns it, who can access it and how its origin is traced. Without it, the same machine has one name in SCADA, another in the MES and a third in the spreadsheet report; OEE has three calculations and meetings are spent arguing about which is right.

We build on the ISA-95 equipment hierarchy: enterprise, site, area, line, work cell and equipment. Tag names follow that hierarchy and are decoupled from raw PLC addresses, so replacing a machine or reprogramming a PLC does not rename anything upstream. The same structure is the foundation of a Unified Namespace (UNS).

The second half of governance is ownership and security. Every data domain has a business owner, and every calculation, such as the OEE formula or energy intensity, has a versioned definition. Access is granted by role, changes are recorded in an audit trail, and the network side is designed with the zones-and-conduits approach of IEC 62443.

What we deliver

Industrial Data Governance

ISA-95 data model

The site, area, line and equipment hierarchy and equipment types are defined. Machines of the same type derive from one template, which makes their data comparable.
Tag naming standard

Naming rules become a written standard covering hierarchy, separators, abbreviations and units. Whoever adds the next machine, the result is the same.
Data dictionary and ownership

Meaning, unit, source and owner of every signal and derived KPI live in a data dictionary. When a definition changes, its version changes too.
Role-based access and audit trail

Separate roles are defined for operators, supervisors, maintenance, quality and IT. Every change to configuration and data is logged with who, when and what.
Lineage

Any number in a report can be traced back to the machine, signal and calculation it came from. That is what auditors and troubleshooters need.
IT/OT security

The OT network is split into zones with defined conduits between them. Data flows outward; there is no direct path from outside into control systems.

How a project runs

From discovery to live, step by step

01
Current-state review

Existing systems, naming habits, reports and competing calculations of the same KPI are inventoried. Conflicts and gaps are listed.
02
Model and standards

The ISA-95 hierarchy, naming standard, data dictionary and role structure are written with representatives from production, IT and quality.
03
Apply on the platform

The model, templates, permissions and audit trail are implemented in Proxus. Existing tags are mapped and migrated to the new names.
04
Keep it alive

A process for adding machines and KPIs is defined and owners are assigned. The standard is handed over as a document the plant team can apply on its own.

Built on Proxus

In Proxus the data model is held as a Unified Namespace: ISA-95 hierarchy, equipment templates, role-based access and audit trail are built into the platform. The model stays on the customer’s own servers and under their control.

Proxus is the industrial data platform built by the VOLSOFT team.

Proxus Unified Namespace ↗

Frequently asked questions

Common questions

What is industrial data governance?

Industrial data governance is defining and enforcing how production data is named, owned, accessed and traced. Its goal is that the same data means the same thing in every system and can be shared safely. As data collection scales, data without governance quickly becomes untrustworthy.

What is ISA-95 used for?

ISA-95 is the international standard that defines the levels and data exchange between enterprise systems (ERP) and manufacturing systems (MES, SCADA, control). Its equipment hierarchy of enterprise, site, area, line and equipment is the common language of plant data models and Unified Namespace designs.

What makes a good tag naming convention?

A good convention is hierarchical, independent of raw PLC addresses and explicit about units. The order of site, line, machine and signal is fixed and abbreviations come from a controlled list. Above all, it must be written down and actually applied whenever a machine is added.

Who should own plant data?

Each data domain should have a named business owner, typically production for output and downtime, maintenance for asset health and energy management for consumption. IT and OT own the platform and security, not the meaning of the data. Clear ownership is what keeps definitions from drifting.