Jaros Overview - History

2. Jaros Overview - History • Founded 1999 as consulting company • GE Medical Systems IT • Sigma Aldrich • Smurfit-Stone Container • Transitioned to Software Company in 2001 • focus on Oracle E-Business Suite • Jaros Analytics General Availability in early 2004 • Signed 1st Customer in 2004 • Venture Funding • Reputation and Growth : 2004 through present

3. Jaros Design Goals • Integration of many data sources • Operational ease of use • Easy to restart • Easy to administer • Synchronized Data Loading • Flexible scheduling • Performance • ODS : Get data in as fast as possible • Data Marts : Query Performance and Ease of Use • Incremental loading • Front-end agnostic (Any Reporting Tool) – Pre-Built Reporting • Near Real Time access to data • Operational Reporting and Dashboards (ODS) • Strategic Reporting and Dashboards (Data Marts) • Meta Data Driven Fully Defined Solution • Help system • Generation of reporting meta data layers • Extensible to customers expectations • Report Integration

4. Oracle E-Business Suite Support • General Ledger • Accounts Payable • Accounts Receivable • Order Management • Shipments • Inventory • Purchasing • Working Capital • Project Accounting • Projects • Commissions • Advanced Pricing • Human Resources • Payroll • Benefits • Services and Contracts • Discrete and Flow Manufacturing • BOM, Routings, WIP, Costing • WMS • Process Manufacturing • Quality • iProcurement • Fixed Assets

5. Jaros Architecture P o w e r C e n t e r Operational Data Store Integrated Data Marts Near Real Time Strategic Jaros Active Meta Data Repository ? Reporting Layer HR Payroll Benefits Order Mgmt Discrete MFG Process MFG Financials Inventory Purchasing Service Simple per Module Pricing

6. Data Model: Integration Data Integration Jaros Data Model Oracle Applications MFG Pro Supported Platforms Legacy Systems Integration Interface Table Non-Supported ERP Non-Supported Platforms

7. Reporting / Dashboards / KPI’s / Strategy FSG’s Transactions General Ledger Sub-Ledgers Drill Path Reporting / Dashboards KPI Data Model FSG Data Model General Ledger / Sub Ledger Data Model Transactional Data Model

8. Jaros Architecture : 5 Major Components • 1. ETL - Informatica PowerCenter • 2. Operational Framework • 3. Data Model • Operational Data Store • Data Marts • 4. Active Meta Data Repository • 5. Reporting Layers • Business Objects • Cognos • Oracle • Pre-Built reports

9. ETL – Informatica PowerCenter Support Informatica 7 and 8

10. ETL – Informatica PowerCenter • Extremely Scalable • Operational Friendly • Powerful Workflow Execution Engine • Graphical Programming • Robust for Operational and Strategic BI • Consistently Rated as Leader in • ETL • Data Quality • Data Integration

11. Data Model: Operational Data Store Operational Data Store Reference Tables Master Tables Detail Tables Reference tables are lookup tables such as country codes, terms codes, etc Master Tables represent customers, products, sales reps, etc. Detail Tables represent order lines, invoice lines, journal entries, AP invoices, etc. Operational Reporting Near Real Time Dimension Dimension Transaction Tables Transaction Tables Dimension Dimension Hybrid Star Schema

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

13. Data Model: Data Marts Contains Low Level Detail (user friendly, structured data) Strategic Analysis Contains Fact tables and Dimension tables. Conformed Type I & II Dimensions. 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. Exclusively Star Schema ROLAP or MOLAP Dimension Table Dimension Table Fact Table Dimension Table Dimension Table 60+ Dimensions 150+ Fact Tables

14. Prebuilt Analytics Reporting Categories (Over 180 Reporting Areas): GL and Sub-ledger Analysis Bookings, Billings, Backlog Customer Profitability Product Margins COA Margins AR Aging Credit Risk Analysis Customer On Time Performance Vendor Ratings Vendor Reject Analysis List Price Analysis AP Cost Analysis Vendor On Time Performance IPV Analysis PPV Analysis Obsolete Inventory Inventory Turns Inventory Value WIP Analysis Item Cost Analysis Sales Analysis Working Capital Fixed Asset Reporting PA – Projects, Tasks, Events, Budgets, Agreements, Expenditures, Fundings PA – AR / AP / PO Drill PA – Revenue Analysis PA – Cost Analysis Quality Reporting Financial Reporting Process Manufacturing Reporting Open AP Aging Discrete Manufacturing Reporting

15. Jaros Architecture : Reporting Layer Consistent Framework for Reporting 150+ Starter Reports today Reporting Tool Cognos, Business Objects Reporting Meta Data Layer Synchronized Jaros Active Meta Data Repository Synchronized Jaros Help System

16. Partnerships • Teradata • Oracle • Microsoft • Cognos • Microstrategy • Informatica

17. On the Horizon TCS Relationship Teradata Support - Platform Independence iGate Relationship Hosting Service Oracle E-Business Suite Jaros Analytics Complete Transactional and Reporting Solution

18. Why Jaros? Value to Customer – GE Case Study - Navilyst Medica Case Study Multiple Platform Support Cognos, Business Objects Oracle, Teradata, MS SQL Server Real Time Information Industry Specific Data Models

19. Thank you