The transition from standard time to daylight-saving time (DST) will occur at 02:00:00 ET on Sunday, March 13, 2016. The ContentDepot transition to DST is very straightforward:
If your local computers have been updated with the latest DST patches, they will automatically step forward at 02:00:00 local time on Sunday, March 13 (check with your automation/playback system vendor to see if you need to do any special maintenance or procedures to accommodate this transition).
The ContentDepot headend will transmit stream setup data and commands for the 03:00:00 ET hour at the end of the 01:00:00 ET hour. We recommend you review your station schedule for Sunday, March 9 to verify your local programming flow from 01:59:00 ET to 03:00:00 ET. In the ContentDepot, the 02:00:00 ET hour on Sunday, March 9 does not exist and will not execute. The System will operationally step from 01:59:59 ET to 03:00:00 ET.
The only operational function in your ContentDepot file storage receivers affected by DST offset is the automated deletion of files based on their kill dates. The SFX 4104 receivers still operate on the "old" DST transition dates, but deleting files an hour later for three weeks won't make any difference in local operation. Displays and log entries will be incorrect for three weeks, but that's easily remedied, if desired, by hand-setting the time zone an hour "ahead" at a convenient time. There is no operational effect of any DST change in your stream decoders—they always function in Coordinated Universal Time.
What Else Do You Need to Do?
The most important action you can take is make sure that your local production systems (including time-of-day displays) have the latest updates so that they'll properly step back (fall) or step forward (spring) . You should also check with your automation/playback system vendor to see if there are any special scheduling considerations for your particular installation.
If you require additional assistance, the PRSS Help Desk is available by telephone at 800.971.7677, or via email: firstname.lastname@example.org
Posted: March 10, 2016