Presented by : Ravindra nath sharma  MBA(SDM) (07-09) SCIT PUNE(symbiosis international university) IBM EVS (Export Valida...
Agenda <ul><li>Case Description </li></ul><ul><li>Current System </li></ul><ul><li>Architecture Of CCM System </li></ul><u...
Enterprise - IBM <ul><li>Business lines  </li></ul><ul><li>Software and hardware with complete solutions  </li></ul><ul><l...
Current system <ul><li>Access Information through legacy system. </li></ul><ul><li>Can not use updated information at a ti...
Architecture of CCM System.
Critical Key entry Points <ul><li>Connectivity –  </li></ul><ul><ul><li>Information feeds from these other distributed cus...
Eleven entry points on the road to SOA
Entry Points/ Functions People Process Information  Connectivity Reuse Customer Administrator X X X X Credit Score X X X M...
Entity – Process Relationship Entity/Process Customer Transaction Product  Business Units Login  R Credit Score R R New Cu...
Entity Identified <ul><li>The entities identified under the case are as follows </li></ul><ul><ul><li>Customer  </li></ul>...
Weak Entity <ul><li>Credit score </li></ul><ul><li>Communication History </li></ul>
Application Integration <ul><li>CRM Siebel (North America) </li></ul><ul><li>CRM Siebel (AP South) </li></ul><ul><li>NIW  ...
 
Upcoming SlideShare
Loading in …5
×

IBM EVS (Export Validation Service) case study – Common Customer Master System

1,577 views

Published on

IBM EVS (Export Validation Service) case study – Common Customer Master System

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,577
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
33
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

IBM EVS (Export Validation Service) case study – Common Customer Master System

  1. 1. Presented by : Ravindra nath sharma MBA(SDM) (07-09) SCIT PUNE(symbiosis international university) IBM EVS (Export Validation Service) case study – Common Customer Master System
  2. 2. Agenda <ul><li>Case Description </li></ul><ul><li>Current System </li></ul><ul><li>Architecture Of CCM System </li></ul><ul><li>Critical Entry Points </li></ul><ul><li>Entity/ Function Relationship </li></ul><ul><li>Entity/ Process Relationship </li></ul>
  3. 3. Enterprise - IBM <ul><li>Business lines </li></ul><ul><li>Software and hardware with complete solutions </li></ul><ul><li>Consulting business for software solution </li></ul><ul><li>BPO /KPO/LPO </li></ul><ul><li>IBM educational partnership and certification </li></ul>
  4. 4. Current system <ul><li>Access Information through legacy system. </li></ul><ul><li>Can not use updated information at a time for all different Branches. </li></ul><ul><li>Impact on customer satisfaction. </li></ul><ul><li>Can not access customer organization and contact information at a time. </li></ul><ul><li>Lacking in consistency and continuity. </li></ul>
  5. 5. Architecture of CCM System.
  6. 6. Critical Key entry Points <ul><li>Connectivity – </li></ul><ul><ul><li>Information feeds from these other distributed customer repositories will be unsettled and replaced by this single system. </li></ul></ul><ul><li>Information – </li></ul><ul><ul><li>The integration of customer data from different data sources -- including Dunn and Bradstreet (D&B), IBM's customer data stored in the Reference Data customer (RDc) hub (representing customer information from a variety of IBM customer databases), and CRM/Siebel (with three separate instances in North America, Europe, and Asia Pacific). </li></ul></ul>
  7. 7. Eleven entry points on the road to SOA
  8. 8. Entry Points/ Functions People Process Information Connectivity Reuse Customer Administrator X X X X Credit Score X X X Multi channel Support X X X International Support X X X Multi product Support X X X
  9. 9. Entity – Process Relationship Entity/Process Customer Transaction Product Business Units Login R Credit Score R R New Customer Profile Creation W Communication History Creation R R R R Customer Updating U
  10. 10. Entity Identified <ul><li>The entities identified under the case are as follows </li></ul><ul><ul><li>Customer </li></ul></ul><ul><ul><li>Payment </li></ul></ul><ul><ul><li>Enquiry </li></ul></ul><ul><ul><li>Transaction </li></ul></ul><ul><ul><li>Product </li></ul></ul><ul><ul><li>Business Unit </li></ul></ul><ul><ul><li>Data Source </li></ul></ul><ul><ul><li>Data Server </li></ul></ul>
  11. 11. Weak Entity <ul><li>Credit score </li></ul><ul><li>Communication History </li></ul>
  12. 12. Application Integration <ul><li>CRM Siebel (North America) </li></ul><ul><li>CRM Siebel (AP South) </li></ul><ul><li>NIW </li></ul><ul><li>S&D Finance </li></ul><ul><li>CRM/Siebel (EMEA) </li></ul>

×