Skip to main content
Home / Can 3DEXPERIENCE simplify change management processes?
Faqs

Can 3DEXPERIENCE simplify change management processes?

The 3DEXPERIENCE platform provides a streamlined, collaborative, and traceable change management process. It integrates tools like issue management, change requests, and change actions to ensure efficient handling of design changes, approvals, and implementation. Here’s an overview of how the process works:

Key features of 3DEXPERIENCE change management

  1. Issue management:
    • Users across departments (e.g., shop floor, design) can raise issues related to products or processes.
    • Issues are tracked with attributes like priority, due dates, and affected items.
    • Attachments and markups can be added for clarity.
  2. Change requests:
    • Once an issue is validated, a change request is created to formalize the proposed change.
    • Impact analysis is conducted across departments to evaluate feasibility and implications.
    • Approvals are obtained before proceeding to the next step.
  3. Change actions:
    • Approved change requests lead to the creation of change actions.
    • Designers or assignees work on implementing changes, such as revising CAD models or updating EBOM parts.
    • The maturity state of files (e.g., “In Work,” “Frozen”) is updated to reflect progress.
  4. Approval workflow:
    • Approvers review proposed changes using dashboards or 3D viewers integrated into the platform.
    • They can accept, reject, or request modifications with comments for better collaboration.
  5. Traceability and automation:
    • All steps in the change process are tracked for accountability and compliance.
    • Automated workflows reduce manual intervention and ensure consistent execution.
    • Scenarios simplified by 3DEXPERIENCE
  6. Single component approval:
    • A designer creates a change action for a single component in the native app (e.g., CATIA).
    • The lead designer/reviewer approves the change after reviewing the proposed updates.
    • The component is promoted from “In Work” to “released.”
  7. Multi-object changes:
    • A designer uses the Web App to create a change action for both a physical product (CAD model) and an EBOM part.
    • Changes are implemented in respective apps (native app for CAD, web app for EBOM).
    • Once approved, both objects are released simultaneously.

Are you ready to talk?