Occurrence Effectivity in Teamcenter
Occurrence Effectivity
Date, unit number or the combination is specified in the revision rule to configure occurrence by their effective date or units. Occurrence effectivity information is stored in effectivity object. This object is referenced by occurrence(s) in structure.
Sharing effectivity means, any change to effectivity object in date or unit number, affects all occurrences referencing this effectivity object.
Note: The occurrence with no effectivity is always effective. Only configured occurrence can be displayed in structure from toggle setting of View–>Show Unconfigured by Occurrence Effectivity.
Copy Occurrences with Effectivity
Remove Effectivity
Select the occurrence and launch Occurrence Effectivity dialog from Tools–>Effectivity–>Occurrence Effectivity–>View, Create and Edit. Click on Remove to remove the effectivity of this occurrence.
Shared effectivity on any other occurrence will not be removed.
Effectivity Preference
Value of CFMOccEffMode preference decides if date/unit number or both the effectivities can be used.
Multi-Unit Configuration & Effectivity Group
Unit Number Effectivity must use an End Item (informs which end item carries this unit number). Occurrence can be associated with multiple unit number effectivity, specified in multi-unit configuration. Multi-Unit Configuration are used to configure occurrence with a combination of multiple end items and range of unit number for each end item. These multi-unit configuration are saved as effectivity group.
This functionality is enabled with Fnd0EnableMultiUnitConfiguration global constant set to true. Effectivity Group is created from New Item dialog and it is not revisable.
Saving multi-unit configuration in effectivity group
This can be done in two ways and comparison is as shown in table below. Select the effectivity group revision.
Configure Occurrences with effectivity group(s)
Load the product structure to configure occurrences of structure with effectivity group(s).In Set Date/Unit/End Item dialog box, [Append, Insert, Replace] effectivity group, by entering effectivity group identifier in the Effectivity Group box.
Configured occurrence effectivity of each occurrence is matched with entry in effectivity group(s).The occurrence is loaded, whose occurrence effectivity matches any of the entry in an effectivity group. This occurrence will not be loaded again, if its effectivity matches any other entry in other effectivity group too.
Also Read:
Revision Effectivity & Nested Effectivity
Incremental Change in Teamcenter
Classic Variant Configuration in Structure Manager
Modular Variant Configuration in Structure Manager
Related External Link:
http://teamcenter-open-gate.blogspot.in/2016/11/teamcenter-unified-architecture.html
https://www.youtube.com/watch?v=oiyd-PFtkmw
I was never able to configure the BOM using AND condition of the multi unit configuration, it always behaves with an OR condition
Lets say.. i have a BOMLine with 1-UP [END ITEM-1], 1-UP [END ITEM-2] and the multi unit configuration has [1 END ITEM-1 and 1 END ITEM-3], I expect that the BOMLine should not be shown but it always shows up (obviously i have show unconfigured occurrences set to false). I did not raise an IR but reading documentation looks like it will work as OR condition, if so not sure what the multi-unit configuration solves
Hi Balamurugan,
Multi-unit configuration will configure different occurrences in the structure having different effectivity (with different end items) at the same time. This eliminates the need of maintaining different product structure and difficult manual reconciliation.
This feature takes care the occurrence is not duplicated by reloading, when the match is found again for the same occurrence.So, it applies the OR condition, i.e. the occurrence will be loaded if any of the condition matches in the effectivity group. If it has to load on both the conditions met (AND), the occurrence will be duplicated (loaded twice), hence defeating the whole purpose.
If we want to have one holistic BoM (single point of truth) for a specific Product, and configure its specific Item Revs to be valid for specific builds, can we utilize Occurrence Effectivity to do so. Basically declare which IR’s are valid for specific representations of the BoM, and retrieve that BoM representation by invoking the appropriate Rule and Effectivity?
Hi Ken,
If the set unit number or date in the revision rule ,configures the occurrences of specific item revisions by its effectivity,then yes.
If the product structure is to be configured by specific item revisions based on its effectivity, we go for revision effectivity.
A product structure can have different types of changes and accordingly appropriate effectivity is used for its configuration.
1) Revision effectivity is used in smaller scope and is easily managed .This is used to configure the specific revision by its effectivity in the structure.
With NX and CAD integration this works well.
2) Occurrence effectivity is used for out-of-sequence or unrelated changes.This is used in larger scope of the product structure.
Other difference of configuring revision and occurrence is , for the same revision, occurrence effectivity can differ in differnt BOM.
3) Incremental change effectivity is mostly used for out-of sequence changes in flat structure.
So, the product structure can have combinations of different type of effectivities to configure it as per the requirement.
Thank you Anjali. That helps clarify the topic. I appreciate the guidance on this.
Anjali – on your Point number 2 above – why can’t I just use Revision effectivity in context of a specific End Item instead of using Occurrence effectivity which seems to be more complex? Is there a drawback to do that?
Hi Hakim,
Use of occurrence or revision effectivity is based on how the product structure modeling is done.Product is configured based on revision effectivity to display the state at which a part is (say,each development of part’s state is captured in a revision)(smaller scope) in the assembly at different stages(planning,design,production etc. )of manufacturing cycle, say at a certain date.Occurrence effectivity is used when the part is replaced with another part(larger scope) to undergo some modification of the product.
Let me try to explain this with an example.Let’s say a bottle is manufactured, where there are three grooves in bottle head and three grooves in cap.Say,each groove is created with each revision of part, at certain stage of manufacturing cycle.Using revision effectivity, we can find out the state of product with its part at certain date(appropriate revision of the same part will be configured).
Now say, this bottle had wider mouth with wider cap.It would help the customer if bottle had narrower mouth.Here comes the occurrence effectivity.Now the bottle head has narrow mouth with three grooves and narrow cap with three grooves.The narrow bottle head and narrow cap both will be different part now with its own set of revisions.Occurrence effectivity will configure the narrower mouth and cap bottle for a certain date.Broader mouth bottle was effective in some past date.
Another question: We are working imprecise (Part BoM and E-BoM combined). For each End Item Rev that is released, the BoM must be frozen in that state so that it may be accurately reflected in higher level assemblies that may consume it. Therefore, each End Item Revision is considered a precise commodity which may be a child to a higher assembly which also might ultimately be an End Item, and therefore have their Revisions locked as precise consumable commodities as well. Is there any way to do this without going Precise?
It should be achieved by nested effectivity. When a product structure with End Item CAR(A10010) has a sub-assembly with End Item-Engine(E10010), end item context changes at the subassembly to configure the whole product structure based on effectivity. For more details, please refer to: https://tcplmbasics.com/2018/03/27/revision-nested-effectivity/
When there is more than one revision to End Item and the structure needs to be configured correctly, nested effectivity can be used with Product Generation technique. Each revision of the End Item can be considered as a generation and can be used as an End Item. So, corresponding to A10010/A, end item is generation GenACar & for A10010/B, end item is generation GenBCar with different effectivity. Also, for engine E10010/A, end item is GenAEngine & for E10010/B , end item is GenBEngine with different effectivity.
Effectivity mapping needs to be created for this on engine to configure the structure correctly based on the correct generation of the end item. Example of effectivity mapping.
Effectivity Mapping on Engine
End Item ——-Range——–Sub_effectivity on engine via generation
GenACar———Date Range—–GenAEngine
GenACar———Date Range—–GenBEngine
GenBCar———Date Range—–GenBEngine