The NETeXPERT™ OSS framework provides users the ability to unify and manage resources. The OSS framework provides common components, "building blocks" which help in automating Network/Service Resource Management, Service Problem Management, Service Quality Management, and Service Delivery. These are operational processes which are defined by the TeleManagement Forum's enhanced Telecom Operations Map (eTOM). We will be discussing the eTOM in future blogs.

The NETeXPERT™ framework core components were first launched in the early 1990's and has incrementally been enhanced over the years. The framework is leveraged across ~70 or more service providers world-wide. The longevity of the framework throughout the world is primarily due to its proven track record especially in managing mission-critical resources. The framework is what supports the ability for service providers to implement a Unified Management Architecture (UMA). By leveraging a UMA one neutralizes the multi-vendor and multi-protocol management problem which allows Subject Matter Experts to focus on implementing applications for critical business and operational processes. Often the framework is called the glue or skeleton upon which applications are implemented.

Longview Software also provides tools, services, and consulting which compliment the NETeXPERT™ framework which we will discuss in future blogs.

Framework Definition

"In software development, a framework is a defined support structure in which another software project can be organized and developed. A framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project.... Frameworks are designed with the intent of facilitating software development, by allowing designers and programmers to spend more time on meeting software requirements rather than dealing with the more tedious low level details of providing a working system" http://en.wikipedia.org/wiki/Framework

The NETeXPERT™ rule writers and API developers over the last ~15 years have developed various applications to focus on OSS needs as identified in the "pyramid" below from resource management (equipment and topology), fault management (root cause correlation), performance monitoring (collection and real-time thresholds), automated-closed loop control (automated repair), service management (correlated measurements), service activation, discovery, trouble management, and customer impact.

Framework Common Components

The framework tools and common components provide a proven wide array of gateway integrations, adapters, open APIs, robust rules, policies, dynamic object modeling, and out-of-the-box as well as extendable Graphic User Interfaces. The framework components deal with the difficulties in managing different protocols such as SNMP, TL1, CMIP, CORBA, XML, TCP/IP, etc.. The components try to normalize various protocols reducing the tedious work of low level programming. Return for future blog topics around gateways.

Some CSPs leverage key components of the framework and wrap this with their own custom GUIs providing their internal users custom functions which can be modified easily. The framework, especially the rule language, accelerates the ability for an internal development team and/or a System Integrator to meet requirements by quickly implemeting operation and business logic.

From an end-user perspective the result is an application which meets their immediate needs and the fact that a framework is being leveraged is transparent to the end-user. This provides the CSP a unique balance between in-house custom development and building upon a proven framework. The resulting benefits include flexibility, stability, supportability, and the ability to meet competitive differentiation requirements in network, service, and business operations.

Add Comments