Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Migrating from SAP BusinessObjects to Oracle Business Intelligence Applications


Published on

As organizations consider upgrading their ERP solution, many are faced with the decision of whether to continue with legacy SAP BusinessObjects or migrate to Oracle Business Intelligence Applications. Among the evaluation criteria are total cost of ownership, evolving business requirements, and existing investments, along with customizations built over years. Attend this session to hear firsthand from customers that have made the decision to migrate to Oracle Business Intelligence Applications. Discussion topics include selection criteria for choosing a single industry-standard enterprise reporting platform and benefits achieved by standardizing on Oracle Business Intelligence.

Published in: Technology, Business
  • Be the first to comment

Migrating from SAP BusinessObjects to Oracle Business Intelligence Applications

  1. 1. ORACLE PRODUCT LOGO Migrating from SAP BusinessObjects to: Oracle Business Intelligence Maria Forney, Director, Customer Programs1 Venkat Penaganti, (IT Manager), St. Jude Medical Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Restricted
  2. 2. 2 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Restricted
  3. 3. St. Jude MedicalBusiness Objects to Oracle BI EEConversion
  4. 4. SJM Quick Facts §  Develop, manufacture, and distribute cardiovascular and neurostimulation medical devices worldwide. §  Founded 1976, St. Paul ,MN §  16,000 employees. §  $5.2 billion sales (50% international, 50%domestic). §  Four Key divisions: §  Cardiac Rhythm Management (CRMD) §  Atrial Fibrillation (AF) §  Cardio-vascular §  Neuro-Modulation4
  5. 5. CRMD Major Product Lines §  Devices §  Implantable Cardiac Defibrillators (ICDs) for Tachycardia §  Accelerated heart rate §  Pacemakers (Pacers) for Bradycardia §  Slow heart rate §  Leads §  High Volt. Leads (HVL) and Low Volt. Leads §  Manufacturing is in 7 sites across the globe. §  We are part of Sylmar site IT.5
  6. 6. Installed Product6
  7. 7. Our BI Situation (1 year ago) §  Site §  Sylmar has multiple applications – ERP , MES and PDM. §  No common BI solution / tool. §  Each application has it’s own BI tool. §  MES application §  MES (Manufacturing Execution System) application called Factory Talk Production Center. §  Used on the manufacturing floor for traceability and processing history.7
  8. 8. Our BI Situation (1 year ago) (contd.) §  Used Business Objects 5.3 as it is packaged with MES. §  Our user base involves §  Production supervisors / leads for operational metrics. §  Managers / directors to monitor manufacturing for output. §  Planners to understand inventory needs. §  100 users and 50 reports from two sites. §  Reports were mostly operational §  Production and Historical schemas are both OLTP (no data- warehouse). §  No dedicated BI team. Application developers were part-time report writers.8
  9. 9. Issues with Business Objects (MES) §  Universe hard to maintain against OLTP. §  Long lead times to develop reports. §  The universe layer complicated queries. §  Most reports were ad-hoc queries not analytical. §  Ad-hoc reports §  Operational reports take longer to write because of universe. §  Features §  Could not build dash-boards.9
  10. 10. Why did we move to Oracle BI? §  Business Needs §  A common BI solution is needed to support business metrics / needs spanning sites and application. §  Dash-boards and faster ad-hoc reports. §  IT needs §  MES vendor chose another Reporting tool. §  Good references for OBIEE from other teams and independent reports. §  Decided to use Oracle BI 11G publisher (only) as faster operational reports is our priority.10
  11. 11. Execution (Buy-in from management) §  Identify key decision makers and make them aware of current issues. §  Better ROI and lower TCO. §  Platform suited to meet current and future needs. §  Better Report delivery times. No universe §  Availability of Dash-boards. §  Support §  We know we could get good support from Oracle based on experience. §  Agreed to try OBIEE as MES reporting tool as a proof of concept for all future BI needs.11
  12. 12. Execution (Project) §  Reduce scope to convert existing reports and build 2 dash boards. §  KPI partners was the contracting partner to perform conversion and provide guidance. §  Steered us towards OBIEE 11G. §  Created dev servers for us to replicate and debug memory issues §  Resources for the project §  KPI partners: 1 Lead and 4 developers §  St Jude Medical: §  2 developers - programmers §  1 Project manager §  1 middleware admin – Oracle DBA §  3 business users for testing – Prior experience12 with Business Objects reports
  13. 13. Execution (Project) §  Cross-training: During user testing we had KPI and my team trouble-shoot issues. §  Used KPI to create dash-board templates and later enhance them with my team. §  Try to create standard metrics for dash- boards.13
  14. 14. Results §  All 40 reports converted in 6 months. §  Users are happy about faster ad-hoc reports, interactive reports & dashboards. §  User base has increased. §  Resources for on-going support §  St Jude Medical §  2 developers – programmers (part-time) §  1 middle-ware admin – Oracle DBA “The dash-boards are exactly as I thought. What took us so long? Now we can free up supervisors from collecting data, and focus14 on manufacturing” - Director of Manufacturing
  15. 15. Next Steps §  Creating more reports, dash-boards and also sourcing data from other systems. §  Exploring score-cards and KPIs. §  Creating common definition for manufacturing metrics. §  Make Oracle BI our standard §  Expanding to other sites15
  16. 16. Example (Dashboard) §  Shows reworks and work in progress. §  Benefits: Helps schedule resources & identify slow moving operations.16
  17. 17. Example (Reports) §  Reports are on the web. Submitted to FDA §  Aggregate and detail reports are available. §  Reports are created from the same data model.17
  18. 18. Lessons Learned §  Get better grip on Validation cycle. §  Business had little incentive as they already had reports. 2 months lost. §  Keep in mind the organizational maturity in terms of data needs. §  Common metric definition is key. §  Training needs to happen way earlier both for report developers and administrators. §  Make the SOW with contractor very clear for support. §  Dashboards need Answers not just Publisher. §  Careful with caching parameters. Can be set at multiple levels.18
  19. 19. Questions19
  20. 20. 20 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Restricted
  21. 21. 21 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Restricted