Please re-phrase the below document:

We have met with necessary leaders and stakeholders, training and educating them as we have progressed through this long and arduous process. Through painful planning and coordination, we have decided it best for your hospital organization to come online in a staggered approach. Prior to changing ISPs, Operations for the installation site will cease and all backups will be performed, completed, and verified. This will ensure that in the event of any possible failures, data will not be lost. Once the new ISP connection is online and running, all devices will have been tested locally before all external network pings have been sent to our site to validate the network, an additional backup will be performed as a redundancy.

When this plan is implemented, we will have teams on location(s) and in place to facilitate this migration of services and any issues that may occur during the transition of services.

Mitigation Plans if issues arise (What If's):

1. What if the network connection to MAI fails?

MAI will be allowed for a period of 6 hours, before existing ISP will be reconnected for continued service purposes until MAI issue(s) are resolved.

1. What network connection is a success, but local client machines are unable to exchange data with MAI as expected?

MAI will assist/train local network support on necessary steps to take to remedy this problem.

1. What if network equipment failed during network connection to MAI?

MAI will have secondary standby equipment on hand at the local site, with a cloned configuration or primary installed equipment.

** All other situations will be addressed and briefed to those affected as needed and required.

RTOs/RPOs

System data must be backed up regularly, as mentioned in our RFP presentation, incremental backups will be performed daily, and full backups will be performed weekly. The IT contingency plan will be made up of a notification phase, a recovery phase, and a reconstitution phase.

1. Notification: Includes procedures for notification, a damage assessment, and criteria-based activation. A notification will be issued to all essential personnel that details the magnitude of data loss/damage, as well as the scope of replacement/repairs/efforts needed for recovery.
2. Recovery: The sequence of recovery events, activities, and procedures. Whether it be a full restore or a single server/hard drive, etc. (Stored data should be routinely tested to validate integrity)
3. Reconstitution: Restoration of the original site, systems tests, and termination of recovery operations.

Planning, training, and running of exercises will be the key to the efficiency of the contingency plan. Efforts to restore this network will require cross-team coordination and communication. Exercises can be rehearsed in a classroom setting by discussing each specific component of the plan, and by simulating the replacement of equipment and data.

Recovery Time Objective (RTO) = 1 hour max

Recovery Point of Objective (RPO) = Most recent backup (0.5 hour for critical data)

**Time starts up receipt of call or trouble ticket