14Predefined Routing Models
Predefined Routing Models
This chapter describes predefined routing models. It includes the following topics:
For more information, see Deploying a Predefined Routing Model.
Predefined Routing Models for Siebel Remote
The following table describes the routing models that come predefined with Siebel Remote. If your implementation uses a routing model, then Siebel Remote does a database extract and routes subsequent transactions to the user that are relevant to the job role that the name of the routing model describes, such as salesperson. To examine the views that some routing models reference, see Using Responsibilities to Route Data.
Table Routing Models that Come Predefined with Siebel Remote
Routing Model | Description |
---|---|
Analyst |
The Analyst routing model routes the following data:
The analyst also receives activities but only those activities that are related to quotes, opportunities, or service requests. Siebel Remote also routes Project Items, such as the following:
|
Consultant |
The Consultant routing model allows a limited use license for the professional services functionality. It routes data only for the following items:
|
Executive Management |
The Executive Management routing model is an extract-only routing model for an executive manager. It allows this manager to use the remote client to do everyday tasks. It excludes all manager rules so that Siebel Remote routes to remote clients only that data that is visible. |
Field Engineer |
The Field Engineer routing model routes data that the user requires to do and debrief a complex job that requires an acceptable level of historical data regarding customer and asset history. The Field Engineer can use this data to do the following work:
Debriefing is the reporting of material usage, time, and expenses to service managers after the user completes an activity. |
Field Sales Manager |
The Field Sales Manager routing model routes data that is typical for the Sales Representative Standard, but it also includes team data for accounts, contacts, and opportunities. |
Field Sales Representative |
The Field Sales Representative routing model routes data that is relevant to a salesperson. |
Field Technician |
The Field Technician routing model routes data that is relevant to a field technician. |
Life Science User |
The Life Science User routing model is similar to the Mobile Client - Standard routing model except that it routes more data to remote clients and contains some extra rules that the Siebel Life Sciences applications require. These extra rules are for the following dock objects:
|
Minimal Data |
The Minimal Data routing model routes data only for the following items:
|
Mobile Client - Extract Only |
The difference between the Mobile Client - Extract Only routing model and the Mobile Client - Standard routing model is that the Mobile Client - Extract Only routing model does not enable synchronization. A local database that uses the Mobile Client - Extract Only routing model reflects a snapshot of application data with respect to the user. |
Mobile Client - Standard |
Unlike other routing models, the Mobile Client - Standard routing model routes the full set of data that is related to the user, according to the configuration of the visibility rules in the Siebel runtime repository. There are some exceptions. For more information, see About the Standard Routing Model. |
Mobile Partner User |
The Mobile Partner User routing model routes data that is relevant to the Partner Sales position and the Service Representative position who use a mobile version of the Siebel PRM Partner Portal application. This model includes the following items:
|
Selective Retrieval |
The Selective Retrieval routing model routes data that allows the user to use individual records that Siebel Remote synchronizes to the remote client. Siebel CRM releases support the selective retrieval functionality for the following objects:
For more information, see Selective Retrieval Routing Model. |
Senior Field Engineer |
The Senior Field Engineer routing model routes data that supports the following:
|
About the Standard Routing Model
A user whom you assign to the Mobile Client - Standard routing model receives the full data set. The following items typically determine the data that this user can view:
Position
Ownership
Organizational structure
Visibility of items in the following views:
My View
My Team View
For example, My Team’s Opportunities.
Siebel Remote also routes data that is visible at the enterprise level that typically includes metadata or the setup data that the Siebel application requires. For more information, see How Positions, Organizations, and Responsibilities Affect Access.
Dock Objects That the Mobile Client-Standard Routing Model Does Not Include
The following table describes the dock objects that the Mobile Client-Standard routing model does not include.
Table Dock Objects That the Mobile Client-Standard Routing Model Does Not Include
Dock Object | Description |
---|---|
Activities |
This routing model does not route the following activities:
|
Assets |
Assets that visible invoiceable charges reference. |
Audit Log |
Audit trail data that is associated with all objects. |
Barcode |
Barcode configuration information. |
Call Script Question |
Data that is associated with SmartScript functionality. |
CHAMP |
Data that the CHAMP methodology requires. |
Comm (Marketing Campaign) |
Data that is associated with Marketing Campaign functionality. |
Content Set |
Data that is associated with Content Base functionality. |
Content Type |
Data that is associated with configuration of Content Base functionality. |
CTI Cfg |
CTI configuration data that CTI functionality requires. |
DD Filter |
Data that is associated with filters that Marketing Campaign functionality requires. |
DD Hierarchical Attribute |
Data that is associated with Hierarchy (family function) that Marketing Campaign functionality requires. |
DD List Format |
Data that is associated with Lists that Marketing Campaign functionality requires. |
DD Measure |
Data that is associated with Measures that Marketing Campaign functionality requires. |
DD Measure-based Attribute |
Data that is associated with Measure Based Attributes that Marketing Campaign functionality requires. |
DD Sort Family |
Data that is associated with Parent for Sort Family that Marketing Campaign functionality requires. |
DD Source Code Format |
Data that is associated with Source Code Format that Marketing Campaign functionality requires. |
DocAgreement |
DocAgreement that a visible invoiceable charge references. |
Docking Object |
Data that is associated with the data definition of the Siebel Remote Docking Object. |
DockRoute |
Data that is associated with the Siebel Remote Routing Model. |
DocQuote |
DocQuote that visible Revenue references. |
EAI Lookup Map |
Data that EAI components use to map external application values to Siebel values and to map Siebel values to external application values. |
Employee Skill |
Employee skills data. |
Expense |
Expense reports that a visible invoiceable charge references. |
Group News |
Data that is associated with Content Path. |
Integration Object Map |
Data that is associated with EAI Integration Object mapping. |
Invoicable Charge |
Visible Charges and credits data that can be invoiced to customers or that the employee creates. |
List of Value |
List of value data that the remote client does not require. |
MS Project Integration |
Seed data that maps Microsoft Project fields to Siebel Project fields. |
Note |
A note that is associated with quote, literature, or other objects that do not contain a note table. |
Order |
Visible order data that can be invoiced to customers. |
Org Source |
Accounts to be targeted for a promotion. |
Outlook Integration |
Seed data that Siebel CRM uses to define business components, business objects, views, and applets that display items in Microsoft Outlook. |
Party |
Party data that a visible invoiceable charge references. Contact records that the CTI configuration teleset references. Party data that a visible quote references. User roles that are associated with the user. |
Postal Code |
ZIP code data. |
Product |
Product data that a visible invoiceable charge references. |
Project |
Project data that a visible invoiceable charge references. |
Project Item |
Project item data that a visible invoiceable charge references. |
PrspCon |
Prospect. |
Repair Part |
Repair part data a visible invoiceable charge references. |
Server Domain |
Server domain information that a PIM (Siebel Server Sync) synchronization that is server based uses. |
Server Domain List of Value |
List of values for PIM language independent code that a PIM synchronization that is server based uses. |
Server Domain Profile |
Server domain configuration that a PIM synchronization that is server based uses. |
Server Domain Translation Map |
Server domain translation map that a PIM synchronization that is server based uses. |
Service Request |
Service request that a visible and invoiceable charge references. |
SMQ Administration |
Message business object information for MQ. |
SMQ History |
History information for MQ. |
Task-Based Process |
Task definition data that an administrator indicates through the administrative screens for regional node only. |
Terr Accnt (Territory Account) |
Territory account data that is the Territory Alignment process uses on the Siebel Server. |
Terr Algn (Territory Alignment) |
Territory alignment data that the Territory Alignment process uses on the Siebel Server. |
Terr Asset (Territory Asset) |
Territory asset data that the Territory Alignment process uses on the Siebel Server. |
Terr Con (Territory Contact) |
Territory contact data that the Territory Alignment process uses on the Siebel Server. |
Terr Hier (Territory Hierarchy) |
Territory hierarchy data that the Territory Alignment process uses on the Siebel Server. |
Terr Region (Territory Region) |
Territory region (brick) data that the Territory Alignment process uses on the Siebel Server. |
Terr ZIP (Territory ZIP) |
Territory ZIP code data that the Territory Alignment process uses on the Siebel Server. |
Time Sheet Item |
Time sheet item that a visible invoiceable charge references. |
Universal Inbox Item |
Universal inbox item data that the system administrator does not mark for replicating to the remote client. |
Universal Inbox Item Typ |
Universal inbox item type data that the system administrator does not mark for replicating to the remote client. |
Workflow |
Workflow process or step that the system administrator does not mark for replicating to the remote client. |
Workflow Definition |
Workflow deployment definition that the system administrator does not mark for replicating to the remote client. |
Predefined Routing Models for Siebel Financial Services
The following table lists the predefined routing models for Siebel Financial Services that come predefined with Siebel Remote.
Table Predefined Routing Models for Siebel Financial Services
Routing Model | Responsibility | Type |
---|---|---|
Institutional Finance Sales Manager |
Institutional Finance Sales Manager |
Specialized |
Institutional Finance Analyst |
Institutional Finance Analyst |
Specialized |
Credit Originator |
Credit Originator |
Specialized |
Insurance Sales Agent |
Insurance Sales Agent |
Specialized |
Insurance Sales Manager |
Insurance Sales Manager |
Specialized |
To reduce the amount of data that Siebel Remote synchronizes to the user, you can use each of these routing models with the responsibility that the table lists. It is strongly recommended that you get help before you deploy Siebel Remote with any of these specialized routing models. For help with routing models, see Getting Help from Oracle.
For more information, see Controlling the Data That Siebel Remote Routes to Clients.
Institutional Finance Sales Manager Routing Model
You can configure Siebel Remote to use the Institutional Finance Sales Manager routing model to send database extracts and transactions that include information that is relevant to a user who manages institutional finance sales. This user can view all records for the manager and all the records for users who report directly to this manager. A manager with no direct reports does not receive team data.
Siebel Remote handles literature routing. It synchronizes links to the literature with the remote client but it synchronizes the literature attachments only on request.
Institutional Finance Analyst Routing Model
To send database extracts and transactions that include information that is relevant to an institutional finance analyst, you can use the Institutional Finance Analyst routing model.
Credit Originator Routing Model
You can use the Credit Originator routing model for individuals in your organization who are responsible for originating mortgages or other consumer loans and for managers of these individuals. If you assign this routing model to a user, then Siebel Remote sends to this user the database extracts and transactions that include information that is relevant to loan origination. A manager can view all records for the manager and for the people who report to this manager. A manager with no direct reports does not receive team data.
Insurance Sales Manager Routing Model
You can use the Insurance Sales Manager routing model for insurance sales managers in your organization. If you assign this routing model to a user, then Siebel Remote sends to this user the database extracts and transactions that include information that is relevant to a person who manages insurance sales agents. Siebel Remote routes to the insurance sales manager the same records that it routes to the people who report to this manager. This routing model includes the business components that a Siebel application uses for the Insurance Sales Agent position in addition to the team data for the manager.
Insurance Sales Agent Routing Model
You can use the Insurance Sales Agent routing model for insurance field sales agents in your organization. You can also use this routing model can for other users, such as health insurance sales agents and site coordinators. If you assign this routing model to a user, then Siebel Remote sends to this user a database extract and transactions that include information that is relevant to the user position.
Claims Manager Routing Model
You can use the Claims Manager routing model for insurance claims managers in your organization. If you assign this routing model to a user, then Siebel Remote sends to this user the database extracts and transactions that include information that is relevant to a person who manages claims adjusters. Siebel Remote routes to the claims manager the same records that it routes to the people who report to this manager. This routing model includes the business components that a Siebel application uses for the Claims Adjuster position in addition to the team data for the manager.
Claims Adjuster Routing Model
You can use the Claims Adjuster routing model for insurance field claims adjusters in your organization. The following business components are associated with this routing model:
Households
Contacts
Policies
Service Providers
Claims
Claim Elements
Service Requests
Activities
Calendar Access
Business Components That Are Associated with Predefined Routing Models for Financial Services
The following table lists the business components that are associated with each of the predefined routing models. The letter Y indicates that the business component is associated with the routing model.
Table Business Components That Are Associated with Predefined Routing Models for Financial Services
Business Component | Finance Manager | Finance Analyst | Credit Originator | Insurance Manager or Agent |
---|---|---|---|---|
Activities |
Yes |
Yes |
Yes |
Yes |
Applications |
Yes |
No |
Yes |
Yes |
Calendar Access |
Yes |
Yes |
No |
Yes |
Call Reports |
Yes |
Yes |
No |
No |
Claims |
No |
No |
No |
Yes |
Companies |
Yes |
Yes |
No |
Yes |
Contacts |
Yes |
Yes |
Yes |
Yes |
Employees |
Yes |
Yes |
No |
No |
Events |
Yes |
Yes |
Yes |
Yes |
Expense Reports |
Yes |
Yes |
No |
No |
Facilities |
No |
No |
No |
Yes |
Financial Accounts |
Yes |
No |
No |
No |
Holdings and Interests |
Yes |
Yes |
No |
No |
Households |
Yes |
No |
No |
Yes |
Literature |
Yes |
Yes |
No |
No |
Opportunities |
Yes |
No |
Yes |
Yes |
Policies |
No |
No |
No |
Yes |
Products |
Yes |
Yes |
Yes |
No |
Providers |
No |
No |
No |
Yes |
Securities |
Yes |
Yes |
No |
No |
Service Requests |
Yes |
Yes |
No |
Yes |
Differences in the Literature List When Connected to the Local Database
The following fields display in the Literature list of the remote client when this client is connected to a local database. They do not display when connected to the Siebel Server:
Local. Specifies to make the document available on the local file system. If a document is not available locally, then the user can request it by placing a check mark in the Request File check box.
Request File. If this check box contains a check mark, then Siebel Remote downloads the literature during each synchronization.