The BrightLogic Digital Automation System provides real-time automation processing, machine control and database management through a single rack unit, embedded hardware platform.
The applications are all programs used in conjunction with the MPC-3200. All programs, with the exception of the Automation Processor, are graphical user interfaces that allow interaction through communication with the MPC-3200 and run on just about any basic Windows workstation. All operator actions can be carried out on any of the DAS workstations.
The Automation Processor, also known as the AP or Real-Time Processor, is the heart of the DAS. It is a non-graphical application that runs under the WinMOS on the MPC-3200. The AP handles all real-time processing of commands and schedules. It also regulates connections from the client applications, including relaying direct machine control commands initiated by an operator.
The Operator Interface Program provides scheduling capabilities for virtually all server-oriented media clips, IRDs, VTRs, character generators, PSIP generators and other broadcast equipment. This application queries the server systems, identifies discrepancies between clip lists and schedules, and produces appropriate system alarms. It allows monitoring of schedules as execution takes place. The built in schedule editor provides capacity for sixteen separate, user-configurable, real-time event lists, each with up to 2,000 events. Schedules can be created for any date in advance. And with configurable schedule load times, schedules are imported into your Day-Of-Air automatically. This system supports direct-schedule management and schedule import from various traffic formats, as well as managing 'as-run' execution logs of completed activities.
The Machine Control Program provides direct, manual control for any connected device, via mouse-driven input or an optional touch-screen control system. The MCP allows for status and tally of all machines connected to the DAS. The interface allows for easy navigation from device to device. Along with basic machine control there is a feature-rich Video Clip Dubbing and Trimming screen, which allows for setting up frame-accurate dubs from tape as well as trimming video clips via a Jog/Shuttle wheel or direct timecode editing.
The LanAp serves as the pipe between the AP and the workstation applications. It establishes communication between the workstation applications and the AP via TCP/IP over a standard 10/100Base-T network or the internet. The LanAp synchronizes clip, scheduling, and resource information with the AP. Thus to properly run DAS applications on a particular workstation, the user connects their LanAp to the AP, and then the LanAp runs quietly in the background.
The Resource Editor is the system configuration component of the Digital Automation System. This application is used to manage all automatable devices connected to the DAS.
The Media Editor is designed to give the user full access to the data assigned to video clips associated with the automation system. It allows the user to view a complete list of video clips from various servers, all in one centralized location. Use sorting filters based on a wide variety of criteria to condense the list into a precise snapshot. The Media Editor may also be used to manage video clip content with respect to whether or not it gets archived via the NLS. The Media Editor allows for transferring of multiple clips from multiple servers to one destination server. With the Media Editor the user can edit information, delete, and duplicate information for all video clips.
The Log Viewer application is designed to give the user a simple view into the event and system data log files generated by the Automation Processor (AP). The types of logs are System Status, Alarm Logs, Schedule 'As Run', and Schedule Status. This application provides the user with a valuable tool for troubleshooting different issues within the automation system, and an authoritative spot to check any changes made to the system. This application will allow for viewing and filtering of these log files, as well as exporting the 'As Run' logs for Traffic system reconciliation.