Reporting - Discussion 25/10/2017

Page content:

Background
TIS Proposed Solutions
High level architecture overview of Data warehouse
Follow ups
Agreed next steps

Background

SSRS – Microsoft SQL – Stored procedures to be written.

Intrepid data flows into the Data warehouse. In parallel, anonymization process of the data takes place. Anonymized data used for planning purposes reporting and does not have personal identifiable data.

ETL – This is the current method of extraction in the DR.

Before TIS – micro-services architecture, pull data to the DW on the same day ideally.

TIS Proposed Solutions

4 sets of tools that can be used:

Suite of standard reports (Work with James freed and the regional workforce). End users could tweak the reports with parameters.
Tableau – dashboard visualisation tool, GUI driven
Potential – connect excel to the data mart and use excel to write queries.
Dynamics flow available within office 365.

Analysts will be responsible for creating those reports.

John Thompson and Kais (London Analysts)

Everyone will be reporting on the same set of data.

Custom reports can be requested via a ticket by admins.

Reassurance reports – BM and SMLs to work out the requirements and needs.

Downside:

TIS Admins cannot create their reports.

High level architecture overview of Data warehouse

Follow ups:(Joanne Watson (Unlicensed))

Ability to bulk import/upload follow up with (Ray/Reuben). Bulk import of people in this sprint or next.
Ability to extract as part of workflows on TIS, E.g. placements extraction

Agreed next steps

BA/SM –

Work with LO on what they currently do and why they do it?
What data extraction do they use as part of their current processes and are these necessary with TIS?
Data quality – manage the change/culture with BM’s – The business they are managing are contained within that data.
Post MVP – work with BM’s
Speak with Angela with regards to London dashboards
Engaging their local workforce people.
Skype call with BM’s (Ray & Others) on 03 Nov 2017