NGOSS

NGOSS stands for New Generation Operations Systems and Software.
It is a business solution framework for creating next generation OSS/BSS software and systems.
The NGOSS program is delivering a framework for producing New Generation OSS/BSS solutions, and a repository of documentation, models, and guidelines to support these developments.
The goal of NGOSS is to facilitate the rapid development of flexible, low cost of ownership, OSS/BSS solutions to meet the business needs of today, cost conscious, competitive, and rapidly evolving telecom environment.

Overview of NGOSS

 

 

The key elements of NGOSS

 

• Enhanced Telecom Operations Map (eTOM)
  The eTOM provides the map and common language of business processes that are used in Telecom Operations. The eTOM can be used to inventory existing processes at a Service Provider, act as a framework for defining scope of a software-based solution, or simply enable better lines of communication between a service provider and their system integrators.

 

• Shared Information/Data Model (SID) The shared information and data model provides a “common language” for software providers and integrators to use in describing management information, which will in turn allows easier and more effective integration across OSS/BSS software applications i.e. COTS products provided by multiple vendorsThe SID provides the concepts and principles needed to defined a   shared information model, the elements or entities of the model, the   business oriented UML class models, as well as design oriented UML class models and sequence diagrams to provide a system view of the information and data from an overall perspective.

 

• Technology Neutral Architecture (TNA) and Contract Interface In order to successfully integrate applications provided by multiple software vendors, the ‘plumbing’ of the system must be common. The Technology Neutral Architecture defines architectural principles to guide OSS developers to create OSS components & systems that operate successfully in a distributed environment and the Contract Interface defines the “API” for interfacing those elements to each other across the architectural framework and components. This architecture is specifically called “Technology Neutral” as it does not define how to implement the architecture, rather what principles must be applied for a particular technology specific such that architecture is NGOSS compliant.

 

• NGOSS Compliance In order to improve the probability that OSS components will truly integrate with each other, NGOSS provides a suite of tests for   compliance to the eTOM, SID, architecture, and contract interface   components. NGOSS compliance can be achieved with any or all of these components either individually, or in combination with other components.

Benefits of NGOSS

• Service Provider’s sideIn addition to the factors that drive need for transformation, it is actually quite time-consuming and expensive to implement OSS systems for newer services based on NGN. The effort needed to maintain OSS is also significant with the current market trends. The NGOSS makes it easy to reuse and combine the functionality altogether if there are any customization (i.e additions or deletions) of modules in the OSS.NGOSS architecture is the best fit for SP as it supports rapid service deployment, flexible OSS architecture i.e. plug and play, customer centric management, well-done QoS management i.e., not neglecting decreasing operational costs and increasing revenue.

 

• System integrator’s sideThe term “Systems Integrator” (SI) is responsible for “the Integration Framework hence responsible for the integration and system test activities”. SIs like Wipro have strong experience in performing large- scale integration projects on variety of COTS products.It is not the best of the breed OSS that provide SP – a competitive advantage, however what matters is how well integrated OSS is with other OSS and how these OSS solutions are being used. SPs must execute such integration projects with SI partners who know their business very well and with whom they have strategic engagements & partnerships.These integration projects at SP’s premises are complex in nature and expensive. NGOSS provides a great relief for Sis involved. By pre-integrating and pre-configuring a set of products the cost and time-to- deployment gets reduced. That way, investments in operational costs of integration projects reduces substantially.

NGOSS design goals

• Focusing on corporate data
• Move away from stand alone OSSs to more of a common infrastructure for management process interaction.
• Application components/re-use
• Functional re-use of business process components .
• Code re-use of software components .
• Increased use of object oriented design.
• Improved development time, costs, etc.
• Multi-vendor supply and integration
• General purpose (cost effective) systems access
• Operational staff low cost access to data/processes
• Customer system interoperability to service provider data/processes
• Provides flexibility to rapidly produce new business solutions
• Allows more re-use of business components across multiple business scenarios
• Workflow automation
• Ability to automate present manual tasks
• Flexibility to change business process sequence
• Ability to integrate existing systems in OSS infrastructure
• Application of adaptation and wrapping techniques

 



For more about NGOSS
http://dpnm.postech.ac.kr/NGOSS/NGOSS.html