Models are at the heart of many digital transformation initiatives but models will have impact one way or another on Configuration Management. With the team from the I4.0 Committee of the IPX Congress, I have been discussing the potential impact model-based approaches will have on configuration management. To support us in this discussion and analysis, we have created an overview of the types of models we so far have identified and mapped to the V model for development.
First, let’s look at the definition of a Model:
A digital graphical, conceptual, mathematical, logical, and/or physical construct of a real system, subsystem, or component designed to convey information to humans and machines in order to support activities in the value chain.
Application ModelsModels intended to define, capture, analyze and control requirements and their linkages.
These models can represent specific features, behaviors, or aspects of a system, subsystem, or component to derive and define requirements and verification approaches.
These models can represent items, attributes, EBOM, functionality, 3D geometry, processes, software models (UML), etc.
Also referred to as: As Designed / As Engineered.
Manufacturing Planning Models
Models intended to plan the materialization of the product definition in the factory, field, and supply chain.
Manufacturing models to support build, maintenance, or upgrade process (re-)sequencing, incl. work-instruction finalization and MBOM.
Operation and Sustainment Models
Also referred to as: As Maintained / As Serviced / As Decommissioned / As Retired / As Disposed.