On Boarding Steps (Prime Detect)
On Boarding Steps (Prime Detect)
Top customer deliverables (prio 1–5)
Pilot plant model — nets, clusters, and key devices exist and are linked correctly
Icinga connected — host/service status visible in Detect for the pilot area
Topography & ERD signed off — map and hierarchy match the real plant for the pilot
Trouble board usable — NOC can see impairments, mute noise, and (if used) raise tickets
Monitoring pairing — operators know when to drill into Prime Monitoring Analysis
Scopes
Access
|
|
|---|---|
NMS brings | Detect package enabled; role templates for dashboard / maps / mute |
Customer brings | Named NOC owners and who may mute production impairments |
Decide | Who may edit topography / net-element positions |
Decisions
|
|
|---|---|
NMS brings | Recommended Icinga checks and map provider options |
Customer brings | Plant hierarchy, geo positions / KML, map API key if required |
Decide | Pilot clusters vs full-plant day one |
Initial data
|
|
|---|---|
NMS brings | Icinga wiring and tree-index support |
Customer brings | Net-element inventory, positions, cable plans |
Decide | Whether Ticket hooks are in scope at go-live |
Acceptance
|
|
|---|---|
NMS brings | Unit Test Protocol (Prime Detect) run on the tenant |
Customer brings | Sign-off that NOC can triage pilot impairments from Detect |
Decide | Exit criteria vs Monitoring / Ticket / Workforce waves |
Parent hub: Prime Detect