BSS/OSS Academy
3.718 min read

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.

COM — Commercial Order ManagementProduct Order → CFS decompositionProduct OrderTMF622SOM — Service Order ManagementCFS→RFS decomposition, dependency sequencing, orchestration planCFS:Fibre-Access500M symmetricCFS:Enterprise-QoSGold SLACFS:CPE-MgmtCE routerROM — Resource Order Management6 Resource Order Items dispatched to activation adaptersResource Order (6 ROIs)TMF652Activation AdaptersProtocol-specific southbound adaptersNETCONFOLT/EMS adapterNETCONF/CLIBNG adapterRESTIPAM adapterNETCONFQoS adapterTR-069/ZTPACS adapterSNMPSLA adapterEnterprise Fixed Network ElementsOLT / EMSFibre accessBNGSubscriber sessionIPAMAddress mgmtEnterprise QoSPolicy engineACS / ZTPCPE configSLA ProbeMonitoringTMF641 Service OrderTMF652 Resource OrderExecution: Per-site — OLT → BNG + IPAM → QoS → ACS/ZTP → SLA probe active

Fixed B2B activation — SOM orchestrates through ROM to provision OLT/EMS, BNG, IPAM, Enterprise QoS, ACS, and SLA probes

Fixed B2B activation — SOM orchestrates through ROM to provision OLT/EMS, BNG, IPAM, Enterprise QoS, ACS/ZTP, and SLA probes per site
B2B vs B2C
Compare this with the broadband B2C example in Section 3.6. In B2C, a single customer orders a single product at a single address — one product order item, one service order, one resource order. In B2B, GlobalTech orders the same product class across 5 sites, requiring: per-site feasibility checks (each site may use different access technology), enterprise approval workflows (technical, commercial, and customer sign-off), SLA selection and enforcement (Gold tier with contractual availability guarantees), phased rollout with gate conditions between waves, and 30 resource order items instead of 7. The catalog decomposition logic is the same — but the orchestration complexity scales with site count and SLA requirements.

The Scenario

Customer Scenario
Customer: GlobalTech Solutions Pty Ltd (mid-sized enterprise, ~200 employees). Product: "Enterprise Fibre Connect Gold" — 500 Mbps symmetric, Gold SLA (99.95% availability, 4-hour restore). Sites: 5 branches — Melbourne HQ (pilot), 2x Sydney offices, 2x Brisbane offices. Technology: GPON (Melbourne HQ, Brisbane) / P2P Ethernet (Sydney). Contract: 36 months, $1,800/site/month (negotiated enterprise rate card). Channel: Enterprise sales console (account manager assisted). Rollout: Phased — Pilot (Melbourne HQ) → Wave 1 (Sydney) → Wave 2 (Brisbane).

Order Summary

AttributeValue
CustomerGlobalTech Solutions Pty Ltd (CUST-ENT-1102)
AccountACC-ENT-3384 (enterprise account)
Product OfferingEnterprise Fibre Connect Gold (PO-EFCG-01)
Product SpecificationEnterprise Symmetric Access (PS-ESA-01)
Sites5 branches — Melbourne HQ, 2x Sydney, 2x Brisbane
Access TechnologyGPON / P2P Ethernet (varies per site)
Download / Upload500 Mbps symmetric
SLA TierGold — 99.95% availability, 4-hour restore
CPECisco ISR 4431 managed router (per site)
Contract Term36 months
Monthly Price$1,800/site ($9,000 total monthly)
RolloutPhased: Pilot → Wave 1 → Wave 2

Step 1: Enterprise CPQ, Feasibility & Approval

Enterprise Sales & CPQ Processing

1
Account Manager Prepares Solution
Enterprise Sales Console

The 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.

2
Per-Site Feasibility Check
CPQ → Address Qualification

CPQ 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.

3
SLA & Pricing Configuration
CPQ → Pricing Engine

The 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).

4
Solution Design & Rollout Plan
Enterprise Sales Console

The 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.

5
Enterprise Approval Workflow
Approval Workflow Engine

The 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.

6
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.

TMF622 — Enterprise Product Order Created
COM assigns order ID: PO-2024-01203. State: "acknowledged". The Product Order contains 5 Product Order Items: POI-001 (Melbourne HQ — pilot), POI-002 (Sydney Office 1 — wave 1), POI-003 (Sydney Office 2 — wave 1), POI-004 (Brisbane Office 1 — wave 2), POI-005 (Brisbane Office 2 — wave 2). Each POI has action "add", references PO-EFCG-01, and carries site-specific characteristics including address, feasibility token, access technology, and SLA tier (Gold).

Step 2: COM Validation and Per-Site Decomposition

COM Processing Steps

1
Contract Validation
COM → Contract Management

COM 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.

2
Credit Check
COM → Enterprise Credit System

COM 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.

3
Per-Site Feasibility Revalidation
COM → Address Qualification

COM 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.

4
Product-to-CFS Decomposition (Per Site)
COM → Service Catalog

COM 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.

5
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 IDCFS TypeActionKey Characteristics
SOI-001CFS:Fibre-Accessaddspeed=500M-sym, technology=GPON, oltArea=SOUTH-03
SOI-002CFS:Enterprise-QoSaddslaTier=Gold, availability=99.95%, restore=4hr
SOI-003CFS:CPE-Managementaddmodel=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 IDRFS TypeActionKey Characteristics
ROI-001RFS:GPON-BeareraddbearerSpeed=1G, oltArea=SOUTH-03
ROI-002RFS:VLAN-ServiceaddvlanType=c-tag, serviceType=enterprise
ROI-003RFS:IP-ProfileaddipVersion=dualStack, pool=SOUTH-ENT

SOM Orchestration Plan

Orchestration Plan: Dependencies (Pilot Site)

TaskDepends OnReason
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 ServiceROI-001VLAN is configured on the provisioned bearer
ROI-003: IP ProfileROI-002IP addressing is bound to the VLAN
ROI-004: QoS PolicyROI-001QoS policy is applied on the bearer connection
ROI-005: SLA MonitoringROI-004SLA probes measure QoS-policed traffic — requires active QoS
Per-Site Independence
Each site's orchestration plan is independent. SOM can execute the pilot site's 6 ROIs without waiting for Wave 1 or Wave 2. If the pilot fails, Wave 1 and Wave 2 remain paused — the pilot acts as a gate condition. Within the same wave, however, individual sites are also independent: if one Sydney site fails during Wave 1, the other Sydney site can still complete.

Step 4: ROM Resource Allocation and Activation

ROM Processing: Network-Side (Pilot — Melbourne HQ)

1
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.

2
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.

3
ROI-003: Configure IP Profile
ROM → IPAM (REST) → DHCP/RADIUS

ROM 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.

4
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)

1
ROI-006: CE Router Configuration
ROM → ZTP Server → Logistics

ROM 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.

2
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)

RFSResourceTypeValue
GPON-BearerOLT PortPhysicalOLT-SOUTH-03 LC2 Port 8
VLAN-ServiceVLAN IDLogicalVLAN 2108
IP-ProfileIPv4 SubnetLogical10.88.12.0/29
QoS-PolicyBandwidth PolicyLogicalBW-500-500-GOLD-ENT
SLA-MonitoringTWAMP ProbeLogicalProbe-ENT-1102-MELB
CE-RouterCPE DevicePhysicalISR-4431 S/N: FDO2340567

Step 5: Completion Cascade and Phased Rollout

Completion Cascade (Pilot Phase)

1
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.

2
SOM Completes Pilot SOIs
SOM

SOM 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.

3
SOM Updates Service Inventory
SOM → TMF638

SOM 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.

4
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.

5
COM Updates Product Inventory
COM → TMF637 → Billing

COM 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.

6
Wave 1 & Wave 2 Execute
COM → SOM → ROM

Wave 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)

TimeEventSystemState
T+0AM submits enterprise orderSales Console → COMPO: acknowledged
T+1 hrEnterprise approval completesApproval WorkflowPO: approved
T+2 hrCOM validates and decomposesCOM → SOMPO: inProgress / SO-PILOT: acknowledged
T+3 hrSOM builds per-site orchestration planSOMSO-PILOT: inProgress
T+4 hrROM begins network-side activationSOM → ROMRO: inProgress
T+5 hrOLT port activated (ROI-001)ROM → OLTROI-001: completed
T+6 hrVLAN + IP configured (ROI-002/003)ROM → BNGROI-002/003: completed
T+7 hrEnterprise QoS applied (ROI-004)ROM → BNGROI-004: completed
T+3 daysCE router shipped and stagedROM → LogisticsROI-006: in transit
T+5 daysCE router ZTP completesROM → ZTPROI-006: completed
T+5 daysSLA monitoring activated (ROI-005)ROM → NMSROI-005: completed
T+5 daysPilot phase completeSOM → COMSO-PILOT: completed
T+5 daysWave 1 (Sydney) triggeredCOM → SOMSO-WAVE1: acknowledged
T+20 daysWave 1 complete (2 Sydney sites)SOM → COMSO-WAVE1: completed
T+35 daysWave 2 complete (2 Brisbane sites)SOM → COMSO-WAVE2: completed
T+35 daysFull order complete — 5 sites activeCOMPO: 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.

  1. COM marks POI-005 as "held" with reason: "resource exhaustion — no OLT capacity at serving exchange"
  2. The remaining 4 sites proceed normally — COM does not block the entire order for one site failure
  3. SO-PILOT (Melbourne HQ) and SO-WAVE1 (2 Sydney sites) execute as planned
  4. SO-WAVE2 is split: Brisbane Office 1 proceeds; Brisbane Office 2 is held
  5. Network planning is engaged for OLT capacity expansion at the Brisbane exchange
  6. When capacity becomes available, Brisbane Office 2 is added to a new Wave 3 (SO-WAVE3)
  7. GlobalTech receives 4 of 5 sites on schedule — partial activation model preserves business value
  8. 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)

EntitySystem of RecordSystem of EngagementSystem of ReferenceNotes
Product Order PO-2024-01203COMSales Console5 POIs (1 per site)
Service Order SO-PILOTSOMCOM3 SOIs (Melbourne HQ)
Service Order SO-WAVE1SOMCOM6 SOIs (2x Sydney)
Service Order SO-WAVE2SOMCOM6 SOIs (2x Brisbane)
Resource Orders (5)ROMSOM6 ROIs per site (30 total)
Product Instances (5)Product InventoryCOM1 per site, Enterprise Fibre Connect Gold
Service Instances (15)Service InventorySOM3 per site (Fibre + QoS + CPE)
Resource: OLT Ports (5)Resource InventoryROMPhysical — 1 per site
Resource: VLANs (5)Resource InventoryROMLogical — enterprise VLAN pool
Resource: IP Subnets (5)Resource InventoryROMLogical — /29 per site
Resource: CE Routers (5)Resource InventoryROMPhysical — ISR 4431 per site
Resource: SLA Probes (5)Resource InventoryROMLogical — 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