CN-370000-CN335-T14.pdf

Florida Department of Environmental Protection

TASK ASSIGNMENT NOTIFICATION FORM

Required Signatures: Adobe Signature

FDEP Contract No.: Task Assignment No.: Owner’s Name: Project No.:

Project Location: Project Name:

Consultant Name:

Consultant Representative: Phone: Email:

FDEP Contract Manager: Phone: Email:

Description of Task:

Project Manager:

Schedule Start Date: Fixed Price Cost:

Completion Date: Cost Reimbursement not to exceed:

Total Task Amount:

Approval Signatures:

Budget Representative, FDEP Signature Date

Project Manager, FDEP Signature Date

Contract Manager, FDEP Signature Date

Consultant Signature Date

Contract Authority, FDEP Signature Date

Project # Grant # Org Code Cat/Year Fund Module Object Code EO Amount

29 digit FLAIR Code: Total:

CN335 TA14 FDEP-RCP R2236

FDEP Sea Level Impact Projection (SLIP)

Taylor Engineering, Inc.

Angela Schedel 904-256-1305 aschedel@taylorengineering.com

Jeffrey Whitfield or successor 850-245-2630 Jeffrey.Whitfield@FloridaDEP.gov

Restasking subtasks 6 and 7 from CNN335 TA10; subtask 6 was removed through CO1 due to limitations of the funding to support the task time frame and subtask 7 expired due to scheduling conflicts for meetings necessary to approve the deliverables. The retasking will allow for continuity of the SLIP Web application maintenance and hosting, per attached d d 9/15/2021 Whitney Gray, or successor

Upon execution $ 69,274.32 June 30, 2022

$ 69,274.32

Lisa Yarborough Lisa Yarborough Digitally signed by Lisa Yarborough Date: 2021.09.27 13:11:28 -04'00'

Whitney Gray

Jeffrey Whitfield

Angela Schedel

Alex Reed

R2236 37538010005 100593/00 000286 U1620 241000 AT $ 69,274.32

$ 69,274.3237101000286375004000010059300

Whitney Gray Digitally signed by Whitney Gray Date: 2021.09.27 13:56:23 -04'00'

Jeffrey Whitfield Digitally signed by Jeffrey Whitfield Date: 2021.09.27 14:41:45 -04'00'

Angela Schedel Digitally signed by Angela Schedel Date: 2021.09.27 15:11:57 -04'00'

Lisa Yarborough Digitally signed by Lisa Yarborough Date: 2021.09.27 15:53:31 -04'00'

10199 SO UT HS I DE BLVD , S U IT E 310 | J ACK SON V ILLE , FL 32 25 6 | TEL 904 . 73 1 .704 0

WWW .T AYLO RENG IN EER I N G.C OM

September 27, 2021

Jeffrey Whitfield Contract Manager Bureau of Design and Construction Florida Department of Environmental Protection 3900 Commonwealth Boulevard 260K, MS 520 Tallahassee, FL 32399

RE: FDEP Agreement Number CN335 TA10 Retask

Sea Level Impact Projection (SLIP) Study Website Design and Web Application Development

Dear Mr. Whitfield:

As requested by FDEP, Taylor Engineering is submitting a retask for the above-referenced project for tasks 6 and 7. Justification for the retask is as follows:

1. Task 6 was removed at FDEP’s request on June 14, 2021 via Change Order 1 due to limitations in FRCP’s funding beyond the fiscal year.

2. FDEP requested the task be submitted as a retask on August 25, 2021 in order for the SLIP Tool to be maintained and hosted by Taylor Engineering until FDEP OIT brings these duties in house.

3. Task 7 was unable to be completed by August 30, 2021 due to scheduling conflicts for a coordination meeting with OGC, OIT, ORCP, and Taylor Engineering.

Please let me know if you have any questions.

Sincerely, Angela Schedel, Ph.D., P.E.

Vice President, Community Resilience

SCOPE OF WORK

SEA LEVEL IMPACT PROJECTION (SLIP) STUDY

WEBSITE MAINTENANCE AND HOSTING AGREEMENT

Introduction:

Taylor Engineering (“Taylor”) will continue to maintain and host a map-based web application for the Florida Department of Environmental Protection (“Department”) in order to provide a SLIP study that meets the goals described in the Tasks below that was initially outlined in TA10 (executed 10/26/2020).

This will be an outward facing web application and will be hosted by Taylor after public launch. Taylor will retain and store all data collected thereby for the duration of the agreement. This Task Assignment incorporates by this reference all provisions of CN335, the contract under which it is issued. Except and only to the extent not irreconcilably inconsistent with the provisions below, all provisions thereof shall apply.

The following tasks comprise the scope:

Task 6a. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include providing new minor functionality improvements, creating/maintaining documentation, modifying verbiage on reports/screens, and other functions as requested.

Discretionary activities, as directed by Department staff, are available at a rate of $162.21 per hour (Senior Professional).

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to repair” limits stated in Attachment A if the issue is caused by the external data source.

Taylor shall select and contract with an internet service provider that meets the Department’s minimum standards for service as described in Attachment A. Taylor will coordinate and monitor web hosting services, as per Attachment A.

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright for the web application and its code as more specifically set forth in the licensing agreement.

Deliverables: Monthly maintenance report.

Documentation: Taylor will submit a monthly report noting web application maintenance actions taken and the number of hours worked.

Performance Standard: The Department’s Contract Manager will review the documentation to verify that the deliverables have been completed as described above.

Task 6a Performance Period: October 1, 2021 through October 31, 2021

Cost Not to Exceed:

Summary of Fees: Total Cost Not To Exceed: $5,695.24 per month

Payment will be made upon approval of deliverables for each subtask by the FDEP in the amount specified. (Please do not alter this language)

Subtask 6b. Maintain and Host SLIP Web Application

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to repair” limits stated in Attachment A if the issue is caused by the external data source.

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6b Performance Period: November 1, 2021 through November 30, 2021

Subtask 6c. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to repair” limits stated in Attachment A if the issue is caused by the external data source.

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6c Performance Period: December 1, 2021 through December 31, 2021 specified. (Please do not alter this language)

Subtask 6d. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to repair” limits stated in Attachment A if the issue is caused by the external data source.

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6d Performance Period: January 1, 2022 through January 31, 2022 specified. (Please do not alter this language)

Subtask 6e. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to repair” limits stated in Attachment A if the issue is caused by the external data source.

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6e Performance Period: February 1, 2022 through February 28, 2022 specified. (Please do not alter this language)

Subtask 6f. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to repair” limits stated in Attachment A if the issue is caused by the external data source.

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6f Performance Period: March 1, 2022 through March 31, 2022 specified. (Please do not alter this language)

Subtask 6g. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6g Performance Period: April 1, 2022 through April 30, 2022 specified. (Please do not alter this language)

Subtask 6h. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to repair” limits stated in Attachment A if the issue is caused by the external data source.

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6h Performance Period: May 1, 2022 through May 31, 2022 specified. (Please do not alter this language)

Subtask 6i. Maintain and Host SLIP Web Application

Description:

For the Performance Period noted below, Taylor will perform regular updates and maintenance on the SLIP web application, to ensure functionality and data connectivity between data sources.

The data sources which the SLIP web application uses will be updated on a quarterly basis. Once the web application is fully operational and accepted by the Department, Taylor will troubleshoot and remediate system issues as directed by the identified Department Administrators.

Maintenance activities may fall into these two (2) categories:

A. Corrective/Preventive: corrective maintenance addresses the repair of application defects to enable the application to provide the required functionality and service levels at the time Taylor began this engagement. Preventive maintenance refers to the modifications needed to prevent potential errors in a software product. Examples include: Inability to commit/insert data, miscellaneous software “bugs”, routine monitoring of batch processes, initiating/monitoring any scheduled data uploads into a Department or other data repository, and other functions as requested.

B. Discretionary: addresses minor modifications to the application. Examples include

Taylor does not guarantee the reliability of the servers on which live external data is hosted, such as NOAA, FEMA, USACE, or other authoritative source. Taylor will contact the external data source to correct issues in a timely manner, but cannot guarantee that the data connection will be resolved within the “time to

Taylor shall select and contract with an internet service provider that meets the Department’s minimum

Throughout the deployment of the SLIP web application, Taylor will hold, assert, and protect a copyright taken and the number of hours worked.

Task 6i Performance Period: June 1, 2022 through June 30, 2022

Task 7. Provide Analysis, Design, and Technical Documentation for the SLIP Web Application Service

This documentation provides the necessary information for the department to re-engineer the

SLIP Web Application Service into a Department-supportable platform. This documentation should include, at a minimum:

1. A general description of the application including documentation of all modules/components.

2. Detailed documentation of all interfaces/interactions with other systems including data layers, data feeds and third-party tools along with associated metadata and any licensing requirements.

3. Business Process Map and Data Flow Diagram.

4. Logical Data Model and Data Dictionary including field and table definitions.

5. By means of text, screenshots, and screen navigation details, description of each screen, each e- mail template, and each report with supporting business rules including field and screen-level data validations.

6. Definition in detail all user roles and security privileges.

7. System architecture diagram – logical and physical.

8. Fully commented source code.

9. Assert and protect a copyright to the Webpage created and assign rights to the Department in accordance with the provisions of the licensing agreement.

Deliverables: Technical system documentation, licensing agreement.

DOCUMENTATION:

1. System documentation as described above

2. Licensing agreement (perpetual, royalty free) allowing for the Department’s use in conjunction with the SLIP webpage and modification of the SLIP Web Application as needed to allow modification or re-platforming, and migration from public hosting to Department or other governmental hosting, as specified in Attachment B.

3. Documentation of the submitted copyright for recordation and registration of the transfer of the copyright from Taylor to the Department with the United States Copyright Office.

4. Department’s approval of performance metrics recommended by Taylor

Performance Standard: The Department’s Contract Manager will review the documentation to verify that the deliverables have been completed as described above.

Upon review and written acceptance by the Department’s Contract Manager, Taylor may proceed with payment request submittal.

Task 7 Due Date: October 15, 2021

FIXED PRICE COST:

TASK 7: Provide Analysis, Design, and Technical Documentation for the SLIP Web Application Service Position Hourly Rate ($) Hours Cost ($) Task Totals Principal 200.94 2.0 401.88

Director 178.02 8.0 1,424.16

Senior Professional 162.21 80.0 12,976.80

Administrative 53.58 4.0 214.32

Total Man-Hours 94.0

Labor Cost 15,017.16

Reimbursable Costs Units Cost ($)

Licensing Agreement Fees 1.0 3,000.00

Total Non-Labor Cost 3,000.00

Total Task 7 $ 18,017.16

Attachment A Hosting, Backup, Security and Service Level Agreement (SLA)

Hosting: The web application will be provided using a high availability cloud-based hosting service.

Performance: Performance will be assessed at the end of each calendar month. If the site does not perform at an acceptable level, a 15% service credit for the month will be applied. The website performance will be deemed acceptable by either:

a) Fulfilling the SLIP Tool’s performance metrics as defined by the Department for each of the website’s functions or, in the event these metrics are not all fulfilled

b) The Department deeming the site’s performance as acceptable

Backups:

1. System snapshots will occur on a daily basis and will be stored at an offsite location.

2. Data backups will occur at the end of the business day and will be stored at an offsite location.

Backup frequency may be increased to as often as every four hours if requested by the department.

3. Retrieval of System or Data backups shall be provided to Department upon request.

4. An export of (or access to) the source code and spatial data shall be provided to the Department on at least a quarterly basis using an agreed upon file location.

Recovery: In the event of a catastrophic failure or major outage, the System will be recovered to a fully functional state and available to the public within 24 hours. Service disruptions during failover to disaster recovery sites and the period of time before those sites are brought up will be counted as downtime.

Availability: Software service will be available twenty-four (24) hours per day, seven (7) days a week, exclusive of scheduled maintenance periods. Unscheduled outages (i.e., any issue that causes the system to fail to perform one or more of its primary functions) may not exceed 4 hours cumulative in a month.

System Availability SLA: Service will maintain at least a 99.5% System Availability Percentage during each Month for the production version of the service. Should outages cumulate in excess of 4 hours within a calendar month, a 5% service credit will be applied, and additional 5% service credits applied every 30 minutes thereafter (not to exceed 100%). Service availability, however, does not include regularly scheduled maintenance or any unscheduled downtime due to failures beyond Contractor’s reasonable control (such as errors or malfunctions due to the Department’s computer systems, or the public user’s local hardware/Internet connectivity).

Maintenance: A weekly routine maintenance window for software, data and service updates will be designated during the period between 12 midnight and 3 AM EST, on a Wednesday. During this time, the system may be temporarily unavailable. Department will be provided at least five (5) days’ notice in order to accommodate any longer or different maintenance windows.

Security:

Services will be provided to the public jurisdiction and its end users solely from data centers in the United States (U.S.). Storage of public jurisdiction data at rest shall be located solely in data centers in the U.S.

Support: Service support representative(s) will be available to respond to Department support requests by phone or e-mail to John Messer or designee in the Taylor development team during the hours of 8 am through 4 pm Eastern Standard Time, Monday through Friday, excluding holidays observed by the Department. Only Department service administrators are authorized to submit service requests to Contractor. Department service administrators will review all lower level requests first to determine the need to escalate to the Taylor Engineering Technology Services support team as a Priority 1, 2, or 3 request.

Response and Resolution: Any error reported by DEP will be corrected in accordance with the priority level as defined below:

Priority Category Definition

Priority 1 An error that renders the software service inoperative or causes the software/service to be unavailable or unusable.

Priority 2

An error other than a Priority 1 error that results in the loss of any major or significant feature or functionality of the software service or significant degradation of the performance of the software/service or that significantly restricts Department’s use of the software service.

Priority 3 An error other than a Priority 1 or 2 error that results in the loss of a less significant feature or functionality of the software/service.

Response and Resolution SLAs:

Priority

Time to Respond (within support hours)

Time to Repair* Financial Consequences for Unsatisfactory Performance

1 4 hours Up to 1 calendar day

3.33% monthly service credit after day 1 and an additional 3.33% per day until 100% monthly service credit is reached or issue is resolved.

2 1 business day Up to 5 calendar days

2% monthly service credit after day 5 and an additional 2% per day until 100% monthly service credit is reached or issue is resolved.

3 2 business days

As scheduled for correction & implementation and communicated to/approved by Department

Failure to meet the Time to Respond (2 business days) and/or Time to Repair requirements as agreed to in writing by Department more than two times in succession during any month, the next payment for the ongoing service will be reduced by 5%.

*Repair means to correct the error or provide a reasonable work-around solution that produces the desired result and is mutually agreed to in writing with Department.

Force Majeure: Support disruptions due to events beyond the Contractor’s control, such as weather events, fires, or other major disruptive events that are beyond the Contractor’s control and affect the ability to provide the support outlined in this document will be excluded from the Response and Resolution SLAs.

Termination: Upon Department’s request and at no additional cost to the Department, John Messer or the current Director of Technology Services at Taylor Engineering will provide an accurate copy of all

Department data in an industry-standard machine-readable format along with adequate documentation to transfer data into a new solution (such as data dictionaries, field definitions, catalogs, and indexes).