Phase 4: Self-Service, Centralized Access Point

[rebekkabry]

Connect these resources to a centralized, self-service platform.

• [ ] Ability to access dashboards and tools, filter by themes, divisions, etc. Users should have the ability to filter type of report or dashboard, service area or division

• [ ] Consider Functionality: Users could create personalized views of the dashboards/reports most valuable to separate from the comprehensive list that will be available. (pic for reference, not exact layout. Visuals TBD)

Included in TPWStat as future state project of data-driven culture initiative.

[rebekkabry]

Gaps and Opportunities:

• [ ] Bring data outputs and data sources into alignment or cycle. For example: SMD has an alignment and cycle between custom applications and original data sources; there are opportunities for data tools and automation to replace Excel storage. OCE opportunity where data used for reporting is not linked to datasets other than Excel.

[rebekkabry]

• [ ] Opportunities to find interdependent and operationally linked divisions and/or services. For example: OCE provides yearly pre-planning schedule and assigns WOs to Pavement; 311 WOs and SRs.

[rebekkabry]

[rebekkabry]

This is starting to sync with DASH initiatives. I will work closely with Kate and team on DASH product/project.

@amenity how should we handle this portion of the ecosystem map? Feels like it is starting to align with other projects (that have more team involvement). Close, leave open, link with another issue/epic? ❔

Or should this maybe be used to discuss Peggy's point of 'consider the user(s)'...

• where will the data ecosystem be housed
  • considering Knack
• will it be accessible...to who? where?
  • need to be discussed
• who will use the ecosystem
  • data stakeholders - understand path, set standards and bring alignment from current state, easily understand area of problem based on location knowledge of data pathway
• how will the system be used
  • review current state of department data pathways
  • understand current usage of data, specifically datasets
• how can it be used
  • understand complexity
  • design desired future state
  • insight into department synergies and gaps

[amenity]

I completely agree that Dash will now be the "self-service" access point. I think these are excellent notes to have on hand for Dash user stories/journey mapping/feature mapping, etc. cc/ @katelunceford

No need