What is Revision Effectivity?

Based on the rule entry (effective date or unit numbers ) in the revision rule and with specified date, unit number or the combination , an effective revision is configured in the structure. Revision effectivity data is stored on attached release status object of the revision.

Click on Tools –>Effectivity –>Revision Effectivity by selecting the structure line to launch the Effectivity Dialog:

• Display: Each status attached to item revision and its effectivity range is displayed in table rows.
• Create/Edit : Create or Edit button launches Edit Effectivity dialog that will add effectivity range to attached status.
• Add : Multiple effectivities can be created on same status with different end items, by selecting the status with effectivity and clicking on Create button. This encourages use of same components in different products.

Nested Effectivity

A product structure may include a product from an external supplier, which will have its own effectivity separate from the effectivity of product structure. For example, engine may not be owned by the manufacturer of car and it is used in the product structure of the car. Since in revision rule only one end item (for effectivity rule entry) can be set, configuring product structure with end item of car, will not configure the product engine that has its sub-structure with end item of engine. Here comes the role of nested effectivity. Nested effectivity will change the end item context from car to engine at the engine. Configuration item is used for this context change. With nested effectivity implemented, the product structure of car including the product engine (its sub-structure) will be configured.

Configuration Item

Configuration Item is created for each sub-structure configured by a different end item in the product structure. This item is set at the top level item of the substructure. Configuration item does not need to be created separately. An item can be identified as a configuration item by setting configuration item property to true. While creating item, configuration item checkbox can be selected.

This checkbox needs to be enabled in BMIDE from CreateInput tab of Operation Descriptor of item business object type.

 

Effectivity mapping allows modifying of the parameters of the revision rule as the end item context changes at the configuration item. Effectivity mapping on configuration item can be defined or viewed by selecting Tools–>Effectivity–>Effectivity Mapping

Nested Effectivity Example

Let’s take an example:

In a car is fitted an engine control module, commonly known as ECM. The main responsibility of this controller is to get information from sensors in the engine and function accordingly. In case of any errors, the ECM shows a check engine light on car’s dashboard. Engine coolant temperature sensor is one sensor on engine the information of which is retrieved by ECM to display on dashboard and function accordingly.

ECM is attached to car but it displays information from engine. ECM and its subassembly has end item of engine. At the same time, ECM is also part of car which displays information from engine on dashboard of car. This is the point where end item context changes from car to engine.

Following example shows the product structure of car with engine control module (ECM) and its subassembly. ECM will be the configuration item. Revision rule is applied and the structure is configured as shown.

Nested Effectivity can be put anywhere in revision rule. This takes care of effectivity mapping on configuration items. End Item will switch from car to engine, while configuring sub-assembly of these configuration items.

Configured with Nested Effectivity

Configured without Nested Effectivity

With no Nested Effectivity in revision rule, effectivity mapping on configuration items are ignored.

End Item context does not change at configuration items (no switch) and the sub-assembly with end item of engine are not configured for product structure with end item of car. ??? denotes no configurable revision found.

Reference Read: Revision Rules

Also Read:

Occurrence Effectivity in Teamcenter

Incremental Change in Teamcenter

Classic Variant Configuration in Structure Manager

Modular Variant Configuration in Structure Manager

BOM Compare in Teamcenter

Supersedure in Teamcenter

 

Was this post helpful?