What a multi-site fiber operator's NOC looks like on CoreSync

The setting

An illustrative composite of the regional-operator pattern: half a dozen OLT sites across neighboring towns, a mixed Huawei-and-ZTE fleet acquired over years, thousands of ONUs, and a small NOC that used to work out of three vendor CLIs, a wall calendar and one veteran's memory of where every splitter hangs.

A fiber cut, minute by minute

The scenario that shows the difference. A trench crew cuts a distribution cable at midday:

• T+0: LOS alarms arrive from every ONU behind one splitter — the map flags the splitter itself, not thirty separate devices
• T+1 min: blast radius is on screen: one splitter, its cascade, the affected subscriber count and streets
• T+3 min: affected subscribers get a scoped outage SMS; the support queue stays quiet
• T+5 min: a technician is dispatched to a street corner, not to 'somewhere between site B and the stage'

The map turns 'the phones are ringing' into 'splitter S2, forty subscribers, this corner'.

The quiet days: optics as maintenance

Between incidents, the same data works as prevention. Per-ONU optical readings trend over weeks, so the NOC's morning view includes fibers that are degrading but not yet dead — a connector oxidizing, a bend some fundi introduced above a shop. Those become scheduled visits instead of midnight failures. Mixed-vendor optics read in one format, so the trend view doesn't care which chassis is watching.

What changed structurally

Three CLIs became one console, so new NOC hires learn the platform, not the fleet's purchase history. Plant knowledge moved from the veteran's head to the map, which survived his annual leave for the first time. And because the platform is priced per user on Premium, adding OLT sites and ONUs adds no platform cost, so the NOC watches the whole plant instead of rationing what it manages.