| Line 48: | Line 48: | 
|  |  |  |  | 
|  | ====Build, Test and Implement==== |  | ====Build, Test and Implement==== | 
|  | + | The following table shows the process of building, testing and implementing RPA. | 
|  | + | {| class="wikitable" | 
|  | + | |+ | 
|  | + | ! | 
|  | + | !Deliverables | 
|  | + | |- | 
|  | + | |Prepare RPA  | 
|  | + |  | 
|  | + | * One-time setup activities  | 
|  | + |  | 
|  | + | * Set up infrastructure  | 
|  | + | * Design server architecture  | 
|  | + | * Install & configure product and applicable applications  | 
|  | + | * Gain access to all needed applications and systems   | 
|  | + | * Develop solution & test environments  | 
|  | + |  | 
|  | + | * Select process based on pipeline management  | 
|  | + | | | 
|  | + | * Automation Pipeline updates  | 
|  | + | * Infrastructure Diagrams   | 
|  | + | * Security Assessment/ATO | 
|  | + | |- | 
|  | + | |Solution Analysis and Design   | 
|  | + |  | 
|  | + | * Document and re-engineer processes  | 
|  | + | * Complete Process Definition Document (PDD)  | 
|  | + |  | 
|  | + | * Understand As-Is and document To-Be  | 
|  | + |  | 
|  | + | * Develop high level timeline  | 
|  | + | * Create test scenarios and start test plan  | 
|  | + | * Conduct infrastructure and security review  | 
|  | + | * Create the Solution Design Document (SDD)  | 
|  | + | | | 
|  | + | * Process Definition Document  | 
|  | + | * User Acceptance Testing Plan  | 
|  | + | * Solution Design Document  | 
|  | + | |- | 
|  | + | |Build RPA Solution  | 
|  | + |  | 
|  | + | * Develop automation for in-scope processes  | 
|  | + | * Build the robot core structure  | 
|  | + |  | 
|  | + | * Make process specific changes  | 
|  | + | * Build and integrate needed Queues  | 
|  | + |  | 
|  | + | * Develop reusable component library  | 
|  | + |  | 
|  | + | * Test existing custom Libraries  | 
|  | + | * Build new custom Libraries  | 
|  | + | * Unit testing for new custom Libraries  | 
|  | + |  | 
|  | + | * Develop workflows with application integration  | 
|  | + |  | 
|  | + | * Build GUI interaction actions  | 
|  | + | * Application state validation (start and end of workflows)  | 
|  | + |  | 
|  | + | * Develop validation workflows  | 
|  | + | * Integrate all workflows into final robot process  | 
|  | + |  | 
|  | + | * Check in and out arguments  | 
|  | + | * Add any required notifications and logging  | 
|  | + |  | 
|  | + | * Conduct unit and technical testing for queue processing, exception handling and workflows  | 
|  | + | * Create the Development Specifications Document (DSD)  | 
|  | + | * Prepare Test Data  | 
|  | + | * Execute code review using development best practices  | 
|  | + | | | 
|  | + | * Development Specifications Document  | 
|  | + | * Reusable Component Architecture  | 
|  | + | * Development Best Practices  | 
|  | + | * Standard Naming Conventions  | 
|  | + | * JIRA logs / Change Requests  | 
|  | + | |- | 
|  | + | |Test RPA Solution  | 
|  | + |  | 
|  | + | * Provide test plan  | 
|  | + | * Conduct User Acceptance Testing (UAT)  | 
|  | + | * Fix issues identified during UAT  | 
|  | + | * Report test results  | 
|  | + | * Signoff on production and Make Go/ No Go decision  | 
|  | + | | | 
|  | + | * User Acceptance Testing Plan  | 
|  | + | * Exception Management   | 
|  | + | * Production Release Document  | 
|  | + | * JIRA logs / Change Requests  | 
|  | + | |- | 
|  | + | |Stabilize RPA  | 
|  | + |  | 
|  | + | * Go Live   | 
|  | + | * Submit ATWS request for migration/deployment approval  | 
|  | + | * Perform Read Only testing in production  | 
|  | + |  | 
|  | + | * Run robot in READ ONLY mode to test selectors  | 
|  | + | * Update any selector changes  | 
|  | + | * Document & build any new exceptions  | 
|  | + | * Volume end to end testing (READ ONLY)  | 
|  | + | * Set up Schedule, Assets and Queues  | 
|  | + |  | 
|  | + | * Move robot to production  | 
|  | + |  | 
|  | + | * Set Config Run Mode to PROD  | 
|  | + | * Increment code versioning   | 
|  | + | * Save final code in control repository  | 
|  | + | * Publish production code in PROD Orchestrator  | 
|  | + | * Monitor execution  | 
|  | + | * Finalize DSD Documentation  | 
|  | + |  | 
|  | + | * Monitor robots in production  | 
|  | + | * Track and report on metrics and SLAs  | 
|  | + | * Document lessons learned  | 
|  | + | |JIRA logs / Change Requests  | 
|  | + | |- | 
|  | + | |Hypercare RPA  | 
|  | + |  | 
|  | + | * Conduct regular reviews and assessments  | 
|  | + | * Make changes to workflow and /or code based on Improvement opportunities   | 
|  | + | * Track benefit realization  | 
|  | + | * Enable Service model  | 
|  | + | | | 
|  | + | * Report on pre-defined metrics  | 
|  | + | * Operational Reports  | 
|  | + | * JIRA logs / Change Requests  | 
|  | + | |} | 
|  |  |  |  | 
|  | ====Monitoring, Maintenance and Support==== |  | ====Monitoring, Maintenance and Support==== |