According to the RFP, proposals should cover final user acceptance testing, MHS team training, support and comprehensive migration documentation.
Other requirements include:
- Migration planning: Develop a comprehensive plan for migrating the non-production Epic instance to Azure, including timelines, risk management and testing to address latency issues
- Ancillary application rationalization: Identify and rationalize non-Epic ancillary applications that need to migrate alongside Epic for both DR and non-production environments
- Collaboration with MHS: Work with MHS to estimate annual resource consumption in Azure and ensure their involvement in environment configuration and deployment templates
- Migration strategy execution: Execute the migration plan, implementing a failover process for seamless transitions between on-premises and Azure environments
- Testing and validation: Conduct rigorous testing to validate data integrity, application performance and system functionality in the Microsoft cloud environment