IBM Netcool Operations Insight · Enrichment & Automation

From raw event to resolved incident.

Netcool/Impact is the policy engine that gives every event meaning — and Runbook Automation is what acts on it. Together they turn a stream of alarms into contextualized incidents that increasingly resolve themselves.

The Policy Engine

Netcool/Impact: the platform's integration and automation hub.

Netcool/Impact is a highly scalable event-processing engine with an advanced policy engine. It looks up related data in external and business systems and adds it to events, applies advanced correlation, calculates KPIs, analyzes business impact, and drives notification and escalation — across every data source in your estate.

Because it can reach into any system and act on any event, Impact is the connective tissue of Netcool Operations Insight: the layer where a bare alarm becomes an incident that carries the context an engineer needs to resolve it — and the layer that triggers the automation to resolve it without one.

What Impact Does

Enrichment, correlation, and action.

Event enrichment

Impact looks up related information in external data sources — inventory, CMDB, customer, and business systems — and writes it back onto the event, so no operator has to go hunting for context.

Correlation & business impact

Policies correlate related events and translate technical faults into business impact — which service, which customers, which SLA — so the right incident rises to the top.

Notification & escalation

Impact drives notification and escalation workflows, making sure the right team knows the moment an event crosses the threshold that matters.

KPI calculation

The engine computes operational KPIs from live event and data streams, feeding dashboards and thresholds with the numbers that describe service health.

Runbook Automation

A disciplined path from manual to fully automated.

IBM's own recommended maturity model — earn trust at each step before removing the human from the loop.

  1. Manual
    Runbooks document the exact, repeatable procedure for a known condition — codifying tribal knowledge so any operator resolves it the same, correct way.
  2. Semi-automated
    An operator runs an automated task against the target from within the runbook — one click, no mistyped commands, full audit trail.
  3. Fully automated
    Triggers map events to runbooks that execute without operator interaction — routine conditions resolve themselves before a human is ever paged. Triggering runbooks from events runs through Netcool/Impact.

How AccuOSS delivers it

Policies and runbooks, tuned to your operation.

  • Enrichment policies wired to your CMDB and business systems

  • Correlation and business-impact rules for your services

  • Runbook libraries built from your operational procedures

  • A staged automation roadmap — manual, then semi, then full

  • ServiceNow and notification integrations, end to end

Automate the routine, not the judgment.

AccuOSS builds the enrichment policies and runbook libraries that let your team resolve incidents instead of chasing alarms.

Talk to our teamNetworks & Topology