Connecting multiple PLCs through OPC UA does not by itself create a common meaning. An information model turns vendor-specific addresses into governed objects, types, relationships, units, states and semantic identifiers so applications and people can interpret the same machine or process concept consistently.
The short answer
Begin with use cases and stable domain concepts, not a flat tag export. Reuse the OPC UA base model and applicable Companion Specifications before creating custom types. Define namespace ownership and versioning, ObjectTypes, VariableTypes, DataTypes, references, engineering units, ranges, states, quality and optionality. Map each vendor source explicitly to the semantic node and retain source address, transformation, timestamp and quality rules. Publish machine-readable model artifacts where appropriate, test browse paths and type conformance with representative clients, and control compatible versus breaking changes across server, gateway and consuming applications.
- Model domain meaning independently from one controller address or vendor naming convention.
- Reuse standard types and Companion Specifications where they fit the actual use case.
- Give every namespace and type a version owner and change policy.
- Test semantics, units, state behavior and quality—not only successful reads.
Decision guide
| Layer | Purpose | Evidence |
|---|---|---|
| Source mapping | Connect PLC address and raw representation to the governed concept | Mapping table, conversion, time and quality rules |
| Type model | Define reusable assets, variables, methods, events and relationships | NodeSet/type definition and modelling decisions |
| Instance model | Represent this line, machine and equipment hierarchy | Browse paths, identifiers and instance conformance test |
| Lifecycle | Keep producers and consumers compatible through change | Namespace version, change log, compatibility and migration test |
A practical workflow
- 01
Define consumers, questions, commands prohibited or allowed, latency and lifecycle requirements.
- 02
Inventory source data and identify stable domain entities, properties, states and relationships.
- 03
Select base and Companion models, then design only the necessary custom namespace and types.
- 04
Build governed mappings with units, conversions, timestamps, quality and missing-data behavior.
- 05
Validate with representative servers and clients; publish version, owner, changes and migration evidence.
Evidence and acceptance
Keep use cases, system and responsibility boundary, namespace URI/version/publication date, reused specifications, modelling rules, type and instance diagrams, NodeSet or equivalent artifact, source-to-node mapping, units and conversions, identifier policy, timestamp/quality behavior, access constraints, client/server versions, conformance cases, exceptions, change log, approval, deployment baseline and consumer migration record.
Common mistakes
- Mirroring PLC tags into folders and calling the result an information model.
- Creating custom types where a suitable standard or Companion model already exists.
- Using display names as stable identifiers or embedding one vendor’s addresses in consuming applications.
- Changing namespace semantics without versioning and consumer impact analysis.
- Testing that values are readable but not their units, states, quality and relationships.
Responsibility boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Is an OPC UA tag tree an information model?
Not necessarily. A useful model defines types, relationships, semantics, units, identity and lifecycle beyond a browsable list.
Should every project create a custom namespace?
Only when the required concepts are not adequately covered by the base model or an applicable Companion Specification.
Can the same model hide every vendor difference?
It can normalize agreed meaning, but source capability, timing, quality and behavior still need explicit mappings and exceptions.
Does AutoNexit host the OPC UA model?
No. It can preserve the controlled engineering record, while OPC UA products serve and consume the model.