Home / Project guide

Project guide

Project Guide | NW Service Assurance Workbench

Free network service-assurance checklist for SLA symptoms, maps, and handoff reports. This guide organizes the repository's original implementation notes for network operations and service assurance teams.

Reviewed 2026-07-28. This page is derived from checked-in repository evidence and links back to its source.

NW Service Assurance Workbench

Scenario-driven carrier network operations system project focused on 5G/LTE access-core visibility, transport and IDC incident handling, service-quality review, and AX-assisted NOC playbooks.

System Overview

A telecom/service-assurance board that converts network noise into SLA, outage, and handoff decisions.

AreaDetails
UsersTelecom operations, IDC/network operations, managed service teams, and enterprise network owners.
Technical pathValidate the demo, README, architecture notes, and quality gate before deeper workflow review.
System scopeOutage triage, service path visibility, network posture, operator notes, and workflow automation patterns.
Operating boundaryThe workbench uses staged scenarios and synthetic service data; production use needs real monitoring adapters and access control.
Evaluation pathRun the local runtime commands and inspect the UI surfaces for service-impact and handoff clarity.

Evaluation Path

Architecture Notes

Public Demo Boundary

The public demo runs without external services:

The runtime is a deterministic React/Vite simulation, not a live network-management system. Production use requires approved telemetry adapters, identity and access controls, retained audit history, and operator validation.

Operational Scope

Why this project exists

This repo makes one operational model explicit:

  1. Network operations language should stay visible, not collapse into generic cloud dashboard copy.
  2. Incident handling and service-quality thinking should become an inspectable product surface.
  3. AX/automation should reduce operational noise without hiding the operator decision boundary.
  4. Operational discipline should connect to a carrier NOC context through concrete workflows.

What the operator sees

Carrier Operations Model

The UI and data model deliberately stay close to carrier operations concerns:

These concepts keep the simulation anchored to service assurance rather than generic infrastructure monitoring.

Operator Fast Path

  1. Open the default Metro Fiber Cut Recovery scenario.
  2. Read Command focus and Operator decision.
  3. Check the domain board for transport/core/IDC blast radius.
  4. Follow the E2E path to the VIP customer outcome.
  5. Scan the alarm queue and timeline.
  6. Finish on the capability board.

This path covers service impact, incident response, and operator-assisted automation without requiring customer data.

Quick Start

npm install
npm run dev

Open http://127.0.0.1:5173.

Verify

npm run verify

Cloudflare Deploy

This project is set up for Cloudflare Workers Static Assets with SPA routing.

npx wrangler login
npm run cf:deploy

For a deployment packaging check without publishing:

npm run cf:deploy:dry

The Wrangler config lives in wrangler.jsonc and serves ./dist with single-page-application fallback enabled.

Project Structure

src/
  App.tsx              main control surface
  data/scenarios.ts    synthetic carrier operations scenarios
  lib/format.ts        severity and status helpers
  test/                UI and utility tests

Private Incident Operations Exercise

The public workbench remains synthetic and read-only. A private, fixed-scope exercise can adapt the scenario pack, role and handoff map, evidence checklist, and after-action report to an approved operating context without accepting credentials or production payloads through GitHub.

Request a private incident exercise

Cloud + AI Architecture

Enterprise Productization

System Architecture

Service Architecture

Search And Service Surface