The Research IT Reporting & Analytics area focuses on creating reporting and analytics for research operational data across OVPR. Quality assurance of administrative research enterprise data is another key area to ensure accurate reporting and representation.
- Data modeling/curation
- Dashboard development
- Operational & ad hoc reporting
- Data analytics development
- Quality assurance
Current Report Backlog Status
Currently, the team is focused on moving the legacy reporting infrastructure into the new PowerBI Architecture. This backlog consists of a number of reports. The below table and subsequent chart shows how these legacy reports and current requests are aligned with the reporting priorities.
| Priority | Total | Total in Progress |
|---|---|---|
| Urgent | 1 | 1 |
| High | 33 | 9 |
| Medium | 40 | 13 |
| Low | 2 | 1 |
| Total | 76 | 24 |
Reporting Priorities
The time required to complete a request can be dependent on the complexity of the reporting or analytics needed. However, the team does strive to return prompt service to priority requests in the following manner.
*The turnaround time listed in the infographic is in business days and is the time it will take for the response to the ticket being submitted and NOT the time it will take for the report or dashboard to be created.
1 – Urgent
A request for an urgent report change or creation will be responded to by a reporting engineer for more detailed information within 1 business day. The estimated time to deliver the needed report will be determined after the initial scoping meeting with the report engineer and documented in the Fresh Service ticket.
2 – High
A request for a high report change or creation will be responded to by a reporting engineer for more detailed information within 3 business day. The estimated time to deliver the needed report will be determined after the initial scoping meeting with the report engineer and documented in the Fresh Service ticket.
3 – Medium
A request for a medium report change or creation will be responded to by a reporting engineer for more detailed information within business 5 days. The estimated time to deliver the needed report will be determined after the initial scoping meeting with the report engineer and documented in the Fresh Service ticket.
4 – Low
A request for a low report change or creation will be responded to by a reporting engineer for more detailed information within 10 business days. The estimated time to deliver the needed report will be determined after the initial scoping meetng with the report engineer and documented in the Fresh Service ticket.