Dashboard - Sponsored Research V.1.2


Dashboard_v1_1.jpg
Quick View
Summary: 

The Research Dashboard helps users to make business decisions using research information.

Start Date: 
October 17, 2008
Go Live: 
January 21, 2009
End Date: 
January 21, 2009
Current Milestone: 
1/20/09 :: Development is complete, and project is fully deployed into production.
Stage: 
Recently Released - Completed in last 3 months.
People
Sponsor/Champion: 
R.F. Rick Shangraw, Vice President of Research and Economic Affairs
Project Manager: 
Rick Bolin, EDS Business Intelligence Analyst
Contact for more information: 
Rick.Bolin@asu.edu
Associate VP University Technology: 
John Rome
University Technology Director: 
Tina Thorstenson
More Info
Source: 
Executive
Priority: 
Medium
Scope: 

There are four tasks within the scope of the v1.2 update of the Research Dashboard; three of these items are behind-the-scenes data storage and aggregation matters. The one change that will be visible to the users, and which involves a change in the Dashboard itself, is a minor change to the display of detail rows on the Monthly Detail page, to make clear that some values are for total activity and some are for activity of those departments and individuals as recognized by participation.

Project Tasks and Requests (as received Thursday, Oct. 16, 2008, and approved Nov. 22, 2008):

1. Implement Change to Activity Details Exhibit on the Monthly Detail Page: December 31, 2009

Currently, the Activity Details Exhibit on the Monthly Details Page of the Research Dashboard includes fields for the Number of Colleges “Cols”, Departments or Centers “Depts” and Investigators “Invs” involved on a project, as well as a field for the dollar value of the itemized research activities “Value”.
When that the users have not applied any filters, these values are reported for the entire activity as in Figure 1.

Existing Output for Detail Row

When however, users have applied a filter(s), these fields are reported based on recognized values limited by the filters as in Figure 2.

Existing Output for Detail Row, Engineering Filter Applied

Because users often mistake the filtered field values as total activity values, the following design modifications to the Activity Details Exhibit are needed:

  1. Report the total activity values for the “Cols”, “Depts”, “Invs” and “Value” fields regardless of any user selections made in the drop-down list boxes.
  2. Change the “Value” column heading to “Total $”.
  3. Remove the “PI” field
  4. Add a new field “RI” that will report the number of recognized investigators consistent with filtering based on any user selections made in the drop-down list boxes.
  5. Add a new field “Recognized $” that will report the recognized value of the activity consistent with filtering based on any user selections made in the drop-down list boxes.

If these design modification are successfully completed, the Activity Detail Exhibit feature in previously in Figure 1, would be revised to be consistent with Figure 3.

Proposed Output for Detail Row, No Filter Applied

In the case that users have applied a filter(s), the “RI” and “Recognized $” fields would be reported based on recognized values limited by the filters as in Figure 4.

Proposed Output for Detail Row, Engineering Filter Applied

These changes to the Activity Details Exhibit do not require modifications to the activity overview pop-up returned if the user clicks an Item’s hyperlinked “Number”.

2. Add/Modify Data Fields in “RA_ALL” Tables in the Sponsored Data Warehouse: December 12, 2008

1. Add recognition based “Direct Cost”, “Indirect Cost” and “Modified Total Direct Cost” to the “RA_ALL_EXPENDITURE_EOM_RECOG” table in the Sponsored Data Warehouse.

2. Add an “Account #” field to the “RA_ALL_AWARD_EOM_RECOG” and “RA_ALL_EXPENDITURE_EOM_RECOG” tables in the Sponsored Data Warehouse.

3. Add "Award Title", "Activity Type", and "Award Status" to tables.

3. New Processes and Procedures for TRIF Data: (deferred)

Note: This item is now removed from the project, and is part of the version 2.0 request.

OVPREA Accounting Staff has indicated that changes should be made the ETL Queries used to populate the TRIF Data in the “RA_TRIF_EXPENDITURE_EOM” and “RA_TRIF_EXPENDITURE_EOM” tables in the Sponsored Data Warehouse which are ultimately reported on the Research Dashboard. UTO, PRIDE and OVPREA Accounting will need to coordinate and specify the required changes.

Currently, there are considerable inconsistencies in many of the data fields for TRIF data. UTO, PRIDE and OVPREA Accounting will need to coordinate and specify the standards for data formats and potentially alternative data storage, management, entry and update procedures.

4. Develop a Multidimensional Database to Support the Research Dashboard: (deferred)

Note: This item is now removed from the project, and will be a stand-alone project, prioritized separately.

To decrease response times on the Research Dashboard, a multidimensional database should be developed to support the Research Dashboard as well as other OVPREA | PRIDE Research Analytics tools. This multidimensional database must be accessible both by direct query and from data “connections” within MS Excel Workbooks, by users authorized to access the Research Dashboard. User authentication should be based on asurite IDs.

5. Implement Facilities & Administrative Costs Grid, Trends, and Details :: January 20, 2009

Modify database objects to be able to return indirect costs (F&A) in addition to proposals, awards, and expenditures. These should include Total Value, Count, and Investigator Count like the other activity types. Grids, trends, and details shall all be modified to display these items, including appropriate selections and options in the drop-down listboxes (DDLs) for each screen. In addition, the row and columns of "Average Size" shall be removed everywhere (except in the trends charts, where the yellow line should remain). Also, the range of dates (month and year DDLs, generally) shall be modified to allow ten years of data to be charted/viewed. This should be a dynamic process, and the ETL routines might need to be changed to accommodate this as well.

All Milestones and Schedule: 
Item 1 (above) :: Work began December 18, 2008 -- Completed on December 31, 2008
Item 2 :: Work began November 22, 2008 -- Completed on December 17, 2008
Item 3 :: Removed from project (see Scope, above)
Item 4 :: Removed from project (see Scope, above)
Item 5 :: Work began January 6, 2009 -- Completed January 21, 2009, with the migration to production

 
 

Deliverables: 

For Item 1:

The Activity Grid on the third page of the Research Dashboard will display the counts of all colleges, all departments, and all investigators involved in each award (or proposal) in the selected time period, along with the total value of this activity, in addition to two new columns that show counts of investigators and recognized value for the activity as filtered by the user's selections in the drop-down lists at the top of the page. These counts will be accurate and the values will sum to exactly the displayed amounts in the Summary Grid, just above the Activity Grid.

For Item 2:

UTO will make changes to the structure of the tables involved, and will prepare and deploy the processes that will populate these new data columns. All data shall be of the proper granularity so that it can be combined (aggregated) with other items in these tables, where used in the Dashboard.

For Item 5:

Deliverables are described in the Scope section, above..

Risk & Threats: 

If the principals decide to proceed with data system changes (relational database to multidimensional database), the development and conversion will conflict with the deliverables of Item 2 and Item 3 until the data system is stabilized and mature on each level, and reporting components are installed on each tier to support the interface.

Granularity issue: Since the SPONSORED data warehouse was not designed to deliver summary data in conjunction with recognition data for both departments and centers, the requested data has been created for this project. This caused the delays in the deliverable for Item 2, but did not significantly impair the overall project release date.

Syndicate content