1. IRIS Business Warehouse Legacy Business Warehouse (LBW) Blueprint Specification May, 2000

2. LBW Blueprint Specification Project Objectives Project Objectives  Preserve legacy master and detail data not planned for conversion into the IRIS R/3 system;  Provide continuing computer access to legacy data for query, reporting and decision support.

3. LBW Blueprint Specification Planned Go Live April 2, 2001 Planned Go Live April 2, 2001 Legacy Data “Frozen” as of March 31, 2001 Legacy Data “Frozen” as of March 31, 2001 Prototype Implementation Planned for December 1,2000 Prototype Implementation Planned for December 1,2000

4. LBW Blueprint Specification In Scope Deliverables In Scope Deliverables  Extraction and Load of UT Legacy System’s Relevant Detail and Master Data  Design and Development of LBW “InfoCubes”  Identification and Training of Strategic Query End Users

5. LBW Blueprint Specification In Scope Deliverables (continued) In Scope Deliverables (continued)  Identification and Training of Reporting End Users  Deployment of BW Explorer  Development of Limited Report Templates and Examples  Establishment of BW Technical Environment

6. LBW Blueprint Specification In Scope Deliverable (continued) In Scope Deliverable (continued)  Investigation of Alternate Query, Reporting and Decision Support Tools

7. LBW Blueprint Specification Out of Scope Actions and Deliverables Out of Scope Actions and Deliverables  Reverse Conversion of IRIS R/3 Data for April, May and June of FY 2001  Any Capability for Retroactive Adjust of Payroll or Financial Data  Development of BW Queries and Reports Beyond Templates and Examples

8. LBW Blueprint Specification Out of Scope Actions and Deliverables (continued) Out of Scope Actions and Deliverables (continued)  Implementation and Deployment of Any Query or Reporting Tool Other Than BW Explorer  Inclusion of Legacy Data Sources Not Identified in Blueprint

9. LBW Blueprint Specification Ten (10) mainframe data sources identified as important for preservation and continued access via computer. Ten (10) mainframe data sources identified as important for preservation and continued access via computer. Financial Data Sources Financial Data Sources  DFNLEDGR database – UT’s Official Account Attribute and Accounting Balances Database

10. LBW Blueprint Specification Financial Data Sources (continued) Financial Data Sources (continued)  DFNYACTV database – the detailed accounting transaction data base supporting balances  DFNGRANT database – Grant and Contract Attribute Data

11. LBW Blueprint Specification Financial Data Sources (continued) Financial Data Sources (continued)  DFNPORDR database – UT’s Financial Purchase Order Database  FLVENDOR database – UT’s Vendor Database  DNFPAYEE database – UT’s Payee Database

12. LBW Blueprint Specification Financial Data Sources (continued) Financial Data Sources (continued)  GHHISTRY database – UT’s Purchase Order MicroFiche Reference Database

13. LBW Blueprint Specification Payroll and Human Resources Data Sources Payroll and Human Resources Data Sources  DHREMPLY database – UT’s Primary Payroll and Human Resources Attribute and Balance Database  Payroll History File – UT’s “Check Stub” History File  Salary Budget File – UT’s Salary Budget and FY Start

14. LBW Blueprint Specification LBW Security LBW Security  Will Parallel IRIS Security  Two Types of User Profiles  Strategic Query Users – Unlimited Access  Reporting Users – Unlimited Financial Balances Access

15. LBW Blueprint Specification BW Explorer – Query, Reporting and DSS Tool BW Explorer – Query, Reporting and DSS Tool  Easy to Use Excel Like Format  Visual Basic Link for Additional Processing Power  64,000 Row Query Limit

16. LBW Blueprint Specification Open Issues Open Issues  Strategy for Campus Access to Referential Files for Chart of Accounts and Employee Status Validation  Disposition of Data Not Converted into IRIS R/3 and Not Preserved in LBW

17. LBW Blueprint Specification Questions?