Manufacturer Equivalent Lifecycle

Basically, the Manufacturer Equivalent lifecycle is the same as the EC Part Lifecycle, with the following additions to the Release and Obsolete states:

Release

The Component Engineer is responsible for promoting manufacturer equivalent parts to the Release state when the part definition is complete. When an equivalent part is promoted to this state, connections are maintained to the last released and/or in process revisions of its enterprise part, and history connections are maintained to the previous enterprise part. This is handled by the release state action trigger.

The Manufacturer Equivalent History relationship accommodates this delayed float logic. This relationship has all the same attributes as the Manufacturer Equivalent relationship. Both of these relationships have the attributes Start Effectivity Date and End Effectivity Date.

On the initial connection of a manufacturer equivalent part, the Start Effectivity Date and End Effectivity Date on the manufacturer equivalent part are both blank. It is not until the enterprise part is promoted to the Release state that the Start Effectivity Date is set to the released date of the enterprise part.

As a Part enters the Release state, the following Action fires:

• When an enterprise part is released, the Start Effectivity Date on the Manufacturer Equivalent relationships between this enterprise part and the equivalent part is set to the released date of this enterprise part.

If the part that is being released is determined to be an equivalence part, then the following actions are performed:

• If the Manufacturer Equivalent connection is from the highest release of an enterprise part, the following steps are performed:
• An identical Manufacturer Equivalent History relationship is created between the parts. This connection has all the same attribute values as the Manufacturer Equivalent connection.
• The End Effectivity Date is set on the Manufacturer Equivalent History connection to the date the equivalent part is released minus 1 second. (The subtraction of 1 second is so that the end effectivity date on the Manufacturer Equivalent History connection is not identical to the start effectivity date on the Manufacturer Equivalent connection)
• The Manufacturer Equivalent connection is floated to the newly released equivalent part.
• The Start Effectivity Date on the Manufacturer Equivalent connection is set to the date the equivalent part is released.
• The End Effectivity Date on the Manufacturer Equivalent connection is kept blank (no end effectivity date since this is the last released revision)
• If the Manufacturer Equivalent connection is from an in-process enterprise part, then the Manufacturer Equivalent relationship is floated to the new released equivalent part. There is no need for a Manufacturer Equivalent History connection here.
• If the Manufacturer Equivalent connection is from a previous release of an enterprise part (previous to the latest released revision), then the Manufacturer Equivalent connection is left as is. There is no need for a Manufacturer Equivalent History connection here.

Obsolete

As a Part enters the Obsolete state, the following Action fires:

• When a equivalent part is promoted to Obsolete a trigger will set the End Effectivity Date on the Manufacturer Equivalent relationship between that part and its enterprise part to the date this part enters the Obsolete state.