FieldOps Telemetry Dashboard
One live view for alarms, fiber routes, and crew dispatch — built for the NOC wall and the technician's phone alike.
Project Overview
During outages, the NOC juggled five tools: alarms in one, fiber records in another, crew locations in a group chat. FieldOps pulls them together into a single incident view with a live map, per-circuit history, and dispatch tracking.
I designed the data model, built the React front end and the Node ingestion services, and ran usability sessions with NOC techs between shifts to keep every screen operable at 3am.
- •Incident view in under 3 clicks
- •Works on wallboard and mobile
- •Shift-handoff notes built in
The Challenge
My own NOC internship made the pain concrete: fiber-cut triage meant cross-referencing alarms against stale spreadsheets while the clock ran on SLA credits. Anything I built had to be faster than the sticky-note workflow it replaced.
- Five disconnected tools and no shared incident context between NOC shifts and field crews.
- Fiber records that lagged reality, sending crews to the wrong manhole during active outages.
- Shift handoffs lost in chat scrollback, with follow-ups falling through the cracks between teams.
Approach & Delivery
1 · Incident-first design
Every screen answers one question: what is broken, where, and who is on it. Alarms, affected circuits, route maps, and assigned crew share a single incident timeline.
2 · Live ingestion
Streaming connectors normalize alarms, telemetry, and dispatch updates into one event bus, so the wallboard, desktop, and phone views never disagree.
3 · GIS-backed routes
Fiber paths render on a real map with splice points and access notes, giving crews turn-by-turn context instead of a manhole number in a spreadsheet cell.
4 · Handoff built in
Shift notes attach to incidents, not chats. Incoming techs get a generated brief: open items, waiting crews, and next actions — nothing lives only in someone's head.
Outcomes & Deliverables
- Triage starts from one URL instead of five logins, and new NOC techs reach confidence in days rather than weeks.
- Field crews arrive with route context and access notes, cutting wrong-site dispatches on fiber events.
- Documented API and connector SDK, so new telemetry sources plug in without touching the front end.
Related Work
Need operations tooling your team will actually use?
I design with the night shift in mind — fast, legible, and forgiving.
Get started