The Process Controller is a fundamental operational role within the Blue Prism Robotic Operating Model (ROM). This role is responsible for the day-to-day management, monitoring, and administration of the Digital Workforce in the live production environment. Key responsibilities include scheduling processes, managing work queues, monitoring the health of runtime resources, and performing initial investigation of process exceptions. The Process Controller acts as the primary human supervisor for the operational digital workers, ensuring that automated processes are executed efficiently and according to the defined schedule, thereby maintaining business continuity.

A. This describes a strategic leadership role, such as the Head of the Robotic Centre of Excellence (CoE) or an RPA Program Manager, who oversees the establishment of the entire RPA capability.

B. This is the responsibility of an RPA Manager or Head of Delivery. Their focus is on managing the human team members involved in the development and support lifecycle, not the live processes.

D. This describes the role of a Project Manager or Delivery Lead, who is accountable for managing the end-to-end delivery of a specific automation project according to a defined methodology.

1. Blue Prism University, ARA02 Courseware, Module: Roles and Responsibilities. The official course material explicitly defines the Process Controller role as being responsible for the "management and monitoring of the Digital Workforce in the production environment," which includes scheduling, queue management, and exception handling.

2. Blue Prism, "Robotic Operating Model (ROM) - Roles and Responsibilities Overview" Guide, Version 2.1, Page 11, Section: "Process Controller". This official document states, "The Process Controller is responsible for managing the Blue Prism production environment. This includes the scheduling of Blue Prism processes, managing the session allocation and monitoring the Digital Workforce." This directly supports the function of controlling and administering operational processes.

3. Blue Prism, "Blue Prism - The Robotic Operating Model (v6)," Document, Section 4.3: "Roles and Responsibilities". This foundational document details the operational nature of the Process Controller, distinguishing it clearly from delivery-focused roles (like Project Manager) and team management roles (like RPA Manager). It places the Process Controller squarely within the "Run/Maintain" phase of the automation lifecycle.

Process Inventory Management, often referred to as Opportunity Pipeline Management within the Blue Prism Robotic Operating Model (ROM), is the systematic framework for handling automation opportunities. It involves creating the necessary infrastructure—including governance, assessment criteria, and tools—to effectively manage the lifecycle of these opportunities from identification to implementation (B). A critical function of this managed inventory is to act as the central data source or platform for tracking progress, reporting on the pipeline's health, and communicating the value and benefits realized from the automation program to stakeholders (D).

A. This describes process discovery, which is the initial step that feeds opportunities into the inventory, rather than the ongoing management of the inventory itself.

C. Establishing a process mining approach is a specific technique for process discovery. It is a potential source for the inventory, not the management framework for the entire inventory.

1. Blue Prism. (2022). Robotic Operating Model (ROM) - Delivery Methodology.

Section 4.2, "Opportunity Pipeline": This section details the mechanism for identifying, validating, qualifying, and prioritizing automation opportunities. It states, "The opportunity pipeline is the mechanism through which opportunities for automation are identified, validated, qualified and prioritized ahead of being delivered." This supports option B by describing the infrastructure and process for managing opportunities.

Section 4.2.5, "Prioritize": This part of the document emphasizes that the pipeline provides the basis for making decisions and reporting. It notes the importance of a "consistent scoring mechanism" and regular reviews, which are foundational to reporting and communicating value, thus supporting option D.

2. Blue Prism University. (2022). ARA02 - Blue Prism ROM Architect Courseware.

Module: "Delivery Methodology": The courseware explains that the opportunity pipeline (process inventory) is not just a list but a managed entity. It requires a defined process (infrastructure) for assessment and prioritization. It also serves as the primary tool for the Head of RPA to report on the program's progress and potential ROI to the business, directly aligning with options B and D.

An RPA Governance Board (often part of a Centre of Excellence or a Design Authority) is primarily focused on the strategic, technical, and operational oversight of the automation program. Its core members typically represent the key functions required for successful delivery. This includes Business Representatives who own the processes and pipeline, IT Representatives who manage infrastructure and security, and the Head of RPA who leads the program. While Human Resources (HR) is a vital stakeholder in the broader change management and workforce transformation aspects of automation, they are not typically a standing member of the core governance board that makes decisions on technical standards, architecture, and pipeline prioritization.

A. IT Representatives are essential for ensuring automations comply with security, infrastructure, and architectural standards, making them a mandatory member.

C. Business Representatives are crucial as they own the processes being automated, provide subject matter expertise, and help prioritize the automation pipeline.

D. The Head of RPA is the leader of the automation program and is central to the governance function, often chairing the board or committee.

1. Blue Prism, "Robotic Operating Model (ROM) - Overview". The official Blue Prism ROM documentation consistently describes the core governance structure as a partnership between the Business, IT, and the RPA Centre of Excellence (CoE). The Design Authority, a key governance body, is composed of technical and business leads. HR's involvement is framed within the "People" and "Change Management" components of the operating model, which is adjacent to, but distinct from, the core governance board. (Accessed via Blue Prism University/Portal).

2. Blue Prism University, "ARA02 - Blue Prism Certified Developer" Courseware. The module on the Robotic Operating Model (ROM) details the composition of governance forums like the Design Authority. It specifies that typical attendees include the Head of RPA, Enterprise Architect (IT), IT Security, and Business Process Owners. This composition underscores the focus on technical, security, and business process alignment, distinguishing it from workforce management functions handled by HR.

The People foundation within the Blue Prism Robotic Operating Model (ROM) is centered on establishing the organizational structure, roles, and responsibilities required to support and scale the Digital Workforce. It involves defining the skills and capabilities needed for the team that will design, build, deploy, and manage the automation solutions. This ensures that the right individuals are in place to govern and operate the RPA capability effectively, forming the core of the Center of Excellence (CoE).

A. This describes the Delivery Methodology foundation, which focuses on the lifecycle and standards for creating and deploying automations.

B. This relates to the Vision and Opportunity Assessment components of the ROM, which establish the strategic goals and identify suitable processes for automation.

C. This describes the Technology foundation, which deals with the IT infrastructure, architecture, and technical environment for the Blue Prism platform.

1. Blue Prism. (2022). Robotic Operating Model (ROM) - An Introduction. Blue Prism Portal Document. In the section "The Foundations of a Successful Digital Workforce," the 'People' foundation is described as: "Defining the roles and responsibilities required to deliver and maintain the Digital Workforce." This directly supports option D.

2. Blue Prism. (2022). Blue Prism Robotic Operating Model (ROM) v2 - Vision and Organization. Blue Prism Portal Document. This document details the 'People' aspect, covering Organization Design, Roles and Responsibilities, and Training, all of which are encompassed by "Defining the skills and responsibilities to build, manage and run the Digital Workforce."

The primary objective of a Blue Prism Developer is to design, develop, and test automation solutions according to the standards and best practices defined within the Robotic Operating Model (ROM). This role is responsible for configuring robust and efficient process automations based on the Process Definition Document (PDD) and Solution Design Document (SDD). The developer also provides ongoing support for the deployed solutions, particularly during the initial hypercare period and for subsequent defect resolution, ensuring the delivered automation meets the business requirements.

A. This describes the primary responsibilities of a Process Analyst, who identifies opportunities and creates the Process Definition Document (PDD).

C. This is a strategic management responsibility, typically belonging to the Head of RPA or an RPA Manager, overseeing the entire capability setup.

D. This describes the role of an RPA Manager or Delivery Lead, who is responsible for managing the team and overseeing the delivery lifecycle.

1. Blue Prism. (2021). Blue Prism Robotic Operating Model (ROM) v2. Section 4.2, 'The Roles', The Developer. This section explicitly states, "The Developer is responsible for designing, developing and testing the automation workflows and supporting the implementation of the Blue Prism solution."

2. Blue Prism. (n.d.). Roles and Responsibilities. Page 7, 'Developer'. This document outlines the developer's key responsibilities as: "Designing Blue Prism process solutions in accordance with standard Blue Prism design principles and conventions," "Configuring new Blue Prism processes and objects," and "Supporting the operational teams during the UAT and roll-out phases."