PUE ECO Lifecycle | ||
| ||
Create
When a Design Engineer or Manufacturing Engineer creates a PUE ECO, builds within the applicability range will be connected to the PUE ECO with the Applicability relationship.
Mod stacks for the product are recalculated to incorporate the new PUE ECO.
Define Components
As the PUE ECO enters the Define Components state, an action fires that automatically routes the PUE ECO to the RDE.
The RDE reviews the ECRs that are attached to the PUE ECO and determines which parts and drawing prints need to be attached to the PUE ECO. The RDE uses the Create Part and Create Drawing pages to create/revise and attach these objects to the PUE ECO using the appropriate relationships. The RDE or assignee can fill in or edit the appropriate Disposition Code and Change Description attributes that are on the relationships. The RDE reviews the attached PUE ECOs and determines if the appropriate parts and specifications have been attached.
The reviewer list is copied from the ECR to the PUE ECO. The RDE can also assign a reviewer list for the Design Work state in order to handle the creation of the reviewer route between Design Work and Review states.
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 affected items that have a Requested Change value set to "Revise." The new revisions are connected to the PUE ECO as affected items. In addition, if the old revision contained approved markups, these markups are copied to the new revisions. This trigger can be inactivated, if desired.
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 necessary to ready these objects for review. Once they have performed all the necessary work, they notify the RDE that s/he can review the package.
Assignees can attach additional affected items and are assigned to them by default. They can add BOM markups, propose specification changes, and approve or reject the markups for their respective affected items.
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.
When any affected item connected to the PUE ECO is promoted to the Approved state, all other affected items connected to the PUE ECO are checked to see if they also are in the Approved state. If all affected items are in the Approved state, the PUE ECO is automatically promoted to the Review state. If any single affected item connected to the PUE ECO is a state prior to Approved, the PUE ECO is not promoted to the Review state. A configurable trigger prevents the PUE ECO from manually being promoted to the Review state unless all affected items are have been approved. See the Engineering Central Administrator's Guide for details.
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. By default, all affected items are also automatically promoted to the Release state. This is configurable. See the Engineering Central Administrator's 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:
- Disconnect the prerequisite ECOs.
- Calculate and update the "Final Effectivity" attribute (tag) of the Applicability Details attribute.
- Set the Unresolved BOM relationship attribute Applicability Status to "current."
A check is made using the CheckPrerequisite trigger to see if all its prerequisite ECOs are released. If any prerequisite exists then an alert is displayed blocking the promote action.
- Dependencies are maintained by the Prerequisite relationship between the PUE-ECOs. For example, if PUEECO-000000110 is a dependent on PUEECO-000000101, then PUEECO-000000101 must be released before PUEECO-000000110 can be released.