Glossary · Semantic interoperability and information models
Type model
German: Typmodell
In information modeling, a type model defines reusable types, such as device types, object types or data types, with their structure, properties and behavior, from which concrete instances are created. OPC UA ObjectTypes and the AAS distinction between asset type and asset instance are examples.
- Information models
In one sentence
A type model defines reusable types, such as device or object types, with their structure and properties, from which instances are created.
Example
An OPC UA type model defines a PumpType with flow, pressure and a Start method; each pump in the plant is an instance of this type.
How it applies
- Engineering: Type models make engineering efficient: changes to a type propagate to all instances, and clients can process all instances of a type the same way.
- Lifecycle: In Industrie 4.0, type information (valid for all units of a product type) and instance information (valid for one unit, such as serial number and maintenance history) are managed separately.
- Documentation: Most technical documentation describes a product type; some information, such as test certificates or as-built configurations, belongs to an instance. Metadata should make the difference clear.
Type model vs. class model
The terms overlap. Class model is the usual term in object-oriented software and UML; type model is common in OPC UA and product information management. Both describe templates for instances, not the instances themselves.