Terminology - 'Thin' report to describe a report that is authored using an existing shared data model
We are wondering if we can get you guys to leverage the use of the term “Thin Report” to describe reports that are written by someone (report writer) that is leveraging a common data model to produce the report.
We consider an Ad-hoc report, or a custom report as follows:
Any report created by a PBI user, sourcing data within PBI outside of a common data model, with the intent to create a report to satisfy a specific need for themselves or a small group of people. These reports can be created and used one time or can reside in a business units workspace.
When people read Ad-hoc or custom within MS PBI documentation, there becomes some confusion.
The reason this is important to us is that our PBI structure is to provide IT developed common data models, certify them and share them with the business units that have reporting needs. This allows reuse of the common data models to satisfy multiple business units reporting requirements using “thin” reports, while providing data consistency and supportability of our platform.
Use Case 1 – ARC’s preferred PBI usage/structure and how we communicate to the report writers about “thin” report creation and usage:
1. ARC IT developed and supports a common data model that massages, models and calculates blood inventory related data from 6 data sources
2. The blood inventory common data model is “certified” and build permission have been provided to several business unit report writers
3. Report writers have produced many “thin” reports from the certified blood inventory common data model and published and shared them with their consumers
Use Case 2 – Not ARC’s preferable PBI usage/structure and how we communicate to the report writers about not creating ‘fat’ reports:
1. ARC business units source data directly from the 6 blood inventory systems and create an Ad-Hoc “fat” report that holds like data as is in the IT supported blood inventory common data model
2. ARC business units share reports and dashboards whose data source was not IT developed, causing refresh data duplication, inefficient use of capacity, potential inconsistent or inaccurate data