Account Management

You need to upload files to an Amazon Web Services (AWS) S3 bucket managed by FreeWheel, which requires an AWS access key.

There are two ways to handle the AWS key:

1. (Recommended) Provide your own AWS account Amazon Resource Name (ARN) to FreeWheel. FreeWheel creates an AWS role that allows your AWS account permissions to upload and list files in your dedicated folder.)
2. FreeWheel provides you with an AWS access key that grants permissions to upload
   and list files in your dedicated folder.

🚧

In the second approach, the AWS account is owned by FreeWheel, and is subject to
FreeWheel's key rotation schedule. This scenario requires more communication between
you and FreeWheel than the first approach.

File Specification

• Must be a comma delimited .csv file
• You are responsible for providing the necessary .csv file before triggering Schedule
  Optimization.
• Each file must be associated with one single MRM network.
• File name must follow the convention of:

spot_feed_BCast{Broadcast_week_start_date}_{Network_ID}_{File_Drop_Date}.csv

where Network ID is your MRM network ID that indicates the network allowed to
access the data and the File Drop Date follows the format of YYYYMMDDHH24MMSS, e.g.
20190606012450.

📘

Note

If the file is compressed, the compressed file must still start with the above format, and have the extension type attached at the end of the file name.

• Each file may contain all or part of the capacity for a particular week, but must not contain
  data outside of the single week.
• Each file must be below 100MB before compression.
• Each row must consist of the total available seconds that Scheduler can consider
  as capacity within a fifteen-minute time window, which resides on a channel, and is within a SysCode.
• Each CorpNetworkCode must map to a valid channel in MRM when ingested.
• Each SysCode must map to a valid syscode in MRM when ingested.
• CorpNetworkName and CorpZoneName are allowed to be empty.
• Time15Min is expected to be a value in a local time zone.
• RawCapacitySeconds is the total break duration, in seconds.
• InventoryType can be LOCAL, MARKETING, or NATIONAL, but only LOCAL
  inventory is considered for addressable inventory allocation.
• insertable_flag can be 1 or 0, but the inventory is considered for addressable inventory allocation only when the insertable_flag is 1.

Data Fields

Ingestion Validation Criteria

• Each file must begin with a spot_feed_BCast prefix and end with a .csv suffix.
• Each field in each row must be separated by a comma.
• Each field must contain data of a valid format, as specified in the Data Fields section above.
• Each file must contain only dates within a calendar week that matches the start date for the week specified in the file name.

Ingestion Result

Each file, when processed, generates an email containing the ingestion result sent to an email
address of your choice. The email specifies whether the ingestion succeeded, and if not,
provides an error message for trouble shooting.

Implementation Recommendations

• Provide the upcoming four broadcast weeks’ local-break capacity data each Wednesday
• Only include Comcast owned & operated, LSA insertable, and local sales inventory in the capacity files
• AutoScheduler by default considers all the break data that you provide as LSA-eligible. You are expected to validate the business rules and ensure all the break data that you provide to FW are considered as LSA-eligible from both business and technical perspectives.

📘

Note

The cadence and scope of data could change as your business and AutoScheduler use cases evolve. It is best to be flexible with your ingestion cadence and scope.