{
  "schema_version": "1.0",
  "last_updated": "2026-03-25",
  "canonical_host": "https://totogi.com",
  "language": "en-US",
  "about": {
    "organization_id": "https://totogi.com/#organization",
    "facts": "https://totogi.com/facts.json",
    "evidence": "https://totogi.com/evidence.json",
    "faqs": "https://totogi.com/company/faqs/"
  },
  "product_scopes": [
    {
      "id": "totogi:product:ontology",
      "name": "Totogi Ontology",
      "url": "https://totogi.com/telco-ontology/"
    },
    {
      "id": "totogi:product:charging",
      "name": "Totogi Charging-as-a-Service",
      "url": "https://totogi.com/ai-native-charging/"
    }
  ],
  "terms": [
    {
      "id": "totogi:term:telco-ontology",
      "term": "Telco ontology",
      "aliases": [
        "telecom ontology",
        "Totogi Ontology",
        "Totogi Telco Ontology"
      ],
      "definition_short": "A machine-readable semantic model of telecom entities, relationships, constraints, and valid state transitions that enables consistent reasoning and automation across BSS, OSS, and network domains.",
      "totogi_usage": "Totogi describes its Telco Ontology as an executable knowledge graph/digital twin that unifies how the business is represented so AI can understand, reason, and act across the estate.",
      "category": [
        "Ontology",
        "Telco",
        "AI"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:semantic-layer",
        "totogi:term:executable-knowledge-graph",
        "totogi:term:digital-twin"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/company/faqs/",
        "https://totogi.com/blog/why-telcos-fail-to-get-real-value-from-ai/"
      ]
    },
    {
      "id": "totogi:term:ontology",
      "term": "Ontology",
      "aliases": [],
      "definition_short": "A formal model that defines concepts, relationships, behaviors, and context so systems can interpret meaning and enforce what is valid or allowed, not just how data is structured.",
      "totogi_usage": "Totogi frames ontology as the missing context layer that makes cross-domain AI automation safe and scalable in telecom.",
      "category": [
        "Ontology",
        "Data"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:taxonomy",
        "totogi:term:schema",
        "totogi:term:valid-state-transition"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:taxonomy",
      "term": "Taxonomy",
      "aliases": [],
      "definition_short": "A hierarchical categorization system (like a folder structure) used to classify data or concepts.",
      "category": [
        "Data"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:ontology",
        "totogi:term:schema"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:schema",
      "term": "Schema",
      "aliases": [
        "data schema",
        "database schema"
      ],
      "definition_short": "A structural definition of how data is stored and shaped (e.g., fields and types in tables or payloads).",
      "category": [
        "Data"
      ],
      "product_scope": [
        "totogi:product:ontology",
        "totogi:product:charging"
      ],
      "see_also": [
        "totogi:term:taxonomy",
        "totogi:term:ontology"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:semantic-layer",
      "term": "Semantic layer",
      "aliases": [
        "executable semantic layer"
      ],
      "definition_short": "A layer that standardizes meaning (entities, relationships, lifecycle states, constraints) so multiple systems interpret and act on data consistently.",
      "totogi_usage": "Totogi positions the ontology as an executable semantic layer that centralizes meaning and action rather than just aggregating data.",
      "category": [
        "Ontology",
        "Integration"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:data-lake",
        "totogi:term:canonical-model",
        "totogi:term:api-governance"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:executable-knowledge-graph",
      "term": "Executable knowledge graph",
      "aliases": [
        "executable knowledge graph for telco"
      ],
      "definition_short": "A knowledge graph that not only models entities and relationships but is used to drive valid actions, workflows, and constraints in operational systems.",
      "totogi_usage": "Totogi describes its ontology as a telco-specific executable knowledge graph enabling AI to reason and safely execute across systems.",
      "category": [
        "Ontology",
        "AI"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:digital-twin",
        "totogi:term:guardrails"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:digital-twin",
      "term": "Digital twin",
      "aliases": [],
      "definition_short": "A structured model of a real-world system used to simulate, validate, and predict outcomes of changes before or during execution.",
      "totogi_usage": "Totogi states the Telco Ontology acts as a digital twin of the telecom business by representing systems, processes, and data in a semantic model.",
      "category": [
        "Ontology",
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:semantic-observability",
        "totogi:term:traceability"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/telco-ontology/understand-and-preempt/"
      ]
    },
    {
      "id": "totogi:term:semantic-observability",
      "term": "Semantic observability",
      "aliases": [],
      "definition_short": "Observability where metrics/events are interpreted with shared, governed meaning across domains, enabling consistent diagnosis and action.",
      "totogi_usage": "Totogi uses this to describe moving from data visibility to a governed, executable view of the telco so AI can act with confidence.",
      "category": [
        "Operations",
        "Ontology"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:single-source-of-truth",
        "totogi:term:traceability"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/understand-and-preempt/"
      ]
    },
    {
      "id": "totogi:term:data-lake",
      "term": "Data lake",
      "aliases": [],
      "definition_short": "A repository that centralizes large volumes of raw structured and unstructured data for storage and analytics.",
      "totogi_usage": "Totogi contrasts a data lake (centralizes data) with ontology (centralizes meaning and action, plus valid states/actions).",
      "category": [
        "Data",
        "Analytics"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:semantic-layer",
        "totogi:term:valid-state-transition"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:canonical-model",
      "term": "Canonical model",
      "aliases": [
        "canonical definitions",
        "canonical semantics"
      ],
      "definition_short": "A standardized representation of key domain concepts that multiple systems map to, enabling consistent meaning and reuse across integrations.",
      "totogi_usage": "Totogi describes mapping each system once into canonical definitions so integration complexity collapses from N-squared to N.",
      "category": [
        "Integration",
        "Ontology"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:n-squared-problem",
        "totogi:term:point-to-point-integration"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:entity",
      "term": "Entity",
      "aliases": [],
      "definition_short": "A distinct business or operational object (e.g., subscriber, product, service, resource, event) with identity and attributes.",
      "category": [
        "Ontology",
        "Data"
      ],
      "product_scope": [
        "totogi:product:ontology",
        "totogi:product:charging"
      ],
      "see_also": [
        "totogi:term:relationship",
        "totogi:term:entity-mismatch"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/blog/why-telcos-fail-to-get-real-value-from-ai/"
      ]
    },
    {
      "id": "totogi:term:relationship",
      "term": "Relationship",
      "aliases": [],
      "definition_short": "A defined connection between entities (e.g., a subscriber is entitled to a service; a service maps to network resources).",
      "category": [
        "Ontology"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:knowledge-network"
      ],
      "source_urls": [
        "https://totogi.com/blog/how-bss-magics-telco-ontology-saves-a-tier-1-millions-in-revenue-leakage/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:constraint",
      "term": "Constraint",
      "aliases": [
        "business constraint"
      ],
      "definition_short": "A rule that restricts what actions or state transitions are valid (e.g., what must be true before a service can be provisioned).",
      "category": [
        "Ontology",
        "Governance"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:guardrails",
        "totogi:term:valid-state-transition"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/telco-ontology/understand-and-preempt/"
      ]
    },
    {
      "id": "totogi:term:lifecycle-state",
      "term": "Lifecycle state",
      "aliases": [
        "state",
        "lifecycle status"
      ],
      "definition_short": "A defined status of an entity (e.g., order state, service state) used to govern behavior and automation.",
      "category": [
        "Ontology",
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:valid-state-transition"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:valid-state-transition",
      "term": "Valid state transition",
      "aliases": [
        "allowed state transition"
      ],
      "definition_short": "A permitted change from one lifecycle state to another, governed by constraints and business rules.",
      "category": [
        "Ontology",
        "Governance"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:constraint",
        "totogi:term:guardrails"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:guardrails",
      "term": "Guardrails",
      "aliases": [
        "AI guardrails"
      ],
      "definition_short": "Controls that prevent invalid or unsafe actions by enforcing constraints, valid operations, and end-to-end validations.",
      "totogi_usage": "Totogi describes ontology as providing shared meaning and guardrails that let AI agents act reliably across the whole estate.",
      "category": [
        "AI",
        "Governance"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:hallucination",
        "totogi:term:cross-system-validation"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:semantic-fragmentation",
      "term": "Semantic fragmentation",
      "aliases": [
        "semantic chaos",
        "inconsistent definitions"
      ],
      "definition_short": "A condition where different systems define the same concepts differently, causing contradictions, brittle integrations, and unreliable automation.",
      "totogi_usage": "Totogi frames semantic fragmentation as the core blocker to telco modernization and reliable AI.",
      "category": [
        "Integration",
        "Ontology"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:manual-reconciliation",
        "totogi:term:n-squared-problem"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/blog/why-telcos-fail-to-get-real-value-from-ai/"
      ]
    },
    {
      "id": "totogi:term:manual-reconciliation",
      "term": "Manual reconciliation",
      "aliases": [],
      "definition_short": "Human effort required to align mismatched data and meanings across systems before insights or actions are trusted.",
      "category": [
        "Operations",
        "Integration"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:semantic-fragmentation"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/understand-and-preempt/"
      ]
    },
    {
      "id": "totogi:term:entity-mismatch",
      "term": "Entity mismatch",
      "aliases": [
        "entity mismatch problem"
      ],
      "definition_short": "When systems disagree on identity or structure of the same real-world object (e.g., subscriber identifiers, product definitions), causing failures downstream.",
      "category": [
        "Integration",
        "Data"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:entity",
        "totogi:term:cross-system-validation"
      ],
      "source_urls": [
        "https://totogi.com/blog/why-telcos-fail-to-get-real-value-from-ai/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:cross-domain-workflow",
      "term": "Cross-domain workflow",
      "aliases": [
        "cross-stack workflow",
        "end-to-end workflow"
      ],
      "definition_short": "A workflow that spans multiple domains and systems (e.g., ordering -> provisioning -> charging -> care) where correctness depends on shared meaning.",
      "category": [
        "Operations",
        "Integration"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:orchestration",
        "totogi:term:traceability"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/blog/why-telcos-fail-to-get-real-value-from-ai/"
      ]
    },
    {
      "id": "totogi:term:cross-system-validation",
      "term": "Cross-system validation",
      "aliases": [
        "end-to-end validation"
      ],
      "definition_short": "Validation that checks behavior and outcomes across systems (not just payload structure) to detect drift and prevent invalid operations.",
      "totogi_usage": "Totogi describes using ontology to enable reusable validations and end-to-end workflow correctness, especially during coexistence and phased modernization.",
      "category": [
        "Quality",
        "Integration"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:guardrails",
        "totogi:term:api-governance"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:orchestration",
      "term": "Orchestration",
      "aliases": [
        "workflow orchestration"
      ],
      "definition_short": "Coordinating actions across multiple systems so execution happens in the correct order with consistent business rules.",
      "category": [
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:insight-to-action-gap"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:traceability",
      "term": "Traceability",
      "aliases": [
        "end-to-end traceability"
      ],
      "definition_short": "The ability to trace symptoms to causes, impacted systems, and the actions taken, with a clear audit trail across systems.",
      "totogi_usage": "Totogi highlights traceability from symptom to cause to recommended actions and links ontology to full traceability for autonomous execution.",
      "category": [
        "Governance",
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:semantic-observability"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/understand-and-preempt/",
        "https://totogi.com/newsroom/press-releases/tier-1-southeast-asian-operator-selects-totogis-telco-ontology-as-foundation-for-ai-strategy/"
      ]
    },
    {
      "id": "totogi:term:insight-to-action-gap",
      "term": "Insight-to-action gap",
      "aliases": [],
      "definition_short": "The delay between generating insights and executing coordinated action across systems, often caused by fragmentation and integration overhead.",
      "totogi_usage": "Totogi states AI insights create value only when they trigger coordinated action and positions ontology as the enabler to execute in seconds, not weeks.",
      "category": [
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:orchestration"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:multi-vendor-estate",
      "term": "Multi-vendor estate",
      "aliases": [
        "multi-vendor stack",
        "fragmented estate"
      ],
      "definition_short": "An environment where multiple vendor systems coexist across domains, often with inconsistent models and duplicated meaning.",
      "category": [
        "Architecture"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:coexistence",
        "totogi:term:vendor-lock-in"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:coexistence",
      "term": "Coexistence",
      "aliases": [
        "phased modernization",
        "coexistence-heavy environment"
      ],
      "definition_short": "A transition period where legacy and target systems run in parallel while migration occurs in phases.",
      "totogi_usage": "Totogi positions ontology as enabling stable coexistence by normalizing meaning and validating outcomes end-to-end while modernizing in phases.",
      "category": [
        "Transformation"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:rip-and-replace",
        "totogi:term:cross-system-validation"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:vendor-lock-in",
      "term": "Vendor lock-in",
      "aliases": [],
      "definition_short": "Dependency on a vendor’s proprietary data model, workflows, or integration glue that makes replacing components expensive and risky.",
      "totogi_usage": "Totogi describes preventing lock-in by separating meaning from vendor models and reusing ontology mappings and validations across replacements.",
      "category": [
        "Transformation",
        "Governance"
      ],
      "product_scope": [
        "totogi:product:ontology",
        "totogi:product:charging"
      ],
      "see_also": [
        "totogi:term:canonical-model"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:rip-and-replace",
      "term": "Rip and replace",
      "aliases": [
        "big bang replacement"
      ],
      "definition_short": "Replacing large legacy systems in a single disruptive program, typically high risk and high cost.",
      "totogi_usage": "Totogi repeatedly positions its ontology approach as not requiring rip-and-replace; it sits above existing systems.",
      "category": [
        "Transformation"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:coexistence"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/newsroom/press-releases/tier-1-southeast-asian-operator-selects-totogis-telco-ontology-as-foundation-for-ai-strategy/"
      ]
    },
    {
      "id": "totogi:term:point-to-point-integration",
      "term": "Point-to-point integration",
      "aliases": [
        "brittle point-to-point integrations"
      ],
      "definition_short": "Direct bespoke integrations between pairs of systems that are costly to maintain and break when either system changes.",
      "totogi_usage": "Totogi describes collapsing point-to-point complexity by mapping each system once into canonical definitions (N-squared to N).",
      "category": [
        "Integration"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:n-squared-problem",
        "totogi:term:canonical-model"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:n-squared-problem",
      "term": "N-squared problem",
      "aliases": [
        "N^2 integration complexity"
      ],
      "definition_short": "Integration complexity that grows quadratically as more systems are added, because each new system requires integrations with all others.",
      "totogi_usage": "Totogi explicitly references collapsing integration complexity from N-squared to N via single mapping to canonical definitions.",
      "category": [
        "Integration"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:point-to-point-integration"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:ai-agents",
      "term": "AI agents",
      "aliases": [
        "agentic AI",
        "agentic systems"
      ],
      "definition_short": "AI systems that can plan and take actions (often via tools/APIs) to achieve goals, not just generate text.",
      "totogi_usage": "Totogi emphasizes agents need stable context (entities, relationships, constraints, valid operations) to act safely across telco systems.",
      "category": [
        "AI"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:guardrails",
        "totogi:term:rag"
      ],
      "source_urls": [
        "https://totogi.com/blog/prepare-your-telco-for-ai-agents/",
        "https://totogi.com/company/faqs/",
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:rag",
      "term": "Retrieval-augmented generation (RAG)",
      "aliases": [
        "RAG"
      ],
      "definition_short": "An approach where a model retrieves relevant external information and uses it as context when generating answers.",
      "totogi_usage": "Totogi lists RAG alongside agentic systems and chat apps as AI capabilities that can be used when grounded by the ontology.",
      "category": [
        "AI"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:ai-agents"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:hallucination",
      "term": "Hallucination",
      "aliases": [],
      "definition_short": "Model outputs that appear plausible but are not grounded in correct data, meaning, or allowed operations.",
      "totogi_usage": "Totogi claims ontology-grounded execution is intended to be hallucination-free by enforcing semantics and valid actions.",
      "category": [
        "AI",
        "Risk"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:guardrails"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:bss",
      "term": "BSS",
      "aliases": [
        "Business Support Systems"
      ],
      "definition_short": "Systems supporting commercial operations such as product catalog, ordering, billing, charging, CRM, and customer care.",
      "category": [
        "Telco"
      ],
      "product_scope": [
        "totogi:product:ontology",
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/newsroom/press-releases/tier-1-southeast-asian-operator-selects-totogis-telco-ontology-as-foundation-for-ai-strategy/"
      ]
    },
    {
      "id": "totogi:term:oss",
      "term": "OSS",
      "aliases": [
        "Operations Support Systems"
      ],
      "definition_short": "Systems supporting network operations such as inventory, fault/performance management, provisioning, and orchestration.",
      "category": [
        "Telco"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:csp",
      "term": "CSP",
      "aliases": [
        "Communications Service Provider"
      ],
      "definition_short": "A telecom operator providing connectivity and digital services to consumers or enterprises.",
      "category": [
        "Telco"
      ],
      "product_scope": [
        "totogi:product:ontology",
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/understand-and-preempt/",
        "https://totogi.com/ai-native-charging/"
      ]
    },
    {
      "id": "totogi:term:mno",
      "term": "MNO",
      "aliases": [
        "Mobile Network Operator"
      ],
      "definition_short": "A CSP that owns spectrum and operates the mobile radio network.",
      "category": [
        "Telco"
      ],
      "product_scope": [
        "totogi:product:ontology",
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:mvno",
      "term": "MVNO",
      "aliases": [
        "Mobile Virtual Network Operator"
      ],
      "definition_short": "A mobile operator that sells services using an MNO's network, typically relying on wholesale agreements.",
      "category": [
        "Telco"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:mvne",
      "term": "MVNE",
      "aliases": [
        "Mobile Virtual Network Enabler"
      ],
      "definition_short": "A platform provider that enables MVNO operations (e.g., provisioning, billing, charging) on top of MNO wholesale arrangements.",
      "category": [
        "Telco"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:tmf-open-apis",
      "term": "TM Forum Open APIs",
      "aliases": [
        "TMF Open APIs"
      ],
      "definition_short": "A set of standardized telecom APIs aimed at interoperability across BSS/OSS components.",
      "totogi_usage": "Totogi states it embraces TM Forum Open APIs and uses ontology plus automation to accelerate conformance and certification.",
      "category": [
        "Standards"
      ],
      "product_scope": [
        "totogi:product:ontology",
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:oda",
      "term": "Open Digital Architecture (ODA)",
      "aliases": [
        "TM Forum ODA"
      ],
      "definition_short": "A TM Forum reference architecture for building composable telecom IT with standardized components and APIs.",
      "totogi_usage": "Totogi describes operationalizing ODA by transforming canonical models into executable semantics across domains.",
      "category": [
        "Standards",
        "Architecture"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:3gpp",
      "term": "3GPP",
      "aliases": [],
      "definition_short": "The standards body that defines cellular network specifications (including 5G core and charging architecture).",
      "category": [
        "Standards"
      ],
      "product_scope": [
        "totogi:product:charging",
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:5g-sa",
      "term": "5G Standalone (5G SA)",
      "aliases": [
        "5G SA"
      ],
      "definition_short": "A 5G architecture with a 5G core enabling advanced services and more granular, real-time charging and policy control.",
      "category": [
        "5G",
        "Charging"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/ai-native-charging/",
        "https://totogi.com/solutions/charging-system-for-5g-sa-5g-advanced/"
      ]
    },
    {
      "id": "totogi:term:5g-advanced",
      "term": "5G Advanced",
      "aliases": [],
      "definition_short": "A set of enhancements to 5G capabilities (often associated with later 3GPP releases) enabling richer telemetry and monetization models.",
      "category": [
        "5G",
        "Charging"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/ai-native-charging/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:caas",
      "term": "Charging-as-a-Service (CaaS)",
      "aliases": [
        "SaaS charging",
        "Totogi Charging-as-a-Service"
      ],
      "definition_short": "A cloud-delivered charging platform operated as a multi-tenant SaaS service rather than deployed and maintained per operator.",
      "totogi_usage": "Totogi positions Charging-as-a-Service as AI-native, cloud-native, and deployable in weeks.",
      "category": [
        "Charging",
        "SaaS"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/ai-native-charging/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:serverless",
      "term": "Serverless",
      "aliases": [],
      "definition_short": "A cloud execution model where infrastructure management is abstracted away and compute scales automatically with usage.",
      "totogi_usage": "Totogi describes serverless charging as eliminating the need to manage networks/servers/instances/clusters and enabling fast scaling.",
      "category": [
        "Cloud",
        "Charging"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/ai-native-charging/",
        "https://totogi.com/solutions/charging-system-for-5g-sa-5g-advanced/"
      ]
    },
    {
      "id": "totogi:term:elastic-scaling",
      "term": "Elastic scaling",
      "aliases": [
        "elasticity"
      ],
      "definition_short": "Automatic scale-up and scale-down of capacity based on demand rather than fixed provisioning.",
      "category": [
        "Cloud"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/solutions/charging-system-for-5g-sa-5g-advanced/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:multi-tenancy",
      "term": "Multi-tenancy",
      "aliases": [
        "multi-tenant SaaS"
      ],
      "definition_short": "A SaaS architecture where multiple customers/brands share the same application codebase and infrastructure with strict data and configuration isolation.",
      "totogi_usage": "Totogi emphasizes true multi-tenancy for CSPs/MVNOs/enterprise slices and links it to speed, efficiency, and evergreen upgrades.",
      "category": [
        "SaaS",
        "Charging"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:saas",
      "term": "SaaS",
      "aliases": [
        "Software-as-a-Service",
        "evergreen SaaS"
      ],
      "definition_short": "Software delivered and operated by the vendor, typically with continuous updates and subscription consumption.",
      "totogi_usage": "Totogi uses SaaS to emphasize evergreen upgrades without downtime and reduced operational burden.",
      "category": [
        "SaaS"
      ],
      "product_scope": [
        "totogi:product:charging",
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/ai-native-charging/"
      ]
    },
    {
      "id": "totogi:term:event-based-charging",
      "term": "Event-based charging",
      "aliases": [
        "real-time event-based charging"
      ],
      "definition_short": "Charging based on real-time events (usage, policy triggers, slice events) rather than batch rating only.",
      "category": [
        "Charging",
        "5G"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:network-slicing",
      "term": "Network slicing",
      "aliases": [],
      "definition_short": "Partitioning a 5G network into logical slices with distinct SLAs and policies, enabling differentiated services and monetization.",
      "category": [
        "5G"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/",
        "https://totogi.com/ai-native-charging/"
      ]
    },
    {
      "id": "totogi:term:chf",
      "term": "Charging Function (CHF)",
      "aliases": [],
      "definition_short": "A 5G core network function responsible for online/offline charging interactions in the 5G service-based architecture.",
      "category": [
        "5G",
        "Charging"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:pcf",
      "term": "Policy Control Function (PCF)",
      "aliases": [],
      "definition_short": "A 5G core network function that manages policy rules (QoS, charging triggers, access policies) for sessions and services.",
      "category": [
        "5G"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:nef",
      "term": "Network Exposure Function (NEF)",
      "aliases": [],
      "definition_short": "A 5G core network function that exposes network capabilities and events to external applications via APIs.",
      "category": [
        "5G",
        "APIs"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:sba",
      "term": "Service-Based Architecture (SBA)",
      "aliases": [],
      "definition_short": "The 5G core architecture style where network functions expose services to each other via standardized service-based interfaces.",
      "category": [
        "5G",
        "Architecture"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:composable-bss",
      "term": "Composable BSS",
      "aliases": [
        "composable architecture"
      ],
      "definition_short": "An architecture where BSS capabilities are modular and can be combined via APIs, allowing mix-and-match components rather than monolithic suites.",
      "totogi_usage": "Totogi argues composability requires shared meaning; otherwise it recreates integration mess with modern APIs.",
      "category": [
        "Architecture",
        "Transformation"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:zero-touch-integration",
      "term": "Zero-touch integration",
      "aliases": [
        "dynamic low-touch integration"
      ],
      "definition_short": "Integration that requires minimal human intervention because semantic models, mappings, and validations are standardized and automated.",
      "totogi_usage": "Totogi states zero-touch becomes realistic when systems are mapped to an executable semantic layer with guardrails and end-to-end validation.",
      "category": [
        "Integration",
        "Automation"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:api-governance",
      "term": "API governance",
      "aliases": [],
      "definition_short": "Policies and processes that ensure APIs remain consistent, versioned, and aligned to business meaning across teams and vendors.",
      "totogi_usage": "Totogi positions ontology as governing meaning so APIs anchor to consistent definitions and prevent semantic drift.",
      "category": [
        "APIs",
        "Governance"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:microservices",
      "term": "Microservices",
      "aliases": [],
      "definition_short": "An architecture style where systems are composed of small, independently deployable services communicating via APIs/events.",
      "totogi_usage": "Totogi argues microservices increase the need for shared semantic contracts to avoid distributed semantic inconsistency.",
      "category": [
        "Architecture"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:cpq",
      "term": "CPQ",
      "aliases": [
        "Configure-Price-Quote"
      ],
      "definition_short": "Tools that configure products, determine prices, and generate quotes; heavily dependent on consistent product and entitlement definitions.",
      "category": [
        "BSS",
        "Sales"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:order-fallout",
      "term": "Order fallout",
      "aliases": [
        "order management failures"
      ],
      "definition_short": "Failures where an order cannot complete due to data/config mismatches, broken linkages, or inconsistent system behavior.",
      "totogi_usage": "Totogi describes ontology enabling AI to detect and remediate order failures across systems with full traceability.",
      "category": [
        "BSS",
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/newsroom/press-releases/tier-1-southeast-asian-operator-selects-totogis-telco-ontology-as-foundation-for-ai-strategy/"
      ]
    },
    {
      "id": "totogi:term:mttr",
      "term": "MTTR",
      "aliases": [
        "mean time to repair"
      ],
      "definition_short": "The average time required to repair a fault or restore service/operations after an incident.",
      "category": [
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/newsroom/press-releases/tier-1-southeast-asian-operator-selects-totogis-telco-ontology-as-foundation-for-ai-strategy/"
      ]
    },
    {
      "id": "totogi:term:order-success-rate",
      "term": "Order success rate",
      "aliases": [],
      "definition_short": "The proportion of orders that complete successfully without manual intervention or failure states.",
      "category": [
        "BSS",
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/newsroom/press-releases/tier-1-southeast-asian-operator-selects-totogis-telco-ontology-as-foundation-for-ai-strategy/"
      ]
    },
    {
      "id": "totogi:term:ticket-volume",
      "term": "Ticket volume",
      "aliases": [],
      "definition_short": "The number of operational/support tickets opened over a time period, often used as a proxy for operational friction.",
      "category": [
        "Operations"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "source_urls": [
        "https://totogi.com/newsroom/press-releases/tier-1-southeast-asian-operator-selects-totogis-telco-ontology-as-foundation-for-ai-strategy/"
      ]
    },
    {
      "id": "totogi:term:single-source-of-truth",
      "term": "Single source of truth",
      "aliases": [
        "SSOT"
      ],
      "definition_short": "A single authoritative representation of key domain concepts used to keep decisions and actions consistent across systems and teams.",
      "totogi_usage": "Totogi uses the ontology as a governed semantic layer that enables a single, consistent understanding of telco entities and their valid relationships across the estate.",
      "category": [
        "Governance",
        "Ontology"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:semantic-layer",
        "totogi:term:canonical-model"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/",
        "https://totogi.com/company/faqs/"
      ]
    },
    {
      "id": "totogi:term:knowledge-network",
      "term": "Knowledge network",
      "aliases": [
        "knowledge network graph"
      ],
      "definition_short": "A network (graph) of entities and relationships that provides context for reasoning about how changes or events propagate across a domain.",
      "totogi_usage": "Totogi describes using an executable knowledge graph as a telco-specific knowledge network that connects business and network concepts into a single semantic model.",
      "category": [
        "Ontology",
        "AI"
      ],
      "product_scope": [
        "totogi:product:ontology"
      ],
      "see_also": [
        "totogi:term:executable-knowledge-graph",
        "totogi:term:relationship"
      ],
      "source_urls": [
        "https://totogi.com/telco-ontology/"
      ]
    },
    {
      "id": "totogi:term:planai",
      "term": "PlanAI",
      "aliases": [
        "Totogi PlanAI"
      ],
      "definition_short": "A module described by Totogi that uses AI to personalize offers or plan experiences based on subscriber behavior and context.",
      "totogi_usage": "Referenced in Totogi case studies as an AI-driven personalization capability used to improve revenue and engagement metrics.",
      "category": [
        "AI",
        "Monetization"
      ],
      "product_scope": [
        "totogi:product:charging"
      ],
      "see_also": [
        "totogi:term:caas",
        "totogi:term:ai-agents"
      ],
      "source_urls": [
        "https://totogi.com/resources/case-studies/planai-case-study/"
      ]
    }
  ],
  "related": {
    "facts_json": "https://totogi.com/facts.json",
    "evidence_json": "https://totogi.com/evidence.json"
  }
}