Infrastructure & Business monitoring
automates typical operations of
mobile operator NOC
What is Fault Management from NOC engineers point of view?
Service impact analysis
Examples are:
-
Analyze additional information from events. In case in event from switch “MSC RP Fault" there is additional status “ABL” or CBL” – it means there is impact on service.
-
Analyze number of events occurrences: if in 5 minutes 10 “switching termination fault” events have arose – 1 synthetic (service affecting) event will be generated and 10 resource events will be suppressed.
Root-cause analysis
-
Topology based;
-
Location basedl;
-
Other methods.
Business impact analysis
For example, by:
-
Site importance (government, normal customer);
-
Is switch intermediate or edge?;
-
Traffic volume;
-
SLA.
Automatic notification
-
Identify responsible group of engineers (using information about location and technology domain from event) and generate relevant to event subject and body of message.
Trouble ticket creation
-
Repair;
-
Proactive maintenance.
Other tasks
-
Site access control;
-
BTS Power Management.
Why I&B monitoring?
Many operators stops at Collect & Consolidate level
-
Events available from a single pane of glass;
-
Reduced number of events through deduplication and problem-resolution correlations;
-
Unified naming convention and event presentation;
-
But other operations NOC engineers still do manually!
We automate Service Assurance operations
-
Events categorization according to their impact on services;
-
Fault prioritization (in what time outage has to be restored);
-
Root-Cause analysis;
-
Intelligent trouble tickets creation and dispatching (manually and automatically);
-
Automatic service restoration.
WE OFFER
DESIGN
Scenarios & templates based on experience of other operators and your custom operations
IMPLEMENTATION
Scenarios & templates using Correlation Engine
INTEGRATIONS
With other OSS systems using REST, SOAP or other interfaces
IBM Netcool CUSTOMIZATION
As well as integrations with EMSs & NMSs