Dial

Dial is a developer ecosystem for TMF Open Digital Architecture. It turns TMF specifications (TMFC components, eTOM processes, Open APIs, the SID model) into first-class developer constructs, so conformance is checked while you write code, not discovered in integration testing or certification.

The problem

ODA conformance is verified late today. Teams build against a specification document, then spend months in integration and certification finding where the implementation drifted from the standard. Gaps found late are expensive to close and slow to re-verify.

How Dial works

Dial makes the specification executable. ODA constructs are typed, spec-aware building blocks in your toolchain. Non-conformant architecture and API violations surface at build time. If a component doesn't conform, it doesn't build, and engineers get that feedback in seconds, in their own environment, instead of weeks later in a certification lab.

Who it's for

Communication service providers, BSS/OSS vendors, and system integrators delivering against TM Forum standards: the 186 organisations and 18 CSPs already committed to ODA.

Runtime

Dial targets JDK 25 and above from any vendor. Eliya is the recommended runtime for its operational-readiness defaults, but Dial never requires it. No vendor lock-in.

Status

Prototype complete. Design-partner preview now; public launch late 2026. Inquire at ping@asymm.systems.