TMF Telco Workbench
55 bundled local assets (54 with TMF API identifiers), curated packs that seed runnable scenarios and mappings, and ODA/TMF pre-validation. 54 assets have exact upstream Git-blob matches; 1 remains unmatched and every licence requires review.
Public TMF install/export is disabled. Source provenance does not clear redistribution or trademark approval, and zero assets are release-ready. Customer-provided specifications and synthetic examples remain available without implying endorsement, certification or partnership.
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.
- TMF622Product Ordering
- TMF641Service Ordering
Public TMF install/export is disabled. Source provenance does not clear redistribution or trademark approval, and zero assets are release-ready.
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.
- TMF629Customer Management
- TMF632Party Management
Public TMF install/export is disabled. Source provenance does not clear redistribution or trademark approval, and zero assets are release-ready.
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.
- TMF621Trouble Ticket
Public TMF install/export is disabled. Source provenance does not clear redistribution or trademark approval, and zero assets are release-ready.
Bundled-asset journey execution and evidence downloads are disabled on the public surface until the exact asset set has redistribution, licence, trademark and release approval. Customer-authorized specifications may still use the general APIMaster import and analysis workflows.
Scope: the selected rules implemented by this workbench. Results are preparation evidence only, not TM Forum certification, approval, or endorsement.
The local linter checks selected TMF630/ODA conventions: resource naming, mandatory id and href, @type polymorphism, state-machine fields, and the TMF error shape on 4xx/5xx.