Telecom Service Fulfilment Management

BC-2620 Level 1 Telecommunications 14 providers 30 API surfaces 1 rated strong or better

Service order capture, decomposition, provisioning, activation, acceptance, and customer-premises installation across consumer, enterprise, and wholesale services — anchored on eTOM Service Fulfilment and TM Forum Open APIs.

Telecom Service Fulfilment Management (BC-2620) is a level-1 business capability in the Telecommunications model. The catalog holds 30 API surface(s) from 14 provider(s) that can perform some part of it, 1 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Service Order Capture BC-2620.10

Multi-channel capture of service orders with feasibility and credit checks prior to submission.

7 providers, 12 API surfaces

Service Order Decomposition BC-2620.20

Decomposition of customer-facing orders into resource-facing work and sequencing of dependencies.

no catalog coverage

Service Provisioning BC-2620.30

Allocation of network resources and orchestration of configuration changes to instantiate services.

6 providers, 9 API surfaces

Service Activation BC-2620.40

Final turn-up of provisioned services and notification of customer and downstream systems.

2 providers, 2 API surfaces

Service Acceptance Testing BC-2620.50

End-to-end testing and baseline capture before formal handover of new services.

no catalog coverage

Customer Premises Installation Coordination BC-2620.60

Coordination of on-site installation of customer-premises equipment and associated activities.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Strong 1 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 2 Early or largely undocumented
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Telecom Service Fulfilment Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →