1. Receive Ticket from ServiceNow
- Description: The deployment process begins when a developer registers a request for deployment in the incident management system (ServiceNow/any other System).
- Process:
- The Deployment Manager is automatically notified of the new request.
- All relevant information about the request, including the nature of the automation, target business processes, and intended impact, is documented within the ticket for reference.
- Objective: Ensure that all deployment requests are tracked and managed systematically to facilitate an organized deployment workflow.
2. Verify Release Package
- Description: The Deployment Manager reviews the release package submitted by the developer.
- Process:
- Check for Fraudulent Scripts: Conduct a security review to ensure the script does not contain unauthorized changes or malicious code.
- Documentation Review: Verify that all necessary documentation (e.g., Process Definition Document (PDD), Solution Design Document (SDD), testing results) is included and accurate.
- Objective: Confirm that the release package is complete and secure, preventing any potential issues during deployment.
3. Create Release Schedule
- Description: The Deployment Manager collaborates with the Workforce Planner to establish a detailed release schedule.
- Process:
- Determine the optimal timing for the release based on business operations and resource availability.
- Identify the required resources for the release and the subsequent hypercare phase, which includes support personnel, monitoring tools, and backup plans.
- Objective: Create a structured and realistic timeline that accounts for all necessary preparations and resources needed for a successful deployment.
4. Review and Provide Input to the Release Schedule
- Description: The Process Manager reviews the proposed release schedule to ensure business alignment.
- Process:
- Business Compatibility Check: Validate that the timing of the release does not conflict with critical business operations or other scheduled automation deployments.
- Resource Coordination: The Workforce Planner ensures that the proposed schedule aligns with other automation releases to optimize resource allocation and avoid conflicts.
- Objective: Ensure that the release schedule is practical and aligned with business needs and operational capacity.
5. Review and Approve Release Schedule
- Description: The Robotics Change Advisory Board (CAB) conducts a formal review and approval of the release schedule.
- Process:
- Present the release schedule, including rationale and potential impacts, to the CAB.
- Address any concerns or questions raised by CAB members during the review process.
- Objective: Obtain necessary governance approval to proceed with the deployment, ensuring compliance with organizational standards.
6. Review Release Schedule (IT CAB)
- Description: The IT Change Advisory Board (CAB) performs a final review of the release schedule before approval in the deployment system (Ivanti).
- Process:
- Confirm that all technical dependencies and impacts on existing systems have been considered.
- Provide feedback or required changes, if necessary, before final approval.
- Objective: Ensure that the technical implications of the release are thoroughly vetted and approved.
7. Approve in Service Now/ any other System
- Description: Once the release schedule has been reviewed and approved by the CABs, it is formally approved in the Service Now/ any other system.
- Process:
- The Deployment Manager updates the release status in Service Now/ any other System to reflect approval and readiness for deployment.
- Objective: Officially document the approval and allow the deployment process to proceed.
8. Inform Process Controllers and Managers
- Description: The Deployment Manager communicates the release schedule to key stakeholders.
- Process:
- Notify Process Managers about the upcoming release, including specifics about the deployment timing and any required preparations.
- Ensure that a Process Controller is appointed and made aware of their role and responsibilities during the go-live phase.
- Objective: Ensure all relevant personnel are informed and prepared for the upcoming deployment.
9. Automation Already Running in Production
- Description: Assess whether the deployment involves changes to an existing automation.
- Process:
- If the deployment modifies an existing automation, inform the Workforce Planner to halt the current process temporarily to facilitate the update.
- Objective: Prevent conflicts and ensure that changes can be applied without disrupting ongoing operations.
10. Import to Production Database
- Description: The Deployment Manager imports the approved script into the production database.
- Process:
- Conduct the import operation while ensuring that all security protocols are followed.
- The Deployment Manager should not be a developer to maintain segregation of duties and ensure compliance.
- Objective: Safely deploy the automation script into the production environment.
11. Start Automation
- Description: Initiate the newly deployed automation in the production environment.
- Process:
- Monitor the initial execution of the automation closely to ensure that it functions as expected.
- Objective: Ensure a smooth transition into live operation with minimal disruptions.
12. Run Hypercare Procedure
- Description: Implement the hypercare support process following the release.
- Process:
- Monitor the automation continuously for the first few weeks after deployment, depending on the complexity of the script.
- Address any bugs or performance issues promptly as they arise.
- Objective: Quickly identify and resolve any post-deployment issues to ensure stability and performance.
13. Go to Value Tracking Process
- Description: After the hypercare period, transition to a value tracking process to evaluate the effectiveness of the automation.
- Process:
- Measure key performance indicators (KPIs) related to cost savings, efficiency gains, and user satisfaction.
- Gather feedback from business users to assess the impact of the automation on their processes.
- Objective: Capture the value generated by the automation and identify opportunities for further improvement.
14. Automation Deployed into Production
- Description: Officially mark the automation as fully deployed and operational in the production environment.
- Process:
- Ensure all documentation is updated to reflect the successful deployment.
- Conduct a final review of the deployment process and any incidents encountered during hypercare.
- Objective: Complete the release process and confirm that the automation is delivering expected business outcomes.
Conclusion
This Release Plan provides a structured approach to deploying Intelligent Automation solutions. By following these detailed steps, organizations can ensure that each deployment is well-managed, thoroughly vetted, and capable of delivering the expected value while minimizing risks and disruptions. Each stage emphasizes collaboration among stakeholders, compliance with governance protocols, and a focus on continuous improvement.