Preliminary
New parts and revisions are created in the Preliminary state. A part
may have its name automatically generated or calculated by the user and
given to the system.
As the part leaves the Preliminary state, the following checks are
fired:
- Attached parts must be beyond Review state
- MCO/ECO must be connected via MBOM Change/New Part Revision relationship
- Previous revisions of this part must be in Review or beyond
- Specifications must be connected to the part. By default, this trigger
is inactive.
If all of these checks pass, the part will be promoted to the next state.
Review
The part is reviewed and approved in this state by the Responsible Manufacturing
Engineer using the ECO/MECO Properties page. The review should include
the parts attributes, Bill of Material, and drawing print.
After determining that the
part can be manufactured consistent with its intent, the Responsible Manufacturing Engineer promotes it
to the Release state.
Because of the following checks, the user is required to promote the
parts from the bottom up.
As the part leaves the Review state, the following check is fired:
- Attached parts must be beyond Release state
If this check passes, the part will be promoted to the next state.
Approved
After the part enters the Approved state, all proposed changes connected
to the part's ECO/MECO are checked to see if they are also in the Approved
state. If all proposed changes are in the Approved state, the ECO/MECO
is automatically promoted to the Review state. If any single proposed change connected to the ECO/MECO is in a state prior to Approved, the ECO/MECO
is not promoted to the Review state.
A trigger checks to see whether the connected MCO/ECO is in the Release
state.
If a part has equivalent parts connected to it, one or more of the
equivalent parts must be in the Release state before this part can be
promoted to Release.
Release
Once in the Release state no connections or disconnections of any relationships
below a part are allowed.
Obsolete
At some point in time it may be determined that a part should be made
obsolete. When this occurs a person who belongs to the special role Product
Obsolescence Manager can login and promote the part to Obsolete.
In this state, the part cannot be used in any new Bill of Material.
This is accomplished by changing permissions such that no connects above
the part are allowed. Once in the Obsolete state, only the Product Obsolescence
Manager is able to demote the object back to the Release state.
|