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.
Siebel's forecasting engine aggregates opportunity data to predict future revenue. Forecasts roll up through organizational hierarchies and can be adjusted by managers.
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
Rep Reviews: Sales rep reviews their opportunities
Rep Submits: Rep submits forecast to manager
Manager Adjusts: Manager can override rep's numbers
Manager Submits: Manager submits to director
Rollup Continues: Process continues up hierarchy
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.
Product-Based: Specialists for specific product lines
Named Accounts: Dedicated reps for strategic customers
Territory Alignment
Proper territory design ensures:
Balance: Equal opportunity across territories
Coverage: No accounts left unassigned
Clarity: Clear ownership, no disputes
Efficiency: Minimize travel time and costs
β οΈ 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.
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.
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.
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:
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)
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.
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.
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:
Labor exclusion: The installation labor item is billed but discarded from asset tracking, ensuring clean inventory hygiene.
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 Contact0106
Allocated | Statuses: Call Completed / In Progress
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:
Opens 3+ emails in one week
Clicks on pricing page
Downloads multiple resources
Revisits website multiple times
Changes job title or company
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.
SR Workflow Stages
Open: Customer reports issue via phone, email, web, or chat
Assigned: Routed to appropriate service agent/team
In Progress: Agent actively working on resolution
Pending Customer: Waiting for customer information
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:
Compliance %: (Met SLA Γ· Total SRs) Γ 100
Average Response Time: Across all priorities
Average Resolution Time: From open to closed
Breach Count: Number of SLA violations
At Risk SRs: Currently open and nearing deadline
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:
Is there an active entitlement for this product?
Is the entitlement still within valid dates?
Are there remaining incidents (if applicable)?
Does customer's issue match covered services?
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
Request Created: Customer schedules installation or reports outage
Skill Matching: System identifies qualified technicians
Availability Check: Find open time slots
Optimization: Minimize drive time, group nearby appointments
Assignment: Dispatch to technician mobile device
Execution: Technician arrives, performs work
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:
View daily schedule and navigate to appointments
Access customer history and equipment details
Update service request status in real-time
Capture photos of installations
Collect customer signatures
Check inventory and order parts
Submit timesheets
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.
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
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.
Service Agents: Respond to customer inquiries while away from desk
Offline Synchronization
For disconnected mobile:
Download: User syncs before going offline (daily or as needed)
Work Offline: Create/update records in local database
Upload: When reconnected, changes sent to server
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
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
Unit Testing: Test individual integration components in isolation
Integration Testing: Test end-to-end flows between systems
Performance Testing: Verify response times under load
Failover Testing: Ensure graceful degradation when external system unavailable
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
Trigger: Sales rep changes opportunity stage to "Proposal"
Decision: Is revenue > $50,000?
If Yes: Create approval task for sales manager
Wait: Until manager approves or rejects
If Approved: Move stage to "Negotiation", send email to rep
If Rejected: Move back to "Needs Analysis", notify rep with feedback
Runtime Events
Workflows can be triggered by:
Record Created: New account, opportunity, SR
Record Updated: Field value changes
Record Deleted: Cleanup actions
Scheduled: Daily/weekly/monthly batch processes
Manual: User clicks button to start workflow
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
Authentication: Verify user identity (LDAP, SSO, Database)
Responsibility: Define what views/functions user can access
Access Control: Row-level security (see only assigned records)
Field-Level Security: Hide/show sensitive fields
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
Bar/Column: Compare values across categories
Line: Show trends over time
Pie: Display proportional breakdown
Gauge: Show progress toward target
Funnel: Visualize conversion rates
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
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-01Enterprise Broadband, TRN26-PLN-02Managed 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.
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-01Broadband Class, TRN26-CLS-02Hardware 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.
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:
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.
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
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
Database Backup: Daily full + hourly incrementals
File System Backup: Repository, custom files
Standby Database: Real-time replication
DR Site: Secondary data center for failover
RTO/RPO Targets: Define acceptable downtime and data loss
Page 110
π Advanced Administration
System Monitoring
Proactive monitoring prevents issues before users are impacted.