Objective: Understand how to use the Obsolete status value and why it exists.
Difficulty: Easy
The Obsolete lifecycle status should be used to lock a component or assembly, indicating that it should not be used in the future. This article details specific uses and questions about the Obsolete status.
Defining the Obsolete Status
Any component, assembly, or document can be moved to the Obsolete status value. This is an indicator to other users that the item at hand can not be used in any new assemblies.
Reasons why components or assemblies may be moved to Obsolete include but are not limited to:
- The component has been found to be faulty
- The component has been replaced with a new option (ex: new generation component)
- The component is no longer available for purchase
The Obsolete status is intended to capture the state of the entire component at the time it becomes obsolete. Once the Change Order moving the component to Obsolete is approved, the current values of the component are captured and are now “locked” against any further editing. The component becomes read only, and cannot be edited or modified.
Revision values for Obsolete components
Obsolete components are locked at the revision value they were in when moved to the Obsolete status. As components may be moved to Obsolete from Design, Prototype, or Production, the allowable revision values within Obsolete is the superset of the allowable values for all other lifecycle statuses.
When the Obsolete item is a standalone component
Standalone components can be moved to the Obsolete status without impacting other components or assemblies. They cannot later be added to assemblies, so will remain standalone.
When the Obsolete item is a child in an assembly
A single child component with the Obsolete status will invalidate an entire assembly, as that assembly contains this component which cannot be used.
In Duro, this is indicated by a warning or error message in the parent assembly, and all parent assemblies above it.
Impact of an Obsolete child component on a Change Order
Children components are not always visible in a Change Order, particularly when there are several nested layers of assemblies. Duro will surface the presence of an Obsolete child component via a warning or error message, depending on your specific account configurations.
Change Orders with warnings can still be submitted for approval; Change Orders with errors cannot, and errors must be addressed before the Change Order is submitted.
When the Obsolete item is a parent assembly
Obsolete parent components or assemblies are highly visible, and the Obsolete status does not inherently impact any child components.
For example: a deprecated assembly that is no longer sold may be marked Obsolete; but the children may all be components with Prototype or Production statuses, which are usable for other assemblies.
Impact of an Obsolete parent assembly on a Change Order
Obsolete components may be added to workflows and revisioned.
Parent-child relationships for all statuses
Parent | Child | Valid | Warning | Error | Submit For Approval |
Obsolete | Prototype / Production | Yes | Optional | Optional | Yes |
Obsolete | Design | Yes | N/A | Yes | Yes |
Prototype / Production | Obsolete | No | Yes | Yes | No |
Production | Prototype / Design | No | Yes | Yes | No |
Prototype | Design | No | Yes | Yes | No |
Prototype | Production | Yes | No | No | Yes |
Design | Prototype / Production | Yes* | N/A | Yes | No |
Design | Design | Yes* | N/A | Yes | No |
*Parent/child relationships here are valid. However, the component cannot be submitted for approval via a Change Order as the component is in the Design status.
Comments
0 comments
Please sign in to leave a comment.