Line 68: |
Line 68: |
| | | |
| ===Next Steps=== | | ===Next Steps=== |
| + | •Engaging IT resources to implement and support RPA software implementation: |
| + | |
| + | •Cloud intake |
| + | |
| + | •Security for RPA licenses |
| + | |
| + | •Accessibility verification |
| + | |
| + | •Governance and approvals |
| + | |
| + | •Establish a Center of Expertise, starting with ROEB and expanding to other programs areas : |
| + | |
| + | •Intake process (e.g. use cases) / RPA guidelines and guardrails - Done |
| + | |
| + | •Governance and prioritization |
| + | |
| + | •Security for each RPA architecture pattern |
| + | |
| + | •Change management |
| + | |
| + | •Training |
| + | |
| + | •Release management |
| + | |
| + | •Resourcing |
| + | |
| + | •Terms of Reference - Done |
| + | |
| + | • |
| + | |
| + | •Implement RPA technology within selected business use cases |
| + | |
| + | •Will require support and engagement from program SMEs and process owners |
| + | |
| + | •Intake form was the first step that will lead the discovery phase, and subsequent planning |
| + | |
| + | •First process to automate will be ALR |