Why "TM Forum-Aligned" Is the Difference Between an AI Demo and an ISP Deployment
Every ISP procurement team asks the same question about any new network automation tool: is it TM Forum-aligned? The answer determines whether the tool fits into their existing operational architecture or requires them to build bridges between incompatible systems.
Most companies rushing to announce AI appliances for ISPs will not have a good answer to this question. They're building general-purpose agentic frameworks and calling them telecom solutions. TM Forum Autonomous Networks standards exist precisely because that label is harder to earn than it looks.
I spent years at ETI Software Solutions building software that had to integrate into ISP operational stacks. I know what TM Forum alignment actually means — not as architecture jargon, but as a procurement requirement that determines whether an ISP can deploy your product in six weeks or spend a year building custom integrations.
TM FORUM IS NOT BUREAUCRATIC OVERHEAD
The TeleManagement Forum maintains the open standards governing telecom OSS/BSS interoperability. Its Open API suite — over 60 standardized REST APIs — defines how systems across the telecom operational stack talk to each other: provisioning, billing, trouble ticketing, service management, network inventory, fault management.
The Autonomous Networks initiative, launched in 2019 and updated through the IG1230 specification series, defines a five-level framework for network automation maturity — from fully manual operations through fully autonomous, self-evolving networks. It provides the taxonomy, the interface standards, and the assessment methodology that ISPs use to evaluate and communicate automation capabilities.
This matters for procurement for a simple reason: when an ISP's OSS/BSS team evaluates a new automation tool, they think in TM Forum terms. "Does this address TM Forum AN Level 3 requirements for fault management?" is a precise question. "Does this do AI for network operations?" is not.
THE FIVE AUTONOMY LEVELS
Level 0: All manual. Human does everything.
Level 1: Assisted. System provides data; human decides and acts.
Level 2: Partial automation. System automates specific tasks on request.
Level 3: Conditional autonomy. System handles defined scenarios autonomously; escalates others.
Level 4: High autonomy. System self-optimizes within defined boundaries.
Level 5: Full autonomy. System self-evolves; no human required.
| Level | Name | Capability | Human Role |
|---|---|---|---|
| 0 | Manual | All operations manual | Full human execution |
| 1 | Assisted | System provides data | Human decides and acts |
| 2 | Partial | Automates specific tasks on request | Human initiates |
| 3 | Conditional ← XSI Target | Handles defined scenarios autonomously | Human handles exceptions |
| 4 | High | Self-optimizes within boundaries | Human sets policy |
| 5 | Full | Self-evolves | Human sets business goals |
Most Tier 2/3 ISPs today operate at Level 1 or Level 2 for most workflows. Their OSS/BSS systems provide data and some task automation, but operators make most decisions and execute most actions manually. The practical target for near-term AI deployment is Level 3: conditional autonomy for defined scenarios, with human escalation for exceptions.
That's exactly what XSI LodeStone's Shadow Mode and graduated autonomy architecture is designed to deliver.
WHY THE STANDARDS ALIGNMENT MATTERS FOR XSI LODESTONE
XSI LodeStone's Telecom Skill Library is built on TM Forum Open API standards — specifically the fault management (TMF642), service management (TMF622), and resource management (TMF639) specifications. This means two things in practice:
First, XSI LodeStone can integrate with any OSS/BSS platform that implements TM Forum Open APIs — which includes the major Tier 2/3 ISP vendors. ETI's Intelegrate platform, the primary integration in our launch configuration, is TM Forum-aligned. The agent framework speaks the same language as the existing operational stack.
Second, when XSI LodeStone executes a fault management action, it does so through the defined TM Forum fault management interfaces. The audit trail it generates uses TM Forum-standard alarm and trouble ticket schemas. The data it produces is compatible with the operator's existing reporting and analytics infrastructure. No translation layer required. No custom integration project.
WHAT LEVEL 3 ACTUALLY REQUIRES
Achieving genuine TM Forum AN Level 3 requires more than a capable language model. It requires:
— Accurate, current network topology data (from GIS and network inventory systems) — Real-time alarm correlation (mapping raw device alarms to service-affecting faults) — Vendor-specific remediation knowledge (the actual CLI sequences for Nokia, Calix, and Adtran equipment) — Exception handling logic (when to escalate rather than act autonomously)
This is not a problem you solve with prompt engineering. It is a data integration problem requiring deep vendor knowledge, built through months of engineering alongside operators and equipment vendors.
I spent years at ETI working on exactly this. ETI's operational stacks are running in hundreds of ISP networks. The fault management workflows, the equipment CLI sequences, the decision logic for escalation — all of this has been built and refined over years of production deployment.
The Telecom Skill Library in XSI LodeStone encodes this — not as general AI capability but as a production-grade implementation of Level 3 fault management automation for the specific equipment and workflows that Tier 2/3 ISPs actually operate.
That is what "TM Forum-aligned" means in practice. Not a label. A specification-level implementation that fits into existing operational architectures without requiring ISPs to translate between incompatible systems. No custom integrations. No consultant engagement. Deploy and it works.
THE MOAT IN STANDARDS ALIGNMENT
Here's what competitors with capital cannot replicate quickly: the institutional knowledge embedded in TM Forum-aligned fault management. You can hire engineers. You can license Nokia CLI documentation. You can build an agent framework. What you cannot do in 12 months is establish the working relationship with ETI that makes this partnership productive, or the familiarity with real ISP operational patterns that makes the Skill Library actually useful rather than theoretically sound.
A competitor starting now faces a choice: build the integrations from scratch (18-month project) or integrate with TM Forum-aligned platforms that already exist (3-month project). That is the timing moat that standards alignment creates.
Every new deployment using XSI LodeStone adds operational intelligence to the Telecom Skill Library. Each new fault type encountered in production, each new equipment configuration handled, each edge case resolved in a real network environment improves the platform for future deployments. The first deployment is backed by 30 years of ETI domain knowledge. The tenth deployment is backed by that knowledge plus the production experience of nine live deployments.
This is how you build sustainable advantage in a vertical market.
Rhyan J. Neble | Founder & CEO, Extended Systems Intelligence | rneble@xtendedsystems.com | xsilodestone.ai
Q&A with Rhyan
Extended questions from discussions — answered in full.
TM Forum Open APIs are the language that ISP OSS/BSS teams speak. When evaluating new tools, operators think in TM Forum terms: 'Does this address Level 3 requirements for fault management?' A product that is TM Forum-aligned can integrate with existing operational stacks without custom bridge development. Misalignment means a year-long integration project.
Level 0: All manual. Level 1: Assisted (system provides data; human decides). Level 2: Partial automation (system automates tasks on request). Level 3: Conditional autonomy (system handles defined scenarios; escalates others). Level 4: High autonomy (self-optimizes within boundaries). Level 5: Full autonomy (self-evolves; no human required). Most Tier 2/3 ISPs today operate at Level 1-2; the practical near-term target is Level 3.
Accurate, current network topology (from GIS and inventory), real-time alarm correlation (mapping raw device alarms to service faults), vendor-specific remediation knowledge (actual CLI sequences for specific equipment), and exception handling logic (when to escalate). This is a data integration problem requiring deep vendor knowledge, built through months of engineering alongside operators and equipment vendors—not something solved by prompt engineering.
A competitor faces a choice: build integrations from scratch (18-month project) or integrate with TM Forum-aligned platforms that already exist (3-month project). The institutional knowledge embedded in TM Forum-aligned fault management cannot be replicated quickly. Each deployment adds operational intelligence to the platform, making it increasingly valuable for future deployments.
Common Questions
Search-ready answers to the questions we hear most often.
TM Forum maintains open standards governing telecom OSS/BSS interoperability. Its Open API suite defines how systems across the telecom stack interact for provisioning, billing, service management, inventory, and fault management. ISP procurement teams think in TM Forum terms, making alignment essential for integration into existing operational stacks without expensive custom development.
The Autonomous Networks initiative defines five maturity levels for network automation: Level 0 (manual), Level 1 (assisted), Level 2 (partial automation), Level 3 (conditional autonomy), Level 4 (high autonomy), Level 5 (full autonomy). Most Tier 2/3 ISPs operate at Level 1-2; the practical near-term target for AI deployment is Level 3 (autonomous for defined scenarios, escalates others).
An ISP with a TM Forum-aligned solution faces a straightforward integration: the agent speaks the same language as existing systems, uses defined interfaces, and produces compatible audit trails. A non-aligned product requires ISPs to translate between incompatible systems—a project that stretches from 6 weeks to a year and requires consultant engagement.
Beyond a capable language model, Level 3 requires accurate network topology from GIS and inventory systems, real-time alarm correlation mapping raw device alarms to service faults, vendor-specific remediation knowledge (actual CLI sequences for Nokia, Calix, Adtran), and exception handling logic. This requires months of data integration engineering, not prompt engineering.
The institutional knowledge embedded in TM Forum-aligned fault management—accumulated over years with hundreds of ISP deployments—is not replicable quickly. Competitors can hire engineers or license documentation, but cannot establish operator relationships or familiarity with real ISP patterns in 12 months. The working relationship between technical teams creates the actual competitive advantage.
Every deployment adds operational intelligence to the platform. Each new fault type encountered, each equipment configuration handled, each edge case resolved in production strengthens the Skill Library. The first deployment is backed by 30 years of partner domain knowledge; the tenth is backed by that plus production experience of nine deployments. This compound advantage is how moats form in vertical markets.