1. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Cisco's Journey Towards Cleaner Customer Data Tina Owenmark, Program Manager, Cisco David Joffe, Applications Architect, Abacus Business Solutions

2. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 2 Agenda  Brief History of Oracle eBusiness Suite at Cisco  Customer Data at Cisco  Cisco’s Data Consolidation Methodology  Lessons Learned / Recommendations for others  Q & A

3. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 3 Oracle eBusiness Suite at Cisco First Oracle implementation, R10.4 1995 2003 - 5 New instances were gradually introduced to support different geos, modules and business needs Current state: Cisco has 10 production Oracle eBusiness Suite instances that are all R11i or R12. Many instances are highly customized AND have complex integrations with each other and with external non-Oracle EBS systems 1998 All instances upgraded to R11i 10.7 Upgrades in advance of Y2K 2007 First R12 instance live at Cisco

4. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 4 Customer Data at Cisco  Cisco has over 2.5 million customer accounts and 6.4 million customer addresses in its core Quote to Cash instances  Customer data can be created through a variety of applications and flows  Customer data is synchronized across multiple EBS and non-EBS instances through Customer Data Hub like replication methodology  More than one million customer accounts are logical duplicates

5. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 5 Why customer data cleanup? Bad / duplicate customer data causes:  Challenges in automating reporting process  Performance problems  User confusion / dissatisfaction  Difficulty in executing future projects Project formed to:  Reduce amount of duplicates by inactivating records IdParty Name 158WIDGETS INC 341WIDGETS INC 345WIDGETS 489WIDGETS SYSTEMS INC 548WIDGETS SYSTEMS

6. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 6 Defining Business Rules: Iterative Approach  Apply proposed steps manually to several sample customers  Review results with all affected teams  Refine steps, re-apply to other customers  Continue to refine steps iteratively until the wider team feels comfortable  Develop scripts to automate many of the consolidation steps

7. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 7 Data Consolidation Steps 1.Identify a batch of potential duplicates according to company name 2.Collect and compare attributes of all the records 3.Gather stats about transactional utilization of each record 4.Decide which records to keep and which records to consolidate 5.Validate that candidate records are eligible for inactivation 6.Inactivate the appropriate records 7.Move useful auxiliary data from the inactivated records to the keeper records 8.Update transactional data 9.Propagate changes to downstream systems

8. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 8 Identify Potential Duplicates: Simple Match Party IdParty Name 158WIDGETS INC 341WIDGETS INC

9. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 9 Identify Potential Duplicates: Complex Match  Using more complex methodology (DQM based) finds more matches  Downside: some may be false duplicates. Need to find right balance Party IdParty Name 158WIDGETS INC 341WIDGETS INC 345WIDGETS 489WIDGETS SYSTEMS INC 548WIDGETS SYSTEMS

10. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 10 Decide which records to keep  Our rules generally involve keeping the records that are most transactionally active  Our data analysis has shown that consistently usage of the records is highly skewed to one or a few records

11. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 11 Validate Inactivation Candidates  Functional teams have provided various conditions under which records may not be consolidated  Conditions may be based on attributes, auxiliary data, or transaction data (from internal or external databases) Examples:  Do not inactivate records that are used in EDI transactions  Do not inactivate records that have special tax set ups IdParty Name # of TxnsStatus 158WIDGETS INC794KEEPER 341WIDGETS INC36INACTIVATE 345WIDGETS3INACTIVATE 489WIDGETS SYSTEMS INC2INACTIVATE 548WIDGETS SYSTEMS7SKIP – TAX SETUPS

12. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 12 Inactivate and Consolidate  Critical data is copied from the inactivated record to the keeper record according to business rules: Examples: address, contacts, address level credit profiles  Only copy data that: Does not exist already on the KEEPER record Is actively used in transaction systems IdParty Name # of TxnsStatus 158WIDGETS INC794KEEPER 341WIDGETS INC36INACTIVATED 345WIDGETS3INACTIVATED 489WIDGETS SYSTEMS INC2INACTIVATED 548WIDGETS SYSTEMS7SKIP – TAX SETUPS

13. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 13 Update Transactional Data as Necessary  It is not generally mandatory to repoint the transaction records –Sales Orders and Invoices  For certain business functions, it is required that transactional data should be updated –Service Contracts and Install Base  Recommend attempting to discourage updates to transaction data as much as possible unless there is a very critical reason cited  Reasons to discourage transactional updates: –Can take a long time to execute and can cause performance / downstream impacts

14. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 14 Keys to Driving Successful Deployment  Gradual rollout  MANY functional teams need to participate, provide rules, and give buy off.  Provide LOTS of data to increase affected teams’ confidence  Start strict, analyze results, and loosen rules as appropriate  Treat data cleanup as an ongoing, repeatable process and not a one time activity  Consider downstream and external impacts  Log and publish errors and results

15. © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 15