ATTA_1_-_CALFIRE_CATIS_SOW_IFB_0000032355.doc

DOC document 216 KB Posted

Attached to
CATIS Aviation Tracking (DGS-OTA)
Solicitation number
0000032355
Issued by
Sacramento County, San Francisco City, California

About this file

This document is a Statement of Work (SOW) for the California Department of Forestry and Fire Protection (CAL FIRE) to develop a new aviation tracking and information system called the CAL FIRE Aviation Tracking and Information System (CATIS). The project will encompass comprehensive development, testing, training, implementation, and ongoing support and maintenance for the new cloud-based software-as-a-service (SaaS) application. The system must integrate with all CAL FIRE applications and programs that track aviation information, and it will replace the existing Aviation Information Management System (AIMS). The system must be flexible, user-friendly, and capable of expanding to meet future needs, such as automatically integrating data from sensors and hardware installed on CAL FIRE aircraft, plotting georeferenced data on maps, and communicating with other CAL FIRE systems.

The contract will be for a three-year term, with the option to extend for two additional one-year terms. There are detailed requirements around security, accessibility, reporting, and training that the selected contractor must meet. The contractor will be responsible for providing experienced staff that meet mandatory staffing qualifications, as well as ongoing maintenance and support for the system. The contract is a fixed-price agreement, with the potential for work authorizations on a labor-hour basis for any additional work. Pricing details and cost estimates are provided in a separate Cost Worksheet attachment.

View the file

Other files

Show all 12

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

BU 3540 Event ID 0000032355 Attachment 1

STATEMENT OF WORK

This Statement of Work (SOW) is made between the California Department of Forestry and Fire Protection, hereinafter referred to as CAL FIRE, and (Contractor name), hereinafter referred to as Contractor. The Contractor will develop an application called CAL FIRE Aviation Tracking and Information System (CATIS). This application will be used by CAL FIRE to track aviation information related to aircraft flights, aviation contracts, and aviation personnel. The system must integrate with all CAL FIRE applications and programs that track, collect, store, and report various aviation information from all CAL FIRE owned and contracted aircraft. It will also record information for CAL FIRE pilots and crew members operating these aircraft, as outlined in this Statement of Work.

SCOPE

The Contractor will provide an application that meets CAL FIRE’s specification as shown in this SOW.

CAL FIRE requires a modern, easily accessible, and user-friendly program that can perform all the current functions of the Aviation Information Management System (AIMS), while also having the capacity for future expansion. This new system should automatically accept data from other CAL FIRE programs to reduce input errors, generate reports based on any combination of user-defined datasets, and produce real-time user-defined dashboards. To meet these needs, CAL FIRE is proposing the development of the CATIS. This initiative will encompass comprehensive development, testing, training, implementation, and ongoing support and maintenance for the new application, ensuring it can effectively manage and support CAL FIRE's expanding aviation operations.

New application must be capable of:

1. Performing all current functions of AIMS.

2. Automatically integrating data from other CAL FIRE programs.

3. Generating reports based on any combination of user-defined data sets.

4. Producing real-time, user-defined dashboards.

5. Expanding functionality to meet future needs.

PROJECT SUMMARY (BACKGROUND)

Since 2006, CAL FIRE has been tracking all of it aviation fleet, pilots, air crews, and some contract aircraft data using an internally developed software entitled AIMS. AIMS was developed in 2005 as an ASP.net application that uses an Oracle database for all of its stored data. AIMS currently tracks basic components of flights such as start time, end time, total flight time, pilot, and air crew time, etc. AIMS also can generate reports based on predetermined data sets, where the date, aircraft, and/or incident number are the only user selected parameters.

Since 2006, CAL FIRE has expanded its total number of aircraft, aviation contracts, missions, pilots, and air crew members that require tracking, thus requiring the AIMS program to track and report more data than originally designed. This sharp increase in data input and data tracked along with the laborious effort required to update the AIMS program to meet these needs has shown the need for a newly designed software program that can accomplish all these tasks and can expand for the future.

PERIOD OF PERFORMANCE

The term of this agreement will be for three (3) years to begin when the agreement has been signed by both Contractor and CAL FIRE, and a fully executed copy is sent to Contractor. Upon mutual consent of both parties the agreement can be extended for two (2) one (1) year terms. If project has software licensing, or Software-as-a-Service (SaaS), upon completion/implementation of the project, CAL FIRE will move forward on an annual software subscription renewal basis.

The Contractor shall not be authorized to deliver or commence performance of services as described in this SOW until written approval has been obtained from all entities. No delivery or performance of service may commence prior to the execution of the agreement.

TASKS TO BE ACCOMPLISHED/FUNCTIONS TO BE PERFORMED

This project will consist of two (2) phases: Development and Enhancements.

Phase I Development will comprise of the following:

1. Data Integration and Migration The application must have the capability to accept and retrieve information from other CAL FIRE software sources (e.g., CAD, IRWIN) and populate the required fields accordingly. CAL FIRE utilizes TracPlus for tracking all its aviation assets. The application must be able to pull all relevant data from TracPlus and input it into the application in near real-time. Contractor will migrate AIMS data into the new application.

If additional sensors and hardware are required to automatically pull data from CAL FIRE aircraft, the Contractor will provide detailed information on the necessary hardware for installation on the aircraft. CAL FIRE will have the final approval on which hardware is installed on their aircraft (e.g., oil pressure sensors, tank door sensors, landing gear pressure sensors, etc.).

2. Auto Population The application must be capable of filtering responses based on user selections through auto-populating fields and dropdown menus. When data entry cannot be automated through auto populated fields, manual keyboard entry should be used as a last resort.

3. Intuitive Layout & Design The application's layout, design, and functionality must be user-friendly and intuitive, ensuring that the average user can operate it effectively without extensive training. User actions should be intentionally grouped together, minimizing the need for users to shift their focus across different areas of the screen to complete tasks. Required user actions should be kept to a minimum, with most tasks completed through button clicks or selecting recommended responses.

4. Accessibility The application must be accessible internal on VPN and external to CAL FIRE’s firewall with an internet connection on desktops, laptops, tablets/iPads, and mobile devices, and must meet CAL FIRE’s security requirements.

5. Reports The application must have the capability to generate user-identified reports, which can be scheduled for a specific single date and time, set to recur (daily, weekly, monthly, etc.), or generated as a single user-identified report. These reports must be able to search and report on any combination of data sets within the application (Ad-hoc reporting).

Reports will be distributed to users in a format specified by the user, at a minimum either Microsoft Excel or Adobe PDF, allowing for easy printing if desired. The application must also provide the ability to email reports automatically or manually to a user-identified recipient without exiting the program.

6. Testing After initial development has been completed, user acceptance testing, and evaluation will occur. The Contractor will conduct a minimum of three (3) training sessions (offering virtual and in-person options) for individuals designated by CAL FIRE to assist users who are performing the test scripts. Additionally, the Contractor will offer ongoing technical support to CAL FIRE users throughout the testing period. CAL FIRE and Contractor will discuss the parameters of the testing and come to an agreement on what constitutes successful testing of the application.

7. Training Upon completion of Development and Testing, the Contractor will deliver the required training. Training sessions will encompass a minimum of three (3) sessions tailored to individual user roles. These sessions will be recorded and accessible to CAL FIRE personnel. The Contractor will conduct training sessions annually as needed or following significant updates. Following each updated training session, the Contractor will revise the recorded version accordingly.

The Contractor will furnish a comprehensive written training manual detailing all aspects of the application's functionality. This manual will be accessible and downloadable for all users. It will be updated concurrently with the addition of any new functionality.

8. Implementation CAL FIRE must conduct testing and acceptance of the application before the conclusion of Phase 1. Once CAL FIRE approves the completed application, CATIS will go live at a date and time specified by CAL FIRE, becoming the primary aviation information tracking system for CAL FIRE.

The Contractor is responsible for ongoing maintenance and updates to ensure that the CATIS application operates according to CAL FIRE's specifications for security, accessibility, speed, reliability, etc. Additionally, the Contractor will provide user support via a "Help Desk," accessible through email and phone. Help Desk assistance will be available 24 hours a day, seven days a week, from April 15th to October 31st each year, and during a “declared fire season”.

Phase II

Enhancements will comprise of the following:

1. Planned Expansion The CATIS application will have the capacity to expand for additional functions and technologies beyond those listed above. This expansion may involve incorporating additional functionalities such as:

a. Automatically fill any tracked data points with information sent via TracPlus from sensors/hardware installed on aircraft, should CAL FIRE install necessary hardware on aircraft.

b. The ability to plot all georeferenced data gathered from TracPlus on a map for visual reference. (Map data used in Situational Dashboards)

c. The ability to track air base data and display on a Situational Dashboard (vendor to provide a list of hardware needed to track these data points automatically):

d. Communicate with other CAL FIRE software:

e. Fill CAL FIRE 62 & 63 Forms with information from database when user requests.

f. Fill Aviation Cost Worksheet with information from database when user requests.

g. Create graphs and other visual representations of data from user requested reports.

h. Produce customizable “Situational Dashboards”.

High-level project requirements are prioritized as follows:

M (Mandatory) – An absolute essential feature; the project will be canceled if it is not included. This functionality is required by regulation.

R (Requested) – Features are not essential, but together they affect the viability of the project; additional functionality not specified by regulation; category of functionality that may be optional or a later system enhancement.

ID
Requirements Description
Priority

1.0 System Requirements (Phase I)

1.1
The system shall be a cloud-based Software as a Service (SAAS) system.
M
1.2
The system shall offer functionality to search, sort, and filter data.
M
1.3
The system must support a minimum of 200 concurrent users to meet business requirements and ensure optimal performance without delays.
M
1.4
The system shall have the ability to access information by roles and security privileges.
M
1.5
The system shall be flexible and allow for configurable data fields.
M
1.6
The system shall be flexible and allow for configurable workflow processes.
M
1.7
The system shall be flexible and allow for configurable business rules.
M
1.8
The system shall allow users to save partially completed records.
M
1.9
The system shall offer all current users the necessary system functionality and requirements stated in the SOW.
M
1.10
The system shall offer portal views of all authorized data based on the authenticated user role.
M
1.11
The system shall enable users to save, upload, and download artifacts in specified formats according to their roles. (i.e., fuel receipts, FC-36 and FC-106 Forms, and images)
M
1.12
The system shall enable flagging and retention of data that is subject to audit or litigation hold.
M
1.13
The system shall have the capabilities to upload file(s) and download data to be transmitted to other entities as may be required.
R
1.14
The selected Contractor shall provide support for the new system during the duration of the project.
M
1.15
The system shall provide users with read-only access to all data, based on pre-defined user roles.
M
1.16
The system shall allow for multiple tracking identifiers (Fixed Wing and Helicopter).
M
1.17
The system shall provide unlimited access to all data owned by CAL FIRE.
M
1.18
Contractor will adhere to CAL FIRE’s record retention policies and have all data available when requested.
R
1.19
The system shall support the latest version of Microsoft Edge.
M
1.20
The system shall have the ability to merge duplicate information from multiple records into a single record or link multiple records to a single record and produce an audit trail of the changes by authorized user (i.e., data cleanup).
M
1.21
The system should allow the creation of additional reports and notifications.
M
1.22
The system shall be flexible and allow for configurable automated alerts and notifications based on time frames and due dates.
M
1.23
The system shall be able to track both Active and Non-Active statuses of personnel, aircraft, or air base.
M
1.24
The system shall be capable of tracking the hours spent on flights.
M
1.25
The system shall be able to track days and hours worked by each personnel.
M
1.26
The system shall be able to track monetary cost for all flight information.
M
1.27
The system shall be able to track all flight information and time stamp the activity as well as who made any edits or changes.
M
1.28
The system shall allow for creating and printing an individual flight document.
M
1.29
The system shall allow for historical data conversion and migration from Aviation Information Management System (AIMS).
M
1.30
The system shall interface with email to send outbound emails.
R
1.31
The system shall be accessible through CAL FIRE’s internal VPN and external the firewall.
M
1.32
The system shall be accessible on multiple devices (desktops, laptops, tablets/iPads, and mobile devices).
M
1.33
The system shall have a configurable time out setting due to inactivity (20 mins).
R
1.34
The system shall be capable of tracking the quantities of retardant and water, in the aircraft tank, and the amount released.
M
1.35
The system shall include an option to track Unmanned Aerial Systems (UAS) owned and contracted by CAL FIRE.
R

2.0 Security Requirements

2.1
The system shall meet Federal and State laws, policies, and regulations for security, privacy and confidentiality of data as outlined in State of California Statewide Administrative Manual (SAM) 5300 and National Institute of Standards and Technology (NIST) SP 800-53 (rev 4).
M
2.2
The system shall support Federated Identity single sign-on security controls, two-factor authentication, and restricted access to specific screens, fields, and processes.
M
2.3
The system shall provide the ability to define and grant/revoke different levels of access to the system based on defined user roles.
M
2.4
The system shall provide the ability to track and report auditing, including the ability to track and monitor users access actions, changes, and modifications by date and time and make this information available to authorized user roles.
M
2.5
The system shall be configured using SAML/MFA with CAL FIRE Microsoft Azure Active Directory accounts.
M
2.6
The system shall create a user profile for all users capturing the following:

First Name, Last Name, Rank/Job Title, Agency, Contact email, Contact phone number, Aviation Role, and Assigned work location (Base).

M

2.7
The system shall provide a single, seamless user interface to access CAL FIRE data, based on authenticated user roles. (Administrator, Base Administrator, User, and Reports only)
M

3.0 Business Analytics and Reporting Requirements

3.1
The system shall allow for the creation of ad-hoc queries and reports. Generate ad-hoc reports and statistics (configurable automatically and manually) with the ability to add narrative to reports.
M
3.2
The system shall include about 35 predefined CAL FIRE standard reports.
M
3.3
The system shall provide the ability to create dashboards and reports with drilldowns.
M
3.4
The system shall have the ability to configure/customizable dashboards.
M
3.5
The system shall have the ability to review, edit, and track changes.
M

4.0 Interface Requirements

4.1
The system shall interface with Microsoft Outlook to send configurable emails/alerts to users.
R
4.2
The system shall sync with Microsoft Outlook and Teams.
R
4.3
The system shall interface with CAD, HEMS, IRWIN, and TracPlus.
M

5.0 Testing Requirements

5.1
The selected Contractor shall prepare a Requirements Traceability test plan for all implemented solution.
M
5.2
The selected Contractor shall prepare a User Acceptance Test Plan with input from CAL FIRE program staff.
M

6.0 Training Requirements

6.1
The selected Contractor shall prepare training plans for all user types and roles.
M
6.2
The selected Contractor shall prepare training materials and train all user types and roles.
M
6.3
The selected Contractor shall provide training on future system enhancements, updates, and changes.
M

7.0 System Requirements (Phase II Enhancements)

7.1
The system shall allow for the completion of CAL FIRE Form 62 & 63 from user request.
M
7.2
The system shall automatically populate any tracked data points with information sent via TracPlus from sensors and hardware installed on aircraft.
M
7.3
The system shall have the ability to plot all georeferenced data gathered from TracPlus on a map for visual reference. (Map data used in Situational Dashboards).
M
7.4
The system shall have the ability to track air base data and display on a Situational Dashboard.
M
7.5
The system shall populate the Aviation Cost Worksheet (Air Ops Worksheet) with information when user request.
M

8.0 Maintenance and Operation Requirements

8.1
The selected Contractor shall provide ongoing maintenance and operation for system updates, upgrades, or additions as needed.
M

CONTRACTOR PERSONNEL

The Contractor personnel shall meet all Mandatory Staffing Qualifications (MSQs) for the duration of the agreement term. The Contractor must ensure the provision and retention of experienced staff throughout the duration of the agreement.

1. Mandatory Staffing Qualifications All personnel listed in this agreement must meet the personnel Mandatory Qualifications for their appropriate role as outlined below. The Contractor shall provide experienced staff that meets all the MSQs listed below. All experience used to meet the MSQs shall have been where the Staff had primary responsibility. CAL FIRE anticipates using the following classifications throughout the term of this agreement:

Senior Project Manager

MSQ#
Mandatory Staffing Qualifications (MSQs)

Within the Last Ten (10) Years

1.
A minimum of seven (7) years of hands-on experience in Agile/Waterfall Project Management methodologies, including the ability to formulate project plans derived from the SOW. Proficient in leading meetings, establishing clear expectations for project teams, setting deadlines, and overseeing the achievement of CAL FIRE project objectives.
2.
Proficient in documenting best practices and processes, along with outstanding communication skills.
3.
PMP Certification is required.

Technical Architect

MSQ#
Mandatory Staffing Qualifications (MSQs)

Within the Last Ten (10) Years

1.
A minimum of eight (8) years of experience in systems development, analysis, programming, or testing.
2.
This classification requires the possession of a bachelor’s degree in an IT-related or Engineering field. Additional qualifying experience may be substituted for the required education on a year-for-year basis.

Technical Writer

MSQ#
Mandatory Staffing Qualifications (MSQs)

Within the Last Ten (10) Years

1.
A minimum of five (5) years of hands-on experience in technical roles within the government industry. Proficient in leading and managing technical teams, demonstrating strong leadership skills, expertise in designing, implementing, and maintaining complex technical solutions. In-depth knowledge of current industry trends, technologies, and best practices. Proven experience in coordinating and executing project plans, ensuring successful project delivery.
2.
Strong problem-solving and analytical skills, with the ability to troubleshoot technical issues effectively. Excellent communication and interpersonal skills, fostering collaboration within the team and with stakeholders.

Senior Software Engineer

MSQ#
Mandatory Staffing Qualifications (MSQs)

Within the Last Ten (10) Years

1.
At least seven (7) years of experience in electronic data processing systems study, design, and programming. At least four (4) years of that experience must have been in a lead capacity.
2.
At least three (3) years coding of multi-tier applications, including but not limited to responsive web application development and mobile application development and proficient in C#, ASP, Java, PowerShell, web service API, SOAP, and REST by using MVC and Angular design pattern.

Software Engineer

MSQ#
Mandatory Staffing Qualifications (MSQs)

Within the Last Ten (10) Years

1.
A minimum of five (5) years of experience in electronic data processing systems study, design, and programming. At least three (3) years of that experience must have been in a lead capacity.
2.
At least three (3) years coding of multi-tier applications, including but not limited to responsive web application development and mobile application development and proficient in C#, ASP, Java, PowerShell, web service API, SOAP, and REST by using MVC and Angular design pattern.

2. Personnel and Rates The personnel shall perform the tasks described in this SOW, at the rates indicated in the agreement.

a. Given the size, scope, and complexity of this project, it is of utmost importance that the staff have adequate hours to work effectively on this project. The Contractor shall be responsible for monitoring the monthly hours billed to ensure the staff effectively meet the needs of the Project.

b. Changes in cost estimates that do not alter the total cost of this SOW will be conveyed to the State. The rationale for the change shall be included. The State shall approve any change to the cost estimates in writing. The identified staff will perform the tasks described and at the rates indicated in this agreement. The Contractor shall identify its staff by name and hourly rate.

c. The assigned staff will perform the tasks described in this SOW, at the rates indicated in the Cost Worksheet. The Contractor shall identify each staff by name, labor category, and hourly rate.

d. Contractor shall provide an Organization Chart identifying each of the proposed team members.

3. Replacement of Personnel

a. If a Contractor’s staff becomes unable to perform duties due to illness, resignation, or other factors beyond the Contractor’s control, the Contractor shall make every reasonable effort to provide suitable replacement personnel by submitting the Add, Delete Personnel form (to be provided at the Kickoff meeting) for review and approval by CAL FIRE. The replacement personnel shall meet all the requirements and shall be approved in writing by CAL FIRE prior to beginning work. Notwithstanding these factors, reassignment and/or substitution of staff may be considered a breach of the agreement, and the Contractor will forfeit all withholds held by CAL FIRE up to the point in time that a suitable replacement has been approved. The forfeiture is in addition to any other remedies CAL FIRE may have for such breach of the agreement.

b. All replacement staff shall meet or exceed the Mandatory Staffing Qualifications for the position in which they are filling. The Contractor has a minimum of five (5) State business days to submit, unless otherwise agreed upon:

i. Add, Delete or Substitute Personnel Request Form,

ii. Résumé for the replacement(s),

iii. Completed Classification Qualifications.

c. CAL FIRE Project Manager will review the Add, Delete or Substitute Personnel Request Form, and résumé within ten (10) business days after receipt to ensure the replacement staff meet or exceed the Mandatory Staffing Qualifications. CAL FIRE Project Manager may interview the replacement staff, and if the substitution is approved, will sign the Add, Delete or Substitute Personnel Request Form. CAL FIRE Project Manager will return the form to the Contractor as formal approval. Upon notification from CAL FIRE Project Manager and receipt of the approved Add, Delete or Substitute Personnel Request Form, the replacement staff may begin work.

d. Replacement personnel shall be the same classification and at the hourly rate of the staff(s) or position(s) being replaced. CAL FIRE and the Contractor shall agree upon the experience and individual skills of the proposed replacement personnel.

4. Additional Contractor Staff

a. If not prohibited by other agreement documents, the Contractor may assign additional staff to the agreement only with the prior written consent of CAL FIRE. Any such consent may be rescinded at CAL FIRE’s discretion. Additional staff must meet the appropriate Mandatory Staffing Qualifications and be assigned to pre-existing work identified within the scope of this Agreement. The Contractor shall submit:

i. Add, Delete or Substitute Personnel Request Form,

ii. Résumé (s) for the additional staff(s)

iii. Completed Resume for position in which they are filling.

iv. Completed IT-MSA Classification Qualifications

b. CAL FIRE’s Project Manager will review the Add, Delete or Substitute Personnel Request Form and résumé within ten (10) business days after receipt to ensure the additional staff meets the Mandatory Staffing Qualifications. CAL FIRE’s Project Manager may interview the additional staff, and if their addition is approved, will sign the Add, Delete or Substitute Personnel Request Form and obtain approval from the assigned Procurement analysist. CAL FIRE’s Project Manager will return the form to the Contractor as formal approval. Upon notification from the CAL FIRE’s Project Manager and receipt of the approved Add, Delete or Substitute Personnel Request Form, the additional staff may begin work.

c. Additional personnel classification cannot exceed the hourly rate of the staff(s) or position(s) as stated in the on the Cost Worksheet provided by the Contractor. CAL FIRE and the Contractor shall agree upon the experience and individual skills of the proposed additional personnel.

CONTRACTOR AND STORAGE OF ELECTRONIC DATA

All IT Services Contractors, both the company and all staff working on the agreement must reside within the United States (US) and/or Canada. All storage of electronic data must be stored within cloud data centers located within the continental US, this includes primary and secondary storage sites. These site locations must be in the IFB response.

AGREEMENT TYPE

1. Unless otherwise specified, the Statement of Work shall define and authorize work on a Fixed Price basis, with a guarantee of task completion.

2. To the extent that additional work not foreseen at the time this agreement is executed must be accomplished, Work Authorizations, as described in the Statement of Work, will be the means for defining and authorizing such work on a Labor Hour basis.

SOLUTION MODIFICATION

The State may request Solution modifications, limited to services and the delivery thereof, at any time. Because such changes could significantly affect critical aspects of the work being performed, all changes requested must follow the formal change control process as set forth below to gain approval.

1. Change Control Process The following change control process will be used except as superseded by mutual written agreement or other binding procedures:

a. A Change Request (CR) prepared in a form and format acceptable to both the State and the Contractor will be the vehicle for proposing a change.

b. A CR must describe the requested change; the rationale for the change, and any anticipated effect the change will have on the agreement and/or the work performed under the agreement.

c. The Change Control Board (CCB) will be comprised of the CAL FIRE Project Manager, the Contractor, and various other members of the State project management team. Contractor will serve in a non-voting capacity on the CCB.

d. Upon receipt of a CR, the CCB will engage in a deliberative process to determine whether the change(s) sought by the CR should be pursued by the Project, seeking such input as is necessary to reach an informed decision.

e. If the CCB determines that a CR merits further action, the State will prepare a draft Work Authorization which describes the Project's requirements related to the change desired. The CAL FIRE Project Manager will sign the draft Work Authorization and transmit it to the Contractor for finalization.

f. The Contractor shall fully develop and finalize a Work Authorization by preparing Attachment 7, Work Authorization Template within ten (10) State business days of receipt or other period as mutually agreed. The Contractor shall not charge the State for preparing a Work Authorization; The Contractor's Project Manager will sign the final Work Authorization and submit it to the CAL FIRE Project Manager.

g. The CAL FIRE Project Manager will review the Work Authorization for quality and accuracy and take such measures as are necessary to ensure its cost-effectiveness, including negotiations with the Contractor as needed. After such review and consistent with Project administrative processes, the CAL FIRE Project Manager will accept and sign, or reject the Work Authorization and transmit it to the Contractor.

h. Upon receipt of the accepted/rejected Work Authorization, the Contractor's Project Manager will sign it to acknowledge receipt thereof and return it to the Project Manager. Upon its return to the CAL FIRE Project Manager, the Contractor may begin performing any work approved by the Work Authorization.

SECURITY AND CONFIDENTIALITY

To preserve the integrity of the security and confidentiality measures integrated into the CAL FIRE information technology systems, the Contractor must be required to certify they shall adhere to the following controls prior to work starting regardless of whether the solution is delivered On-Premises or in the Cloud. Contractor must provide all security related certifications to the CAL FIRE ISO prior to work start date. If the Contractor has engaged services from a Sub-Contractor or a Subsidiary as part of an agreement, the Contractor must ensure that these parties adhere to these requirements as shown in the Security bullet points listed below.

SECURITY AND DATA PROTECTION REQUIREMENTS

The host Cloud provider must provide FedRAMP High Certification, plus, meet the additional requirements found in SAM and CA Statewide Information Management Manual (SIMM).

CAL FIRE must ensure agreements with state and non-state entities include provisions which protect and minimize risk to the state when engaging in the development, use, or maintenance of information systems, products, solutions, or services. In order to comply with the State Administrative Manual (SAM) Section 5305.8, Contractor must comply with the terms and conditions of the Cloud Computing Software as a Service (SaaS) General Provisions and Cloud Computing Special Provisions.

Security:

1. The Contractor must comply with applicable Federal, State, and local governmental laws and regulations and the CAL FIRE must verify the Contractor’s assurance of their ability to adhere to said laws and regulations.

2. The Contractor must implement an Information Security Program for the prevention and detection of fraud and malware, the protection of data, and to authorize security awareness training; the Contractor must meet or exceed the CAL FIRE Information Security Program. The Contractor must submit to the CAL FIRE Information Security Officer a copy of their Information Security Program.

3. All Contractors having access to CAL FIRE Information Technology resources and assets must take CAL FIRE’s Cyber Security Training.

4. The Contractor must implement a Risk Assessment Program for assessing risks and to identify the specific threats and vulnerabilities; the Contractor must meet or exceed the CAL FIRE Risk Assessment Program; The Contractor must submit to the CAL FIRE Information Security Officer a copy of their Risk Assessment Program.

5. The Contractor must implement an Incident Response Program defining the response procedures and the points of contact between the Contractor and the CAL FIRE including escalation thresholds; the Contractor must meet or exceed the CAL FIRE Incident Response Program; The Contractor must submit to the CAL FIRE Information Security Officer a copy of their Incident Response Program.

6. The Contractor must maintain their Information Security Program, Incident Response Program, and Risk Assessment Program at all times, including monitoring and testing the programs to ensure their effectiveness; the Contractor must provide to the CAL FIRE Information Security Officer the results of these test.

7. The Contractor must disclose to the CAL FIRE any breach of the security of any information or information resource in accordance with the criteria and procedures set forth by the CAL FIRE. The Contractor must notify the CAL FIRE’s Information Security Officer within the agreed upon time‑frame of any confirmed or suspected security incident or breach, followed by a report of the incidents that it has identified, and the measures taken to resolve and mitigate the incident.

8. The Contractors must sign formal undertakings (e.g., Nondisclosure Agreement) regarding the intellectual property rights of work performed during their terms of agreement.

9. Under no circumstance must the Contractor Perform any activities that can harm CAL FIRE or lessen its security program; and,

10. CAL FIRE reserves the right to audit the Contractor’s information security controls, logs, and associated plans and processes to verify compliance with the agreement.

Confidentiality:

1. CAL FIRE owns all data collected by CAL FIRE, third party users of the database and/or by the Contractor may not share, transfer, give access to any of the information of the database to any private, public, or state entity without express permission by CAL FIRE program, management and/or CAL FIRE legal.

2. The Contractor must implement an Information Privacy Program to safeguard the confidentiality and integrity of the CAL FIRE information; the Contractor must meet or exceed the CAL FIRE Information Privacy Program; The Contractor must submit to the CAL FIRE Information Security Officer a copy of their Information Privacy Program.

3. The Contractor must work with designated staff within the CAL FIRE to classify information used by or created by the Contractor’s development environment or any of its deliverables.

4. The Contractor must assume all responsibility for the Confidentiality, Integrity, and Availability of the information and the information systems under its control including its protection by the use of encryption of information at rest and in transit in accordance with applicable Federal, State, and local laws and regulations.

5. The Contractor must limit information collected and retained to legitimate business purposes associated with the agreement; and not use or redistribute any of the CAL FIRE information processed, stored, or transmitted by the Contractor except as specified in the agreement or upon written CAL FIRE approval. All data Shall be confidentially destroyed or returned to the CAL FIRE as directed by the CAL FIRE within a mutually agreed upon date.

6. The Contractor must keep audit logs of any access or other activities associated with the CAL FIRE’s information.

7. The Contractor must disclose to the CAL FIRE any requests, from any source, for copies of or access to, or other disclosure of the CAL FIRE’s information.

8. The Contractors must sign the Confidentiality Statement, Attachment 5, regarding the confidentiality of the information being access during their terms of agreement; and,

9. The CAL FIRE reserves the right to re-classify data and require additional information security controls as necessary.

10. Contractor may not remove any confidential information from CAL FIRE locations. Contractor must adhere to CAL FIRE policies and procedures regarding Acceptable Use and security of CAL FIRE computing systems.

WARRANTY

Contractor warrants all work done on this project. CAL FIRE will assure that during installation, and/or implementation of changes to webpage functionality are not voided by adhering to proper installation instructions.

COST OR PRICING DATA

See Attachment 2 – Cost Worksheet.

CHANGE CONTROL/WORK AUTHORIZATION PROCESS

The State may request modifications/enhancements, limited to services and the delivery thereof, at any time. Because such changes could significantly affect critical aspects of the work being performed, all changes requested must follow the formal enhancement process as set forth below to gain approval. Contractor shall provide solution, which allows for minor enhancements and expanded functionality utilizing the below change control/work authorization process.

MODIFICATION/ENHANCEMENT REQUEST PROCESS

The following enhancement request process will be used except as superseded by mutual written agreement, or other binding procedures:

1. An Enhancement Request (ER) prepared in a form and format acceptable to both the State, and the Contractor will be the vehicle for proposing a change.

2. An ER must describe the requested change, the rationale for the change, and any anticipated effect the change will have on the agreement and/or the work performed under the agreement.

3. Upon receipt of an ER, CAL FIRE Program Management will engage in a preestablished internal process to determine whether the change(s) sought by the ER should be pursued for the Project, seeking such input as is necessary to reach an informed decision.

4. If CAL FIRE Program Management determines that an ER merits further action, the State will prepare a draft Work Authorization which describes the Project’s requirements related to the change desired. The CAL FIRE Project Manager will sign the draft Work Authorization and transmit it to the Contractor for finalization.

5. The Contractor shall fully develop and finalize a Work Authorization by preparing Attachment 7, Work Authorization Template within ten (10) State business days of receipt or another period as mutually agreed. The Contractor shall not charge the State for preparing a Work Authorization. The Contractor’s Project Manager will sign the final Work Authorization and submit it to the CAL FIRE Project Manager.

6. The CAL FIRE Project Manager will review the Work Authorization for quality and accuracy and take such measures as are necessary to ensure its cost-effectiveness, including negotiations with the Contractor as needed. After such review and consistent with Project administrative processes, the CAL FIRE Project Manager will accept and sign, or reject the Work Authorization and transmit it to the Contractor.

7. CAL FIRE IT Procurement will review all ER to determine if this can be processed as a minor change or will require an amendment to the agreement.

8. Upon receipt of the accepted/rejected Work Authorization, the Contractor’s Project Manager will sign it to acknowledge receipt thereof and return it to the Project Manager. Upon its return to the CAL FIRE’s Project Manager, the Contractor may begin performing any work approved by the Work Authorization.

CONTRACTOR RESPONSIBILITIES

1. Contractor shall deliver an Aviation Tracking Information System using a cloud-based Software as a Service (SaaS) solution. Please reference the high-level project requirements listed within this SOW.

2. Contractor shall establish a point of contact for escalation procedures for both technical and non-technical support.

3. Contractor shall provide user support via a "Help Desk," accessible through email and phone. Help Desk assistance will be available 24 hours a day, seven days a week, from April 15th to October 31st each year, and, during a “declared fire season”.

4. Contractor shall provide ongoing maintenance and updates.

5. Contractor shall establish a training plan based on implementation.

6. Contractor shall provide production and customer support.

7. Contractor shall be available to provide any additional training at the CAL FIRE’s request.

8. Contractor shall provide notification of any planned outages to the system due to scheduled maintenance activities.

9. Contractor shall provide reliable levels of service from trained professional support staff.

10. Contractor shall be solely responsible for all travel arrangements and expenses that may accrue, such costs will not be reimbursed.

DEPARTMENT RESPONSIBILITIES

1. CAL FIRE will provide a project manager for the duration of this agreement.

2. CAL FIRE shall provide access to the systems.

3. CAL FIRE will provide the Contractor the AIMS data set in a csv or Excel file for data migration from AIMS into CATIS.

4. CAL FIRE shall engage in weekly status meetings where the CAL FIRE team will go over current progress, issues, resolutions, and other agenda items.

5. CAL FIRE Subject Matter Experts shall be available to project team when needed throughout all phases of implementation and be engaged during the implementation process.

6. CAL FIRE will be available for testing throughout the implementation.

7. CAL FIRE will provide detailed requirements for work items to be reviewed and estimated.

8. CAL FIRE will approve all estimated hours for work items.

TRAVEL COSTS

Travel costs shall not be included in a proposal.

BILLING INFORMATION

The Contractor shall submit invoices (including the purchase order number) to the following address:

Department of Forestry and Fire Protection P.O. Box 944246

Sacramento, CA 94244-2460 Attn: Marty Buno Ph: 916-531-4096 Email: marty.buno@fire.ca.gov

PRIMARY POINTS OF CONTACT

Contractor Primary Contact:

Name:

Street Address:

City, State, Zip:

Ph:

Fax:

Email:

State’s Primary Contact:

Tom Firth 5500 Price Ave McClellan, CA 95652 Ph: 209-419-4408 Email: tom.firth@fire.ca.gov Please forward renewal notices to the attention of the State’s Primary Contact.

TERMINATION

The State shall have the right to terminate this agreement within (30) days with written notice to the Contractor.

Consistent inability to provide quality products or services, as stipulated in the above sections, as adjudged by the CAL FIRE’s Project Manager shall be grounds for termination of the individual or contracting agency providing support under this agreement.

AMENDMENTS

The agreement can be amended for time, tasks, and funding at current agreement rates specified in Attachment 2: Cost Worksheet upon mutual agreement of both parties. The Contractor will be required to contact the CAL FIRE contract administrator prior to the agreement completion date.

File details come from the government source that posted it. Updated .