Control Room Scheduling and Resource Allocation
A Blue Prism environment has 3 runtime resources (R1, R2, R3) and a control room that schedules processes. There are two processes: Process A (high priority, runs every hour, takes 20 minutes) and Process B (low priority, runs every 2 hours, takes 45 minutes). Both require the same application, but only one instance can run at a time per resource due to licensing. Currently, Process A is scheduled on R1, Process B on R2. However, R3 is idle. The business wants to maximize resource utilization and ensure Process A always completes within its hour. Recently, Process A missed its SLA twice because R1 was down for maintenance. There is also a backlog of Process B items. The control room manager wants to implement a failover and load balancing strategy.
1. How would you reconfigure the schedules and resource allocation to ensure Process A meets its SLA and improve overall utilization?
Read the worked answer
To ensure Process A meets SLA, implement a dedicated resource pool for high-priority processes. Assign Process A to run on R1 and R2 in a round-robin or failover manner: schedule Process A on R1, but if R1 is unavailable, automatically start on R2. Use Blue Prism's scheduling with multiple resources: create a schedule for Process A that targets a resource group containing R1 and R2, with the option to run on any available resource. For Process B, use R3 as primary, and R1/R2 as secondary when idle. This balances load. Additionally, set Process A's schedule to run every hour with a timeout of 50 minutes; if not started within 10 minutes, trigger an alert. For Process B, allow it to run on any resource but with lower priority. This ensures Process A has redundancy and Process B utilizes idle capacity.
2. What governance measures would you put in place to monitor and maintain this setup?
Read the worked answer
Implement monitoring dashboards in Blue Prism Control Room to track process status, resource utilization, and SLA adherence. Set up alerts for when Process A fails to start or complete within its window, and when resources are down. Use Blue Prism's built-in reporting or export logs to a central system. Establish a change management process for schedule modifications, requiring approval. Conduct regular reviews of resource capacity and adjust schedules as needed. Also, implement a maintenance calendar to avoid scheduling conflicts during resource downtime. Document the failover procedures and train operators. Finally, use Blue Prism's audit logs to track changes and ensure compliance.