telecommunication business process - etom flows

38
© 2015 RobertBratulic.com Telecommunications Business Process – eTOM Flows Business Architecture, Engineering & Transformation

Upload: robert-bratulic

Post on 11-Jan-2017

17.531 views

Category:

Business


66 download

TRANSCRIPT

Page 1: Telecommunication Business Process - eTOM Flows

© 2015 RobertBratulic.com

Telecommunications Business Process – eTOM Flows

Business Architecture, Engineering & Transformation

Page 2: Telecommunication Business Process - eTOM Flows

2 © 2015 RobertBratulic.com

Table of Contents

Understanding Process Flows Detailed Walk-Through of Major Customer-Centric End-to-End Process

Flows Using eTOM Request-to-Answer Order-to-Payment Usage-to-Payment Problem-to-Solution

Prerequisite Familiarity with eTOM level-2 processes, especially Fulfillment, Assurance and

Billing

Page 3: Telecommunication Business Process - eTOM Flows

3 © 2015 RobertBratulic.com

eTOM is a business process framework organized as a hierarchical process listing or decomposition, i.e. “tree diagram” – which is great for classifying “what” a process does into categories and sub-categories … … but eTOM does not contain process flows, i.e. “blocks and arrows” – which

people look for to understand “how” a process actually unfolds.

Understanding Process Flows

eTOM Level-1 View eTOM Hierarchical Decomposition

Level-2

Level-3

Level-4

Page 4: Telecommunication Business Process - eTOM Flows

4 © 2015 RobertBratulic.com

Understanding Process Flows: A Sample Process Decomposition

Enterprise Management

Page 5: Telecommunication Business Process - eTOM Flows

5 © 2015 RobertBratulic.com

Understanding Process Flows: A Sample Process Flow

“Manage Billing Inquiries”

Page 6: Telecommunication Business Process - eTOM Flows

6 © 2015 RobertBratulic.com

Understanding Process Flows: Process Decompositions and Flows are Complementary

Both process listings/decompositions and process flows are needed – just like a book’s index (listing by category) and table of contents (flow) are both needed, but for different purposes. Process flow, business stream, value stream, journey – these terms are often

used interchangeably, but the common intent is to show a time sequence from one step to another rather than a listing or decomposition which shows no such flows (eTOM out of the box). An eTOM listing/decomposition alone is helpful for creating “heat maps”, to show

what processes are in scope, where functional gaps exist, etc. … … but engaging clients in process discussions with eTOM but no process flows is

hardly better than a dictionary and a blank sheet of paper – eTOM on its own simply has no process content the way most business people think of process! So we need to pre-build process flows, using TMForum examples, work from past

engagements, process experts, best practices, etc…. but where do we start?

Page 7: Telecommunication Business Process - eTOM Flows

7 © 2015 RobertBratulic.com

Understanding Process Flows: End-to-End Process Flows

There are infinitely many possible flows one can construct using eTOM blocks. Which flows are the best ones to prepare? Based on the need to have holistic and intuitive flows, our focus will be on

customer-centric, “end-to-end” flows, suggesting a “closing of the loop”, i.e. the customer who has triggered the flow by placing a request, receives satisfaction as to the request’s completion by the end of the flow. For example, the process flow “Configure Router” would not be an end-to-end flow from

the customer’s perspective, since it typically would not begin and end with a customer action. However, a flow that begins with customer placement of an order, follows with fulfillment

of the order by the CSP (including router configuration), and ends with customer confirmation of product delivery, would be an end-to-end flow.

Unfortunately, there is no one common set of “end-to-end flows”, although there is no shortage of terms for such constructs, often with an “X to Y” naming pattern, like “Lead to Order”, “Order to Cash”, “Hire to Retire”, “Record to Report”, etc.

Page 8: Telecommunication Business Process - eTOM Flows

8 © 2015 RobertBratulic.com

Understanding Process Flows: TMForum Process Flows

The relatively recent eTOM document “GB921 Addendum E” attempts to add to this discourse, by describing the several major customer-centric flows – the four depicted below will be the core of this presentation.

Usa

ge-to

-Pay

men

t

Prob

lem

-to-S

olut

ion

Ord

er-to

-Pay

men

t

Req

uest

- to

-Ans

wer

Page 9: Telecommunication Business Process - eTOM Flows

9 © 2015 RobertBratulic.com

Understanding Process Flows: Accessing eTOM Documentation

While TMForum and eTOM documentation is not at all necessary to go through this presentation, if you are a TMForum member, then you will have access to the source documents. The latest eTOM materials can be found here: Primary archive – PDF: https://www.tmforum.org/resources/suite/gb921-business-

process-framework-r14-5-1-pdf/ Alternate archive – Word: https://www.tmforum.org/resources/suite/gb921-business-

process-framework-r14-5-1-word/ Handy Poster: https://www.tmforum.org/resources/standard/business-process-

framework-etom-poster-frameworx-14-5etom/ Note that the TMForum update cycle is 6-months, so these links may change, in

which case you will need to search on the TMForum site for the latest archive of refreshed eTOM documents. Much of the content and images for this PowerPoint walk-through come from: “GB921E End to End Process Flows R13.5.0.docx”

Keep in mind that there is no one “correct” process flow. The examples which follow are illustrative, and suppress detail when it is repetitive or cluttered. We’re now ready to begin with the first process flow …

Page 10: Telecommunication Business Process - eTOM Flows

10 © 2015 RobertBratulic.com

Flow 1: Request-to-Answer

Overview This process flow comprises activities relevant to managing customer requests across all

communication channels (customer interfaces). Specific information requests or product requests from the customer are qualified and addressed. This could lead to the preparation of a pre-sales offer if the customer shows interest in a particular

product. Assumptions

The offer preparation may or may not lead to a reservation of resources in advance. Resources might be reserved for some special products or customers depending on the operator‘s

policies and procedures. If the offer is accepted by the customer, the next process flow ‘Order to Payment‘ is triggered.

Examples Customer calls in to request product and pricing information Customer walks into a store interested in upgrading to an HD set-top box Customer logs on to a website to explore offerings Customer sends an email to ask request product literature

Page 11: Telecommunication Business Process - eTOM Flows

11 © 2015 RobertBratulic.com

Request-to-Answer: Key Elements

Presentation of portfolio Inform about products Customer access to product

portfolio Handle customer retention and

loyalty Handle customer data Offer management Handle product request Provide status information Provide consultation Trigger to perform cross- or up-

selling activities

Tasks

Customer need Customer product request General information request Product catalog Product portfolio

Input Offer Product information General information Status information

Output

Time to offer Amount new customers (per product) Customer requests vs. offers Ability to offer seamless services Standardized vs. individual offers Product complexity

Request handling time Customer satisfaction measurement First done rate Availability of relevant information Availability of products and services at

customer location Availability of contact center and channels

Critical Issues

Request-to-Answer

Page 12: Telecommunication Business Process - eTOM Flows

12 © 2015 RobertBratulic.com

Request-to-Answer: Footprint in eTOM Level-2

1.1.1.1 CRM - Support & Readiness

1.1.1.2 Customer Interface Management

1.1.1.3 Marketing Fulfillment Response

1.1.1.4 Selling 1.1.1.5 Order Handling 1.1.1.9 Retention & Loyalty

eTOM Level2Request-to-Answer

OperationsOperations Support & Readiness

Fulfillment Assurance Billing & Revenue Mgmt

Customer Relationship Management

Service Management & Operations

Supplier/Partner Relationship Management

Resource Management & Operations

Supplier / Partner Interface Management

Retention & Loyalty

Customer Interface Management

CRMSupport &Readiness

SM&OSupport &Readiness

RM&OSupport &Readiness

S/PRMSupport &Readiness

Service Guiding & Mediation

S/P Settlements& PaymentsManagement

Resource Data Collection & Distribution

ResourceProvisioning

ServiceConfiguration& Activation

S/P ProblemReporting &

Management

S/PPerformanceManagement

S/P Requisition

Management

ResourceTrouble

Management

ResourcePerformanceManagement

ServiceProblem

Management

ServiceQuality

Management

ProblemHandling

CustomerQoS / SLA

Management

Selling

OrderHandling

MarketingFulfillmentResponse

Bill Payments & Receivables Management

Manage Billing EventsCharging

Resource Mediation &

Reporting

Manage Workforce

Bill Inquiry Handling

Bill Invoice Management

OperationsOperations Support & Readiness

Fulfillment Assurance Billing & Revenue Mgmt

Customer Relationship Management

Service Management & Operations

Supplier/Partner Relationship Management

Resource Management & Operations

Supplier / Partner Interface Management

Retention & Loyalty

Customer Interface Management

CRMSupport &Readiness

SM&OSupport &Readiness

RM&OSupport &Readiness

S/PRMSupport &Readiness

Service Guiding & Mediation

S/P Settlements& PaymentsManagement

Resource Data Collection & Distribution

ResourceProvisioning

ServiceConfiguration& Activation

S/P ProblemReporting &

Management

S/PPerformanceManagement

S/P Requisition

Management

ResourceTrouble

Management

ResourcePerformanceManagement

ServiceProblem

Management

ServiceQuality

Management

ProblemHandling

CustomerQoS / SLA

Management

Selling

OrderHandling

MarketingFulfillmentResponse

Bill Payments & Receivables Management

Manage Billing EventsCharging

Resource Mediation &

Reporting

Manage Workforce

Bill Inquiry Handling

Bill Invoice Management

Page 13: Telecommunication Business Process - eTOM Flows

13 © 2015 RobertBratulic.com

Request-to-Answer: Where to Get eTOM Level-3 Detail?

eTOM Level-3 Detail: GB921 Addendum D eTOM Level-4 Detail: GB921 Addendum DX http://www.tmforum.org

Page 14: Telecommunication Business Process - eTOM Flows

14 © 2015 RobertBratulic.com

Request-to-Answer: Relevant eTOM Level-2 Decompositions, Part 1

Note: For Level-3 block details, consult TMForum GB921 Addendum

(Red checkmark = block used in process sample)

Level-2

Level-2

Level-2

Level-3

Level-3

Level-3

Page 15: Telecommunication Business Process - eTOM Flows

15 © 2015 RobertBratulic.com

Request-to-Answer: Relevant eTOM Level-2 Decompositions, Part 2

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2 Level-2

Level-3

Level-3 Level-3

Page 16: Telecommunication Business Process - eTOM Flows

16 © 2015 RobertBratulic.com

Request-to-Answer: Sample Flow in eTOM Level-3

Manage Prospect

Determine Customer Order Feasibility assumes that a Sales Proposal was established and a Customer Order will be issued to execute this proposal, thenthe Detemine Customer Order Feasibility should be invoked after the execution

of Develop Sales Proposal.

Manage ContactIssue & Distribute

Marketing Collaterals

Determine Customer Order

Feasibility

Develop Sales Proposal

Validate Customer

Satisfaction

Manage Request (Including Self

Service)

Resource Inventory

Sevice Inventory

Costomer Subscription

Inventory

Customer request

Customer identified

Information request fulfilled

Sales requestProduct not available

Check product

availability

Check customer provisioning (for existing customer)

Product available

Customer selects product & provides configuration info…

Sales proposal received by customer

Customer satisfaction validated

Offer elaborated & submitted

Mar

ket P

rodu

ct &

Cus

tom

erS

ervi

ceR

esou

rce

(App

licat

ion,

C

ompu

ting

and

Net

wor

k)

Sup

plie

r/ P

artn

er

BPMN Start Symbol

BP

MN

End

Sym

bol

These process models use the common BPMN process notation standard. Start with Wikipedia if you want to know more about BPMN notation.

Page 17: Telecommunication Business Process - eTOM Flows

17 © 2015 RobertBratulic.com

Flow 2: Order-to-Payment

Overview This process deals with all activities which convert the customer request or an accepted offer into a

‘Ready for use’ product. This process involves capturing customer order information, triggering the relevant provisioning

process and handing over the order to the Service layer. Once the product is successfully provisioned, the customer order is closed and the customer

satisfaction is validated. Assumptions

This scenario is relevant for products offered to the mass customer base. Pre-order feasibility check verifies whether the requested product can be offered to the customer

based on the service / resource availability, the product portfolio, and the customer’s configuration. Pre-order feasibility check would not generally involve the reservation of resources prior to issuance

of customer order. However, there might be a reservation of some critical resources, depending on the operator‘s

policies and procedures. Examples

Customer calls to order high-speed internet Customer walks into a shop to buy a mobile phone with service

Page 18: Telecommunication Business Process - eTOM Flows

18 © 2015 RobertBratulic.com

Order-to-Payment: Key Elements

Page 19: Telecommunication Business Process - eTOM Flows

19 © 2015 RobertBratulic.com

Order-to-Payment: Footprint in eTOM Level-2

Page 20: Telecommunication Business Process - eTOM Flows

20 © 2015 RobertBratulic.com

Order-to-Payment: Relevant eTOM Level-2 Decompositions, Part 1

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-2

Level-3

Level-3

Level-3

Page 21: Telecommunication Business Process - eTOM Flows

21 © 2015 RobertBratulic.com

Order-to-Payment: Relevant eTOM Level-2 Decompositions, Part 2

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-3

Level-3

Page 22: Telecommunication Business Process - eTOM Flows

22 © 2015 RobertBratulic.com

Order-to-Payment: Relevant eTOM Level-2 Decompositions, Part 3

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-2

Level-2

Level-3

Level-3

Level-3

Level-3

Page 23: Telecommunication Business Process - eTOM Flows

23 © 2015 RobertBratulic.com

Order-to-Payment: Relevant eTOM Level-2 Decompositions, Part 4

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-3

Level-3

Page 24: Telecommunication Business Process - eTOM Flows

24 © 2015 RobertBratulic.com

Order-to-Payment: Sample Flow in eTOM Level-3

Page 25: Telecommunication Business Process - eTOM Flows

25 © 2015 RobertBratulic.com

Flow 3: Usage-to-Payment

Overview This process deals with all activities related to the handling of the product/service usage. The accuracy of pricing is ensured and all usage data is captured and duly processed for billing

information requests and bill generation. Assumptions

This scenario is relevant for products offered to the mass customer base. The process elements ‘Mediate Resource Usage Records‘ and ‘Guide Resource Usage Records‘ are

not always applicable. ‘Perform Rating‘ element is usually under the Customer layer for customized products, and under the

Service layer for standardized products. Examples

Customer makes toll calls Customer receives a report of all long-distance phone calls made last month

Page 26: Telecommunication Business Process - eTOM Flows

26 © 2015 RobertBratulic.com

Usage-to-Payment: Key Elements

Page 27: Telecommunication Business Process - eTOM Flows

27 © 2015 RobertBratulic.com

Usage-to-Payment: Footprint in eTOM Level-2

Page 28: Telecommunication Business Process - eTOM Flows

28 © 2015 RobertBratulic.com

Usage-to-Payment: Relevant eTOM Level-2 Decompositions, Part 1

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-2

Level-3 Level-3

Level-3

Page 29: Telecommunication Business Process - eTOM Flows

29 © 2015 RobertBratulic.com

Usage-to-Payment: Relevant eTOM Level-2 Decompositions, Part 2

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-2

Level-2

Level-3 Level-3

Level-3

Level-3

Page 30: Telecommunication Business Process - eTOM Flows

30 © 2015 RobertBratulic.com

Usage-to-Payment: Sample Flow in eTOM Level-3

Page 31: Telecommunication Business Process - eTOM Flows

31 © 2015 RobertBratulic.com

Flow 4: Problem-to-Solution

Overview This process deals with a technical complaint (problem) initiated by the customer, analyzes it to

identify the source of the issue, initiates resolution, monitors progress and closes the trouble ticket. The basis for a problem is an unplanned interruption to a product / service or reduction in the quality

of a product/service. (In comparison, the process “complaint-to-solution” deals with customer inquiries in which the customer is not pleased with a product or handling speed of an inquiry etc.)

Assumptions This scenario is relevant only for technical complaints which are termed as ‘problems’. Problems such as no outgoing call or SMS and faulty handset, may be resolved at first level support

or re-directed to other layers Examples

Customer calls to report that there is no internet access Customer calls to report a cable channel has choppy video

Page 32: Telecommunication Business Process - eTOM Flows

32 © 2015 RobertBratulic.com

Problem-to-Solution: Key Elements

Page 33: Telecommunication Business Process - eTOM Flows

33 © 2015 RobertBratulic.com

Problem-to-Solution: Footprint in eTOM Level-2

Page 34: Telecommunication Business Process - eTOM Flows

34 © 2015 RobertBratulic.com

Problem-to-Solution: Relevant eTOM Level-2 Decompositions, Part 1

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-2

Level-3

Level-3

Level-3

Page 35: Telecommunication Business Process - eTOM Flows

35 © 2015 RobertBratulic.com

Problem-to-Solution: Relevant eTOM Level-2 Decompositions, Part 2

Note: For Level-3 block details, consult TMForum GB921 Addendum D

Level-2

Level-2

Level-2

Level-2

Level-3 Level-3

Level-3 Level-3

Page 36: Telecommunication Business Process - eTOM Flows

36 © 2015 RobertBratulic.com

Problem-to-Solution: Sample Flow in eTOM Level-3

Page 37: Telecommunication Business Process - eTOM Flows

37 © 2015 RobertBratulic.com

Conclusion

In this guided PowerPoint walkthrough, we have reviewed the following customer-centric, end-to-end flows, and how they can be constructed out of eTOM processes: Request-to-Answer Order-to-Payment Usage-to-Payment Problem-to-Solution

Remember, the eTOM framework does not contain process flows itself. eTOM gives you the elements with which to build a process (flow), and these elements are organized by process (hierarchy). To connect with business people, you need to have flows! This should help you on process projects, when you have to build process flows

using eTOM.

Page 38: Telecommunication Business Process - eTOM Flows

38 © 2015 RobertBratulic.com

For More Information

TMForum eTOM primary archive – PDF: https://www.tmforum.org/resources/suite/gb921-business-

process-framework-r14-5-1-pdf/ eTOM alternate archive – Word: https://www.tmforum.org/resources/suite/gb921-

business-process-framework-r14-5-1-word/ Within archive, find:

eTOM Process Flows: GB921E End to End Process Flows R13.5.0.docx eTOM Level-3 Detail: GB921 Addendum D eTOM eTOM Level-4 Detail: GB921 Addendum DX

Robert Bratulic www.robertbratulic.com