Telco vertical

TMF Telco Workbench

The TM Forum integration workbench — 56 bundled TMF Open API specs, curated packs that seed runnable scenarios and mappings, and ODA conformance pre-validation. The category-of-one wedge for CEE & EU telco integration teams.

Pro
offline
56 TMF specs, bundled
Every TM Forum Open API ships in the workbench — no horizontal competitor carries this asset.
one click
Packs that run
Install a pack and get importable APIs, mock scenarios, telco data packs and cross-API mappings — instantly.
CTK-mirroring
ODA conformance
Pre-validate any imported API against TMF630 / ODA conventions and get a readiness score with actionable findings.
TMF quick start
1
Install a pack
Seed APIs, scenarios, data packs and mappings in one click.
Pick a pack
2
Open in Explorer
Inspect the imported TMF endpoints and bundled specs.
Open Explorer
3
Run a mock
Replay the seeded scenarios against the mock contract.
Run scenarios
4
Check ODA readiness
Lint the imported API against TMF/ODA conventions.
View readiness
Curated TMF packs
0 of 3 installed
Pack · TMF622 + TMF641
Order Cascade
Pro

Product-to-service order fan-out: map a TMF622 Product Order onto a TMF641 Service Order, with happy-path, validation-error and downstream-failure scenarios on each main operation.

▸ Wire product ordering to service fulfilment in minutes, not sprints.
Bundled TMF specs
  • TMF622Product Ordering
  • TMF641Service Ordering
6
Scenarios
2
Data packs
2
Errors
6
Mappings
Est. time saved ~3 weeks
Pack · TMF629 + TMF632
Customer 360
Pro

Reconcile a TMF629 Customer against the underlying TMF632 Party (Individual / Organization). Ships realistic MSISDN / ICCID data packs and the identity-resolution mappings that hold a single customer view together.

▸ One reconciled customer view across CRM and party master data.
Bundled TMF specs
  • TMF629Customer Management
  • TMF632Party Management
4
Scenarios
3
Data packs
2
Errors
5
Mappings
Est. time saved ~2 weeks
Pack · TMF621
Assurance
Pro

A TMF621 Trouble Ticket assurance flow: an escalation scenario chain (raise → acknowledge → escalate → resolve) backed by an Error Library of TMF-shaped fault payloads for the common assurance failure modes.

▸ Ship a credible trouble-to-resolve assurance loop out of the box.
Bundled TMF specs
  • TMF621Trouble Ticket
5
Scenarios
1
Data packs
4
Errors
0
Mappings
Est. time saved ~1.5 weeks
Conformance
ODA Readiness
Pick an API to assess

The linter checks TMF630 / ODA conventions: resource naming, mandatory id & href, @type polymorphism, state-machine fields and the TMF error shape on 4xx/5xx.