Skip Headers

Agile Product Lifecycle Management Product Collaboration User Guide Release 9.3.3 E39292-01 |
| Contents

Previous | Next |

# 6 Variant Management

Variant Management is a strategic direction for Agile Product Lifecycle Management solutions.

## 6.1 About Agile PLM Variant Management

Diversity and complexity of product variance is a cross-industry challenge, driven by strong demand among consumers for mass customization and personalization. Consequently, Variant Management continues to be a critical consideration early in the product lifecycle, especially as evolving design paradigms influence product variance.

The Variant Management solution enables Product Collaboration to store a single "Model Option BOM", which represents all variants of a product line. The Model Option BOM is the basis for deriving an Instance BOM, to validate prototypes, and establish made to stock pre-configurations. An Instance BOM can be generated either internally or externally:

- Internal Configurator

Instance Manager - an Agile 9 mask and User Interface.

- External Configurator

Oracle Generic Configurator User Interface - an Oracle mask and User Interface.

Depending on which Configurator you would like to work with, a setting has to be made in the Preferences tab of My Settings.

Detailed information about privileges, activating the Internal Configurator, activating the External Configurator, and Event Management for Variant Management can be found at Configuring Variant Management on page 267.

Note: This document will describe the Instance Manager in detail. The Oracle Generic Configurator User Interface is only briefly described.

Note: Further information about the Oracle Generic Configurator User Interface can be found in the Oracle Configurator Implementation Guide from OTN (`http://www.oracle.com/technology/documentation/applications.html`).

## 6.2 Configuring Agile PLM Variant Management

In Agile PLM a BOM is created that contains Items like Models, Option Classes, Parts, Assemblies, and Documents for a product range. This BOM is called Model Option BOM.

### 6.2.1 How Agile PLM Variant Management Works

Each BOM item can be a mandatory or an optional item. Because a Model Option BOM contains all possible variants, the Internal Configurator (Instance Manager) or the external Configurator (Oracle Generic Configurator User Interface) is used to derive an individually configured product, an Instance BOM. The Model Option BOM is a superset of all potential BOMs and is not itself intended to be manufactured.

The creation of the Model Option BOM, and the configuration of the Instance BOM with the internal or external Configurator depend on rules. Further information about these rules can be found at Combination Rules on page 123.

#### 6.2.1.1 Description of the BOM Items

Item | Description
--- | ---
Model | A Model is denoted by the icon. A Model is used as the top level element of a Model Option BOM, but can also used as a generic item on lower levels under Models or Option Classes. Models cannot be added to Parts or Documents. The BOM tab of a Model contains the additional fields: Min Qty (minimum quantity) Max Qty (maximum quantity) Optional Mut Excl (mutually exclusive) A Model can contain items such as Models, Option Classes, Parts, Assemblies, and Documents in its BOM structure. These items can also be components of other objects to define a different product. A Model with an assigned BOM structure is denoted by the icon. Note The internal or external Configurator can only be opened from a Model! Note We do not support a site specific BOM for Models. Note The Agile administrator is able to create subclasses with the part subtype of the type Model.
Option Class | An Option Class is denoted by the icon. An Option Class acts like a placeholder in a BOM which is later replaced by at least one of its options. The BOM tab of an Option Class contains the additional fields: Min Qty (minimum quantity) Max Qty (maximum quantity) Optional Mut Excl (mutually exclusive) An Option Class can have Models, Option Classes, Parts, Assemblies, and Documents in its BOM structure. An Option Class with an assigned BOM structure is denoted by the icon. Note We do not support a site specific BOM for Option Classes. Note The Agile administrator is able to create subclasses with the part subtype of the type Option Class.
Part | A Part is a final standard item. A Part can have Parts and Documents in its BOM structure, thus it is called Assembly. A Part is also used as the Instance for the Instance BOM. The Title Block tab of the Part contains the field Base Model that lists the number and revision of the Model to which this Part was added as Instance.
Assembly | An Assembly is a Part with a BOM.
Documents | Documents are treated as Parts.

#### 6.2.1.2 Possible Combinations

The following diagrams show possible combinations of Models, Option Classes, Assemblies, and Parts in the Model Option BOM.

The following diagram shows all possible Model combinations.

The following diagram shows all possible combinations with Option Classes.

The following diagram shows all possible combinations with Parts and Assemblies.

#### 6.2.1.3 Mandatory

Items that are defined as mandatory Items in the Model Option BOM, will automatically be copied to the Instance BOM. They cannot be deselected in the Instance Manager.

Note: A detailed description of combination rules and their impact on the Instance BOM can be found under Combination Rules on page 123.

#### 6.2.1.4 Optional

When defining an Item as an Optional Item in the Model Option BOM, it can be selected or deselected for the Instance BOM.

By default, this field is set to Null which is equivalent to the setting No.

Note: A detailed description of combination rules and their impact on the Instance BOM can be found under Combination Rules on page 123.

#### 6.2.1.5 Minimum/Maximum Quantity

- When defining a minimum and maximum quantity for an Item in the Model Option BOM, it is possible to choose a quantity value of type Floating Point Value within this range (including the minimum and maximum quantity) in the Instance Manager.

- The minimum and maximum quantity value has to be >0. It cannot be a negative value.

- When no minimum and maximum quantity is defined, the Quantity column in the Instance Manager is read only.

- When entering only a minimum quantity, the maximum quantity can be up to the biggest possible number.

- When entering only a maximum quantity, the minimum quantity has to be > 0.

Note: A detailed description of combination rules and their impact on the Instance BOM can be found under Combination Rules on page 123.

#### 6.2.1.6 Mutually Exclusive

Only the BOM entries of an Option Class can be defined as Mutually Exclusive in the Model Option BOM. This defines that exactly one valid option of an Option Class has to be selected for the Instance BOM. In case the Option Class is Optional AND Mutually Exclusive, and is not selected in the Instance Manager, no option of the Option Class has to be selected.

By default, this field is set to Null which is equivalent to the setting No.

Note: A detailed description of combination rules and their impact on the Instance BOM can be found under Combination Rules on page 123.

Note: Mandatory items of an Option Class are not affected by the Mutually Exclusive regulation.

#### 6.2.1.7 Combination Rules

The following rules influence the behavior of the Instance Manager and are applied when deriving an Instance BOM.

Note: Further information about the combination rules for the Oracle Generic Configurator User Interface can be found in the Oracle Configurator Implementation Guide from OTN (`http://www.oracle.com/technology/documentation/applications.html`).

Note: The following screenshots show only possible examples.

#### 6.2.1.8 Valid Options of an Option Class

1. An Option Class has to have at least one valid option. An empty Option Class is not valid.

2. Options are mandatory or optional items.

3. An Option Class containing only mandatory options is valid.

4. If a mandatory Option Class has only optional options, at least one option has to be selected in the Instance Manager.

5. If an optional Option Class has only optional options and is selected in the Instance Manager, at least one option has to be selected in the Instance Manager.

6. If an optional Option Class is not selected in the Instance Manager, it is not required to select an option in the Instance Manager.

#### 6.2.1.9 Mutually Exclusive BOM Items

1. Only Option Classes can be mutually exclusive.

2. Mandatory items (Parts, Assemblies, Option Classes, and Models) have no influence on the mutually exclusive behavior.

#### 6.2.1.10 Mandatory BOM Items

1. Mandatory items are always selected and cannot be deselected in the Instance Manager.

2. All mandatory child items of a selected parent item are automatically selected.

3. An optional item that is the only valid option of an Option Class is automatically selected and cannot be deselected.

4. Child items of a Part are mandatory items. The system considers this Part as an Assembly.

#### 6.2.1.11 Quantities of BOM Items

Note: Quantities are not calculated during the configuration in the Instance Manager. The entered quantity is independent of other quantities in upper or lower levels. The quantity does not change automatically during a configuration. The quantity of an item is relative.

1. For every selected item a default quantity is automatically assigned.

2. Entered quantities have to be >0. Otherwise, an error message is displayed.

3. If a minimum and/or maximum quantity has been defined for an item, the quantity can be entered manually, however, the quantity entered must be within the defined parameters.

4. If a predefined alphanumeric quantity value is not a valid number, the system ignores the minimum and/or maximum values and copies this predefined value into the quantity column.

5. The default quantity can have alphanumeric quantity values, thus the quantity is not changeable in the Instance Manager.

#### 6.2.1.12 Selecting BOM Items

1. When selecting a child item, the parent item is automatically selected.

   NoteWhen deselecting an optional parent item, all selected child items will be deselected as well.:

   - When clearing the Quantity field of an entry with minimum and maximum values, this entry will be deselected.

2. Every item with a valid quantity (>0) in the Quantity column of the Instance Manager is selected.

#### 6.2.1.13 Documents as BOM Items

Note: Documents and their structure are treated like Parts and Assemblies.

#### 6.2.1.14 Model Option BOM

When you create the Model Option BOM, make sure all entries are created like defined in the Combination Rules, and explained in the Possible Combination sections.

A Model Option BOM is the basis for a derived Instance BOM.

Important: We recommend DO NOT modify the Model Option BOM, from which the Instance BOM will be derived, once the Instance Manager is opened. Modifying the Model Option BOM when the Instance Manager is open will result in discrepancies with the actual loaded structure and the currently modified structure.

Note: Variant Management does not support temporary items that are added to the Model Option BOM as placeholders. It also does not support duplicate item number on the same BOM level.

WARNING: Recursive structures are not supported in Variant Management.

Further information about possible combinations in the Model Option BOM can be found at Possible Combinations on page 119.

Further regulations about combinations (e.g. only Parts can be children of Parts) can be found in the Smart Rules in the Agile PLM Administrator Guide.

Important: Recommendation for Model Option BOMs with more than 2500 entries in total:

By default, Agile A9 allows to create BOMs with maximum 2500 entries. To be able to create BOMs with more than 2500 entries, the preference value can be updated via the following SQL statement:

update propertytable set value = 2500 where PARENTID = 5004 and PROPERTYID = 811;

commit;

Setting the value to 0, allows expanding BOMs with unlimited entries.

You require Administrator rights to update the SQL statement!

#### 6.2.1.15 Quantities

For every BOM item, quantity values can be defined, either as a constant value or selectable between minimum and maximum values.

Note: For further information about minimum and maximum quantities see: Minimum/Maximum Quantity on page 123

Quantity fields are restricted to 20 characters and can be either Integer or Floating Point Values.

Note: When working with the external configurator, make sure Models and Option Classes have only Integer Values assigned for Quantity. Floating Point Values are not supported for Models and Option Classes. Otherwise, the external configurator produces warnings and sets it to an invalid configuration.

Quantity values cannot be negative values, they have to be >0.

- The Quantity field in the Instance Manager is a read-only field for BOM items:

  - with the same minimum and maximum quantity value

  - with a predefined alphanumerical value

- The Quantity field in the Instance Manager is an editable field for BOM items:

  - with a defined minimum or maximum value range

#### 6.2.1.16 Alphanumerical Quantity Values

An alphanumerical quantity value (e.g. xy) can be entered into the Qty field of a Part as placeholder. This placeholder can be replaced by a real value in the Instance BOM.

Note: The Quantity field in the Instance Manager shows the entered alphanumerical value and is read-only.

#### 6.2.1.17 Reference Designator

Note: For detailed information about the Reference Designator, see: Agile Product Lifecycle Management Product Collaboration User Guide.

Reference Designator can be entered only for a BOM item of subtype Part. The quantity value in the Qty field should match the quantity of the Ref Des field. Otherwise, a warning is displayed which can be ignored or resolved.

In the Instance BOM, it can be possible that the quantity value does not match the Reference Designator. This is due to the multiplication of the quantity of Option Classes with the quantity of their options. To correct the discrepancy, you have to amend either the value of the quantity or the value of the Reference Designator in the Instance BOM.

#### 6.2.1.18 Instances Tab

The Instances tab lists all created Instances with a status symbol.

Symbol | Name | Description
--- | --- | ---
| Has no configuration | This symbol is assigned to an Instance that has not been configured with the Instance Manager.
| Has Configuration Draft | This symbol is assigned to an Instance that has been configured with the Instance Manager but has not been derived.
| Has derived Instance BOM | This symbol is assigned to an Instance that has been configured with the Instance Manager and has been derived.

Only items of subtype 'Part' can be added as an Instance. A Part without a BOM can also be dragged and dropped from e.g. the Recently Visited folder in the left pane.

Although the drag and drop process of other items like Models, Option Classes, or Documents is displayed with a green drag and drop symbol, an error message will be displayed when dropping them onto the Instances tab. These items cannot be dropped onto the Instances tab.

A Part can only be associated to a specific revision of a specific Model. A user, who attempts to add the same Instance (Part) to another revision of the Model, or to a different Model, will get an error message.

Note: Performed actions on the Instances tab are not tracked on the History tab.

#### 6.2.1.19 Instance

To configure an Instance BOM in the Instance Manager, you have to add a so called Instance (a Part) to the Instances tab of the top level Model of the Model Option BOM.

Note: A Part can only be added to the Instances tab when it does not have a BOM structure.

Note: The added Part, which is the Instance, has to be in a state in which its BOM table can still be modified. This Part should not be assigned to a Pending Change or is in the state Released.

Ø To avoid inconsistencies in the Instance Manager do not create a pending change or revision for a configurable Instance which is currently opened in the Instance Manager.

Important: Do not assign a BOM manually to an Instance. When you assign a BOM manually to an Instance, the status symbol changes to ' Has derived Instance BOM', but no Configuration Graph has been created.

A BOM will automatically be assigned to an Instance once the Instance has been configured and an Instance BOM has been derived.

Several Instances can be displayed and configured in the Instance Manager.

An Instance can only be configured by one user at a time. When you try to launch the Instance Manager for an Instance that is in use by a different user, a message is displayed.

You can load a derived Instance into the Instance Manager to compare the configuration of the derived Instance with a new Instance. If you load only the derived Instance into the Instance Manager, only the functions Expand, Collapse, personalized view, and Close are available.

#### 6.2.1.20 Propagate Instance Revision

Note: You require the Modify privilege on the Configuration Graph in order to have the Propagate button activated. Otherwise, the Propagate button is grayed out.

Note: The Propagate function can only be applied to a not derived Instance.

On the Instances tab, when clicking the Propagate button, a pop-up window is opened that lists all Instances with Configuration Graph for all Model Option BOM revisions. Selecting an Instance from this list, copies its configuration to the selected Instance of the current Model Option BOM revision.

Example of the information shown in the select menu:

Model Revision | Instance Item Name | Item Description
A C00010 | P00010 | Test Name

#### 6.2.1.21 Instance Manager

Important: To be able to work with the Instance Manager, the setting 'Internal Configurator' needs to be activated in the Preferences.

Note: To activate it, see: Activating 'Internal Configurator' - Instance Manager

Note: You require the Configure Instance privilege to open the Instance Manager. Otherwise the Launch Configurator button on the Instances tab is grayed out.

The Instance Manager is launched from the Instances tab of the Model containing the Model Option BOM. It shows the complete Model Option BOM and allows configuring the entries to derive the Instance BOM.

Important: Only one Instance Manager can be opened at a time.

Note: Only if the Model Option BOM is valid, the Instance Manager is opened. Otherwise, an error message is displayed.

Note: No error message is displayed when opening the Instance Manager for a Model without a BOM.

#### 6.2.1.22 Configuration Graph

Important: By default, the Configuration Graph field of the Instances tab is hidden. To make it visible, the view needs to be personalized.

Important: We strongly recommended not to manually modify the Configuration Graph.

In the Instance Manager, when you click the Save as Draft or Create Instance button, a Configuration Graph is created for the Instance. This Configuration Graph is stored as an XML file and contains information about all configurations that you made in the Instance Manager.

#### 6.2.1.23 Derive Instance BOM

Once you have configured the Instance in the Instance Manager, you can derive the Instance BOM. For the derivation process, the Model Option BOM and the Configuration Graph are considered.

The derivation process starts when you click the Create Instance button, and no error message is returned for the configuration of the Instance.

If an error occurs during the derivation process, the derivation is stopped and the Instance BOM is not created completely. Please remove manually the incomplete Instance BOM from the respective Instance, resolve the occurred error, and derive the Instance again.

During the process of deriving the Instance BOM, the Configuration Graph is stored, and the Instance BOM is saved.

The following is performed:

- Models are replaced by newly created Parts.

Note: When a model is replaced by a newly created Part, in the Java Client, the Part subclass should have at least one Autonumber assigned to it and also AutoGenerate set to Yes.

- Option Classes are replaced by options that were selected in its structure.

- The correct quantity is calculated for parts, considering the quantities of all parent Option Classes.

#### 6.2.1.24 Instance BOM

The Instance BOM describes a specific configuration derived from a Model Option BOM and contains only those options that have been selected in the Instance Manager. In addition, all mandatory BOM items of a Model Option BOM are also part of the Instance BOM.

Note: Once the Instance BOM is derived, the Instance BOM as well as the Model Option BOM can be modified independent of each other.

The Instance BOM shows every Part with its correctly calculated quantity. The correct quantity for a Part that replaces an Option Class is calculated with the quantity of the Part, multiplied with the quantity of its parent Option Classes. The quantity calculation for Assemblies is done at top level, thus the quantity for children of Assemblies is not calculated. The quantity for an Assembly in the Instance BOM is the same as defined in the Model Option BOM.

Note: If the quantity shows an alphanumeric value, no calculation is performed with this value. The Quantity field in the Instance BOM will show the alphanumeric value.

The Instance Manager, after clicking the Create Instance button, shows a read-only preview of the derived Instance BOM. Modifications to the Instance BOM can be made in the BOM tab of the respective Instance.

#### 6.2.1.25 Revisions

Important The Model Option BOM and its objects can have different revisions, but we strongly recommend to always use the latest revision of a Model Option BOM in the Instance Manager.

- The Instances tab is revision specific. Each Instance is assigned to one specific Model revision. Thus, after creating a new revision of a Model, the Instances tab is empty. Newly added Instances to the Instances tab of this Model revision are always shown with their latest released revision.

  - Instances on the Instances tab of older revisions of this Model are shown with their revision at the state before the revision of the Model was changed.

Important: We recommend do not add and do not delete Instances from old Model revisions. Please contact your administrator to set the correct privileges for this behavior.

- In the just created Instance BOM, a Part is always shown with its latest released revision.

Note: This revision can be different to the revision shown in the Model Option BOM from which the Instance BOM is derived.

- In the just created Instance BOM, the Part, which replaces a selected Model, shows the same tab content as the tabs of the replaced Model.

#### 6.2.1.26 Import / Export

The import / export behavior for Variant Management is the same as the standard import / export behavior.

Note: The import from, or export into PDX files is not supported.

For more information see Agile PLM Import/Export User Guide.

#### 6.2.1.27 Import Objects into Instances Table

For Variant Management you can import Parts as Instances into the Instances tab of Models.

We recommend that you check the Instances tab for already derived Instances before performing an import to the Instances tab.

If the Instances tab contains already derived Instances, please set the Smart Rule DeleteInstanceWithBOM to Allow. Otherwise, a warning is displayed and the import process is stopped at the point where the error occurred.

Note: The import process will not be rolled back and may be partially performed.

Note: The import process will replace the complete Instances tab, independent of the selected import preferences for the Multi Row Update Mode.

#### 6.2.1.28 Import Configuration Graph into Instances Table

The Configuration Graph can only be imported into the same Agile 9 system.

When importing an Instance with Configuration Graph into a Model Option BOM, make sure the Model Option BOM contains the same BOM items and structure as the Configuration Graph.

We strongly recommend not to manually modify the Configuration Graph before importing it.

Note: You need to have the Modify privilege on the Configuration Graph field. This can be configured by assigning Item.Instance.Configuration Graph to the Modify Items privilege in your role.

For further information about the Configuration Graph format see the Appendix of the Agile PLM SDK Developer Guide.

## 6.3 Working with Agile PLM Variant Management

Note: The instructions in this section are referring to the Web client only, but some actions can also be performed in the Java client.

### 6.3.1 Creating a Model Option BOM

The top level element of a Model Option BOM is always a Model. For a detailed description of possible combinations see the chapter Configuring Agile PLM Variant Management.

A Model Option BOM can contain Models, Option Classes, Parts, Assemblies, and Documents.

To simplify the following examples, only Option Classes are added to the Model Option BOM.

#### 6.3.1.1 Creating a Model

To create a Model:

1. Select Create New > Items > Parts.

   The Create New Parts dialog box is opened.

2. In the new window, select the Type Model.

3. Enter a unique identification number (unique identifier for the Model) in the Number field, or click for the system to generate a number based on the Auto Numbering functionality defined for Models.

4. Click Save.

   The new Model appears with the Title Block tab showing.

5. Fill in information as desired.

6. Click Save.

#### 6.3.1.2 Creating a BOM Entry with Min/Max Value

You can define a minimum and maximum value for a BOM entry. The concrete value for this item is then selected in the Instance Manager for the Instance BOM.

To create a BOM Entry with Min/Max Value

1. Open the newly created Model.

2. Open the BOM tab.

3. Click the Add button.

4. Select an Option Class.

   Note: If no Option Class is selectable, create a new one.

5. Click the Add button.

   The Option Class is added to the Model BOM list.

6. To edit the Min Qty field double click it.

7. Enter a value for the minimum quantity and hit the enter key.

8. To edit the Max Qty field double click it.

9. Enter a value for the maximum quantity and hit the enter key.

   Note: The maximum quantity value has to be greater than or equal to the minimum quantity value.

10. Enter a value into the Qty field that is within the defined minimum / maximum range.

    The here defined value is the default value shown in the Instance Manager.

11. To save the changes click the Save button.

#### 6.3.1.3 Creating an Optional BOM Entry

You can define optional BOM entries. Such entries CAN be selected for the Instance BOM.

To create an Optional BOM Entry

1. Open the newly created Model.

2. Open the BOM tab.

3. Click the Add button.

4. Select an Option Class.

   Note: If no Option Class is selectable, create a new one.

5. Click the Add button.

   The Option Class is added to the Model BOM list.

6. To edit the Optional field, double click it.

   A select menu is opened.

7. Select Yes.

8. To save the changes click the Save button.

#### 6.3.1.4 Creating a Mutually Exclusive BOM Entry

You can define mutually exclusive Option Class BOM entries. This means that only one valid BOM entry of this Option Class has to be selected for the Instance BOM.

Note: A detailed description of combination rules and their impact on the Instance BOM can be found under Combination Rules on page 123.

To create a Mutually Exclusive BOM Entry

1. Open the newly created Model.

2. Open the BOM tab.

3. Click the Add button.

4. Select an Option Class.

   Note: If no Option Class is selectable, create a new one.

5. Click the Add button.

   The Option Class is added to the Model BOM list.

6. To edit the Mut Excl field, double click it.

   A select menu is opened.

7. Select Yes.

8. To save the changes click the Save button.

Note: The BOM tab of this Option Class has to have at least one valid option. A detailed description of valid options can be found under Combination Rules.

#### 6.3.1.5 Creating an Optional Mutually Exclusive BOM Entry

You can define mutually exclusive Option Class BOM entries that are optional. If selecting this optional Option Class for the Instance BOM, only one valid BOM entry of this Option Class has to be selected for the Instance BOM as well.

Note: A detailed description of combination rules and their impact on the Instance BOM can be found under Combination Rules on page 123.

To create a Mutually Exclusive BOM Entry

1. Open the newly created Model.

2. Open the BOM tab.

3. Click the Add button.

4. Select an Option Class.

   Note: If no Option Class is selectable, create a new one.

5. Click the Add button.

   The Option Class is added to the Model BOM list.

6. To edit the Mut Excl field, double click it.

   A select menu is opened.

7. Select Yes.

8. To edit the Optional field, double click it.

   A select menu is opened.

9. Select Yes.

10. To save the changes click the Save button.

    Note: The BOM tab of this Option Class has to have at least one valid option. A detailed description of valid options can be found under Combination Rules.

#### 6.3.1.6 Adding Manufacturer Sites to a Model Option BOM

We do not support site-specific information for Models and Option Classes, and thus the Site tab is disabled for Models and Option Classes.

#### 6.3.1.7 Checking the Model Option BOM

A first check of the Model Option BOM can be carried out with the Check Model-Option BOM function in the More menu of the BOM tab.

To check the Model Option BOM:

1. Open the Model that contains the Model Option BOM.

2. Open the BOM tab.

3. Open the More menu.

4. Select Check Model-Option BOM.

If the Model Option BOM is correct, no error message is displayed.

If the Model Option BOM contains errors, a list with all errors is displayed.

### 6.3.2 Deriving an Instance BOM with the Internal Configurator

Note: The information of this section is referring to the Web client only.

Once all BOM items have been added to the Model Option BOM, the different product variants can be derived to an Instance BOM.

The Instance BOM is referenced in the Instances tab of the Model containing the Model Option BOM. For every product variant an Instance (a Part) has to be created here. The Instance BOM, which will be derived with the help of the Instance Manager, is then added to the BOM tab of this Instance. Once the Instance BOM is derived, the Instance is displayed as an Assembly.

#### 6.3.2.1 Creating an Instance

To Create an Instance:

1. Open the top level Model of the Model Option BOM.

2. Open the Instances tab.

3. Click the Add button.

4. Click the Create to Add button.

   The Create New window for the type Part is opened.

5. Create a new Part.

   This Part is then called Instance.

   Note: The created Part, which is the Instance, has to be in a state in which it still can be modified (e.g. a released part or a part with a pending change cannot be used as an Instance).

6. Click the Add button.

   The Part is added to the Instances tab with the status Has no configuration.

#### 6.3.2.2 Configuring One Instance

To configure one Instance:

1. In the Instances tab select the Instance of the respective product variant.

   Note: Only Instances with no BOM assigned to it can be configured.

2. Click Launch Configurator.

   Note: Only if the Model Option BOM has been created with valid entries, the Instance Manager is opened. Otherwise, error messages are displayed.

   The Instance Manager is opened, showing all entries of the Model Option BOM. Guide icons are displayed next to any selections with open issues.

   At the end of the table, the columns Select and Quantity have been added to an Instance.

   Note: An entered Reference Designator in the Model Option BOM is copied into the Ref Des field of the Instance Manager. Its value of the Qty field in the Model Option BOM is copied into the Quantity field of the Instance Manager.

   Note: For complete information about Reference Designator, see Agile Product Lifecycle Management Product Collaboration User Guide.

3. In the Select column, select all entries for the Instance BOM.

4. In the Quantity column, - where possible - enter the quantity for the Instance OM.

5. Click Save as Draft to save the configured Instance BOM.

   Note: As soon as the Instance is saved, the Configuration Graph is created. The status of this Instance is set to Has Configuration Draft.

#### 6.3.2.3 Validating the Instance

Before you can create the Instance BOM, you have to validate the configured Instance.

To validate the Instance:

1. In the Instances tab select an Instance.

2. Click Launch Configurator.

   The Instance Manager is opened, showing all entries of the Model Option BOM.

3. Click Validate.

This checks if the configuration complies with all combination rules.

Note: A detailed description of combination rules and their impact on the Instance BOM can be found under Combination Rules on page 123.

If the validation returns errors, a message like the following can be displayed.

In this case, you have to resolve the listed errors first.

Note: The same validation is carried out when clicking the Create Instance button.

#### 6.3.2.4 Comparing and Modifying Instances

In the Instance Manager, more than one Instance can be opened. This allows you to compare the configuration of Instances with each other and modify more than one Instance at a time.

To compare the configuration of Instances:

1. In the Instances tab select all Instances that you wish to compare.

   For comparison, an already derived Instance BOM can also be opened in the Instance Manager.

2. Click Launch Configurator.

   Note: Only if the Model Option BOM is valid, the Instance Manager is opened. Otherwise, an error message is displayed.

   Note: An already derived Instance BOM is not validated again before opening it in the Instance Manager.

   The Instance Manager is opened, showing all entries of the Model Option BOM, and the configuration of each Instance.

Note: The Save as Draft operation applies to all Instances opened in the Instance Manager. The Create Instance operation applies only to the selected Instance.

#### 6.3.2.5 Creating the Instance BOM

Once you have done all configurations and resolved possible errors, the Instance BOM can be created.

To create the Instance BOM:

1. Select the Instance.

2. Click Create Instance.

The Instance BOM is created and is displayed as a preview in the Instance Manager window. A Back button at the bottom left of the Instance Manager window allows to go back to the configuration window in the Instance Manager, which is displayed as read-only.

Note: In the Instances tab of the Model, the previously created Part for the Instance is now displayed with the Icon of an Assembly. The status of the Instance is set to Has derived Instance BOM.

The BOM tab of this Instance shows the result of the configurations performed in the Instance Manager.

### 6.3.3 Propagating the Configuration of One Instance to Another

Once the Instances tab of the Model Option BOM contains a derived Instance BOM or an Instance with Configuration Graph, the Configuration Graph of this Instance BOM can be propagated to a not derived Instance.

To propagate the Configuration Graph of one Instance to another:

1. Open the Instances tab.

2. Select a not derived Instance (target Instance).

3. Click Propagate.

   The Select an Instance for propagating a configuration to Pxxxx window is opened.

4. From the Instance: drop-down menu, select the source Instance from which the configuration should be propagated to the target Instance.

5. Click OK.

   Note: In case the target Instance already contains a configuration, a Warning is issued.

   Now, the target Instance contains the same configuration as the source Instance and its status is set to Has Configuration Draft.

### 6.3.4 Importing / Exporting Variant Management Information

All items and their subclasses can be imported into, and exported from Agile PLM.

Note: For complete information about how to import/export, see Agile Product Lifecycle Management Import/Export User Guide.

#### 6.3.4.1 Exporting into aXML Files

To export into aXML files:

1. Open the model you would like to export.

2. Click Actions.

3. Select Export.

   The Export - Select Objects to Export window is opened.

4. From the Format field, select aXML.

5. Click Next.

6. Select Create custom filter.

7. Click Next.

   The Export - Select Item content to export window is opened.

8. Select Instances.

   Important: Make sure the selection Instances is selected. Otherwise, it is not included in the exported file.

9. Click Next till the Export - Specify Export Properties window is opened.

10. Enter your information.

11. Click Export.

#### 6.3.4.2 Importing aXML Files

Note: For detailed information on how to import aXML files, please see the Agile Product Lifecycle Management Import/Export User Guide.

To import aXML files:

1. In Agile 9 from the Tools and Settings menu select Import.

2. In the Import Wizard, browse for the file to be imported.

3. Click Next.

   The Import - Specify File Content window is opened.

4. Expand Item.

5. Select Item only, Bill of Material, and Instances.

   Every other selection is optional.

6. Click Next.

   The Import - Select Content Options window is opened.

   Make your selections.

7. Click Next.

   The Import - Specify Attribute Mapping window is opened.

8. Map the fields to be imported to the Agile Fields.

9. Click Next.

   The Import - Review Import Definition window is opened.

10. Review the summary of your import definition.

11. Click Import.

#### 6.3.4.3 Importing/Exporting PDX Files

Note: The import from and export to PDX files is not supported for Variant Management.

#### 6.3.4.4 Exporting into Text (csv) or Excel (xls) Files

To export into Text (csv) or Excel (xls) files:

1. Open the model you would like to export.

2. Click Actions.

3. Select Export.

   The Export - Select Objects to Export window is opened.

4. From the Format field, select either Text (csv) or Excel (xls).

5. Click Next.

6. Select Create custom filter.

7. Click Next.

   The Export - Select Item content to export window is opened.

8. Select Instances.

   Important: Make sure the selection Instances is selected. Otherwise, it is not included in the exported file.

9. Click Next.

   The Export - Specify Export Properties window is opened.

10. Enter your information.

11. Click Export.

#### 6.3.4.5 Importing Text (csv) or Excel (xls) Files

Note: For detailed information on how to import Text (csv) or Excel (xls) files, please see the Agile Product Lifecycle Management Import/Export User Guide.

To import Text (csv) or Excel (xls) files:

1. Prepare the file to be imported.

2. Open the Import Wizard.

3. Browse for the file to be imported.

4. Click Next.

   The Import - Specify File Content window is opened.

5. In the Item section, select the Instances radio button.

6. Click Next.

   The Import - Select Content Options window is opened.

   Make your selection.

7. Click Next.

   The Import - Specify Attribute Mapping window is opened.

8. Map the fields to be imported to the Agile Fields.

9. Click Next.

   The Import - Review Import Definition window is opened.

10. Review the summary of your import definition.

11. Click Import.

    Note: Repeat these steps to import the information from any other tab of a Model.

## 6.4 Working with Agile PLM Variant Management - External Configurator

The following section describes how to derive an Instance BOM with the Oracle Generic Configurator User Interface.

### 6.4.1 Deriving an Instance BOM with the External Configurator

Note: Settings, as described in the section External Configurator - Oracle Generic Configurator User Interface have to be done prior to working with the Oracle Generic Configurator User Interface.

Note: After creating the Model Option BOM like described in this document, the Oracle Generic Configurator User Interface can be used to derive an Instance BOM.

#### 6.4.1.1 Creating an Instance BOM with the External Configurator

Note: For further information about how to create an Instance, please see: Creating an Instance.

To create an Instance BOM:

Before the instance can be configured in the Oracle Generic Configurator User Interface, a Change Order with the respective workflow assigned to it has to be created first.

For further information about how to set up the respective workflow, please see: Agile PLM Integration Pack for Oracle E-Business Suite - Design to Release 2.5 - Implementation Guide.

1. Select the Model that contains the Model Option BOM.

2. Select Actions > Create New > Change.

3. From the Type field select ECO.

4. Click Save.

5. On the Cover Page tab in the Workflow field select the respective workflow.

6. Open the Affected Item tab.

7. Add all items of the Model Option BOM.

8. Add a new revision in the NewRev column for all entries (e.g. A).

9. In the Lifecycle Phase column select Prototype for all entries.

10. Set the Status of the ECO to Released.

    Note: In EBS, the released ECO has to be set to Implemented. The Oracle Generic Configurator User Interface can only show those BOM items that have been set to Implemented.

11. In the Instances tab of the Model select the Instance of the respective product variant.

    Note: Only Instances with no BOM assigned to it can be configured.

    Note: The created Part, which is the Instance, has to be in a state in which it still can be modified (e.g. a released part or a part with a pending change cannot be used as an Instance).

12. Click Launch Configurator.

    The Oracle Generic Configurator User Interface window is opened. A login is required for it.

    Note: Only if the Model Option BOM has been created with valid entries, the Oracle Generic Configurator User Interface is opened. Otherwise, an error message is displayed.

    Note: The Oracle Generic Configurator User Interface shows only optional BOM items. Mandatory BOM items are not displayed.

13. In the Select column, select all entries for the Instance BOM.

14. In the Quantity column, - where possible - enter the quantity for the Instance BOM.

    Note: The Oracle Generic Configurator User Interface always shows the absolute quantity values.

    Note: When changing the quantity of a child item, consider that the new value has to be a multiple of its default quantity. Further information about Quantity Cascade Calculations can be found in the Oracle Configurator Developer User Guide on OTN (`http://www.oracle.com/technology/documentation/applications.html`).

15. In the Generic Configurator User Interface click Finish to save the configured Instance BOM back to Agile A9.

    Note: In Agile A9 the Configuration Graph calculates the absolute quantity values back to relative quantity values.