About Us  |  Membership |  Help
Sign In |  Register

Document Catalog

Guidebooks

GB942, NGOSS Contracts -Concepts and Principles, Release 1.0

Need Support? - Go to TM Forum's Online Community!
This guidebook focuses on the unification of the interface, information model activities with the NGOSS Contracts across the TM Forum ranging from framework to real implementation across all aspects of our industries business operations. The number of TM Forum teams and work products identified the need to clearly articulate the dependencies of the key NGOSS artifact: Information Framework (SID), Business Process Framework (eTOM), Application Framework (TAM), TM Forum Interfaces (TIP) and contracts in a SOA context ensuring a seamless migration to the future, which adhere to a common architecture.

This document provides a full definition for NGOSS Contracts from Business and System view. The document also provides direction for the Implementation view (TM Forum Interface Program) and for tooling (Tooling Taskforce and subsequent program work).

The document shows how contracts provide the necessary linkage between the key NGOSS artifacts (SID, eTOM, TAM) and the interface implementation.

NGOSS Contract extends SOA to recognize that there is a long lived relationship between specific client and server systems in the BSS/OSS environment. These systems are defined by the Application Map. SOA is also extended with granularity guidelines that derive from eTOM and finally the information model that is implemented in NGOSS Contracts is compliant with SID.

NGOSS Contracts add Service Level Agreements to the interface specification and record metrics against these SLAs.

The aim is to produce an interface specification for BSS/OSS that is expressed in the language of the Service Provider and can be implemented with a range of different technologies. Ideally the implementation will be compliant to a TMF standard, such as MTOSI, OSS/J or the result of the TMF Interface Program. The contract is technology agnostic providing the ability to harmonize disparate interface standards. The granularity fine or larger grained is based on the number of use cases it implements.

This concepts and principles identified in this book provide a single, adaptable, standardized solution environment that supports all necessary service operations across the entire range of properties for a converged network, operations and business continuum. Maintaining alignment of key NGOSS artifacts providing a solution environment that continuously supports the OSS/BSS needs through growth and change in network and service capabilities and through the evolution of implementation technologies.

We expect that TMF will manage real world, pragmatic Contracts based on the definition presented here using tooling so that the standards can be conformance and change controlled and so that the standards can be applied directly to integrations 

For further information on the Architecture Harmonization click here


                                                         To return comments on this document click here

Declaration of Patent Interest Form


If you would like help on this material or to join current discussions please visit the Community Area Integration Framework

Return to the Architecture Harmonization Home page