Create
A legacy ECO may have been created by a user with the Design Engineer
or Senior Design Engineer
roles.
The ECO name is automatically generated. An ECO may or may not have an ECR.
Without an ECR, the ECO creator becomes the owner and the Responsible Design
Engineer (RDE) for the ECO.
If an ECO was created from an ECR, all proposed changes and assignees
from the ECR were copied to the ECO.
When using an ECR as the basis for the ECO, attributes carried over
from the ECR to the ECO include Category of Change, Reported Against, and
Severity. If the ECR had a distribution list or reviewer list, they are also
copied over to the ECO. All attributes copied from the ECR can be changed
except for the related ECR. If an ECO already exists, the reviewer list will
not be copied over.
The RDE has overall coordination responsibility of the work to be
performed on the ECO and also assigns work on the ECO.
While creating an ECO, the user selected an organization that has
design responsibility. The ECO creator must be a member of that organization
and must have an Engineering
role
within the organization.
The assignees of the proposed changes on the ECR are carried over as
assignees on the ECO. If the ECR does not contain any proposed changes, the RDE
can attach proposed changes to the proposed change list of the ECO.
The RDE can also assign people as assignees on the ECO to work on a
proposed change. An assignee can add proposed changes to the ECO and, in turn,
become assigned to work on the respective proposed change.
The RDE can assign an approval list at this state to handle the
creation of the approval route and assigns the Manufacturing Engineer who must
review and approve the ECO before releasing it.
The RDE then promotes the ECO to the Define Components state. The RDE
retains the ownership of the ECO in the Define Components state.
When the ECO is promoted to the Define Components state, new revisions
are created for all proposed changes with a Requested Change of "Revise." The
new revisions are connected to the ECO. In addition, if the old revision
contained approved markups, these markups are copied to the new revisions. This
trigger can be inactivated, if required.
Define Components
As the ECO enters the Define Components state, an action fires that
automatically routes the ECO to the RDE.
The RDE reviews the ECRs that are attached to the ECO and determines
which parts and drawing prints need to be attached to the ECO. The RDE uses the
Create Part and Create Drawing pages to create/revise and attach these objects
to the ECO using the appropriate relationships. The RDE or assignee can fill in
or edit Change Description attributes that are on the relationships. The RDE
reviews the attached ECOs and determines if the appropriate parts and
specifications have been attached.
The reviewer list is copied from the ECR to the ECO. The RDE can also
assign a reviewer list for the Design Work state to handle the creation of the
reviewer route between Design Work and Review states.
The RDE can promote the 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 ECO is promoted to Review. The owner of the route is the current ECO
owner, usually the RDE.
When the 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 "Revise." The new revisions are connected to the 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 ECO, in which case the ownership is
reset back to the previous owner.
Design Work
As the 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 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 by default. 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.
When any proposed change connected to the ECO is promoted to the
Approved state, all other proposed changes connected to the ECO are checked to
see if they also are in the Approved state. If all proposed changes are in the
Approved state, the ECO is automatically promoted to the Review state. If any
single proposed change connected to the ECO is a state before Approved, the ECO
is not promoted to the Review state. A
trigger prevents the ECO
from manually being promoted to the Review state unless all proposed changes
are have been approved.
Review
As the ECO enters the Review ECO state, the ECO is sent to the
Responsible Manufacturing Engineer. The Responsible Manufacturing Engineer 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, Responsible Manufacturing
Engineer demotes the ECO back to the Design Work state, which automatically
notifies the RDE.
If the package is acceptable, the Responsible Manufacturing Engineer
promotes the ECO to the Release state. All proposed changes are also
automatically promoted to the Release state.
Release
As the ECO enters the Release state, an action fires that
automatically changes the owner of the ECO to be a special user in the system
"Corporate." This locks down the ECO so no additional changes can be made and
removes the ECO from the engineer's desk.
Implemented
The 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.
Canceled
In any state before Release, the ECO can be canceled by the ECO owner
or a user assigned to any of the following
roles
in the organization that has change responsibility for the ECO: Design
Engineer, Senior Design Engineer, Manufacturing Engineer, Senior Manufacturing
Engineer, ECR Chairman, ECR Coordinator, ECR Evaluator, Part Family
Coordinator, Product Obsolescence Manager or Component Engineer.
When an ECO is canceled, the following actions are performed:
- All proposed changes connected to the ECO are disconnected.
- All routes connected to the ECO are disconnected. The route owner
receives notification that the route has been canceled. All routes are stopped
if the ECO is the only content of the route.
- Route templates connected to ECO are disconnected.
- All assignees, distribution list, reviewer list members, and the
ECO originator, are notified that the ECO has been canceled.
- The ECO is promoted to the Canceled state.
|