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 numbers have changed, what are those probable influences. Example
Operator: accounting for multiple media operators
Market plan would allocate inventory across system rather than by garage and placement
Average quantities by garage? system-wide. manual process through inventory plan or garage distinction in market plan or saved inventory sets
Market plan garage level, examples. previous vs current pulls
Inventory set ID built into the API, porting over into UX
How are inventory sets updated? public/private by username/credential. provision access
application: outfront url package linked
Notes
Methodology Document Review
...
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)
Address alternative field names for “Operators” and “Division Name” (Geopath)
Inventory Plan Reach and Frequency for packages (Geopath)