Provides overview of various standards adopted by Telecom ISP/ISV in Management and Monetization space. These standards provides open framework for OSS/BSS business processes to support interoperability and to avoid vendor lock-in
3. • Non-profit global consortium found in 1988 as OSI/Network Management
Forum renamed toTeleManagement Forum in 1998.
• Global industry association for digital business, connecting talented
individuals, leading companies, and diverse ecosystems to accelerate
members’ successful digital business transformation.
• 900+ market-leading organizations including Ericsson.
4. The Forum provides hands-on collaboration programs and
communities; thought-provoking research and publications; tools, best practices,
and standards such asTM Forum Frameworx™; conferences and workshops;
and training for business and IT leaders.
WHAT & WHY
To help member companies across a wide range of industries
address 3 major challenges
• Transform IT and operations to reduce cost, minimize risk, and improve
business agility and time to market
• Deliver new value-added services quickly, easily, and securely with partners
• Maximize market share and enhance customer engagement, loyalty and
growth
6. • Suite of best practices and standards that when adopted enable a service-
oriented, highly automated and efficient approach to business operations
providing.
• Hundreds of standardized Business Metrics.
• Suite of interfaces and APIs that enable integration across systems and platforms
• Adoption best practices to help companies implement and use the standards
• Management best practices to ensure ongoing conformance
What is ?
7. • Innovate and reduce time-to-market with streamlined end-to-end service
management
• Optimize business processes to deliver highly efficient, automated operations
• Reduce integration costs and risk through standardized interfaces and a
common information model
• Reduce transformation risk by delivering a proven blueprint for agile, efficient
business operations
• Gain clarity by providing a common, industry-standard language
WHAT CAN DO?
11. A hierarchical catalog of the key business processes required to run
a service-focused business.At the conceptual level, the framework has
three major process areas, reflecting major focuses within typical
Enterprises.
Strategy,
Infrastructure &
Product Operations Enterprise
Management
12. APPLICATION
Service Providers
The Business Process Framework
serves as the blueprint for process
direction. It also provides a neutral
reference point for internal
process reengineering needs,
partnerships, alliances, and general
working agreements with other
companies.
Vendors
The Business Process Framework
outlines potential boundaries of
software components that should
align with their customers' needs,
as well as highlighting the required
functions, inputs, and outputs that
must be supported by their
products.
13. Process Areas (Verticals)
• Strategy, Infrastructure, and Product (SIP) covering planning and lifecycle management
• Operations covering the core of day-to-day operational management
• Enterprise Management covering corporate or business support management
ETOM LEVEL 0 MODEL
Functional View (Horizontals)
– Market, Product, and Customer: High-level view of the market and the
enterprise’s offerings
– Service: Product components developed by the enterprise
– Resource (Application, Computing, and Network): Consumed in the
production of the Service
– Supplier/Partner: Providing products and services to the enterprise for the
production of the Service
15. • Shows seven end-to-end vertical process groupings required to support
customers and manage the business.
• The focus of eTOM is on the core customer operational processes of
Fulfillment,Assurance, and Billing (FAB).
• Operations Support and Readiness (OSR) is the “back-office” environment
that enables support and automation for FAB.
• The SIP processes do not directly support the customer and they include the
Strategy and Commit and the two lifecycle process groupings.
ETOM LEVEL 1 MODEL
20. Level 0: Business Activities that distinguish operational customer-
oriented processes from management and strategic processes
Level 1: Process Groupings including business functions and
standard end-to-end processes
Level 2: Core Processes that combine together to deliver
service streams and other end-to-end processes
Level 3:Tasks and associated detailed “success model” business
process flows
Level 4: Steps and associated detailed operational process flows
with error conditions and product and geographical variants
(where required)
Level 5: Further decomposition into operations and associated
operational process flows where required
..AND SO ON.
Functions
Processes
Tasks
Operations
22. • The Information Framework (SID) provides a reference model and
common vocabulary for all the information required to implement
Business Process Framework (eTOM) processes.
• It's part ofTMForum Frameworx
Model
INTRODUCTION
25. A common information model to streamline the processes associated with
information exchange, both within an Enterprise and between the Enterprise
and its external stakeholders.
• Provides common terminology across enterprise
• Unification of information with in and between enterprises.
• Bridge between business & IT groups.
WHY SID?
26. • An information model is useful:
• as a starting point for internal modeling work, applications and messages between
software components or database schemas.
• to help in defining a common business terminology, e.g. for integration activities
• to help in business transformation programs
• to help in understanding business concepts and their relationships
• as a source of inspiration for a new view on traditional practices
OBJECTIVES
27. • TMForum offers compliance services to Products and system implementations.
• Each assessment defines boundary of ABE's included in it.
• Assessment evaluation is done on two categories
• Information Framework Maturity Conformance Levels
• Information Framework Adoption Conformance Scores
• Maturity levels are based on progressive scoring system starting from lowest
level ABE.
• Adoption level recognizes overall adoption of information framework. It's based
on accumulative scoring system.
WHAT IS INFORMATION FRAMEWORK
(SID) COMPLIANCE ?
28. • EAI is one of very few NRM systems which are complaint to SID.
• ABE's in scope for assessment and its mapping with EAI objects.
IS GRANITE/EAI SID COMPLIANT?
29. • mapping of Ericsson’s Granite Inventory to the Information Framework ABEs
30. • As perTMForum web site, only NetCrackerTOMS is certified but on older
version of SID way back in 2011.
• EAI seems to be only full blown inventory solution which is certified on
latest version of SID. (Certified in April,2015).
Source: https://www.tmforum.org/certifications-awarded
OTHER PRODUCTS ?
32. THE ORIGINS OF
TOGAF®
A CUSTOMER INITIATIVE
A FRAMEWORK, NOT AN ARCHITECTURE
A generic framework for developing architectures to meet different business needs
Not a “one-size-fits-all” architecture
ORIGINALLY BASED ON TAFIM (U.S. DOD)
33. TOGAF STRUCTURE AND
COMPONENTS
• Architecture
Development Method
• Foundation
Architecture
• Resource Base
Building Blocks
Information
Base
(architecture
building blocks -
future)
Standards
Information
Base
(standards)
Technical
Reference
Model
(services taxonomy)
Architecture Development Method
Resource Base
Target
Architectures
TOGAF
Foundation
Architecture
34. ARCHITECTURE DEVELOPMENT
METHOD (ADM)
Open, industry
consensus
method for IT
architecture
Quick-start
foundation
Practical,
experience
based guidance
Requires
continual
validation
against
requirements
35. FOUNDATION ARCHITECTURE:
TECHNICAL REFERENCE MODEL (TRM)
• Associated with detailed
taxonomy of services
• defines scope of each
service category
• Identifies system-wide
capabilities (“qualities”),
e.g.:
• Internationalization
• Security
• Management
Qualities
Qualities
Network Services
Operating System Services
DataManagement
Location&Directory
Infrastructure
Applications
Business
Applications
DataInterchange
InternationalOperations
UserInterface
TransactionProcessing
System&NetworkManagement
Security
SoftwareEngineering
Graphics&Image
Communication Infrastructure
Application Programming Interface
Communications Infrastructure Interface
Qualities
Qualities
38. EVA - INTRO
• EVA is an internal Ericsson tool.
• Best of both worlds – External & Internal
• Amalgamation of best of Industry Standards into one unified architecture.
• From mere standard to implementation architecture.
• Rich with real world application perspective.
• Ever improving and intelligent
evaeva
39. Current State Target & or Interim State
Inefficient Operations
High Churn, Long Time to Market
Innovation Limitations
“Spaghetti”-like Application &
Technology Landscape
Value Oriented Projects
Optimized Operations
Improved Customer Experience
Opex Reduction
Data Monetization
Voice Transformation
Order To Cash/Plan to Provision
Best In Class solutions
EVA: transformation
driver
E2E ICT view
Global Best
Practices
Industrialization
Enabler
Communication
Facilitator
EVA Vision
40. EVA AND TOGAF
A business strategy
is implemented…
By offering business
processes…
That run data &
information…
Managed by functions and
applications…
Deployed on a technology
network & platform
Enterprise
Architecture is the
explicit description
and documentation
of the current and
desired relationships
among strategy,
business processes,
information,
applications &
technology.
41. EVA AND TMFORUM
FRAMEWORX
TMF
EVA
Process
E2E L1 Processes
aligned; eTOM L3
processes leveraged to
create EVA E2E Flow
Models
eTOM(plus)
EVA Process Map
Application
Functional Domains and L1
aligned; Functional
Decomposition into 3 levels
TAM
EVA Functional Map
Information
SID ABEs leveraged to
create EVA Information
Model.
SID
EVA Information Map
