Table of Contents
Role: Network Operations Manager #
INTERA does not replace NOC tools
Primary role objective: This tells the NOC lead which network problems actually matter — without drowning them in alarms.
After a week of using INTERA the NOC lead should say: “I stop jumping between systems just to understand if something is serious.”
Primary responsibility: Keep the network stable and customers unaffected — by prioritizing the right issues at the right time. This role does not fix problems. This role decides what matters now.
Daily questions this role must answer:
- Is the network healthy right now?
- Which alarms actually matter?
- Are customers or revenue impacted?
- Is this an incident or just noise?
- Do we need to escalate — and to whom?
Typical systems connected:
- Network monitoring (NMS / EMS)
- Performance & KPIs
- Alarm management
- Trouble ticketing
- Service inventory
- (Contextual) CRM & SLA data
The role package hides:
- Vendor alarm codes
- Raw KPIs
- Device-level metrics
- Protocol-level data
And exposes:
| Raw concept | INTERA term |
|---|---|
| Alarm storm | Network instability |
| Packet loss | Service degradation |
| Link flap | Intermittent risk |
| Threshold breach | Performance risk |
Documentation shipped with the role package:
