Worked Example: Fixed B2B
Worked Example: Fixed B2B — "Enterprise Fibre Connect Gold"
This is the second of five technology-specific worked examples in Module 3 (Sections 3.6–3.10), each showing how COM, SOM, and ROM handle a different product and technology domain. Where Section 3.6 traced a single residential broadband order through the stack, this section introduces the B2B differentiators that make enterprise order management significantly more complex: multi-site ordering, per-site feasibility, SLA selection, enterprise approval workflows, negotiated pricing, and phased rollout across geographic waves.
Fixed B2B activation — SOM orchestrates through ROM to provision OLT/EMS, BNG, IPAM, Enterprise QoS, ACS, and SLA probes
The Scenario
Order Summary
| Attribute | Value |
|---|---|
| Customer | GlobalTech Solutions Pty Ltd (CUST-ENT-1102) |
| Account | ACC-ENT-3384 (enterprise account) |
| Product Offering | Enterprise Fibre Connect Gold (PO-EFCG-01) |
| Product Specification | Enterprise Symmetric Access (PS-ESA-01) |
| Sites | 5 branches — Melbourne HQ, 2x Sydney, 2x Brisbane |
| Access Technology | GPON / P2P Ethernet (varies per site) |
| Download / Upload | 500 Mbps symmetric |
| SLA Tier | Gold — 99.95% availability, 4-hour restore |
| CPE | Cisco ISR 4431 managed router (per site) |
| Contract Term | 36 months |
| Monthly Price | $1,800/site ($9,000 total monthly) |
| Rollout | Phased: Pilot → Wave 1 → Wave 2 |
Step 1: Enterprise CPQ, Feasibility & Approval
Enterprise Sales & CPQ Processing
Account Manager Prepares Solution
Enterprise Sales ConsoleThe account manager (AM) uses the enterprise sales console to load the GlobalTech account hierarchy. They select "Enterprise Fibre Connect Gold" (PO-EFCG-01) and add 5 site entries — Melbourne HQ, 2 Sydney offices, and 2 Brisbane offices — each with verified site addresses and contact details.
Per-Site Feasibility Check
CPQ → Address QualificationCPQ calls the address qualification API for each of the 5 sites independently. Melbourne HQ: GPON available (OLT-SOUTH-03 serving area). Sydney Office 1: P2P Ethernet available. Sydney Office 2: P2P Ethernet available. Brisbane Office 1: GPON available. Brisbane Office 2: GPON available. All 5 sites pass feasibility with confirmed access technology and port capacity.
SLA & Pricing Configuration
CPQ → Pricing EngineThe AM selects Gold SLA tier (99.95% availability, 4-hour restore) for all 5 sites. The system applies the negotiated enterprise rate card: $1,800/site/month (vs. list price $2,200/site/month). Total contract value: $324,000 (36 months x 5 sites x $1,800).
Solution Design & Rollout Plan
Enterprise Sales ConsoleThe AM configures a phased rollout: Pilot (Melbourne HQ, target T+14 days), Wave 1 (2x Sydney sites, T+30 days), Wave 2 (2x Brisbane sites, T+45 days). Each wave will trigger separate service orders. The pilot phase acts as a gate — subsequent waves only proceed after pilot success.
Enterprise Approval Workflow
Approval Workflow EngineThe quote is submitted for internal approval through a three-stage workflow: (1) Technical review — network capacity confirmed at all 5 sites, (2) Commercial review — discount authorisation for negotiated rate card approved, (3) Customer sign-off — GlobalTech procurement reviews and accepts the proposal. All three stages complete successfully.
Order Submitted to COM
CPQ → COM (TMF622)CPQ submits a TMF622 POST /productOrder request to COM containing 5 Product Order Items (one per site), each referencing PO-EFCG-01 with site-specific address, feasibility token, and SLA selection. The phased rollout schedule is captured as order-level metadata.
Step 2: COM Validation and Per-Site Decomposition
COM Processing Steps
Contract Validation
COM → Contract ManagementCOM validates: enterprise rate card is approved and current, contract term matches (36 months), Gold SLA tier is available at all 5 sites, and total contract value ($324,000) matches the approved quote. No discrepancies found.
Credit Check
COM → Enterprise Credit SystemCOM queries the enterprise credit system. GlobalTech Solutions has an existing account in good standing with a $500K credit limit. Combined order value ($324K over 36 months) is within the approved limit. No deposit or additional guarantees required.
Per-Site Feasibility Revalidation
COM → Address QualificationCOM re-validates feasibility for each of the 5 sites (feasibility tokens may expire between quote and order submission). All 5 sites confirmed available. OLT port capacity and P2P Ethernet handoff capacity reserved at each exchange.
Product-to-CFS Decomposition (Per Site)
COM → Service CatalogCOM reads Product Specification PS-ESA-01 and determines the required CFS types for each site: CFS:Fibre-Access (mandatory — symmetric bearer), CFS:Enterprise-QoS (mandatory for Gold SLA tier), CFS:CPE-Management (mandatory — managed Cisco ISR 4431 router). This produces 3 CFS items per site, totalling 15 service order items across all 5 sites.
Phased Service Order Creation
COM → SOM (TMF641)COM creates 3 separate TMF641 Service Orders aligned to the rollout plan: SO-PILOT (Melbourne HQ — 1 site, 3 SOIs), SO-WAVE1 (2 Sydney sites — 2 sites, 6 SOIs), SO-WAVE2 (2 Brisbane sites — 2 sites, 6 SOIs). The pilot service order is submitted to SOM immediately. Wave 1 and Wave 2 are held in "scheduled" state pending pilot completion.
COM Decomposition: Service Order Items (Pilot — Melbourne HQ)
| SOI ID | CFS Type | Action | Key Characteristics |
|---|---|---|---|
| SOI-001 | CFS:Fibre-Access | add | speed=500M-sym, technology=GPON, oltArea=SOUTH-03 |
| SOI-002 | CFS:Enterprise-QoS | add | slaTier=Gold, availability=99.95%, restore=4hr |
| SOI-003 | CFS:CPE-Management | add | model=ISR-4431, config=enterprise-fibre, mgmt=fullManaged |
Step 3: SOM Orchestration and CFS → RFS Decomposition
SOM receives SO-PILOT and begins orchestration for the Melbourne HQ site. Its first task is to decompose each CFS-level service order item into RFS-level items using the service catalog. The pilot phase is processed first — Wave 1 and Wave 2 remain paused until the pilot completes successfully.
CFS:Fibre-Access with technology=GPON and speed=500M-sym decomposes into three RFS items:
| ROI ID | RFS Type | Action | Key Characteristics |
|---|---|---|---|
| ROI-001 | RFS:GPON-Bearer | add | bearerSpeed=1G, oltArea=SOUTH-03 |
| ROI-002 | RFS:VLAN-Service | add | vlanType=c-tag, serviceType=enterprise |
| ROI-003 | RFS:IP-Profile | add | ipVersion=dualStack, pool=SOUTH-ENT |
SOM Orchestration Plan
Orchestration Plan: Dependencies (Pilot Site)
| Task | Depends On | Reason |
|---|---|---|
| ROI-001: GPON Bearer | (none) | No prerequisites — bearer provisioning starts immediately |
| ROI-006: CE Router Config | (none) | Router can be pre-staged and shipped independently |
| ROI-002: VLAN Service | ROI-001 | VLAN is configured on the provisioned bearer |
| ROI-003: IP Profile | ROI-002 | IP addressing is bound to the VLAN |
| ROI-004: QoS Policy | ROI-001 | QoS policy is applied on the bearer connection |
| ROI-005: SLA Monitoring | ROI-004 | SLA probes measure QoS-policed traffic — requires active QoS |
Step 4: ROM Resource Allocation and Activation
ROM Processing: Network-Side (Pilot — Melbourne HQ)
ROI-001: Allocate GPON Bearer
ROM → Resource Inventory → OLT/EMS (NETCONF)ROM queries Resource Inventory for an available OLT port in the SOUTH-03 serving area. Selected: OLT-SOUTH-03, Line Card 2, Port 8. ROM reserves the port and sends GPON activation commands to the OLT/EMS via NETCONF adapter. OLT confirms bearer is UP.
ROI-002: Assign Enterprise VLAN
ROM → VLAN Manager → OLT/BNG (NETCONF)ROM allocates VLAN 2108 from the enterprise VLAN pool (separate from residential pools). VLAN is configured on the OLT uplink and BNG-facing interface via NETCONF. Enterprise VLAN tagging confirmed on both ends.
ROI-003: Configure IP Profile
ROM → IPAM (REST) → DHCP/RADIUSROM requests a /29 subnet from IPAM for enterprise use: 10.88.12.0/29 allocated (6 usable addresses). DHCP relay and RADIUS profiles updated with enterprise binding. Static gateway assignment configured for the CE router interface.
ROI-004: Apply Enterprise QoS
ROM → BNG (NETCONF)ROM selects QoS policy template BW-500-500-GOLD-ENT (500 Mbps symmetric, enterprise Gold class with committed information rate). Policy applied to BNG via NETCONF. CIR enforced — unlike residential best-effort, this guarantees 500 Mbps in both directions.
ROM Processing: CPE & Monitoring (Pilot — Melbourne HQ)
ROI-006: CE Router Configuration
ROM → ZTP Server → LogisticsROM pre-stages a Cisco ISR 4431 (S/N: FDO2340567). Day-1 configuration is prepared and pushed via ZTP: WAN/LAN interfaces, OSPF/BGP routing towards PE, management ACLs, SNMP community strings, NETCONF agent enablement. Router is shipped to Melbourne HQ and boots against the ZTP server to download its configuration automatically.
ROI-005: SLA Monitoring Activation
ROM → NMS/APM (SNMP)ROM registers the circuit in the NMS/APM platform. TWAMP (Two-Way Active Measurement Protocol) probes are configured between the PE router and CE router. Alert thresholds are set: availability <99.95%, latency >10ms, packet loss >0.01%. NMS confirms monitoring is active and baseline measurements begin.
Complete Resource Allocation Summary (Pilot Site)
| RFS | Resource | Type | Value |
|---|---|---|---|
| GPON-Bearer | OLT Port | Physical | OLT-SOUTH-03 LC2 Port 8 |
| VLAN-Service | VLAN ID | Logical | VLAN 2108 |
| IP-Profile | IPv4 Subnet | Logical | 10.88.12.0/29 |
| QoS-Policy | Bandwidth Policy | Logical | BW-500-500-GOLD-ENT |
| SLA-Monitoring | TWAMP Probe | Logical | Probe-ENT-1102-MELB |
| CE-Router | CPE Device | Physical | ISR-4431 S/N: FDO2340567 |
Step 5: Completion Cascade and Phased Rollout
Completion Cascade (Pilot Phase)
ROM Completes Pilot ROIs
ROM → SOM (TMF652 Events)All 6 ROIs for the Melbourne HQ site complete successfully. ROM publishes a ResourceOrderItemStateChangeEvent for each completed item. Network-side ROIs (bearer, VLAN, IP, QoS) complete within hours; CPE and SLA monitoring complete over several days as the router is shipped and installed.
SOM Completes Pilot SOIs
SOMSOM evaluates its orchestration plan as each ROI completes. When all ROIs for a given CFS are done, SOM marks the corresponding SOI as complete: SOI-001 (Fibre Access) — complete when bearer, VLAN, and IP are done. SOI-002 (Enterprise QoS) — complete when QoS policy and SLA monitoring are done. SOI-003 (CPE Management) — complete when CE router config is done.
SOM Updates Service Inventory
SOM → TMF638SOM creates 3 service instances in Service Inventory (TMF638): SI-FA-ENT-1102-MELB (Fibre Access, Active), SI-QOS-ENT-1102-MELB (Enterprise QoS, Active), SI-CPE-ENT-1102-MELB (CPE Management, Active). Each instance carries the provisioned characteristic values and references the allocated resources.
SOM Completes Pilot Service Order
SOM → COM (TMF641 Events)With all 3 SOIs complete, SOM marks SO-PILOT as "completed" and publishes ServiceOrderStateChangeEvent to COM. This event also triggers the gate condition — SOM signals that Wave 1 (SO-WAVE1) can now be submitted.
COM Updates Product Inventory
COM → TMF637 → BillingCOM receives the pilot completion event. Product Instance PI-EFCG-1102-MELB is created in Product Inventory (TMF637) with state "Active". Billing is activated for the Melbourne HQ site at $1,800/month. The remaining 4 sites will be billed individually as each completes.
Wave 1 & Wave 2 Execute
COM → SOM → ROMWave 1 (2 Sydney sites) starts immediately after pilot completion. COM submits SO-WAVE1 to SOM. Each Sydney site follows the same 6-ROI orchestration pattern (with P2P Ethernet instead of GPON for the bearer). Wave 2 (2 Brisbane sites) starts after Wave 1 completes. Total rollout target: approximately 45 days for all 5 sites.
Order Timeline (Pilot Phase)
End-to-End Timeline (Pilot — Melbourne HQ)
| Time | Event | System | State |
|---|---|---|---|
| T+0 | AM submits enterprise order | Sales Console → COM | PO: acknowledged |
| T+1 hr | Enterprise approval completes | Approval Workflow | PO: approved |
| T+2 hr | COM validates and decomposes | COM → SOM | PO: inProgress / SO-PILOT: acknowledged |
| T+3 hr | SOM builds per-site orchestration plan | SOM | SO-PILOT: inProgress |
| T+4 hr | ROM begins network-side activation | SOM → ROM | RO: inProgress |
| T+5 hr | OLT port activated (ROI-001) | ROM → OLT | ROI-001: completed |
| T+6 hr | VLAN + IP configured (ROI-002/003) | ROM → BNG | ROI-002/003: completed |
| T+7 hr | Enterprise QoS applied (ROI-004) | ROM → BNG | ROI-004: completed |
| T+3 days | CE router shipped and staged | ROM → Logistics | ROI-006: in transit |
| T+5 days | CE router ZTP completes | ROM → ZTP | ROI-006: completed |
| T+5 days | SLA monitoring activated (ROI-005) | ROM → NMS | ROI-005: completed |
| T+5 days | Pilot phase complete | SOM → COM | SO-PILOT: completed |
| T+5 days | Wave 1 (Sydney) triggered | COM → SOM | SO-WAVE1: acknowledged |
| T+20 days | Wave 1 complete (2 Sydney sites) | SOM → COM | SO-WAVE1: completed |
| T+35 days | Wave 2 complete (2 Brisbane sites) | SOM → COM | SO-WAVE2: completed |
| T+35 days | Full order complete — 5 sites active | COM | PO: completed |
What-If Scenarios
Enterprise orders introduce failure modes and change scenarios that do not exist in B2C. Here are three common B2B-specific scenarios and how the order management system handles them:
Scenario: Brisbane Office 2 (POI-005) fails feasibility revalidation — no OLT capacity at the serving exchange.
- COM marks POI-005 as "held" with reason: "resource exhaustion — no OLT capacity at serving exchange"
- The remaining 4 sites proceed normally — COM does not block the entire order for one site failure
- SO-PILOT (Melbourne HQ) and SO-WAVE1 (2 Sydney sites) execute as planned
- SO-WAVE2 is split: Brisbane Office 1 proceeds; Brisbane Office 2 is held
- Network planning is engaged for OLT capacity expansion at the Brisbane exchange
- When capacity becomes available, Brisbane Office 2 is added to a new Wave 3 (SO-WAVE3)
- GlobalTech receives 4 of 5 sites on schedule — partial activation model preserves business value
- Billing activates per site as each completes: 4 sites billing at $1,800/month while the 5th is pending
Complete Entity Map
Here is the complete set of entities created across all systems for this enterprise order. The scale difference compared to B2C is striking — a single B2C broadband order creates roughly 12 entities; this B2B order creates over 60:
Entities Created by This Order (All 5 Sites)
| Entity | System of Record | System of Engagement | System of Reference | Notes |
|---|---|---|---|---|
| Product Order PO-2024-01203 | COM | Sales Console | — | 5 POIs (1 per site) |
| Service Order SO-PILOT | SOM | COM | — | 3 SOIs (Melbourne HQ) |
| Service Order SO-WAVE1 | SOM | COM | — | 6 SOIs (2x Sydney) |
| Service Order SO-WAVE2 | SOM | COM | — | 6 SOIs (2x Brisbane) |
| Resource Orders (5) | ROM | SOM | — | 6 ROIs per site (30 total) |
| Product Instances (5) | Product Inventory | COM | — | 1 per site, Enterprise Fibre Connect Gold |
| Service Instances (15) | Service Inventory | SOM | — | 3 per site (Fibre + QoS + CPE) |
| Resource: OLT Ports (5) | Resource Inventory | ROM | — | Physical — 1 per site |
| Resource: VLANs (5) | Resource Inventory | ROM | — | Logical — enterprise VLAN pool |
| Resource: IP Subnets (5) | Resource Inventory | ROM | — | Logical — /29 per site |
| Resource: CE Routers (5) | Resource Inventory | ROM | — | Physical — ISR 4431 per site |
| Resource: SLA Probes (5) | Resource Inventory | ROM | — | Logical — TWAMP per site |
Section 3.7 Key Takeaways
- A single enterprise order for 5 sites generates 3 service orders (phased), 5 resource orders, 15 service order items, and 30 resource order items
- B2B orders require per-site feasibility, enterprise approval workflows, and SLA selection — none of which exist in B2C
- Phased rollout means COM creates multiple service orders (pilot, wave 1, wave 2) with gate conditions between phases
- The pilot phase acts as a gate — Wave 1 only starts after pilot completes successfully, including SLA validation
- Per-site orchestration plans are independent — a failure at one site does not block other sites in the same wave
- Enterprise QoS uses committed information rate (CIR) policies, not best-effort residential profiles
- SLA monitoring is activated from Day 1 as part of the order — it is not a separate post-activation process
- CE router provisioning via ZTP follows the same adapter pattern as residential CPE via TR-069, but with richer configuration
- Mid-rollout changes require different handling for active sites (modify order) vs pending sites (order amendment)
- The entity count (30 ROIs across 5 sites) shows why B2B order management is significantly more complex than B2C