Make sure to install the latest version of MediaOps Plan and Live. Once this is done, any script located in the 'MediaOps/OrchestrationScripts' folder in the automation module can be selected to run at those events. Regular automation scripts have elements of a given connector/version and parameters that can be used as inputs, but know that you can also make use of profile parameters (to have discreets, min/max, units, ...) with Orchestration scripts.

• From Resource Studio, you can predefine on pools the scheduling config (three dots => Scheduling config). This will define what automated actions have to be triggered when such a pool is used in a workflow or job. When a node is added to a workflow or job, the orchestration settings defined on the pool will be copied to the node.
• From Workflow Designer, you can define orchestration settings for workflows and nodes of workflows. This will define the automated actions that have to be triggered when such a workflow is used. When a job is created from a workflow, the orchestration settings defined on the workflow and the nodes within will be copied to the job.
• From Scheduling, you can define orchestration settings for jobs and nodes of jobs. The orchestration settings define the automated actions that will trigger at the different events of the job (pre-roll start, pre-roll stop, post-roll start, and post-roll stop). When no pre-roll is defined, then the pre-roll start and pre-roll stop will be triggered sequentially if both are defined (similar for post-roll). If an orchestration script is defined for the job for a specific event, then it is up to that script to trigger orchestration scripts defined on nodes and connections. If no orchestration script is defined for the job for a specific event, then all node and connection orchestration scripts will be executed automatically for the corresponding event.

With the upcoming MediaOps release 1.6.0 (aimed to be released by the end of June 2026), it will be possible to link input arguments to reduce the overhead for operators to fill in all the needed arguments manually. This way you can link for example, the selected resource and/or resource properties to input arguments of the automation script to ensure when you swap the resource the script will also have the updated input arguments. Let us know if you have any challenges to set this up.