Network Operations Center Design

Today’s NOC solutions include rule-based processing of alarms from different sources, namely, nodes or service management systems or network/element management systems. Rules are written such that they convert the domain specific information into a general view of the network at the NOC and additionally they include hardcoded rules that process/correlate alarms for appropriate grouping.
Such rule development is time consuming and manually intensive. Continuous changes in the network with new types of network nodes and resulting new types of alarms, also make rule development and maintenance more complex. Further, rule generation/updates need to be done frequently; else the rule database will be incomplete or even inaccurate.

Does that mean we stop domain-oriented rule development?

This does not mean traditional rule development goes away, rather it will be augmented by domain independent data driven approaches. Additionally, automatic detection of possible correlations among alarms can augment the rule-based approach where rules are not complete or where the specific domain knowledge is yet to be acquired.
The data-driven approach will enable identification of cross-domain correlations and data-driven insight generation. Gradually, the system can evolve towards a fully automated solution.

Comments

Popular posts from this blog

difference between computer science and computer information systems

telecommunications network engineer

architect job description