The Governance domain allows companies to launch enterprise-wide new product introductions on-time and on-budget. Within Governance are these sub-processes: Requirements Management, Portfolio Configuration, Program Management, Decision Support Business Intelligence, and Compliancy.
CATIA Program Change Control
ENOVIA® Program Change Control provides program driven change management.
ENOVIA Program Change Control makes it possible for companies to define, plan, track and implement complex product changes using traditional project management processes. With ENOVIA Program Change Control companies can determine the scope and cost of all product changes before they are implemented. Programs can establish a change project plan, assigned to internal and external organizations to capture the total impact, scope and cost of a proposed change. During initial impact analysis, the program can capture and record decisions as a result of any scheduled meeting. All decision and impact analysis information for a given product or program is aggregated for analysis and approval, including estimates of changes provided by partners/suppliers. This enables complete visibility of all changes that occur throughout the product development process leading to improved productivity, higher quality and faster time-to-market.
- Consolidate sources of change information to collect, analyze, plan and implement product issues, requests and change processes across the enterprise
- Assess the impact of changes to the overall product development schedule with real-time product change dashboards that eliminate manual collection, assessment and reporting
- Reduce the risk of regulatory or customer non-conformance penalties by ensuring that company standard change processes are followed consistently
- Eliminate the potential to repeat past mistakes by maintaining a complete change history with traceability and lessons learned
- Close the communication gaps between customer support, R&D and cross functional development teams by leveraging a global, cross functional, change identification and resolution solution
Change ProjectsENOVIA Program Change Control provides engineering project managers a way to plan and manage complex product changes under one or more change projects. Change projects can be used in conjunction with other program execution projects to provide visibility to the status of program level product changes which can have a significant impact on the overall program development schedule. Each functional department, including outsourced design partners or suppliers, can capture the impact, scope and cost of implementing the change for their discipline (e.g., software, mechanical, electrical) by leveraging project meetings and decisions. Meetings can be scheduled for the change project and official decisions can be captured against the change project or individual change tasks. Once the change project is approved, the change project and assigned change tasks track the impacted organization (manufacturing, engineering, or both) to enforce proper business rules during the implementation process.
Change TasksChange tasks are added to a project’s Work Breakdown Structure (WBS) to decompose and organize complex changes into manageable work packages. Change tasks can be used in conjunction with other type of project tasks to ensure that specific program change processes and procedures are followed. Change project managers can create one or more changes with a single change task, make resource assignments, and identify deliverables for each task.
Change RequestsChange requests are used as a formal mechanism to collect a number of product issues and request approval to resolve them with one or more change tasks / processes. An approved change request is the transition from informal issue management to formal change approval and control.
Change Task DeliverablesAs proposed changes are approved, each impacted functional group (e.g., software, mechanical, electrical) is assigned a change task. The deliverable for the task is the completion of an approved change process (e.g., Engineering Change Order, Engineering Change Request, Action, etc.). As the change process is executed, the change task status is updated automatically to provide a change summary status at the task or project level. Change tasks control new feature changes to specific product revisions in a product portfolio instead of automatically applying the change to all products that use the previous feature revision.
The Role of ENOVIA V6 and PLM 2.0ENOVIA IP Export Classification supports PLM 2.0, product lifecycle management online for everyone, and the ENOVIA V6 values, which are: Global collaborative innovation Single PLM platform for intellectual property (IP) management Online creation and collaboration, ready to use PLM business processes Lower cost of ownership.