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

Platform

Three parts, one platform.

Every product runs on the same knowledge graph, orchestration and governance.

Three parts keep the organisation informed.

  • Knowledge Graph

    One shared language for the enterprise: every artefact a node, every dependency a relationship.

    • Shared understanding
    • Trace change impact
    • Spot missing information
    • Richer context for genies

    Visibility

    Everyone can find what the organisation knows

  • Orchestration

    Moves work between specialist genies and people, and writes each outcome back to the knowledge graph.

    • Ingestion
    • Specialist genies
    • Work routing
    • System connectors
    • Model updates
    • Rule-based tools

    Change management

    The model updates as work is done

  • Governance

    Records who approved each change, and why.

    • Human approval
    • Traceability
    • Access control
    • Data separation
    • Layer standards
    • Audit history

    Governance

    Every change is audited and checked against standards

Every approved change updates the model everyone sees.

Knowledge Graph

A knowledge graph creates a shared language.

Every artefact is a node and every dependency a relationship, so people and genies work from the same connected facts.

Why it helps

  1. Shared understandingBusiness and IT describe systems, processes and owners with the same terms.
  2. Trace change impactFollow the relationships from a proposed change to every system, process and team it touches.
  3. Spot missing informationGaps show wherever the metamodel expects a link or detail, such as an application with no owner.
  4. Richer context for geniesGenies reason over connected, approved facts instead of isolated documents.
Example knowledge graphA generic example network of ten nodes: Sales team, CRM, Support team, Customer record, Customer onboarding, Identity API, Payments API, Data warehouse, Access policy and Billing service, joined by relationships. CRM to Customer record and Payments API to Billing service are highlighted.SalesteamCRMSupportteamCustomerrecordCustomeronboardingIdentityAPIPaymentsAPIDatawarehouseAccesspolicyBillingservice
  • Sales team is related to CRM
  • Support team is related to CRM
  • CRM is related to Customer record (highlighted)
  • Customer record is related to Customer onboarding
  • Customer record is related to Identity API
  • Support team is related to Customer onboarding
  • Customer onboarding is related to Identity API
  • Customer onboarding is related to Payments API
  • Customer onboarding is related to Data warehouse
  • Identity API is related to Access policy
  • Payments API is related to Billing service (highlighted)
  • Billing service is related to Data warehouse
  1. The agreed blueprintMetamodelThe agreed blueprint: types, allowed links and required details.
  2. definesTypeCustomerWho the business serves
  3. usesTypeServiceWhat the customer uses
  4. depends onTypeApplicationWhat delivers the service

Example rule: every application must have an owner.

Orchestration

Orchestration keeps the knowledge graph current.

It routes work between genies and people, and writes every outcome back to the graph.

Ingestion

Every source becomes one shared language

  • CodeSpecs read from the running code
  • Confluence & JiraDocs and tickets reconciled
  • ExcelEvery operating company’s format, one model
  • System connectorsVendor systems, read live
  • ScreenshotsMissing designs rebuilt from images
  • Teams & transcriptsDecisions captured, not lost

Every review and conversation in EcoGenie feeds back in, continuously.

The platform loop

  • Knowledge GraphWhat’s been agreed
  • GovernanceChecked and approved
  • OrchestrationRoutes work between genies and people

Genies and people do the work

Action

Outcomes change the enterprise or update the model

Model update

Approved findings go back into the knowledge graph with their source, so the next question starts from what’s been agreed.

Drive an initiative

  1. 01Input
  2. 02Analysis
  3. 03Impact assessment
  4. 04Deliverables

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.

Controls

  • Human approvalA named person approves each change before it reaches the model.
  • TraceabilityEvery decision and artefact links to its source and its approver.
  • Access controlPeople and genies see only what their role allows.
  • Data separationEach customer’s data is held separately and never shared across customers.
  • Standards checksEach change is checked against the standard for its layer.
  1. 1Change proposed
  2. 2Checked against the standard
  3. 3Reviewed by the owner
  4. 4Approved
  5. Written to the model

EcoGenie for Telco

One platform, configured for each industry.

EcoGenie for Telco is the first industry solution, with four products on the shared platform.

  1. Industry solutions

    Configured per industry

    EcoGenie for Telco

    First industry solution

    • TM Forum ODA
    • eTOM
    • SID
    • TAM
    • Open APIs
    • Telco metamodel
  2. Platform

    Industry-agnostic

    EcoGenie Platform

    AI-native, with enterprise architecture and delivery knowledge built in, based on Open Group standards.

    • Knowledge Graph

      One shared language for the enterprise: every artefact a node, every dependency a relationship.

      • Ingests code, documents, tickets and transcripts
      • Structured against TM Forum and Open Group

      Example Trace one API to every journey it serves

    • Orchestration

      The orchestration genie 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, and the audit trail keeps every decision.

      • TM Forum ODA, eTOM, SID, TAM and Open APIs
      • Role-based access, customer data kept separate

      Example New APIs checked for Open API conformance

See EcoGenie on your own architecture.

Bring a question about your estate. We’ll answer it from the model.