As industrial products become more automated, their engineering models must account for more than component geometry and design data. They also need to represent the relationships, decisions, operating conditions, and experience that influence how a product is developed and used. An organized content model (OCM) is a proposed way to manage this context and connect an engineering model system (EMS) with a product operating as a cyber-physical system (CPS).
The practical challenge is keeping virtual product definitions consistent with changing physical configurations, control software, sensor information, and human decisions. OCM is intended to organize the knowledge that drives model parameters and supports lifecycle engineering, including situation-aware operation.
Why system-level engineering needs contextual links
Complex industrial products are multidisciplinary systems, often composed of many interacting mechanical, electrical, electronic, and software elements. Their engineering models must support requirements, functional behavior, logical relationships, and physical implementation—not just a collection of isolated parts.
A common structure for this work is RFLP: requirements, functional, logical, and physical. In this arrangement, requirements inform functions; functions inform logical components; and logical components inform physical components. Contextual links help carry relevant information and decisions between these levels, as well as between objects within each level.
In a highly automated product, however, important context also comes from outside the engineering model. Sources may include authorized operator actions, engineering decisions, laws and standards, intellectual property, and experience from earlier lifecycle stages. The operating product can also return information, such as sensed parameter values and processed experience. Without a coordinated way to manage these relationships, a locally correct model change may not remain consistent with the wider system.
How an organized content model connects the system
OCM is designed to fill the gap between external context and the product model, while also linking the virtual model to the cyber units of the physical product. The broader concept is an extended product system (EPS): the product model system and the field-operating CPS interact and are updated in relation to one another across the lifecycle.
Here, “driving” means setting an object parameter using values from related parameters through defined contextual connections. OCM organizes the content behind those connections. Rather than managing every relationship as a direct, manual link, it provides structured content that can be used to define or update relevant model elements and their parameters.
Context may represent information, knowledge, or experience. Information can establish what is happening and where; knowledge can help represent how a process or response should work. The source concept also identifies why a decision was made as an important question, while recognizing that representing this kind of understanding remains an area for further research.
Managing context through controlled changes
For OCM to support continuous engineering, newly received context must be checked and coordinated with existing model relationships. A proposed context-handling process includes several stages:
- Check eligibility: Assess whether an incoming item can be considered under the protocols used in the engineering environment.
- Identify its role: Determine which aspects and OCM elements the context relates to, then transform it into a form suitable for those elements.
- Check correctness and conformity: Test the item against applicable requirements and against related, already active contexts. A context can be correct on its own yet conflict with another part of the system.
- Resolve issues: Reject clearly erroneous items, notify their owners, and refer disputed or conflicting cases to responsible people or higher-level decision-making.
- Assess downstream effects: Review how an accepted change affects linked elements and parameters throughout relevant contextual chains.
- Activate approved connections: Once accepted, connect the context to the relevant engineering model elements with the appropriate driving effect.
This discipline matters because a new or modified context may require changes to relationships—or even revisions to previously accepted content. The aim is not to automate every judgment, but to keep changes visible, assessed, and coordinated across the system.
OCM and situation awareness in CPS products
The proposed OCM structure organizes content across five levels: construction, behavior, systems, control, and human aspects. Together, these levels address how a product model is built, how it behaves, how its component systems interact, how equipment and devices are controlled, and how people connect with the operating system.
Situation awareness is relevant to both autonomous functions and the people responsible for overseeing them. In the proposed approach, context about circumstances can support situation recognition, while control-related content connects equipment, procedures, and sensed values. Human-related content can organize phenomena, possible interventions, and experience from previous cases—including both successful and unsuccessful interventions.
This structure is intended to support communication between OCM, the product model, and CPS cyber units. Cyber units use sensor information and decision processes to control physical actions. If a malfunction alert or an uncertain situation calls for human intervention, organized contextual information may also help an operator understand the situation and consider prior experience. Human oversight remains important, particularly where an autonomous decision needs correction.
Implementation considerations for engineering teams
OCM is a modeling approach, not a substitute for a capable engineering platform or sound governance. Its implementation depends on a platform that can represent the required system-level models, contextual relationships, and lifecycle changes. Restricting modeling capabilities can limit the content available to engineers and weaken the consistency of the resulting model.
Teams also need clear protocols for accepting, checking, and resolving context. This includes assigning responsibility for decisions, recording context status, and providing a path for disputed items. As products and their models change, continuous engineering processes can help evaluate the consequences of model or software modifications; the OCM concept depends on keeping relevant content current over the product lifecycle.
Practical implications
For industrial automation engineers, system integrators, and operations leaders, the central idea is that model integration depends on more than connecting engineering tools or exchanging parameter values. Teams also need to manage why those values and relationships apply, what other decisions they depend on, and how they change as the physical system evolves.
An organized content model offers a structured approach to that work by connecting contextual knowledge with RFLP product models, CPS control functions, and human oversight. It is a demanding lifecycle practice, requiring appropriate platforms, disciplined review, and continuing engineering effort. Applied as intended, it can help teams reason about system-wide effects and maintain alignment between virtual product definitions and operating systems as requirements and conditions change.
Access Official Technical PDF