Skip Headers

Agile Product Lifecycle Management Database Upgrade Guide Release 9.3.3 E39282-01 |
| Contents

Previous |

# A Upgrading from Agile Advantage 2006

You can upgrade an Agile Advantage 2006 file vault to Agile PLM 9.3.3 with the Upgrade File Vault Utility.

## A.1 Upgrade File Vault Utility for Agile Advantage

When upgrading from Agile Advantage 2006, the file vault structure must be reorganized. An Upgrade File Vault utility is provided for this purpose and can be found in the AGILE_HOME\AgileDomain\tools\ directory.

To upgrade the Agile Advantage file vault:

1. Unzip the UpgradeFVUtils.zip file to a temporary directory.

2. Backup the existing Agile Advantage file vault to a safe location.

3. Modify the following options and parameters in the config.properties file, located in the <UpgradeFVUtils_Home>\config directory:

   Parameters | Description
   --- | ---
   SourceStoreDir | Agile Advantage 2006 file vault store directory The value of SourceStoreDir is located in the Agile Advantabe 2006 registry key {HKEY LOCAL MACHINE\SOFTWARE\Agile Advantage\AgileIFS\StorDirs}.
   DestStoreDir | Agile PLM 9.3.3 file vault base directory
   FilePrefix | File prefixes of the Agile Advantage and Agile PLM files. The format is FilePrefix=AAschema1,932fileprefix1; AAschema2,933fileprefix2 You can use this option to upgrade multiple file vaults. All existing files will be renamed using the 9.3.3 file name prefix. If the 9.3.3 file name prefix is omitted, the default value is the same as the Agile Advantage file prefix.

4. Run the UpgradeFVUtils command.

   Windows: UpgradeFVUtils.cmd UNIX: UpgradeFVUtils.sh

   Parameters:

   Parameter | Description
   --- | ---
   -help | Displays the readme file.
   -upgrade [-configfile] | Upgrades the file vault with the named configuration file. If no configuration file is specified, the config.properties file located in the config directory is used. To specify a different configuration file, use the -configfile option. The option and path of the file must be enclosed in quotation marks; for example, "-configfile=c:\myconfig.properties"
   -rename <old file name prefix> <new file name prefix> | Only used to rename the file name prefix in the Agile PLM 9.3.3 file vault located in the DestStoreDir defined directory.

5. View the fvu.log file, located in the UpgradeFVUtils directory, for detailed information and error messages. The log file is overwritten each time the utility is run.

## A.2 Post-Upgrade Considerations

When upgrading from Agile Advantage 2006 to Agile PLM 9.3.3, existing objects must change to reflect the new structure. The following sections discuss how some existing Agile Advantage objects will appear in Agile PLM 9.3.3.

### A.2.1 Supplier Objects

Supplier objects on Agile Advantage are migrated to Agile PLM 9.3.3 with the following changes:

1. Suppliers are migrated as non-Web suppliers.

   Geography details are not migrated because of how the data is stored in the Agile PLM 9.3.3 database. In Agile Advantage, this attribute points to a single geographic location. In Agile PLM 9.3.3, geographic details are obtained from a cascading list containing Continent, Country, State, and Region information.

2. Contact users on the Users tab of Agile Advantage are not migrated as contact users of Agile PLM 9.3.3.

   Users are migrated as normal users without any association to a specific supplier. The migrated users are disabled and have no assigned roles and privileges. You must enable the users and associate them to a supplier. In Agile Advantage, the same user can be added to multiple suppliers. In Agile PLM 9.3.3, a user can be added to only one supplier.

3. The Manufacturer Parts tab in a Supplier object is not supported in Agile PLM 9.3.3.

   In Agile PLM 9.3.3, there is a Manufacturers tab in Supplier. This tab displays the manufacturer line cards for each manufacturer part in Agile Advantage. The price information that was available in the Manufacturer Parts of a Supplier is migrated to Quote History objects with the material and non-material costs migrated as Page Two fields of the Quote History object. The prices are visible in the Prices tab of the Manufacturer Part object. The Manufacturer Parts from the Supplier object are migrated to the Suppliers tab in the Manufacturer Part object.

### A.2.2 Manufacturer Part Objects

The Manufacturer Part object is migrated with the following changes:

1. The status of a supplier on the Supplier tab in Agile Advantage is not migrated to the Supplier tab of the Manufacturer Part in Agile PLM 9.3.3.

   The pricing details on the Supplier tab are moved to Prices in Agile PLM 9.3.3 as Quote History objects.

2. The standard cost and the target cost on the Cover Page of a Manufacturer Part object in Agile Advantage are moved to Page Two of a Supplier object in Agile PLM 9.3.3.

   Other price-related information, like Min Qty and Max Qty, are moved to the Cover Page tab of a Quote History object.

### A.2.3 Item Objects

Price information is revisable in Agile Advantage, but not in Agile PLM 9.3.3 This information is moved to Page Two of the Item object.

Agile PLM 9.3.3 does not support the summation functionality like Agile Advantage. Instead, you can run the Assembly Cost Report as part of Product Collaboration's report. If there is a missing price, Agile Advantage displayed the price with an asterisk (*), while the Assembly Cost Report in Agile PLM 9.3.3 displays the price as 0.

Unlike Agile Advantage, there is no feature available out-of-box to set the target cost based on the Supplier. You can manually set the costs in the Page Two fields of Items and Manufacturer Parts or this can be automated through a Process Extension.

### A.2.4 Compliance

In Agile Advantage, the compliance information on Manufacturer Part, Item, and Document objects is stored in 14 separate lists with the list label detailing the type of compliance this particular object meets. In Agile PLM 9.3.3, compliance information is a combination of Specification object and compliance status. During migration, the 14 lists on each object specified are moved as a Specification object with the specification name as the label of the enabled compliance list.

The migrated specification of Item and Document objects have a prefix of Item_ and Doc_ to differentiate between the specifications migrated from each object. The flex field information is moved to the Compliance tab, along with the status of each specification.

Unlike Agile Advantage, Agile PLM 9.3.3 does not support the Audit Report functionality for calculating compliance. Instead, customers can use the BOM Compliance Report which displays similar compliance information. Likewise, Agile PLM 9.3.2 does not support calculating compliance of an ECO or generating an audit report of an ECO in the out-of-box product. You could view the compliance of the parts in the ECO manually or this could be automated through a Process Extension.