Model Build Workflow¶
Model Administration Meta-Model is designed to guide the model build process or workflow, ranging from drafting, approval, to release. The goal of a model build process is to create a model release used to initialize the operational systems such as EMS or planning tools. A model release is dynamically assembled by applying the Projects along the corresponding model evolution path sequentially to the base model denoted as Base Version. The following model diagram illustrates model evolution.
A model release can be dynamically assembled for any of the milestones along the model evolution paths, including Change Set, Version or Plan.
As-Built model maintenance is a linear process. There is only one Version thread dedicated to managing reality-based model evolution. The most recent Version represents the present model release (referred to as-built), while the earlier Versions identify the historic model releases. Typical workflow for As-Built model maintenance is shown below.
Planning model build is similar to As-Built model maintenance, except that a Plan dedicated for a planning study is normally not converted to a Version. For planning purposes, a Plan thread represents a planned model evolution path from which multiple planning study cases can be derived at various milestones. Multiple Plans can co-exist to support different planning business processes. Plans typically require high maintenance. A Plan thread normally starts from a Version. As a new Version of model is released, Plans should be upgraded to be based on the latest Version. During this upgrade, consistency checking must be performed to ensure that no modeling conflicts exist.