⏱️ Lab 4: Trace SLA Timers and Explore Workflow
Estimated time: 20–25 minutes
Goal
Trace an incoming telecom customer Service Request (SR) through SLA-driven status changes and inspect the underlying workflow automation in Siebel Web Tools.
Prerequisites
- Login:
TRAINEE00throughTRAINEE09(10 Trainees, Password is the same as Username: e.g.TRAINEE00 / TRAINEE00) - Applications: Siebel eCommunications (or Call Center) for SR processing, and Siebel Web Tools for workflow exploration.
Exercise 1: Create or Locate a Service Request
Record a Telecom Coverage Complaint
- Log in to Siebel eCommunications.
- Click Site Map → Service Requests → All Service Requests.
- Click New to log an incident:
- Area:
Network / Coverage - Sub-Area:
Data Latency / Dropped Calls - Priority:
2-High - Status:
Open - Summary:
Customer reporting high latency on 5G tower cell #304 - Account: Select
Juma Family Account(from Lab 3) - Contact: Select
Amina Juma
- Area:
- Save the record (Ctrl+S). Note the generated SR #.
✅ Success Check: Service Request is created with Status = "Open" and linked to customer account.
Exercise 2: Review SLA Timers and Entitlements
Verify SLA Commitments
- With your SR open, inspect the Service Request Detail applet.
- Locate the SLA and commitment date fields:
- Commitment Response Due: Calculates initial acknowledgement SLA (e.g. within 2 hours).
- Commitment Resolution Due: Calculates final fix SLA deadline (e.g. within 24 hours based on entitlement).
- Entitlement: Shows customer service tier (e.g., Gold Premium Telecom SLA).
- In the child applet tabs, click Activities → click New:
- Type:
Customer Contact - Call - Description:
Acknowledged ticket with subscriber; initiated field diagnostics - Status:
Done
- Type:
- Save the activity. This timestamps response SLA compliance.
Exercise 3: Execute Lifecycle Status Transitions
Simulate Escalation and Resolution
- Return to the main SR form.
- Change Status from
OpentoIn Progress→ Save. (Engineering investigation underway). - Simulate third-party dependency: Change Status to
Pending External→ Save. (In telecom, this pauses SLA timers while waiting on field fiber repair). - Resume and complete: Change Status to
Resolved→ enter Resolution Code:Tower Antennas Realighed. - Finally, change Status to
Closed→ Save. Note the Date Closed timestamp populated.
✅ Success Check: Status cycle completed: Open → In Progress → Pending External → Resolved → Closed.
Exercise 4: Inspect Workflow Process in Siebel Web Tools
Explore Workflow Automation (Read-Only)
- Open a new browser tab and navigate to Siebel Web Tools:
https://siebeltraining.shreejientserv.in/siebel/app/webtools/enu - Log in using your assigned credentials (e.g.
TRAINEE00 / TRAINEE00). - In the Object Explorer on the left, locate and click Workflow Process.
- In the query bar, search for:
FS - Verify Entitlement SR*(orSR Recommendation Workflow). - Select the workflow and click Design / double-click to view the visual process canvas.
- Observe the core workflow building blocks:
- Start Step: Initiated when an SR is created or modified.
- Business Service Step: Calls
Rule Engine ServiceorEntitlement Serviceto calculate SLA due dates. - Decision Point: Checks if customer contract has Gold vs. Standard coverage tier.
- End Step: Commits calculated deadline timestamps back to
S_SRV_REQ.
Mermaid: SLA Escalation Architecture
flowchart TD
A[SR Created in eCommunications] --> B[Workflow Triggered: FS - Verify Entitlement SR]
B --> C{Check Entitlement Tier}
C -- Gold Tier --> D[Response SLA: 2 Hrs / Resolution SLA: 12 Hrs]
C -- Standard Tier --> E[Response SLA: 4 Hrs / Resolution SLA: 24 Hrs]
D --> F[Timers Monitored in Background]
E --> F
F -- Resolved in SLA --> G[Closed - SLA Compliant]
F -- Timer Breached --> H[Escalate to Level 2 Manager]
Validation Checklist
- ✅ Service Request created with Account and Contact linked
- ✅ Acknowledgment activity logged with completion timestamp
- ✅ Status cycled through In Progress, Resolved, and Closed
- ✅ Inspected
FS - Verify Entitlement SRworkflow structure in Siebel Web Tools