Product Key Customer Benefits
|>Formal but flexible change management ensure that changes to products are captured, authorized, tracked and communicated throughout the enterprise and the entire life cycle of the product. ECM usage is more suitable for mature designs whereas Action (informal change mechanism) usage is more suitable for early product design phases. ENOVIA engineering change processes are unique because they employ Actions as task components. This provides a degree of ad-hoc capability to the formal change processes due to the dynamic nature of the Action that can be broken down into smaller assignable child Actions, or sub-tasks, that can be transferred to other people or organizations.
>Comprehensive engineering changes release planning utilize prerequisite, co-requisite EC and EC structure (hierarchy) capabilities to allow all changes to be inherently linked together and released according to a planned sequence. This is especially helpful for releasing a large product structure without after-the-fact costly reworks.
>Correct errors before an actual change is committed simulate the progression of an Action/ECO/ECR to the next state in its lifecycle graph. With this feature, users will be able to make necessary corrections prior to the actual change.
>Seamless transition between informal and formal change process ENOVIA LCA builds on the experience acquired with both ENOVIAVPM and ENOVIAPM. It is the next-generation solution that satisfies both the VPDM (Virtual Product Development Management) and the PDM (Product Data Management) domains. While most other commercially available systems have separate VPDM and PDM system, which results in difficulty for corporations to oversee a change process that will span the entire product life cycle, ENOVIA LCA supports seamless transition between informal to formal change processes. Actions are used in early product development phases (VPDM function) where changes to products and parts are made in informal fashion. When product design has stabilized and matured, it can be moved under the formal control of an engineering change order or a workflow (PDM function). Conversely, engineering change and workflow use Action as task components providing a degree of ad-hoc capability to the formal change processes due to the dynamic nature of the Action itself that makes it easy to be broken down into smaller assignable child Actions or sub-tasks that can be transferred to other person or organizations.