DCR Lifecycle | ||
| ||
Evaluate
In the Evaluate state, the Responsible Design Engineer and assignees review the change description, any supporting documentation, and the items attached, and check that all part dispositions are set correctly. The Responsible Design Engineer can also attach additional parts and drawings or even change some of the existing connections based on specific knowledge of how the change is likely to be done. The Responsible Design Engineer can modify the start effective date, end effective date and also assign users to the reviewer list for use in the Review state.
When the Responsible Design Engineer or an assignee adds an affected item to the DCR, that person becomes the assignee of that affected item. Also, if they create a BOM markup, plant BOM markup, or plant item markup for an affected item, the affected item assignee becomes the owner of the markup and has the authority to approve it for implementation or reject it. Before the DCR can be promoted, all attached markups must be approved or rejected by the owning assignee.
If the DCR is acceptable, the Responsible Design Engineer promotes it to the Review state. Triggers check to ensure that a change responsibility has been defined, that there is an ECR Chairman defined within that organization, and that a reviewer list, affected plants, a start effective date, and an end effective date have been assigned.
Review
On promotion to the Review state, a route is created and started using the template from the reviewer list with a Route Base Purpose set to "Standard" and a Route Completion Action set to "Promote Connected Objects." All tasks must be completed before the DCR can be promoted from Review to Plan DCO. When all tasks are complete, the route owner is notified and can then promote the DCR. If a route already exists, which may happen on demote and subsequent promote, then a new route is not created but a message is sent to the route owner (Responsible Design Engineer) to restart the route.
As the DCR enters the Review state, a request is sent to the ECR Chairman and the Senior Manufacturing Engineers in the affected plants to review the DCR. The Senior Manufacturing Engineer in each of the affected plants reviews the DCR, all supporting documentation, and the BOM markups, plant BOM markups, or item markups. They either approve or reject the DCR by approving or rejecting their assigned route tasks. Notification about approval or rejection is sent to the Responsible Design Engineer.
If one or more route tasks are rejected, the DCR cannot be promoted. In this case, the Responsible Design Engineer needs to evaluate the rejected comments. If the Responsible Design Engineer feels the DCR needs more work, then he rejects his task and demotes the DCR back to the Evaluate state where the DCR approvers and assignees are able to add the affected items that need additional work. The Responsible Design Engineer must then promote the ECR again when it is ready for review.
The Responsible Design Engineer can also cancel the DCR, as long as there are no applied markups attached to the DCR. When the last signature (the ECR Chairman) is approved, the DCR auto-promotes to the Plan DCO state. The DCR Requestor, ECR Coordinator, ECR Chairman, members of distribution list, and MCO coordinator of each plan are notified when the DCR reaches the Plan DCO state.
Plan DCO
As the DCR enters the Plan DCO state, DCOs are released to implement the changes released by the DCR. For each affected plant, one DCO is released to apply the changes and another is released to reverse the DCO after the temporary changes have occurred and are no longer effective. The start and end effective dates can be changed for the DCO that applies the changes. If the end effective date of the DCO is changed, the start effective date of the reversing DCO is automatically updated to be the same.
After the DCO is applied, the end effective date can still be changed. Effective dates can be changed from the Editing ECR Details page. All affected items are handled according to the value of their Requested Change attribute. Since a DCR is a temporary change request, the change value for each DCR item is always "For Update." Only one BOM markup, plant BOM markup, or item markup is required for each affected item update.
An MCO and DCO or an ECO generated from an MCO and DCO cannot be active at the same time for a plant. The MCO will be pending until the DCO is reversed.