Siebel Applications Administration Guide > Upload of UPT and UPT-IRM Intersect Data >

Overview of UPT and IRM Data

The UPT data allows administrators to review details about when and how often users access the features in a Siebel CRM application. The process of performing UPT yields a set of .csv files.

NOTE:  The information in this chapter is applicable only when you run IRM after migrating from a prior Siebel CRM release in which UPT was enabled such as version 15.5 or later. For information about the specific releases (including applicable patchset releases) for which UPT can be enabled, see 2145521.1 (Article ID) on My Oracle Support. For more information about Usage Pattern Tracking, see Usage Pattern Tracking and for running IRM, see Siebel Database Upgrade Guide.

As a Siebel CRM database administrator, you also obtain a set of .csv files when you use IRM to apply Siebel Innovation Pack during database upgrade (see Siebel Database Upgrade Guide).

Execution of UPT is an optional but recommended process. IRM is a mandatory process for customers upgrading from a previous Siebel Innovation Pack to the current one. Both yield .csv files that you may upload to your Siebel CRM database for further analysis in the form of reports. The .csv files of UPT list the actual repository objects in use by end users. In the case of IRM, these files list the repository objects modified or newly added during the ongoing IRM process. The actual change to a repository object is termed direct change. This change may trigger an indirect change to other objects in its hierarchy. Both types of changes reflect in the IRM log (see Siebel Database Upgrade Guide) and the UPT-IRM Intersection report (see Analytical Reports for UPT and UPT with IRM Intersection).

NOTE:  The objects exported to the IRM .csv file are Business Objects, Business Components, Applets, Views, Web Pages, Schema and Workflows. The export is performed during the Upgrade Repository (upgrep) process once IRM is completed.

You can choose to perform only UPT to monitor and report usage data or IRM to upgrade to a Siebel Innovation Pack or both.

Benefits of Intersecting UPT-IRM Merge

It is useful to compare the UPT .csv with the IRM .csv files so as to focus testing only on objects that are in use by the customer as well as modified by IRM and not on all modified objects. If you choose to compare the two sets of .csv files, the intersection will yield a list of repository objects that are used and modified. These objects are the ones most used by end users and, therefore, require more testing.

NOTE:  To intersect UPT and IRM data, you need to migrate from Siebel CRM version 15.0 or 15.5 as UPT is enabled on the patchsets of these versions only.

When you intersect UPT data with IRM data, you obtain an accurate view of the actual product components used by a customer and the repository artifacts that IRM touches during the upgrade cycle. This targeted testing will help customers:

• Obtain data-backed targeted and specific investments so as to get predictable results.
• Reduce the cost of upgrades and cost of ownership through focused functional, integration, and performance testing post upgrade.

For example, UPT events may indicate that 10 applets across five views in two screens are the only objects used by a customer. IRM delta changes may be across 15 applets, 10 views, and 12 screens. The resultant intersection of UPT and IRM could be 6 applets, 3 views, and 1 screen. This would be generated as a report and be an output of the IRM Upgrade cycle. This will help the customer focus on testing the entities obtained solely from the intersection. The resultant saving will be on resources, time, and money.