Pages
More Information

From cell alarm to credit note

Where BSS meets OSS

The network tells you what broke. The telecom ontology tells you who it broke for and what you promised them. Exosphere Agentic runs on Azure and integrates with the Microsoft AI platform, deployed into the customer's own tenant — so context, data and governance stay where they belong.

Updated

The question every operator wants answered

Which customers are affected by this cell-site degradation, and what do we owe them?

Answering it means crossing from the network to the customer: from a resource, to the services that ride on it, to the products and customers those services support, to the agreements that set what was promised.

In Exosphere Agentic that join is a modelled path, not a report. A loop can follow it the moment a signal arrives, so the customer hears from you before they need to call you.

From cell alarm to credit, at a glance

flowchart LR
    A["Cell site degrades"] --> B["Which services<br/>ride on it"]
    B --> C["Which customers<br/>and products"]
    C --> D["What we<br/>promised them"]
    D --> E(["A person approves"])
    E --> F["Proactive notice"]
    E --> G["Credit raised<br/>in billing"]
    classDef human stroke:#009688,stroke-width:3px
    class E human
One path from a network signal to a customer outcome, with a person approving before anything changes.

The customer-facing service is the join

SID already describes the bridge between OSS and BSS:

  • A resource is the physical or logical thing in the network, such as a cell. 3GPP SA5 models cells as managed objects.
  • A resource-facing service (RFS) is the internal technical service built on resources. The customer never sees it.
  • A customer-facing service (CFS) is what a customer actually gets through a product, described in technology-neutral terms such as throughput and availability.

The CFS is the crossing point. Model it once in the telecom ontology, with typed links down to resources and up to products and customers, and every loop can use it.

Every hop is already a standard

StepTM Forum anchor
A resource alarm is raisedTMF642 Alarm Management
Find the resource and the services it supportsTMF639 Resource Inventory, TMF638 Service Inventory
Find the products and customersTMF637 Product Inventory, TMF629 Customer Management
Check what was promisedTMF651 Agreement Management, TMF657 Service Quality Management
Record the service impactTMF656 Service Problem Management
Drive the resource repairTMF621 Trouble Ticket Management, with TMF724 as the ITIL incident view across both
Tell the customerTMF681 Communication Management
Make it rightCredit raised in billing, visible via TMF678 Customer Bill Management

No new contract to adopt: each hop follows a TM Forum Open API your stack already speaks or can expose.

The crossing point, hop by hop

flowchart TD
    EV["Resource alarm<br/>TMF642"]
    subgraph OSS["OSS DOMAIN"]
        RES["Resource<br/>for example a cell"]
        RFS["Resource-facing<br/>service"]
    end
    subgraph XP["THE CROSSING POINT"]
        CFS["Customer-facing<br/>service"]
    end
    subgraph BSS["BSS DOMAIN"]
        PRD["Product"]
        CUS["Customer<br/>and agreement"]
    end
    ANS["Who is affected<br/>and what we owe"]
    A1["TMF656<br/>service impact"]
    A2["TMF621<br/>resource repair"]
    H(["Person approves"])
    A3["TMF681<br/>proactive notice"]
    A4["Credit raised in billing<br/>visible via TMF678"]
    EV -->|"TMF639"| RES
    RES -->|"TMF638"| RFS
    RFS -->|"TMF638"| CFS
    CFS -->|"TMF637"| PRD
    PRD -->|"TMF629 · TMF651"| CUS
    CUS --> ANS
    ANS --> A1
    ANS --> A2
    ANS --> H
    H --> A3
    H --> A4
    classDef exos stroke:#0077B6,stroke-width:2px
    classDef std stroke:#005F8A,stroke-width:1px
    classDef human stroke:#009688,stroke-width:3px
    class CFS,ANS exos
    class A1,A2,A3,A4 std
    class H human
Resource to customer through the TM Forum inventories; anything that touches the customer waits for a person.

Proactive, and a person approves every credit

The agent assembles the evidence. A person signs.

  • The loop proposes the notice and the credit with its evidence attached: which services, which customers, which agreement, and what data is missing.
  • Exosphere, the judgment layer inside Exosphere Agentic, checks the proposal against your policy and routes it to the role with the authority to approve it.
  • Only then is the customer notified and the credit raised in billing, and the whole chain lands in one audit record.

How Exos gets you there. Exos Systems delivers the ontology binding, the OSS telemetry connection and the closed-loop assurance flow as an engagement path: map one domain properly, cross the boundary from BSS into OSS, then make it a reusable asset. Follow the full cell-site walk.

See it on a network signal

Book a demo, ask for the ontology briefing, or open the library.