Skip to main content

System Status: 

Report Developers and Consumers

Learn about the analytics report developers and report consumer roles at UC San Diego.

We work with two broad categories of users, each having different needs and levels of technical expertise.

  • Report Developers sit with the busines unit and spend much of their time working with data and using the analytics tools. Developers have extensive knowledge of a report's data source(s) and a working knowledge of data tables and joins. 
  • Report Consumers run reports and analyze data, but they do not frequently use analytics tools.

activity hubs user type diagram

Are You a Report Developer or Consumer?

Requirements Developer Consumer
Output Preference
PDF file Yes Yes
Excel file Yes Yes
Interactive web display Yes Yes
Prompted selections - user selects what
content they would like to see in the report
Yes Yes
Level of Data Source Knowledge
None to limited knowledge Yes
Limited to average knowledge Yes Yes
Extensive knowledge Yes
Data source table joins Yes
Report Types
Run Monthly + Yes
Run Weekly Yes Yes
Run Daily Yes
Build a new report Yes
Modify an existing report Yes

BIA Issue Resolution

BIA has a robust QA process for identifying data quality issues or bugs prior to enhancements going live to production. If you feel there is a data quality issue in building your report, BIA can help.

After checking your report, the next step back in the data flow is with the Business Intelligence & Analytics (BIA) team. The BIA team will check the Cognos/Tableau models, the Activity Hub views, the Hana data load and more to determine if a data quality issue is occurring. If everything matches the data source and the data source itself is incorrect then BIA will escalate the issue to the data source team. The data source team may fix the issue or they may indicate an alternate option to meet the user’s reporting needs. 

Ticket process flow:

In summary, after checking your own report, email all identified issues to with (1) the location of your report, (2) screen shots of your report output and (3) screen shots or links to the source data showing the correct data.

 Data Quality Issues