Abstract: A device manager includes a processor and memory, coupled to the processor, that stores a program of instructions. The processor is configured to execute the program of instructions to determine an availability of at least a portion of a cloud-based media management system configured to provide media automation services to a managed device, and in response to determining that the at least a portion of a cloud-based media management system is unavailable, transmit a status message to the managed device, wherein the status message indicates that the managed device is to emulate the at least a portion of a cloud-based media management system.

Abstract: An application programming interface (API) receives broadcast-related information from media automation applications. A traffic log is received from a first media automation application configured to generate a traffic log associated with a media station, and spot information associated with spots included in the traffic log is received from at least a second media automation application. The API stores the broadcast-related information, including the traffic log and the spot information, in one or more databases. The API also receives, from a media playout system, at least one request for the stored broadcast-related information. The media playout system is configured to insert media content into a media broadcast associated with the media station. The API provides the requested broadcast-related information to the media playout system, which inserts the media content into the media broadcast associated with the media station.

Abstract: An edge device operates in an online mode of operation during a first period of time, wherein during the online mode of operation, the edge device obtains broadcast-related information originating from media automation applications. The edge device operates in a local mode of operation during a second period of time, wherein during the local mode of operation the edge device obtains locally stored broadcast-related information, and emulates services provided by the media automation applications. The edge device operates in a disaster recovery mode of operation during recovery from the local mode of operation, wherein during the disaster recovery mode of operation the edge device obtains stored broadcast-related information from a content recovery database.

Abstract: An edge device operates in an online mode of operation during a first period of time, wherein during the online mode of operation, the edge device obtains broadcast-related information originating from media automation applications. The edge device operates in a local mode of operation during a second period of time, wherein during the local mode of operation the edge device obtains locally stored broadcast-related information, and emulates services provided by the media automation applications. The edge device operates in a disaster recovery mode of operation during recovery from the local mode of operation, wherein during the disaster recovery mode of operation the edge device obtains stored broadcast-related information from a content recovery database.

Abstract: An edge device remotely accesses cloud-based media automation services by pointing an interface of the edge device to a cloud-based sequencer. Broadcast logs defining a broadcast schedule and media files specified in the broadcast logs are obtained from the cloud-based sequencer, and local versions are stored in a storage device locally accessible to the edge device. Availability of the cloud-based sequencer is monitored, and if the cloud-based sequencer becomes unavailable, the interface of the edge device is pointed to a local sequencer instead of the cloud-based sequencer. The local sequencer emulates one or more media automation services normally provided by the cloud-based sequencer. In response to determining that availability of the cloud-based sequencer has been restored, the edge device's interface is re-pointed to the cloud-based sequencer.

Abstract: An edge device remotely accesses cloud-based media automation services by pointing an interface of the edge device to a cloud-based sequencer. Broadcast logs defining a broadcast schedule and media files specified in the broadcast logs are obtained from the cloud-based sequencer, and local versions are stored in a storage device locally accessible to the edge device. Availability of the cloud-based sequencer is monitored, and if the cloud-based sequencer becomes unavailable, the interface of the edge device is pointed to a local sequencer instead of the cloud-based sequencer. The local sequencer emulates one or more media automation services normally provided by the cloud-based sequencer. In response to determining that availability of the cloud-based sequencer has been restored, the edge device's interface is re-pointed to the cloud-based sequencer.

Abstract: An application programming interface (API) receives broadcast-related information from media automation applications. A traffic log is received from a first media automation application configured to generate a traffic log associated with a media station, and spot information associated with spots included in the traffic log is received from at least a second media automation application. The API stores the broadcast-related information, including the traffic log and the spot information, in one or more databases. The API also receives, from a media playout system, at least one request for the stored broadcast-related information. The media playout system is configured to insert media content into a media broadcast associated with the media station. The API provides the requested broadcast-related information to the media playout system, which inserts the media content into the media broadcast associated with the media station.