• US: +1-800-476-7226

Software and services for the radio industry.

Automation System: Rushworks Automation

Modified: 2017/05/17 13:18 by EricCrocker - Uncategorized
Edit

Rushworks Automation

back

WORK IN PROGRESS - Please understand that we are actively rewriting much of our documentation and this page is currently "under construction"; if there's anything that you'd like to see added to and/or expanded upon, please let us know by sending us a smile.

Edit

Introduction

RadioTraffic converts to a specific Rushworks Automation log format.

Edit

Station Configuration

To configure RadioTraffic to work with Rushworks Automation, you will first need modify the station configuration to utilize Rushworks Automation as the automation system. In the settings module, open 'Stations'. Select the station you want to configure and double click. Once the station configuration is visible, select the 'Files' tab. Select the 'Product' to Rushworks Automation using the drop down selection tool. The 'Automation Log Path' is where RadioTraffic will export the log to, so set this to the file system folder that Rushworks Automation will pull the file from.

The filename that we export follows the MDD.sch pattern where M represents the month converted to a 0-9,A-C single character and DD represents the day of the month.

Edit

Cart Numbers

Rushworks Automation system can use cart number from 00000000001 to ZZZZZZZZZZZ (11 character alpha/numeric).

Edit

Automation Commands

RadioTraffic exports the cart number portion of automation commands except for special commands; see below.

Edit

Log Notes

Log Notes are currently not supported.

Edit

Programs

Programs are supported; see additional information below.

Edit

Avails/Breaks

Avails are used (in addition to scheduling) in special ways when exporting; see below for additional details.

Edit

Log Reconciliation

Automatic log reconciliation is currently not supported; if you would like to have this available, please contact us for further details.

Edit

FAQ

TODO Add any questions as they come up to this section.

Edit

Additional Information

Sequence type (column 1) is determined using special Automation Commands that have an at (@) sign in the "command" field; where the "cart number" specifies the type of sequence (LOI, LOB, etc.). If this command does not exist on the log, the default sequence type is "LOI".

Event times (column 4) are determined using special Automation Commands that have a pound sign (sharp, #). The time on the log that these occur sets the "event time". The "cart number" of these events determines the "event length" (column 5). The event length is in number of minutes. The segment number (column 6) and segment entry (column 7) are reset to 1 for these type of entries.

The segment number (column 6) is controlled using the plus sign (+). Any time the plus sign is encountered on the log, the segment number will increase. The segment entry (column 7) increments automatically for each and every spot, program and automation command exported.

LOB sequence entries will utilize the Avail time start time for each and every entry of the Avail; other entries will utilize the actual start time of the entry as the time.

Programs, regardless of current sequence type, will utilize the start time of the event.