17-Appendix O – Business Continuity-Disaster Recovery Plan.pdf

Appendix O – Business Continuity/Disaster Recovery Plan

Business Continuity/Disaster Recovery Plan

The primary objective of the City Disaster Recovery Program is to enable the organization to survive a Service Interruption, natural or manmade, and to reestablish normal business operations in a reasonable timeframe. ITS, as the centralized manager of IT, must assure that critical operations can resume normal processing within a reasonable time frame. To this end, the main goals of the ITS Disaster Recovery Program are: 1) Identify risk and weaknesses developing solutions to mitigate those risk and weaknesses; 2) Assist in the reduction of complexity of the recovery effort; 3) Facilitate effective coordination of IT recovery task; and 4) Minimize the duration of a disruption to business operations.

The City supports operations through a mixture of On Premise, Hosted, Hybrid, Infrastructure as a Service (IaaS) and Software as a Service (SaaS). Regardless of delivery mechanism, the Proposer must identify and propose how City Business Continuity (including data backups) and Disaster Recovery goals are to be supported by the proposed solution. The City has an annual Disaster Recovery Test requirement. Please provide content that details how the testing can be accomplished in your solution.

The City has local, county, state, and federal government data retention requirements, that impact business continuity, for various types of data the City captures and maintains. The Proposer should provide the Disaster Recovery Strategy. Please provide the Standard Disaster Recovery Procedures including the Response Phase, Resumption Phase, Escalation and Internal or External Dependency Recovery. Please included the proposed landscape design and any other supporting network mapping or applicable API design.

The City owns and maintains its data and all proposed solutions (including SaaS) must identify and propose how City data will be supported for Business Continuity and Disaster Recovery operations. The Proposer should identify how data retention is accomplished for a proposed solution based upon the data types and required retention schedules identified in the functional requirements for this procurement opportunity. If such information is not identified within the functional requirements of this document, the Proposer must identify data types and relevant data retention requirements and include methods of recovering this data to support business continuity and disaster recovery operations of the City.

As stated, the City owns its data and at the termination of any solution shall be required to preserve data retention. Especially for externally hosted solution the proposal would need to include consideration for return of the data for the City to maintain those internal and external retention requirements. The proposal should include a detailed method and explanation of how data reclamation or migration would occur. Also, please include the timeframe and methodology the proposed solution would include to support that recovery.

In addition, the City may be required by internal requirements and external regulations to audit controls and standards. The proposal should allow such measures that may be required for all types of operations, including Hosted, Hybrid, IaaS, and SaaS solutions. The Proposer should provide details of any limitations concerning the City’s ability to conduct audits or assessments.