Telecommunications

Network Operations Copilot

Designed for NOC engineer

Cut mean time to repair in the network operations centre by correlating alarms with topology and change records, retrieving the matching runbook, and requiring engineer approval before any automated remediation touches the network.

Contract TEL-01 · primary aggregate NetworkIncident · mode loading

Decision brief

Approve and execute remediation: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

NOC engineer

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

At 02:10 a metro region raises 380 alarms; the copilot correlates them to a single aggregation router, links the onset to a configuration push 14 minutes earlier, retrieves the rollback runbook, predicts 26,000 subscribers restored, and the NOC engineer approves the rollback which clears the incident in nine minutes..

Decision to make

Cut mean time to repair in the network operations centre by correlating alarms with topology and change records, retrieving the matching runbook, and requiring engineer approval before any automated remediation touches the network.

Outcome to show

Executed change with rollback plan and incident update gives NOC engineer the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Ingest and deduplicate alarms
  2. 2Correlate alarms into a service incident
  3. 3Test change and maintenance causation
  4. 4Retrieve and adapt the runbook
  5. 5Approve and execute remediation

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

NOC engineer verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved NetworkIncident evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Cut mean time to repair in the network operations centre by correlating alarms with topology and change records, retrieving the matching runbook, and requiring engineer approval before any automated remediation touches the network.
Primary aggregate
NetworkIncident
Primary container
networkIncidents
Hierarchical key
/tenantId + /networkRegionId
Schema version
1

Sample scenario

At 02:10 a metro region raises 380 alarms; the copilot correlates them to a single aggregation router, links the onset to a configuration push 14 minutes earlier, retrieves the rollback runbook, predicts 26,000 subscribers restored, and the NOC engineer approves the rollback which clears the incident in nine minutes.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
networkIncidents Primary /tenantId + /networkRegionId NetworkIncident, NetworkAlarm, TopologyRelation, ChangeRecord, RemediationProposal
networkRunbookLibrary Reference /tenantId + /faultSignatureCode RunbookProcedure

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
NetworkIncident networkIncidents /tenantId + /networkRegionId incident::{networkRegionId}::{incidentId} impactSummaryVector
NetworkAlarm networkIncidents /tenantId + /networkRegionId alarm::{networkRegionId}::{alarmId} None
TopologyRelation networkIncidents /tenantId + /networkRegionId topology::{networkRegionId}::{elementId} None
ChangeRecord networkIncidents /tenantId + /networkRegionId change::{networkRegionId}::{changeId} None
RunbookProcedure networkRunbookLibrary /tenantId + /faultSignatureCode runbook::{faultSignatureCode}::{runbookId}::{stepIndex} stepVector
RemediationProposal networkIncidents /tenantId + /networkRegionId remediation::{networkRegionId}::{proposalId} None

Query patterns