Business Drivers to Requirements

First any Project starts with Business Drivers.

Once the Business Drivers have been identified , then Business Objectives , then Business Processes , then Business Process Steps and finally they are broken down into Requirements.

First we have High-Level Requirements which are further broken down into Detailed Requirements

Business Drivers ---------> Business Objectives -----------> Business Processes --------------------------------> Business Process Steps -----------> Requirements

Siebel Basic Access Control Mechanisms

We have 2 different ways of controlling Access in Siebel.

View Access :-

Responsibilities determine access to Views

Data

There are 2 types of Data.

1.Master Data and

2.Customer Data

Master Data :- Determined by Access Groups , Catalogs and Categories

Examples :- Accounts , Opportunities , Contacts and Campaigns

Customer Data :-

Personal Ownership

Determined by User Id

Examples :- Service Requests , Product Defects and Activities

Position

Determined by Position

Examples :- Accounts , Opportunities , Contacts & Campaigns

Organization

Determined by Organization

Examples :- Accounts , Opportunities , Contacts & Campaigns

Siebel 8 - Siebel Sync

Siebel 8 - ODBC Registration

Siebel 8 - Siebel Remote

Siebel 8 - Business Rules Developer

Siebel 8 - New Marketing

Siebel 8 - RTD

Siebel 8 - Search Administration

Siebel 8 - eMail Marketing

Siebel 8 - Marketing Segmentation

Siebel 8 - Marketing Campaigns

Siebel 8 - Workflow

Siebel CRM On Demand Web 2.0 Features Demo

Integrated Siebel CRM On Premise and CRM On Demand from Oracle

Siebel Mobile Client Installation

Siebel - Territory Management - Managing Territories

How to Extend Column of Siebel Table

Siebel 8 Task UI demo

OBIEE Delivers

OBIEE App Demo Clip

OBIEE Architecture

OBIEE Overview and Components

Siebel 8 Quick Hits: Task UI

Siebel 8 Business Analyst Certification Exam Details

Exam Number:1Z0-219

Exam Price: € 154


Siebel 8 Business Analyst Exam Syllabus

Introducing Siebel Applications
[ ] Describe Siebel Customer Relationship Management (CRM) applications
[ ] Give examples of employee and partner Siebel CRM applications

Using the Siebel Web Client
[ ] Start and log in to a Siebel application
[ ] Navigate screens and views in the application

Working with Data in the Siebel User Interface
[ ] Create, modify, and delete records
[ ] Query for records

Common Siebel Business Entities
[ ] Identify common business entities (Accounts, Contacts, Activities, Opportunities, and Quotes)
[ ] Describe relationships between these entities

Using Siebel Business Entities
[ ] Give an example of how a company could use Siebel business entities to support a business process

Exploring Siebel Sales
[ ] Describe how Siebel Sales users manage opportunities
[ ] Describe how forecasts can be used
[ ] Describe advanced Siebel Sales features

Exploring Siebel Call Center
[ ] Use Siebel Call Center to assign and handle service requests
[ ] Describe advanced Siebel Call Center features

Other Siebel CRM Features
[ ] Use iHelp for assistance with complex procedures
[ ] Describe the Universal Inbox functionality
[ ] Run a Siebel Report
[ ] Use Audit Trail to examine changes to a record
[ ] Describe how to use Siebel Search to locate information

Administering Siebel Applications
[ ] Describe how administrative users manage Siebel data and functionality
[ ] Identify commonly used administrative screens
Exploring the Siebel Architecture
[ ] Identify the major architectural components and their roles
[ ] Describe how different Siebel client types access data

Securing Siebel Applications
[ ] Describe the major entities that support security within a Siebel application
[ ] Describe the types of authentication supported by Siebel CRM Applications
[ ] Controlling Access to Views
[ ] Describe the relationships among views, users, and responsibilities
[ ] Outline two strategies for assigning views to responsibilities

Controlling Access to Customer Data
[ ] Describe the Siebel mechanisms that determine access to customer data records
[ ] Describe the relationship between views and access control mechanisms

Creating the Company Structure
[ ] Create position, division, and organization hierarchies
[ ] Create employees and users

Understanding Object Definitions
[ ] Describe the major types of object definitions
[ ] Describe the relationships between them
[ ] Use About View

Using Siebel Tools to Examine Object Definitions
[ ] Explain the differences between an object type and an object definition
[ ] Use Siebel Tools to examine parent and child object definitions
[ ] Determine relationships between object definitions

The Siebel Data Model
[ ] Describe the role of tables, columns, keys, indexes, and data types
[ ] Describe how cardinality between tables is represented
[ ] Describe 1:1 and 1:M extension tables

Siebel Business Components
[ ] Describe business components (BCs)
[ ] Describe properties of BCs and BC fields
[ ] Map UI controls and list columns to BC fields
Siebel Business Objects
[ ] Define a business object
[ ] Describe how links are used to relate business components within a business object

Picklists and Multi-Value Groups
[ ] Identify different types of picklists
[ ] Define a multi-value group (MVG)

Customizing UI Elements
[ ] Specify UI elements as part of a solution

Siebel Workflow
[ ] Describe the different steps of a workflow process
[ ] Describe the behavior of workflow processes
[ ] Examine existing workflow processes
[ ] Contrast methods used to invoke workflow processe

Siebel Assignment Manager
[ ] Describe Siebel Assignment Manager
[ ] Identify the parts of an assignment rule

Siebel Assignment Manager
[ ] Describe Siebel Assignment Manager
[ ] Identify the parts of an assignment rule

Siebel Task UI
[ ] Describe Siebel Task UI
[ ] Invoke and complete a task

Preparing for a Global Deployment
[ ] Define terms related to a global deployment
[ ] Describe Siebel internationalized features
[ ] Discuss requirements and best practices for a global deployment

Integrating Siebel Applications
[ ] Explain the business need for integration
[ ] Describe Siebel integration solutions at the data, business, and UI layer
[ ] Define service-based integration

Siebel 8 Core Consultant Certification Exam Details

Exam Number: 1Z0-202

Exam Price: Rs 9118

Duration: 120 Minutes

Number of Questions: 60

Passing Score: 64%

Siebel 8 Core Consultant Certification Exam Syllabus


Introducing Siebel Applications


Describe Siebel Customer Relationship Management (CRM) applications and how they are classified

[ ]

Identify the common business entities found in Siebel CRM applications

Using the Siebel Web Client


Start and log in to a Siebel application

[ ]

Navigate screens and views in the application

[ ]

Identify major user interface (UI) features in a Siebel CRM application

Working With Siebel Data


Create, modify, and delete records

[ ]

Query for records in a Siebel CRM application

Responsibilities and Views


Describe the purpose of a responsibility

[ ]

Create a new responsibility

[ ]

Modify an existing responsibility

Users, Positions, and Organizations


Describe how data access is controlled by users, positions, and organizations

[ ]

Implement the company structure using divisions, organizations, positions, users, and employees

Controlling Access to Customer Data


Describe the difference between customer and master data in Siebel applications

[ ]

Describe the different Access Control mechanisms used to restrict access to data in Siebel applications

[ ]

Identify the different view types used for different types of users

The Siebel Web Architecture


Identify the pieces that make up the Siebel Web architecture

[ ]

Identify the role of each piece of the architecture

[ ]

Describe how Siebel requests are processed

Server Components and Parameters


Define component groups

[ ]

Define components

[ ]

Describe parameters as inputs for components

[ ]

Describe the various levels at which you can set parameters and how to set them

[ ]

Describe named subsystems and job templates

Server Management


Monitor the state of the enterprise, and individual servers and components within that enterprise

[ ]

Perform routine administrative tasks on the enterprise, including: a. Managing components b. Backing up and restoring the enterprise c. Setting logging options d. Submitting jobs

Siebel Client Types


Identify the various Siebel clients

[ ]

Describe files associated with each client, including configuration files and local databases

[ ]

Describe how each client accesses Siebel servers and data

Securing Access to the Application


Describe the types of user authentication supported by Siebel applications

[ ]

Explain the role of the security adapter

[ ]

Describe Single Sign On (SSO) security and how it differs from other authentication methods

Installing Siebel Applications


Describe pre-installation steps necessary to prepare your environment for a Siebel installation

[ ]

Install the Siebel application

[ ]

Perform post-installation steps to verify your Siebel environment

[ ]

Describe how to use the multi-server update tool to automate installations

Siebel Application Architecture


Describe the major types of object definitions

[ ]

Describe the relationships between them

Using Siebel Tools to Examine Object Definitions


Describe the differences between object types and object definitions

[ ]

Use Siebel Tools to examine parent and child object definitions

The Siebel Data Model


Describe the purpose of the Siebel Data Model

[ ]

Describe the role of primary and foreign keys, indexes, and user keys

[ ]

Identify prominent tables in the Siebel Data Model

Siebel Business Components


Define a business component

[ ]

Describe how business component fields at the business object layer are mapped to columns at the data layer

[ ]

Describe how base and joined tables are used as a part of this mapping

Siebel Business Objects


Describe how business objects focus data presented in the UI based on context

[ ]

Describe how views reference business objects

[ ]

Describe how links are used to relate parent business components to child business components

Configuration Strategy


List the critical elements of the Siebel configuration strategy

The Configuration Process


Describe the development environment architecture

[ ]

Set up the development environment

Managing Object Definitions


Explain the role of projects

[ ]

Manage object definitions using Check Out and Check In

[ ]

Lock projects locally

Editing and Compiling Object Definitions


Create new and edit existing object definitions

[ ]

Validate edited object definitions

[ ]

Archive object definitions and projects

[ ]

Back up the local database

[ ]

Compile object definitions into a repository file

UI Layer Configuration: Web Templates


Describe the role of Siebel Web template files

[ ]

Describe the role of Siebel tags in template files

[ ]

List the types of templates

[ ]

Describe how to register, associate, and bind a template file

UI Layer Configuration: Applets


Create and modify a list applet

[ ]

Create and modify a form applet

UI Layer Configuration: Applications, Screens, and Views


Tailor applications

[ ]

Configure how a view is accessed on a screen

[ ]

Change the order of screen views for a screen

[ ]

Create and administer a view

[ ]

Associate a view with a template

UI Layer Configuration: Drilldowns


Configure drilldown to a related view

[ ]

Enable the thread bar

Business Layer Configuration: Joins


Create a join that brings data from a standard table into a standard business component

[ ]

Create a join that brings data from a party table into a standard business component

[ ]

Create a join that brings data from a party table into another party business component

Business Layer Configuration: Existing Business Components and Fields


Edit business component properties to capture business logic

[ ]

Describe business component view modes

[ ]

Edit field properties to capture business logic

[ ]

Specify business component and field user properties

Business Layer Configuration: New Business Components and Fields


Create a new business component (BC)

[ ]

Add a business component to a business object

Business Layer Configuration: Picklists


Describe the differences between dynamic and static picklists

[ ]

Administer a list of values

[ ]

Configure a static or dynamic picklists

Configuring Multi-Value Groups


Describe multi-value groups and their benefits

[ ]

Use Siebel Tools to configure a multi-value group

Data Layer Configuration


Create extension columns in a table

[ ]

Create custom tables: standalone table, 1:1 extension table, 1:M extension table, intersection table

Siebel Business Services


Describe a business service

[ ]

Describe the structure and role of property sets

[ ]

Use the business service simulator to test a business service

Building Siebel Workflow Processes


List the types of workflow processes and workflow steps

[ ]

Create a new workflow process and configure business service, Siebel operation, and decision steps

Testing and Deploying Workflow Processes


Test a Siebel workflow process using the simulator

[ ]

Deploy a Siebel workflow process

Executing Workflow Processes


Describe the workflow execution architecture

[ ]

List several ways to invoke workflow

[ ]

Invoke a workflow process using a run-time event

[ ]

Invoke a workflow process using a custom control

Using Workflow Policies


Create a workflow policy that invokes a workflow process in the Workflow Process Manager server component

[ ]

Enable the workflow policy using workflow server components

Siebel Task UI


Describe the role and benefits of Siebel Task UI

[ ]

Invoke and complete a task

Task UI: Creating a Task


Identify the major components of a task

[ ]

Configure a task

[ ]

Administer a task

Transient Business Components and Branching


Describe the role of transient business components and task applets

[ ]

Configure branching logic in a task

Introducing Siebel Assignment Manager


Explain the role of Siebel Assignment Manager

[ ]

List the elements used to create rules that assign business data

Creating Assignment Rules


Create an assignment rule that assigns sales data to a sales team

[ ]

Create an assignment rule that assigns service data to a skilled employee

[ ]

Test assignment rules

Tailoring Assignment Manager Behavior


Describe the steps in the assignment methodology

[ ]

Prioritize rules using exclusive rules and rule group sequencing

[ ]

Modify the behavior of an assignment object

Invoking Siebel Assignment Manager


List the modes in which Assignment Manager can be invoked

[ ]

Invoke Assignment Manager in dynamic mode

State Models


Describe how state models can enforce business logic

[ ]

Create a new state model

Introducing Enterprise Integration Manager


Describe the features of Enterprise Integration Manager (EIM)

Introducing Application Deployment Manager


Describe the Application Deployment Manager (ADM) architecture

[ ]

Describe how deployment options are configured

Deploying Application Customizations


Use the packager utility to bundle application customizations

[ ]

Deploy a package using the ADM command-line interface

Siebel Party Business Components


Define a party business component

[ ]

Describe the role of S_PARTY and its extension tables in storing party business component data

[ ]

Describe how data is stored differently for non-party business components and party business components

[ ]

Describe how implicit and explicit joins are used with party business components

Siebel SOA & Fusion Blackbook

Oracle Siebel BPEL Guide

Siebel Field Service Basics

Basics of Field Service


 RMA: RMA (Return Material Authorization)


 Cycle Counting


 Replenishment


 Fulfillment


 Asset Management


 Dispatch Board


 Agreements

RMA (Return Material Authorization)


 The RMA (either RMA Repair Return or RMA Advance Exchange) signifies that the product is to be repaired.



 Repairs begin when a customer calls a service center about a defective product.



 The customer service representative assigns an RMA (Return Material Authorization) to the product, and requests that the customer ship the product to the service center.



Cycle Counting


 A method of counting inventory by grouping products into classes.

 Counts the products in each class at designated intervals over a period of time.

 Only part of the products are counted at one time, but over the designated time period all products are counted.

 Since assets are moving in and out of inventory, cycle counting creates a dynamic, statistical view of inventory.

An Example: Products of class X, for instance, might be counted once every three months, products of class Y once every six months, and products of class Z once a year.


Methods of Product Classification for Cycle Counting



 The ABC cycle count basis ranks products according to their financial value. The Cycle Counting Engine counts the items with a larger dollar value more often than those with a lower value.



 The XYZ cycle count basis ranks products according to their turnover. Higher-turnover products are counted more often, resulting in a higher accuracy of counting.



Replenishment


 The process of generating orders to restock depleted parts in an inventory location.

 Replenishment Engine generates internal orders to other inventory locations or purchase orders to outside vendors using the following information about a product in inventory:


■ Minimum and maximum stock levels, plus a safety level.


■ Replenishment relationships with other inventories.


Sources of Replenishment



Another service inventory location. The Replenishment Engine generates an internal order. For example, the main service warehouse replenishes a subsidiary warehouse.



External provider. The product is purchased from an external vendor. In this case, the Replenishment Engine generates a purchase order.



Manufacturing inventory. The product is provided by an internal manufacturing division. Such replenishments are usually handled as if from an external provider; a purchase order is generated.



Fulfillment


Siebel Field Service provides two methods for filling an order automatically:

 The Fulfillment Engine automatically locates in inventory the ordered items (or substitutes for these items), allocates these items, and generates a pick ticket.


 The Part Locator is a semi-automated version of the Fulfillment Engine. It gives the user control over fulfillment of individual line items in an order. The user can select the line items and choose to carry out these automatic procedures for the selected items:


 Find products or substitutes in inventory.


 Allocate these items.


 Generate pick tickets.



Fulfillment Engine


The Fulfillment Engine automatically finds and allocates products for selected service orders, and produces pick tickets to use for the orders. The engine uses the following information to find a product:

 Distances of source inventory locations to the order address.

 Priority of an order, which can influence fulfillment relationships.



Dispatch Board


 Is a graphical user interface that allows call center personnel and dispatchers to select, schedule, and assign field service engineers to service activities.



 The Dispatch Board screen shows all unplanned activities and a list of the selected field service engineers and their schedules.



 Dragging unplanned activities onto the schedules of field service engineers automatically assigns and schedules these activities.



 Lets a dispatcher or customer service representative manually assign and schedule individual activities by dragging and dropping an activity onto a Gantt chart.



Agreements


 Describes a product or service provided to the customer and the financial relationship between parties.



 Different types of agreements can be created manually in the Agreements screen or
automatically from a quote in the Quotes screen.



 Agreements can have a hierarchical relationship; that is, a master agreement can have multiple child agreements.

Siebel Field Service Automation Engines

Siebel Field Service provides the following automated functions:



 Fulfillment Engine. Analyzes orders, locates parts for each line item, returns the located parts (products or substitute products) to the user, allocates parts, and generates pick tickets.



 Renewal Engine. Automatically renews agreement line items.



 Charge Engine. Automatically creates charges. These charges can then be consolidated using the Charge Consolidation Engine.



 Charge Consolidation Engine. Automatically generates invoices, based on defined charge consolidation plans.



 Part Locator Engine. Analyzes orders, locates parts for each line item, and returns the located parts (products or substitute products) to the user. The user can manually allocate these parts and generate the pick tickets.


 Replenishment Engine. Selects source and target inventories when restocking is needed and generates the orders required to obtain materials from an external provider, an internal inventory site, or an internal manufacturing facility.



 Cycle Counting Engine. Generates cycle counting orders (parts lists).



 Preventive Maintenance Engine. Generates service requests for the maintenance of assets, based on predefined triggers.



 Mobile Inventory Transaction Engine. Generates inventory and asset transactions when a field service engineer reports part movements in the field.

Siebel Functional Guide

Siebel Interviews Q & A

Siebel Tips & Tricks

Siebel Upgrade Guide

Siebel Loyalty Management Guide

Siebel Server Administration 8 Blackbook

Siebel Scripting 8 Blackbook

Siebel Customer Order Management ( COM ) Blackbook

Siebel Server Administration Guide

Siebel Best Practice Manual

Siebel Smartscripts Blackbook

Advanced Siebel Guide

Siebel Workflows

Siebel EAI Blackbook

Siebel EAI Blackbook

Siebel EAI Blackbook

Workflow Utilities Business Service

Workflow Utilities Business Service is a predefined business service in Siebel Workflow. This business service has one available method, Return Property Values. This method returns a mirror image of the input arguments. The Return Property Values Method is also referred to as the Echo Method.

Return Property Values method arguments:

I/P arguments - This method accepts any input arguments.
O/P arguments - This  method returns an exact copy of the input arguments.

This can be used to evaluate expressions dynamically.

What are the different Workflow modes ? What are they ?

There are 4 types of Workflow Modes:-

They are:-

Service Flow

Interactive Flow

Long running Flow

7.0 Flow

Service Flow

Is the default mode for a new workflow.An important point to note here is that cannot include wait or Use Interact Step

Interactive Flow

Is used to Navigate users through a set of View

Long Running Flow

Is a workflow that can run for hours , days or months.Cannot include a wait step.Can be Paused and resumed as an inbox item

7.0 Flows

Should not be used for new workflows.Provided for backward compatability  of workflows defined prior to Siebel 7.5 Release

Siebel Quiz Series - Part 2

Which components make up the Business Objects Layer ?

Choose Three.

A.Business Components

B.Tables

C.Fields

D.Controls

E.Business Objects

Ans:- A,C,E

What features are available to  you on screen home page in Siebel 7.7 ?

Choose three ?

A.Record details

B.Search Capabilities

C.User preference settings

D.Task-related iHelp Topics

E.Add New Records

Ans: B,D,E

What are the Valid methods for returning to a recent screen in Siebel 7.7 ?

Choose two ?

A.Use the Internet Browser History list

B.Use the Internet Browser Back button to the previous screen

C.Use the Siebel History Button to return to a recent screen

D.Use the Siebel Back button to return to the previous screen

Ans: A,B

Which is an Installed solution designed for companies with fewer than 100 users ?

A.Siebel Analytics

B.Siebel CRM Enterprise

C.Siebel CRM Professional Edition

D.Siebel CRM onDemand

Ans:-C

Which Siebel Business Entity represents businesses external to your company that could be current or potential client , business partner or competitor ?

A.Opportunity

B.Contact

C.Position

D.Account

Ans:- D

Which Siebel Business entity represents a potential revenue-generating opportunity ?

A.Account

B.Quote

C.Activity

D.Opportunity

Ans:- D

Which is a collection of  data organized to reflect the users business ?

A.Business Object

B.Table

C.Business Component

D.Picklist

Ans:- C

Which component of the Siebel Architecture contains Virtual Directories and the eapps.cfg file ?

Ans:-

A.Siebel Web Client

B.Siebel Servers

C.Siebel Gateway  Name Server

D.Third-Party Web Server

Ans:-D

Which client accesses the Siebel Application  Object Manager through the Web server running the SWSE ?

A.Web Client

B.Mobile Web Client

C.Dedicated Web Client

D.Handheld Client

Ans:-A

What are the Characteristics of  Customer Data ? Choose Two.

A.Relatively stable referntial data

B.Typically Managed by Administrators

C.Typically created and managed by users

D.Relatively dynamic transactional data

Ans:-C,D

What are the Examples of  Customer Data ? Choose three ?

A.Products

B.Activities

C.FAQs

D.Service Requests

E.Quotes

Ans:-B,D,E

What type of data is displayed in the My contacts View ?

A.Records assigned to a region

B.Records assigned to a user or position

C.Records assigned to an Organization

D.Records assigned to an enterprise

Ans:-B

As a Business Analyst , you may need to Create responsibilities to allow users to access data within the Siebel Application. What are the Advantages of creating a single responsibility for each job function based on required screens ? Choose two.

A. Users may have access to views that they do not need

B.More duplication of view mappings across responsibilities

C.Managers & Executives are assigned to more responsibilities

D.Less Administration required over time as Views are changed

Ans:-A,B

A Business Analyst may need to define the tasks users can perform based on their job responsibilities.How would you allow sales representatives to create quotes but not view service Requests ?

A.Do not assign the sales representative position to the Service Request Views

B.Do not assign sales representatives to the service organization

C.Do not assign Service Request Views to the Sales Representative responsibility

D.Do not assign Service Request Views to the Sales representative Position

Ans:-C

Which can be directly assigned to an access group ?

A.User Lists

B.Enterprises

C.Organizations

D.Individual Users

Ans:-A,C

Which can be directly assigned to an access group ?

A.Responsibilities

B.Individual Users

C.Organizations

D.Positions

Ans:-C,D

Which statement is true of Customer Data ?

A.Is created and managed by only company administrators

B.Has access controlled at record level

C.Includes static , referential data

D.Can be grouped into catalogs & categories

Ans:-B

Which authentication method allows for self-registration by web users ?

A.Web single sign on

B.Database Authentication

C.Directory server authentication

D.Windows authentication

Ans:-C

Your customer needs to go the Accouint  View when they click a contact name from the Contact View.What type of navigation is this ?

A.Static Drilldown

B.Dynamic Drilldown

C.Thread Bar

D.Applet Toggle

Ans:-A

Which questions might you ask in regard to global time zone support.Choose two.

A.Do you provide support around the world ?

B.In which currencies do you do business ?

C.How many employees are in the support organization ?

D.Which locations provide customer service & sales support ?

Ans:-A,D

Your customer uses a 13-point Verdana font on all of their web pages ? They want their Siebel Application to adhere to this standard.What must be edited to ensure that the default font will comply with this standard ?

A.HTML  tags on each web page

B.Cascading Style Sheets ( CSS )

C.Siebel Configuration file ( .cfg )

D.Siebel Web templates

Ans:-B

Your customer wants their application to use the same visual layout as their existing corporate home page.Which need to be modified to define the layout of the user interface elements ?

A.Siebel Configuration (.cfg ) file

B.Applets using Siebel Applet Designer

C.Cascading Style Sheets

D.Siebel Web Templates

Ans:-D

Which fields are implicitly joined between a base table and its 1:1 extension table ?

A.PAR_ROW_ID on the base table and ROW_ID on the extension table

B.PAR_ROW_ID on the base table and PAR_ROW_ID on the extension table

C.ROW_ID on the base table and ROW_ID on the extension table

D.ROW_ID on the base table and PAR_ROW_ID on the extension table

Ans:-D

What is the purpose of the ROW_ID Column  in Siebel Tables ?

A.Identifies  the data and time that each record was created

B.Uniquely identifies each row in the table

C.Tracks changes to each record

D.Used by EIM tables to enforce referential integrity

Ans:-B

Enterprise Selling Process ( ESP ) - Siebel Sales Methodology

Enterprise Selling Process ( ESP ) is one of the Sales Methodologies Provided by Siebel.The Other Sales Methodologies are Target Account Selling ( TAS ) and Portfolio Management Process ( PMP ).

Enterprise Selling Process (ESP) is a structured methodology that enables virtual account teams to deploy their account resources to better penetrate and cover all opportunities..
ESP analyses the customer's key business drivers to identify selling opportunities throughout each business unit and provides a formal process for defining value from the customer's perspective.


Members of the account team learn how to look at the account as a marketplace and determine the full revenue potential.

To ensure comprehensive coverage of the account, sales teams are taught techniques for effectively utilizing resources and working together cohesively to grow the client relationship.

Enterprise Selling Process is designed for virtual account team members who are focused on a particular enterprise account, including sales managers, account managers, field sales personnel, marketing and support staff.

Enterprise Selling Process (ESP)- enables sales teams to penetrate, cover and grow large strategic accounts.

When do Customers need to go in for Siebel on Premise Solution ?

Complex Order Management

High Volume Call Center

Deep Industry CRM Required

• Trade Promotion Management ( TPM ) for consumer goods

• Case Management for Public Sector

• Account Activation for Financial services

• Order to Activation in Communications

Cultural Propensity for on Premise Eg :- Automotive

Social CRM Applications Provided by Oracle

Oracle currently Provides 3 Social CRM Applications:-

Oracle Sales Prospector

Oracle Sales Campaigns

Oracle Sales Library

Oracle Sales Prospector: Offers Insight  on what to sell next based on analysis of buying patterns of customers with similiar attributes

Oracle Sales Campaigns: Empower Sales Representatives to create sophisticated html campaigns in email and track the results of their campaigns

Oracle Sales Library :- Provides a shared library to facilitate finding and sharing of sales content

Siebel 8.1 Sales New Features

The following are the New Features of Siebel 8.1 Sales:-

XML Publisher Integration

Embedded Sales Analytics

Customer Adaptive Forecasting

Enhanced Global Account Hierarchy

Web services

Lead Pooling

Deal Registration

Special Pricing

Oracle XML Publisher

Siebel Sales 8 New Features

The following are the New Features of Siebel Sales 8 :-

PMP Embedded Sales Methodology

MS Office Integration : Word & Excel

Advanced Forecasting

Territory Management

Global Account Management

Siebel 7.8 Sales New Features

The following are the New features of Siebel 7.8 Sales:-

Cross-sell and Real-time Product Promotions

MS-Outlook Integration - Contacts , Calendar & Tasks

Collaboration Via MS Sharepoint

iHelp

Usability enhancements such as Quick Fill Template , Navigation History and Quick Print