Implementation Case Study (Siebel 8.

0)

Module 2: Case Study Introduction

2
Copyright © 2007, Oracle. All rights reserved.
Module Objectives
 After completing this module you should be able to:
 Describe the customer’s functional requirements
 Identify the deliverables
 Identify the activities required to complete the project

 Why you need to know:

 To be able to successfully start and complete the project

Copyright © 2007, Oracle. All rights reserved. 2 of 16

Telecom Solutions and Products (TSP)
 TSP is a company that:
 Manufactures and sells telecommunication equipment
 Networking solutions for home and businesses
 Cellular and smart phones
 Phone systems for businesses, hotels, and small offices
 Markets to home offices, small offices, and medium-to-large
businesses
 Markets all of its product lines through its internal telesales
organization
 Leverages several dedicated field sales organizations when necessary

Copyright © 2007, Oracle. All rights reserved. 3 of 16

TSP Business Goals
 Capture all incoming caller information
 Accept and process orders immediately
 Forward leads when required to desired field sales organization
 Track opportunities, quotes, and orders

Copyright © 2007, Oracle. All rights reserved. 4 of 16

Case Study Activities
 Install the necessary Siebel software
 Set up the development environment
 Create the customer organization structure with appropriate
Access Control mechanisms
 Configure the application to meet the requirements
 Import legacy data
 Configure business automation using some of the following:
 Assignment Manager
 Siebel Workflow
 Siebel State Model
 Task UI
 Deploy Siebel clients

Copyright © 2007, Oracle. All rights reserved. 5 of 16

Case Study Implementation
 Focuses on the build phase
 Work products from the design phase will be provided

Project Phases Project Stages

Analyze
Plan
Plan

Define Business analyst

hands off the
Design Discover Solution Design
Design Document to the
technical team
Configure
Focus of the
Case Study Build Validate

Deploy

Manage

Run Evaluate

Update

Copyright © 2007, Oracle. All rights reserved. 6 of 16

Inputs for the Case Study
 Customer information from the business analyst includes:
 Scoping document
 Proof-of-concept requirements
 Acceptance criteria
 Functional requirements
 Customer process models to demonstrate business processes
 Organization structure for visibility
 Master data catalog requirements
 Legacy data definitions

Copyright © 2007, Oracle. All rights reserved. 7 of 16

Outputs of the Case Study
 Project team deliverables for the Configure stage include:
 The following completed work products:
 Planning document
 Assignment Manager rules
 Workflow processes and policies
 An installed Siebel database populated with:
 Legacy data
 Employees
 Categorized master data

Copyright © 2007, Oracle. All rights reserved. 8 of 16

Typical Activities: Monday Morning
 Introductions
 Instructor presentations about case study
 Review materials
 Q&A on materials
 Team formation
 First team meeting
 Name team and nominate project manager
 Review installation options

Copyright © 2007, Oracle. All rights reserved. 9 of 16

Typical Activities: Monday Afternoon
 Decide on installation architecture
 Install Siebel server software
 Gateway, Enterprise Servers, SWSE
 Populate database
 Install one machine per student as a development machine
 Install Dedicated Web Clients and sample databases as desired
 Install Siebel Tools
 Extract local databases
 Get repository objects
 Create backups
 Conduct a team meeting to review your progress with the
instructor (as the representative of TSP)

Copyright © 2007, Oracle. All rights reserved. 10 of 16

Typical Activities: Tuesday
 Complete company organization administration
 Organizations, divisions, positions, employees/users
 Import legacy data
 Import product and product lines
 Review data mapping for accounts and contacts
 Import accounts
 Import contacts
 Recommend first review plans with instructor (as the technical expert)
 Complete company catalog administration
 Use the imported products and product lines
 Create a price list for all products
 Test the private access group rights
 Test the product catalog
 Conduct a team meeting to review your progress with the
instructor (as the representative of TSP)

Copyright © 2007, Oracle. All rights reserved. 11 of 16

Typical Activities: Wednesday
 Complete design of all configuration requirements
 Recommend obtaining sign-off for all design solutions before any
configuration is performed
 Complete the configuration
 Test all work in the Dedicated Web and Siebel Web clients
 Conduct a team meeting to review your progress with the
instructor (as the representative of TSP)

Copyright © 2007, Oracle. All rights reserved. 12 of 16

Typical Activities: Thursday
 Complete business process automation including workflow
processes and assignment rules
 Recommend client sign-off for all solutions before any
implementation is performed
 Test all work in all clients
 Work with instructor to determine subject of your presentation
 Develop presentation
 Conduct team meeting to review progress with instructor (as
representative of TSP)

Copyright © 2007, Oracle. All rights reserved. 13 of 16

Typical Activities: Friday
 Conduct final team testing
 Make presentations
 Complete evaluations

 Work with your instructor to understand the specific daily

activities and deliverables expected from each team

Copyright © 2007, Oracle. All rights reserved. 14 of 16

Module Highlights
 Case study activities
 Install the necessary Siebel software
 Set up the development environment
 Create the customer organization structure with appropriate
Access Control mechanisms
 Configure the application to meet the requirements
 Import legacy data
 Configure business automation
 Deploy Siebel clients
 Deliver the following:
 An Siebel application that satisfied the TSP requirements
 An installed Siebel database populated with legacy data
 Work with your instructor to understand the specific daily
activities and deliverables expected from each team

Copyright © 2007, Oracle. All rights reserved. 15 of 16

Copyright © 2007, Oracle. All rights reserved. 16 of 16