1. May, 2010 Reporting Approach

2. Agenda  Background  Proposed Dashboards  Reporting Sub-Teams  Approach 2

3. Background  Reporting Inventory Developed in 2009  Business Process Analysis – Reporting Requirements  List of ISW (legacy report storage application) Reports  Analyzed with Business Process Owners  List cut from over 500 to around 300 3

4. Proposed Dashboards 4

5. Proposed Dashboards-Cont’d  “Going-In Position”  Subject to change based on additional requirements gathering  General vs. Central Dashboards  Security would likely not restrict groups from any dashboards 5

6. Reporting Sub-Teams 6

7. Approach 1)Proposed menu developed 2)Dashboards assigned to teams 3)Reports assigned to dashboards 4)Teams will review reports assigned to their dashboards for disposition 5)Design/Requirements sessions will be held with “owners” of dashboards 6)Teams will develop Dashboard Design Specifications; owners will be asked to sign-off 7)Dashboards will be broken down to work units and assigned by team leads 8)Teams (to include owners or appointees) will build dashboards and owners will sign-off 7

8. Approach-Cont’d 9)Reporting team leads will be responsible to work with module leads to ensure dashboards are included in scenarios/scripts for testing in Integration Test 2 10) Dashboard user guide/help text will be completed for each dashboard 11)Team Leads responsible to ensure the Reporting Inventory is updated to reflect new report locations to provide old to new mapping 8

9. 9 Questions? Mosaic.arizona.edu