GLOCO Enterprise Measurement System Team 4 John Armstrong Ananthkumar Balasubramanian Emily James Lucas Suh May 5, 2012

Business Problem Managers are unable to make timely, well-informed decisions from current data analysis reporting GLOCO’s Data is: Siloed by department, region, and enterprise system Reporting is: Aggregated manually from canned reports Infrequent, inaccurate, shallow Opportunity cost estimated at $250,000 2

Business Process As-Is 3

Proposed Solution BIT4 proposes the GLOCO Enterprise Measurement System (GEMS) GEMS will allow for better, faster decisions Automated, daily, dashboard reporting via the web. Better analysis for: Business Segment Profit Mix Sales Forecasting On-Time In-Full Delivery Levels 4

Business Process To-Be 5

Approach to Technology Reporting Database with OLAP cubes Online Analytical Processing for faster querying performance Multidimensional Data Views Business Intelligence Server Performs calculations Turns data into reports Application Server: Deployment container for reporting tools 6

Flow of Data in GEMS 7 OLAPBI Server Web-based Reporting Tools Data Sources GLOCO Management

Architecture of GEMS 8

GEMS Architecture 9

GEMS Architecture – Overview 10

GEMS Report Request Timeline 11

GEMS: Costs and Return On Investment 12

Vendor Costs 13 Oracle BI EE License$276,050 BIT4 Consulting$152,600 Oracle Support$60,695/year Total $489,345

GEMS Return On Investment 14

Success Metrics 15 BenefitGoal Automated ReportingReduces required hours to produce reports by 60% Report IntegrityIssue/Error Resolution to be reduced by over 90% Report FrequencyDaily dashboard viewing exceeds 95% of GEMS users Decision Making UseGreater than 80% of GLOCO executive management accessing dashboard reports on a daily basis

Assumptions, Dependencies, and Constraints: Highlights GLOCO’s current Oracle 11g database license covers the 11g database required for the GEMS solution GEMS will have read access to GLOCO Data Warehouse GLOCO owns the data and is responsible for its integrity GLOCO’s Help Desk will handle support issues once GEMS is operational 16

Operational Governance 17 PMO Office Project Manager Project Teams Project Sponsor Steering Committee PMO Office Project Manager Project Teams Solution Architect BIT4 Imp Consults GEMS Admin GEMS DBA Sr. Analyst Jr. Analyst

User Adoption 18 Labor Saving Great Product More and better than Excel Training Communicate success Success Access to canned reports removed Final Cutover

Implementation Plan for GEMS 19

Implementation Timeline: 4.5 months 20

Project Deliverables Requirements Use Cases and Functional Requirements Technical Specification GEMS architectural diagram, Dashboard user interface specifications, Design documents Development GEMS hardware and software including the Oracle BI EE, OLAP database, and dashboard user interfaces 21

Project Deliverables Testing System test plan and report, and the UAT test plan and report Deployment Training schedule and materials, and training of personnel System Maintenance Transitional support and Help Desk documentation 22

Dashboards for Better, Faster Decisions 23

OLAP Cube Structure Business Segment Data in a Single Cube Created from Tables: Product, Customers, Date, and Business Segment Category Star schema relational model 24

Data Tables Model: 25 OLAP data populates GLOCO’s KPIs in the Dashboard

Excel Dashboard: 26 The Dashboard helps GLOCO measure KPIs using an automated, daily process Business Segment Mix – Pie Chart (Use Case) Allows for Drill Down and Drill Through functionality

Oracle BI Interactive Dashboard: 27 Personalized views of corporate and external information Organized in pages Results from analysis that is the output returned from the Oracle BI Server

Conclusion: Making better, faster decisions with GEMS 28

Questions 29