Skip to main content
BSS/OSS Academy
L2C — during fulfilment

Lead-to-Cash

The runtime phase that faces the customer. Lead-to-Cash runs once per order — qualify, quote, capture, decompose, activate, bill. It consumes what Concept-to-Market published and produces the installed base: the inventory records that state what this customer actually has.

Clock
Runtime
Unit of work
Per order
Cadence
Minutes to days
Produces
An installed base

The constraint on Trouble-to-Resolve

Trouble-to-Resolve can only assure what Lead-to-Cash instantiated. A service with no inventory record is a service nobody can correlate a fault to.

Decomposition is where the phase either works or does not. A product order becomes service orders, which become resource orders, and each hop is driven by catalog relationships defined at design time. Where those relationships are missing, the hop is closed by hand or hard-coded in the orchestrator, and the resulting instance has no lineage back to a specification.

L2C is where commercial truth and technical truth first diverge. Billing starts from the product order; the network knows only what was activated. If the two are never reconciled, the divergence dates from the day the order completed and grows quietly from there.

Modules in this phase

Foundations and the reference modules — TMF Open APIs, frameworks, architecture patterns and the vendor landscape — apply across all three phases, so they are not listed under any one of them.

Hands downstream

L2C hands Trouble-to-Resolve an installed base: product, service and resource inventory records that a fault can be correlated against.

Next: T2R — Trouble-to-Resolve