OSS/BSS Design

One of the most important requirements of all telecommunication companies is to have integrated OSS/BSS systems for managing all aspects of business from Customers to services and network equipment. In telecommunication business competition is in its highest level and technology is growing all the time, for being successful in this fast changing environment, your design and solution has to as flexible as possible to overcome these changes. TM Forum have been proposed a guideline as a name of NGOSS which has include all main and necessary rules for designing OSS/BSS systems.
According to TM Forum standards main rules to have an NGOSS are as follow:

  • Common Communication Vehicle (CCV): for integrating services or different systems.
  • Externalized Process Control (EPC): ability to separate business logic from implementing components.
  • Contract Defined Interface: it means that functionality like an interface has to be independent from technologies.
From Architecture perspective, NGOSS rules can be implemented by IT technologies. For example, 1st rule by EAI, 2nd one by BPM technology and the last one can be implemented by SOA technology. Our goal is to design OSS/BSS systems based on these technologies.
In the other hand which is business perspective, for designing OSS/BSS, TM Forum has been proposed e-TOM and TAM and SID reference models. e-TOM is and framework which includes business process in Telco domain and SID has all the information for implementing use cases based on specified process in e-TOM. In fact SID is a centralized and logical information model for guaranty consistency between OSS/BSS modules.
Possible Services for Designing OSS/BSS systems
  • Analyzing requirements
    • Future Goals and Policies
    • Gathering requirements through Interviews
    • Identifying organization’s special business process
  • Mapping requirements to e-TOM business process
    • AS-IS analysis
      • Operation analysis
      • Rules and responsibilities analysis
      • Current systems analysis
      • Identify issues and weakness
    • Gap analysis
  • Design Business Process Architecture (based on e-TOM)
  • Specify Business process characteristics
  • Design Workflows
  • Design Application Architecture (based on TAM)
  • Design Data Architecture (based on SID)
  • Design Disaster Recovery solution

Copyright© 2006 - 2015 Fava Pars Co., All rights reserved.