EZ-NET for RadioTraffic.com

About

EZ-NET for RadioTraffic.com is a radio broadcasting industry utility that can save traffic people significant hours per week. stations that used to spend over 6 hours per week importing network ads the old fashioned way tell us they can now get the job done in under 6 minutes with EZ-NET for RadioTraffic.com. The EZ-NET for RadioTraffic.com utility contains everything you need to import, process, manage and report on network related spots.

This document relates to the special edition available for Marketron Broadcast Solutions RadioTraffic.com Premier product. EZ-NET for RadioTraffic.com is not the same product as EZ.NET; but rather a custom, directly-integrated edition that works directly with RadioTraffic.com's internal/back-end systems providing a very seamless and tight integration.

The EZ-NET for RadioTraffic.com application contains everything you need to import, process, manage and report on network related spots.

There are several advantages gained by using EZ-NET for RadioTraffic.com.

The first of which is the significant reduction of time spent gathering the ever-changing schedules (which change every week - many times, more often), managing existing copy and new copy (which changes every week) and leveraging a strategy that minimalizes the amount of time spent scheduling these spots on logs.

The above is done using a three-part approach:

The second advantage is providing a simplified summary of work to be done by the production team to prepare the automation system for executing these spots. This is done by providing all of the details of what has been added and/or extended for the upcoming week in a simple and straight forward easy to follow report.

The third advantage gained is the simplification of "reporting back". Most networks require that you provide them additional details regarding your actual follow through on your commitment to airing these spots. EZ-NET for RadioTraffic.com provides a detailed report that is specifically designed to simplify this process by bringing together all of the as-run details in a format that is specifically designed to reduce the time it takes to "report back". Additionally, this information is automatically leveraged when you utilize the built in custom web browser to navigate to the networks web sites for the purpose of submitting affidavits. All you have to do is "click" through and review the process.

What the network states is what we do, automatically.

Comparison

Without EZ-NET for RadioTraffic.com

Before even beginning the process, it is necessary to have the following available:

Now that we have this, the following occurs every Thursday/Friday:

At this point one must cross their fingers hoping that nothing was missed, no mistakes were made, and all contract obligations were adhered to.

Now, after each weekly schedule has completed, it is then necessary to take the "as-play" information from the traffic / automation system and manually "re-key" it into the submit affidavits forms provided by the networks through their websites. This, you can imagine, is a time consuming and extremely error prone process.

With EZ-NET for RadioTraffic.com

After the initial setup which includes adopting the overall strategy mentioned above, every Thursday/Friday:

When notified of a schedule change:

When the weekly schedule has completed:

Yes! That's all there is to it. Using EZ-NET for RadioTraffic.com along with the right strategy, the painful process of dealing with getting the details from the networks to the air is reduced to nearly nothing.

Supported Networks

Networks

The list of supported networks is growing all the time; here is a list of what is currently supported:

Additional networks are added based on what our customers encounter (and, of course, what is feasible).

Installation (Walkthrough)

(TODO) - For installation, scroll to the bottom of this page.

login

(TODO)

Main Screen

(TODO)

Networks

Layout

(picture)

Across the top is the Main Menu. On the left hand side of the window you’ll see a list of network vehicles. When you select a network vehicle, the right hand side of the screen contains the network schedules for that vehicle.

Main Menu

Network Vehicles

The network vehicles section contains the list of active network vehicles that will be processed when clicking on the “Fetch” button (located just below the list of network vehicles). Each vehicle is named using a short-hand nomenclature to assist in easily identifying where the network vehicle originates and what station it belongs to. For example, “P.KXYZ-AM – Yellow Rose News Hour” is the Yellow Rose News Hour network vehicle from Premiere Network for the KXYZ-AM radio station. As a side note, we also, by default, create an avail type that matches this name to assist in the direct placement of these spots on the log; you just need to include these on your templates/formats accordingly. For example, using “Yellow Rose News Hour”, we are bartering 7 minutes per week. The first time we see this network vehicle (during configuration), you will also need to update your templates/formats to specify where this network vehicle will fall in order to dedicate the 7 minutes per week (according to the agreed upon schedule). After doing this, the spots will fall according to this configured placement so you basically don’t have to worry about the “scheduling” of these each week which further reduces the overall effort involved.

Context Menu

This menu is access by using the mouse to right click anywhere in the network vehicle pane.

Fetch Button

Clicking on the Fetch button will process the entire active list of network vehicle entries for new network schedules.

Progress

The bottom right hand corner of this window you will see two progress bars. The first progress bar represents the scanning progress for the processing of the network vehicles. The second progress bar represents the overall progress for processing any found network schedules.

Network Schedules

The network schedules pane contains two tabs, Schedules and Network.

Schedules Tab

The Schedules tab contains a list of network schedules that have been successfully imported using either the Fetch button or the Fetch tool from the network vehicle context menu. Each network schedule represents one week worth of spots.

Context Menu

This menu is access by using the mouse to right clicking an a particular network schedule pane.

Network Tab

The “Network” tab provides for a custom web browser that enhances/streamlines the networks actual web site.

Some of the customizations include:

Close Button

Closes the window.

Network Vehicle

This window contains the configuration details for a particular network vehicle and is accessed from the main EZ-NET window.

(picture)

The above screen shot represents the default view of the network vehicle.

Across the top of the window you will see the name of the network vehicle and the current status.

There are three tabs ("Scheduling", "Copy" and "EzScript").

Copy

By default, the "Copy" tab is selected displaying the list of Copy associated with this network vehicle. This provides you the ability to make changes to Copy in the event of changes occurring after the schedule was imported.

Scheduling

(picture)

In the less often times that you need to integrate EZ-NET differently than the defaults provided, you can utilize the "Scheduling" tab to control the behavior of how EZ-NET will integrate into your existing log pipeline.

Defaults

CS DO NOT CHANGE THIS without significant consideration. Changing the avail type value to something "you already have" may save you some time and effort in the beginning, but you will lose much of what EZ-NET has to offer in the way of saving you time and effort every single day by not using the avail type created specifically for this vehicle. In other words, investing now in modifying your templates/formats to use the avail types created for this vehicle will save you countless hours going forward by effectively removing any work related to "scheduling" these vehicles on logs, each and every single day. With that stated, when choosing a different avail type, you should really consider configuring the "Vehicle Separation (optional)" section; otherwise, you may end up with undesired separation since, by default, EZ-NET doesn't need to worry about this because of the dedicated avail types that it utilizes.

Vehicle separation (optional)

CS When leaving the avail type to the default created and leveraging this on logs/templates, you should really consider leaving the separation type set to None in order to get the best possible results.

EzScript

Variables

It is possible to apply EzScript during the import process in order to affect the behavior of how RadioTraffic will translate the schedule provided into a schedule that will be used. The EzScript related to this vehicle (if any) is located on the EzScript tab.

The following variable(s) are available:

mergedayparts

Normally we import the schedule "as-is". If the network has defined the schedule in such a way that the times are pretty specific (especially true with regards to pledge times), EZ-NET will import this so that the times are pretty specific (again, "as-is"). If you wish to override this behavior, you can specify the mergedayparts variable in the script and set the value to something other than zero. This will cause the import process to ignore the specific dayparts defined, determining the earliest and latest times and use those results to determine the overall start and end time of all of the scheduled items.

Examples:

mergedayparts = 1

LET mergedayparts = 1

CS Currently, the mergedayparts variable is only enabled / available / active when importing schedules from Premiere Radio Networks, Westwood One, United stations Networks, ESPN, Compass Media Networks and ADLarge Media. The usage of the LET keyword is optional.

forcewholeday

Normally we import the schedule "as-is". If the network has defined the schedule in such a way that the times are pretty specific (especially true with regards to pledge times), EZ-NET will import this so that the times are pretty specific (again, "as-is"). If you wish to override this behavior, you can specify the forcewholeday variable in the script and set the value to something other than zero. This will cause the import process to ignore the specific dayparts defined, utilizing midnight to midnight as the overall start and end time of all of the scheduled items.

Examples:

forcewholeday = 1

LET forcewholeday = 1

CS Currently, the forcewholeday variable is only enabled / available / active when importing schedules from Premiere Radio Networks, Westwood One, United stations Networks, ESPN, Compass Media Networks and ADLarge Media. The usage of the LET keyword is optional.

Exclusions

It is possible to apply EzScript during the import process in order to affect exclusions to reduce what is actually imported. The EzScript related to this vehicle (if any) is located on the EzScript tab.

The EzScript is built in such a way that you will define, on a per day of the week basis, what will be excluded. Some examples include:

By default, all exclusions are "off".

The day of the week after the word Set is optional. If not included, whatever is excluded is applied to all days of the week.

The Set statement is pretty flexible and supports several optional target types (Times, Breaks, Hours, First, Last and All). The definitions for each are:

Set DayOfWeek Exclude Times ("time","time")
Set DayOfWeek Exclude Breaks ("value","value")
Set DayOfWeek Exclude Hours (
number,number
)
Set DayOfWeek Exclude All

DayOfWeek is the day of the week to apply the exclusion; valid values are Monday, Tuesday, Wednesday, Thursday, Friday, Saturday and Sunday. This keyword is optional; if excluded, the Exclude is applied to all days of the week.

The Times, Breaks and Hours versions must contain parenthesis around a "list of stuff". The actual list can be "empty"; which would cause that particular day of the week to be reset to the default for the particular target type.

The individual items, if specified, for Times must be a comma-separated list of _quoted times_. The actual format of these times follows the same rules for the rest of the software.

The individual items, if specified, for Breaks must be a comma-separated list of quoted values that matches how the network is specifying "breaks" (usually referred to as "pledgetime").

The individual items, if specified, for Hours must be a comma-separated list of non-quoted numbers that are between 0 and 23 (24-hour format).

The All version is included to make it easy to completely ignore a particular day of the week altogether.

If any syntax errors exist, a message stating so will be presented during the running of the EzScript (during the import process). Use the errors to assist in correcting any problem in the EzScript and try again.

If a particular exclusion is attempted against a vehicle where the pledge time column doesn't "make sense", the exclusion is ignored.

CS It is now possible to use the "Verify..." button to review the syntactical correctness of the script; this tool simply reviews the correctness of the "words" and overall "punctuation". This tool does not, in any way, guarantee any sort of successful (or failure) result of the actual execution of the script.

Configuration

The EZ-NET configuration window contains all of the access details for each of the networks and stations. This window is accessed from the EZ-NET window.

(picture)

This window is only used when you are beginning to use the EZ-NET or, as the case might be, that you add an additional network vehicle to an existing or new network. To access this, use the “Tools” menu and select the “Options” entry from the EZ-NET window.

Main Menu

Main Body

This window contains an “Excel” style list that contains all of the stations that are enabled for EZ-NET grouped into all of the currently supported networks. On each station line, the associated logon credentials for each of these. To configure a network/station combination, enter the logon credentials.

Upon entering the information, we will validate the information in the background and automatically determine the available network vehicles to populate the network vehicle list on the main EZ-NET screen.

During this validation process, the line will be highlighted in yellow.

(picture)

If the validation fails, the line will be highlighted in red.

(picture)

During the validation processing, the OK/Cancel buttons are disabled. If validation fails, the OK/Cancel buttons will continue to be disabled until any problems are corrected. If the credentials are invalid and cannot be corrected, remove them to clear the problem.

Once finished, press the OK button.

Upon doing so, you'll see any new vehicles added to the EZ-NET network vehicle list.

Non-supported Networks

The list of non-supported networks is unfortunate, but a reality due to decisions made by the respective networks beyond the control and/or influence of Shiny Stone Digital.

Install

Currently the installation works best with Microsoft Internet Explorer. You can launch Microsoft Internet Explorer by following these steps:

Alternatively, you can try to use the eznet_setup.exe. If you choose to go this route, please follow the widely different procedures necessary based on the browser you are using in order to download and launch the installation. Additionally, you may need to:

(¬‿¬)