Attachment_C_-_CHP_Statement_of_Work_CHP_Final_Updated.docx

1 INTRODUCTION

This Statement of Work (SOW) describes the equipment and services the Contractor, hereinafter referred to as the “Contractor,” will provide the California Highway Patrol (CHP) for a commercial off-the-shelf (COTS) Wireless Mobile Video and Audio Recording System (WMVARS).

The Contractor is expected to:

1. Identify business processes to support system configuration;

2. Document the configuration settings selected by CHP;

3. Collaborate with the CHP Fleet Operations Section (FOS) to agree on the appropriate equipment placement, mounts, brackets, and wiring;

4. Configure, test, train, and support the statewide implementation;

5. Develop and provide knowledge transfer and training to State staff; and

6. Collaborate with CHP in developing and maintaining project plans.

2 WORK LOCATION

The Contractor’s Staff work locations under this Agreement are the Contractor’s location and on-site at the following CHP locations:

The Contractor must be escorted by CHP personnel for all project-related activities occurring at the CHP locations. All project- related activities conducted in a Contractor-supplied location must be located in the continental United States.

No tasks shall be performed offshore. The Contractor must make off-site staff available for meetings at the CHP Headquarters in Sacramento (in person or via telephone) 8:00 a.m. to 5:00 p.m. PST/PDT during State Business Days. State Business Days are defined as Monday – Friday, 8:00 AM to 5:00 PM, excluding State Holidays as defined by the California Department of Human Resources at: (http://www.calhr.ca.gov/employees/Pages/state-holidays.aspx).

All on-site work at CHP locations must be preauthorized by the State’s Project Manager prior to date of visit. The Contractor must notify CHP within 24 hours of visit. The Contractor staff must be escorted by CHP personnel while on site at CHP locations.

3 SCOPE/DESCRIPTION

This section will provide a high-level description of the system and the approach to the statewide WMVARS deployment.

System Overview The WMVARS must be configurable to meet the Department’s needs without custom software development.

The WMVARS will be comprised of hardware, software, and services. Specifically, the WMVARS involves:

· Configuration of direct cloud interconnection from the Contractor’s SaaS cloud to CHP’s Multiprotocol Label Switching (MPLS) enterprise network and third-party government cloud;

· Initial installation of an in-car recording system in CHP patrol vehicles; CHP will complete the installations statewide;

· Installation of on-premise appliances for local storage in selected CHP field offices and configuration of interface connections from those offices to the Contractor’s SaaS cloud;

· Implementation and configuration of a central, cloud-based WMVARS that can be accessed from any CHP location.

WMVARS Data Transmission This project will include approximately 150 locations throughout the State. The CHP would prefer an all direct to cloud solution; however, due to the disparate bandwidth capacity at some of these locations, a hybrid WMVARS solution that provides on-premise storage that will transmit to the cloud storage is required in select locations. The centralized video storage application shall serve the “direct to cloud,” “on-premise,” and body-worn camera (BWC) dock inputs.

Direct to Cloud It is expected most of the video evidence will be uploaded to the cloud solution through CHP’s 4G cellular modem during the officer’s shift and then, once the vehicle is within CHP’s Wi-Fi range, the modem will detect the Wi-Fi signal and switch from the cellular transmission method to the faster Wi-Fi method to either continue to upload directly to the cloud or upload any remaining videos on the central unit directly to the on-premise appliance’s video storage system. If a user wishes to view a video, the video can be downloaded from the WMVARS cloud-based central data repository and viewed on a CHP workstation.

On-Premise Approximately eighty (80) CHP locations might not have adequate network bandwidth or strong enough cellular service coverage to upload videos directly to the WMVARS cloud based central data repository or download videos to view in a timely manner. These locations will require an on-premise appliance to temporarily download and store WMVARS data through the CHP-secured Wi-Fi WMVARS in-car camera or BWC system. The locally stored WMVARS data is uploaded periodically daily to the WMVARS cloud-based data repository. If videos uploaded to the on-premise appliance storage are no longer available on the on-premise appliance, the user will download the video from the cloud to the on-premise storage appliance to view or view the video directly from the cloud.

4 WMVARS HARDWARE

The hardware to be provided shall include all commercially available equipment (e.g., cameras, cabin and wireless microphones, in-car data storage, on-premise appliances etc.). All in-car, BWC, and on-premise systems hardware provided under the resultant contract must meet the requirements as defined in Exhibit 8.19 WMVARS Specification and as described below. Hardware coming to the end of its useful life will not be considered as compliant with the Agreement requirements. In-car cameras and body worn cameras must be from the same Original Equipment Manufacturer (OEM) with one software application for the WMVARS solution.

On-Premise Appliances All on-premise appliances must be provided as part of the integrated in-car and BWC solution. The appliances must include the operating system and local storage. The racks must be four posts with panels and locks to ensure physical access. All on-premise appliances shall have the computing power to provide similar software performance to that of the software running in the cloud. The on-premise appliances shall be sized to hold thirty (30) days’ worth of video with a minimum of 100 TB storage capacity. The videos will be available to view locally for thirty (30) days.

Central Unit/Head Unit The in-car WMVARS solution includes a computing system that will store video and allow the officer to manage the video from within the vehicle before the video is uploaded. This device has two (2) forms: a central unit and a head unit. The central unit is to be mounted in the vehicle’s trunk. The head unit is to be installed in the front cabin of the vehicle.

WMVARS Display The WMVARS display unit shall allow the user not only to view the video but also categorize the recorded video before it is uploaded to the video system’s cloud storage. For BWC users, the BWC shall wirelessly connect to the user’s tablet to categorize and view video before the data is uploaded.

In-Car Cameras A total of 2,800 CHP patrol vehicles shall be equipped with in-car cameras. With the exception of select vehicles (defined below), a minimum of one front facing and one rear facing camera for each patrol vehicle shall be provided with the system. An Ethernet cable or the manufacturer’s industry standard cable shall be used to connect the central unit and the required cameras.

The required number of rear facing cameras is approximately 2,571 as the 229 K9 and Mobile Road Enforcement (MRE) vehicles will not require a rear camera. The rear facing camera shall have the ability to record in low light settings, such as an infrared feature. The rear facing camera shall be activated by the officer as it is not necessary in all recording situations.

In-Car Cabin Microphone Most patrol vehicles will require an in-car cabin microphone. The required number of cabin microphones is approximately 2,740 as the 60 K9 vehicles do not require a cabin microphone.

In-Car System Integrated Wireless Microphone Patrol vehicles require two wireless microphones; approximately 5,600 microphones are required as a component of the WMVARS solution to record audio from outside the vehicle and associate the audio with the video recorded by the WMVARS solution.

In-Car WMVARS Mounts All vehicle equipment installations will require the approval of the CHP FOS. After Contract execution, the Contractor shall agree to collaborate with FOS to agree on the appropriate placement in the vehicle for installation of the in-car cameras, the cabin and wireless microphones, and the central/head unit mounts.

The Contractor shall agree to provide the CHP's FOS acceptable mounts according to CHP specification for various patrol vehicles in CHP’s fleet.

Body Worn Cameras Body-worn camera shall be a single unit that consists of a camera, microphone, battery, and onboard storage.

WMVARS ––Recording (Both In-Car and BWC) The WMVARS shall record from multiple cameras and microphones once activated, either manually by the officer or configured automatic triggers such as activating the emergency lights (front facing red lights). The rear camera shall require manual activation/deactivation only.

Looping Video (In-Car Only) The WMVARS shall provide continuous recording, video only, until space on the central/head unit is used, then start recording over the oldest footage. The cameras shall not indicate the in-car system is recording. This video is not expected to be uploaded to the cloud storage.

Event triggered or user-triggered video shall begin immediately following trigger activation.

Pre-Event Recording The WMVARS shall provide an agency-configurable feature that will continuously record within the full capacity of the available disk space, both audio and video, before the active recording of an event was triggered. Once the active event recording is triggered, the event shall include the pre-recorded video up to one (1) minute before the activation. This video shall be able to be accessed through user permission settings according to CHP specifications and converted into event data.

This video will automatically become a part of the event recording and will be used to show events leading up to the recorded event. It shall be possible to configure this feature not to capture audio during the pre-event recording time.

Categorization/Tagging Pre-Upload The system shall provide functionality that allows an officer to categorize and add notes to their videos before uploading to the WMVARS. In-car systems shall provide a mounted head unit display in the front cabin to facilitate categorization. Motorcycle officers using a BWC shall categorize their videos on their tablet that connects wirelessly to the BWC before uploading to the WMVARS. After the video has been uploaded, WMVARS software shall allow additional categorization on a CHP workstation.

Categorization/Tagging Post-Upload The system shall include functionality that will allow CHP to configure the standard categories that will apply to video evidence. These categories will be available to officers on the in-car system, the BWC tablet, as well as on a CHP workstation so they may ‘tag’ the video with the appropriate category (e.g., Use of Force, Enforcement Contact, Traffic Collision) after the video has been uploaded.

The WMVARS shall support bulk modifications to any metadata, both initial and modified. For example, when an officer retires, all of the officer’s evidence needs to be reassigned to another owner or, if several videos need be re-categorized, an authorized user shall be able to select all of the targeted videos and apply the change in one transaction.

Video Upload The in-car system shall provide the ability for the officer to either manually upload event videos or have event videos automatically uploaded. Automatic upload shall occur without officer intervention, once the vehicle enters cellular or CHP-secured Wi-Fi coverage areas. The system shall intake an officer’s video evidence from any CHP location directly to the cloud or on-premise appliance, whichever the central or head unit has been configured to communicate with from the vehicle.

Body Worn Camera – Charging/Uploading Data The BWC shall provide the ability for the officer to either manually upload event videos or have event videos automatically uploaded. Automatic upload shall occur when BWC is placed in the associated docking station slot. While the BWC is docked, it shall charge as well. The data shall be uploaded directly to the cloud or on-premise appliance, whichever the BWC has been configured to communicate with from the Area office.

Chain of Custody Data (In-Car and BWC) Chain of custody, in legal contexts, refers to the chronological documentation or paper trail that records the sequence of custody, control, transfer, analysis, and disposition of physical or electronic video evidence throughout the WMVARS. The WMVARS shall maintain a rigorous audit trail required to prove the chain of custody of all digital evidence. The WMVARS shall have function to support all transactional activity (e.g., viewing, tagging, etc.) and allow for the associated metadata to be auditable throughout the system.

5 WMVARS SOFTWARE

The Contractor’s software application must meet all requirements per RFP Event ID 0000011599, Section 3.1.6 Accessibility Compliance.

The Contractor shall provide a single software application that provides the same capabilities on any desktop, tablet, and mobile devices and on all on-premise appliances.

The WMVARS system should be robust enough to support a minimum of two thousand (2,000) simultaneous users without affecting system performance, as defined by service levels stipulated in this Contract.

Permissions and Access The system shall include role-based privilege access and management capability that will limit access to functions unless permissions have been bestowed to the user by the CHP Application Administrator.

The system shall integrate with CHP’s Active Directory for authentication and authorization. Permissions to view videos shall support a hierarchy of the CHP chain of command so a commander or chief can view the videos of personnel within their command.

Further access rights are to be configured by the CHP Application Administrators, with the Contractor’s assistance, during the implementation stage of the project.

The system shall provide role/permissions-based access on the following user groups:

The CHP requires the permissions granted to users be selected individually, ala carte, to tailor a user’s system privileges to their individual roles within the organization in addition to a set of privileges associated with a role. The system shall provide role-based access for management, control, and prevention of unauthorized viewing, alteration, redaction, or deletion of recorded data.

Search A critical system feature is the search function. This function allows users to search, view and (re)categorize their videos. Users with elevated permissions can also search the entire system using a built-in search function. The WMVARS shall allow search on across all CHP locations by any metadata element (e.g., user name, ID, category, date/time, date ranges, etc.) or a combination of these elements such as category and date ranges.

Viewing (Both In-Car and BWC) It is critical the video evidence can be viewed by any user. The videos a user will have access to view will be determined by their system permissions. In-car video view is required to appear on the WVMARS display and BWC video view is required to display on the motorcycle tablet before the video is uploaded.

Attachment C – CHP Statement of Work Wireless Mobile Video and Audio Recording System

Revised 3/9/2022

All authorized users shall be able to view videos, based on their system permissions, on a CHP Windows workstation.

Redaction The WMVARS shall provide an audio and video redaction function available to authorized users only. A central group at CHP performs video evidence redaction to respond to Public Records Act (PRA) and media requests. The WMVARS software shall always retain an original copy of the evidence file and create a copy to be evaluated for redaction of both video and audio. The WMVARS software shall provide the ability to determine and authenticate an original file or indicate if a file has been modified.

Video Duplication / Export The WMVARS will provide the ability to create multiple evidence files, tags, markers, indexes, and clips without altering the original video. The system shall have the ability to share video evidence with groups inside and outside of CHP (e.g., the courts) with no proprietary file formats to view the video. The WMVARS software shall only allow authorized users to export video evidence. The software shall provide online sharing including support video export to several types of video files including at least one common type of video file (e.g., MP4, AVI, etc.) as well as physical media such as DVD. The software shall support sections of video to be exported to physical media (e.g., DVD) in a manner that retains the chain of custody. The WMVARS shall support splitting a video across multiple media, while preserving the integrity and authenticity of the file (e.g., A video file may be too large to fit onto on DVD).

Data Retention and Purging The CHP follows an evidence retention policy that also applies to digital evidence. The WMVARS shall include an agency-configurable data retention policy that evaluates video retention by both date and category. The CHP anticipates video retention for a minimum of one (1) year with the ability to keep video at the life of the contract if the video is held for a court case. Less than five (5) percent of CHP’s enforcement activities will require a video to be held for a court case beyond one (1) year.

The CHP Evidence Officer in each Area office is responsible for the management, review, categorization and tracking of evidence in the CHP’s possession. As such, the final evidence disposition for video data is also the responsibility of the Evidence Officer. Ninety (90) days prior to the end of the data retention period, video evidence that meets the criteria for final processing must be presented to the Evidence Officer, via a user interface or report prior to purging from the WMVARS system. Once the Evidence Officer has identified/tagged videos that are not to be purged from the list, all remaining videos on the list shall be automatically purged from the WMVARS. The WMVARS shall provide functions to enable the Evidence Officer and other authorized users to purge based on categorization schedule and configure per data retention schedule.

Reporting The WMVARS shall facilitate the reporting of data in video records, files, and tables. The WMVARS system must be able to store data needed for predefined report generation and ad hoc queries. The WMVARS system shall provide for generating ad hoc queries a nontechnical resource can understand and use. The reporting system should be robust enough to support a minimum of two thousand (2,000) simultaneous users without affecting system performance, as defined by service levels stipulated in this Contract. The timing of the reports shall be configurable by CHP.

Chain of Custody Logs The system must provide chronological documentation, (i.e., paper trail) showing the custody, control, transfer, and disposition of video evidence within the WMVARS. The WMVARS shall include a canned “Chain of Custody” report that will follow video evidence from initial recording though its removal from the WMVARS system.

Management Reports The WMVARS Management reporting shall include detailed, summary, and statistical reports. Detailed and summary reports must include daily reports for videos uploaded by CHP Location, Device, and CHP User (employee ID). These reports shall assist Evidence Officers, Area Commanders, and Application Administrators in managing digital evidence within the WMVARS. The WMVARS statistical reports shall include daily, weekly, monthly, year-to-date, and annual reports for videos uploaded, storage space utilized, number of users, average duration of videos by category, and should be able to breakout data both by CHP Location and a statewide rollup for use in trending data.

Upgrades The Contractor is solely responsible for providing 100 % of the required software maintenance and support for software upgrades seamlessly for the SaaS cloud portion. For on-premise software upgrades, the Contractor is responsible for performing the same work as required for the SaaS cloud solution with an approval from CHP first. The CHP will provide the same level of infrastructure capability to assist and support the Contractor’s software upgrade work.

Upgrades to the WMVARS software shall be offered to CHP during the life of the Agreement.

All system upgrades shall be administered from a central location (e.g., firmware updates, camera configuration, video storage system upgrades).

The CHP shall have the option to upgrade the production system with the latest software offered by the Contractor (when the software is in the same product line and the hardware does not restrict the upgrade) within the term of the Agreement.

On-Premise Appliances The Contractor shall ensure each on-premise appliance and software running on the appliance passes CHP’s standard security scanning. The appliance must be provisioned and configured in compliance with CHP network security standards. If the Contractor creates a standard image (i.e., a golden image), then all subsequent appliances will not require the security scanning process.

WMVARS Software Maintenance The Contractor shall coordinate scheduled downtime for regular system maintenance. Scheduled downtime shall not exceed two (2) hours and must occur during off, or nonpeak, hours, as determined and approved by CHP.

6 WMVARS IMPLEMENTATION

The CHP is organizationally divided into eight (8) geographic Field Divisions across the State and CHP Headquarters (nine [9] Divisions total) the roll-out schedule for these nine (9) Divisions is divided into three (3) stages per the table below. Individual purchase orders will be issued for each stage. The specific delivery requirements will be based on the schedule developed by CHP and the resultant Contractor per Section 6, subsection entitled Statewide Rollout. It is expected the full implementation of the WMVARS (as defined in this SOW) will be complete within 36 months of contract award. The first project stage will include WMVARS configuration with the Contractor, system testing, and productive use of the system based on the criteria outlined in Section 7, Testing, and pre-rollout training per Section 8, Training, before the statewide rollout will commence. It is expected that a similar multi-staged implementation approach will be followed, and schedule developed accordingly once a purchase order is issued for BWCs.

Stage 1

· 384 In-car July 2018 •15 On- June 2019 through Premise Appliances Stage 2 July 2019 through June 2020

· 1946 In-car

· 20 On- Premise Stage 3 July 2020 through J une 2021

· 930 In-car

· 45 On- Premise

Statewide Rollout Plan The statewide WMVARS rollout will be a staggered deployment and, as such, all equipment shall be delivered to CHP Headquarters or to other CHP selected locations based on the mutually agree upon rollout schedule. The Contractor shall deliver all WMVARS hardware equipment for each Division to CHP Headquarters, at which point the hardware will be configured, security scanned by CHP staff, and shipped to the Divisions in preparation for the Division Training sessions.

Equipment deliveries will be staggered to align with the Divisional Training sessions.

Spare Parts All line items on Exhibit 8.21 Cost Worksheet shall be available for individual purchase. These items will either be purchased for immediate use or as spare parts.

Units not in productive use by CHP staff are to be considered spare units. Spare units will be used as backups to WMVARS equipment sent to the Contractor for repair/replacement or if a vehicle is sent out for repairs and is out of use.

Schedule After Contract execution, CHP will conduct an on-site kickoff meeting within the first two

(2) weeks. The kickoff meeting will be a discussion to set mutual (between the State and the Contractor) expectations and to finalize the project schedule.

Within the first fifteen (15) days after Contract execution, the Contractor shall deliver a project schedule in Microsoft Project format. This schedule can deviate slightly from the schedule shown in this Contract, but only with CHP’s approval. The schedule must detail when the Contractor intends to deliver the requirements of the Contract, when the Contractor needs CHP to perform a responsibility of the Contract, and other details to ensure the Contractor’s project is well planned.

Training material and Outline Deliverable 30 days after contract award

4.

After successful completion of Ten (10) day proof-of-compliance/twenty (20) day Burn- in Test

Configuration Once the Contract is awarded, the Contractor shall provide three (3) in-car WMVARS equipment and one (1) on-premise appliance to CHP. The Contractor shall configure the in-car WMVARS systems and then train CHP staff on the configuration process. Contractor will be required to install all on-premise appliances. Training will not be required for the on-premise installations.

These WMVARS units will be distributed to the following teams for testing:

· FOS for mounting and power planning

· Public Safety Communications Office (PSCO)

· California Highway Patrol ITS for testing and documentation The CHP will coordinate meetings (shown on the schedule) with the Contractor to obtain CHP’s input and agreement through the detailed system configuration decisions. These configuration sessions shall take place at CHP Headquarters in Sacramento, California.

Simultaneously, CHP will coordinate meetings with the Contractor and FOS to design the in-car WMVARS system installation, including camera and cabin microphone placement, central unit placement, cabling, etc. If it is determined by CHP and the Contractor that a custom mount is needed, Contractor shall provide custom mount within thirty days. All dates in Section 6. subsection entitled Schedule may need to be modified to allow for custom mount.

The placement of any WMVARS components within the vehicle's front occupant compartment must take into consideration officer safety. The components shall not interfere with the deployment of air bags, existing vehicle displays, the use of vehicle controls (such as, but not limited to, shift lever, steering wheel and environmental controls), or obstruct the drivers forward, rear, and side vision.

Once installed in CHP test vehicles or on a test bench, a WMVARS unit shall be provided to the PSCO to certify the WMVARS does not interfere with the public safety radio system in a CHP patrol vehicle or motorcycle.

7 TESTING

The initial three (3) in-car WMVARS systems and the one (1) on-premise appliance will be tested to ensure the system performs as required per Exhibit 8.19 WMVARS Specification, Exhibit 8.19A – Statement of Work, and RFP Event ID 0000011599. The CHP will verify and document whether each requirement listed below is satisfied.

If any aspect of the WMVARS does not pass the system testing, the ten (10) day proof-of- compliance testing, or the twenty (20) day burn-in period as defined below, the Contractor shall have one opportunity per testing phase to resolve unpassed requirements.

Systems Functionality and Configuration Testing The system testing will be conducted as follows:

a. Cloud interconnection – Contractor’ SaaS Cloud to connect to Multiple CHP MPLS enterprise network and cloud service providers.

b. Configuration testing – all systems settings selected by CHP.

c. Unit testing to verify system readiness.

d. Requirements testing to ensure the system performs all requirements as defined in Exhibit 8.19 WMVARS Specification, Exhibit 8.19A – Statement of Work and RFP Event ID 0000011599.

If the solution does not successfully complete the system functionality and configuration test, the contractor will have ten (10) days to remedy and resubmit for re-testing. Failure to successfully pass the re-test may result in contract default per Exhibit 8.22 IT General Provisions, Article 25. Rights and Remedies of the State for Default.

Ten (10) day Proof-of-Performance Testing Upon successful system functionality and configuration testing, the initial three (3) in-car WMVARS systems and the one (1) on-premise appliance will be required to operate in compliance with the contract requirements for a period of ten (10) days. If, during the ten

(10) day proof-of-compliance test, the system fails to perform as required, the contractor will have ten (10) days to remedy and resubmit. The ten (10) day proof-of-compliance period shall start over for re-testing. Failure to successfully pass the re-test may result in contract default per Exhibit 8.22 IT General Provisions, Article 25. Rights and Remedies of the State for Default. Upon successful completion of the ten (10) day proof-of-compliance period, the burn-period testing, as described below, will be initiated.

Burn-in Period Testing Upon successful completion of the System Functionality and Configuration Testing and the ten (10) day proof-of-compliance period, the burn-in testing period (20 days) will begin.

If the solution does not successfully complete the burn-in testing, the Contractor will have 10 days to remedy and resubmit for testing. The twenty (20) day burn-in period shall start over for re-testing. Failure to successfully pass the re-test may result in contract default per Exhibit 8.22 IT General Provisions, Article 25. Rights and Remedies of the State for Default.

System Acceptance The CHP will formally accept the WMVARS with the successful completion of the burn-in period testing. The CHP will authorize the contractor to invoice for the equipment and services provided and proceed with delivery of the existing equipment on the purchase order.

Statewide Rollout This section explains the project’s implementation approach, in a chronological format. The implementation must be finished (i.e., all WMVARS in productive use) within thirty-six

(36) months of the Contract award. The CHP will work with the Contractor to finalize the approach and schedule within fourteen (14) days after Contract award. The CHP reserves the right to approve changes to the approach if in the best interest of the state and the Contractor agrees to the change(s) within two (2) weeks.

The first purchase order will be for the initial three (3) in-car WMVARS systems and one

(1) on-premise appliance and all other equipment and services required for the first stage of the statewide rollout. The additional stages will begin per the agreed upon schedule and when a purchase order is issued.

All WMVARS systems, including BWCs, are to be received by CHP thirty (30) days after issuance of purchase order and prior to the Division Training sessions to allow time for CHP to perform Asset Management tasks and ship to the Divisions.

8 TRAINING

Pre-Rollout Training After the successful completion of the System Functionality and Configuration Testing and during the ten (day) proof-of-compliance testing and twenty-day burn-in period, the Contractor shall provide system training to CHP System Administrators and select field staff at CHP Headquarters and assist FOS to train field staff on the in-car WMVARS installation process.

Standard training material is to be provided within thirty (30) days after contract award and should accompany the initial three (3) in-car WMVARS systems and one (1) on- premise appliance. The Contractor's training outlines shall be specific to the hardware and software being implemented on this project.

Deployment Training The resultant contract will employ a “Train the Trainer” approach. Representatives from CHP and the Contractor will facilitate system training at the remaining eight (8) CHP Field Divisions. Select CHP staff representing the Area offices of a Division will attend the Division Training. Once those CHP Area office representatives have received training at the Division Training sessions they will return to their respective Areas to train the remaining field staff.

Division Trainings shall cover the following CHP User Groups:

· Patrol Officers

· Evidence Officers

· Application Administrators

· System Administrators

· Fleet Operations The contractor must provide at least one trainer, onsite, to each CHP Divisional training for four (4) days, four-hour training sessions to help the CHP trainer deliver each End User training class.

Two (2) training tracks will be scheduled throughout the week of Divisional Training.

Track 1: Automotive Technician (Auto Tech) Training in the Parking Lot (weather permitted):

· Each Area will bring one type of each patrol vehicle to the Division office.

· FOS will provide an installation overview and the installation instructions prepared by FOS.

· Auto Techs perform an installation with FOS assistance.

· CHP will test the system before the Auto Techs return to their Areas. Auto Techs then return to their Areas with the necessary WMVARS equipment to retrofit the rest of the patrol vehicles in their Area.

Track 2: User and Evidence Officer Training in the Division Office Training/Briefing Room:

· Each Area will send their Training Officers and their Evidence Officers.

· Part A: CHP will provide a system overview and ‘how to’ instructions for the officers with the Contractor on-site for support.

· Part B: CHP will train Evidence Officers how to utilize the system with respect to video management and reports (Training Officers are option for this portion), again, with the Contractor on-site for support.

At the Division Training, CHP will be responsible for the CHP policy portion of the training while the Contractor will train on use of the system, equipment, and software. The CHP, with the assistance of the Contractor, will deliver training to the CHP Auto Techs to install the new system. The Auto Techs will return their respective CHP Area offices and continue the equipment installations in the remainder of their vehicles.

The Contractor shall provide enough trainers to support the rollout which is comprised of all nine (9) Divisions broken into three (3) stages of implementation.

The table below stipulates the training topics that shall be included in the training outline. Officers and other system users must receive sufficient hands-on training so they are able to operate the system. In addition to topics in the table, Contractor must provide training for hardware and software technical support and system administrator staff and training for the video redaction system. The Contractor is encouraged to offer additional training that will increase the likelihood for project success.

The training shall be based on the Contractor’s most current software version.

Training Topics and Stakeholders

The Contractor shall be responsible for training CHP System Administrators to support and manage the system infrastructure including applying updates and supporting the WMVARS application and the on-premise appliances.

Troubleshooting malfunctioning equipment.

(20) Office of Risk Management staff on the process of redaction and data exportation.

*Training sessions will be an individual line item on the resultant contract and CHP may order more or less training sessions as they deem appropriate.

9 STATE’S ROLES AND RESPONSIBILITIES

The CHP will provide the infrastructure and resources to support the WMVARS system video upload, download, and WMVARS. The CHP responsibilities include:

· A wide area network to transmit video to the cloud solution from an on-premise appliance as well as download video from the cloud for viewing and redaction.

· A 4G cellular/Wi-Fi modem that will be configured to transmit data over both a cellular network (AT&T or Verizon) and Wi-Fi connection.

· Wireless access points at each CHP location to support the upload of video evidence from the WMVARS via the CHP-provided 4G cellular/Wi-Fi modem.

· Security scanning of on-premise appliances using the Rapid7 application. Once an appliance has passed the security scan process and the CHP Information Security Officer (ISO) has approved the hardware, it will be allowed on to the CHP network for productive use.

· Installing the in-car system in CHP patrol vehicles during the rollout phase.

· Providing train-the-trainer training on CHP policy to field users who will use the WMVARS system and Auto Techs who will install the systems at each Division Training session.

· Collaborating with the Contractor to finalize a Project Plan and implementation schedule.

10 CONTRACTOR’S ROLES AND RESPONSIBILITIES

The Contractor will be responsible for tasks necessary to configure, test, train, support, and maintain the WMVARS system. These responsibilities include:

· Delivering quality hardware and software products according to the Contract requirements.

· Collaborating with CHP to finalize a Project Plan and implementation schedule.

· Providing train-the-trainer training on the functions and features of the WMVARS solution to field users who will use the WMVARS system.

· Assisting with placement and installation training of the in-car solution to Auto Techs.

· Installation of all on-premise appliances.

11 DATA HANDLING AND OWNERSHIP

In the performance of this Contract, the Contractor agrees to protect all information (including, but not limited to electronic files, data, and paper documents and forms) designated confidential and provided by CHP to carry out this Contract from unauthorized access, use, and disclosure through observance of the same or more effective procedural requirements as used by the CHP. The Contractor agrees to establish security procedures to protect CHP’s information.

The Contractor further agrees to implement the minimum administrative, physical, and information security safeguards to comply with the information security and privacy requirements provided in the California State Administrative Manual (SAM) Chapter 5300; State of California Information Security Office Information Security Program Management Standard Statewide Information Management Manual (SIMM) 5305-A; National Institute of Standards and Technology (NIST) Computer/Cyber/Information Security and Guidelines 800-37, 800-47, 800-53, 800-95 and 800-122; Federal Information Processing Standards (FIPS) Publications approved by the Secretary of Commerce pursuant to the Federal Information Security Management Act (FISMA) 140-2,197 and 199, and California Information Practices Act (IPA), Civil Code section 1978 et seq. for the terms and length of this Contract and while in possession of, maintaining, or accessing State information.

Data Storage The WMVARS’ centralized data repository resides in the cloud for each camera’s data either uploaded directly to the WMVARS’ cloud or temporarily uploaded to an on-premise appliance; then uploaded to the WMVARS’ cloud. WMVARS shall provide individual cloud data storage subscription accounts for each officer who is recording and uploading video and shall provide an unlimited data storage for each of the subscriptions. The WMVARS shall have a method of suspending individual user.

On-Premise Each on-premise appliance shall be sized to hold thirty (30) days of video data with a minimum of 100 TB storage capacity for the selected site as a temporary data repository. As soon as the data is uploaded to the on-premise appliance, the data will be uploaded to the WMVARS’ cloud central data repository. The upload to the cloud will occur periodically during the day in the background as bandwidth allows.

Data Ownership The confidential, sensitive, and personal information being provided by CHP under this Contract remains the exclusive property of CHP. Confidential, sensitive, and personal information is not open to the public and requires special precautions to protect it from loss and unauthorized use, disclosure, modification, or destruction. This information must not be shared without written permission from CHP.

The Contractor shall have a nonexclusive right to use and process the disclosed information for the purposes stated in this Agreement. This right shall be revoked immediately upon termination of this Agreement.

Statement of Confidentiality and Requirements Information maintained by the Contractor is confidential under this Agreement and exempt from disclosure under the provisions of California PRA (Government Code 6250-6265), the California Elections Code (Elections Code 2194), and other applicable state or federal laws.

Use of Information The Contractor acknowledges and agrees the information furnished or secured pursuant to this Contract shall be used solely for the purposes described in this Contract, and agrees to implement policies and procedures to ensure the confidentiality of said information. The Contractor further agrees information obtained under this Contract shall not be reproduced, published, sold, or released in original or any other form for any purpose other than identified in this Contract.

It is understood by the Contractor all confidential information transmitted over a public network must be encrypted. The Contractor and CHP shall use encryption standards, methods, and/or best practices as stated within NIST SP 800-53 such as, but not limited to, utilizing minimum encryption strength of AES 256 bit when transferring or encrypting electronic files or information.

The Contractor shall coordinate with the authorized Requestors to implement the above referenced encryption standards to send and receive all information as required. California Highway Patrol data being transmitted shall not be collected, stored, and/or transmitted electronically unencrypted on any Contractor system.

Data Access and Controls The CHP requires that a video can be accessed from any CHP Area location and CHP Headquarters. The CHP requires real-time access to the video data.

Incident Reporting, Breach, and/or Disclosure of CHP Information Disclosure of any CHP information to any person or entity not specifically authorized in this Contract is strictly prohibited. Personnel assigned to work with CHP’s confidential information shall not reveal, share, or divulge to any person or entity any of the confidential information provided under this Contract, except as authorized or required by law.

All unauthorized or suspected unauthorized access, use, and/or disclosure of information obtained under this Contract shall be thoroughly investigated by Contractor.

The Contractor shall immediately notify the CHP Project Manager who will in turn notify the CHP ISO of any actual or suspected information security breach involving information accessed or obtained under this Contract within twenty-four (24) hours of detection of the security incident. The CHP reserves the right to participate in the investigation of any security incident involving its data and may conduct its own independent investigation, and the Contractor shall cooperate fully in any such investigation.

The CHP shall not be held liable for any Contractor breach that results in the release of any information provided by CHP. The Contractor shall assume full responsibility of all claims, including but not limited to any and all liability, damages, costs, expenses, or attorney fees resulting from an information breach as defined in the California IPA.

Notification of any alleged or confirmed misuse of CHP data shall be made to CHP immediately by telephone. In addition, a written notification shall be mailed within three

(3) business days. The Contractor shall inform the State Project Team who will provide formal notification to the CHP Information Security Office.

12 SECURITY AND DATA PROTECTION

The Contractor agrees to abide by and implement the security safeguards identified in Sections 12, 13, and 14 below.

The videos in the WMVARS will be treated as evidence – just as the videos from the current CHP in-car and BWC systems are. Unlike data in most nonpublic safety COTS applications, the WMVARS must be designed by the Contractor to ensure the chain of custody is maintained to such an extent the data is admissible in court.

The CHP restricts access to evidence to authorized internal staff only. The type of information in evidence can be anything (e.g., personal, health, tax, financial, legal, confidential). Digital and physical measures are taken to protect evidence. The WMVARS shall have a secure method to access the camera equipment to prevent any unauthorized access to the recording device.

Cloud Environment The CHP requires the Contractor’s cloud infrastructure service providers comply with State of California cloud service security standards. The system uptime requirement for the SaaS solution or the cloud services is 99.99%.

A centralized cloud-based and secured data repository is required. All WMVARS data, either uploaded directly to the cloud from the camera system or uploaded from on-premise appliance data storage, must be synchronized at least daily to the centralized data repository in the cloud where it provides a single version of truth for the data.

The Contractor shall provide cloud services capable of multiple cloud interconnections.

Digital Evidence Management System The WMVARS system must have a comprehensive cloud-based Digital Evidence Management System (DEMS).

Additionally, the WMVARS application software must be designed and implemented following the software industry best practice of a Service Oriented Architecture.

The application solution must separate the data, rules for managing the data, and the methods of accessing the data from the application. The application must have a minimum of three (3) tiers, including a user interface (UI) layer, a middle data application program interface (API) service layer, and a database layer. There shall never be a direct database connection from the UI to the database and all database access must be made through data API services.

Contractor’s Cloud Service Provider Facility The Contractor-provided hosted facility site shall adhere to and implement the minimum administrative, physical, and information security safeguards to comply with the information security and privacy requirements provided in the California SAM Chapter 5300; State of California Information Security Office Information Security Program Management Standard SIMM 5305-A; NIST Computer/Cyber/Information Security and Guidelines 800-37, 800-47, 800-53, 800-95 and 800-122; FIPS Publications approved by the Secretary of Commerce pursuant to FISMA 140-2,197 and 199, and California IPA, Civil Code section 1978 et seq. and certified by the Federal Risk and Authorization Management Program (FedRAMP).

The compliance requirements include the following:

· The hosted datacenter shall be within the continental United States and provide a backup facility…