Teamcenter Change Management (Part 2)
Updated: Aug 17, 2021
Continuation of Change Management (Part 1)
Change Objects in Teamcenter
Change objects are related to each other by relation Implemented By and Implements as shown in the picture.
Problem Report (PR)
Problem Report (PR) is used to capture the problem or idea or enhancement. Any user in the system will be provided access to create a problem report to report an issue or share an idea or opportunity for an enhancement.
Problem Report (PR) includes the information on problem identified and steps to reproduce the problem. It can also hold documents to support identified problem or enhancement.
Once PR is reported, it goes for a approval process. The workflow process should be designed as per business process involving stakeholders who can review the PR and take decision whether the problem reported can proceed for analyses of the problem. Change Request are derived from PR once approved by stakeholders.
One or more Change Request's (CR) are created from Problem Report (PR) based on various reasons like complexity of the problem, long lead items, region or department based, etc.
In some business, Problem Report is optional in their change process. They skip PR and directly create Change Request.
Change Request (CR)
Change Request (CR) or Engineering Change Request (ECR) is used to analyze the problem and recommends the proposal for the change. It also captures business decisions associated with the change.
An ECR proposes the solution to the problem reported with additional details addressing the cost and benefits of making the change. The solution is not implemented with CR, it is implemented in Change Notice (CN).
A single ECR can be used to address issues identified in multiple PRs. This allows to logically group similar PR's (PR's reported for same issue). An ECR can be address by one or more ECN's.
Change Notice (CN)
Change Notice (CN) or Engineering Change Notice (ECN) is used to implement the solution. It is also used to capture detailed work pan to resolve one or more ECRs or a portion of on ECR.
An ECN identifies all the objects affected by a change and authorizes the actions that address a change.
Deriving a change
We can derive a change object from another object to mange the next phase of the change process.
Derive an engineering change request (ECR) from a problem report (PR) to determine a solution for the problem.
Derive an engineering change notice (ECN) from an ECR to implement the solution to the problem.
How change objects are related
You might have understood each change object is managing the different phases of the change process. It is necessary to relate these change objects.
Multiple PR's can be grouped and addressed by a single ECR. Similarly multiple ECR's can be grouped and addressed by a single ECN.
Using Change Manager, you can create very complex structures of changes to satisfy specific change requirements, providing the flexibility we need.