Pages 81-115

πŸ“ˆ Day 2 - Topic 4: Advanced Siebel Features

⏱️ Estimated Time: 2.5 Hours
Page 81

🎯 Module Overview

Welcome to Day 2! Today we explore advanced Siebel CRM features that power enterprise operations. This module covers sophisticated functionality for sales, marketing, service, and integration.

What You'll Learn:

Sales Excellence

  • Pipeline Management
  • Opportunity Tracking
  • Forecasting & Quotas
  • Territory Management

Marketing & Service

  • Campaign Management
  • Lead Generation
  • Service Level Agreements
  • Entitlement Management

Integration

  • EAI Architecture
  • Web Services
  • ERP Integration
  • Data Synchronization

Mobile & Modern UI

  • Siebel Mobile
  • Open UI Framework
  • Responsive Design
  • Offline Capabilities
Page 82

πŸ’Ό Sales Pipeline Management

Understanding the Sales Pipeline

The sales pipeline visualizes opportunities from initial contact through closed deals. Siebel provides comprehensive tools to track, analyze, and optimize your sales process.

Standard Pipeline Stages:

  1. Qualification (10%): Initial contact, needs assessment
  2. Needs Analysis (25%): Detailed requirements gathering
  3. Proposal (50%): Solution presentation, pricing
  4. Negotiation (75%): Terms discussion, contract review
  5. Closed Won (100%): Deal finalized
  6. Closed Lost (0%): Opportunity lost to competitor or no decision
Siebel Sales Pipeline

Key Pipeline Metrics

Velocity: Average time opportunities spend in each stage

Conversion Rate: Percentage advancing from one stage to next

Pipeline Value: Total weighted value of all open opportunities

Win Rate: Percentage of opportunities closed as won

Page 83

🎯 Opportunity Management

Creating and Managing Opportunities

Opportunities represent potential sales. Each opportunity tracks products, revenue, timeline, competitors, and probability of success.

Opportunity Fields

Basic Information:
β€’ Name: Descriptive title (e.g., "MegaCorp 5G Enterprise Network")
β€’ Account: Associated customer account
β€’ Contact: Primary decision maker
β€’ Owner: Sales representative responsible
β€’ Sales Stage: Current position in pipeline
β€’ Probability: Likelihood of closing (auto-calculated by stage)
β€’ Revenue: Expected deal value
β€’ Close Date: Target closing date
β€’ Type: New Business, Renewal, Upsell, Cross-sell
β€’ Sales Method: Methodology used (e.g., Solution Selling)

Best Practices

⚠️ Common Mistakes:
  • Creating opportunities too early (before qualification)
  • Not updating close dates regularly
  • Leaving opportunities in late stages too long
  • Inflating revenue projections
βœ… Success Tips:
  • Update opportunities weekly at minimum
  • Use Activities to track all customer interactions
  • Document reasons for stage progression
  • Involve sales managers in large deals early
Page 84

πŸ“¦ Products and Revenue Management

Adding Products to Opportunities

Opportunities can contain multiple products, each with its own quantity, price, and discount structure.

Product Configuration

Product Hierarchy:

  • Product Line: High-level category (e.g., Mobile Services)
  • Product: Specific offering (e.g., 5G Business Plan)
  • Product Defect: SKU or variant (e.g., 5G-BUS-100GB)

Revenue Calculation

Revenue Formula:
List Price Γ— Quantity = Subtotal
Subtotal - (Subtotal Γ— Discount %) = Net Amount
Net Amount + Tax = Total Revenue

Example:
Product: 5G Business Plan
List Price: $500/month
Quantity: 100 lines
Subtotal: $50,000/month
Discount: 15%
Net: $42,500/month
Annual Contract: $510,000

Revenue Types in eCommunications

Page 85

πŸ“Š Sales Forecasting

Forecast Management

Siebel's forecasting engine aggregates opportunity data to predict future revenue. Forecasts roll up through organizational hierarchies and can be adjusted by managers.

Sales Forecasting Dashboard

Forecast Categories

Pipeline: All open opportunities (weighted by probability)

Best Case: All opportunities you might win

Commit: Opportunities you're confident will close

Closed: Deals already won this period

Forecast Submission Process

  1. Rep Reviews: Sales rep reviews their opportunities
  2. Rep Submits: Rep submits forecast to manager
  3. Manager Adjusts: Manager can override rep's numbers
  4. Manager Submits: Manager submits to director
  5. Rollup Continues: Process continues up hierarchy
  6. Executive Review: Senior leadership reviews final forecast
Forecast Accuracy: Measured by comparing forecasted vs actual closed revenue. Industry average is 75-85% accuracy. Siebel tracks accuracy metrics to improve future predictions.
Page 86

🎯 Quota Management

Setting Sales Quotas

Quotas define revenue targets for sales teams and individuals. Siebel tracks performance against quota in real-time.

Quota Types

Revenue Quota

Total dollar amount to be sold

Example: $2M annually

Unit Quota

Number of products/licenses sold

Example: 500 mobile lines

Quota Allocation

Hierarchical Distribution:
Company Quota: $100M
β”œβ”€β”€ Region North: $40M
β”‚ β”œβ”€β”€ Territory A: $15M
β”‚ β”‚ β”œβ”€β”€ Rep 1: $5M
β”‚ β”‚ β”œβ”€β”€ Rep 2: $5M
β”‚ β”‚ └── Rep 3: $5M
β”‚ └── Territory B: $25M
└── Region South: $60M

Quota Attainment Tracking

Attainment %: (Actual Revenue Γ· Quota) Γ— 100

Example: Rep closed $4.5M against $5M quota = 90% attainment

Compensation Impact: Most organizations tie compensation to quota attainment:
  • <80%: Base salary only
  • 80-100%: Base + prorated commission
  • 100-120%: Base + full commission
  • >120%: Base + commission + accelerators
Page 87

πŸ—ΊοΈ Territory Management

Defining Sales Territories

Territories organize customers and prospects for sales coverage. Can be defined by geography, industry, company size, or product line.

Territory Assignment Rules

Geographic: Accounts in specific regions/postal codes

Industry Vertical: Accounts in specific industries (Healthcare, Finance, etc.)

Account Size: Enterprise (>1000 employees), Mid-Market (100-1000), SMB (<100)

Product-Based: Specialists for specific product lines

Named Accounts: Dedicated reps for strategic customers

Territory Alignment

Proper territory design ensures:

⚠️ Territory Overlap: When multiple reps can claim the same account, implement clear rules:
  • First to create opportunity owns it
  • Split credit between reps
  • Manager adjudicates disputes
Page 88

Oracle Siebel Marketing: Enterprise Architecture, Lifecycle & The Golden Thread

1. Module Overview: What is Siebel Marketing?

Siebel Marketing is the core enterprise module of Oracle Siebel CRM designed to govern the entire customer acquisition and retention lifecycle: strategic planning, target segmentation, campaign execution, multi-channel delivery, response tracking, sales opportunity handoff, and closed-loop ROI measurement. In telecom operations, it powers high-impact commercial initiatives including high-speed business broadband acquisition, prepaid-to-postpaid migrations, 5G fiber upsells, and proactive churn retention.

The 4-Layer Architectural Framework

Oracle Siebel Marketing operates across four tightly integrated architectural layers:

  • Layer 1 — Foundation: Organizations/Divisions, Positions, Marketing Responsibilities, Fiscal Periods & Calendars, Catalog Products (Broadband 100/200, Routers), and Marketing Server Engines.
  • Layer 2 — Strategic Planning: Marketing Plans (annual roadmap, executive objectives), Forecasts & Budgets, Quota Plans, and Programs (operational workstreams).
  • Layer 3 — Tactical Execution: Operational Campaigns → Target Lists & Segments → Campaign Contacts → Treatment Offers & Communication Channels (Email/Call/SMS) → Wave Schedules.
  • Layer 4 — Measurement & Closed-Loop Sales: Logged Customer Responses → Lead/Opportunity Conversion → CPQ Quote → Sales Order → Installed Asset → Recurring Revenue & Customer Service.
Marketing Campaign Structure

2. The Core 7-Step Marketing Lifecycle (WHY, WHERE, HOW & NEXT)

Every commercial marketing initiative in Siebel must follow this strict 7-step sequence. Each entity serves a unique governance purpose and directly feeds the downstream operational object:

Step & Entity 1. WHY (Business Reasoning) 2. WHERE (Siebel Location & Table) 3. HOW (Setup Details & Fields) 4. NEXT (Downstream Handoff)
Step 1: Marketing Plan Governance & Budgeting: Establishes the corporate strategic roadmap, financial budget, executive ownership, and revenue targets for a fiscal year. Without a Plan, marketing spend is unbudgeted and unmeasured. Site Map > Marketing Plans
View: Marketing Plans List View
Table: S_SRC (SUB_TYPE = 'Marketing Plan')
1. Click New in Plans applet.
2. Set Name (e.g. TRN26 Telecom Growth Plan FY2026).
3. Set Plan Type = Corporate.
4. Enter Budget Amount ($500,000 USD) and Start/End Dates (Jan 1 – Dec 31, 2026).
5. Set Status = Active.
Feeds Programs: The approved budget and strategic dates of the Plan govern all child Programs created under it.
Step 2: Marketing Program Workstream Partitioning: Divides the corporate plan into targeted business lines (e.g., B2B Broadband, Mobile 5G, Enterprise Leased Lines) so different marketing teams can manage their respective portfolios independently. Site Map > Marketing Plans > Programs View (or Marketing Programs Screen)
Table: S_SRC (SUB_TYPE = 'Marketing Program', PAR_SRC_ID = Plan.ROW_ID)
1. Navigate to Marketing Plans > Programs tab.
2. Click New.
3. Set Name (e.g. TRN26 National B2B Broadband Acquisition Program).
4. Link Parent Plan = TRN26-PLN-01.
5. Enter allocated budget ($250,000 USD).
6. Set Status = Active.
Feeds Campaigns: Provides the programmatic umbrella and budget envelope for multiple tactical campaigns.
Step 3: Marketing Campaign Execution Engine: The operational vehicle that delivers specific product offers (Broadband 100/200) to customer cohorts through assigned channels, wave schedules, and sales teams. Site Map > Campaigns
View: Campaign List View
Table: S_SRC (SUB_TYPE = 'Marketing Campaign', PAR_SRC_ID = Program.ROW_ID)
1. In Campaigns view, click New.
2. Set Name (e.g. TRN26-T01 Broadband Acquisition).
3. Associate Program = TRN26-PRG-01.
4. Set Campaign Type = Acquisition.
5. Set Status = Active, currency = USD, and campaign budget ($25,000).
Feeds Target Groups: The campaign defines what is being sold, which now requires a specific target audience.
Step 4: Target List & Segments Audience Definition & Privacy Compliance: Identifies which specific customer accounts and contacts are eligible, while applying suppression rules (Do Not Call, Do Not Email, Existing Active Contract). Site Map > List Management > Lists
View: List Management List View
Tables: S_CALL_LST, S_CALL_LST_CON
1. Click New in Lists view.
2. Set Name (e.g. TRN26-T01 Broadband Target List).
3. Set List Type = Prospect or Customer.
4. Navigate to List Members sub-tab.
5. Add eligible contacts (e.g. Learner01 Contact01 to 06) verifying suppression flags.
Populates Campaign Contacts: The list members are imported or allocated into the Campaign Target Group.
Step 5: Campaign Contacts Operational Recipient Roster: Represents the live roster of individual contacts assigned to sales agents, call centers, or automated email/SMS dispatch engines. Tracks per-contact outreach state. Site Map > Campaigns > Contacts/Prospects View
Table: S_CAMP_CON (links SRC_ID and CON_PER_ID)
1. In Campaign detail, navigate to Contacts / Prospects.
2. Click Add Target List or Add Contacts.
3. Select TRN26-T01 Broadband Target List.
4. System populates roster and sets initial status = In Progress or Pending Outreach.
Logs Responses: As agents interact with contacts on this roster, customer outcomes are captured as Responses.
Step 6: Logged Responses Customer Sentiment & Interaction Tracking: Records the exact customer reaction to the outreach (Interested, Requested Callback, Quote Request, Declined, Opt-Out). Enables closed-loop marketing ROI. Site Map > Responses (or Campaigns > Responses)
Table: S_COMMUNICATION (links SRC_ID, ACCNT_ID, PR_CON_ID)
1. From Campaign Contact or Responses screen, click New.
2. Select Response Type = Inbound Call or Web Lead.
3. Set Outcome = Interested or Requested call back.
4. Enter Subject and details (e.g. Interested in 200Mbps Business Fiber Upgrade).
5. Set Status = Completed.
Converts to Opportunity: Positive, qualified responses trigger sales handoff via Opportunity conversion.
Step 7: Converted Opportunity Sales Handoff & Pipeline Bridge: Bridges the marketing execution to the B2B sales pipeline. Establishes the commercial deal with expected revenue, sales stage, and assigned account executive. Site Map > Opportunities
View: Opportunity List View
Table: S_OPTY (links PR_SRC_ID = Campaign.ROW_ID, COMM_ID = Response.ROW_ID)
1. In Responses view, click Create Opportunity (or create in Opportunities linking Lead Source).
2. Set Opportunity Name (e.g. TRAIN26-T01 Broadband 200M Expansion).
3. Link Lead Campaign = TRN26-T01 Broadband Acquisition.
4. Set Sales Stage = Qualified, Revenue = $2,400 USD.
Initiates CPQ & Order Management: Feeds directly into Quote generation, Order fulfillment, and Asset provisioning.

3. The Golden Thread: Connecting Marketing to Order Management, Installed Assets & Customer Service

The true power of Siebel CRM lies in the seamless, uninterrupted transition from Marketing lead generation to recurring operational revenue and post-sales service:

The End-to-End Enterprise Golden Thread:
[Marketing Plan] → [Marketing Program] → [Campaign] → [Target List] → [Campaign Contacts]
    ↓
[Customer Response (Interested)] → [Sales Opportunity (Qualified)]
    ↓
[CPQ Sales Quote (Broadband 200 + Managed Router + Installation)] → [Credit Check Passed]
    ↓
[Sales Order (Submitted & Approved)] → [Provisioning Workflow (SIS OM Submit Order Process)]
    ↓
[Installed Customer Asset (Circuit ID & Serial Number with $95/mo Recurring Revenue)]
    ↓
[Customer Service (Service Request against Installed Asset & Ongoing Retention)]

Step-by-Step Order Management to Asset Provisioning:

  1. From Opportunity to Quote (CPQ): In the Opportunity, the sales representative clicks Auto-Quote or creates a new Quote (S_DOC_QUOTE). Using the Standard Telecom Price List, line items are configured:
    • Line 1: TRAIN26 Business Broadband 200 ($95.00/month recurring service, Track as Asset = Y)
    • Line 2: TRAIN26 Managed Business Router ($120.00 one-time hardware, Track as Asset = Y)
    • Line 3: TRAIN26 Broadband Installation ($50.00 one-time professional labor charge, Track as Asset = N)
  2. From Quote to Sales Order: Once customer approves the commercial proposal, clicking Order converts the quote into a formal Sales Order (S_ORDER, S_ORDER_ITEM). Line items inherit pricing, discount schedules, and billing accounts.
  3. Order Fulfillment & Provisioning Workflow: Submitting the order triggers the telecom order management workflow (SIS OM Submit Order Process). Network engineering provisions optical fiber ports, assigns circuit numbers, and configures static IP blocks. Order line statuses advance from Pending Provisioning to Complete.
  4. Auto-Asset Creation (S_ASSET): For every order line where the product flag Track as Asset = Y, the Siebel PMT engine automatically generates an active installed asset:
    • Asset 1: TRAIN26-AST-BB200-T01 (Status = Installed, Circuit = CIRCUIT-200M-T01, generating $95.00 Monthly Recurring Revenue).
    • Asset 2: TRAIN26-AST-RTR-T01 (Status = Installed, Serial = RTR-SN-994101-T01, Enterprise Router equipment).
    • Labor exclusion: The installation labor item is billed but discarded from asset tracking, ensuring clean inventory hygiene.
  5. Customer Service against Active Installed Assets (S_SRV_REQ): Once assets are active in S_ASSET, post-sales support begins. When a customer calls support, the representative creates a Service Request directly linked to the customer's specific asset (e.g. Fiber Port Speed Profile Verification against Circuit CIRCUIT-200M-T01). Representatives resolve technical cases within SLA, ensuring high customer satisfaction and preventing churn.

4. Live Classroom Environment Verification Data Matrix

All entities across the complete 7-step marketing cycle and downstream order-to-asset pipeline are fully loaded in the live classroom database (SIEBDB). Trainees and instructors can query and inspect these verified records in Siebel Call Center:

Lifecycle Stage Entity & Record ID Name & Description Status / Key Attributes
Plan (L1) 1-TRN-PLN-01 TRN26 Telecom Growth Plan FY2026 Active | $500,000 USD Budget | Corporate Scope
Program (L1) 1-TRN-PRG-01 TRN26 National B2B Broadband Acquisition Program Active | $250,000 USD Budget | Child of PLN-01
Campaigns (L2) 1-TRN-CMP-00 to 10 TRN26-T00 to T10 Broadband Acquisition Active | $25,000 USD each | Child of PRG-01
Target Lists (L2) 1-TRN-LST-00 to 10 TRN26-T00 to T10 Broadband Target List Active | 6 Contacts each (66 total list members)
Contacts (L3) 1-TRN-CC-01 to 66 Learner00 to Learner10 Contact01–06 Allocated | Statuses: Call Completed / In Progress
Responses (L4) 1-TRN-RSP-00A to 10B Inbound Call & Callback Responses Outcomes: Interested, Callback, Unsubscribe (22 logged)
Opportunities (L4) 1-TRN-OPT-00 to 10 TRAIN26-T00 to T10 Broadband Expansion Won / Qualified | Linked to Lead Campaigns & Responses
Quotes (CPQ) 1-TRN-QUO-00 to 04 TRN26-Q-000 to Q-004 Order Placed / Approved / In Review | Multi-line bundles
Orders (OM) 1-TRN-ORD-00 to 03 TRN26-O-000 to O-003 Complete (T00, T01, T02) | Open/Provisioning (T03)
Installed Assets 1-TRN-AST-BB1, 01B, 02B, RTR Circuit 100M/200M & Enterprise Routers Installed | $60/mo & $95/mo Recurring Revenue
Service Requests 1-TRN-SR-00 to 02 TRN26-SR-000 to SR-002 Linked to Assets | Port speed verification & Wi-Fi config
Activities 1-TRN-ACT-01 to 05 Calls, Feasibility Surveys, Installation & Review Done / Scheduled | Pre-sales to post-sales tracking

5. Server Components Required for Marketing & Order Runtime

The following background engines on the Siebel Server support the marketing and order execution pipelines:

  • Marketing Object Manager: Handles high-concurrency UI interactions for campaign managers and analysts.
  • Workflow Process Manager (WfProcMgr): Orchestrates asynchronous order submission, auto-asset conversion, and notification processes.
  • Marketing Server: Executes campaign workflows, wave segmentation jobs, and schedule triggers.
  • Email Marketing Server / ESD: Manages high-volume outbound email dispatch, bounce processing, and click-through tracking.
  • List Import Service Manager: Ingests external subscriber prospect lists and bulk contact files.
  • Data Quality Manager: Evaluates duplicate contact records and validates address cleansing during import.
Page 89

🎯 Lead Generation and Management

Lead Lifecycle

Leads represent potential customers who have shown interest but are not yet qualified as sales opportunities.

Lead Management Process

Lead Stages

  1. New: Lead just created, not yet contacted
  2. Contacted: Initial outreach attempted
  3. Qualified: Meets BANT criteria (Budget, Authority, Need, Timeline)
  4. Converted: Promoted to Account/Contact/Opportunity
  5. Disqualified: Does not meet criteria
  6. Nurture: Not ready now, keep warm for future

Lead Scoring

Assign points based on lead characteristics to prioritize follow-up:

Demographic Scoring:
β€’ Company Size: Enterprise (+30), Mid-Market (+20), SMB (+10)
β€’ Industry: Target verticals (+25), Others (+5)
β€’ Title: C-Level (+30), VP (+20), Director (+15), Manager (+10)

Behavioral Scoring:
β€’ Downloaded Whitepaper (+10)
β€’ Attended Webinar (+15)
β€’ Visited Pricing Page (+25)
β€’ Requested Demo (+40)
β€’ Multiple Website Visits (+5 each)

Hot Lead: Score > 75
Warm Lead: Score 50-75
Cold Lead: Score < 50

Lead Assignment

Round Robin: Distribute leads evenly across team

Territory-Based: Route by geography or account rules

Skill-Based: Match lead needs to rep expertise

Load Balancing: Assign to rep with fewest active leads

Page 90

🌱 Lead Nurturing Programs

What is Lead Nurturing?

Lead nurturing is the process of developing relationships with leads who aren't ready to buy yet. Automated email sequences keep your company top-of-mind until they're ready.

Nurture Campaign Example: New Mobile Technology

Week 1: Welcome email + 5G overview whitepaper
Week 2: Case study - How Company X improved with 5G
Week 3: Webinar invitation: 5G for Business
Week 4: ROI Calculator tool
Week 6: Competitive comparison guide
Week 8: Limited-time offer or demo invitation

Nurture Best Practices

  • Provide Value: Educational content, not sales pitches
  • Segment Appropriately: Different content for different industries/roles
  • Timing Matters: Space emails appropriately (weekly or bi-weekly)
  • Track Engagement: Monitor opens, clicks to identify hot leads
  • Make Unsubscribe Easy: Maintain list health and compliance

Re-engagement Triggers

Automatically alert sales when nurture lead takes action:

Page 91

πŸ› οΈ Service Operations Management

Service Request Lifecycle

Service requests (SRs) are the core of customer service operations. They track issues from initial report through resolution.

Service Operations

SR Workflow Stages

  1. Open: Customer reports issue via phone, email, web, or chat
  2. Assigned: Routed to appropriate service agent/team
  3. In Progress: Agent actively working on resolution
  4. Pending Customer: Waiting for customer information
  5. Pending Vendor: Escalated to third party
  6. Resolved: Solution provided, awaiting confirmation
  7. Closed: Customer confirms resolution

SR Categories for eCommunications

Technical Issues

  • No service/outage
  • Slow data speeds
  • Dropped calls
  • Device malfunction

Account Services

  • Billing inquiries
  • Plan changes
  • Account updates
  • Payment issues

Multi-Channel Support

Modern service organizations support customers across multiple channels:

Page 92

⏱️ Service Level Agreement (SLA) Management

What are SLAs?

SLAs define contractual commitments for service response and resolution times. Siebel automatically tracks SLA compliance and escalates overdue items.

SLA Management

SLA Metrics

Response Time SLA: How quickly agent must respond
β€’ Priority 1 (Critical): 15 minutes
β€’ Priority 2 (High): 1 hour
β€’ Priority 3 (Medium): 4 hours
β€’ Priority 4 (Low): 24 hours

Resolution Time SLA: How quickly issue must be resolved
β€’ Priority 1: 4 hours
β€’ Priority 2: 24 hours
β€’ Priority 3: 3 days
β€’ Priority 4: 5 days

SLA Components

Agreement: High-level contract with customer

Objective: Specific metric to track (response time, resolution time)

Target: Goal value (e.g., 95% within SLA)

Threshold: Acceptable range before penalties

Breach: SLA violation requiring remediation

SLA Clock Management

Business Hours: SLA clock runs only during business hours (e.g., 8AM-6PM weekdays)

24/7 Support: Clock runs continuously for critical services

Pause Conditions: Clock stops when waiting for customer response

Escalation: Automated escalation when 75% of SLA time elapsed

SLA Reporting

Track SLA performance with metrics:

Page 93

🎫 Entitlement Management

Understanding Entitlements

Entitlements define what services a customer is eligible to receive based on their contract or product purchase. They govern support levels, warranties, and service coverage.

Entitlement Types

Time-Based

Valid for specific duration

Example: 1-year warranty, 90-day support

Incident-Based

Limited number of uses

Example: 5 support calls included

Entitlement Validation

When customer contacts support, Siebel automatically checks:

  1. Is there an active entitlement for this product?
  2. Is the entitlement still within valid dates?
  3. Are there remaining incidents (if applicable)?
  4. Does customer's issue match covered services?
  5. Is customer in good standing (payments current)?
⚠️ Out-of-Entitlement: When customer doesn't have valid coverage:
  • Offer paid support incident ($250-$500 per case)
  • Sell new support contract
  • Escalate to sales for renewal
  • Provide basic troubleshooting only

Service Tiers

Basic Support:
β€’ Email support only
β€’ 5-day response time
β€’ Business hours coverage
β€’ Knowledge base access

Standard Support:
β€’ Phone + email support
β€’ 24-hour response time
β€’ Extended hours coverage
β€’ Community forums

Premium Support:
β€’ 24/7 phone support
β€’ 1-hour response for critical
β€’ Dedicated support manager
β€’ On-site support available
β€’ Proactive monitoring
Page 94

πŸš— Field Service Management

Dispatching Technicians

For telecommunications, field service handles installations, repairs, and equipment maintenance. Siebel optimizes technician scheduling and routing.

Service Appointment Workflow

  1. Request Created: Customer schedules installation or reports outage
  2. Skill Matching: System identifies qualified technicians
  3. Availability Check: Find open time slots
  4. Optimization: Minimize drive time, group nearby appointments
  5. Assignment: Dispatch to technician mobile device
  6. Execution: Technician arrives, performs work
  7. Completion: Update status, capture signature, close SR

Technician Skills

Match appointments to qualified technicians:

  • Fiber Installation: Certified fiber technicians only
  • Network Troubleshooting: Senior technicians
  • Equipment Swap: Any field tech
  • Business Installation: Commercial installation certification

Mobile Field Service

Technicians use mobile devices for:

Page 95

πŸ”— Enterprise Application Integration

πŸ“Œ Training Note: This section covers integration concepts and architecture. Our training environment is a standalone Siebel system without external ERP/billing systems. Integration content is theoretical to help you understand how Siebel connects with other systems in production environments.

Why Integration Matters

Siebel CRM rarely operates in isolation. Modern enterprises integrate CRM with ERP, billing, provisioning, and other systems to create seamless processes.

Integration Architecture

Common Integration Scenarios

Order to Cash: Opportunity in Siebel β†’ Order in ERP β†’ Invoice in Billing β†’ Payment Collection β†’ Revenue Recognition

Service to Provisioning: Service Request in Siebel β†’ Ticket in OSS β†’ Provision in Network β†’ Update Siebel

Marketing to Sales: Campaign in Marketing Automation β†’ Lead in Siebel β†’ Opportunity β†’ Account in ERP

Integration Technologies

Real-Time

  • Web Services (SOAP/REST)
  • Business Services
  • EAI Siebel Adapter
  • Oracle Integration Cloud

Batch

  • EIM (Data Import/Export)
  • File-based interfaces
  • Scheduled workflows
  • Database links
Page 96

🌐 Web Services Integration

Siebel as a Service Provider

Siebel exposes business logic through web services, allowing external systems to create, query, and update CRM data.

Inbound Web Service Example

Scenario: External website creates service request

SOAP Request:
<CreateServiceRequest>
<Account>MegaCorp Industries</Account>
<Type>Technical Issue</Type>
<Description>Internet outage</Description>
<Priority>High</Priority>
</CreateServiceRequest>

Response:
<Response>
<SRNumber>SR-2025-12345</SRNumber>
<Status>Success</Status>
</Response>

Siebel as a Service Consumer

Siebel can call external web services to retrieve data or trigger actions in other systems.

Scenario: Check product availability in ERP

Outbound Call from Siebel:
Business Service β†’ External Web Service Endpoint
Request: Product SKU, Quantity
Response: Available (Yes/No), Lead Time, Price
Update Opportunity with availability info

REST APIs

Modern REST APIs provide simpler integration:

GET /api/accounts/12345 - Retrieve account details

POST /api/opportunities - Create new opportunity

PATCH /api/serviceRequests/SR-789 - Update SR

DELETE /api/contacts/98765 - Delete contact

Page 97

πŸ’Ό ERP System Integration

CRM to ERP Data Flow

Critical data must flow between Siebel CRM and ERP systems like Oracle EBS, SAP, or NetSuite for unified operations.

Key Integration Points

Accounts: Master customer data shared between systems

Products: Catalog synchronized from ERP to CRM

Pricing: Real-time price lookups from ERP

Orders: Opportunities become sales orders in ERP

Inventory: Available-to-promise checks

Invoices: Billing data from ERP visible in CRM

Payments: Account status updates from ERP

Bi-Directional Sync

CRM β†’ ERP:
β€’ New accounts created by sales
β€’ Opportunities converted to quotes
β€’ Quotes converted to orders
β€’ Service requests requiring billing adjustments

ERP β†’ CRM:
β€’ Product catalog updates
β€’ Pricing changes
β€’ Order fulfillment status
β€’ Invoice and payment information
β€’ Credit hold notifications

Data Governance

⚠️ Master Data Management:

Designate system of record for each data type:

  • Accounts: CRM creates, ERP enriches with financial data
  • Products: ERP is master, CRM is read-only
  • Contacts: CRM is master
  • Orders: CRM initiates, ERP owns after submission
Page 98

πŸ“± Siebel Mobile Architecture

Mobile CRM Overview

Siebel Mobile enables users to access CRM functionality from smartphones and tablets, with online and offline capabilities.

Siebel Mobile Architecture

Mobile Deployment Options

Siebel Mobile (Disconnected)

Full offline capability with local database

  • Download data to device
  • Work without connectivity
  • Synchronize when online
  • Ideal for field service

Open UI (Connected)

Browser-based responsive interface

  • Always online
  • Real-time data
  • No installation needed
  • Ideal for office/remote workers

Mobile Use Cases

Sales Reps: Update opportunities on customer site, check inventory, send quotes

Field Technicians: View appointments, update service requests, capture signatures

Executives: Review dashboards, approve discounts, monitor pipeline

Service Agents: Respond to customer inquiries while away from desk

Offline Synchronization

For disconnected mobile:

  1. Download: User syncs before going offline (daily or as needed)
  2. Work Offline: Create/update records in local database
  3. Upload: When reconnected, changes sent to server
  4. Conflict Resolution: If same record modified online and offline, user resolves
Page 99

🎨 Open UI Framework

What is Open UI?

Open UI is Siebel's modern, responsive user interface framework introduced in IP 15. It replaces the legacy ActiveX controls with HTML5, CSS3, and JavaScript.

Open UI Benefits

  • Browser Compatibility: Works in Chrome, Firefox, Safari, Edge - no plugins needed
  • Responsive Design: Adapts to desktop, tablet, and phone screen sizes
  • Modern UX: Contemporary look and feel
  • Customizable: Easier to modify UI with CSS and JavaScript
  • Better Performance: Faster page loads and interactions
  • Accessibility: Improved support for screen readers and keyboard navigation

Customization Architecture

Presentation Model (PM): JavaScript logic layer
β€’ Controls UI behavior
β€’ Handles events
β€’ Communicates with server

Physical Renderer (PR): HTML generation
β€’ Creates DOM elements
β€’ Defines layout
β€’ Applies styling

Custom Files:
β€’ /custom/scripts/ - Custom PM/PR JavaScript
β€’ /custom/styles/ - Custom CSS
β€’ /custom/images/ - Custom icons and graphics

UI Customization Examples

  • Change color scheme to match corporate branding
  • Add custom buttons with JavaScript actions
  • Create new applet types (e.g., Kanban board)
  • Integrate third-party JavaScript libraries (charts, maps)
  • Build custom controls for specific data types
Page 100

βœ… Integration Best Practices

Design Principles

Loose Coupling: Systems should interact through well-defined interfaces, not direct database access

Error Handling: Gracefully handle timeouts, invalid data, and system unavailability

Logging: Comprehensive audit trail of all integration transactions

Monitoring: Real-time alerts for integration failures

Scalability: Design for growing data volumes and transaction rates

Performance Optimization

  • Batch vs Real-Time: Use real-time only when necessary (e.g., pricing). Batch is more efficient for bulk data.
  • Pagination: For large datasets, retrieve in chunks (e.g., 1000 records at a time)
  • Caching: Cache frequently accessed reference data locally
  • Asynchronous Processing: Don't make users wait for slow external calls

Security Considerations

⚠️ Protect Your Data:
  • Authentication: Use OAuth 2.0 or API keys, never embed passwords in code
  • Encryption: Always use HTTPS/TLS for web service calls
  • Authorization: Validate user permissions before exposing data
  • Input Validation: Sanitize all incoming data to prevent injection attacks
  • Rate Limiting: Prevent abuse with API throttling

Testing Strategy

  1. Unit Testing: Test individual integration components in isolation
  2. Integration Testing: Test end-to-end flows between systems
  3. Performance Testing: Verify response times under load
  4. Failover Testing: Ensure graceful degradation when external system unavailable
  5. Data Validation: Confirm data accuracy after transformation
Page 101

πŸŽ“ Advanced Configuration Topics

Workflow Automation

Siebel Workflow automates business processes with visual drag-and-drop design. Common uses include approval routing, notification triggers, and data synchronization.

Workflow Components

Process: Top-level workflow definition
Steps: Individual actions (Decision, Task, Business Service)
Connectors: Logic flow between steps
Siebel Operation: Create, update, query records
Business Service: Call custom logic
Wait Step: Pause for time or event

Example: Opportunity Approval Workflow

  1. Trigger: Sales rep changes opportunity stage to "Proposal"
  2. Decision: Is revenue > $50,000?
  3. If Yes: Create approval task for sales manager
  4. Wait: Until manager approves or rejects
  5. If Approved: Move stage to "Negotiation", send email to rep
  6. If Rejected: Move back to "Needs Analysis", notify rep with feedback

Runtime Events

Workflows can be triggered by:

Page 102

πŸ“‹ Assignment Rules

Automated Record Assignment

Assignment Manager automatically routes records to appropriate owners based on configurable rules.

Assignment Criteria

Geographic: Assign based on customer address/zip code

Product-Based: Route to specialists for specific products

Skill-Based: Match to qualified resources

Load Balanced: Distribute evenly across team

Round Robin: Rotate assignments sequentially

Assignment Example: Service Requests

IF SR Type = "Network Outage" AND Priority = "Critical"
THEN Assign to: Network Operations Team
AND Escalate to: NOC Manager

IF SR Type = "Billing Question" AND Account Type = "Enterprise"
THEN Assign to: Enterprise Billing Specialist

IF SR Type = "Technical Support" AND Product = "5G Service"
THEN Assign to: 5G Support Team Member (Round Robin)
Page 103

πŸ” Advanced Security

Multi-Layered Security Model

Siebel implements defense-in-depth with multiple security layers working together.

Security Layers

  1. Authentication: Verify user identity (LDAP, SSO, Database)
  2. Responsibility: Define what views/functions user can access
  3. Access Control: Row-level security (see only assigned records)
  4. Field-Level Security: Hide/show sensitive fields
  5. Audit Trail: Log all data changes

Visibility Rules

Organization: Users see only records in their organization

Position: Managers see their team's records

Personal: Users see only records they own

All: Unrestricted access (administrators only)

Data Privacy Compliance

⚠️ GDPR & Privacy Regulations:
  • Implement "Right to be Forgotten" workflows
  • Mask sensitive personal data (SSN, credit cards)
  • Encrypt data at rest and in transit
  • Maintain consent records
  • Enable data export for customer requests
  • Set retention policies and auto-delete old records
Page 104

πŸ“Š Analytics and Insights

Embedded Analytics

Siebel provides built-in analytics dashboards with real-time metrics and charts.

Key Performance Indicators (KPIs)

Sales KPIs

  • Pipeline value by stage
  • Win rate percentage
  • Average deal size
  • Sales cycle length
  • Quota attainment

Service KPIs

  • First call resolution
  • Average handle time
  • SLA compliance rate
  • Customer satisfaction
  • Backlog by priority

Chart Types

Page 105

πŸ”„ Business Process Automation

End-to-End Process Design

Link multiple workflows and business services to automate complex business processes spanning multiple departments.

Example: New Customer Onboarding

Step 1: Sales (Opportunity Won)
β€’ Opportunity marked Closed-Won
β€’ Trigger: Create account in ERP
β€’ Create customer record in billing system

Step 2: Order Management
β€’ Convert quote to order
β€’ Reserve inventory
β€’ Schedule installation

Step 3: Fulfillment
β€’ Dispatch technician
β€’ Provision service
β€’ Activate in network

Step 4: Customer Success
β€’ Send welcome email
β€’ Create onboarding tasks
β€’ Schedule follow-up call
β€’ Assign customer success manager
Page 106

Telecom Product Administration, Catalog Architecture & Order Management

In Siebel Communications (eCommunications), product administrators design, price, and release multi-tier product catalogs that automatically decompose into structured parent/child line items across Quotes, Sales Orders, and Installed Assets.

1. The 4-Tier Product Administration Architecture

Before a sales representative or customer can configure an order, the product management team establishes four foundational layers in Siebel Administration:

Layer / Entity WHY (Business Purpose) WHERE (Siebel Navigation) HOW (Key Setup Fields & Actions) NEXT (Downstream Hand-off)
1. Product Lines
(S_PROD_LN)
Partitions the catalog into high-level business families for revenue forecasting, quota tracking, and sales territory alignment. Site Map → Administration - Product → Product Lines Create Product Line (e.g., TRN26-PLN-01 Enterprise Broadband, TRN26-PLN-02 Managed Hardware). Associate products in child Product Line Products applet (S_PROD_LN_PROD). Governs catalog search visibility and feeds product-family quota rollups in Administration - Period.
2. Product Classes & Dynamic Attributes
(S_XA_CLASS, S_XA_ATTR)
Defines technical and commercial specifications dynamically without database schema changes. Subclasses inherit parent attributes. Site Map → Administration - Product → Product Classes Create Class (e.g. TRN26-CLS-01 Broadband Class, TRN26-CLS-02 Hardware Class). Under Attributes, add: Download Speed, Upload Speed, IP Type, SLA Level, Wi-Fi Standard. Set data types, defaults, and user display flags. All products linked to this class inherit its dynamic attributes automatically during CPQ quoting.
3. Product Definition & Versioning
(S_PROD_INT, S_PROD_REL)
Defines sellable items, structure types (Single, Bundle, Customizable), asset tracking rules, and locks versions for runtime stability. Site Map → Administration - Product → Products Create product (e.g. TRAIN26 Business Connect Starter Bundle). Set: Structure = Commercial Bundle, Class = TRN26-CLS-01, Orderable = Y, Track as Asset = Y. Click Release Version. Freezes definition into S_PROD_REL. Unreleased products cannot be quoted or ordered by end users.
4. Price Lists & Rate Cards
(S_PRI_LST_ITEM)
Determines transactional pricing: One-Time Non-Recurring Charges (NRC) vs Monthly Recurring Charges (MRC). Site Map → Administration - Pricing → Price Lists Open Standard Telecom Price List. In Price List Items, add product: List Price = .00, Currency = USD, Payment Type = Non-recurring, Effective Start = 2026-01-01. Populates baseline price and fuels the Siebel Pricing Engine during quote calculations and discount adjustments.

2. Structured Bundles & Parent/Child Line Item Decomposition

When selling enterprise packages (such as fiber broadband combined with managed routers and installation services), Siebel CPQ supports structured Bill of Materials (BOM) decomposition:

Commercial Bundle Hierarchy Example (TRAIN26 Business Connect Starter Bundle):
[Line 1.0] TRAIN26 Business Connect Starter Bundle (Parent Package Header - .00 Flat)
  +-- [Line 1.1] TRAIN26 Business Broadband 100 (Child Component - .00/month Recurring MRC)
  +-- [Line 1.2] TRAIN26 Managed Business Router (Child Hardware - .00 Non-Recurring NRC)
  +-- [Line 1.3] TRAIN26 Broadband Installation (Child Labor Service - .00 Transient Labor)

Database Hierarchy Linking Rules Across the Golden Thread:

  • Quotes (S_QUOTE_ITEM): Child lines reference PAR_SQ_ITEM_ID pointing to the root bundle item (ROOT_QUOTE_ITEM_ID).
  • Orders (S_ORDER_ITEM): Decomposed lines maintain exact parentage via PAR_ORDER_ITEM_ID and ROOT_ORDER_ITEM_ID.
  • Installed Assets (S_ASSET): Active physical/service assets reference parent package via PAR_ASSET_ID and ROOT_ASSET_ID.
  • Asset Conversion Filtering: Products marked with Track as Asset = Y (Broadband Circuit & Router) persist into S_ASSET, while labor charges (Track as Asset = N) automatically expire upon order fulfillment.

3. The Complete Order Management Lifecycle (CPQ to Provisioned Asset)

Step 1: Sales Quote Creation & CPQ Configuration

In Opportunities → Quotes, sales reps select the Standard Telecom Price List and add the bundle or individual products. Dynamic class attributes (e.g. Static IP, 100 Mbps) are chosen. Clicking Reprice validates pricing totals ( MRC + NRC = Total).

Step 2: Quote Validation & Order Conversion (Auto-Order)

Clicking Auto Order invokes the CPQ business service. Siebel validates required attributes, credit checks, and pricing rules, then creates a formal Sales Order (TRN26-O-XXX) with fully decomposed parent/child line items.

Step 3: Order Submission & Provisioning Workflow

Updating Order Status to Submitted triggers the SIS OM Submit Order Process workflow. The order progresses from Open → Submitted → Complete as provisioning and network dispatch are confirmed.

Step 4: Automated Asset Provisioning & Recurring Revenue Tracking

The Order-to-Asset engine converts completed order lines into active records in S_ASSET. The active circuit asset generates Monthly Recurring Revenue (MRR: /mo or /mo), tracked across financial periods.

Step 5: Post-Sales Customer Service Linked to Active Asset

When the subscriber requires technical assistance, a customer service representative opens Service Requests and links the ticket directly to the installed asset (e.g., TRAIN26-AST-BB100-T01). This enables complete 360-degree service visibility from lead generation through recurring revenue.

Page 107

πŸš€ Performance Tuning

Query Optimization

Slow queries are the #1 performance issue. Follow these guidelines:

βœ… Best Practices:
  • Use Indexes: Ensure frequently searched fields have indexes
  • Limit Results: Use filters to reduce record count
  • Avoid Wildcards: "Smith%" is faster than "%Smith%"
  • Denormalize When Needed: Copy critical data to avoid joins
  • Use Search Specifications: Pre-filter data at BC level

Caching Strategies

Static LOV Cache: Cache picklist values
Server Cache: Cache frequently accessed BCs
Browser Cache: Cache images, JavaScript, CSS
Named Search Cache: Cache common queries

Database Tuning

Page 108

πŸ”§ Troubleshooting Advanced Issues

Common Problems and Solutions

Problem: Workflow not triggering

Solutions:

  • Check workflow policy conditions are met
  • Verify runtime events are enabled
  • Review workflow policy filter criteria
  • Check user has permission to execute workflow

Problem: Integration timeout errors

Solutions:

  • Increase timeout value in business service
  • Optimize external service performance
  • Implement asynchronous processing
  • Add retry logic with exponential backoff

Problem: Mobile sync conflicts

Solutions:

  • Configure conflict resolution rules (server wins/client wins)
  • Reduce sync visibility to minimize conflicts
  • Train users to sync more frequently
  • Implement optimistic locking
Page 109

πŸ“ˆ Scalability and High Availability

Horizontal Scaling

Add more servers to handle increased load:

Web Tier: Multiple web servers behind load balancer

Application Tier: Multiple Siebel servers in enterprise

Database Tier: Oracle RAC for database clustering

Load Balancing Strategies

Round Robin: Distribute requests evenly
Least Connections: Route to server with fewest active users
Session Affinity: Keep user on same server (sticky sessions)
Geographic: Route to nearest data center

Disaster Recovery

Page 110

πŸ”’ Advanced Administration

System Monitoring

Proactive monitoring prevents issues before users are impacted.

Key Metrics to Monitor

Server Health: CPU, memory, disk I/O

Application Response: Page load times, query duration

Database Performance: Connection pool, lock waits

Workflow Engine: Backlog, error rate

Integration: Message queue depth, failure count

User Activity: Concurrent users, session duration

Alerting Strategy

Critical Alerts: Page/call immediately
β€’ Database down
β€’ All servers unavailable
β€’ Data corruption detected

Warning Alerts: Email to team
β€’ CPU > 80% for 5 minutes
β€’ Disk > 90% full
β€’ Integration failures > 10/hour

Info Alerts: Daily summary
β€’ Performance trending
β€’ Capacity planning metrics
Page 111

🌐 Globalization and Localization

Multi-Language Support

Siebel supports 35+ languages out of the box. Users can switch language preferences without affecting underlying data.

Localization Components

Multi-Currency Operations

Base Currency: USD (Organization default)
Opportunity Currency: EUR (Customer preference)
Amount in EUR: €100,000
Exchange Rate: 1.10
Amount in USD: $110,000

Time Zone Handling

Store all timestamps in UTC, display in user's local time zone:

Server Time: 2025-10-31 14:00 UTC

US Eastern: 2025-10-31 10:00 AM EDT

India: 2025-10-31 7:30 PM IST

Australia: 2025-11-01 1:00 AM AEDT

Page 112

πŸ”„ Upgrade and Migration

Siebel Upgrade Path

Keep Siebel current with Oracle's regular updates (typically annual).

Upgrade Planning

  1. Review Release Notes: Understand new features and deprecations
  2. Test in Sandbox: Validate compatibility with customizations
  3. Regression Testing: Test all critical business processes
  4. Performance Testing: Ensure no degradation
  5. User Acceptance Testing: Validate UI changes
  6. Training: Educate users on new features
  7. Cutover Planning: Minimize downtime
  8. Rollback Plan: Be ready to revert if needed

Data Migration

When migrating from legacy systems to Siebel:

⚠️ Migration Checklist:
  • Profile source data quality (completeness, accuracy)
  • Map source fields to Siebel tables
  • Cleanse and deduplicate data before migration
  • Migrate in phases (master data β†’ transactions β†’ history)
  • Validate migrated data thoroughly
  • Maintain data lineage for audit
  • Plan for cutover weekend
Page 113

πŸ“š Advanced Topics Summary

Key Takeaways

βœ… Sales Automation: Pipeline, forecasting, and territory management drive revenue growth

βœ… Marketing Excellence: Campaigns and lead nurturing generate qualified opportunities

βœ… Service Operations: SLAs and entitlements ensure customer satisfaction

βœ… Integration: Web services and ERP connectivity create unified systems

βœ… Mobile Access: Field teams stay productive anywhere

βœ… Open UI: Modern, responsive interface improves user experience

Page 114

🎯 Practical Exercise Preview

Day 2 Practicals

In this afternoon's labs, you'll apply these advanced concepts:

Lab 1: Sales Process Configuration

  • Create opportunity with products
  • Configure approval workflow
  • Generate forecast

Lab 2: Service Operations

  • Configure SLA rules
  • Set up entitlements
  • Test assignment rules

Lab 3: Integration Hands-On

  • Call external web service
  • Configure EIM integration
  • Test data synchronization
Page 115

πŸ“– Additional Resources

Oracle Documentation

Community Resources

πŸŽ‰ Congratulations!

You've completed Topic 4: Advanced Siebel Features. You now understand enterprise-grade functionality for sales, service, marketing, and integration.

Next: Topic 5 will cover Reporting and Analytics to help you extract insights from your CRM data.