A few weeks ago we talked about our new date effectivity feature in PLM 360 in “Are you Affected by Effectivity” Bastien, from our support team, wrote a detailed example of how this works to give some more insight in how to use this new feature. Let’s say you are planning some future changes to your Spur Gear product and decided to make a change to the Gear Box part to go along with it.

The changes to the product require some facility changes, so the plan is to make that in a month from now. This can be easily done in PLM 360 thanks to the new BOM effectivity feature. All that is required is to create a new change order, add the Gear Box part as the only affected item and set its effectivity date to be in a month from now.

After completing the change order, the Spur Gear assembly BOM will now show revision B for the Gear Box part after changing the BOM view date to a month from now.

However, soon after that, warranty claims start coming requiring an emergency change to the same Gear Box part taking effect immediately.
This is also easily taken care of in PLM 360 by creating yet another change order for that part to move it to revision C with an effectivity date set to a couple of days from now.

This may raise some high brows since the next revision C will have an effectivity date earlier than its previous revision B. This is however not a problem due to PLM 360 high flexibility in BOM area.
Changing the BOM view dates around in assembly shows that revision A is superseded:

… that revision C is in Production:

… and that revision B is superseded:

But most importantly if you navigate to the Gear Box item itself, you will find that superseded revision B was never in effect.

In addition, this same method could be used to accelerate delivery plans by going with a different supplier, or fixing mistakes.
Hope that helps you get a better understanding of how it all works!
--Michelle Stone