Role definition for the Blue Prism Junior Process Developer role and the responsibilities

This is a document that underpins the key roles and the responsibilities within an enterprise strength Robotic Operating Model.

This template is a way of tracking all the Business Objects within the environment and should feed into the Design Authority sessions to ensure objects are not being overwritten, duplicated or amended with out authorization.

This is a peer review checklist that can be used for reviewing processes and objects against the best practices. The checklist provides the Blue Prism best practices and can be adapted to your own best practices and standards to help ensuring the solutions comply

This template is a way of tracking all the Processes within the environment and should feed into the Design Authority sessions to ensure process are not duplicated or amended with out authorization.

This document describes in detail a single Blue Prism Business Object, including all the actions in the object and all the inputs and outputs to those actions

This document describes in detail the impact on the Operation from the delivery of the automated solution. This document is intended for the client’s project delivery team to ensure that all components of the required operational architecture are in place. In signing off this document, the business will be acknowledging and agreeing to the retention of some resource to support the solution.

This Operational Contingency Plan describes the procedures and controls in the event of an automated solution being unable to meet its agreed Service Level Agreements (SLAs).

This document is to give instruction, information and advice of the running of a Blue Prism automated process in a normal daily operational environment