COGNOS Upgrade to 10.1 Project Financial Area Representatives January 18, 2012

Upgrade Project Scope   Move off of “buggy” v 8.3 to 10.1   Leverage product improvements   Stabilize the reporting system   Simplify monthly maintenance   Improve monthly report package & consolidate with SOA   Free up resources towards PeopleSoft   Move off of “buggy” v 8.3 to 10.1   Leverage product improvements   Stabilize the reporting system   Simplify monthly maintenance   Improve monthly report package & consolidate with SOA   Free up resources towards PeopleSoft

New Features   Monthly reports will be written to folders:   Monthly reports will be written to folders: UNIT LEVEL (FOLDER 1)AREA LEVEL (FOLDER 2) Who receives? Account Administrators & SOA Delegates VP/AVP, Deans & persons who have been receiving monthly reports ScopeAll Unit Codes & FundsCertain Unit Codes, All Funds Reports Included? Statement of Accounts - 1 file with 4 worksheets: Monthly Account Summary SOA Detail Summary by Budget Group Summary by BG & Subacct Reconciliation Worksheet 12 Month Revenues & Expenditures - New

Report Distribution   will provide a hyperlink to network drive folders   Recipient will see all folders he/she has security access to   Folders will contain 2 months only – current month & prior month   will provide a hyperlink to network drive folders   Recipient will see all folders he/she has security access to   Folders will contain 2 months only – current month & prior month

Report Distribution   Account administrators cannot opt out of receiving monthly s - for compliance & subcertification purposes.   Changes to recipients are made through existing forms & business processes:   SOA delegates - DEFINE Departmental User Access Form (Section IV.)   Account Administrators – Unit and Account Request Form   Account administrators cannot opt out of receiving monthly s - for compliance & subcertification purposes.   Changes to recipients are made through existing forms & business processes:   SOA delegates - DEFINE Departmental User Access Form (Section IV.)   Account Administrators – Unit and Account Request Form

Report Changes & Enhancements  Overall – improved formatting  SOA Detail  Data more sortable & manipulative  Transactional level details  SOA Summary by Budget Group  New report to replace monthly detail  Provides balances at a budget group level  Overall – improved formatting  SOA Detail  Data more sortable & manipulative  Transactional level details  SOA Summary by Budget Group  New report to replace monthly detail  Provides balances at a budget group level

Report Changes & Enhancements  SOA Summary by Budget Group & Subaccount  Balances at budget group & subaccount levels  Slight changes with presentation of adjusted budget  SOA Summary by Budget Group & Subaccount  Balances at budget group & subaccount levels  Slight changes with presentation of adjusted budget

Report Changes & Enhancements  SOA Reconciliation Worksheet – will completely change to improve usability  More concise worksheet for certification by administrators  Worksheet will provide balances at budget group level, not subaccount  One page wide  Adds a worksheet with monthly income & expenses of PY & CY  SOA Reconciliation Worksheet – will completely change to improve usability  More concise worksheet for certification by administrators  Worksheet will provide balances at budget group level, not subaccount  One page wide  Adds a worksheet with monthly income & expenses of PY & CY

Report Changes & Enhancements New Report: 12 Month Revenue & Expenditures:   Month to month revenues by budget group by subaccount   Month to month expenditures by budget group by subaccount   Use for projections, planning & to detect unusual patterns New Report: 12 Month Revenue & Expenditures:   Month to month revenues by budget group by subaccount   Month to month expenditures by budget group by subaccount   Use for projections, planning & to detect unusual patterns

System Improvements  Framework Model  Time to Run Reports  Simplicity of Approach  Ease of Maintenance  Folder Structure  Framework Model  Time to Run Reports  Simplicity of Approach  Ease of Maintenance  Folder Structure

Next Steps  Completion of:  Framework data model  Monthly report package  Distribution model including testing & setup of network connections:   Pilot group will receive test to verify folder access   Roll out for February month end reports  Completion of:  Framework data model  Monthly report package  Distribution model including testing & setup of network connections:   Pilot group will receive test to verify folder access   Roll out for February month end reports