Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Current »

Agenda

New Items

  1. Market Plan is currently available in the Workspace Module.

    1. Workflow example from Market Plan, to Explore, to Inventory Plan

      1. The Workflow example submits a goal of 50 TRPs in Chicago using full wraps

      2. As a result, we are able to build a package of full wraps with spot IDs

Action Items Review

  1. Review transit systems for approval from staging into production (Task Force)

  2. The production cutoff and release schedule is posted. Inventory into production will follow this schedule (Geopath)

  3. Has anyone in the Transit Task Force had the chance to test workflows in Staging? Please provide feedback in the User Workflows. We would like everyone to partake in testing workflows.

  4. Transit Task Force, please create your own packages using your inventory to approve the measures you see in Staging (Task Force)

    1. The sample packages sheet can be used as one potential process in creating packages

  5. Provide additional example of Fleet Impressions Changes for placement type (Geopath)

Notes

Market Plan

The Market Plan is now available for testing. We walked through a workflow from Market Plan to Explore to Inventory Plan. In the example there were 19 CTA full wrap spot IDs audited.  One spot from each garage was selected for a total of 7 spots.  The spots were selected as having a larger quantity of units available. 

Not being able to enter in Operator in Market Plan. Several reports of the program not processing the Operator request, maybe resolved with Geopath IT data transfer.

What constitutes a spot ID

Each garage creates a Geopath ID for a frame media name, while additional attributes create Spot IDs. We also referred to the confluence page which lists the attributes which create a spot ID. 

 

How will we account for digital advertising?

Our database is structured to account for static or digital media.  We have fields for ads in rotation and ad length.  The construction is the moving vehicle and the frame is the section which the advertising can be affixed.  The face is advertising space while the layout accounts for multiple areas of advertising.  For digital fleet advertising, because we keep track of the location of the vehicles, we could build hex maps displaying geographies with a heavier presence. 

 

Can we roll up Market Plan metrics by garage?

The market plan is too aggregate while the inventory plan is too specific.  Can we list certain deployments based on garage with the standards for planning numbers. 

This is a feature from the legacy tool which group members would like to reinstate.

We would want to make a few corresponding modifications; with Market Plan we would specify what those parameters are, disclosing what the meta data is. 

Thoughts on the UI?

If they are transit specific, feedback would be welcome here.  If the considerations are not media class specific, they could be directed towards the Futures Council and Scott’s team. 

Action Items

  1. Review transit systems for approval from staging into production (Task Force)

  2. Test workflows in Staging. Please provide feedback in the User Workflows. (Task Force)

  3. Create your own packages using your inventory in Staging. Share any packages in Reporting Standard Packages (Task Force)

  4. Provide additional example of Fleet Impressions Changes for placement type (Geopath)

  5. Review Market Plan modification request (Geopath)

  6. Test Market Plan inputs. E.g. Operators (Geopath)

  • No labels