Skip to content
Africa Tech FestivalMeet us in Cape Town, 17–19 Nov.

Solution

Available

The whole enterprise in one Enterprise Twin, kept current.

EcoGenie keeps an Enterprise Twin of your organisation and gives architects the tools to design, plan and govern change.

Solves
Architecture knowledge spread across documents and people
Used by
Enterprise, solution and domain architects
You receive
Blueprints, portfolio management, impact assessment, capability and process maps, architecture governance
Proof
Telco programme: the full application portfolio in one model, each application with its lifecycle stage and owner

What it does

Seven connected layers, from strategy to technology.

Every system, process and capability sits in one model, with the links between them, so a question about one layer can be answered from the others.

  • Built from what you already hold

    The Enterprise Twin starts from existing documents and systems, so nobody models from a blank page.

  • Structured against recognised frameworks

    Each layer follows its standard, so the model reads the same to every team.

  • See what a change touches

    Dependencies are traced across layers before a change is made.

  • Stays current as work ships

    Approved changes are written back through governance, so the model stays in step with what ships.

  • Open to product, delivery and business teams

    They explore the model without booking an architect’s time.

Navigate the enterprise, layer by layer.

The Enterprise Twin shows the organisation as one connected model, from strategy down to the technology that runs it.

SelectSelect a layer to see an example

  1. StrategyBusiness Motivation Model
  2. CapabilityTM Forum ODA Digital Experience
  3. ProcessesTM Forum eTOM
  4. IntegrationsTM Forum Open APIs
  5. ApplicationsTM Forum ODA and TAM
  6. Genies
  7. TechnologyTechnical Reference Model
  1. Layer 1 · Strategy1 of 7

    Business Outcomes

    Business Motivation Model

    Strategic goals and objectives, structured using the Business Motivation Model.

    • Vision, goals and objectives on one scorecard, grouped by the perspectives your board already reports on.
    • Every KPI carries its baseline, target and progress.
    • Each initiative traces up to the objective it serves and down to the work beneath it.
  2. Layer 2 · Capability2 of 7

    Customer capabilities

    TM Forum ODA Digital Experience

    Journey-based digital functions aligned to the ODA Digital Experience domain.

    • Each customer-facing capability is named once, against the ODA Digital Experience domain.
    • See which journeys your estate already supports before a second team builds the same one.
    • Capability gaps show up next to the objectives they block.
  3. Layer 3 · Processes3 of 7

    Operating Model

    TM Forum eTOM

    Business requirements mapped to TM Forum’s eTOM process framework.

    • L1 to L4 processes laid out against eTOM, each linked to the capability it supports.
    • Where a process crosses teams, the handoff and the control that governs it are both recorded.
    • See where handoffs cause delays.
  4. Layer 4 · Integrations4 of 7

    APIs and integrations

    TM Forum Open APIs

    Service and API discovery governed by TM Forum Open API standards.

    • Services and APIs are discovered from code and gateways, not from a wiki.
    • Each interface is matched to the TM Forum Open API specification it implements.
    • Consumers are known before a contract changes, so you see what breaks before it ships.
  5. Layer 5 · Applications5 of 7

    Application Portfolio Management

    TM Forum ODA and TAM

    EA and CMDB data reconciled against ODA and TAM functional blocks.

    • Every application sits under the ODA component and TAM function it delivers.
    • Duplicates surface wherever two systems claim the same function.
    • Cost, risk and lifecycle decisions use the same data.
  6. Layer 6 · Genies6 of 7

    Intelligence Stack

    The genies, models and AI tools at work across the enterprise, each with its purpose and boundaries.

    • Every genie listed with its purpose, tools and permissions.
    • See which processes and teams each genie supports.
    • Models and prompts governed like any other component.
  7. Layer 7 · Technology7 of 7

    Technology Portfolio Management

    Technical Reference Model

    Technology components mapped to the Technical Reference Model (TRM).

    • Platforms, versions and vendors are mapped to the Technical Reference Model.
    • Standards and lifecycle attach to every component in the estate.
    • End-of-life dates show on the roadmap before they become urgent.

Governance

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.

Detail

Standards applied in EcoGenie for Telco
LayerStandard
StrategyBusiness Motivation Model
CapabilityTM Forum ODA Digital Experience
ProcessesTM Forum eTOM
IntegrationsTM Forum Open APIs
ApplicationsTM Forum ODA and TAM
GeniesEcoGenie approval rules
TechnologyTechnical Reference Model

Modules

Six modules, from import to governance.

The architect’s work in one place: bring in what exists, design the change and approve it.

  1. Import and set-up

    Imports code, documents, tickets, spreadsheets and transcripts, and sets up the metamodel to the customer’s standards.

    Benefit

    Start from a mapped estate.

  2. Modelling and design

    Diagramming, solution diagrams and functional decomposition.

    Benefit

    Keep every design consistent with the current estate.

  3. Business and capability planning

    Capability planning, business alignment and L1–L4 process mapping.

    Benefit

    Plan the capabilities and processes business priorities depend on.

  4. Application portfolio and lifecycle

    Portfolio and lifecycle management, with rationalisation against reference models.

    Benefit

    Guide application investment, consolidation and retirement.

  5. Integration management

    Relationships between systems and interfaces, modelled and maintained.

    Benefit

    Keep the integration architecture coherent as systems change.

  6. Architecture governance

    Architecture principles and standards, compliance reviews, waivers and decision records, applied to every change.

    Benefit

    Keep designs compliant and decisions traceable.

How it works

Design from the model, update the model.

Each design starts from the Enterprise Twin and is written back to it through governance.

  1. Understand the context

    Start from the Enterprise Twin and existing documents.

  2. Model and design

    Create diagrams, decompose functions and map capabilities, processes and integrations.

  3. Guide architecture decisions

    Apply reference models, principles and reusable patterns to each design.

  4. Maintain the architecture

    Update artefacts and portfolio data through governance.

    Governed updates

You receive

Architecture outputs

  • Solution and architecture diagrams
  • Capability and L1–L4 process maps
  • Application portfolio and lifecycle views
  • Integration models
  • Architecture principles, blueprints and patterns
  • Architecture governance records

Deliverables

Deliverables that stay current.

Each one is drawn from the Enterprise Twin, so it changes when the estate does.

  • Solution and architecture diagrams

    Generated from the model, so each diagram reflects the current estate.

  • Capability and L1–L4 process maps

    Mapped to TM Forum ODA and eTOM through EcoGenie for Telco.

  • Application portfolio and lifecycle views

    Each application with its lifecycle stage and rationalisation status.

  • Integration models

    Systems and interfaces, with their Open API conformance.

  • Principles, blueprints and patterns

    Reusable starting points for each new design.

  • Architecture governance records

    Reviews, waivers and decisions recorded against the components they affect.

Benefits

  • Clearer solution designs

    Show how each proposed solution supports the business need it addresses.

  • Better investment decisions

    Capability plans and lifecycle data show where to invest, consolidate or retire.

  • Reusable architecture

    Established blueprints and patterns give every design a consistent starting point.

  • Governed architecture

    Reviews and decisions stay on record, so every design follows your architecture principles.

Used by

Enterprise, solution and domain architects.

Architect genieDraws diagrams, capability and process maps and integration models from the current model.

See EcoGenie on your own architecture.

Bring a system or domain. We’ll show it in your Enterprise Twin.