• Save
RODOD, RSDOD Implementation Pitfalls
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

RODOD, RSDOD Implementation Pitfalls

  • 181 views
Uploaded on

RODOD, RSDOD Implementation Pitfalls

RODOD, RSDOD Implementation Pitfalls

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
181
On Slideshare
154
From Embeds
27
Number of Embeds
7

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 27

http://philipjung.blogspot.kr 15
http://philipjung.blogspot.in 4
https://www.blogger.com 3
http://philipjung.blogspot.sg 2
http://philipjung.blogspot.com 1
http://philipjung.blogspot.co.uk 1
http://philipjung.blogspot.pt 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. RODOD/RSDOD Implementation Pitfalls (Type: PPT, Total Page: 23) Most common pitfalls by Implementation Partners in CRM Telco implementations are related to Order Management, Integration & Customer Management: Complex Order Management (C/OM) Asset-based ordering (ABO) workflow processes. Poorly designed Sales Order Capture process, in particular ABO workflow processes. These mistakes in design of Siebel ABO processes impact down streams systems as well Lack of expertise on PSP framework, which leads to over customization & poor performance of the eligibility rules execution Product Modeling. Large & complex models are designed from Product Configurator‟s technical perspective, without much consideration about the other appropriate functionality, which can help reduce the size & improve the performance of the product model. Design of the product Models is tightly integrated with the ABO design and consequently with e2e order mgt processes. Poor design is very difficult to rectify once in place due to the broad impact C/OM Web services - Rarely processes are designed with a cross-channel view. Most of the times the Order Mgt processes are not designed with the self-service or IVR channels in mind Customer Management. Customer Modeling (B2B) for Customer, Service, Billing hierarchies. Design of over-complicated Customer structures that mostly reflect billing structure and integration needs rather than how customer wants to do business with the organization General lack of skills on Customer Mastering, and Cross-referencing with Legacy systems Customer Modeling (B2C), Cash accounts/prospects, Contact/Household modeling. A common mistake is to model all customers as large organizations instead of leveraging households model Contact: yohaim@gmail.com Blog: http://philipjung.blogspot.kr Example