September 2007 Movex User Association John Calvey European B.I. Manager NewellRubbermaid -

2 Project Background » Company OverviewNewellRubbermaid » Business Requirement » Identify Issues » Possible Options » Chosen Solution » Current Status and Future Plan

3 The Company ▪ Fortune 500 Company ▪ European Headquarters in Paris ▪ European Data Centre Located in Sunderland ▪ Systems – Movex Installed Since 1999 – Demand Solutions (Forecasting) – PKMS Warehouse Management – Hyperion – Financial Budgeting – TM1 – Financial Budgeting ▪ Cognos Used for BI Reporting – Web based 1200 users – 400+ Powerplay Cubes – 1000 Impromptu Reports

4 Business Requirement » Company Re-Organisation ▪ From Four Business Units – RCP – GRACO – Sanford – Irwin Tools ▪ To a Single Reporting Structure » What Does That Mean? ▪ Each split into a number of Divisions ▪ Reporting – Each with their own store of data & Reporting Requirements – Cognos Cubes and Reports built in the overnight window

5 Current Architecture Sanford DataWarehouse Data Point to Powerplay Cubes RCP & Graco Exchange (External data) iSeries (DB2) Microsoft SQL Server DTS Extracts NOMAX Replication Data Point to Impromptu Reports and Powerplay Cubes (Sanford) Irwin Tools DataWarehouse Data Point to Impromptu Reports and Powerplay Cubes (Irwin Tools) Wintel (SQL) P2 BI Staging P1 Movex ERP System Data Point to Impromptu Transactional Reports Data Point to Impromptu Transactional Reports. Sanford, RCP. Graco & Irwin Sarbanes-Oxley DataWarehouse Data Point to Impromptu Business Level Reports (Sarbanes)

6 Business Requirement - Implications » Issues -1.Data & Process Harmonisation ▪ Use of Master Data, Customer Numbering etc ▪ Product Hierarchies ▪ Customer Hierarchies ▪ Supplier Harmonisation complete ▪ Process Change ▪ External (non Movex) Data to be captured » Solution Internal Resource ▪ Business Knowledge ▪ Movex Knowledge

7 Business Requirement - Implications » Issues -2.Reporting ▪ New Powerplay Cubes  Larger Data Volumes » 500k Customer Records » 450k Item Master Records » OSBSTD 150 Million Records  Larger Cubes / More Variations  Greater Build Times (Same Overnight Window Available) ▪ New Reports  Historical and Real Time Reporting Requirements ▪ External Data (non Movex) ▪ Business Logic – In One Place

8 Proposed Architecture Enterprise Environment Exchange (External data) Data Point to Impromptu Business Level Reports Data Point to Powerplay Cubes Staging Environment Wintel DataWarehouse Environment Movex ERP System Data Point to Impromptu Transactional Reports Data Views (DataMarts) Data Push (Changes ) Staging linked to ERP / Source SystemsEnterprise & Data Marts Independent of ERP / Source System Other Data Sources

9 Proposed Solutions for Architecture » Have to Change ▪ Combining the Extracts, the Overnight Window – Too Small ▪ Cubes Build Time – will increase ▪ Available Time For Data Extract – will decrease ▪ Re-handling Data – Time – Bandwidth » Options ▪ Part Data Extracts / Full Weekly Extracts ▪ Build Cubes Weekly, Incremental Builds ▪ ETL Tool

10 Solution » Vision Software- Integrator ▪ Reasons – Software  iSeries and SQL Server  Identify Changes  Data Transformation Capabilities  Daisy Chain (iSeries >>> SQL Staging >>> SQL Enterprise)  Monitoring – Company  iSeries knowledge  Previous work – Prototype Test  Project Plan  Vision installed software / basic training  Ran for 4 weeks  Contact with Vision support during this time – excellent (and since!) ▪ Additional Benefits Identified – Reduced Development and Maintenance Time – Reduced Errors – Standardisation  Single Data View  Business Process Rules held once – Date and Time Stamp on Records

11 Current Status » Software ▪ Live Version Installed » Replication Status ▪ 25 tables replicating Movex to Staging ▪ 5 tables to Enterprise » Plan – 60 tables – 30 Master Tables – 30 Transaction Tables – Business Logic being applied to Enterprise – “Use of Data” – transaction date / time information