Change Management Setup in Windchill

[UM_14390122]

Version: Windchill 13.0

Use Case: I am working on implementing Engineering Change Management in Windchill from the perspective of a Business Analyst within the Configuration Management department. I currently have both the AS-IS process and a proposed TO-BE process mapped out. Given this situation, I want to understand how an experienced Windchill/Configuration Management professional would approach this initiative. Where would you begin the configuration within Windchill to ensure the new process is structured, efficient, and scalable? What would be the logical sequence of steps to move from process definition to system configuration and rollout? I wanted an overall outline on this.

Description:

Our company is transitioning from managing change requests through email and Jira to a standardized Change Management process within Windchill. We currently use both Fast Track and Full Track processes for handling Change Requests (CRs), and the goal is to migrate these into Windchill while incorporating improvements and stronger governance.

I am a Business Analyst from the Configuration Management team, and although I have limited CAD/Designer experience, I am familiar with Windchill capabilities and Change Objects such as Problem Report (PR), Change Request (CR), Change Notice (CN), Change Task (CT), and Promotion Request. My challenge now is determining how to begin building and configuring the end-to-end process in Windchill so it aligns with our business workflows.

I am looking for guidance on:

• Where to start when implementing Change Management workflows in Windchill

• Recommended steps or best practices for structuring Fast Track and Full Track processes in the system

• Any free online resources or documentation that can help me learn the configuration aspects

• How to leverage my PTC Learn license effectively for this initiative

[HV_13054754]

Hi,

I would suggest that you could directly start using the OOTB change process. Its a well laid out process.

For Fast Track and Full Track, the criteria for Full track should be set by your Change Management COE.

For eg:

1. Any Change implementation that calls for more than 10K USD as one time cost 

2. Change that require multiple departments to review and assess the technical solution from a safety , Product performance perspective.

Also, a good change process means that 70% of all the changes are in Fast track, it will take sometime but this is the benchmark as per CM 2 Standards.

Also, in Fast track, the Creator of the artefacts and the user of the artefact should agree already before implementing the documentation upgrade (revision approvals).

You can give a good read on CM 2 standards for closed loop changes. There is a CM2 Basic course which is immensely useful.

All the best!

Best Regards

Hari