What is CRM

************

Different CRM vendors

************

Reporting for Data mining- what is data mining? How was it implemented?

************

The current Siebel application provides a customer information system, a

product information

system, a competitive information system, and a decision support system with a

large database.

Siebel Workflow

Siebel Workflow, the focus of this guide, is a customizable business application

that

allows you to define, manage, and enforce your business processes. It allows you
to

design complex workflow processes and automate the enforcement of business

policies and procedures.

-Workflow Processes. Allows you to define your company’s business processes

using a familiar flowcharting interface. A workflow process consists of one or

more process steps such as start steps, sub-processes, decision points, and
tasks.

-Workflow policies. Allows you to define policies that can act as triggers to
execute

a process. A policy consists of conditions and actions. When policy conditions

are met, the policy action executes the relevant process.

Siebel Workflow works with all Siebel eBusiness Applications and involves the

following architectural components:

Siebel Tools. Siebel Tools is a software application that allows you to

reconfigure

and extend the functionality of Siebel Workflow.

 Siebel Client. Workflow Processes, Workflow Policies, and State Model are

administered through Siebel Workflow Designer views in the Siebel Client.

Siebel Server. Siebel Server manages the Siebel Workflow components that

automate business policies.

Siebel Database. A relational database containing the set of data that

Workflow

Policies act against.

Workflow Policies Log

The view contains the following fields:

_ Policy. The name of the policy.
_ Workflow Object. The name of the workflow policy object.
_ Object Identifier. The ID of the workflow policy object for which the policy
condition was met.
_ Object Values. Identifying information for the row that met the policy condition.
_ Event Date/Time. The date and time of the policy condition was met.
Once you have verified that the workflow policies work as expected, you can
migrate the workflow policies to your production environment.

Why testing necessary in Siebel projects:

8 Insufficient or inappropriate testing

It is not necessary to spend an excessive
amount of time checking the standard features
of the packaged Siebel application,
which can usually be assumed to work correctly.
Pre-deployment testing must instead
focus on the specific configuration that has
been carried out to meet the organisation’s
particular requirements. Ensuring that the
application supports the business processes
as intended, and that processes run correctly
across multiple applications, is also vital.
The trick is to use the limited time period
available for testing in the most effective
way possible,
concentrating on the
areas of highest risk
and/or those with
the most impact if
there is a problem.
This usually means
focusing on the
following:
• Do the processes,
as defined in the
workshops, work as anticipated?
If a good job has been done of involving
users through the design and development
process, this should not normally
be a major area of concern.
• Are any exceptions to those processes
supported?
• Do integrations work between
applications?
• Is all the master data, e.g. list of values,
correct? Do the initial data loads import
all the data correctly?
• Will the application work correctly in the
production environment? For example,
the development environment might sit
on a single LAN, but multiple firewalls
might be involved in the production
environment that require opening of
ports and other infrastructure changes.
• Do any specialist modules, e.g. Siebel
Remote, work as expected?
• Will the application work with production
volumes? As it can be very difficult
to replicate production usage scenarios,
careful thought ought to be given to
whether this style of testing is necessary
and practical and, if so, what scenarios
will be simulated.
Test plans are also advisable to ensure a
degree of repeatability, although these
should be as brief as possible to keep the
emphasis on high quality testing, not on
the maintenance of test plans.

10 Inadequate reporting
When designing and configuring a Siebel
application, it is easy to focus entirely on
the entry of data, and how that data should
be transferred to other applications by
integration.
However, in most implementations, a key
requirement is to extract data from the
application and put it in a form that
managers at all levels can use to make
decisions. In other words, the application
must have the capability to report on and
analyse information held in the database.
Oracle provides a number of reporting and
analysis tools including Siebel Reports
(Actuate), Oracle BI Publisher and Oracle
Business Intelligence Enterprise Edition
(Siebel Analytics). The most suitable tool
depends on the situation, and it is often
appropriate to meet multiple requirements
with multiple technologies.
It is essential to consider reporting at the
start of a project, to ensure that the
information captured suits the reporting
requirements, and to ensure that reporting
and analysis are delivered either in parallel
with, or very shortly after, the main Siebel
releases. If any of these steps are omitted,
an otherwise excellent Siebel implementation
can elicit a reaction of “so what?” from
the business community.

************
Siebel EIM

Siebel DB

Siebel Tools

Siebel File Systems

Siebel Workflow

Siebel Configurator

Siebel EAI

Good details on IBM DB2 Siebel Integration Red Book for each
component

*******************************************************************

Activity template

This module allows you to automatically generate activities for processing work.

You have the ability to generate activities for whatever function you are
currently

performing. Activities can automatically be generated for an account, contact,

opportunity, or service request. Activity templates allow administrators to define

standard processes for managing an opportunity or handling a service request.

You use activity templates primarily for processing work. You can create
activities

with dynamic due dates and assign an activity to any user on the system. See
Siebel
Applications Administration Guide for more information.

************

Siebel applet

Discount Authority

Client server vs Web based applications (examples)

Pre-bill adjustments

Post-bill adjustments

eTom
OSS

BSS

SSIS

SSRS

ETL technologies

Database Testing

Basics of performance testing

Basics of Automation testing

Knowledges alligned with the CV

MNP- India Telecordia

MNP is implemented in different ways across the globe. The international and European
standard is for a customer wishing to port his/her number to contact the new provider
(Recipient) who will then arrange necessary process with the old provider (Donor). This is
also known as 'Recipient-Led' porting. The UK is the only country to not implement a
Recipient-Led system, where a customer wishing to port his/her number is required to contact
the Donor to obtain a Porting Authorisation Code (PAC) which he/she then has to give to the
Recipient. Once having received the PAC the Recipient continues the port process by
contacting the Donor. This form of porting is also known as 'Donor-Led' and has been
criticised by some industry analysts as being inefficient. It has also been observed that it may
act as a customer deterrent as well as allowing the Donor an opportunity of 'winning-back' the
customer. This might lead to distortion of competition, especially in the markets with new
entrants that are yet to achieve scalability of operation.
Singapore was the first country to implement MNP

Service Assurance

Service Activation

V Model

• Defect Efficiency

Defect Removal Efficiency (DRE)

DRE is a measure to detect defects before delivery.It is calculated as a percentage of the defects identified and
corrected internally with respect to the total defects in the complete project life cycle. Thus, DRE is the
percentage of bugs elimiated by reviews, inspections, tests etc.

• Defect Effectiveness

No of defect detected divided by time taken for total execution

• Test Plan Effectiveness

No of written divided by time taken for total execution