Skip to main content

Models

Overview​

A model defines the engineering reference data and the allowable configuration for a type of complex asset.

The allowable configuration is sometimes referred to as the "as designed" or "could build" configuration.
At the simplest level, a Model consists of:

  • A collection of Build Items representing the tracked (often serialized) components which make up a complex asset.
  • For each Build Item one or more Configuration-managed (CM) Items. A CM Item is typically used to represent a Part Number and can be related to a Rotating Item Master record.
  • For each Build Item one or more Labels which may be used to represent the functional system that the Build Item is part of.
  • One or more Configurations that may represent different Variants of the asset type.
  • A Build Hierarchy formed from the list of Build Items to represent the physical structure of the Asset.
  • Configuration rules defining specific criteria that must be obeyed for the associated Asset to be in a valid configuration.

The Model is used as template from which configuration managed assets can be created.

The Build Data Interpreter (BDI) validates changes to a configuration-managed asset against the Model definition.

This is to ensure that operational changes to the associated assets comply with the allowable configuration, defined in the Model, and any problems are communicated to the user.

A model can represent a top-level asset, such as an airplane or a train or it can represent a complex equipment subassembly, such as an engine or a locomotive. Any asset which corresponds to the top level position in a model is often referred to as an "End Item".

A default configuration-managed (CM) item is created automatically when a new Model is created. You create and modify CM items in the CM Item Master application.

New CM asset hierarchies can be created from a Model using the New Asset Assemblies (CM) application.