dSeries End-of-Service Approaching

First, we’ll assess your current state, processes, and requirements. Then we’ll provide strategic recommendations and a co-created upgrade roadmap. The roadmap is typically followed by a 2-month (estimated) engagement encompassing   

• Implementation and deployment support 
• Testing and validation of the new deployment   
• Training and Support to empower your application teams in effective utilization of the solution’s new features 
• Migration of workload artifacts 
• Champaign toast with possible happy hour to follow  

dSeries upgrades should ideally be scheduled several weeks to a few months in advance, depending on the complexity of the upgrade, the criticality of the systems involved, and the potential impact on business operations.

We want you to start early enough to complete the upgrade before End of Service hits.

This time frame allows for thorough planning, risk assessment, creation of backup systems, comprehensive testing, and communication with all stakeholders to ensure minimal disruption.

It also provides sufficient time to train resources on new features and changes, align resources, and address any potential issues that may arise during the preparation phase.

The cost of upgrading dSeries Workload Automation can vary widely depending on several factors:

1. License Type and Volume: If additional licenses are needed, or if existing licenses need to be upgraded, this can affect the cost.
2. Current Version and Target Version: The complexity of the upgrade path (e.g., upgrading several versions at once vs. a single version upgrade) can impact the amount of work required.
3. Customizations and Integrations: If your current setup involves extensive customizations or integrations with other systems, adapting these to the new version can add to the scope.
4. Training and Support: Training your team on the new features and ongoing support options are common requirements.
5. Agents: Upgrading or adding new agents that facilitate the automation tasks across different environments and platforms may also affect the overall scope. 

It’s best to start with a feasibility call with RMT for an accurate estimate based on your specific requirements and circumstances.

Over the last twenty-five years, we’ve accumulated an impressive 99.9% success rate on upgrades. So you can rest easy.

In the unlikely event we lose cabin pressure (yes, it’s that rare), the following steps will oxygenate your system:

1. Immediate Troubleshooting: The team would quickly diagnose the issue to understand the root cause and begin resolving it promptly.

2. Rollback Plan: Yes, a pre-defined rollback is always available, but it’s usually less cumbersome to fix the issue and move forward. If activating a rollback is necessary, this involves reverting to the previous stable version of the system to ensure continued business operations while the issue is addressed.

3. Incident Reporting: An incident report would be created, detailing what went wrong, why, and the impact. This transparency helps in learning from the event and avoiding similar issues in the future.

4. Communication: Regular updates would be communicated to all stakeholders throughout the process to maintain transparency and manage expectations.

5. Review and Analysis: After resolving the issue, a thorough review would be conducted to analyze the cause and refine future upgrade processes based on learned insights.

6. Support: Support would be provided following the incident to ensure the system remains stable and to quickly address any subsequent minor issues.

With a high success rate and these robust mitigation strategies in place, we ensure potential disruptions are minimized and swiftly managed, which is why our clients trust and rely on our upgrade services. 

Workload Automation is all we do. And we do it well.