EcoGenie for Telco
Telco standards, built in.
EcoGenie for Telco configures the platform with TM Forum frameworks, a telco metamodel and patterns from 21 years of delivery.
First industry solution
One platform, configured for each industry.
Four products, one platform.
Industry solutions
Configured per industry
EcoGenie for Telco
First industry solution
- TM Forum ODA
- eTOM
- SID
- TAM
- Open APIs
- Telco metamodel
Platform
Industry-agnostic
EcoGenie Platform
Industry-agnostic and AI-native, built on Open Group standards (TOGAF and the Digital Practitioner Body of Knowledge).
- Knowledge Graph
Every artefact is a node and every dependency a relationship, with its source and approval history.
- Ingests code, documents, tickets and transcripts
- Structured against Open Group standards
Example Trace one API to every journey it serves
- Orchestration
The Orchestrator assigns each task to a specialist genie or a person, passes context between steps and writes each outcome back to the graph.
- Specialist genies draft designs and test cases
- People review and sign off at set points
Example An idea reaches Definition of Ready in days
- Governance
A named person approves each change before it reaches the model, with a full audit trail.
- Standards set per industry solution
- Role-based access, customer data kept separate
Example A new interface checked against its layer’s standard
Industry frameworks
Mapped to the industry reference models.
TM Forum ODA
Functional domains and components
TM Forum Business Capability Map
Business capabilities across the telco value chain
TM Forum Open APIs
API realisation and conformance
TAM
Application framework functions
SID
Information and data ownership
eTOM
Business processes
Telco metamodel
The object types, attributes and relationships of a telco estate, set before the first mapping.
Delivery experience
Patterns from enterprise architecture delivery for major telcos.
Standards applied in EcoGenie for Telco
Changes checked against your industry’s standards.
Governance checks each change against the standard for its layer and records who approved it. EcoGenie for Telco sets those standards to the frameworks telcos already use.
| Layer | Standard |
|---|---|
| Strategy | Business Motivation Model |
| Capability | TM Forum Business Capability Map |
| Processes | TM Forum eTOM |
| Integrations | TM Forum Open APIs |
| Applications | TM Forum ODA and TAM |
| Genies | EcoGenie approval flow |
| Technology | Technical Reference Model |
- 1Change proposed
- 2Checked against the standard
- 3Reviewed by the owner
- 4Approved
- Written to the model
Human approval
A named person approves each change before it reaches the model.
Traceability
Every decision and artefact links to its source and its approver.
Access control
People and genies see only what their role allows.
Data separation
Each customer’s data is held separately and never shared across customers.
Standards checks
Each change is checked against the standard for its layer.
Example output
The estate, read against TM Forum ODA.
Each tile shows how well today’s estate realises a capability, so gaps and overlaps are visible at a glance.
Engagement Management
- Digital channels: Strongly realised
- Campaign & offer: Partially realised, gap
- Interaction management: Partially realised, gap
- Journey orchestration: Thin or absent
- Personalisation: Thin or absent
- Loyalty & rewards: Thin or absent
Party Management
- Customer 360: Partially realised, gap
- Party role & account: Strongly realised
- Agreement management: Partially realised, gap
- Privacy & consent: Thin or absent
- Partner onboarding: Partially realised, gap
- Identity & access: Strongly realised
Core Commerce
- Product catalogue: Strongly realised
- Product ordering: Strongly realised
- Quote & CPQ: Partially realised, gap
- Billing & invoicing: Strongly realised
- Payment & collection: Strongly realised
- Usage rating: Strongly realised
Production
- Service catalogue: Thin or absent
- Service orchestration: Partially realised, gap
- Resource inventory: Partially realised, gap
- Activation & config: Strongly realised
- Assurance & fault: Partially realised, gap
- Workforce management: Thin or absent
Intelligence & OSS
- Data warehouse: Partially realised, gap
- Analytics & reporting: Partially realised, gap
- AI decisioning: Thin or absent
- Revenue assurance: Partially realised, gap
- Fraud management: Partially realised, gap
- Data governance: Thin or absent
capabilities strongly realised
partially realised, gaps remain
thin or absent: build, buy or keep the legacy system
capabilities across 5 ODA domains
- Strongly realised
- Partially realised, gap
- Thin or absent
Example output
One canonical API layer.
The TM Forum Open API set, under its official TMF names, between channels, the commercial core and the retained estate.
Party Management
- TMF629Customer: Served by the converged commercial core
- TMF632Party: Served by the converged commercial core
- TMF669Party Role: Served by the converged commercial core
- TMF666Account: Served by the converged commercial core
- TMF651Agreement: Served by the converged commercial core
- TMF683Party Interaction: Partial, core plus a retained system
- TMF672User Roles & Permissions: Partial, core plus a retained system
Core Commerce Management
- TMF620Product Catalog: Served by the converged commercial core
- TMF622Product Ordering: Served by the converged commercial core
- TMF637Product Inventory: Served by the converged commercial core
- TMF663Shopping Cart: Served by the converged commercial core
- TMF648Quote: Partial, core plus a retained system
- TMF671Promotion: Partial, core plus a retained system
- TMF676Payment: Served by the converged commercial core
Billing & Usage
- TMF678Customer Bill: Served by the converged commercial core
- TMF670Payment Method: Served by the converged commercial core
- TMF654Prepay Balance: Served by the converged commercial core
- TMF677Usage Consumption: Served by the converged commercial core
- TMF635Usage: Partial, core plus a retained system
- Collections: Partial, core plus a retained system
- Revenue assurance feeds: New-build or owned outside the core
Production
- TMF633Service Catalog: Partial, core plus a retained system
- TMF641Service Ordering: Served by the converged commercial core
- TMF638Service Inventory: Partial, core plus a retained system
- TMF640Service Activation: Served by the converged commercial core
- TMF634Resource Catalog: Partial, core plus a retained system
- TMF639Resource Inventory: Partial, core plus a retained system
- TMF621Trouble Ticket: New-build or owned outside the core
Engagement Management
- TMF681Communication: Partial, core plus a retained system
- Notification: Partial, core plus a retained system
- Federated identity: Partial, core plus a retained system
- Case / contact centre: New-build or owned outside the core
- Digital experience / UI: New-build or owned outside the core
- TMF646Appointment: Partial, core plus a retained system
- TMF680Recommendation: New-build or owned outside the core
Decoupling & Integration
- TMF688Event: Served by the converged commercial core
- TMF701Process Flow: Served by the converged commercial core
- Integration / middleware: New-build or owned outside the core
- Event mesh / topics: New-build or owned outside the core
- API gateway & security: New-build or owned outside the core
- Schema & contract registry: New-build or owned outside the core
- Conformance (Open API / CTK): New-build or owned outside the core
Intelligence Management
- TMF628Performance: Partial, core plus a retained system
- TMF921Intent: New-build or owned outside the core
- AI agent: New-build or owned outside the core
- Conversational AI / NLP: New-build or owned outside the core
- Knowledge: New-build or owned outside the core
- AI / ML model: New-build or owned outside the core
- Data & analytics: Partial, core plus a retained system
Enterprise & Platform
- TMF667Document: Partial, core plus a retained system
- Change: Partial, core plus a retained system
- EA & programme governance: New-build or owned outside the core
- Policy & security: New-build or owned outside the core
- ERP financials: Partial, core plus a retained system
- HR / workforce: Partial, core plus a retained system
- Facilities & budget: Partial, core plus a retained system
- Served by the converged commercial core
- Partial, core plus a retained system
- New-build or owned outside the core
See EcoGenie on your own architecture.
Bring a question about your estate. We’ll answer it from the model.