Transit & Fleet Task Force meeting 220621

Agenda

Action Items Review

1. Review transit systems for approval from staging into production.  Review the TRPs and impressions for individual transit systems, approve measures (Task Force)

2. Test Market Plan and post any feedback or useful examples of output

   1. Sample Packages can also be created and shared using Market Plan (Task Force & Geopath)

   2. Reviewed the inclusion of the total number of spots data point for the summary level. Output documented to show Export Output spots summary. (Geopath)

3. Write examples of Own and Manage representation types.  Phoenix Valley Metro is a requested example

4. Provide feedback on Guidance for Using Preliminary Impressions

   1. Access to impressions data

   2. Define Popfacts demographic audiences

5. Find updates for transit and Market Plan R/F (Task Force & Geopath)

   1. Briefing from the Data & Technology team

Notes

Workspace – Market Plan

We reviewed the total number of spots data point.  The Market Plan UI does not currently show the total number of spots required. The Market Plan shows the required spots by garage but not the total in the summary line item. The Market Plan does report the total number in the Export Output at 534 units, as displayed in the example. The total number of units, however, would not be editable as it would require an allocation methodology. We have notified our team working on the User Interface and noted that this data point should be added. 

Operators/Division Name

We walked through Valley Metro as example for finding intended inventory.  The manage accounts would be Clear Channel – Valley Metro and Outfront – Valley Metro while the own account is Valley Metro.  The first screenshot shows finding the own account, Valley Metro which would include all Clear Channel and Outfront inventory.  The second screenshot shows under the Division Name, Clear Channel – Valley Metro.  Outfront would be included in this list as well, with the next update to Staging.  We also walked through the example of not knowing the name of the transit system.  You could get to the same data if you filtered for Clear Channel bus exterior in Phoenix. 

Guidance for Using Preliminary Impressions

We are sending out an update in our Newsletter that Transit and Scheduled Fleet impressions will be available upon request. The Guidance on Using Preliminary Impressions will be able to be shared for any members asking for more information.  We were able to clarify items that need editing. The references to the Staging site are not all required.  Secondly, the POPFACTS audiences can be defined to differentiate the two age breakdown sets.   

Briefing on Transit R/F

A new proof of concept architecture for market plan is under way to address performance issues for roadside.  The update is targeted for staging testing next week. 

The Data and Technology compiled datasets for observed reach data along a transit travel path.  They will require comparison analysis against the existing reach models. 

Action Items

1. Review transit systems for approval from staging into production.  Review the TRPs and impressions for individual transit systems, approve measures (Task Force)

2. Test Market Plan and post any feedback or useful examples of output (Task Force)

3. Apply updates around Operators/Division name, including updated filtering and revised headers (Geopath)

4. Update Guidance for Preliminary Impressions document. References to staging and POPFACTS audiences will be edited. (Task Force and Geopath)