A Installing the Usage Accelerator Application

This appendix provides instructions for installing the optional Usage Accelerator application.

This appendix contains the following topics:

• Section A.1, "What is Usage Accelerator?"

• Section A.2, "About Installing the Usage Accelerator"

• Section A.3, "Usage Accelerator Application Integration with Siebel 7.5.3 CRM Application"

• Section A.4, "Usage Accelerator-Analytics Adapter Files"

A.1 What is Usage Accelerator?

Usage Accelerator was developed to enable sales organizations to measure and manage user adoption and effectiveness of Oracle's Siebel Sales. Every level of the sales organization benefits from the richer understanding of how each member of the team is contributing to the overall objective. Usage Accelerator provides a comprehensive set of management dashboards and pre-built metrics that deliver rich information to help accelerate organizational usage, drive alignment and increase the overall ROI of CRM implementations.

A.1.1 About Configuring Usage Accelerator

This section explains how Usage Accelerator is configured.

A.1.1.1 Tracking of Targeted Users

In order to optimize the storage space required for the application data the Usage Accelerator has been designed to let you choose which users you want to measure. The Usage Accelerator determines the users that you want to measure through the use of a new responsibility called "Usage Accelerator – Tracking". This new responsibility will need to be associated to each user in the operational Siebel application.

A.1.1.2 Other Required Responsibilities

The Usage Accelerator application introduces eight new responsibilities. Four of the responsibilities will be used by all organizations except for FINs customers. FIN's customers will use four responsibilities that are targeted specifically for their user groups. The responsibilities determine which dashboards a user will see when they use the Usage Accelerator application. These responsibilities need to be assigned to users in the operational application. The responsibilities are:

Table A-1 User Accelerator Responsibilities

Usage Accelerator Responsibilities	Usage Accelerator FIN's Responsibilities
Usage Accelerator – Sales Rep	Usage Accelerator - FINS Sales Rep
Usage Accelerator - Sales Manager	Usage Accelerator – FINS Sales Manager
Usage Accelerator - Sales Executive	Usage Accelerator – FINS Sales Executive
Usage Accelerator – Administrator	Usage Accelerator – FINS Administrator

Note: You must not remove a Responsibility for a User and later add the same Responsibility for that User in Siebel CRM Administration View "Responsibilities". If you do so, the related ETL will fail (for more information, see Section H.7, "ETL Issues".

A.1.2 About Deployment Date

Oracle's Usage Accelerator Application needs to be calibrated with the Deployment Date variable UA_DEPLOY_DT, which determines the time that you want the Analysis to commence. This date will default to the date on which you create the Usage Accelerator Data Warehouse, but can be modified by changing the UA_DEPLOY_DT variable.

Note: If you set the Deployment Date earlier than the current calendar date, then metrics that rely on the Last Updated Date (e.g # of Updated Records, # of Logins, # of Sync's, etc.) of a record might be inaccurate. For this reason Oracle recommends setting the Deployment Date to the current Calendar Date.

A.1.3 About Metric Definitions and Variables

Usage Accelerator tracks user adoption and effectiveness metrics across the following metric categories:

• User Adoption Metrics

• Opportunity Metrics

• Information Completeness Metrics

• Coverage Metrics

A.1.3.1 User Adoption Metrics

User Adoption Metrics provide visibility into the behavioral attributes and usage patterns of those using the system. These metrics enable you to quickly identify areas in need of improvement and individuals who require additional help to meet the company's CRM standards.

Table A-2 User Adoption Metrics

Metric Category	Description	Variables
Active User	Identifies users that have not logged in or synced in the last seven day time period.	Number of logins needed is currently set to 2. Variable Name is: ACTIVE_NUMLOGINS. Number of Syncs needed is currently set to 0. Variable Name is: ACTIVE_NUMSYNCS.
Login	Measures the number of days the user's login. Note – Only one login a day will be captured for each user.	Not Applicable
Sync	Measures the number of days the user's sync. Note – Only one sync a day will be captured for each user.	Not Applicable
Records Created	Tracks the number of Accounts, Contacts, Opportunities, Activities, Quotes created by each user and group. FINS version also tracks number of Financial Accounts and Policies Created.	Not Applicable
Records Updated	Tracks the number of Accounts, Contacts, Opportunities, Activities, Quotes updated by each user and group. FINS version also tracks number of Financial Accounts and Policies Created.	Not Applicable

A.1.3.2 Opportunity Updates Metrics

Opportunity Updates Metrics deliver reliable information to organizations that use Opportunity Management for tracking their pipeline and sales forecasts. The metrics provide a focus on opportunities by ensuring that current and accurate information is in place.

Table A-3 Opportunity Updates Metrics

Metric Category	Description	Variables
Opportunity Updates	Identifies Opportunities that have not been modified in the time period specified or have a close date that has passed. Opportunity Updates Needed is currently set to 90 Days.	Variable Name is: OPT_OUTDATED_NUMDAYS

A.1.3.3 Information Completeness Metrics

Information Completeness Metrics assist in the completion of contact and account information by highlighting what is missing in an individual entry or in a set of entries.

Table A-4 Information Completeness Metrics

Metric Category	Description	Variables
Account Completeness	Looks for the presence of information in each of the primary Account Address fields.	Address Line 1, City, State, Zipcode, Phone
Contact Completeness	Looks for the presence of information in each of the primary Contact Address fields.	Address Line 1, City, State, Zipcode, Work Phone, Email Address, Title

A.1.3.4 Coverage Metrics

Coverage Metrics monitor sales activity against Accounts, Contacts, Opportunities and Financial Accounts. It is not envisioned that you will need to use all of these metrics just the ones that are in alignment with your sales process.

Table A-5 Coverage Metrics

Metric Category	Description	Variables
Account Coverage	Determines whether an account has had a contact and activity associated to it in the timeframe specified. Activity Needed is currently set to 90 Days.	Variable name is: ACC_NEED_ACT_NUMDAYS. Contact Needed is currently set to 180 Days. Variable name is: ACC_NEED_CON_NUMDAYS.
Contact Coverage	Determines whether a Contact has had an activity associated in the time frame specified Activity Needed is currently set to 90 Days.	Variable Name is: CON_NEED_ACT_NUMDAYS.
Opportunity Coverage	Determines whether an Opportunity has had a contact and activity associated to it in the timeframe specified. Activity Needed is currently set to 90 Days.	Activity Needed is currently set to 90 Days. Variable name is: OPT_NEED_ACT_NUMDAYS. Contact Needed is currently set to 180 Days. Variable name is: OPT_NEED_CON_NUMDAYS.
Financial Account Coverage & Insurance Policy Coverage (FINS)	Determines whether a Financial Account or Insurance Policy has had an Activity Associated to it in the time frame specified	Activity Needed is currently set to 90 Days. Variable name is: AST_NEED_ACT_NUMDAYS.

A.2 About Installing the Usage Accelerator

If an execution plan in DAC metadata contains a Usage Accelerator Subject Area, it should include a preceding task "Create View For Usage Accelerator". All out of the box execution plans that contain Usage Accelerator subject area are configured with this preceding task. This step is required if you want to create a new execution plan or modify an existing execution plan to include "Usage Accelerator Subject area". This step is also required if you are using any customized subject area containing Usage accelerator warehouse tables for your execution plans. These tables are prefixed with "W_UA*".

Note: The following instructions in this appendix are required only if you are planning to use the Usage Accelerator analytics application integrated with Siebel CRM 7.5.3 applications. If you licensed the Usage Accelerator application versions 7.7 or 7.7.1, you should follow the installation instructions in Oracle Business Intelligence Platform Installation and Configuration Guide. No additional steps are required to install these versions of the Usage Accelerator application.

A.3 Usage Accelerator Application Integration with Siebel 7.5.3 CRM Application

Note: The following steps are required only if you are planning to use the Usage Accelerator in an integrated environment with a Siebel Business application version 7.5.3.

The Usage Accelerator installation process consists of installing the Usage Accelerator application and importing seed data into the transactional database. You install the Usage Accelerator application using the standard Oracle Business Intelligence installer. The installation options that are available to you depend on the license key you enter.

To integrate the Usage Accelerator application

1. Import repository objects to enable embedded Analytics.

   Use Siebel tools to imports "SRW_753_UA_Integration_objects.sif" file into tools repository.

2. Lock the following projects:

   • Analytics

   • ERM

   • Siebel Field Service

   • Siebel Marketing Enterprise

   • Siebel Channel

   • Siebel Sales Enterprise

   • Siebel Service Enterprise

   • Siebel Universal Agent

   
   

   Note: Do not apply the schema in the transactional database after importing these objects in tools repository. You might see some tables created in this step. These tables would have been applied in the transactional database.

   
   

3. Recompile the srf file, as follows:

   1. In Windows Explorer, navigate to \tools\objects\enu, and create a copy of siebel.srf under a different name.

   2. In Oracle's Siebel Tools, navigate to Tools, then Compile Projects, and select the Locked Projects radio button.

   3. Under the Siebel Repository, select the new SRF file you created in Step a, and click Compile.

   To see the Usage Accelerator screen in your application, the new SRF file must replace the siebel.srf file you were using.

4. Confirm the Analytics Server name to run Embedded Analytics.

   1. Log in to the Siebel application as the administrator.

   2. Navigate to Site Map, then Administration - Integration, then WI Symbolic URL List.

   3. In the Administration - Integration screen, from the visibility filter, select Host Administration.

   4. In the Host Administration list, locate the record Name=[AnalyticsServerName].

   5. Change [AnalyticsServerName] to the name of the machine hosting your Analytics Server.

5. Import language-independent Siebel seed data, as follows:

   1. Copy the appropriate seed data files:

      Table A-6 Seed data files

      File name	From	To
      seed_753_UA.dat	OracleBI\dwrep	Local machine
      seed_753_<xxx>_UA.inp where xxx corresponds to the database platform you are using	OracleBI\dwrep	Local machine

      
      

   2. Open a command line, and go to the same directory where you copied the .dat and .inp files.

   3. Replace each of the connection parameters with the values appropriate to your database environment, and then run the appropriate import command from the following table:

      Table A-7 Import commands

      Database Platform	Run Import Command
      Oracle	$SIEBELSERVERROOT\bin\dataimp /u $UserName /p Oracle $Password /c "$ODBCDataSource" /d $DatabaseOwner /f seed_753_UA.dat /w y /q 100 /h Log /x f /i seed_753_ora_UA.inp /lseed_753_ora_UA.log
      DB2UDB	$SIEBELSERVERROOT\bin\dataimp /u $UserName /p $Password /c "$ODBCDataSource" /d $DatabaseOwner /f seed_753_UA.dat /w y /q 100 /h Log /x f /i seed_753_db2_UA.inp /lseed_753_db2_UA.log
      MSSQL	$SIEBELSERVERROOT\bin\dataimp /u $UserName /p $Password /c "$ODBCDataSource" /d $DatabaseOwner /f seed_753_UA.dat /w y /q 100 /h Log /x f /i seed_753_mssql_UA.inp /lseed_753_mssql_UA.log

      
      

6. Associate the new Usage Accelerator responsibilities with the users whom you want to see the Usage Accelerator screen.

   The Usage Accelerator responsibilities are as follows:

   • Usage Accelerator Tracking

   • Usage Accelerator - Sales Rep

   • Usage Accelerator - Sales Manager

   • Usage Accelerator - Sales Executive

   • Usage Accelerator – Administrator

   
   

   Note: The first responsibility has to be associated with any transaction application user whom you want to be tracked in the Usage Accelerator reports.

   
   

A.4 Usage Accelerator-Analytics Adapter Files

The contents of each of the files included in the OracleBI\dwrep folder are shown in the table below.

Table A-8 Usage Accelerator Analytics Adapter Files

File	Description
seed_753_UA.dat	Siebel Seed Data file containing language- independent seed data records for the following tables: S_WI_SYMURL, S_WE_SYMURL_ARG, S_RESP, S_APP_VIEW, S_APP_VIEW_RESP.
seed_753_db2_UA.inp¦ seed_753_mssql_UA.inp¦ seed_753_ora_UA.inp	Import file used to control the import of the seed_753_UA.dat file to a particular database platform.