Action Items Review
Reviewed updated methodology 1-pager documents (please confirm that you’ve reviewed)
Test out UX workflows in Insights Staging
Transit Authority & Operator grouping - transit authorities listed as operators
Inventory Plan: Frame Selected - adding in larger quantities of units
Market Average data - Market Plan pending
Transit Release Timeline
124 remaining under audit
Reporting Standard Packages of Transit Inventory
Market Planning Level (goals only)
Inventory Specific (discrete inventory with dates)
Inventory Set
Intermediate (does not exist yet in UX)
Inventory Plan reach and frequency for fleet packages
Pending bug fixes in UX
Notes
TAB vs. Geopath highlights changes
Station Interior doesn’t show designation, perhaps include?
If Meeting Notes
Methodology Document Review
In order to finalize the methodology 1-pager documents, we opened the floor to any thoughts. The Tab/Geopath designation in the original one pager was helpful to breakout the old vs. new methodology. Ultimately, we’ll want to keep a uniform design between the fleet and station interior documents and will be sharing this feedback with our marketing team.
If the numbers have changed, what are those probable influences. Example
Operator: accounting for multiple media operators
Market plan would might be some probable reasons why. If the impressions went down, can Geopath provide any examples?
UX Workflows
Why are the Transit Authorities listed under Operators? The Operator field accounts for both media vendors and transit authorities. The structure is designed to be able to search for inventory associated with a transit system. In the case of the New York MTA, for example, “MTA” would be the “operator” though there are multiple transit agencies (“divisions”) such as the Long Island Railroad, the Metro North, subway and bus.
The Inventory Plan – Frames Selected feature was described in a user workflow. The number of frames selected just needs to be fewer than or equal to the frames total.
The Market Plan currently under development will be able to allocate inventory across system rather than by garage and placementAverage quantities . Would users be able to find average metrics by garage? system-wide. Users would be able to apply a manual process through inventory plan or garage distinction in market plan or saved inventory setsMarket with a saved inventory set. To accommodate a market plan garage level , examples. previous vs current pullsInventory set ID built into the API, porting over into UXmetric, Geopath can look into the requirements.
Transit Release Timeline
The Tier 1&2 systems in staging can enter into production on 3/30, with some limited time to review R/F. The proceeding deadline would be 4/13.
Tier 3 inventory has been formatted to database spec. Base impressions will be available the week of 4/11.
Reporting Standard Packages of Transit Inventory
How can we expect to use Inventory sets? An inventory set ID is the inventory package detail, summarized into a capsule. The inventory set ID is built into the API and we would have the capability of porting this over to the UX.
How are inventory sets updated? public/private by username/credential. provision accessapplication: outfront url package linked There could be public inventory sets available to all members as well as private inventory sets verified by the username credentials. Those private sets could be shared to other users.
Applications of an inventory set could include outward facing services. For example, a rate card might link to the inventory set and data.
Action Items
Provide examples of changes in impressions and causes (Geopath)
Test workflows in Staging, provide feedback in User Workflows (Task Force)
Provide feedback on Reporting Standard Packages of Transit Inventory (Task Force)
Address alternative field names for “Operators” and “Division Name” (Geopath)
Inventory Plan Reach and Frequency for packages (Geopath)