What is change management? Why is it important?
In today’s accelerated manufacturing environment, products evolve fast. Teams need a way to easily manage changes to a product’s definition and share those changes across the enterprise.
With PLM engineering change management, teams can create data governance, visibility, and associativity so that all changes are fully defined and controlled. This ensures that tasks are delivered to those responsible using a repeatable and automated workflow. Changes are made and issues are resolved accurately, efficiently, and in real time.
Teams can also create, review, and gain formal approval for engineering change requests, engineering change orders, and engineering change notifications.
Key product features
Take advantage of an accurate, fast-paced, and coordinated change process across the organization.
Standardized, automated change management: Start with change processes that include full track (full CRB/CIB), fast track (change admin) or basic (lightweight CN only).
Configurable change process: Tailor a change process from simple and quick to deep traceability. Scale the process for different points in time such as prototype, new product introduction, and sustaining production.
Problem report: Capture issues or opportunities for products and processes and determine next steps. Tie these to both change and quality processes.
Deviation or waiver: Capture a “temporary” change to a product or process as part of the standard change workflow.
Engineering change notice: Create and execute the implementation plans for delivering the change to the enterprise. Allow for auditing and validation of the results prior to release of the data.
Electronic signatures: Change records, including sign-offs, markups, and comments connected to product data with audit trails.
Workflow: Create repeatable, easy-to-use processes that deliver tasks automatically to users. Easily configure task templates to deliver information the users need to complete their work.
Automatic synchronization with manufacturing systems: Publish updated information to downstream systems when changes are resolved.
Business rules: Apply business rules to ensure product data meets corporate standards.
Remote requirements: See the impact on requirements from remote system (using OSLC traceability) involved in the product design.