Glossary · Semantic interoperability and information models
Canonical model
Also known as: Canonical data model
German: Kanonisches Modell
In system integration, a canonical model is a shared, application-independent data model that all connected systems map to and from, so that each system needs only one mapping to the common model instead of separate mappings to every other system.
- Information models
In one sentence
A canonical model is a shared data model that all integrated systems map to, avoiding a separate mapping between every pair of systems.
Example
A manufacturer defines a canonical model for production orders; ERP, MES and the warehouse system each translate their own format into it.
How it applies
- Engineering: With n systems, point-to-point integration can need up to n times n minus one mappings; a canonical model reduces this to one mapping per system. Standards such as ISA-95 (B2MML) or OPC UA companion specifications can serve as the canonical model.
- Operation: The canonical model needs an owner and change process, since every change affects all connected systems (Schema governance).
- Documentation: Document the canonical model's entities, attributes, units and code lists in one place, and the mapping of each system to it.
Canonical model vs. information model
An Information model describes the concepts of a domain independent of technology. A canonical model is a concrete, agreed data model used as the common exchange format in an integration architecture. A canonical model is often derived from an information model.