Create
When a Design Engineer or Manufacturing Engineer creates a PUE ECO, or a CECO is automatically created through a CO (change order), builds within the applicability range will be connected to the PUE ECO / CECO with the Applicability relationship. Mod stacks for the product are recalculated to incorporate the new PUE ECO / CECO. Define Components
As the PUE ECO enters the Define Components state, an action routes the PUE ECO to the RDE. The RDE can promote the PUE ECO to the Design Work state once a reviewer list for the Design Work state is assigned. Upon promotion, a route is created and started using the reviewer list template with a Route Base State set to "Design Work" with the route having a Route Base Purpose set to "Standard" and a Route Completion Action set to "Notify Route Owner." The route is placed between the Design Work and Review states and all tasks must be completed before the PUE ECO is promoted to Review. The owner of the route is the current PUE ECO owner, usually the RDE. When the last task is completed, a notification is sent to the route owner that the route is complete and the PUE ECO can be promoted. If a route already exists, which may happen on demote and subsequent promote, then a new route will not be created but a message is sent to the route owner (RDE) to restart the route. When the PUE ECO is promoted to the Design Work state, a trigger is run to create new revisions for all proposed changes that have a Requested Change value set to "For Revise." The new revisions are connected to the PUE ECO as proposed changes. In addition, if the old revision contained approved markups, these markups are copied to the new revisions. This trigger can be inactivated, if required. The owner may also demote the PUE ECO, in which case the ownership is reset back to the previous owner. Design Work
As the PUE ECO enters the Design Work state, the permissions change that prevent any relationships from being made or broken. Once in the Design Work state, the RDE notifies Draftsmen and Design Engineers that they have work to do on this PUE ECO and indicates which parts and drawing prints they are responsible for completing by making them the owner of these objects as required. These other Design Engineers and Draftsmen perform whatever CAD and Bill of Material work is required to ready these objects for review. Once they have performed all the required work, they notify the RDE that s/he can review the package. Assignees can attach additional proposed changes and are assigned to them. They can add BOM markups, propose specification changes, and approve or reject the markups for their respective proposed changes. If the package is not acceptable, the RDE notifies the user responsible for making the correction. If the package is acceptable, the RDE signs and promotes the drawing prints and parts to the Review state. If a configured part in the In Work state is added as a proposed change, releasing the PUE ECO will release the part. If a configured part in the Released state is added as a proposed change, releasing the PUE ECO will supersede the current revision and the new revision will be released. Review
As the PUE ECO enters the Review state, an action fires that automatically routes the PUE ECO to the user who is the Responsible Manufacturing Engineer. The Responsible Manufacturing Engineer reviews the disposition codes and sets the effectivity dates on the new parts accordingly. The Responsible Manufacturing Engineer may also update other part attributes like Lead Time and Estimated Cost. If the package is not acceptable, s/he demotes the PUE ECO back to the Design Work state, which automatically notifies the RDE. If the package is acceptable, the Responsible Manufacturing Engineer promotes the PUE ECO to the Release state. All proposed changes are also automatically promoted to the Release state. This is configurable. See the Engineering BOM Management Administration Guide for details. Release
When a PUE ECO is promoted from the Review to Release state, an action trigger called "Update Applicability" is added to perform the following actions:
A check is made using the CheckPrerequisite trigger to see if all its prerequisite CECOs/PUE ECOs/CCAs are released. If any prerequisite exists then an alert is displayed blocking the promote action.
Implemented
The PUE ECO Implemented state closes the loop of the change process. This state provides verification and visibility that a change, as published by Engineering, has in fact been implemented in the factories. It is a "closure" check to ensure that other processes have worked. Cancelled
The owner of the PUE ECO can promote it to the Cancelled state from the Create, Review or Release state. The PUE ECO remains in this state to preserve a record of its creation and cancellation. Prerequisite calculation and Mod Stack calculation are performed. | |||||||