Admin - Rundowns
The ROAD Admin - Rundowns page enables users to create and manage Rundown configurations.
Rundown configurations specify which Shows of BCS a Rundown Broker should read and pass to specific ROAD jobs for playout or streaming.
To understand how ROAD processes BCS rundowns, visit Rundown Broker.
BCS instances configuration
Configure connections to your BCS backends via BCSS (HTTP/ WebSocket + DPE token) for rundown jobs
Navigate to: ROAD Admin > Rundowns > BCS Instances
BCS instances are pre-configured connections to a Broadcast System via BCS Service that can be used across multiple rundown configurations. These instances may refer to different Broadcast Systems or vary only by user access for different programs.
Actions
Add new configuration – Create a new BCS instance.
Duplicate – Clone an existing configuration for faster entry.
Delete – Remove obsolete configurations.
Check – Test connectivity for each field (HTTP, WS, Token).
Save / Discard – Commit or cancel changes to the selected configuration.
Mandatory fields to configure are:
Name | Name of the BCS server to connect with (e.g., ROAD-BCS, Local-NNi) |
BCSS HTTP URL | URL to access BCS service over http/https (e.g., http://localhost:8081) |
BCSS WS URL | URL to access BCS service over ws/wss (e.g., ws://localhost:8085) |
BCS user | DigaSystem user with sufficient rights to the BCS instance and the program |
BCS password | The password of the BCS user |
Rundowns
Navigate to: ROAD Admin > Rundowns
This section allows you to create and manage rundown configurations linked to BCS instances. Rundown configurations define how and what should be processed by the backend system.
Actions
Add new configuration – Create a new rundown config.
Duplicate – Clone an existing config for efficiency.
Delete – Remove unnecessary entries.
Save / Discard – Commit or cancel changes to the selected configuration.
BCS Instances – Opens the BCS Configuration page.
Field | Description |
Name | Unique name of the rundown configuration. |
BCS Instance | Reference to a BCS instance (from the BCS instances screen) |
Program | Name of the program to process |
Date | (Optional) Date of the rundown (format: dd/mm/yyyy) |
Show | (Optional) Specific show to load; leave empty to include all shows |
Track | (Optional) Track number; default is 0 |
Protocol Track | (Optional) BCS Protocol Track (1000–1099) for played-out element metadata |
ROAD Job Alias | Job alias that triggers processing of this rundown: (This must match the "alias" in your playout template. No spaces or special characters allowed.) |
RDB Alias | Name of the Rundown Broker instance that will process this rundown. This is either the machine name where RDB runs or an explicitly defined alias set in the RDB configuration. |
Example of a playout configuration for a Icecast streaming server
{
"alias": "myJobAlias",
"name": "template name",
"transitions": [
{
"trigger": {
"type": "Immediate",
"requestedProcState": "Start"
},
"jobDescription": {
"pipeSpec": {
"inputGraph": [
{
"name": "Input",
"filter": [
{
"name": "Rundown Player",
"format": {
"sampleRate": 44100
},
"rundown": []
}
]
}
],
"mixer": {
"route": [
{
"input": {
"channels": "0,1",
"graph": "Input"
},
"name": "Route",
"output": {
"channels": "0,1",
"graph": "Output"
}
}
]
},
"outputGraph": [
{
"filter": [
{
"name": "FFmpeg Streaming Renderer",
"url": "icecast://source:<pass>@<your_icecast>:<port>/<showname>",
"outputContainerFormat": "mp3",
"outputAudioCodec": "libmp3lame",
"outputVideoCodec": "",
"options": {}
}
],
"name": "Output"
}
]
}
}
}
]
}
Notes & best practices
Verify all URLs and tokens using the Check button before saving BCS configurations.
Follow standard naming conventions for ROAD Job Alias: use no spaces or special characters.