Change and Configuration Management

Evolve products in an orderly fashion, from concept through retirement.

Best Practices: Key Change and Configuration Management Process Improvements Enabled by PTC Capabilities

Change and Configuration Management: Best Practices
  • Standardized, automated change management: Implement a closed-loop standard change process. Adapt routing workflows according to change severity. Automatically capture change history, electronic signatures and audit trails. Notify affected parties of change effectivity.
  • Integrated cross-discipline change management: Implement a change process across the complete product definition (e.g., mechanical, electrical, software, documentation), within the common product information repository. Provide stakeholders with access to all necessary product data and configuration information during evaluation, review, approval and change implementation.
  • Standardized software change management: Ensure that a common, consistent change management process is applied to all aspects and artifacts of software development.
  • Coordinated software configuration management: Manage evolving software configurations across the entire life cycle, ensuring all artifacts corresponding to a software deliverable are consistent and reproducible.
  • Integrated software release management: Ensure repeatable software build, packaging, testing and deployment to system integration and product management environments.
  • System and software asset reuse: Enable effective product line engineering through holistic, strategic reuse of system and software assets, including requirements, design, simulations, software source code and test cases.
  • Partner change management integration: Integrate partners into engineering change review, approval and implementation activities. Increase visibility by ensuring problem and impact are fully understood and improve the quality and efficiency of changes.
  • Integrated product issue management: Implement a flexible online issue/change request process. Allow any affected party to indicate and substantiate the need to rectify a problem or improve a design/process.
  • Product configuration lifecycle management: Manage evolving product configurations over the entire lifecycle. Accommodate rule-based configurability, substitute parts, serialized parts, effectivity (time-or lot-based) and organization-specific BOMs (e.g., as-maintained, as-planned). Provide traceability between upstream design and downstream configurations to ensure change visibility and appropriate change propagation.
  • Basic BOM creation: Enable a development team to create and maintain the parts and structures needed to define a product.
  • Product configuration sharing to enterprise: Automate sharing and synchronization of product configuration information across enterprise systems.