BI Technical Infrastructure Approach May 15, 2013

Increase Data Consistency Expand Access to Data Drivers for Change Increase Data Consistency Expand Access to Data Improve Ways to View Data At a lower, more sustainable cost of ownership

Current BI Environment Multiple data warehousing storage methods that contain inconsistent data. No Support for OLAP No consistency in data definitions and business rules Limited ways to view data All reporting needs have to go through Central IT, resulting in bottlenecks Business logic in multiple places and inconsistent with each other. Business logic not transparent to customers Heavy reporting load on transactional systems

Design Guiding Principles Keep it Simple; Eliminate redundancies and failure points Reduce licensing costs and total cost of ownership Provide BI self-service capabilities Promote transparency

Future BI Environment Business logic is transparent to customers More visualization choices Consistent business logic in one place Single data warehouse that contains consistent data Support for OLAP Self Service BI Mashup Data! Reduced IT bottlenecks Data is persisted in models; reduced load on transactional systems

Standardize on Microsoft BI Platform Reduce Ellucian Dependencies Migration Plan Standardize on Microsoft BI Platform Standardize on Microsoft ETL Tool (SSIS) Standardize on SQL Server Upgrade to MS 2013 Tools Phase out SAP BI Tools Reduce Ellucian Dependencies Provide near-real time data access Phase out Ellucian ODS and EDW Add tools to support data governance Introduce Data Governance tools Introduce data services layer

EXAMPLE - Standardize on Microsoft SQL Server What’s Changing Make Microsoft SQL Server the primary reporting relational database platform in BI environment Phase out Oracle in BI environment Stakeholder Impact It will be possible to query the Relational Data Warehouse from Excel. If you’re a developer, you’ll need to install SQL Server Data Tools. Start reducing dependency on the Oracle Platform for reporting needs Drivers for Change Lower licensing cost per user (SQL Server: $5.39 vs Oracle: $118.59) Microsoft Database is feature complete - No additional licensing for partitioning, compression, OLAP. With Oracle, these components would be extra (e.g. partitioning - $150k one time and $30k recurring) Timeframe Microsoft SQL Server: 3 - 6 months Phase out Oracle – 2 - 3 years

BI Infrastructure – Stakeholder Analysis

BI Infrastructure Projects - Timeline