Dashboard - Faculty V.1.0

Quick View

Summary:

Provosts and Deans face countless decisions relating to the University’s faculty staff. Unfortunately the data and information needed to make informed decisions isn’t always readily available as the University’s data is not centrally located or easily retrieved.

The FACULTY DASHBOARD is a tool that brings together data from multiple sources, displays the timeliest and most pertinent information for faculty members, provides ad hoc reports for the recurring analysis of faculty members’ contributions to the University’s colleges and departments, and ultimately provides actionable options to the user so they can implement the decisions they make.

Latest Update:

The dashboard was released to selected individuals in the Provosts' office on Monday June 8th, 2009

Start Date:

September 25, 2008

Go Live:

June 5, 2009

End Date:

June 18, 2009

Current Milestone:

06/05 go live.

Stage:

Recently Released - Completed in last 3 months.

People

Sponsor/Champion:

Elizabeth D. Capaldi, Executive Vice President and University Provost

Lead Customer:

John Hepburn

Project Manager:

Matt Sheppard

Contact for more information:

matthew.sheppard@asu.edu

Associate VP University Technology:

John Rome

More Info

Source:

Executive

Priority:

High

Scope:

Click to view the Faculty Dashboard - Project Overview

Click here to view the case in PeopleSoft: CRM Case #318569

All Milestones and Schedule:

12/05/08	Tenure KPI working(complete)
03/13/09	The Employee Profile Table will capture the revised and cleaned up rank codes on this payroll date.
03/27/08	Final round of development
04/03/09	Complete Review / Testing in preparation for presentation to Provosts and Deans
04/21/09	Present dashboard to Provosts
05/15/09	Final Touches and Go Live

Deliverables:

1. Faculty Profile:

This page is the one-stop-shop for the most comprehensive display of individual faculty member’s information. In addition to the usual HR data that’s expected to be displayed, this page shows the salary history, pay from non-primary jobs, supplemental pay, and the accounts they are paid from. It conveys their promotion history, tenure information, where they received the education, and their contributions to the University’s graduate programs and research initiatives. Historical instructor load statistics are displayed along with their current semester’s teaching schedule and participation in the Academic Status Report (ASR) program.

2. Reports:

The dashboard makes available a repository of dynamic reports that can be tailored to answer questions related to Adjunct Faculty, Headcount Analysis (distributions of faculty by gender, ethnicity, citizenship, and rank), and Salary Analysis ( distributions by years in rank and as a measure of total SCH and Research Expenditures). Reports based on instruction and research are also available. The dashboard makes the most of the comparisons regarding teaching (courses, number of students, SCH, etc) in terms of three groups: Tenure and Tenure Track, Contract Faculty and Faculty Associates. Similarly, with regard to research it compares research grants/funding in terms of Assistant Professors, Associate Professors, Professors and Research Faculty.

3. Other Pages:

The dashboard offers pages that visually display Tenure and Rank counts by college and department. It also includes an Alma Mater page. In one glance this Alma Mater page impresses upon the user the quality of our Institution by showcasing the quality institutions from which our faculty received their highest degrees. Finally, there are pages for Census Data and PAC 10 comparisons as well.

Risk & Threats:

Data quality. A byproduct of showing all the data in summarized views is that bad data is easily spotted and it is glaringly obvious which departments aren't entering it correctly. Perhaps this will create a since of urgnecy for it to get cleaned up. However, we put ourselves at risk if we go live with a dashboard that doesn't bring back accurate data. If the dashboard is branded as such (one that doesn't bring back good data) the liklihood of it ever being adopted is slim. Thus we need to rely on Deans and BOMs to put a stamp of approval on the data we're bringing back in a testing phase. This could ultimately delay the release of the dashboard, but the work on the dashboard will be complete. The bottleneck at that point will be another project to clean up the data.