NNTV MSTR Calculation Document

This documentation contains proprietary information of The Nielsen Company. Publication, disclosure, copying, or distribution of this document
or any of its contents is prohibited, unless consent has been obtained from The Nielsen Company.
 Copyright © 2012 The Nielsen Company
All rights reserved.

Document Version History Log

Version
Number
(xx.yy) Author Version Date Description of Changes Date Distributed
PREFACE

Purpose of this Document

 This document describes how MSTR pass the information to the inner layer basing on which
ONCE will perform metrics calculation according to the selection done by users in the MV screens.

 The document is split by category of dimension providing example of calculation per each of
them.

Using this Document

The following guidelines are to be followed while working on this document:

 Calculation rules and examples refer to each single category of dimension (e.g. Date Range,
Viewing Sources, other)

 To simulate any possible scenario, it is just needed to merge together calculation rules of each
single dimension category that will be included in the final layout (e.g. if the final layout will include Date
Range dimension and Daypart dimension, the final result is given by the sum of the related calculation
rules)

 The breakdown of each single dimension category is given by the selection done in Media View

References
The following references have been referred to or used as input while preparing this document:

Reference Location Description

SRS Contains FlexFormatter platform
 requirements

TABLE OF CONTENTS
 Project Requirements Planning
 Program/ Project Scope

Micro Strategy (MSTR) is envisioned as the platform used for generating Flexible Formatter report grid
via Report Viewer (MV).

 MSTR define the grid specs and passes them to an inner layer which provide ONCE element for
the calculation
 Allow users to re-arrange their report on the fly by adding/removing/moving dimensions
without the need of submitting a brand new report
 Saving and sharing re-arranged layout as new template


 Interface Document
 Interface purposes

Micro Strategy communicates with ONCE via an inner layer which collects report grid information and
provides ONCE with them for generating stats accordingly.
Calculation fragmentation is driven by grid structure provided by MSTR, which is given by the dimensions
included in the report layout, and the item selected in MV per each of the element included in the layout
Business Rules and Assumptions with regard to each possible scenario are detailed out in this document.
This document provides the general rules, and specific rules related to each single Dimension category;
to generate all possible scenarios, those rules shall be combined together

 Interface systems

System Name Business Area Description

Media View Media 3.0 Media View will provide Media 3.0 with inputs for
the generation of reports
ONCE Media 3.0 ONCE shall use the input provided by Media
View to generate extracts
MSTR Media 3.0 MSTR displays extract provided by ONCE and
generated using grid structure provided by MSTR

 Reference Information

Document References

Reference Name Location Description

 Acronyms and Abbreviations

The following acronyms and abbreviations have been used in this document

Acronym/Abbreviation Description

BPQ Better Product Quicker: A Nielsen enterprise process framework

INT Reqs Interface Requirements Specification

ONCE One Nielsen Calculation Engine

MSTR Micro Strategy

MV Media View

 MSTR Time Period report – General report rules

A Time Period report is made up of the following specifications that Media View will pass to ONCE for
the calculation:

 Date Range (dateKey)

 Viewing Source (ViewingSourceId)

 Demographic (demographicId)

 Data stream (dataStreamId)

 Dayparts (timeKey)

Foreach UI specification, the MSTR dimension creation process will assign the corresponding values for
each dimension the specification belongs to. For instance, per each Viewing Source, MSTR will assign the
corresponding value for External Call letters.

Moreover:

 All calculations within the Time Period report will be for the whole measurement period selected
in the UI. For Example: selecting Monday to Friday for the calendar month of March 2013, the
calculation will process 21 days, which includes Friday March 1 plus 4 complete weeks Mon-Fri.
 Exclusions are identified and applied by ONCE. Information is sent back to Media View for the
report.
The full list of dimensions belonging to each specification is reported below in the document.

 Time Period Analysis Report – Dimensions list

Category Label Description Example

Reports the individual data date
Date Range Date associated with a program or daypart. 12/15/2012
Format is mm/dd/yyyy 01/25/2012
Will identify all increments requested by
the user: Quarterly, Monthly, Daily, Weekly,
Day of Week, Average within Custom
Range, Average across custom Range.
Each of these average types requested will
represent separate rows of data in the
Date MicroStrategy output. For example if the
Date Range
Increment user only requested Daily and Weekly
Increment on the report; for Daily the
report would show data for each date
12/15/2012,
1/31/13, 2/1/13, … 2/27/13. Followed by
Weekly data, the report would show each Week of 12/15/2012,
week as Week of 1/31/13, Week of 1/7/13, NOV 12
Week of 1/14/13, and Week of 1/21/13. 1/31/2013 – 2/27/2013
Avg Will identify type of increment: Quarterly,
Monthly, Daily, Weekly, Day of Week,
Date Range Level/Increme Daily
Average within Custom Range, Average
nt Type across custom Range. Weekly
Displays custom ranges defined by the
user when building their report. This could
Date Range Custom Range represent a Trend Interval. "2011 Baseball Season" and
"2012 Baseball Season"
Date Range Daily Breaks data out by day. 1/5/2013, 1/6/2013…
Breaks data out by week. The start day of
week will be defined by the users minimum
start date requested. For example, the
user may request 2/1/13 (Fri) thru 2/28/13
(Thur) and request Tuesdays and
Wednesdays only. Week of 2/1/13, Week
Date Range Week of 2/8/13, Week of 2/15/13, and Week of
2/22/13 would be available. If the user
would like Sweep (ie. VIP) weeks, then
they should select the minimum start date
of a Thursday based on the 1st date of the
VIP cycle (ie. 1/31/13 Thursday is the first
date of the Feb 13 cycle). Week of 4/30/12
Date Range Month Breaks data out by calendar month. April, May, June
Format is April, May, June. Year will not be
applied to the label. This will allow Year to
 be moved onto the report if the user wants
it aggregated by Week and Year.
Breaks data out by Calendar quarter.
Format is QUARTER 1, QUARTER 2. Year
will not be applied to the label. This will
Date Range Quarter
allow Year to be moved onto the report if
the user wants it aggregated by Week and
Year. QUARTER 1
Breaks data out by Calendar Day of Week
Date Range Day of Week
Monday, Tuesday, etc. Monday, Tuesday, etc.
Indicates the most current Legacy Call
Letters, or Report Call Letter. Users will
have the option to switch from Legacy to
Report Call Letter with a right click
Viewing command. By default, Legacy Call Letter is
Viewing Source
Source displayed. Will need a separate sequence
number than Report Call Letters. For
Station Groups will be the user entered
value. The sort order will be by user
selection. CNDY, Commedy Central
Indicates the affiliation associated with a
broadcast station. Will display 'CABLE' for
cable networks. Will display N/A for
pseudo stations (those that do not
contribute to hut) and any station that does
not contain a value. Will display GROUP,
External Call
Viewing Source if it is a station group. This includes All
Letters
Broadcast, All Cable, All Other, Other
Broadcast, and Other Cable as well as
user defined station groups. If user drags
off Viewing Source, data will be
aggregated by Affiliation. Will reflect most
current affiliation. CABLE, ABC GROUP
Identifies the Daypart selected by the user
Time Daypart
in UI. Early Fringe
Indicate the time increment (Start Time –
End Time) selected in UI by users for a
specific Daypart. It applies only to a
Time Time specific daypart. Different daypart may
have a different increment type. Keep 10:00am-10:30am –
this label when drilling. 10:30am-11:00am

Identifies each Hour within the Daypart

Time Hour
(ie. 8:00pm - 9:00pm) 10:00am-11:00am
Identifies each Half Hour within the
Time Half Hour
Daypart (ie. 8:00pm - 8:30pm) 10:00am-10:30am
Identifies each Quarter Hour within the
Time Quarter Hour
Daypart (ie. 8:00pm - 8:15pm) 10:00am-10:15am
Data Stream Data Stream Indicates the stream of viewing being Live +7
reported.
 The number of hours will not appear in the
label.
The dimension is mandatory.
Indicate the Demographic selected in Female 25-44
Demographic Demographic
report spec. The dimension is mandatory

*MSTR Comments are mentioned in blue

 Time Period Analysis Report – Metrics list

Assumptions:

 ONCE will send the following base metrics to MSTR in order to compute the Total and CVG stats

 Projections - available in RPRTTIMEPERIOD table as two separate

columns,TOTALUSPROJECTIONS and CVGAPROJECTIONS <MN> We need to use
TOTALUSPROJECTIONS for TOTALUS stat that uses projections as its building blocks and
CVGPROJECTIONS for CVG stat that uses projections.

 US UE (For US stats)

 CVG UE (For CVG Stats)

 Number of Quarter Hours

 HUT Projections (For US stats)- no column mapping in RPRTTIMEPERIOD ?or is

HOUSEHOLDPROJECTION the column to be used? <MN:> Need to confirm this with ONCE team. I
believe it’s householdprojection column

 CVG HUT Projections (For CVG Stats)- no column mapping in RPRTTIMEPERIOD ?or is
HOUSEHOLDPROJECTION the column to be used? <MN:> Need to confirm this with ONCE team. I
believe it’s householdprojection column

 Total US:
US AA% = (Projections / US UE) / Number of Quarter Hours- Should TOTALUSPROJECTIONS
column be considered as Projections in the formula? <MN:> Yes. Please verify this with ONCE
team

US AA Proj = (Projections/ Number of Quarter Hours)- Should TOTALUSPROJECTIONS

column be considered as Projections in the formula? <MN:> Yes. Please verify this with ONCE
team

US HUT/PUT % = (HUT Projections / US UE) / Number of Quarter Hours-HUT Projections

column mapping in RPRTTIMEPERIOD? <MN:> Yes. Please verify this with ONCE team
 US HUT/PUT Proj = (HUT Projections / Number of Quarter Hours)--HUT Projections column
mapping in RPRTTIMEPERIOD? <MN:> Yes. Please verify this with ONCE team

US Share % = US AA %/ US HUT/PUT %- Dependent on previous metrics

US AA VPVH = (Persons Demographics US AA Proj / Household Demographics US AA Proj) *

1000-Metric calculation needs explanation(if any level to be involved?)

P2+ Est. Median Age - TBD- IS MEDIANAGE column to be mapped? <MN:> Based on our
earlier discussions, P2+ Est. Median Age will be a computed stat from ONCE.

 CVG:
CVG AA % = (Projections / CVG UE) / Number of Quarter Hours- Should CVGAPROJECTIONS
column be considered as Projections in the formula?

CVG HUT/PUT % = (CVG HUT Projections / US UE) / Number of Quarter Hours--CVG HUT
Projections column mapping in RPRTTIMEPERIOD?

CVG HUT/PUT Proj = (CVG HUT Projections / Number of Quarter Hours)-CVG HUT Projections
column mapping in RPRTTIMEPERIOD?

CVG Share % = CVG AA %/ CVG HUT/PUT %- - Dependent on previous metrics

Minimums- Thresholds under discussion

Intab- Columns are present as CVGAINTABCOUNT,TOTALUSINTABCOUNT

UE-Columns are present as TOTALUSUNIVERSEESTIMATE, CVGAUNIVERSEESTIMATE

Duration-ONCE to provide in output file

Feed Pattern-ONCE to provide in output file