DE

MO
MA
TE
RI
AL

2-1
 AL
RI
TE
MA

Telecom Equipment Manufacturers

Experience in managing Products belonging to different Development Life cycle
stages
Experience in Traditional as well as NGN systems
Clients: Leading equipment manufacturers
MO

Telecom Service Providers

Encompass the entire range from consulting to Systems Integration
Rich Customer Base: Varying from largest telcos in Tier 1 to many growing
clients belonging to Tier 3
DE

Independent Software Vendors

End to end solutions integration expertise: from product evaluation,
recommendations, business process re-engineering to COTS implementation
Relationship Transformation: Many a clients have chosen Tech Mahindra as a
preferred vendor

2-2
 DE
MO
MA
TE
RI
AL

2-3
 AL
RI
TE
MA

The telecom industry has seen tremendous advancements in the last few years, is still
evolving and yet at the same time is grappled by unexpected industry forces. The
above slide shows some of the most challenging times for the telcos across the globe
and to ensure sustainability in the market the operators will need to necessitate
changes to deal with the tough situation ahead.
MO
DE

2-4
 AL
RI
TE
MA

Marketing: Slow growth because processes and systems cant scale

Planning: Poor economies of scale because of using hundreds of suppliers
Engineering: Slow new service introduction because of high risks & costs to
make system changes
Customer Service: Weak customer service because of poorly integrated systems
MO

with inaccurate data

Sales: Poor time-to-revenue because of having rigid and inflexible business
processes
Finance: High manpower costs because of a lack of automated process flow-
through
DE

2-5
 AL
RI
TE
MA

The New Generation Operational Support System has evolved immensely. Existing
OSS fail to meet service providers demand in a mixture of products based OSS
ecosystem such as:
Thousands of discrete processes
Hundreds or thousands of discrete OSS/BSS applications
MO

Integration of multiple Applications to achieve automation of a single process

Limited by complexity of changing systems to keep up with process
enhancements
DE

2-6
 AL
RI
TE
MA

NGOSS is the TeleManagement Forum (TM Forum) 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 address operations, development, integration costs. Also
NGOSS adress future direction for Telecom service provider. It facilitate the rapid
MO

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.
With NGOSS, enable Telecom service provider to provide better customer service,
rapid service evolution, technology choices without OSS worries, and affordable and
DE

supportable OSS solutions.

2-7
 AL
RI
TE
MA

NGOSS design goals:

Focusing of corporate data
Physically and logically centralized data, providing more integrated views of
customer and operational data
Loosely coupled distributed systems
MO

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
DE

Because of those goals, service provider, OSS Software vendors, and system
integration need to implement NGOSS.

2-8
 AL
RI
TE
MA

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
MO

solution, or simply enable better lines of communication between a service provider

and their system integrator.
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
DE

turn allows easier and more effective integration across OSS/BSS software
applications provided by multiple vendors. The 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 diaframs to provide a system view of the information and
data.

2-9
Technology Neutral Architecture (TNA) and Contract Interface
In order to successfully integrate applications provided by mutiple 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
that operate sucessfully in a distributed enviroment; and the Contract Interface
definesthe "API" for interfacing those elements to each othe across the architecture.
This architecture is called specifically called "Technology Neutral" as it does not
define how to implement the architecture, rather what principles must be applied for

AL
a particular technology specific architecture to be NGOSS compliant.
NGOSS Compliance
In order to improve the probability that OSS components will truly intefrate with each

RI
other, NGOSS provides a suite of tests for compliance to the eTOM, SID, architecture,
and contract interface components. NGOSS compiance can be archieved any or all of
these components either singly, or in combination with other components.
TE
Practical implementations and demonstrations of these solutions through a series of
multi-vendor collaborative Catalyst projects
MA
MO
DE

2 - 10
 AL
RI
TE
MA

The Business Process Framework describes all the enterprise processes required by a
service provider. Thus, business needs MUST be the Driving Force NOT Technology
or systems.
MO
DE

2 - 11
 AL
RI
TE
MA

The Enhanced Telecom Operations Map (eTOM) starts at the high level process view
and then uses a hierarchical structure to breakdown each process according to where
they exist within the enterprise. The eTOM business process framework is a tool used
for process creation, process analysis, and process improvement.
Business Process Framework (eTOM) processes fall into three major process areas,[3]
as shown in the diagram:
MO

Strategy, Infrastructure & Product (SIP),

Columns: Strategy and Commit, Infrastructure Lifecycle Management
and Product Lifecycle Management
Rows: Marketing & Offer Management, Service Development &
DE

Management, Resource Development & Management and Supply Chain

Development & Management
Operations
Columns: Operations Support & Readiness, Fulfillment, Assurance and
Billing
Rows: Customer Relationship Management, Service Management &
Operations, Resource Management & Operations and Supplier/Partner
Relationship Management.
Enterprise Management.

2 - 12
 AL
RI
TE
MA

The above figure illustrates the Information Framework Level 1 Aggregate Business
Entity - ABE (blue border) that were presented in scope for the Assessment, and the
textual callouts represent the domain areas of the NetCracker Telecom Operations
and Management Solutions (TOMS) Suite that were assessed and support the
corresponding SID ABEs.
MO
DE

2 - 13
 AL
RI
TE
MA

The top layer (Layer 1) contains domains which are aligned with eTOM level 0
concepts.
Information Framework Domain Addenda:
MO
DE

2 - 14
 AL
RI
TE
MA

The Application Framework (TAM) is a sub-component of Frameworx, the TM Forums

blueprint for enabling successful business transformation. It provides a common
language and means of identification for buyers and suppliers across all software
application areas.
The Application Framework (TAM) provides a systems map which captures how
business capabilities are implemented in deployable, recognizable applications.
MO

The Application Framework provides a common language for communities who

specify, procure, design, and sell systems, so that they can understand each others
viewpoints. It provides logical groupings of applications, then describes each
applications functionality.
DE

As a result, it is a practical, everyday working guide to define and navigate the

elements of the complex management systems landscape.

2 - 15
 AL
RI
TE
MA

The NGOSS supports the following TNA

Requirements:
1. An NGOSS system must have re-useable software entities that offer their services
via open,well defined interfaces known as contracts.
2. An NGOSS system must have all its external dependencies explicitly defined.
MO

3. An NGOSS system must be characterized by a separation of the services offered

by the constituent components from the software that automates business
processes across the components.
4. An NGOSS system must support data stewardship. For each datum,there is a
steward that controls access and modification of the datum.
DE

5. An NGOSS system must support a common communication mechanism like Java

Message Service(JMS).

2 - 16
 AL
RI
TE
MA

The framework contains the policies, guidelines, documentation templates and

approaches to be used throughout the enterprise. In addition Enterprise Architecture
Management details the processes used to capture, modify, communicate, and
review the enterprise architecture and manage exceptions to it.
At the conceptual level, the framework has three major process areas, reflecting
major focuses within typical enterprises:
MO

Strategy, Infrastructure, and Product, covering planning and lifecycle

management
Operations, covering the core of operational management
Enterprise Management, covering corporate or business support management.
DE

2 - 17
 AL
RI
TE
MA

A key part of TM Forum Frameworx, the Information Framework (also known as SID),
provides an information reference model and a common vocabulary from a business
perspective. The Information Framework scope covers all of the information required
to implement business processes in a Service Providers operations based on the
Business Process Framework (eTOM) processes.
The Information Framework focuses on what are called business entity definitions
MO

and associated attribute definitions. A business entity is a thing of interest to the

business, such as customer, product, service, or network. Its attributes are facts that
describe the entity. Together, the definitions provide a business-oriented perspective
of the information and data that you need to run your organization. In short, the
Information Framework provides the model that represents business concepts and
DE

their characteristics and relationships, described in an implementation independent

manner.

2 - 18
 AL
RI
TE
MA

The following is description of the above figure:

1. Took business processes that were eTOM compliant as input to this stage and
modeled those as EEPC (Extended Event Process Chain) using process designer
tool.
2. Identified data requirement and mapped data with the process. Data mapping
MO

in Process Support gives more information along with the Action and Actor. This
was done by addressing questions like - What is the data required in the
process?, Where can one get the data?, What exact meaning of data?, Which
are the systems using this data?
3. Mapped SID on the NGN processes at high level using
DE

4. Made the Enterprise Data Model "Process Aligned"

2 - 19