Siebel Analytics Installation and Configuration Guide > Siebel Industry Applications Analytics Metadata > About Siebel Industry Applications Analytics Metadata >

Life Sciences

This section covers these topics:

Common Dimensions

These dimensions are used in all subject areas:

Positions Dimension

A sales territory is defined in Group Administration-Positions by a Siebel position. Creating parent positions creates the sales force hierarchy. Up to 10 levels of sales force hierarchy are supported by the application. Employees should be assigned to positions to populate employee hierarchy.

Position Types need to be set up according to compensation type (Rx or sales) only at the sales territory level. A district manager does not need to have a Position Type assigned to it. Sales Allocation needs to be exposed on the list applet to enter script compensation percentages (Rx or Sales) associated with each territory. For example, if all sales representatives receive 100% of the Rx on a ZIP Code, no action is needed or Position Type = Sales Representative can be assigned to the position.

Seed data on the Position Type list of values has been enhanced to include types for mirror, job share, and swat. Typically, both mirror and job share represent a position that receives less than 100% of the total scripts on a ZIP Code.

Alignments Dimension

A sales territory alignment is the relationship of ZIP Code-to-territory or brick-to-territory. The alignment relationship is created in Siebel Assignment Manager under Assignment Administration-Territories, as shown in Table 29.

Table 29.  Sales Territory Alignment
Contact ZIP to Territory
Contact ZIP Code
Use contact primary address ZIP Codes. Do not use ranges of ZIP Codes (that is, enter unique ZIP Codes as low and high values).
Do not enter duplicate ZIP Codes.
Account ZIP to Territory
Account ZIP Code
Do not use ranges of ZIP Codes (that is, enter unique ZIP Codes as low and high values).
Do not enter duplicate ZIP Codes.
Contact Brick to Territory
Contact Brick
Use contact primary address brick. Do not use ranges of bricks (that is, enter unique bricks as low and high values).
Do not enter duplicate ZIP Codes.
Account Brick to Territory
Account Brick
Do not use ranges of bricks (that is, enter unique bricks as low and high values).
Do not enter duplicate ZIP Codes.
Account to Territory
Do not enter duplicate accounts.
Contact to Territory
Do not enter duplicate contacts.

Products Dimension

The product hierarchy requires customer products (products of the company who licensed the software) to have predefined product types as shown in Table 30.

Table 30.  Customer Products Predefined Product Types
Product Level
Product Type
Aracid 400 MG
No Level
Sub Market

NOTE:  Competitive products should use the product type Competitor. Competitor product hierarchies are set up using parent product relationships exclusively and should not have product levels assigned to them.

Product Costs Dimension

Product costs for customer products (that is, products of the company that licensed the software) require population in the Product Administration, Product Form Applet, as shown in Table 31.

Table 31.  Product Costs For Customer Products
Product Type
Field to be Populated
Sample Cost
Avg. Promo Cost
Promotional Item Cost
Sample Cost

Pharma Subject Areas

This section discusses the subject areas used by ePharma Analytics.

Pharma Sales Effectiveness

This subject area is focused on syndicated data analytics.

The specific configuration required for the S_SYND_DATA table depends on your data types, and the Analytics application and reports that you have licensed. The Data Loading Matrix table in Siebel Data Warehouse Installation and Administration Guide guide is the basis of prebuilt reports. The syndicated data loading matrix populates both base and derived metrics used in pharmaceutical sales analytics.

Product Categories

Siebel Pharma Analytics supports custom and prebuilt product category trees to allow rollup of syndicated data by alternative hierarchies. To populate a custom category, first create a Catalog in Catalogue Administration, and create categories and sub categories as part of the catalogue. Table 32 lists the categories that need to have the Usage Type field populated in the Catalog Admin Category Detail Applet.

Table 32.  Hierarchy Categories to be Populated in Pharma Analytics
Usage Type Code
Hierarchy Category
Anatomical Therapeutic Class
Application Form
Product application
User-defined codes and custom hierarchies

Pharma Promotional Effectiveness

This subject area combines call activity data with syndicated data to analyze effectiveness of call activity.

Call Activity analysis records are derived from submitted call activity records stored in S_EVT_ACT in the Siebel transactional database, where they are stamped with the ZIP Code or brick where the activity took place—that is, the Contact primary address's ZIP code/brick or the Account ZIP Code/brick. Allocation of these ZIP Code/brick records should be done by Assignment Manager rules to make sure that they are correctly allocated. Assignment Manager rules must match the Contact or Account primary address ZIP Codes or bricks. Otherwise, data integrity is not maintained.

Only calls that have status Submitted on the Pharma Professional Call Form Applet are brought over from the Siebel transactional database to the Siebel Data Warehouse.

Pharma Medical Education Effectiveness

This subject area combines measures from MedEd and Syndicated Data to measure effectiveness of medical education events used on medical education analytics.

Only MedEd events with the status Completed on the Pharma ME Event List Applet are extracted from Siebel transactional database to populate the Siebel Data Warehouse.

MedEd Event costs are based on costs of activities in the Pharma ME Event Activity List Applet. Costs are allocated based on MedEd Team cost allocation, and promoted products Cost Allocation on the MedEd event.

Costs are solely based on physician invitees with the status Attended in the Pharma ME Event Professional Invitee Session List Applet.

Control groups are based on physicians who have the same contact ranking as attendee physicians within the same sales territory at the time of the event, but who did not attend the event.

Pharma Customer Demographics

This subject area supplies denormalized table for contact and account profiling. It is typically loaded from external sources and contains the master contact list. Prebuilt ETL extracts the contact list from Siebel.

Pharma Objectives Achievement

This subject is used to measure achievement and results for pharma call activity and Rx/sales targets. It is based on Pharma Objectives.

Objectives need to have a Unit populated in Retail Objective Form Applet. Actual target numbers per contact and account need to be populated in the Pharma Campaign Target Account List Applet or the Pharma Campaign Target Professional List Toggle Applet.

 Siebel Analytics Installation and Configuration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003