No. ISO 22400 does not prescribe a specific database schema or physical data model.
What ISO 22400 actually provides
ISO 22400 is a family of standards for manufacturing operations management metrics. It focuses on:
- Common terminology for KPIs and their components
- Conceptual data structures and relationships (e.g., how events, time, resources, and quantities relate)
- Calculation logic and definitions for metrics such as OEE and related indicators
These are conceptual and logical views, not implementation-level database designs.
What remains your responsibility
Your organization (or your vendors/integration partners) must still:
- Design the physical database schema in your chosen technology (relational, time-series, historian, data lake, etc.).
- Map ISO 22400 concepts (e.g., equipment, shifts, states, production orders, loss categories) to actual tables, fields, and relationships.
- Align the schema with existing MES, ERP, historian, and QMS models so that KPIs can be computed consistently without breaking current integrations.
- Ensure traceability, versioning, and change control for schema changes, consistent with your validation and qualification practices.
ISO 22400 can guide what needs to be represented and how to interpret it, but not how to implement it technically.
Brownfield and integration considerations
In a typical brownfield environment, you will not replace existing schemas wholesale just to align to ISO 22400. Full replacement often fails or is rejected because of:
- Qualification and validation burden for changing MES/ERP/QMS data models.
- Downtime risk for schema migrations across multiple plants and vendors.
- Integration complexity with legacy systems, custom reports, and regulatory evidence chains.
- Traceability impact if historical data structures change without robust governance.
A more practical pattern is to:
- Keep core operational schemas largely intact.
- Add integration/semantic layers, views, or derived tables that reflect ISO 22400 concepts for KPI computation and analytics.
- Progressively align naming, data types, and event definitions to move closer to the standard over time.
Constraints in regulated environments
For regulated or aerospace-grade environments, any ISO 22400-aligned schema work should be treated as a controlled change:
- Document how ISO 22400 concepts map to your actual data structures.
- Validate KPI calculations and queries against reference scenarios and legacy reports.
- Preserve audit trails and ensure that any new schema or views do not compromise existing evidence needed for inspections or customer audits.
The standard can support more consistent and explainable KPIs, but it does not remove the need for careful design, validation, and coexistence with your existing data models.
