Hi TM Forum Community,
I'm exploring a Canonical Automation Ontology as a possible way to normalise and compare automation use cases across operators.
The current version has been developed using two reference sets:
40 use cases from ITU-T Use cases for Autonomous Networks (Y.Sup71)
28 use cases from ETSI ENI 001 (Experiential Networked Intelligence)
The ontology currently uses 19 attributes covering aspects such as:
Domain
Business Problem
Automation Goal
Autonomous Behaviour
Human-in-the-loop
Telemetry Inputs
Execution Actions
Target AN Level
Evidence
Confidence
The intention is to create a reference use-case catalog that can help CSPs describe automation initiatives using a more consistent vocabulary.
I have also developed a Unified 40×28 Crosswalk Matrix between the ITU-T and ETSI reference use cases.
The purpose of the crosswalk is not to claim that an ITU-T use case and an ETSI use case are semantically equivalent. Rather, it is intended as an analytical reference tool that identifies groups of potentially related standard use cases and their relative correspondence.
This could potentially support:
- Normalising operator automation use cases against a common reference model.
- AN roadmap analysis by domain, autonomous behaviour, AN level and business objective.
- Gap analysis against ITU-T / ETSI reference use cases and TM Forum Autonomous Networks maturity models.
- Identifying reference use-case neighbourhoods that may be useful when analysing an operator's less clearly defined automation proposals.
At this stage, I am not proposing this as a new standard. I am looking for industry feedback to determine whether the approach is useful, what may be missing, and whether similar work already exists.
I would particularly appreciate feedback on:
1. Ontology design
Is a 19-attribute model practical for an industry-wide reference catalog, or is it too detailed / not detailed enough?
2. Missing dimensions
Are there attributes or analytical axes that you consider essential for describing automation use cases that are currently missing?
3. Relationship to existing TM Forum work
How could such an ontology best complement existing TM Forum Autonomous Networks models, frameworks or artifacts rather than duplicate them?
4. Existing work / prior art
Has anyone already published a catalog, ontology or framework that addresses a similar problem - particularly one that normalises operator automation use cases against ITU-T / ETSI references and supports Autonomous Networks roadmap analysis?
If so, I would greatly appreciate any references or pointers.
I'm particularly interested in practical industry experience, including examples where teams have struggled to maintain a consistent vocabulary across automation initiatives.
I can share a sample catalog (5–10 use cases), the 19-attribute schema, and a high-level view of the 40×28 crosswalk for anyone interested in reviewing the approach.
I would be very interested in constructive criticism, alternative approaches, and examples of existing work that I may have missed.
Best regards,
#DigitalTransformationMaturity#General------------------------------
Ngoc Linh Nguyen
Vietnam Posts and Telecommunications Group (VNPT)
------------------------------