User Stories (Prime Detect)

Business stories for Prime Detect. Plain language for customers, NOC, and delivery.

1. See impairments at a glance

As a NOC engineer, I want a dashboard of impaired plant elements with severity and affected modems, so that I prioritise the right cluster first.

Done when: Detect / Trouble Dashboard shows live impaired hosts/services with counts.

2. Mute known noise

As ops, I want to mute a problem that is already understood, so that the board stays actionable during planned work.

Done when: Mute from the trouble board hides or flags the problem as muted.

3. Topography matches the plant

As a planner, I want nets and devices on a geo map, so that field and NOC share one picture of the plant.

Done when: Topography MAP shows the pilot net/cluster with positioned elements.

4. ERD for hierarchy

As a plant engineer, I want an entity-relation diagram of nets and clusters, so that I understand upstream dependencies during an outage.

Done when: ERD opens for a known net and shows child relationships.

5. Customers under the fault

As support, I want to see customers / modems on the map under an impaired element, so that I can answer “who is affected?” quickly.

Done when: Customer geo context is available when provisioning data is present.

6. Icinga truth in NMS Prime

As delivery, I want Icinga host/service state visible inside Detect, so that operators do not need a separate monitoring UI for day-to-day triage.

Done when: Icinga object lists and state history open for a known host.

7. Jump to deep analysis

As NOC, I want to move from an impaired cluster into Monitoring Analysis for a modem or NetGw, so that I confirm RF detail before sending a truck.

Done when: From Detect context, operators can open Monitoring Analysis on a related device.

8. Raise work from an impairment

As ops, I want ticket hooks from the trouble board, so that impairments become tracked work.

Done when: With Ticket enabled, impaired items can be linked or raised as tickets.