| - | A lifecycle for each ENOVIA object. The purpose of a lifecycle is to define the status progression/maturity of an object throughout the object's existence |
| - | A graphical user interface to view and customize lifecycles. |
| - | An ability to define conditions and operations at the lifecycle gates (transitions) |
| - | Three methods for attaching a lifecycle: default, alternate, rules-based |
| - | Provides a graphical user interface to define programs-related milestones. Milestones can be used as effectivity criterion during the configuration process to express date and range effectivity |
| - | Provides the ability to identify the Products controlled by a specific program. |