Field Use Only and Obsolete Part ECs
Field Use Only and Obsolete Part ECsThere are two options in ENOVIA for designating that parts have reached the end of engineering life:
Field Use Only
Parts that should no longer be used in Production assemblies but may be kept in stock for use by the Service organization
A user should contact the Service organization to reactivate a Field Use Only part.
Obsolete
Parts that should no longer be used in Production engineering assemblies or for Service work.
Part may still be used in physical assemblies.
Obsolete from an Engineering standpoint does not necessarily equate to Obsolete from a Manufacturing standpoint.
Obsolete parts may be reactivated.
Collections may be used to access the specific Obsolete to New EC command.
ECs For Field Use Only create a new part revision.
The new revision, in Preliminary state, is created when the EC is promoted from Submit to Evaluate state.
The new part revision does not require a CAD file.
To change a Release state Production part to Field Use Only:
Select
Actions > Edit
All or 
on the page tool bar.
Set the Requested Change field to For Field Use Only.
When the EC is Complete, the part is promoted to the Release state and the RDO is set to the Service business unit.
To promote a part out of Preliminary state when in an EC For Field Use Only, the immediate EBOM parents must meet one of the following criteria:
In the Service RDO, or
In an open EC For Field Use Only, or
In the Obsolete state, or
In an open EC For Obsolescence.
ECs For Obsolescence create a new part revision.
The new revision, in Preliminary state, is created when the EC is promoted from Submit to Evaluate state.
The new part revision does not require a CAD file.
The new revision is promoted to Obsolete when the EC is Complete.
A part revision is eligible for obsolescence if:
It is the latest revision, in Release state.
It is not attached to an open EC.
Parent parts are Obsolete or in an active EC For Obsolescence.
See Replace or Remove Parts in EBOM if needed.
A Collection may be used to obsolete multiple parts and automate the process of finding and obsoleting all eligible EBOM children.
See Create EC with Multiple Parts Across Multiple Projects -- Collections for more information.
To obsolete all eligible parts and EBOM children:
Select the parts in a Collection.
If a part in your Collection displays
, Higher Revision Exists, you may select the part and click Actions > Update to Latest Revision
(if the latest is in Release).
Click 
.
Select Obsolete to New EC on the Actions menu.
The eligible and ineligible parts and EBOM children from the selected parts are listed separately.
If a part is not added to the obsolescence EC, none of its children will be processed either.
Click Continue to create the EC with all eligible parts.
The Create New EC window includes a field to Exclude Part Types in Obsolescence.
Exclude part types you do not have the authority to obsolete or commodity parts (screws, washers, etc.) in an EBOM that should not be obsoleted.
To change a Release state Production part to Obsolete:
Select
Actions > Edit
All or on the page tool bar.
Set the Requested Change field to For Obsolescence.
To promote a part out of Preliminary state when in an EC For Obsolescence, the immediate Production policy EBOM parents must meet one of the following criteria:
In the Obsolete state, or
In an open EC For Obsolescence.
Development parts in the EBOM do not prevent obsolescence.
If a Release state EBOM parent cannot be obsolesced at the current time, remove (and/or replace) the For Obsolescence child component from the assembly. This change can be performed using the same EC.