Reporting Status

1. Reporting Status Designing a scalable reporting solution for Amherst November 2009

2. Introduction The Colleague Advancement migration allows us the opportunity to imagine reporting in a new way. In response, we understand that the centralization, accuracy and usability of our reporting solution will be the cornerstone of the College’s understanding of the past and the basis on which we plan for the future.

3. Purpose To share our status and the vision of the direction, scope and process by which we are framing the Advancement Reporting Solution.

4. Agenda • Reporting Conversion Vision • Partnering with our Users • Reporting Priorities • Definition of Success • Current Status • Next Steps

5. Reporting Conversion Vision We are striving to conform to a reporting standard that holds centralization, accuracy and usability as its central tenants. Realizing this vision hinges on partnering with our users. Through this partnership we will build a team to define reports deliverables, establish priorities, and test/validate report output.

6. Centralization • Single data source for all data elements • Encourages sharing of reporting Best Practices • Consistent Report Look and Feel • Common Naming Conventions • Minimizes Report Duplication

7. Accuracy • Established through a controlled set of Business Rules • Provided by establishing a single validated source of critical Advancement data elements • Campaign Total • Annual Fund Total • Alumni Fund Total • Etc. • Ensures that all reports represent the data in a consistent manner

8. Usability • Web Interface – Accessible on and off campus • Minimizes specialized tool sets or knowledgebase • Common user interface minimizes support cost • Common Naming Conventions ensures users are discussing the same element

9. Partnering with our Users • Working directly with users, will help: • Ease their transition • Open dialog with them builds confidence • Greater understanding of common reporting needs • Shared ownership of report requirements

10. Why Reporting Priorities • Determine the minimal number of reports needed to support the community • Identify which users, need to: • be involved in conversations to combine data elements from many reports • to validate and test reports • to schedule user involvement in a way complimentary to their schedules and our Datatel training • Establish an order to report development • Determine the timely delivery of reporting data elements • Minimize the number of unidentified reporting needs • Establish joint ownership • Negotiate the subset of reports that need to be ready day 1

11. Reporting Priority Rules • How priority will be established: • Who and how many users • What is a report attempting to communicate • Where in our Datatel Training schedule • When is the report needed: Daily, Weekly, Monthly, Quarterly, Annually • Why is this a unique requirement or an augmentation to an existing report • How to implement: BusinessObjects, Access, CMS

12. Definition of Success

13. Current Status • Requirements Gathering • ADVIS Report Catalog – in progress • Compiling User Email Feedback – in progress • ‘Thumbs up’ meeting • Datatel Trainings • ODS data definitions started

14. Short Term Steps • Monthly Status Meetings • Continue, Report Aggregation of User Email Feedback • Meet with users to clarify, as needed • Incorporate additional requirements, as needed • Establish and Communicate Report Priorities • Communicate Project Goals, Status, Needs at each All Advancement Staff Meeting

15. Long Term Milestones • Include additional ADVIS team members in report development and testing • End User Involvement • Reports Requirement Validation • Testing • Set and Manage User Expectations, gain versus loss • End User Training, developed by ADVIS • Delivery of a scalable reporting solution