Getting started
How the NOC runs
Imminent is how Yuno watches its network sites, finds what's down, and gets it fixed. This handbook covers how the operation is run, what each role does, and how to use every screen — by doing it.
Start with your role
How the operation runs
One chain of command, so every team works from one plan. The model is a simple military one: intelligence drives operations.
Imminent already does the analysis and the route planning, so people focus on decisions and on the work itself.
Region 8 at a glance
NOC operators cover areas, not projects, in two groups that match how the installer teams already work.
| Group | Provinces | Sites |
|---|---|---|
| Samar Group | Eastern Samar, Samar, Northern Samar | 699 |
| Leyte Group | Leyte, Biliran, Southern Leyte | 82 |
Who covers which area is on the org chart and in the NOC Operator guide (staff only). Region 4 runs as before for now.
Two kinds of work
Both run on the same installer teams, so the Region Lead splits team-days between them every week. Maintenance never drops to zero.
Maintenance
New Deployments
How each week is split is in How we work.
The five rules
One source of orders. Installer teams take orders from the Region Lead only. Every other request goes to the Region Lead, who adds it to the plan.
The Region Lead owns the team calendar. New Deployments asks the Region Lead for team-days. The CTO breaks ties.
Always keep one team on maintenance. At least one Samar team is never on New Deployments. The reserve team rotates weekly.
Own your area, then help. Once a NOC operator's area is clear, they take the oldest open ticket in the busiest area.
Don't leave until it's green. An installer team stays on site until the NOC operator confirms it's back online in Imminent.
Learn by doing
Each guide opens the real screen on made-up sites and walks you through it one click at a time.