Telecom Operation

Enhanced Telecom Operations Map
(eTOM)
The Business Process Framework
For The Information and Communications Services Industry
Addendum F:
Process Flow Examples
Release 4.5
GB921 F
Member Evaluation
November 2004
TeleManagement Forum 2004
eTOM Business Process Framework, Addendum F
Page 2
Notice
The TeleManagement Forum (TM Forum) has made every
effort to ensure that the contents of this document are
accurate. This document is a draft working document of TM
Forum and is provided to the public solely for formal
comments and evaluation. It is not a Forum Approved
Document and is solely circulated for the purposes of
assisting TM Forum in the preparation of a final document in
furtherance of the aims and mission of TM Forum.
Any use of this document by the recipient is at its own risk.
Under no circumstances will TM Forum be liable for direct or
indirect damages or any costs or losses resulting from the use
of this document by the recipient.
This document is a copyrighted document of TM Forum.
Without the appropriate permission of the TM Forum,
companies that are not members of TM Forum are not
permitted to make copies (paper or electronic) of this draft
document other than for their internal use for the sole purpose
of making comments thereon directly to TM Forum.
This document may involve a claim of patent rights by one or
more TM Forum members, pursuant to the agreement on
Intellectual Property Rights between TM Forum and its
members, and by non-members of TM Forum.
Direct inquiries to the TM Forum office:
89 Headquarters Plaza North, Suite 350
Morristown, NJ 07960, USA
Tel.: +1 973-292-1901
Fax: +1 973-993-3131
TM Forum Web Page: www.tmforum.org
GB921F v4.6
Page 3
Acknowledgements
See main document (GB921 v4.5) for acknowledgements.
Particular thanks go to Jane Hall of Fraunhofer Fokus who handled editing of the
release 4.0 document, and integrated comments and suggestions into the final form
shown here. This task requires insight and an ability to balance and combine
suggested changes into a result that can find consensus amongst those involved, and
the efforts involved are much appreciated.
Thanks also to Viviane Cohen of Amdocs who coordinated the work on the new
material in GB921F 4.5 and also edited the updates.
GB921F v4.6
Page 4
About TeleManagement Forum

TeleManagement Forum is an international consortium of communications service
providers and their suppliers. Its mission is to help service providers and network
operators automate their business processes in a cost- and time-effective way.
Specifically, the work of the TM Forum includes:
Establishing operational guidance on the shape of business

processes.
Agreeing on information that needs to flow from one process activity
to another.
Identifying a realistic systems environment to support the
interconnection of operational support systems.
Enabling the development of a market and real products for
integrating and automating telecom operations processes.
The members of TM Forum include service providers, network operators and suppliers
of equipment and software to the communications industry. With that combination of
buyers and suppliers of operational support systems, TM Forum is able to achieve
results in a pragmatic way that leads to product offerings (from member companies)
as well as written specifications.
GB921F v4.6
Page 5
GB921F v4.6
Page 6
About this document

This is a TM Forum Guidebook. The guidebook format is used, for example, when the
document lays out a core part of TM Forums approach to automating business
processes.
Document Life Cycle

The Enhanced Telecom Operations Map (eTOM) The Business Process Framework
For The Information and Communications Services Industry is being issued as a TM
Forum Version Release 4.5 with a Guidebook Number of 921F.
See main document (GB921 v4.5) for further information.
Time Stamp
This version of the eTOM Business Process Framework can be considered valid until
it is updated or replaced.
How to obtain a copy

An electronic copy of the eTOM Business Process Framework can be downloaded at
the TM Forum Web Site (http://www.tmforum.org). Contact the TM Forum office (see
previously for contact details, or via the web site) for any further information.
How to comment on the document

Comments must be in written form and addressed to the contacts below for review with the project
team. Please send your comments and input to:
Enrico Ronco, Telecom Italia Lab
Team Lead of eTOM Team
enrico.ronco@telecomitalia.it
Mike Kelly, TM Forum
eTOM Program Manager
mkelly@tmforum.org
GB921F v4.6
Page 7
Please be specific, since your comments will be dealt with by a team evaluating numerous
inputs and trying to produce a single text. Thus, we appreciate significant specific input. We are
looking for more input than word-smith items, however editing and structural help are greatly
appreciated where better clarity is the result.
Document History
Version
eTOM
Version 3.5
Addendum F
eTOM
Version 3.6
Addendum F
eTOM
Version 4.0
Addendum F
eTOM
Addendum F
Release 4.5
Version 4.6
Date
07/03
Purpose
Launched as an Addendum to the main eTOM
GB921 v3.5 document, to improve readability.
11/03
Released for public review and comment. No

changes to technical content from v3.5
2/04
Updated to reflect the process decompositions of

GB921D version 4.0.
08/04
Updated to include new process flows concerning

billing, and also to update some existing material
11/04
Updates prior to Release 4.5 Member Evaluation
Summary of Changes in this Version

See main document (GB921 v4.5) for change information.
GB921F v4.6
Page 8
References
Related or Source Documents

F1. SLA Management Handbook, TMF, GB917, Public Evaluation Version 1.5
See main document (GB921 v4.0) for additional references.
GB921F v4.6
Page 9
Table of Contents
NOTICE .....................................................................................................................................................................................2
ACKNOWLEDGEMENTS ......................................................................................................................................................3
ABOUT TELEMANAGEMENT FORUM .............................................................................................................................4
ABOUT THIS DOCUMENT....................................................................................................................................................5
DOCUMENT LIFE CYCLE ...........................................................................................................................................................6
TIME STAMP .............................................................................................................................................................................6
HOW TO OBTAIN A COPY ...........................................................................................................................................................6
HOW TO COMMENT ON THE DOCUMENT ....................................................................................................................................6
DOCUMENT HISTORY ...............................................................................................................................................................7
SUMMARY OF CHANGES IN THIS VERSION ................................................................................................................................7
REFERENCES ..........................................................................................................................................................................8
RELATED OR SOURCE DOCUMENTS ..........................................................................................................................................8
TABLE OF CONTENTS ..........................................................................................................................................................9
TABLE OF FIGURES AND TABLES ..................................................................................................................................11
PREFACE ................................................................................................................................................................................13
ETOM BUSINESS PROCESS FRAMEWORK ...............................................................................................................................13
CHAPTER 1 - INTRODUCTION..........................................................................................................................................15
CHAPTER 2 - BILLING-RELATED FLOWS ....................................................................................................................17
PREPAID BILLING ...............................................................................................................................................................17
CONTEXT ................................................................................................................................................................................17
FEDERATED BILLING ........................................................................................................................................................21
CONTEXT ................................................................................................................................................................................21
Scenario description ..........................................................................................................................................................22
Pre Conditions...................................................................................................................................................................22
Post Conditions..................................................................................................................................................................22
Process Flow ( eTOM Level 3 processes)..........................................................................................................................23
ADVICE OF CHARGE ..........................................................................................................................................................24
CONTEXT ................................................................................................................................................................................24
Scenario description ..........................................................................................................................................................24
Pre Conditions...................................................................................................................................................................24
Post Conditions..................................................................................................................................................................25
Process Flow (eTOM Level 3 processes)...........................................................................................................................25
ETOM LEVEL 3 PROCESSES INVOLVED IN BILLING FLOWS ................................................................................26
MANAGE COLLECTION ...........................................................................................................................................................26
MEDIATE USAGE RECORDS ....................................................................................................................................................26
RATE USAGE RECORDS ..........................................................................................................................................................27
PROCESS RESOURCE DATA (RM&O AB) ............................................................................................................................27
GB921F v4.6
Page 10
APPLY PRICING, DISCOUNTING & REBATE .............................................................................................................................27

CHAPTER 3 DSL FULFILLMENT PROCESS FLOWS ................................................................................................28
DSL FULFILLMENT ASSUMPTIONS .........................................................................................................................................28
DSL FULFILLMENT PROCESS INTERACTIONS .........................................................................................................................28
DSL FULFILLMENT PROCESS FLOWS......................................................................................................................................29
CHAPTER 4 PLM PROCESS FLOWS .............................................................................................................................33
PLM ASSUMPTIONS ...............................................................................................................................................................33
PLM PROCESS INTERACTIONS ................................................................................................................................................34
APPLICATION OF SIP BUSINESS PROCESSES ...........................................................................................................................35
Approach ...........................................................................................................................................................................35
PLM PROCESS FLOWS ............................................................................................................................................................36
CHAPTER 5 SLA PROCESS FLOWS ..............................................................................................................................39
SLA ASSUMPTIONS ................................................................................................................................................................39
SLA PROCESS INTERACTIONS ................................................................................................................................................40
Normal Execution ..............................................................................................................................................................40
Execution with SLA Violation ............................................................................................................................................42
Assessment.........................................................................................................................................................................42
SLA PROCESS FLOWS ............................................................................................................................................................45
Normal Execution ..............................................................................................................................................................45
Execution with SLA Violation ............................................................................................................................................50
Assessment.........................................................................................................................................................................54
GB921F v4.6
Page 11
Table of Figures and Tables

Figure 2.1: Billing flow prepaid: Authorization request /balance reservation (enough balance) ..18
Figure 2.2: Billing flow Authorization Request/Balance reservation (not enough balance).........19
Figure 2.3: Billing flow prepaid: Debit request...................................................................................20
Figure 2.4 Business Relationship Context for Federated Billing .....................................................21
Figure 2.5 Federated Billing Flow........................................................................................................23
Figure 2.6 Level 3 Process Flow Advice of Charge ..........................................................................25
Figure 3.1: Fulfillment Process Interactions ......................................................................................29
Figure 3.2a: Pre-Sales Level 2 Process Flow .....................................................................................30
Figure 3.2b: Pre-Sales Process Dynamics Flow ................................................................................30
Figure 3.3a: Ordering Level 2 Process Flow ......................................................................................31
Figure 3.3b: Ordering Process Dynamics Flow .................................................................................31
Figure 3.3c: Ordering Process Dynamics Flow: Status Updates .....................................................32
Figure 3.4a: Post-Ordering Level 2 Process Flow .............................................................................32
Figure 4.1: Scope of Product Lifecycle Management........................................................................33
Figure 4.2: Example of PLM Process Interactions.............................................................................34
Figure 4.3: Different Scopes for PLM..................................................................................................35
Figure 4.4: Approve the Development of a New Product (pre-approval) .........................................37
Figure 4.5: Develop New Product or Modify an Existing One (post-approval)................................38
Figure 5.1: Product/Service and Associated SLA Lifecycle .............................................................39
Figure 5.2: Normal Execution of SLA Service Case A: Performance Data during Normal Operation
........................................................................................................................................................41
Figure 5.3: Normal Execution of SLA Service Cases B and C: Threshold Crossing Alerts and
Resource Failure Alarms ..............................................................................................................41
Figure 5.4: Customer Detected SLA Violation....................................................................................42
Figure 5.5 Assessment Initiation Case A: Customer Needs Have Changed ...................................43
Figure 5.6 Assessment Initiation Cases B and C: Internal Assessments at the Customer and Service
Layers.............................................................................................................................................43
Figure 5.7: Normal Execution of SLA Service Case A: Performance Data during Normal Operation
........................................................................................................................................................46
Figure 5.8: Normal Execution of SLA Service Cases B and C: Threshold Crossing Alerts and
Resource Failure Alarms. Steps 1 to 17 ......................................................................................48
Figure 5.9: Normal Execution of SLA Service: Cases B and C: Threshold Crossing Alerts and
Resource Failure Alarms. Steps 18 to 26 ....................................................................................49
Figure 5.10: Customer Detected SLA Violation. Steps 1 to 16d .......................................................51
Figure 5.11: Customer Detected SLA Violation. Steps 17 to 26........................................................53
Figure 5.12: Assessment Initiation Case A: Customer needs have changed..................................55
GB921F v4.6
Page 12
Figure 5.13: Assessment Initiation Cases B and C: Internal Assessments at the Customer and
Service Layers ...............................................................................................................................56
GB921F v4.6
Page 13
Preface
eTOM Business Process Framework

The eTOM Business Process Framework is a reference framework for categorizing all
the business activities that a service provider will use. This is done through definition of
each area of business activity, in the form of process components or Process
Elements that can be decomposed to expose progressive detail. These process
elements can then be positioned within a model to show organizational, functional and
other relationships, and can be combined within process flows that trace activity paths
through the business.
The eTOM can serve as the blueprint for standardizing and categorizing business
activities (or process elements) that will help set direction and the starting point for
development and integration of Business and Operations Support Systems (BSS and
OSS respectively). An important additional application for eTOM is that it helps to
support and guide work by TM Forum members and others to develop NGOSS
solutions. For service providers, it provides a Telco industry-standard reference point,
when considering internal process reengineering needs, partnerships, alliances, and
general working agreements with other providers. For suppliers, the eTOM framework
outlines potential boundaries of process solutions, and the required functions, inputs,
and outputs that must be supported by process solutions.
The eTOM Business Process Framework has grown to include a number of
components. The overall eTOM document set includes:
A main document (GB921) that provides an overview of the eTOM

Business Process Framework, from both Intra-Enterprise and InterEnterprise viewpoints, and describes the main structural elements and
approach
An Addendum (GB921D) describing the Service Provider enterprise
processes and sub-processes in a form that is top down, customercentric, and end-to-end focused. Process decompositions are
provided for all processes from the highest conceptual view of the
eTOM framework to the level of detail agreed for use by the industry.
An Addendum (GB921F) describing selected process flows at several
levels of view and detail that provides end-to-end insight into the
application of eTOM.
An Addendum (GB921B) describing the implications and impact of
ebusiness for service providers and their business relationships, and
how eTOM supports them, including a description of handling of
business to business Interactions by eTOM. Associated with this is a
separate Application Note (GB921C) describing a Business
Operations Map for processes involved in business to business
interaction
GB921F v4.6
Page 14
A separate Application Note (GB921L) that shows how eTOM can be

used to model the ITIL processes
An Addendum (GB921P), not included at time of release in the GB921
v4.0 document set, providing an eTOM Primer to assist new users of
eTOM
A separate Application Note (GB921T), not included at time of release
in the GB921 v4.0 document set, that shows how eTOM processes
relate to the functional view provided by the ITU-T M.3400
Recommendation (this work was developed in conjunction with ITU-T
within the joint Telecom Management Collaboration Focus Group)
Note:
Addenda are adjuncts to the main document that are presented separately, to avoid a
single document becoming cumbersome due to its size.
Annexes and Appendices both allow material to be removed from a document body,
so that the reader is not distracted from the document flow by too much detail.
However, these have different statuses within a document: Annexes have equivalent
status to the material within the body of the document, i.e. an Annex represents a
formal agreement and requirements for the users of the document. Appendices
contain material included for information or general guidance. Also, Addenda have the
same status as Annexes.
Thus, a document body, together with its Annexes and Addenda (and their Annexes, if
any), represents the normative material presented, while any Appendices in the main
document or its Addenda represent non-normative material, included for information
only.
In addition, Application Notes are a specific document type, used to provide insight into
how a specification or other agreed artifact is used in a particular context or area of
application. They are non-normative as they provide information and guidance only
within the area concerned.
GB921F v4.6
Page 15
Chapter 1 - Introduction
This document stands as an Addendum to the " Enhanced Telecom Operations Map
(eTOM) The Business Process Framework For The Information and Communications
Services Industry", GB921 Version 4.0. It provides additional insight into the eTOM
framework and its application through the description of some example business
scenarios, or applications, in which the eTOM framework is applied, and shows
process flows and related information that demonstrate how the eTOM processes
interact in these situations. It should be read in conjunction with the main GB921
document and other Addenda (see GB921 for details).
A number of example scenarios are described in this document. These can be
considered as "Use Cases", if this terminology assists, with a business, rather than an
implementation, perspective since the eTOM framework and these scenarios seek to
define the business requirements rather than a particular solution that addresses these
requirements. Nevertheless, since these scenarios are examples, certain assumptions
have been made about the nature of the business problem concerned, and it should
be stressed that these assumptions do not imply that the eTOM framework can only
be applied in the context described. Instead, these are intended to provide insight for
the cases considered, but many other scenarios and examples can be addressed, and
it is hoped that as the work on the eTOM framework progresses, a growing library can
be assembled on these.
It should be emphasized that the example scenarios shown here are not to be viewed
as normative in the sense that the recommendations embodied in the main eTOM
document are normative these scenarios are examples to illustrate how to apply the
eTOM framework.
The value of information is confirmed when it is put to use. The eTOM framework has
many possible applications, but the most obvious way to use a framework of Process
Elements is to use it to guide the design of actual Process Flows that deliver value for
the Enterprise.
To appreciate this, it is important here to differentiate between Process Flows and
Process Elements, especially from the point of view of how they relate to standardizing
processes.
The Process Elements in the eTOM framework are intended as an exhaustive list,
i.e. an enterprise uses only the eTOM process elements when categorizing business
activities within process implementations. Should an exception arise where some
activity is identified as not being supported by (i.e. able to fit within) any existing
process element, then a new process element would be created and added to the
eTOM framework in order to maintain its role as a comprehensive process framework.
The Process Flows represent the way that the business activities (in the form of the
process elements) can work together to satisfy a particular need. An exhaustive list of
process flows will never be completed because needs are continually changing, but
this is not an issue as the individual scenarios, and the process flows developed
around them, provide insight that contributes to an enhanced understanding of how
the eTOM framework can be used. What is important for an enterprise that is trying to
GB921F v4.6
Page 16
improve its efficiency by re-using its process and IT capabilities, is that it must ensure
that process flows are built using business activities that are categorized using only the
eTOM process elements.
The example scenarios described in this Addendum make use of a tried and proven
method intended to ensure that process flows can be built using the eTOM process
elements in order to address the actual business needs identified in each case.
For the scenarios included here, some description is included with each explaining the
scenario concerned and its scope of application.
A number of diagrams have been developed to assist in fleshing-out these scenarios.
The first scenario, on Fulfillment, explains the use of these.
Many of the diagrams are produced with the aid of a process analysis tool, and some
of the conventions involved may not be obvious. The flow diagrams are organized into
"swim lanes" or horizontal tracks that follow the layers visible in the eTOM framework
(e.g. CRM, SM&O, etc). This is done to assist readers by positioning processes in their
familiar relative orientation as seen in the eTOM structure. Within each swim lane,
individual processes are then shown with interactions that link the processes within
and between the swim lanes. Note that these interactions are primarily concerned with
event transitions, i.e. the interaction is labeled to identify the event that causes the
transition from the originating to the destination process. This transition may imply
transfer of information, but it is not the primary purpose of the labeling to highlight the
information that may be involved. This reflects the reality that other mechanisms for
information sharing (e.g. access to common databases) may be involved and are
documented separately. Also, the binding of information with process has
implementation implications and therefore needs to be done in recognition of potential
implementation choices. Further work on these information aspects is underway in
conjunction with other work and activities within TM Forum, and will be documented in
due course.
Process flows are initiated and terminated in the diagrams by boxes that may be
shown outside of the swim lane area. Arrowed boxes pointing right-wards indicate
Events (initiating a flow), while arrowed boxes pointing left-wards indicate results
(terminating a flow). As flow diagrams can become very extended, in some cases
these have been broken into sub-flows for convenience. These can then be linked
together via Events and Results, as indicated.
GB921F v4.6
Page 17
Chapter 2 - Billing-Related Flows
Prepaid Billing
Context
A customer is using his prepaid mobile device to make a voice phone call that does
not involve roaming.
During this call, events are being generated by network equipment. Those events are
sent to a real time system that will identify the customer account, check the balance,
authorize (or not) the call and decrease the balance accordingly.
Note: The scenario described below only focus on the billing aspects of a larger
scenario that would be the setting and rating of prepaid voice call. The network
aspects are not discussed here.
Scenario 1: Authorization Request/Balance reservation (enough balance) description
The end user places a call using a prepaid account. Events being generated are
authorization request for the call with balance reservation. There is enough balance for
the duration implied by the reservation request.
The flow below (see Figure 2.1) is repeated for the duration of the call.
Pre Conditions
The end user uses a prepaid account
The end user places a voice call
There is a sufficient balance for the duration of the call implied by the reservation request
Post Conditions
There is a balance reservation
The end user is still talking on his voice call
GB921F v4.6
Page 18
Process Flow (eTOM Level 3 processes)

Authorization Request /
Balance Reservation
Request for prepaid call

authorization/balance
reservation
Market
Product &
Customer
Apply Pricing,
Discounting &
Rebate
Manage
Collection
Service
Mediate Usage
Records
Resource(A
pplication,
Computing
and
Network)
Process
Resource Data
Rate Usage
Records
Report
Resource Data
Supplier/
Partner
Authorize
Call
Reserve
Balance
Figure 2.1: Billing flow prepaid: Authorization request /balance reservation (enough balance)
Scenario 1a: Authorization Request/Balance reservation (not enough balance) description
The end user places a call using a prepaid account, or the end user has placed a call
already. Events being generated are authorization request for the call with balance
reservation. The balance of the prepaid account has reached zero or a negative value,
therefore the call cannot be authorized anymore. A non authorization event will be
generated.
Pre Conditions
The end user has a prepaid account
The end user places a voice call
There is no sufficient balance for the duration of the reservation requested (according to policy of
the SP).
Post Conditions
The call was rated correctly
The balance has been decreased for the correct amount and reached 0 or less.
The call is cut because of a zero or negative balance
GB921F v4.6
Page 19
Process Flow (eTOM level 3 processes)

Billing Flow Prepaid Scenario 1a
balance re se rvation (not enough
balance)
Request for prepaid call

authorization/balance
reservation
Market
Product &
Customer
A pply Pricing,
Discounting &
Rebate
Service
Resource(Ap
plication,
Computing
and Netw ork)
Mediate Usage
Records
Process Resource
Data
Manage Collection
Rate Usage
Records
Report Resource
Data
Supplier/
Partner
Call not Authorized
Figure 2.2: Billing flow Authorization Request/Balance reservation (not enough balance)
Scenario 2: Debit Request description
The end user is finishing a call using a prepaid account. A debit request events was
generated for charging the call, i.e; decreasing the balance. (see Figure 2.3). Balance
has been previously reserved, the call is rated correctly and the balance is decreased,
the reservation is released. There is enough balance for the duration of the call.
Pre Conditions
The end user uses a prepaid account
The end user has ended a voice call
There was sufficient balance for the duration of the call.
Post Conditions
The call has terminated normally
The call was rated correctly
The balance has been decreased for the correct amount
The balance reservation made for this call is released
GB921F v4.6
Page 20

De bit Request
Debit Request
Release
Balance
reservation
Decrease
Balance
Market
Product &
Customer
A pply Pricing,
Discounting &
Rebate
Manage Collection
Service
Mediate Usage
Records
Rate Usage
Records
Resource(Ap
plication,
Computing
and Netw ork)
Process Resource
Data
Report Resource
Data
Supplier/
Partner
Figure 2.3: Billing flow prepaid: Debit request
GB921F v4.6
Page 21
Federated Billing
Context
The business relationship model of this scenario is that of a Mobile Portal Service
Provider providing services to customers, some of which are provided by third party
service providers. As a service aggregator, the Mobile Portal Service Provider
undertakes order handling and subscription, customer care, QoS monitoring, and
billing functionality associated not only with the services of the Mobile Portal Service
Provider but also with the services from third party service providers that it offers via its
portal. Customers can access their services wherever they are located as a
subscription with the Mobile Portal Service Provider includes network access (see
Figure 2.4). The customers have postpaid accounts and receive a regular, for example
monthly, bill.
Customer
Contractual
Relationships
Mobile Portal
Service Provider
ThirdParty
Party
Third
Third
Party
Service
Service
Service
Provider
Provider
Provider
Mobile
Mobile
Network
Mobile
Network
Operator
Network
Operator
Operator
Figure 2.4 Business Relationship Context for Federated Billing

In order to bill customers for the services they use, the charging model for each of the
services has to be known. If service usage is charged for, the usage data needs to be
collected and processed so that the usage records can be used for rating and
charging purposes. As the Mobile Portal Service Provider is the service provider
issuing the individual bills to customers for their usage of all the services they are
subscribed to, it requires charging data to be sent to it by the third party service
providers and mobile network operators that can be aggregated into a single bill for
each customer.
It is anticipated that further work will be done on the Federated Billing

scenario to give it a more generic use. A new role of Billing Aggregator may need to
be defined to cover the functionality currently contained in the Mobile Portal Service
Provider and a clearer understanding of the relationship between the Billing
Aggregator, the Service Content and Network Providers and the Customer established
GB921F v4.6
Page 22
Scenario description
The customer uses services that have been subscribed to. After the services have
been used the required usage and charging data is sent from third party service
providers / mobile network operators to the Mobile Portal Service Provider for
incorporation into a single bill for the customer.
Pre Conditions
The contracts between the Mobile Portal Service Provider and the third party service providers /
network operators have been signed and are in place
The customer has subscribed to services offered via the Mobile Portal Service Provider and has
concluded an appropriate contract with the Mobile Portal Service Provider
The customer has a postpaid account
The customer uses the services subscribed to
Post Conditions
There was normal operation of the services supplied and no SLA violation occurred
Each service provider / network operator involved in providing a service rated the service usage
correctly and provided the Mobile Portal Service Provider with the appropriate usage and
charging data
The Mobile Service Provider aggregated the external data with its internal usage and charging
data
The customers account was updated by the correct amount for the service usage
The billing information encompassing all the individual services used by the customer via the
Mobile Portal Service Provider was provided to the customer for payment
GB921F v4.6
Page 23
Process Flow ( eTOM Level 3 processes)

C us tom e r Bil l ed
M a rk e t
P ro du c t &
M an ag e Req ue s t
C u s to m e r
(in c l . Se lf Se rv i c e )
C re ate & Del i v e r

Bi ll
App l y Pri c i ng ,
Di s c ou nti ng &
R eb ate
S e rv i c e
R ate Us ag e
R ec ords
M e di a te Us a g e
R ec ords
R e s o u rc e
( Ap pl i c a tio n,
C o m p uti ng
a n d Ne two rk )
R e s ou rc e Data
C ol l ec t Res ou rc e
P roc es s Res ou rc e
R e p ort Res ou rc e
Av ai l ab l e
D ata
D a ta
D ata
S u pp l i er/
P a rtn er
M a na ge Ac c o un t
M a na ge S/P
R eq ue s ts
P artne r Us a ge
&
Cha rg i ng
Data Av a il a bl e
Figure 2.5 Federated Billing Flow
GB921F v4.6
Page 24
Advice of charge
Context
The end user, using a device (phone, mobile or fixed / PDA/ PC / etc), accesses a
specific, value added product, ie. a product, which is not included in the customers
subscription, or which has different pricing rules from the norm. This product may
carry dynamic charging. The customer will not buy this product until an indication of
the cost of the product or a rate for the product has been presented to her/him.
Scenario description
The end user indicates an interest in buying a product, a charge or rate for this product
is displayed to the customer. The end user is presented with this information, aka
Advice of Charge (AoC) via a screen display, voice message, text message, etc. This
may also involve presenting relevant (to that user) alternative charges.
Example.1: A video clip of a goal scored may be more expensive in the first hour
after the match is played and/or follow normal time related charging rules, eg cheaper
after 18.00 hours. The AoC would display the current cost of the video clip download,
plus may display the reduced cost of the video clip if the user is prepared to wait until a
later time. (NB. this is down to the business rules/policy of the company concerned).
Example.2: The download of a music CD may take 3 hours via a 500k Broadband line
and cost $5 for the video and nothing for transport (covered by normal flat rate
subscription), or it may take 5 minutes to download via the 500 BB line temporarily
boosted to 10M and cost $5 for the video and $3 for the extra temporary bandwidth.
(NB. The charges displayed here would be decided by the company involved, but best
practice would suggest both charges are displayed.)
Pre Conditions
The user must be using a valid/authorized device,
The end user must be a valid/authorized user of that network
The user must be permitted to buy that product (eg. End user of corporate intranet often have
restrictions on value-add services)
The Network/Service Provider (which ever is responsible for the billing for this product) has
dynamic access to the charging and rating rules for the specific service required
or*
The Network/Service Provider has dynamic access to the charging and rating rules for the
specific service required plus the charging /discount rules for the individual end customer*.
* This will depend on whether the customer is a subscriber of the Network/Service Provider and/or whether that
Network/Service Provider wishes to offer such an individualized AoC service.
GB921F v4.6
Page 25
Post Conditions
The customer is presented with the charge or rate that will be applied to that user if they buy this
product, (and if applicable any alternative charging options), so the user can continue or
otherwise with buying this product
There has been no change made to the customers account records
No call records have been established
MIS data may have been recorded for that query dependant on business /marketing policy of
that Network/Service Provider.

Adv ice of Charge
Advice of Charge
Request
Charge
presented to
Customer
Market
Product &
Customer
A pply Pricing,
Discounting &
Rebate
Cr eate & Deliver

Bill
Manage Request
( Including Self
Service)
Service
Rate Usage
Records
Resource(Ap
plication,
Computing
and Netw ork)
Process Resource
Data
Report Resource
Data
Supplier/
Partner
Figure 2.6 Level 3 Process Flow Advice of Charge
GB921F v4.6
Page 26
eTOM Level 3 Processes involved in Billing Flows

The following processes are used in the different scenarios described above. Their
definitions will need adjustment to encompass these scenarios.
Manage Collection
Manage Collection needs to encompass balance management processes in its
description (increase/decrease/:reserve and release reserved balance)
Process Name
Process Identifier
Brief Description
Extended
Description
Manage Collection
1.B.1.8.5
Collect payments for service consumed by the customer and match to
invoices if needed
The purpose of this process is to collect payments made by the customer.
For prepaid customer this process will handle the customer balance
management processes. Furthermore this process matches these payments
with the services/invoices delivered to this customer. This process is also
meant to manage the amount due from the customer, i.e. check whether the
payments are made in time. If not so, this might result in putting the
customer on hold.
Mediate Usage Records
Process Name
Process Identifier
Brief Description
Extended
Description
Mediate Usage Records

1.B.2.5.1
Validate, normalize, convert and correlate usage records collected from the
resource layer
The purpose of the Mediate Usage Records processes is to validate,
normalize, convert and correlate usage records collected from the resource
layer. These processes also group usage records that relate to a specific
service usage.
GB921F v4.6
Page 27
Rate Usage Records
Process Name
Process Identifier
Brief Description
Extended
Description
Rate Usage Records

1.B.2.5.2
Identify and apply tariffs and charging algorithms to specific parameters
encapsulated in usage records
The purpose of the Rate Usage Records processes is to identify and apply
tariffs and charging algorithms to specific parameters encapsulated in
usage records in order to produce a charge that is then inserted in the usage
record.
Process Resource Data (RM&O AB)
Process Name
Process Identifier
Brief Description
Extended
Description
Process Resource Data

1.AB.3.5.2
Process the raw data collected from the resources
The Process Resource Data processes are responsible for processing the
raw data collected from the resources. This includes the filtering of
Resource Data based on well-defined criteria, as well as providing
summaries of the Resource Data through aggregation.
These processes are also responsible for formatting the Resource Data
before distributing it to other processes within the enterprise
Apply Pricing, Discounting & Rebate
Process Name
Process Identifier
Brief Description
Extended
Description
Apply Pricing, Discounting & Rebate

1.B.1.8.2
Ensure that the customer receives an invoice that is reflective of all the
billable events delivered by the Service Provider as per the business
relationship between the customer and the Service Provider
The purpose of this process is to ensure that the customer receives an
invoice that is reflective of all the billable events delivered by the Service
Provider as per the business relationship between the customer and the
Service Provider. In addition, it ensures that the appropriate taxes, rebates
(i.e. missed customer commitments) and credits are applied to the
customers invoice(s). This process contains the account and customer
specific pricing, charges, discounting, credits and taxation for services
delivered to the customer by the Service Provider. It accepts events that
have been collected, translated, correlated, assembled, guided and service
rated. It takes these events and determines the account or customer specific
pricing, charges, discounts, and taxation that should be delivered to the
invoice(s) for the customer. This process can occur in real-time as events
are service rated, or can be on a scheduled on a periodic basis at the
Service Providers discretion.
GB921F v4.6
Page 28
Chapter 3 DSL Fulfillment process flows
DSL Fulfillment Assumptions

The Fulfillment process to be documented here is only one scenario out of many
possible ways of delivering a Fulfillment process.
To scope a typical generic Fulfillment process, here are the assumptions used
There is limited pre-provisioning of infrastructure to end users

(perhaps more typical of HDSL than ADSL).
Part of the resource needed will be provided internally and part
externally using supplier-partner processes e.g. the ISP is the retailer
and is buying the Local Loop from the incumbent carrier.
At Level 2 only the dominant process flow is shown - exception cases
(e.g. no resource available) may be detailed in Level 3 Flows.
Multiple external suppliers will be considered for external supply of
resources.
The service has moderate complexity and after negotiations with the
customer's purchasing staff are completed, the SP's technical
contacts will interact with the customer's engineering staff.
DSL Fulfillment Process Interactions

The first step in documenting the end-to-end (E2E) flows is positioning the Fulfillment
flows in their context within the overall eTOM model.
Figure 3.1 shows this context for Fulfillment. As would be expected, the majority of the
high-level process linkages are within the Level 1 Fulfillment process grouping, but a
number of significant interactions are identified outside of this vertical process area.
GB921F v4.6
Page 29
Customer
Strategy, Infrastructure & Product

Strategy &
Commit
Operations
Infrastructure Lifecycle
Management
Product Lifecycle
Management
Operations Support
& Readiness
Fulfillment
Assurance
Customer Relationship Management
Marketing & Offer Management
Customer Interface Management
Sales
Development
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Billing
Marketing
Capability
Delivery
Product Marketing
Communications
& Promotion
Selling
CRM
Support &
Readiness
Product & Offer

Development &
Retirement
Marketing
Fulfillment
Response
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Retention & Loyalty
Service Development & Management
Service Management & Operations

Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning
Resource Development & Management
Resource Management & Operations

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Problem
Management
Service
Configuration &
Activation
SM&O
Support &
Readiness
RM&O
Support &
Readiness
Service
Quality
Management
Resource
Performance
Management
Resource
Trouble
Management
Resource
Provisioning
Service &
Specific
Instance Rating
Resource Data Collection & Processing
Supply Chain Development & Management

Supply Chain
Strategy &
Planning
Supplier/Partner Relationship Management
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
S/P Interface Management
Supplier/Partner
Enterprise Management
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management
Enterprise Risk Management
Group
Enterprise
Management
Business
Continuity
Management
Financial & Asset Management

Financial
Management
? Work Task
Assignment ?
? Info & Comm

System Support ?
Strategic & Enterprise Planning
Asset
Management
Procurement
Management
Security
Management
Fraud
Management
Audit
Management
Insurance
Management
Process
Management &
Support
Enterprise
Quality
Management
Program &
Project
Management
Stakeholder & External Relations Management

Corporate
Communications &
Image Management
Shareholders
Community
Relations
Management
Knowledge & Research Management
Enterprise Effectiveness Management
Shareholder
Relations
Management
Regulatory
Management
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Research
Management
Technology
Scanning
Human Resources Management

Legal
Management
Board &
Shares/Securities
Management
HR Policies &
Practices
Employees
Organization
Development
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
Other Stakeholders
Figure 3.1: Fulfillment Process Interactions
DSL Fulfillment Process Flows

Further insight is developed through a more detailed illustration of the process
interactions among the major Level 2 processes involved.
Flow diagrams for the DSL Fulfillment example are divided into three flows
representing three phases within Fulfillment: pre-sales, ordering and post-ordering.
This is shown in the three Level 2 Process Flow diagrams (Figures 3.2a, 3.3a and
3.4a) below.
Here the Level 2 processes are shown with relative positioning similar to that in the
eTOM framework, to assist understanding and to make the diagrams more intuitive.
Start points for the Fulfillment process are shown, and the interconnecting arrows
indicate events or information linking the Level 2 processes.
This view can be developed further to indicate sequencing, and to imply involvement
by different Level 3 processes within the indicated Level 2 process, as shown in
Process Dynamics diagrams (e.g. Figure 3.2b). Here, a given Level 2 process may be
shown several times to allow the sequencing of its involvement in the flow to be more
clearly seen. Typically, different functionality is involved at each point for a given Level
2 process, so this is a step towards identification of the specific Level 3 process or
processes within the Level 2 process which will support the interactions.
GB921F v4.6
Page 30
Customer
contacts retailer
Sales Proposal
received By
Customer
Sales Inquiry
Routed
Marketing
Fulfillment
Response
Customer
Need
Clarification
Requested
Customer
Need
Clarification
Provided
Alternative
Solution
Offered
Selling
Customer
Profile
Sales Proposal Retrieved
Offered
Retention &
Loyalty
Feasibility
Customer
Contact
Recorded
Order Handling
Requested
Feasibility
Assessment
Completed
Design &
Technology
Selection Request
Service Configuration & Activation
Resource
Reservation
Requested
Resource
Reservation
Confirmed
Resource Provisioning
Check External
Supplier
Solution
Pre-Order initiated
S/P Requisition
Management
Pre-Order
Figure 3.2a: Pre-Sales Level 2 Process Flow
Customer
contacts retailer
Market
Product &
Customer
Customer
Interface
Management
Customer Profile
retrieved
Retention &
Loyalty
Sales Inquiry
Routed
Customer Interface
Management
Customer Interface
Management
Customer Need
Customer Need Clarification
Clarification
Provided
Requested
Customer Interface
Management
Alternative
Solution
Offered
Selling
Sales Proposal
received By
Customer
Sales
Proposal
Feasibility
Offered
Assessment
completed
Selling
Order Handling
Feasibility Requested
Service
Resource
(Application,
Computing
and Network)
Design & Technology

Selection requested
Service Configuration &
Activation
Design &
Technology
Selection response
Resource Reservation
Confirmed
Resource Reservation
Requested
Resource
Provisioning
Check External
Supplier Solution
Supplier/
Partner
S/P Requisition
Management
Pre-Order
Pre-Order
Initiated
Figure 3.2b: Pre-Sales Process Dynamics Flow
GB921F v4.6
Page 31
Order Completion
Notification
Customer places Order
Order
Confirmed
by Customer
Design
Confirmation by
Customer
Engineering
Requested
Retention & Loyalty

Priority
Requested
Priority
Advised
Selling
Customer Order
Processing Requested
Billing &
Collections
Management
Order Handling
Internal
Service
Order
Initiated
Design
Requested
Design
Completed
External Supplier
Selection Required
Completion
Advised to
Customer
Design
Accepted by
Customer
Service Details
for Billing
Service
Activated
Service Configuration & Activation

Internal
Capacity
Work Order
Requested Capacity Initiated
Reserved
Internal
Resource
Resource Activation
Provisioning Requested
Completed
Resource
Activated
Service Details
for Assurance
External
Resource
Activated
Customer
QoS/SLA
Management

External Component Requested
S/P Requisition
Management
External Order
Issued
Figure 3.3a: Ordering Level 2 Process Flow
Customer
requests SP
offering
Market
Product &
Customer
Order
Completion
Notification
Customer Interface
Management
Customer
Request
Received
Selling
Customer Interface
Management
Customer
Order
Confirmed
Customer Order
Initiated
Order
Handling
Design Confirmation
by Engineering
requested
Order Handling
Priority
Requested
Customer Interface
Management
Design
Accepted by
Customer
Completion advised
to Customer
Order
Handling
Priority Advised
Order Handling
Design Requested
Retention &
Loyalty
Internal
Service Order
Initiated
Design Completed
Service Activated
Service
Service
Configuration &
Activation
Service
Configuration &
Activation
Service
Configuration &
Activation
Resource
Allocation
requested
Resource
(Application,
Computing
and Network)
External Supplier required
Supplier/
Partner
Resource
Provisioning
S/P Requisition
Management
Service
Configuration &
Activation
Resource
Activation
Internal Resource requested
Provisioning
Completed
Resource
Provisioning
Internal
Work Order
Initiated
Resource
Allocated
Service
Configuration &
Activation
Resource
Provisioning
Resource
Activated
External Resource
Activated
External
Component
Requested
S/P Requisition
Management
External Order
Issued
External
Resource
Activated
Service Details
for Billing
Service Details
for Assurance
Figure 3.3b: Ordering Process Dynamics Flow
GB921F v4.6
Page 32
Status Request
Market
Product &
Customer
Order Status
Customer Interface
Management
Customer Interface
Management
Order Status
Requested
Order Handling
Order Status
Provided
Service Order
Status Requested
Order Handling
Service Order
Status Update
Service
Service
Configuration &
Activation
Service
Configuration &
Activation
Work Order Status
Request
Resource
(Application,
Computing
and Network)
Resource
Provisioning
External Order Status

request
Supplier/
Partner
Work Order Status

response
External Order
Status Response
S/P Requisition
Management
S/P Requisition
Management
External Order
Status Request
External Order
Status
Figure 3.3c: Ordering Process Dynamics Flow: Status Updates
Order
Completion
Notification

Customer
Satisfaction
Request
Customer
Satisfaction
Reply
Order Handling
Billing Starts
Customer
QoS/SLA
Management
Figure 3.4a: Post-Ordering Level 2 Process Flow
Billing & Collections

Management
GB921F v4.6
Page 33
Chapter 4 PLM process flows
PLM Assumptions
Product Lifecycle Management encompasses the processes required for the
definition, planning, design, build, delivery, maintenance, revision and retirement of all
products in the enterprises portfolio. They enable a Service Provider to manage
products in relation to profit and loss margins, customer satisfaction and quality
commitments.
PLM processes are end-to-end oriented processes that enable the enterprise strategic
and business vision; they drive the core operations and customer processes to meet
market demand and customer expectations.
Customer
Strategy &
Commit
Operations
Management
Product Lifecycle
Management
Operations Support
& Readiness
Fulfillment
Assurance
Billing

Sales
Development
Selling
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Marketing
Capability
Delivery
CRM
Support &
Readiness
Product Development &

Product Development &
Product &Retirement
Offer
Retirement
Development &
Retirement
Product Marketing
Communications
& Promotion
Marketing
Fulfillment
Response
Product Marketing
Product Marketing
Communications &
Communications &
Promotion
Promotion
Sales Development
& Channel Development
Sales & Channel Development
Development &
Service Development & ManagementService
Service Development &
Retention & Loyalty

CRM
CRM
Support &
Support &
Readiness
Readiness
Retirement
Retirement
Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning
Supply Chain
Strategy &
Planning
Service &
Specific
Instance Rating
Resource
Performance
Management
Resource
Trouble
Management
Product Lifecycle
Management
RM&O
Support &
Readiness
Service
Quality
Management
SM&O
SM&O
Support &
Support &
Readiness
Readiness

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Problem
Management
Service
Configuration &
Activation
SM&O
Support &
Readiness
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Resource
Provisioning
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
Resource Development &

Retirement
Retirement
RM&O
RM&O
Support &
Support &
Readiness
Readiness
Supplier/Partner
Supply Chain
Supply Chain
Development
Development
& Change
& Change
Management
Management
S/PRM
S/PRM
Support &
Support &
Readiness
Readiness
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management

Business
Continuity
Management
Group
Enterprise
Management

Financial
Management
Asset
Management
Procurement
Management
Shareholders
Security
Management
Fraud
Management
Audit
Management
Insurance
Management
Process
Management &
Support
Enterprise
Quality
Management
Program &
Project
Management

Corporate
Communications &
Image Management
Community
Relations
Management
Shareholder
Relations
Management
Regulatory
Management
Employees
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Research
Management
Technology
Scanning

Legal
Management
Board &
Shares/Securities
Management
HR Policies &
Practices
Organization
Development
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
Other Stakeholders
Figure 4.1: Scope of Product Lifecycle Management

PLM spreads across the whole enterprise; Figure 4.1 shows the scope of Product
Lifecycle Management across the eTOM framework.
GB921F v4.6
Page 34
PLM Process Interactions

PLM processes are end-to-end processes that affect and have interactions with most
entities in the enterprise. PLM process flows can be represented in many different
ways depending on the use and the scope of application, and such interactions could
become so dense that they could simply confuse. To simplify, Figure 4.2 selects an
example of such process interactions in PLM; and the diagram depicts an extract of all
the possible process flows from PLM. It should be noted that depicting the entire set of
process interactions for PLM would require a significantly more complex diagram.
Approved Product Concept
Product Plan, Product Change Request

Marketing
Marketing
Fulfillment
Fulfillment
Response
Response
Product
Product&&Offer
Offer
Portfolio
PortfolioPlanning
Planning
Reports on target
segments
Selling
Selling
Service
ServiceQuality
Quality
Management
Management
To Sales
& Channel
Development
Product Delivery Schedule

Product Discontinuation Plan
Product Change Request
From Product
Development & Retirement
Product line definition,
Product Planning
Operational Perfformance
Report
QoS Goals & Thresholds
Product
Status
Information
Service Quality Plan,

Service Specifications
Service
ServiceStrategy
Strategy&&
Planning
Planning
Service Usage Forecasts
Resource
ResourceStrategy
Strategy &&
Planning
Planning
To Resource Development
Report on Services Configuration
Preliminary Networks/Services Design Plan
Product Infrastructure Requirements

Product Change Request
Product
Product Delivery Schedule
Product&&Offer
Offer
Portfolio
PortfolioCapability
Capability
Product Configuration
Delivery
Delivery
Reports
Product
Product
Development
Development
&&Retirement
Retirement
CRM
CRMSupport
Support&&
Readiness
Readiness
Product Delivery
Product
Schedule
Communications
& Promotions
Product
ProductMarketing
Marketing
Communications
Communications&&
Promotion
Promotion
From
Selling
Resource
Resource
Capability
CapabilityDelivery
Delivery
Report on Services Configuration
P/S Launch
Plan
Sales
Sales
Development
Development
Operations
Capabilities
Report
Preliminary Networks/Services Design Plan
Product Configuration Reports
Plan for Supporting

Systems
Resource
Resource
Development
Development&&
Retirement
Retirement
Network capabilities
(including performance
goals)
Service
ServiceCapability
Capability
Delivery
Delivery
Product & Offer Capability Delivery Report
Product Status
Information
Service
Development
Plan
Planned logical network

configuration and
Deployment Plans
SLA Agreements
To Service
Development &
Retirement
Service
Service
Development
Development&&
Retirement
Retirement
Definition of requirements
for distribution channels,
Incentive Plans, Plan for
Supporting Systems
Capacity Constraints
Service
Readiness Plan
Service Infrastructure Requirements

Service Creation Request
SM&O
SM&OSupport
Support&&
Readiness
Readiness
Service Specifications
Logical & Physical Resource

Configurations
RM&O
RM&OSupport
Support&&
Readiness
Readiness
CRM
CRMSupport
Support
&&Readiness
Readiness
Requirements for distribution

channels
Figure 4.2: Example of PLM Process Interactions

To address this complexity, in the more general case, PLM processes could be
organized according to different scope levels, for example, in terms of Core PLM,
Strategic PLM, Operational PLM, E2E PLM, etc. as depicted in Figure 4.3.
GB921F v4.6
Page 35
Customer

Strategy &
Commit
Operations
Management
Product Lifecycle
Management
Operations Support
& Readiness
Fulfillment
Assurance
Sales
Development
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Billing
Marketing
Capability
Delivery
Product Marketing
Communications
& Promotion
Selling
CRM
Support &
Readiness
Product & Offer

Development &
Retirement
Marketing
Fulfillment
Response
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Retention & Loyalty

Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Configuration &
Activation
SM&O
Support &
Readiness
RM&O
Support &
Readiness
Resource
Provisioning
Service
Problem
Management
Service
Quality
Management
Resource
Trouble
Management
Resource
Performance
Management
Service &
Specific
Instance Rating

Supply Chain
Strategy &
Planning
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
Core PLMSupplier/Partner
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management
Business
Continuity
Management

Financial
Management
Asset
Management
Strategic PLM
Group
Enterprise
Management
Procurement
Management
Security
Management
Fraud
Management
Audit
Management
Process
Management &
Support
Enterprise
Quality
Management
Program &
Project
Management
Stakeholder & External Relations

Management
Operational
PLM
Corporate
Communications &
Image Management
Community
Relations
Management
Shareholder
Relations
Management
Insurance
Management
Regulatory
Management
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Research
Management
Technology
Scanning

Legal
Management
Board &
Shares/Securities
Management
HR Policies &
Practices
Organization
Development
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
E2E PLM
Shareholders
Employees
Other Stakeholders
Figure 4.3: Different Scopes for PLM
Application of SIP Business Processes

In order to describe how the SIP (Strategy, Infrastructure and Product) business
processes from the eTOM framework can be used in an actual environment, this
example draws on the work of the Product Lifecycle Management (PLM) Catalyst
project within the TM Forums Catalyst program. This project illustrated how TM Forum
NGOSS concepts and framework could be leveraged to dramatically improve the
processes and systems for building and releasing new products, through the
automatic linkage of appropriate product information to the right operations systems
and information catalogs on the network side. It demonstrated integrated Product
Lifecycle Management with established flow-through order processes, showing how
product managers can effectively manage the product lifecycle from beginning to end,
with a real-time capability to create, approve, release, distribute, order, fulfill, and bill
for new services.
In support of this, the process flows included here show eTOM level 2 processes
involved in PLM, with some aspects of relevant level 3 processes also included.
Approach
Based on a selected business scenario for PLM (see later), the relevant eTOM
business processes have been identified. Additionally, business process KPIs and
triggers have been defined to illustrate how these PLM scenario processes can be
measured against their performance indicators.
In PLM a product can have one or more services and each service is supported by
one or more resources. These and other rules were identified and mapped to
GB921F v4.6
Page 36
corresponding eTOM business processes based on a commonality that determines

the way business actions are executed whilst covering at the same time specific
business requirements.
The results illustrate the effectiveness of the eTOM and related NGOSS work, such as
SID, across all activities involved with the scope of the project, such as product,
service, resource and supply chain planning, specification, development, test and
delivery to the operations environment, using product and service bundle concepts.
The insights gained on the SIP (Strategy, Infrastructure and Product) area of the
eTOM framework have been used to feedback into the ongoing eTOM work.
PLM Process Flows

In order to define the business process flows across the SIP and Operations areas, a
scenario with the following issues has been considered:
There are products and service bundles made of components that can be accessed at
any time and reused to further define and build new products and services. A product
manager can then generate ideas from the analysis of current product and service
bundles. These aspects are covered by SM&O Readiness processes that also support
Manage Service Inventory processes.
The new product proposal is then submitted for approval by the product manager.
Once approved, the development project for the new product and related services and
resources starts. The primary processes that support this project are: Product & Offer
Portfolio Planning, Product Marketing Communications & Promotion, Product & Offer
Development & Retirement, Service Strategy & Planning, Service Development &
Retirement, Resource Development & Retirement, Product & Offer Capability Delivery,
Service Capability Delivery and Resource Capability Delivery.
Once the new product with its associated services and resources is developed, tested
and accepted, all of its configuration information including pricing rules and promotions
are transferred to the Operations area through the Product Development &
Retirement, Service Development & Retirement, and Resource Development &
Retirement processes respectively. The configuration information is then transferred to
the Manage Service Inventory and Manage Resource Inventory processes, which are
part of the SM&O Support & Readiness and RM&O Support & Readiness processes
respectively. Additionally, CRM Support & Readiness processes provide all of the
necessary updates to support the new product as well as its marketing campaign and
billing.
Customer Interface Management, Selling, Service & Specific Instance Rating and
Billing & Collections Management processes create or update the necessary
information to offer the new product and services to the market. This includes price,
billing, discount and other parameters and rules.
The customer requests the new product through a call center, sales channel or selfprovisioning via the Customer Interface Management and Selling processes. In order
to fulfill the order and deliver the requested product, the following business processes
are involved: Order Handling, Billing & Collections Management, SM&O Support &
Readiness, Service Configuration & Activation, Service & Specific Instance Rating,
RM&O Support & Readiness, and Resource Provisioning.
GB921F v4.6
Page 37
The customer invoice related to the new product and services is generated; the
processes that support the business flows here are: Customer Interface Management,
Billing & Collections Management, CRM Support & Readiness, Service & Specific
Instance Rating, and Resource Data Collection & Processing.
If the customer later on requests a change in the new product, the following business
processes will be involved: Customer Interface Management, Selling, Order Handling,
Billing & Collections Management, SM&O Support & Readiness, Service Configuration
& Activation, RM&O Support & Readiness, and Resource Provisioning.
The business process flows that support the above-described scenario are shown in
Figures 4.4 and 4.5 below. Figure 3.4 describes the product manager accessing the
product and service bundles inventory when envisioning a new product and/or service
based on the components of existing ones; then further actions are described in order
to obtain approval for a new product development project. Figure 4.5 depicts the
process flows involved with product development after approval has been granted
from the product manager or a higher executive committee. The business process
flows described represent a change request received from a customer requiring the
new product and/or service.
New Product Development

Approved & Integrated in
Product Portfolio
Request to Create a
New Product

Product & Offer Development & Retirement
Product & Offer Development &

Retirement
Product & Offer

Capability Delivery
Product & Offer

Capability Delivery

Product Infrastructure
Requirements Provided
Service
Capability Delivery

Retirement
Service Deployment Plan

(SDP) Provided
Resource
Infrastructure
Requirements
(RIP) Provided
Resource
Development &
Retirement

Supplier/Partner Infrastructure &
Capability (SPIC) Requirements
Provided
Supply Chain Capability
Delivery
Supplier/Partner Required
Capabilities Provided
Product & Offer

Capability Delivery

Retirement
Service
Capability Delivery
Resource
Infrastructure Plan
(RIP) Provided
Supply Chain
Development & Change
Management
Approved Service
Infrastructure Plan (SIP)
Provided
Approved Service Infrastructure Plan

(SIP) Provided
Service
Infrastructure Plan (SIP)
Approval Requested
Service Infrastructure Requirements Provided

Resource
Capability Delivery
Approved Product
Infrastructure Plan (PIP)
Provided
Product Infrastructure Plan

Approval Requested
Product Development Plan (PDP)

Provided
Service Capability
Delivery
Resource Infrastructure Plan

Approved
Resource Infrastructure
Plan (RIP) Approval
Requested
Resource
Capability
Delivery
Supplier/Partner
Integration Plan
(S/PIP) Provided
Resource
Development &
Retirement
Resource
Capability
Delivery

Integration Plan (S/PIIP)
Approval Requested

Integration Plan (S/PIIP)
Approved
Supply Chain
Development &
Change Management
Supply Chain
Capability Delivery
Figure 4.4: Approve the Development of a New Product (pre-approval)
GB921F v4.6
Page 38
Request to Develop New Product

or Change an Existing Product
Sales Catalog Updated with

New or Modified Product

Product & Offer Development & Retirement
Pricing Information
Updated
Selling
Customer
Request
transmitted
Product Inventory Updated
Product Changes Communicated

Product Marketing
Communications & Promotion

Product Information
Provided
Products Promoted & Advertised

Product Inventory Updated
CRM Support
& Readiness
Service Order
Customer Informed of
Signed by Customer Order Completion
Order Handling
Product
Billing
Activated
Customer
Interface
Management
Billing &
Collections
Management
Product Billing Inormation

Rating
Updated
Activation
Service
Rated
Plans
& Status
Instance
Services Data
Info on
Services and
Information
Service Rating Rules Provided
of Service
Reserved &
Available
Provided
Products
Provided
Service Development & Retirement
Confirmed
Pre-assigned
Services
Inventory
Service & Specific Instance
Rating
Provided
Synchronized
Service Rating Rules Provided
SM&O Support &
Services Inventory Info Provided
Readiness
Service
Configured and
Activated
Service Configuration Information
Activation &
Updated Service Configuration & Activation
Availability of
Service Confirmed
Usage
Events
NEs
Configuration of
Pre-rated
Configuration
Resources &
Resources and Services
Data Provided
&
Availability
NEs Requested
Inventory
Synchronized
Confirmed
Resources Inventory
Retirement
Resource Data
RM&O Support &
Info Requested
Collection &
Readiness
Resource Inventory
Processing
Updated

Supplier and Resources Inventory Aligned
S/PRM Support & Readiness
Figure 4.5: Develop New Product or Modify an Existing One (post-approval)
GB921F v4.6
Page 39
Chapter 5 SLA process flows
SLA Assumptions
The SLA process flows depicted here have their origins in the SLA Management
Handbook [ref F1] where a set of use case scenarios and TOM process flows were
depicted in order to illustrate the interactions between the TOM processes involved in
SLA management. In a liaison between the SLA Management Team and the eTOM
Team, the TOM flows have been updated to eTOM process flows for version 2.0 of
the SLA Management Handbook. A subset of these flows is provided in this chapter.
The lifecycle of an SLA is analyzed in the following five phases as shown in Figure 5.1.
Develop Templates
and Parametric
Boundaries
Negotiate
Individual
Contracts
Take Line/Service
Orders and Provision
Ex
ec
Im
em
pl
n
io
t
ta
en
ut
io
n
Product/Service Development
Negotiation and Sales
Implementation
Execution
Assessment
Pr
D od
ev uc
el t/S
op e
m rv
en ic
t e
N
eg
ot
ia
ti o
n
an
d
Sa
le
s
Monitor,
Surveillance,
Maintain, Bill
ss
sm
s
e
t
en
Reassess
Figure 5.1: Product/Service and Associated SLA Lifecycle

Scenarios were selected to illustrate the process flows required to support the above
SLA lifecycle phases. They were not intended to be prescriptive but were provided as
one possible approach to the process flows involved in SLA management. The
scenarios originally selected have not been changed for the eTOM flows except where
it was thought necessary or desirable in the light of experience with the original flows
and with the different scope of eTOM compared to TOM. This is evident, for example,
in the fact that there were no processes for supplier/partner relationships in TOM, and
so the original scenarios did not include such processes. In one of the flows depicted
here, a relationship with a third party service provider has been included in order to
GB921F v4.6
Page 40
show how supplier/partner processes can be used. Clearly, such relationships can be
included in other flows, but the first step was to adapt the TOM flows to eTOM flows
and then to exploit the wider scope of the eTOM framework as required.
Another point on which work within the TM Forum has progressed is in the clarification
of the relationship between product and service, and the greater emphasis on
marketing processes in the Service Provider enterprise. Although a product can
consist of several services, the scenarios here retain the approach of the original flows
in that a product consists of one service. In further work in this area, it would be
desirable to coordinate the performance of several services comprising a product and
to examine the flows required for the management of SLAs for such products, as well
as between several service providers in a value chain.
The original TOM flows were designed to be generic as the focus was on SLA
management and not on any specific implementation of a service, and this is also the
case in the eTOM flows. Again, it would be desirable to examine this approach given
the different kinds of service now available, particularly in the mobile environment, and
the work being undertaken in this area by the TM Forum.
The process flows selected here are those for Stages 4 and 5 of the SLA lifecycle, i.e.
the Execution and Assessment phases. The scenarios originally selected for these two
phases are shown here, first as interaction diagrams and then as eTOM process
flows. As with the TOM process flows, these flows are provided as examples depicting
illustrative approaches to aspects of SLA management in the two lifecycle phases.
SLA Process Interactions

The process interactions are first shown as high-level linkages in the eTOM model.
They are categorized as Normal Execution, Execution with SLA Violation, and
Assessment.
Normal Execution
The Execution phase covers all normal operations of the service instances covered by
the SLA.
Figure 5.2 presents normal in-service execution and monitoring where performance
data is collected from resources and analyzed for resource performance, then for
overall service quality, and finally checked against the customer SLA. In this case, a
third party service provider is involved and performance data from the external service
components is included in the service quality analysis. In addition, a billing flow was
added to show how both internal usage data as well as data from the third party
service provider is incorporated into the customer bill. All of these interactions occur in
the Assurance process grouping for the resource performance and service quality
analysis interactions and in the Billing process grouping for the billing interactions.
GB921F v4.6
Page 41
Customer

Strategy &
Commit
Operations
Product Lifecycle
Management
Management
Operations Support
& Readiness
Fulfillment
Assurance
Sales
Development
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Billing
Marketing
Capability
Delivery
Product Marketing
Communications
& Promotion
Selling
CRM
Support &
Readiness
Product & Offer

Development &
Retirement
Marketing
Fulfillment
Response
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Retention & Loyalty

Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Configuration &
Activation
SM&O
Support &
Readiness
RM&O
Support &
Readiness
Resource
Provisioning
Service
Problem
Management
Service
Quality
Management
Resource
Trouble
Management
Resource
Performance
Management
Service &
Specific
Instance Rating

Supply Chain
Strategy &
Planning
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
Supplier/Partner
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management

Business
Continuity
Management
Group
Enterprise
Management
Asset
Management
Corporate
Communications &
Image Management
Procurement
Management

Audit
Management
Process
Management &
Support
Insurance
Management
Enterprise
Quality
Management
Program &
Project
Management

Financial
Management
Fraud
Management
Security
Management
Community
Relations
Management
Shareholders
Shareholder
Relations
Management
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Technology
Scanning
Research
Management
Regulatory
Management
Board &
Shares/Securities
Management
Legal
Management
HR Policies &
Practices
Organization
Development
Employees
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
Other Stakeholders
Figure 5.2: Normal Execution of SLA Service

Case A: Performance Data during Normal Operation
Customer
Strategy &
Commit
Operations
Management
Product Lifecycle
Management
Operations Support
& Readiness
Fulfillment
Assurance
Sales
Development
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Billing
Marketing
Capability
Delivery
Product Marketing
Communications
& Promotion
Selling
CRM
Support &
Readiness
Product & Offer

Development &
Retirement
Marketing
Fulfillment
Response
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Retention & Loyalty

Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Problem
Management
Service
Configuration &
Activation
SM&O
Support &
Readiness
RM&O
Support &
Readiness
Service
Quality
Management
Resource
Performance
Management
Resource
Trouble
Management
Resource
Provisioning
Service &
Specific
Instance Rating

Supply Chain
Strategy &
Planning
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
Supplier/Partner
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management
Group
Enterprise
Management
Business
Continuity
Management

Financial
Management
Asset
Management
Procurement
Management
Shareholders
Security
Management
Fraud
Management
Insurance
Management
Process
Management &
Support
Enterprise
Quality
Management
Program &
Project
Management

Corporate
Communications &
Image Management
Community
Relations
Management

Audit
Management
Shareholder
Relations
Management
Regulatory
Management
Employees
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Research
Management
Technology
Scanning

Legal
Management
Board &
Shares/Securities
Management
HR Policies &
Practices
Organization
Development
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
Other Stakeholders

Cases B and C: Threshold Crossing Alerts and Resource Failure Alarms
GB921F v4.6
Page 42
Figure 5.3 illustrates the case where threshold crossing alerts and resource failure
alarms are reported and have to be rectified. However, after checking against the
customer SLA it is established that no SLA violation has occurred. Most of these
interactions occur in the Assurance process grouping, but interactions also take place
with the Fulfillment and OSR process groupings.
Execution with SLA Violation

Figure 5.4 shows the operation of the service where real-time SLA violation handling is
required. In this case, the customer reports a problem that is rectified but which leads
to a violation of the customer SLA so that a Billing rebate is given. In this case, there is
interaction between the Assurance and Billing process groupings, but interactions also
take place with the Fulfillment and OSR process groupings.
Customer
Strategy &
Commit
Operations
Management
Product Lifecycle
Management
Operations Support
& Readiness
Fulfillment
Assurance
Sales
Development
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Billing
Marketing
Capability
Delivery
Product Marketing
Communications
& Promotion
Selling
CRM
Support &
Readiness
Product & Offer

Development &
Retirement
Marketing
Fulfillment
Response
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Retention & Loyalty

Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Problem
Management
Service
Configuration &
Activation
SM&O
Support &
Readiness
RM&O
Support &
Readiness
Service
Quality
Management
Resource
Performance
Management
Resource
Trouble
Management
Resource
Provisioning
Service &
Specific
Instance Rating

Supply Chain
Strategy &
Planning
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
Supplier/Partner
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management
Group
Enterprise
Management
Business
Continuity
Management

Financial
Management
Asset
Management
Procurement
Management
Shareholders
Security
Management
Fraud
Management
Insurance
Management
Process
Management &
Support
Enterprise
Quality
Management
Program &
Project
Management

Corporate
Communications &
Image Management
Community
Relations
Management

Audit
Management
Shareholder
Relations
Management
Regulatory
Management
Employees
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Technology
Scanning
Research
Management

Legal
Management
Board &
Shares/Securities
Management
HR Policies &
Practices
Organization
Development
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
Other Stakeholders
Figure 5.4: Customer Detected SLA Violation
Assessment
The Assessment phase can relate to a single customer SLA and the QoS required, or
it can be related to the Service Providers overall quality goals, objectives and risk
management.
Figure 4.5 represents the case where the customer needs have changed and there is
no SLA to meet these needs. The interactions occur in the Market, Product and
Customer layer and involve not just Operations process groupings but also Product
Lifecycle Management process groupings.
Figure 4.6 depicts the process interactions relating to the internal business review
concerning the overall SLA performance across all customers as well as a realignment
GB921F v4.6
Page 43
of service operations and service goals to improve overall service class performance.
The process interactions here occur among the Assurance process groupings as well
as among the OSR process groupings.
Customer
Strategy &
Commit
Operations
Management
Product Lifecycle
Management
Operations Support
& Readiness
Fulfillment
Assurance

Sales
Development
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Billing
Marketing
Capability
Delivery
Product Marketing
Communications
& Promotion
Selling
CRM
Support &
Readiness
Product & Offer

Development &
Retirement
Marketing
Fulfillment
Response
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Retention & Loyalty

Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Problem
Management
Service
Configuration &
Activation
SM&O
Support &
Readiness
RM&O
Support &
Readiness
Service
Quality
Management
Resource
Performance
Management
Resource
Trouble
Management
Resource
Provisioning
Service &
Specific
Instance Rating

Supply Chain
Strategy &
Planning
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
Supplier/Partner
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management

Business
Continuity
Management
Group
Enterprise
Management

Financial
Management
Asset
Management
Procurement
Management
Security
Management
Fraud
Management
Process
Management &
Support
Insurance
Management
Enterprise
Quality
Management
Program &
Project
Management

Corporate
Communications &
Image Management

Audit
Management
Shareholder
Relations
Management
Community
Relations
Management
Shareholders
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Technology
Scanning
Research
Management
Regulatory
Management
Legal
Management
Board &
Shares/Securities
Management
HR Policies &
Practices
Organization
Development
Employees
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
Other Stakeholders
Figure 5.5 Assessment Initiation

Case A: Customer Needs Have Changed
Customer
Strategy &
Commit
Operations
Management
Product Lifecycle
Management
Operations Support
& Readiness
Fulfillment
Assurance

Sales
Development
Market
Strategy &
Policy
Product & Offer

Capability
Delivery
Product &
Offer Portfolio
Planning
Billing
Marketing
Capability
Delivery
Product Marketing
Communications
& Promotion
Selling
CRM
Support &
Readiness
Product & Offer

Development &
Retirement
Marketing
Fulfillment
Response
Billing &
Collections
Management
Customer
QoS/SLA
Management
Problem
Handling
Order
Handling
Retention & Loyalty

Service
Development &
Retirement
Service
Capability
Delivery
Service
Strategy &
Planning

Resource
Development &
Retirement
Resource
Capability
Delivery
Resource
Strategy &
Planning
Service
Configuration &
Activation
SM&O
Support &
Readiness
RM&O
Support &
Readiness
Resource
Provisioning
Service
Problem
Management
Service
Quality
Management
Resource
Trouble
Management
Resource
Performance
Management
Service &
Specific
Instance Rating

Supply Chain
Strategy &
Planning
Supply Chain
Capability
Delivery
Supply Chain
Development &
Change Management
S/P Problem
Reporting &
Management
S/P
Requisition
Management
S/PRM
Support &
Readiness
S/P
Performance
Management
S/P Settlements
& Billing
Management
Supplier/Partner
Strategic
Business
Planning
Business
Development
Enterprise
Architecture
Management
Group
Enterprise
Management
Business
Continuity
Management

Financial
Management
Asset
Management
Procurement
Management
Shareholders
Security
Management
Fraud
Management
Insurance
Management
Process
Management &
Support
Enterprise
Quality
Management
Program &
Project
Management

Corporate
Communications &
Image Management
Community
Relations
Management

Audit
Management
Shareholder
Relations
Management
Regulatory
Management
Employees
Enterprise
Performance
Assessment
Facilities
Management &
Support
Knowledge
Management
Technology
Scanning
Research
Management

Legal
Management
Board &
Shares/Securities
Management
HR Policies &
Practices
Organization
Development
Workforce
Strategy
Workforce
Development
Employee &
Labor Relations
Management
Other Stakeholders
Figure 5.6 Assessment Initiation

Cases B and C: Internal Assessments at the Customer and Service Layers
GB921F v4.6
eTOM Business Process Framework Addendum F
Page 45
SLA Process Flows

The process flows presented here are based on the process interactions between the Level 2 processes shown in the interaction
diagrams and provide more detail of the processes involved and the actions undertaken for each of the scenarios depicted.
Normal Execution
Normal execution, also known as steady state, is the phase where the customer receives service on all the contracted and
instantiated service instances. This section first analyzes in Case A a situation where no outages or other alerts occur and the
customer is billed for the service used (Figure 5.7). It then analyzes in Cases B and C the situation where, although outages occur, no
outage exceeds either the individual or aggregated parameters set in the SLA (Figures 5.8 and 5.9). In the first case of normal
operation, a supplier/partner is also involved; in the second case the outages are within the Service Provider enterprise and so do not
involve a supplier/partner.
The steps shown in Figure 5.7 for Case A are as follows:
1. During normal operation, performance data that is used for general monitoring of service levels as well as for longer-term capacity
prediction is collected on an ongoing basis from the service-providing infrastructure by Resource Data Collection & Processing.
2.
During normal operation, performance data from external service components of third party service providers is sent on an
ongoing basis to S/P Performance Management for general monitoring of service levels, as well as for longer-term
supplier/partner capacity prediction.
3. Resource Data Collection & Processing sends performance data to Resource Performance Management for further analysis.
4. Resource Performance Management sends resource performance reports to Service Quality Management for QoS calculations
and averaging to maintain statistical data on the supplied service instances.
5. S/P Performance Management sends external service component performance reports to Service Quality Management for QoS
calculations and averaging to maintain statistical data on the supplied service instances.
GB921F v4.6
Page 46
Customer QoS
Report
Received
Customer Interface
Management
Ma rket
Product &
Customer
Customer Interface
Management
10. Customer service level

reports generated (and
possibly periodic discussion
with Customer undertaken)
Customer
QoS/SLA
Management
11. Chargeable
details generated
Service Quality
Management
Resource
(Application,
Computing
a nd Network)
5. External service component performance reports generated
Resource
Performance
Data Available
1.
Resource Data
Collection &
Processing
Service & Specific

Instance Rating
4. Resource performance reports

generated
3. Resource
performance
Resource
data passed
Performance
on
Management
6. Resource usage data passed on
2. External component
performance data sent S/P Performance
Management
Supplier/
P artner
7. 3rd Party SP usage

and charging data sent
S/P Interface
Management
P artner
Performance
Data Available
12. Bill generated
Billing &
Collections
Management
9. Service QoS
reports generated
Service
Customer Billed
S/P Interface
Management
8. External service
component billing data
passed on
S/P Settlements &
Billing
Management
Partner Billing
Data Available

Case A: Performance Data during Normal Operation
6. Resource Data Collection & Processing sends resource usage data to Service & Specific Instance Rating for rating service
usage.
7. Third party service providers send their usage and charging data to S/P Settlements & Billing Management.
8.
S/P Settlements & Billing Management analyzes the data and passes it on to Service & Specific Instance Rating for rating
service usage.
9. Service Quality Management analyzes the performance reports received and sends overall service quality reports to Customer
QoS/SLA Management so that it can monitor and report aggregate technology and service performance.
GB921F v4.6
Page 47
10. Customer QoS/SLA Management checks the service quality reports it receives against the individual customer SLA and
establishes that no SLA violation has occurred. Customer QoS/SLA Management sends periodic service level reports to the
customer on either a requested or agreed basis.
11. Service & Specific Instance Rating sends charging details to Billing & Collections Management.
12. Billing & Collections Management generates bills for the customer on either a requested or agreed basis.
The steps shown in Figure 5.8 and 5.9 for Cases B and C are as follows:
1. Notifications are collected from the service-providing infrastructure by Resource Data Collection & Processing on an ongoing
basis. In Cases B and C these notifications are in the form of:
2B. Threshold Crossing Alerts that represent congestion or performance degradation in a congestable resource that leads to slowed
or diminished capacity to support customer services. Resource Data Collection & Processing sends all performance data to
Resource Performance Management, which identifies a resource performance problem and requests Resource Trouble
Management to discover the cause of the alert and possible impact on service performance.
2C. Alarms that represent the failure of a component that affects the service of one or more customers. Resource Data Collection &
Processing sends data on alarms to Resource Trouble Management for further action.
3. Resource Performance Management sends details of the Threshold Crossing Alerts to Service Quality Management so that
various notifications and other steps may be taken to ensure that required service KQI levels are maintained.
4/5.Depending on the nature of the problem, Resource Trouble Management either triggers automatic resource restoration
procedures itself and informs Service Problem Management of its actions, or it raises alarm reports to Service Problem
Management, indicating the time and potential duration of any outage to allow Service Problem Management to determine
potential alternate actions to minimize service impact.
6. Service Problem Management and Service Quality Management correlate their information about the problem.
7. Service Quality Management sends details of the service impact of Threshold Crossing Alerts and Alarms to Customer QoS/SLA
Management.
8. Customer QoS/SLA Management checks the customer SLA and obtains information on the significance of the customer from
Retention & Loyalty. It undertakes various notifications and other steps in order to prevent customer SLAs from being violated,
e.g. clocks started, tracking initiated.
GB921F v4.6
Page 48
C u s t omer
i n f o rmed
C u s t o m e r Interface
M a n a g e ment
M a r ket
P r o duct &
C u s t omer
9 . C u stomer
i n f o r m e d (optional)
C u s t omer
Q o S /SLA
M a n a g e ment
7 . D etails sent of
s e r v i ce quality
i m p a cted by
t h r e s h o ld alerts and
f a i l u re alarms
S e r vice
L o y alty
8 . C u stomer
p r i o r itization
r e q u e s ted and
r e t u r ned
S e r v i ce Problem
M a n a g e ment
M a n a g e ment
5 . R e s o u r ce restored or
p e r f o r m a n c e impacted by
t h r e s h o l d alerts and alarms
t r o u b l e r e p ort generated
R e s o urce
( A p p l ication,
C o m p u ting
a n d N etwork)
P e r f o r mance
M a n a g e ment
2 B . T hreshold
c r o s s ing alerts
n o t ified
R e s o u r ce Data
1.
a c t i o n s undetaken
i n c l u d i n g details of resource
r e s t o r a t i on if applicable
3 . D etails sent of
R e s o urce
1 6 . D etails sent of
6 . O u t a g e i n f ormation correlated,
S e r v i ce Quality
R e s o urce
P e r f o r mance
D a t a Available
R e t ention &
C o l lection &
P r o c essing
1 0 . R e c o nfiguration
r e q u ested if
S e r vice
r e q u ired
C o n f i guration &
A c t ivation
1 5 . Updates
g e n e r ated
a l a r m s notified
M a n a g e Service
o f p roblem
r e s o lution
I n v e ntory
1 1 . R e c o nfiguration
r e q u e sted
1 4 . Details
s e nt of
c o r r ective
a c t ions
R e s o urce
P r o v i sioning
M a n a g e ment
1 3 . Updates
g e n e r ated
n o t ified
2 C . Failure
M a n a g e ment
1 7 . Details sent
R e s o u r c e Trouble
2 B . T hreshold
c r o s s ing alerts
S e r v i ce Problem
M a n a g e ment
M a n a g e R esource
I n v e ntory
4.
R e s o urce
r e s t ored
1 2.
A c t ion(s)
c a r r ied out
S u p plier/
P a r t ner

Cases B and C: Threshold Crossing Alerts and Resource Failure Alarms. Steps 1 to 17
9. Customer QoS/SLA Management may inform the customer of the QoS degradation, depending on the significance of the
customer and the extent of the degradation.
10. If Resource Trouble Management has not been able to trigger automatic resource restoration, Service Problem Management
requests Service Configuration & Activation to undertake the required corrective actions. (Steps 10 to 17 are therefore only
carried out if automatic resource restoration did not take place).
11. As the problems have been notified in the resource layer, Service Configuration & Activation will require changes to be made to
the underlying infrastructure per contractual agreements. This requirement is sent to Resource Provisioning for activation.
12. Resource Provisioning undertakes the required resource configuration changes to ensure that resources meet service KQIs.
13. Resource Provisioning generates updates for Manage Resource Inventory.
GB921F v4.6
Page 49
14. Resource Provisioning reports the results of the changes as well as the time taken and all other infrastructure and operational
parameters to Service Configuration & Activation.
15. Service Configuration & Activation generates updates for Manage Service Inventory.
16. Service Configuration & Activation reports on the actions undertaken to Service Problem Management.
Customer
informed
Market
Product &
Customer
Customer Interface
Management
Customer Interface
Management
25. Customer informed of

restoration of service quality
( optional)
Customer
QoS/SLA
Management
Service
Cus tomer QoS

Report
Received

reports generated and possibly
periodic discussion w ith
Cus tomer undertaken
24. Service QoS

reports generated
Service Quality
Management
23. Rectification
r eport generated
Ser vice Problem

Management
21. Resource
performance reports
generated
Resource
( A pplication,
Computing
and Netw ork)
Resource
Performance
Management
22. Resource
trouble report
closed
20. Rectification
r eport generated
Resource Trouble
Management
19. Resource performance

data passed on
Resource
Performance
Data Available
18.
Resource Data
Collection &
Processing
Supplier/
Partner
Figure 5.9: Normal Execution of SLA Service:

Cases B and C: Threshold Crossing Alerts and Resource Failure Alarms. Steps 18 to 26
GB921F v4.6
Page 50
17. Service Problem Management sends details of the corrective actions to Service Quality Management for incorporation into ongoing
service quality monitoring and management.
18. Notifications and performance data are collected from the service-providing infrastructure by Resource Data Collection &
Processing.
20. Resource Performance Management establishes that the resources are meeting their KPIs and informs Resource Trouble
Management that the trouble has been rectified.
21. Resource Performance Management sends resource performance reports to Service Quality Management for QoS calculations and
averaging to maintain statistical data on the supplied service.
22. Resource Trouble Management informs Service Problem Management of the closed resource trouble report.
23. Service Quality Management analyzes the resource performance reports and sends a rectification report to Service Problem
Management when it is established that the troubles causing the Threshold Crossing Alerts or Alarms have been resolved and that
the service is meeting its KQIs.
24. Service Quality Management sends overall service quality reports to Customer QoS/SLA Management so that it can monitor and
report aggregate technology and service performance.
25. Customer QoS/SLA Management checks the service quality reports it receives against the customer SLA and establishes that no
SLA violation has occurred. It may inform the customer of the quality restoration, depending on the significance of the customer and
the extent of the degradation.
26. Customer QoS/SLA Management sends periodic Service Performance reports to the customer on either a requested or agreed
basis.
Execution with SLA Violation

From time to time, service conditions will exceed the parameters specified in the SLA. At least two cases need to be examined, one
where the Service Provider detects the outage first, and one where the customer detects and reports it first. The second case is
depicted in Figures 5.10 and 5.11.
The steps shown in Figures 5.10 and 5.11 are as follows:
GB921F v4.6
Page 51
1. The customer perceives service degradation and reports the visible parameters to Problem Handling.
C u s t o mer
i n f o rmed
C u s t o mer
R e p o rts
P r o b lem
1 0 a . Actual
M a n a g e m ent
M a r k et
P r o duct &
C u s t o mer
3 . C u stomer
p r i ority
r e t u r ned
1 . C u stomer
p r o b l e m report
p a s s ed on
s e r vice
p e r f o r m ance
r e p o r t ed (if no
p r o b l em)
R e t e ntion &
L o y alty
P r o b l e m Handling
M a n a g e m ent
R e t e ntion &
L o y alty
P r o b l e m Handling
2 . P r o b l e m report info sent
4 . C u s tomer SLA info

r e t u r ned
5 . Details of
p r o b l e m report
S e r vice
9 a . A c tual service
p e r f o r m ance
C u s t o mer
Q o S /SLA
M a n a g e m ent
r e p o r t ed (if no
p r o b l em)
1 1 b . D etails sent
o f p r oblem
r e s o l ution
s e nt
S e r v i c e Problem
M a n a g e m ent
7 . I n v estigation M a n a g e m ent
c o r r e lation
r e q u e sted
R e s o u rce
( A p p l i cation,
C o m p u ting
a n d N e twork)
6 . P roblem
i n v e s t igated at
r e s o u r ce layer
8 . P r oblem or
C u s t o mer
Q o S /SLA
M a n a g e m ent
M a n a g e m ent
1 6 c . D etails sent of
p r o b l e m resolution
1 5 c . D etails sent
o f a ctions
u n d e r t aken
M a n a g e m ent
o t h e r w i s e confirmed
9 b . R e source
r e s t o r ation
r e q u e sted
S e r vice
C o n f i g uration &
9 c . R e c o n figuration
A c t i vation
r e q u e sted
1 0 c.
1 0 b . Details
R e c o n f i g uration
s e nt of
r e q u e sted
r e s t o r ation
R e s o u rce
a c t ions
P r o v i sioning
1 4 c . Updates
g e n e r ated
1 3 c . Details
s e nt of
c o r r e ctive
a c t ions
M a n a g e m ent
1 2 c . Updates
g e n e r ated
M a n a g e m ent
1 1 c.
M a n a g e m ent
M a n a g e Service
I n v e n tory
M a n a g e R esource
I n v e n tory
A c t i on(s)
c a r r i ed out
S u p p lier/
P a r t ner
Figure 5.10: Customer Detected SLA Violation. Steps 1 to 16d

2. Problem Handling sends details of the problem as reported by the customer to Customer QoS/SLA Management and Retention
& Loyalty.
3. Retention & Loyalty returns information to Problem Handling on the significance of the customer.
4. Customer QoS/SLA Management checks the customer SLA and undertakes various steps for tracking the problem in order to
prevent the customer SLA from being violated, e.g. clocks started, tracking initiated. It determines potential priorities or other
actions depending on the type of customer SLA and informs Problem Handling.
5. Problem Handling sends a detailed problem report with contract commitment data and request prioritization to Service Problem
Management for normal flow handling.
GB921F v4.6
Page 52
8. 6/7. Service Problem Management investigates whether there is a problem, possibly engaging Resource Trouble Management
for further investigation, and then requests Service Quality Management to correlate its findings. Service Quality Management
either confirms the trouble report or, if no problem is noted, returns the actual service performance to Service Problem
Management.
Service Problem Management then carries out one of the three following alternatives:
Alternative a
9a. If there is no problem, Service Problem Management sends the actual service performance to Problem Handling.
10a. Problem Handling informs the customer of the actual service performance as well as Retention & Loyalty for future reference
and Customer QoS/SLA Management so that any steps initiated can be terminated.
This flow alternative then terminates.
Alternative b
9b. In some cases, Service Problem Management requests automatic resource restoration procedures from Resource Trouble
Management.
10b. Resource Trouble Management undertakes the required procedures and sends details of the actions to Service Problem
Management.
11b. Service Problem Management informs Service Quality Management of the corrective actions.
The flow continues at step 17.
Alternative c
9c. In other cases, Service Problem Management requests Service Configuration & Activation to undertake the required corrective
actions.
10c. Service Configuration & Activation will require changes to be made to the underlying infrastructure per contractual agreements.
This requirement will be sent to Resource Provisioning for activation.
11c. Resource Provisioning undertakes the required resource configuration changes to ensure that resources meet service KQIs.
12c. Resource Provisioning generates updates for Manage Resource Inventory.
GB921F v4.6
Page 53
13c. Resource Provisioning reports the results of the changes as well as the time taken and all other infrastructure and operational
parameters to Service Configuration & Activation.
14c. Service Configuration & Activation generates updates for Manage Service Inventory.
15c. Service Configuration & Activation reports on the actions undertaken to Service Problem Management.
16c. Service Problem Management sends details of the corrective actions to Service Quality Management for incorporation into
ongoing service quality monitoring and management.
Customer
acknow ledges
pr oblem resolved
Customer Interface
Management
Market
Product &
Customer
22. Problem resolution

r eported to Customer
Cus tomer QoS

Report
Received
Customer Interface
Management
Customer Interface
Management

reports sent (and possibly
periodic discussion w ith
Customer carried out)
26. Customer billed
Customer
QoS/SLA
Management
Pr oblem Handling
Cus tomer Billed
24. Rebate
information
generated
Billing &
Collections
Management
Retention &
Loyalty
23. Service QoS
r estoration confirmed
21. Problem
r esolution
r eported
Service
Ser vice Problem

Management
Resource
( A pplication,
Computing
and Netw ork)
Resource Data
Collection &
Processing
Resource
Performance
Data Available
20. Rectification
r eport generated

data passed on
Service Quality
Management
19. Resource
perfomance reports
generated
Resource
Performance
Management
17.
Supplier/
Partner
Figure 5.11: Customer Detected SLA Violation. Steps 17 to 26

17. Notifications and performance data are collected from the service-providing infrastructure by Resource Data Collection & Processing.
19. Resource Performance Management sends resource performance reports to Service Quality Management for QoS calculations and
averaging to maintain statistical data on the supplied service.
GB921F v4.6
Page 54
20. Service Quality Management analyzes the resource performance reports and sends a rectification report to Service Problem
Management when it establishes that the problem has been resolved and that the service is meeting its KQIs.
21. Service Problem Management reports that the problem has been resolved to Problem Handling.
22. Problem Handling informs the customer and receives acknowledgement from the customer that the problem is resolved.
23. Service Quality Management reports the problem resolution to Customer QoS/SLA Management. Customer QoS/SLA
Management checks the details against the customer SLA and establishes that an SLA violation has occurred.
24. Customer QoS/SLA Management reports the violation rebate to Billing & Collections Management for billing adjustment and to
Retention & Loyalty for future reference.
25. The customer is notified in semi real-time about the actions taken on their behalf.
26. Billing & Collections Management bills the customer at the end of the billing cycle with the SLA agreed treatment included.
Assessment
During the assessment phase, SLAs are examined to determine if they still fit the business needs. There are several triggers for the
assessment, including periodic either per service or overall, customer-triggered reevaluation, customer exit, etc. Figure 4.12 shows
Case A where customer SLA needs have changed because the customers business needs have changed and there is no SLA
meeting these needs, leading to an assessment of the potential for an enhanced product SLA. Figure 4.13 shows Cases B and C
where internal assessments at the Customer and Service layers lead to a realignment of infrastructure support for SLA parameters
and service KQIs respectively. In these flows, Level 3 processes from the Operations Support & Readiness vertical are included for
increased clarity.
The steps shown in Figure 5.12 for Case A are as follows:
1. The customer discusses changed requirements with Selling.
2.
Selling checks the significance of the customer with Retention & Loyalty.
GB921F v4.6
Page 55
C ustomer
I n q uiry Made
C u stomer Interface
Ma n agement
Ma rket
Product &
C ustomer
Retention &
L oyalty
1 . Customer request
for changed SLA
p a rameters made
Selling
2. Information on
C u stomer prioritization
r e quested
P roduct
D e velopment &
R e tirement
5. Enhanced
p roduct SLA
re quested
Input to SLA
Lifecycle Stage 1
P roduct
D e velopment
Support Selling
4. Request
a n alyzed and
passed on
3. Details sent of Customer request

for enhanced SLA
S ervice
R esource
( Application,
C omputing
a n d Network)
S upplier/
P a rtner
Figure 5.12: Assessment Initiation

Case A: Customer needs have changed
3. Selling is unable to meet the customers requirements with existing product SLA(s). It sends details of the customer request to
Support Selling for analysis.
4. After analyzing the request, Support Selling passes it on to Product Development & Retirement for a reassessment of the existing
product SLA(s).
5. Product Development & Retirement reassesses the SLA parameters and sends a request for development of an enhanced
product SLA to the product planning processes.
GB921F v4.6
Market
Product &
Cus tomer
SLA data
1B. SLA
reports
generated
Page 56
Enable Customer
Quality
Management
Customer
Q oS/SLA
Management
2. Action to improve servic e KQI support

for SLAs requested
Serv ice
Service
Performance
Data
Res ource
(Application,
Computing
and Network)
1C. Service
performance
reports
generated
Enable Service
Quality
Management
3. Corrective
action requested
4. Correc tive
action
requested
CRM Operations
Readiness
Service
specification
consistent with SLA
Service
Management &
Operations Rea . ..
Formalized service
configuration
change
14. SLA trend reports

generated
12. Service QoS

reports generated
Enable Serv ice

Configuration &
Activation
8. Updates
generated
Service Quality
Management
Manage Service
Inventory

reports generated
7. Details sent of
corrective action
Resource Data
Collection &
Processing
Manage Resource
Inventory
Enable Resource
Provisioning
6. Updates
generated
5.
13. Service
performance trend
reports generated
Action c arried
out
Resource
Performance
Data Available
10. Resourc e
performance data
passed on
Resource
Performanc e
Management
9.
Supplier/
Partner
Figure 5.13: Assessment Initiation

Cases B and C: Internal Assessments at the Customer and Service Layers
The steps shown in Figure 5.13 for Cases B and C are as follows:
1B. Enable Customer Quality Management receives SLA reports for trend analysis (mainly from Customer QoS/SLA Management).
Enable Customer Quality Management establishes that given SLAs are being violated too often, require excessive rebates, and
that the service KQIs are not supporting the product KQIs.
1C. Enable Service Quality Management receives service quality reports for trend analysis (mainly from Service Quality
Management). Enable Service Quality Management establishes that the service being provided is not meeting the required levels
on an average basis.
2. Enable Customer Quality Management requests Enable Service Quality Management to undertake the required service class
KQI improvements so that they will support the SLAs more adequately.
3. Enable Service Quality Management analyses the problems and requests Enable Service Configuration & Activation to undertake
the required corrective actions to improve the service class KQIs.
4. Enable Service Configuration & Activation requests changes in the infrastructure from Enable Resource Provisioning.
5. Enable Resource Provisioning takes corrective action to ensure that resources meet the service class KQIs.
GB921F v4.6
Page 57
6. Enable Resource Provisioning generates updates for Manage Resource Inventory.

7. Enable Resource Provisioning reports details of its actions to Enable Service Configuration & Activation.
8. Enable Service Configuration & Activation generates updates for Manage Service Inventory.
9. Notifications and performance data are collected from the service-providing infrastructure by Resource Data Collection &
Processing.
11. Resource Performance Management sends resource performance reports to Service Quality Management for QoS calculations
and averaging to maintain statistical data on the supplied service instances.
12. Service Quality Management analyzes the resource performance reports received and sends overall service quality reports to
Customer QoS/SLA Management so that it can monitor and report aggregate technology and service performance.
13. Service Quality Management sends service quality reports to Enable Service Quality Management for trend analysis where it is
established that the service being provided is now meeting the required levels on an average basis.
14. Customer QoS/SLA Management sends SLA reports to Enable Customer Quality Management for trend analysis where it is
established that given SLAs are now consistent with SLA requirements.
GB921F v4.6

Telecom Operation

Uploaded by

Copyright:

Available Formats

Telecom Operation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Telecom Operation

Uploaded by

Copyright:

Available Formats

Enhanced Telecom Operations Map

eTOM Business Process Framework, Addendum F

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

About TeleManagement Forum

Establishing operational guidance on the shape of business

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

About this document

Document Life Cycle

How to obtain a copy

How to comment on the document

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

Released for public review and comment. No

Updated to reflect the process decompositions of

Updated to include new process flows concerning

Updates prior to Release 4.5 Member Evaluation

Summary of Changes in this Version

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

Related or Source Documents

See main document (GB921 v4.0) for additional references.

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

eTOM Business Process Framework, Addendum F

APPLY PRICING, DISCOUNTING & REBATE .............................................................................................................................27

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

Table of Figures and Tables

eTOM Business Process Framework, Addendum F

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

eTOM Business Process Framework

TeleManagement Forum 2004

A main document (GB921) that provides an overview of the eTOM

eTOM Business Process Framework, Addendum F

A separate Application Note (GB921L) that shows how eTOM can be

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

eTOM Business Process Framework, Addendum F

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

Chapter 2 - Billing-Related Flows

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

Process Flow (eTOM Level 3 processes)

Request for prepaid call

eTOM Business Process Framework, Addendum F

Process Flow (eTOM level 3 processes)

Request for prepaid call

Call not Authorized

TeleManagement Forum 2004

eTOM Business Process Framework, Addendum F

Process Flow (eTOM Level 3 processes)

Figure 2.3: Billing flow prepaid: Debit request