MoneyGram International, Inc.

1. MoneyGram International, Inc. MoneyGram’s Business Intelligence Implementation for Oracle Applications TCF OAUG May 15, 2008 Pat Redding Kathy Follese

2. MoneyGram International, Inc. • Leading global payment services company • 2nd largest global money transfer company • Over 150,000 global money transfer agent locations • Over 2000 employees worldwide • NYSE company: “MGI”

3. Background • MoneyGram’s current environment consists of a number of legacy operational systems • Decided to implement Oracle EBS in 2004 to streamline operational systems • Oracle GL/AP went live in Jan ’07 • BI/DW for GL/AP went live in Dec ‘07 • Currently in progress • AR/Settlement • Agent Data Hub • BI/DW

4. More Background • Many data sources, many projects • Each project with its own reporting solution • Many reporting /analysis tools: • Discoverer • Native queries • Actuate • Excel/Access • Hyperion/Essbase • Inconsistent information • Lack of standard definitions and reporting processes • Lack of BI maturity • Reporting and spreadsheets

5. Challenges for BI/DW • Immediate need for GL/AP • Near Real Time Reporting (NRT) to keep operational reporting to a minimum • Transaction volume – ½ million money transfers => 2 ½ million trx/day (AR/Settlement) • Short time to implement • Minimally invasive for Oracle apps • Flexible architecture to expand beyond Oracle applications • Minimize introducing new technology • Informatica, Cognos • Proven/Mature BI solution for Oracle Apps

6. Decisions Made • Jaros – packaged data warehouse solution for Oracle Applications • Uses Informatica • Pre-built Operational Data Store for EBS • Pre-built Data Marts for EBS • Cognos – BI toolsuite

7. The Big Picture

8. Implementation Plan Development Timeline General Ledger and Accounts Payable Gather General Ledger and Accounts Payable Requirements Prototype General Ledger and Accounts Payable Reporting Requirements Finalize General Ledger and Accounts Payable Reports and Queries General Ledger and Accounts Payable Report and Query Training Sept ’07 – Dec ’07 (3 ½ months)

9. Implementation Plan Development Timeline Accounts Receivable and Custom Settlement Transactions Gather Accounts Receivable And Custom Financial Settlement Transaction Reporting Requirements Prototype Accounts Receivable And Custom Financial Settlement Transaction ODS / Data Mart And Reports Finalize Custom Financial Settlement Transaction ODS / Data Mart Accounts Receivable And Custom Financial Settlement Transaction Report and Query Training Sept ’07 – Ongoing

10. Jaros Architecture: ODS Functional Groups • Extraction • Light Transformation • Loading AP – 1 hour Reference/Lookup Tables Country Codes Order Types Lookups Customer Item Order Headers Order Lines OM – 2 Hrs Oracle Applications Operating Unit Sales Rep Rest Nightly Detail Tables Master Tables Operational Data Store • Operational Data • Dimensionalized • Near Real Time

11. Jaros Architecture: Data Mart Contains Low Level Detail (user friendly, structured data) Strategic Analysis Contains Fact tables and Dimension tables. Many ODS detail tables make one fact table. Dimension tables are sourced from Master tables in ODS. Reference tables are used in this schema for lookups such as terms and country codes. Fact Exclusively Star Schema

12. Data Mart – Conformed Dimensions Customer Date Orders Detail Fact Orders Detail Fact Orders Detail Fact Order Details Sales Rep Product Operating Unit Set of Books

13. AP Example ODS Data Marts • AP Details • Payments • Invoices • Payment Schedules • Distributions • AP Sub-Ledger • Checks • AP Payment Analysis • Payment Days (Snapshots) • Average Purchases-per-day (future) • Past – Present – Projected (future) • Trends • AP Invoice Analysis • Invoice Price Variance (IPV) (future) • Vendor Balance

14. Where we were? • Oracle Standard Reporting • Difficult to format data • Difficult to retrieve data with our specifications for reporting • Difficult to perform analysis on data

15. Requirements for Business Intelligence/Data Warehouse • Accurate and Reliable Data from Oracle • Retrieve data per Reporting Request • Required fields needed on one report • Easily Format data in Excel, PDF • Professional style of report • Ad hoc query ability • Near Real Time

16. Cognos/Data Warehouse • Oracle information sent to data warehouse (restructured and reindexed for reporting) • Option of Near Real Time Data with ODS • Data marts are nightly • Ease of capture all required fields • Ease of creating Excel or PDF formats

17. Cognos Query Studio • Training is needed for end user • Fields need to be under respective directory (Cognos namespace) for build • Easy to build a query on particular fields • Sort, Format, Group, UnGroup Queries

18. Cognos Report Studio • Training needed to build reports • Standard Report can be created • Fewer, more flexible reports • Ease of running reports • Ease of converting to Excel

19. A Sample of Benefits • Cognos reports allows analysis of AP information giving management ability to see opportunity in analyzing contractual obligations • Identified shipping costs going to South American Corridor • Ease of On Demand reports for management and auditors. • Easily update date ranges • Easily update Supplier Names • Savings of time and increase efficiencies to the business

20. Conclusion • Moneygram goal is ease of business reporting • Gives management opportunity to quickly review information for decision making purposes • Continue moving Oracle GL/AP and AR to Cognos reporting and querying FUTURE • Exploiting BI capabilities of Cognos • Dashboards • KPI’s • Event Manager/Alerts • Blackberry capabilities