Transit & Fleet Task Force meeting 220315

Agenda

Action Items Review

1. Documentation Review

   1. Methodology Documentation

      1. Forward and Reverse circulation

   2. Fleet Impression Changes

      1. “What has changed” and “Why it matters”

2. Review User Workflows

   1. Systemwide/targeted/combined

Transit Release Roadmap

1. Review of UX in Staging

   1. Walk through video

   2. New Features

      1. Ability to query inventory by transit system

      2. Display total quantity of frames (e.g. Kings) by garage

2. Known Bugs

   1. Inventory Plan RF not displaying

   2. Market Plan allocation (next week)

3. Under Development

   1. Roadside RF dependency for plans with transit AND roadside (TBD)

4. Important Dates

   1. 3/21 release of new systems into staging

   2. 3/30 cutoff for 4/4 release to production

Next Steps:

1. Draft transit executive summary

2. Gather additional fleet measurement requirements

3. Gather additional feedback on UX workflow

Meeting Notes:

Demand side. Is the explanation sufficient?

General trends. E.g. kings fewer impressions, metro markets, etc. Wraps double counted. Pedestrian model

Markets by operator (footprint, product, etc).

User Workflows: mixing in roadside inventory

Highlighting inventory that is placed in area (Manhattan). Exposing route data by garage?

Geopath Spot ID level of detail. street/curb breakout. garage breakout.

Reporting: aggregate level of inventory sets/ package

Exposing routes data by garage?

Hybrid approach - intermediate level between market and inventory plan. Connect with developers to share expected final product.

Reach/Frequency in Inventory Plan available this week

Market Plan 25, 50, 100 weekly TRPs standard package sizes

R/F for transit and roadside being updated, transit alone will remain

Geopath IDs being included in rfps. How will these be provided?

Confluence to document best practices of IDs.