Closed patrickm02L closed 2 years ago
Patrick and I met today and created a template for what these dashboards could look like.
Starting ideas for report tabs:
Meeting with Charlie on 7/19/22 to go over functionality and approach to building out the dashboard. Will bring to the afternoon Dev Sync.
In between this note and then, Patrick still needs to make design refinements if there are any for Charlie to update in PowerBI templates that were created.
Data sources for some ideas for each tab:
Chatted with Xavier about trying to calculate the VZ stats on the high injury network and top contributing behaviors. He supports adding some flags in the Socrata dataset, but he's concerned that there are some inconsistencies between what Socrata shows and what the VZ DB is showing.
He also shared his SQL that he is using to calculate the SD 23 measures. He's tracking them on Power BI using some files stored on his PC and updates them manually. High injury power BI
Here is the chart I can add now using Socrata data to our VZ tab from here
@maccallump Please create a list of data from the divisions that you want.
Here's what we have so far...
Meeting set for Charlie and Patrick to review datasets and nail down metrics on 8/1.
Build out the following pages:
Fatalities and Serious Injuries
Include Time filters for all Dashboard pages: Drop down to change from weekly, monthly, last-five years.
Vehicles, Travel Time Volumes, Cap Metro Ridership, Trail Counter
Parking Revenue
Work orders, Asset Inventory
Project Delivery
Types of Issues, Volume of Issues, Location, SR Stat
Permits, Time, Traffic Control Plans
(In Amanda, eventually available, but not easy at the moment)
Things to ask @maccallump in Dashboard Review meeting:
How to approach datasets?
Do we want to only use the data in Socrata or should define what we want to show and find the datasets to make that visible?
What do the executives want to see?
How do we handle transparency?
Set up meeting with Signs and Marking (Susanne G. & Christina T.) to go over what data their capturing in their Power BI dashboard, and what data would help tell a story in the Executive Dashboard.
Kate is going to take the lead with the storytelling for the different division pages that will be included in the dashboard.
@katelunceford is working on prototyping Signs and Marking Dashboard in #10039
Basics for monthly dashboard via @maccallump
Put together a dashboard with Financial information through August, and signs and marking dashboard. A 2 page dashboard is alright for now.
@Charlie-Henry look at ATD Financials spreadsheet EXP 5125 tab for the raw data, represent visually. Reach out to Crystal T.
Update: New pages have been added in the Executive Dashboard prototype.
Better to represent the month-in-closed data rather than updating the data semi-daily.
@Charlie-Henry is still working with data Crystal T. provided to get this automated. There are challenges in microstrategy - specifically removing prompts from reports. @maccallump said that you can remove it from the script from the prompt - this happens when reports are being built.
Perhaps we can work with someone at the Budget office to see if there's a way to pull the data straight from the data warehouse.
Things discussed in 09/13/22 Sync:
@Charlie-Henry
I had some troubles getting some things to work like the border or shading the text to match the arrow, but here's another stab at the revenue page. Currently, I just have the FDUs selectable but we can make a lookup table to convert those to something more friendly.
@maccallump The ATD Revenue and Finance Pages on the Executive Dashboard are good to show at the next Executive meeting.
Closing with the intention of adding more Pages to the dashboard which we'll add to the Epic #7700.
Based on the research from #9504 it makes sense to build out an MVP of to see how an Executive Dashboard might operate.
Using data from the following dashboards:
We're looking to create a single dashboard that's an amalgamation of other dashboards so that other teams can continue to use what they've created while we reference their data.
Also need to follow up with points of contacts who maintain the dashboard data. Suzanne G. in Signs, Allison R. & Lance B., Xavier A., and someone from CapMetro.
Prototype miroboard