1.0 SCOPE AND CLASSIFICATION

1.1 Background: The Columbus Police Department (“CPD”) in one of the top 25 largest police departments in the United States with approximately 1,960 sworn personnel serving a diverse community of over 898,553 residents. The CPD is committed to making positive changes to protect all residents of Columbus and the people who visit Columbus. The safety of the City’s residents continues to be a top priority and is the single largest investment made by the City every year. Safe streets and violence reduction initiatives, police and community relations, intervention efforts, and investments in public safety video cameras are critical components of the city’s safety priorities, including increasing transparency and accountability and adopting best practices in the rapidly evolving field of law enforcement. In 2016, CPD was one of the first police departments in Ohio to implement a body-worn camera (BWC) program. Since 2016, the use of body-worn cameras by CPD has continued to expand and evolve. Prior to the adoption of body-worn cameras, like many police departments, CPD also utilized dash cameras – or in-car (IC) video system. Since 2016, many body-worn and in-car providers’ systems have evolved to include new capabilities, including integration of body-worn and in-car systems, synchronization of video and audio recordings, and much more. The purpose of this Best Value Procurement (BVP) is for the CPD and the City to enter a contract for a next generation public safety video solution that includes body-worn, in-car cameras for CPD’s sworn personnel, vehicle fleet, and interview rooms with a qualified Offeror (the “Contract”).

1.2 Scope: The City of Columbus, Department of Finance and Management, Purchasing Office, on behalf of the Department of Public Safety and Department of Technology, is seeking proposals pursuant to Columbus City Codes, from experienced professional firms, (hereafter Offerors) to design, purchase, configure, install, and test a body-worn, in-car video systems, and interview room recording technologies, including cameras, video management software, storage of public safety videos, and the professional services to migrate or integrate the City’s existing public safety video technologies, and to design, configure, test, install, and achieve satisfactory operational production of a turnkey public safety video system, i.e., “the public safety video system.”

The City expects to purchase approximately 2300 BWC’s, 400 IC systems and 16 interview room cameras, associated software, hardware, training, and services in the award of this BVP. It is expected that members in all five CPD zones, plus personnel assigned to other units, will receive BWCs, with the goal of 2,000 BWCs issued in 2021 with an approximate total of 2000 issued over the course of the initial first year of the contract. It is expected that members in all five CPD zones, plus personnel assigned to other units, will receive CVS systems, with the goal of 15X issued in 2021 with an approximate total of 400 issues over the course in the initial year of the contract. At the end of the first year of the proposed initial term, the public safety video system will be fully operational with approximately 2000 BWCs and 400 IC systems. The 2,000 BWC count, and 400 IC does not include reserve cameras or systems, which must be readily available to replace any BWC cameras or IC components that are damaged or need repair. Offeror is responsible for installation of all CVS into existing Division of Police fleet. Installation services must be within 30 miles of down-town Columbus area. The quantity of reserve BWC cameras required will depend on the award but we the City would like to have an inventory equal to 10 % of the total implemented BWC cameras on-hand for this purpose, and 5% of IC Systems on-hand for this purpose. The purpose of this BVP is for the City to expand or replace its public safety video client technologies (the cameras) and the video management software and infrastructure needed to support public safety operations.

Additionally, the City maintains sixteen interview rooms. If the Offeror can provide integration of audio and video to these rooms, the City would welcome a review of those offerings. However, this is not a necessary component of the BVP.

The City is publishing this BVP with the intention to enter one or multiple contracts with experienced Offerors who will (as a whole) provide a complete solution to upgrade or replace the existing Public Safety video system components. Interested Offerors may submit one or multiple proposed solutions for the City to consider each as options with their own cost/benefit.

The City seeks to have full, turnkey, implementation and migration completed within 6-12 months of award and receipt of fully executed contracts as well as purchase order(s) confirmed by the Columbus City Auditor’s Office with Offeror(s) who will provide hardware, software, licenses, implementation, and support services, and to train City personnel in its best use, to keep the system fully functional throughout its expected life span of no less than five years.

0 PAGE This document serves as a guide for use by potential Offerors as to the format and requirements of a successful proposal.

1.3 Classification: Offerors are encouraged to submit proposals that demonstrate their competence, ability, past performance, quality and feasibility, cost, and environmental impact as defined in this request. The City may contract with one or more Offerors chosen through this BVP process.

1 PAGE 2.0 APPLICABLE STANDARDS AND PUBLICATIONS

This BVP utilizes various information technology, digital video and audio recording, and other related technical standards, definitions, frameworks, concepts, protocols, and descriptions as a method for describing City requirements and for obtaining Offeror responses to questions and requirements. The Offeror should review and refer to the City’s reference architecture as part of its response.

The reference architecture is presented as a means describe the various components and technologies herein. The reference architecture includes use of common industry terms and definitions. In most cases, references for the architecture herein are referenced as part of the technical requirements section below. The reference architecture considers various technology and human components necessary to design and operate a public safety body-worn and in-car video program. Descriptions, illustrations, conclusions, and other information provided are derived from various direct and indirect resources available to the City and therefore are subject to interpretation. The reference architecture, therefore, is provided for informational and illustrative purposes only, and are subject to change without notice.

See included Generic Camera Reference Architecture reference sheet for defined terminology and technology

3.0 EXISTING CITY PUBLIC SAFETY VIDEO TECHNOLOGIES

3.1 MOBILE SYSTEMS: Current vehicle data connectivity is achieved through LTE between the mobile data computer (MDC) and the Verizon Wireless Network. NetMotion provides a persistent connection for the MDC and creates a VPN tunnel through the Verizon public network into the City’s LAN via the internet. Police MDCs are routinely used as an extension of the user’s desktop, with Active Directory authentication, folder redirection, SharePoint access, Mobile CAD, and other standard desktop applications. Additional applications used by officers in the field are to include Panasonic Arbitrator, Motorola Premier One records management system, State of Ohio Law Enforcement Automated Data System (LEADS), Intergraph Computer-Aided Dispatch, DataWorks Mugshot, Franklin Co. Sheriff License plate reader, Safran MorphoTrac AFIS, Matrix case management, Division Intranet, custom application Patrol View, Orion AgencyWeb, DayForce, and various applications.

3.1.1 Current Mobile data standards in the City of Columbus environment includes the following:

Fujitsu T732 Fujitsu T731 · i7 processors · i7 processors · Windows 7 Enterprise – 64-bit OS · Windows 7 Enterprise – 64-bit OS · 8 GB RAM · 8 GB RAM · 320 GB HDD · 250 GB HDD · DVD CD/ROM Drive · DVD CD/ROM Drive · Wi-Fi AC and Bluetooth · Wi-Fi AC and Bluetooth · Ethernet · Ethernet · Touch Screen · Touch Screen · NetMotion Wireless Mobility client · NetMotion Wireless Mobility client · Mobile Communications · Mobile Communications o Verizon 4G LTE data services o Verizon 4G LTE data services

3.1.1.1 New Mobile data standards in the City of Columbus environment includes the following:

Panasonic CF-33 Tablet Panasonic FZ-55 Laptop

2 PAGE · Core I7-10810U 1.1GHZ (4.9GHZ) · Core i7-8665U 1.9GHz · Windows 10 Professional – 64-bit OS · Windows 10 Professional – 64-bit OS · 16 GB RAM · 16 GB RAM · 512 GB OPAL SSD · 512 GB SSD · Intel Wi-Fi 6 and Bluetooth · Intel Wi-Fi 6 and Bluetooth · Ethernet · Ethernet · Touch Screen · Touch Screen · NetMotion Wireless Mobility client · NetMotion Wireless Mobility client · Mobile Communications · Mobile Communications o Verizon 4G LTE data services o Verizon 4G LTE data services

3.1.2 NETWORK: The City’s network is built on a high speed 100gb ethernet core with redundant failover to multiple internet service providers over the 1,000+ mile private fiber network. Police substations are currently connected on dedicated 1gb/s links to the core network. Individual Police substations also include Wi-Fi (802.11) radio coverage. The City operates two main data centers at different locations that provide the core infrastructure services and redundancy. The City compute infrastructure capacity includes redundant failover Dell VXRail hyperconverged clusters with support for over 2,000 virtual machines. The current storage environment includes redundant NetApp storage arrays of 1.5PB each. The purpose-built storage arrays include a high-speed SSD ingestion layer and a tier 3 storage layer. In addition, the NetApp storage arrays can be integrated with commercially available cloud storage to allow for a third layer of redundancy.

 TCP/IP is the only protocol permitted in the routed environments.

 Multicast network is IGMP/CGMP sparse mode IEEE RFC 2932

 Required to utilize DNS for name resolution

 DHCP with Dynamic DNS Update provisions the majority of IP

 The WAN encompasses over 200 facilities/sites using one or more of the following transports:

 All sites on City of Columbus fiber - 1G

 Only 1 Police facility is on VPN (35mb/5mb)

 Internet edge includes multiple connections through different providers as follows:

 Inbound internet pipe for City’s e-commerce – Multihomed environment. 100 mbps & 180 mbps

 Outbound internet pipe for City access to the internet - Multihomed environment. 100 mbps & 180 mbps

3.1.3 SERVER: The City’s server infrastructure is built on an Enterprise Scalable HyperConverged Model, incorporating industry Best-Practices. The City standard for server and block storage equipment is Dell VXRail. The City standard for file storage is Dell PowerScale. The Core Network is 10Gbps capable running with Juniper QFX-10K network underlay. Additional City standards include VMWare hypervisor 6.7 with NSX, Microsoft SQL server 2019, Oracle 19c, Microsoft Windows server 2019 operating systems, and RedHat Enterprise Linux 7.0 operating systems. Also in place is a Brocade fiber channel environment for high-speed data transmission for standalone storage arrays such as NetApp and EMC VNX. Full redundancy is incorporated to both data centers to protect from equipment or service malfunctions. Any adjustments must be approved by the Department of Technology.

3 PAGE 4.0 SPECIFICATIONS 4.1 General Information

4.1.1 Term: The City will negotiate a term with the selected vendor for a term of up to three (3) years with an option for two successive annual extensions for a potential total contract award of no less than three (3) years and no longer than (five) 5 years.

4.1.2 Quantity Estimate: The City anticipates purchasing 2,300 BWC’s in 2021. The City anticipates purchasing 400 IC Systems in 2021. Any estimate made in this document or by any other representative of the City are not to be construed as representing an actual order(s) or a guarantee that any minimum amount will be purchased.

4.1.3 Universal Term Contract: This proposal is offeror's offer to sell the item(s) set forth in its proposal, under the terms and conditions of this proposal. Offeror is to take notice that the City makes no warranties or representations that the estimated quantity, or any quantity at all, will be ordered by the City even though Offeror’s proposal is accepted by the City and a firm offer for sale executed.

If Offeror’s proposal is accepted by the City and the firm offer for sale is executed the Offeror is to take further notice that no act, failure to act, or order placed by the City or by any official, employee or agent of the City shall constitute an order or contractually bind the City without the proper certificate by the City Auditor that funds sufficient for full payment due on any order are available. Each order placed under the firm offer for sale shall require execution of a purchase order. Therefore, in consideration of one (1) dollar received by the awarded Offeror, said bidder shall offer to sell buyer, City of Columbus, who shall have the Contract Term to exercise this option to purchase, at the price and on the terms set forth in the negotiated agreement arising from this proposal.

The City shall not be precluded from buying similar items from other suppliers, or the same items in the event of an emergency. In the event of an overlap in the annual term of subsequent Universal Term Contracts, the City may purchase the desired item from either awarded contract at the City's sole discretion.

4.1.3.1 Written Purchase Order: Written Purchase Orders may be established for the CPD, signed by the Director of Finance and Management, referencing the terms of this contract, and specifying items to be delivered and the delivery locations. Any number of written purchase orders may be issued at the discretion of the city to increase or decrease available funds during the term of the agreement. At no time shall the maximum obligation of the City agency exceed the cumulative dollar amount of associated purchase orders. Any available funds balance not obligated by the City for accounts payable on items/work ordered on or prior to that date shall be cancelled after that date.

4.1.4 Non-disclosure: The contractor agrees that no information will be disclosed to third parties or published in case studies, advertisements, white papers, customer testimonials, trade publications without the express, written consent of the City.

4.2 BVP Overview

The Offeror’s response to this BVP should be a clear and concise description of the Offeror’s capabilities and proposed offerings. The BVP will be evaluated using (1) the competence of the offeror to perform under the contract as indicated by the technical expertise, training, education and experience of the Offeror's personnel who would be assigned to perform the work; (2) past performance of the Offeror as reflected by evaluations of the city agency, other city agencies and other previous clients of the offeror with respect to such factors as quality of work, success in controlling costs, and success in meeting deadlines; (3) the quality and feasibility of the Offeror's technical proposal; (4) the ability of the offeror to perform under the contract competently and expeditiously as indicated by the Offeror's workload and the availability of necessary personnel, equipment and facilities; and (5) overall cost for the proposed solution, expressed as a total cost of ownership over a period of five-years.

Each of these factors are to be responded to in the manner described herein. After a review of the responses to the BVP, including the proposed investment, selected offerors will be invited to participate in a six (6) week trial evaluation by CPD and city personnel. The six (6) week trial evaluation will require selected offerors to design, set-

4 PAGE up, train, and implement a portion of their solution for evaluation purposes. An evaluation committee will review all offeror’s products and services and will separately score usage outcomes. The outcome of the trial evaluation will be combined with the BVP proposal review to select Offerors who will enter the negotiation phase with the goal of a contract award. At the end of the trial all participants will be expected to provide all video files captured during the trial to the City of Columbus in machine readable format (DVD, USB, hard-drive, file transfer compatible with MPEG-4 (preferred) or other non-proprietary format, e.g. MPEG-3, WMV, AVI.

Any costs incurred by the offeror because of the trial evaluation are the responsibility of the offeror. The City will not pay for or reimburse any costs associated with the trial.

4.2.1 Process Summary: The City will appoint an evaluation committee to evaluate proposals received. The committee will evaluate all Offerors and proposals received and rank the offerors based upon the evaluation criteria specified in the BVP for completeness, benefit, and costs. The committee may then select two (2) or more of the highest qualified Offerors with which to conduct the six (6) week trial. The trial may include, but are not limited to, presentations by the Offerors to the committee to elaborate upon their qualifications, proposals, and/or other pertinent information, and the outcomes from the trial evaluation. Based upon the content of the proposals received including any revisions thereto, and upon any additional discussions with the Offerors the committee shall rank the remaining offerors based upon the evaluation criteria specified in the BVP. The committee shall submit its ranking of the Offerors along with a written explanation to the Finance and Management Director. The Finance and Management Director in consultation with the Public Safety Director shall select the Offeror(s) with which to enter contract negotiations. If negotiations fail, negotiations with these offeror(s) shall be terminated, and the city agency may enter contract negotiations with another Offeror.

4.2.2 BVP Sequence of Events: The following BVP sequence of events represents the City’s best estimate of the schedule that will be followed. Exact times for questions / answers and due date (on the BVP cover page) are noted in this document and will be published on Bonfire and in the City Bulletin:

- BVP Issued June 29, 2021 - Deadline for written questions: July 20, 2021 - City response to questions: July 27, 2021 - Proposals Due: August 6, 2021 - Notification of semi-finalists: approximately 20-30 days after proposals received - Presentations to City: approximately 10-15 days after notifications sent - Trial Evaluation: approximately 15 days after conclusion of City presentations - Negotiations begin approximately 10-15 days after Trial Evaluations Complete - Contract completed: approximately 50 days after completed negotiation

4.2.2.1 Specification Questions:

Questions regarding this BVP must be submitted on the Bonfire portal by noon on July 20, 2021. Responses will be posted as asked, no later than noon on July 27, 2021

For additional information concerning this bid, including procedures on how to submit a proposal, you must go to the Bonfire portal web site at https://columbus.bonfirehub.com/projects.

4.2.2.2 Communications: During the proposal and evaluation process, Offerors are strictly prohibited from communicating with any City employees or officers regarding this solicitation except through the method stated immediately above during the Question & Answer Period. Any communication from the vendor to the City after the Question & Answer period should be limited to only what is necessary. Necessary communication required by the City will be communicated clearly to Offerors. If any Offeror has a need to communicate with the City, the communication should come only to the Chair of the Committee. If a City employee attempts to communicate with an Offeror contrary to this provision, the Offeror shall report said incident to the Chair of the Committee. The Chair is Roblyn Slaughter, Procurement Administrative Officer. She can be reached at [email protected] or 614- 645-7651. A violation of this section on the part of the Offeror will lead to disqualification of the Offeror from this BVP.

5 PAGE 4.2.2.3 Proposal Submittal Guidelines

Submit per the instructions on the Bonfire portal.

A separate Microsoft Excel workbook has also been provided for Offerors to submit their business and technical responses to this BVP in Attachment A. Completion of Attachment A is mandatory.

4.2.3 Evaluation Criteria:

4.2.3.1 Section One – Competence (10 points): The competence of the Offeror to perform the required service and provide the required goods, as indicated by the technical training, education and experience of the Offeror's personnel who would be assigned to perform the work.

4.2.3.2 Section Two – Past Performance (20 points): The past performance of the Offeror as reflected by evaluations of the city agency, other city agencies and other previous clients of the Offeror with respect to such factors as quality of work, success in controlling costs, and success in meeting deadlines.

4.2.3.3 Section Three – Quality and Feasibility (30 points): The quality and feasibility of the Offeror's technical proposal. Offeror will demonstrate through the conversion of the BVP technical specifications into detailed line drawings and documents that clearly explain how the Offeror meets the operational needs expressed by the preferences of the technical specifications. The committee will give points to Offerors who clearly demonstrate their compliance with the needs defined in the technical specifications. If the Offeror does not include a specific item preferred in the technical specification, the Offeror will be scored based on its ability to demonstrate how its offer meets the high-quality demands of the refuse service industry and the feasibility of Offeror’s proposed solution.

4.2.3.4 Section Four – Ability (15 points): The ability of the Offeror to perform the required service competently and expeditiously as indicated by the Offeror's workload and the availability of necessary personnel, equipment, and facilities.

4.2.3.6 Section Six – Cost (25 points) – Overall cost for the proposed solution, expressed as a total cost of ownership over a period of five-years.

4.3 Section One – Competence (10 points):

Provide sufficient information in a clear, concise manner to the City to evaluate the competence of Offeror to perform the requested services. Information in Section One should include the following:

4.3.1 If your company has changed its name in the past 5 years, also list the previous name(s). 4.3.2 Is your company a division or subsidiary of another organization? If so, what is the name of your parent company? 4.3.3 Describe the products and services offered by your company. 4.3.4 Is your company publicly traded or privately held? For public companies, provide a link to your most recent annual and quarterly financial reports. For privately held companies, provide your full-time employee count, your most recent full-year revenue, and your most recent quarterly revenue. Please note that private companies may be requested to provide financial statements at a future point in time upon request by the City. 4.3.5 What is the total number of years your company has been in business? 4.3.6 What is the total number of years your company has implemented public safety video solutions? How long has the solution been available? 4.3.7 Describe the strategic direction for the product line including any planned major enhancements. Include a product roadmap for the duration of warranty and product life with life cycles of all equipment provided. The City is willing to non-disclosure agreements to gain better insights into offerors roadmap for their product line. 4.3.8 Describe any industry awards, articles, or third-party evaluations of your public safety video (BWC and IC system) products. Attach a copy of any articles or third-party evaluations of your products. 4.3.9 Describe at a high-level the key differentiating, or highly innovative aspects of your solution compared to leading competitors. 4.3.10 Describe the projected life cycle of the proposed solution, including any expected end-of-support for any of the proposed product or components. Include which components and/or features can be upgraded.

6 PAGE 4.3.11 In what country are you incorporated, and what is the location of your corporate headquarters? If you have regional headquarters in multiple regions in the United States, please list those and your closest office to the City of Columbus as well 4.3.12 What is the total number of full-time employees dedicated to providing public safety video solutions in North America? 4.3.13 Please list your DUNS Number if available. 4.3.14 Is your company a "Minority Business Enterprise (MBE)?" If so, please send all appropriate certifications along with your response with your BVP response. 4.3.15 Will you use sub-contractors and/or third-part party companies in your implementation or installations? If yes, please list the name(s), address(es) and contact information. 4.3.16 Are you the original equipment manufacturer or publisher, the OEM for all the products included within your proposal? If not, please provide the name of the original equipment manufacturer(s), publishers or suppliers of the proposed system components not made by you. For example, the camera manufacturer, software publisher or commercial cloud provider. If multiple manufacturers are involved, please list each one and the component(s) or services used from them. 4.3.17 For the items where you are not the OEM in 4.3.16 above, do you hold any certifications, or belong to any partner programs, for this OEMs used? If so, describe your certification level or relationship with the OEM. 4.3.18 Please list all relevant industry or consulting partnerships related to your proposal. 4.3.19 Please describe your company’s overall market position in the public safety (BWC and IC) video market. What is your approximately market share in your current and prior fiscal year?4.3.20 Explain various stages of your company’s hiring process. What skills do you require employees to possess to work for your team on projects of this complexity? 4.3.21 Explain the process used by your company to select contracted staff. What do you require of a contractor to make them a part of your team on a project of this complexity? 4.3.22 List and explain the various subcontracted staff you plan to use on this project. 4.3.23 What is the average tenure of your employees company-wide? What is the average tenure of the employees you plan to assign to this project? 4.3.24 Explain your company’s strategy to deal with turnover of staff as it relates to providing service to your clients. 4.3.25 Explain the training services you provide your staff to ensure their expertise is relevant as technology changes. How does this affect your cost structure and prices?

4.4 Section Two – Past Performance (20 points):

Provide sufficient information in a clear, concise manner to the City to evaluate the competence of Offeror to perform the requested services. Information in Section Two should include the following:

4.4.1 Please describe any existing or pending business arrangements your firm may have with City or any of its personnel. 4.4.2 Are you a current or former supplier to us, or any of our city departments? If "yes", please list the date or date ranges of business conducted and the products or product categories. 4.3.3 What is the total number of current government clients or customers in the United States for all products and services of your company? 4.3.4 What is the current number of clients or customers you have implemented and are in production, and/or are currently in the process of implementing for public safety video solutions (BWC and IC systems) in the United States? 4.4.5 How many total units or licenses of body-worn cameras have been sold to date by your company? List the first year body- worn cameras were sold by your company. How many unique body-worn cameras local, state, or federal government customers have purchased body-worn cameras from your company? 4.4.6 How many total units or licenses of in-car camera systems have been sold to date by your company? List the first year in-car systems were first sold by your company. How many unique body-worn cameras local, state, or federal government customers have purchased in-car camera systems from your company? 4.4.7 Does your company have a Net Promotor Score or NPS? If yes, please provide your current NPS. 4.4.8 Has your company been involved in any contracts which were ended due to termination for cause, any unresolved claims, any litigation, or arbitration with the City of Columbus and/or one of our city departments in the past 5 years, or any other local, state, or federal government agency in the United States? If "yes," provide details. 4.4.9 Please return Past Performance Questionnaires included at the end of this document from four of your company’s prior or current clients.

4.5 Section Three – Quality and Feasibility (30 points):

Scope: Provide detailed information in a clear, concise manner addressing each of the technical and solution specifications in the categories listed below to determine quality and feasibility of the proposed solution.

7 PAGE The proposal shall not include components, or finished units that are of a prototype nature, or have not been in production for a sufficient period to prove their performance capabilities. If the proposal includes components, or finished units that are of a prototype nature, or have not been in production for a sufficient period to prove their performance capabilities, this shall be clearly indicated. The City will determine the acceptability of any proposal of prototype equipment. The Offeror shall clearly describe any parts of its proposed solution products or services which are currently not sold or supported by the Offeror as part of their standard product offering for purchase at the time their BVP was submitted to the City.

Offerors shall submit with their proposal detailed drawings, logical diagrams and build sheets clearly showing all the necessary components of the turnkey BWC and IC solution as required in the sections below. Offerors may also submit with their proposal’s descriptive literature, brochures, and other technical details as its discretion.

The technical response includes the following components and references various industry standards (see included Generic Camera Reference Architecture reference sheet):

4.5.1 Body-Worn Cameras (BWC) 4.5.2 In-Car Camera Systems (IC) 4.5.3 Evidence Management and Streaming 4.5.4 Use of Existing City Assets 4.5.5 Security 4.5.6 Availability and Disaster Recovery 4.5.7 Support, Maintenance and Warranty

4.5.1 Body-Worn Cameras (BWC)

4.5.1.1 Camera Features

4.5.1.1.1 What is the model number of the proposed camera, model name and stock keeping unit? 4.5.1.1.2 What are the dimensions (height, width, and depth) of the proposed camera in inches? e.g., 3”H x 2.5” W X 1.5” D 4.5.1.1.3 What is the weight of the proposed camera in ounces? e.g., 8 ounces. 4.5.1.1.4 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? e.g. -40°F to 140°F. 4.5.1.1.5 What is the MIL SPEC rating of the camera? e.g., MIL-STD-810G 4.5.1.1.6 What is the Ingress Protection (IP) Rating of the Camera? e.g., IP67 4.5.1.1.7 The Offeror shall provide individual product specifications, datasheets, technical specification documents or "cut sheets" for each body-worn camera product proposed.

4.5.1.2 Camera Lens

4.5.1.2.1 What is the horizontal field of view of the camera lens specified in degrees? e.g., 120° horizontal. 4.5.1.2.2 What is the vertical field of view of the camera lens specified in degrees? e.g., 70° vertical. 4.5.1.2.3 Specify the range of motion for the camera lens vertically up or down in degrees, e.g., 10° and 20° up. 4.5.1.2.4 Does the camera automatically remove the fisheye effect, otherwise known as vertical dewarping? 4.5.1.2.5 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux, e.g., 1lux.

4.5.1.3 Video Recording Features

4.5.1.3.1 List the Codecs supported by the camera for video and audio recording, e.g., H265. 4.5.1.3.2 Is the camera compliant with H.264 also known as MPEG-4 Part 10, Advanced Video Coding (MPEG-4 AVC) yes, or no? 4.5.1.3.3 List the H.264 profiles supported. 4.5.1.3.4 Specify the maximum number of vertical pixels that can be read by the image sensor. 4.5.1.3.5 Specify the maximum size of the digital image sensor in number of vertical pixels of the sensor. 4.5.1.3.6 Specify the pixel size of the sensor in micrometers (μm).

8 PAGE 4.5.1.3.7 For each of the video formats listed below, provide whether supported (yes or no), the Horizontal X Vertical Resolution Supported in pixels, e.g., 1980H x 1080V, the frame rates supported in frames per second (FPS) from lowest to highest, e.g., 24 fps, 30 fps, and 60 fps, and the bit depth per RGB sensor, e.g., 10-bits. 4.5.1.3.7.1 4K Ultra High Definition 4.5.1.3.7.2 1080p Full High Definition 4.5.1.3.7.3 720p Standard Definition 4.5.1.3.7.4 480p 4.5.1.3.7.5 Other supported video formats – specify each. 4.5.1.3.8 Can the frames rates for various video formats in 4.5.1.3.7? be configured by the customer? 4.5.1.3.9 For the video formats supported in 4.5.1.3.7., what are the typical compression ratios for common raw bit streams? Describe the compression profiles (e.g., Scalable High Profile) for each in terms of the raw number of uncompressed bits per second, expressed as megabytes (MB), e.g., 100MB, the compressed number of bits per second, expressed as megabytes (MB), e.g., 50MB, and the computed compression ratio equal to the number of compressed megabytes per second ÷ the number of uncompressed megabytes per second. Each video format may have more than one compression profile, e.g., low, medium, or high compression: 4.5.1.3.9.1 4K Ultra High Definition 4.5.1.3.9.2 1080p Full High Definition 4.5.1.3.9.3 720p Standard Definition 4.5.1.3.9.4 480p 4.5.1.3.9.5 Other supported video formats – specify each. 4.5.1.3.10 Describe any digital rights management capabilities of the camera for protecting access to individual files. 4.5.1.3.11 Describe how the device separates the start and ending of a video so users do not accidently confuse the two different functions

4.5.1.4 Pre- and Post-Event Recording, Background Recording Pre-event recording records video and/or audio prior the putting the camera into a recording state by the end-user.

4.5.1.4.1 Does the camera provide for configurable recording of video and audio prior to the record function being initiated by the end-user? (yes or no) 4.5.1.4.2 Can the length of pre-event video and audio recording be configured separately by the customer? (yes or no) 4.5.1.4.3 What is the total length of pre-event video recording in minutes, and what lengths can be configured? E.g., 2 minutes, 1.5 minutes, 1 minute, .5 minutes, 0 minutes. 4.5.1.4.4 What is the total length of pre-event audio recording in minutes, and what lengths can be configured? e.g., 2 minutes, 1.5 minutes, 1 minute, .5 minutes, 0 minutes.

Post-event recording records video and/or audio after setting the cameras recording state to non-recording, e.g., turning it off.

4.5.1.4.5 Does the camera provide for configurable recording of video and audio after to the record function has been turned off by the end-user? (yes or no) 4.5.1.4.6 Can the length of post-event video and audio recording be configured separately? (yes or no) 4.5.1.4.7 What is the total length of post-event video recording in minutes, and what lengths can be configured? e.g., 10 minutes, 20 minutes, 30 minutes, 60 minutes. 4.5.1.4.8 What is the total length of post-event audio recording in minutes, and what lengths can be configured? e.g., 10 minutes, 20 minutes, 30 minutes, 60 minutes. 4.5.1.4.9 Describe any features where officers can recover recordings in the event, they did not initiate recording when expected. What is the duration of the recording that is recovered from the time the recovery recording function is turned on in minutes? e.g., 45 minutes.

Background recording records video and audio while the camera is powered on regardless of whether the camera record button has been initiated by and end-user.

4.5.1.4.10 Does the camera provide for background recording? (yes or no) 4.5.1.4.11 Can the background recording be turned on or off? (yes or no) 4.5.1.4.12 Is the background recording configured by the officer or by the administrator? 4.5.1.4.13 What is the video and audio resolution of background recording, Describe the configuration and compression options of Codecs, resolution and frame rates of background video and audio? 4.5.1.4.14 What is the duration in hours of background recording for the proposed camera? e.g., minutes, hours? 9 PAGE 4.5.1.4.15 What is the process for transferring background recordings to the evidence library or video storage? Is this part of the normal transfer process by officers, or are there unique controls or circumstances that must be implemented to transfer background recordings? Please describe.

4.5.1.5. Automated Recording Activation, Sensors, Synchronization and Streaming Automated recording activates the recording function of the camera without any input from the officer, including those initiated by sensors or a person who activates the camera remotely.

4.5.1.5.1 Method 1 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.1.5.2 Method 2 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.1.5.3 Method 3 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.1.5.4 Method 4 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.1.5.5 Method 5 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.1.5.6 Method 6 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.6.1.5.7 Describe any end-user reported issues, entries into your helpdesk or support system or known problems with camera automated activation. Examples may include technology pairing or radio frequency caused problems, sensor failure or other issues.

4.5.1.6 Synchronization and Streaming Synchronization includes matching the time signature of active recordings of other cameras in proximity to the camera, including other cameras whether body-worn or in-car.

4.5.1.6.1 Does this camera provide synchronization with other cameras? Please describe. 4.5.1.6.2 Does synchronization include time synchronization? 4.5.1.6.3 Describe any other synchronization capabilities of the camera or solution, including the process to synchronize. 4.5.1.6.4 Describe any end-user reported issues, entries into your helpdesk or support system or known problems with camera automated synchronization. Examples may include technology pairing or radio frequency caused problems, sensor failure or other issues.

Streaming sends the compressed video and audio bit stream over a network connection to a remote video streaming service that allows the bit stream to be viewed remotely.

4.5.1.6.5 Does the camera provide for live bit streaming of video and audio? Please describe. 4.5.1.6.6 Is the bit stream transmitted at the camera's source video and audio resolution and frame rate? 4.5.1.6.7 If the network capacity to live stream the camera's source video is less than needed to transmit the source signal in real time (it is deprecated), describe how this is managed to ensure that the viewer can continue to watch the live stream. Describe what methods are used. 4.5.1.6.8 What happens to live streams originating from the camera when the network connection to the live streaming server is unavailable? 4.5.1.6.9 If the bit stream is transmitted at a lower resolution and frame rate than the camera's source resolution and frame rate, specify the codec used, resolution and frame rate. E.g., H.264 120 H x 720V, 20 fps 4.5.1.6.10 What is the network transfer protocol used to transmit the compressed bit stream, e.g., RTMP? 4.5.1.6.11 What wireless network methods are used for live streaming? e.g., 802.11, 4G LTE 4.5.1.6.12 Can live streaming be achieved with local camera recording turned off? Please describe. 4.5.1.6.13 In your company’s view, should live streaming be implemented with camera recording turned off? What are the implications for evidence quality of turning off local recording? 4.5.1.6.14 In what circumstances are recordings transmitted from the camera and live streamed, and then stored on a video server at a lower quality (reduced video resolution, frame rate or lost information) than the source video recorded on the camera's local storage? 4.5.1.6.15 If live streaming is recorded to a video server at a lower quality and the local recording on the camera is a higher quality, how are the two versions reconciled in the evidence management solution? 10 PAGE 4.5.1.7 Audio Recording Features

4.5.1.7.1 Specify the audio codecs supported, e.g., AAC. 4.5.1.7.2 Describe how wind noise is minimized for audio recording. 4.5.1.7.3 Describe how audio recording components, such as microphones are protected from water infiltration. 4.5.1.7.4 Describe any unique characteristics of the camera's audio recording capabilities.

4.5.1.8 Battery Functions

4.5.1.8.1 Specify the battery type or chemical composition, e.g., Lithium Polymer. 4.5.1.8.2 If the proposed camera has a removable/replaceable battery, what are the dimensions of the removable battery (height, width, depth) in inches? 4.5.1.8.3 If the proposed camera has a removable/replaceable battery, what are the combined dimensions (height, width, and depth) of the camera and battery in inches? 4.5.1.8.4 Describe any unique characteristics of the camera's audio recording capabilities. 4.5.1.8.5 If the proposed camera has a removable/replaceable battery, what is the combined weight of the camera and battery in ounces? 4.5.1.8.6 What are the available methods for recharging the battery? Describe each. 4.5.1.8.7 What is the approximate time to recharge the battery to 100% for each method of recharging the battery? If applicable, specify the USB Battery Charging Standard release name, and volts and amps supported, e.g., USB-C, Revision 2.0 5 V, 3A 4.5.1.8.8 What is the storage capacity of the battery in milliampere hours or mAh? 4.5.1.8.9 On a fully charged battery, how many hours can the camera operate in standby mode, continual recording, or background recording, or with typical use? Please Describe.

4.5.1.9 Camera Screens and Operating Functions

4.5.1.9.1. Does the camera have a display screen? 4.5.1.9.2. What is the size of the screen in horizontal x vertical pixels? 4.5.1.9.3. What type of display screen is included, e.g., LCD, IPS, TFT, etc.? 4.5.1.9.4. Specify the number of colors supported on the camera's display screen. 4.5.1.9.5. Does the camera include a speaker? What is the size and number of speakers? 4.5.1.9.6. What control functions are installed on the camera, please describe the physical?

4.5.1.10 Camera Storage

4.5.1.10.1 Specify the storage medium for video and audio file storage on the camera. e.g., non-volatile computer memory (flash). 4.5.1.10.2 Specify the total amount of useable storage in the camera in megabytes of MB. 4.5.1.10.3 Specify the storage capacity of the camera for 4K UHD video in hours of recording. 4.5.1.10.4 Specify the storage capacity of the camera for 1080p HD video in hours of recording. 4.5.1.10.5 Specify the storage capacity of the camera for 720p HD video in hours of recording. 4.5.1.10.6 Specify the storage capacity of the camera for 480p SD video in hours of recording. 4.5.1.10.7 Specify the storage formats of other formats identified in 4.5.1.3.7.5 above. 4.5.1.10.8 Specify the read/write transfer speed of the storage reads or writes in megabits per second or in the format MB per second read, MB per second write. 4.5.1.10.9 Specify the file management system for the camera storage, e.g., MS-FAT. 4.5.1.10.10 Are files 'at rest' encrypted? Specify the cypher and key strength of files recorded at rest.

4.5.1.11 Network and Telecommunications Features 4.5.1.11.1 What methods can be used to read and transfer stored video and audio from the camera's storage drive? 4.5.1.11.2 USB, Specify version and transfer speed. 4.5.1.11.3 802.3 ethernet, specify speed supported in megabits per second. 4.5.1.11.4 802.11 wireless fidelity, specify the protocols supported, 802.11 a, b, g, n, ac etc. 4.5.1.11.5 Does the camera include a cellular radio? 4.5.1.11.6 If yes, is the cellular radio fixed, or installed via a removable SIM card? 11 PAGE 4.5.1.11.7 Specify the network compatibility for the following: 4.5.1.11.7.1 GMS 4.5.1.11.7.2 CDMA 4.5.1.11.7.3 CDMA/TDMA 4.5.1.11.7.4 UMTS 4.5.1.11.7.5 4G LTE and/or LTE Advanced 4.5.1.11.7.6 5G eMBB 4.5.1.11.7.7 5G URLLC 4.5.1.12.7.8 5G mMTC 4.5.1.12.7.9 5G CBRS

4.5.1.11.8 Specify the name of the cellular carriers supported: 4.5.1.11.8.1 Carrier 1 4.5.1.11.8.2 Carrier 2 4.5.1.11.8.3 Carrier 3 4.5.1.11.8.4 Carrier 4 4.5.1.11.8.5 Carrier 5 4.5.1.11.8.6 Carrier 6 4.5.1.11.8.7 Carrier 7 4.5.1.11.9 Can the camera be integrated with an in-car systems DVR or VPU or the in-car MDC to transmit recordings over the DVR or VPU or MDC's data connections? Please describe either or both capabilities. 4.5.1.11.10 Are bit streams sent over a telecommunications network encrypted in transit? Indicate the cypher and key strength.

4.5.1.12 Accessories, Mounts, and Additional Features

4.5.1.12.1 Describe the mounting options for body-worn camera specified below: 4.5.1.12.1.1 Mounting Option 1 4.5.1.12.1.2 Mounting Option 2 4.5.1.12.1.3 Mounting Option 3 4.5.1.12.1.4 Mounting Option 4 4.5.1.12.1.5 Mounting Option 5 4.5.1.12.2. Do existing CPD uniforms need to be modified to utilize the camera specified? 4.5.1.12.3. Do existing CPD uniforms need to be replaced to utilize the camera specified? 4.5.1.12.4. Do existing CPD uniforms accepts the mounts for the camera specified without modification? 4.5.1.12.5. Describe any accessories for the camera below. 4.5.1.12.5.1 Accessory 1 4.5.1.12.5.2 Accessory 2 4.5.1.12.5.3 Accessory 3 4.5.1.12.5.4 Accessory 4 4.5.1.12.5.5 Accessory 5 4.5.1.12.6. Describe any additional or unique features of the body-worn camera system specified. 4.5.1.12.6.1 Feature 1 4.5.1.12.6.2 Feature 2 4.5.1.12.6.3 Feature 3 4.5.1.12.6.4 Feature 4 4.5.1.12.6.5 Feature 5 4.5.1.12.7 Please list any features in your proposed body-worn camera system which serves to enhance officer safety.

4.5.2 In-Car Camera Systems (IC)

4.5.2.1 In-Car Video System Features

Describe the overall in-car video recording architecture or configuration. Is there a single or multiple components? What are the basic components, what functions do they provide, and how do they inter-connect with each other?

12 PAGE 4.5.2.2 Is video and audio recording for all in-car cameras recorded to a single device such as a digital video-recorder or DVR or video processing unit? 4.5.2. 3 If video and audio for an in-car system recorded by cameras is NOT stored on a separate digital video-recorder or video processing unit, where are video and audio files stored? 4.5.2.4 Describe each of the main system components being proposed, including their name, model number and stock keeping unit for each. Add additional lines if necessary and continue the number system below. The Offeror shall provide individual product specifications, datasheets, technical specification documents or "cut sheets" for each main In-car system component proposed. 4.5.2.4.1 Component 1, Name 4.5.2.4.2 Component 2, Name 4.5.2.4.3 Component 3, Name 4.5.2.4.4 Component 4, Name 4.5.2.4.5 Component 5, Name 4.5.2.4.6 Component 6, Name 4.5.2.4.7 Component 7, Name 4.5.2.4.8 Component 8, Name 4.5.2.4.9 Component 9, Name 4.5.2.4.10 Component 10, Name 4.5.2.4.11 Component 11, Name

4.5.2.2 Digital Video-Recorder (DVR) or Video Processing Unit (DPU) Systems 4.5.2.2.1 What is the size of the DVR or VPU measured in ISO 7736 dashboard mounted head units or DIN? 4.5.2.2.2 What is the total size of the DVR or VPU expressed as (height, width, and depth) in inches? 4.5.2.2.3 What is the size of the DVR or VPU without the front bezel or faceplate installed expressed as (height, width, and depth) in inches? 4.5.2.2.4 What is the size of the front faceplate for the DVR or VPU expressed as height x width in inches? 4.5.2.2.5 What is the weight of the DVR or VPU expressed in pounds and/or ounces?

4.5.2.3 In-Car System Display 4.5.2.3.1 Does the DVR/VPU have a display screen? 4.5.2.3.2 What is the size of the screen expressed as (height, width, and depth) in inches? 4.5.2.3.3 What is the weight of the screen in ounces? 4.5.2.3.4 What is the panel type of display screen is included, e.g., LCD, IPS, etc.? 4.5.2.3.5 What is the screen size horizontally, vertically, and diagonally in inches? 4.5.2.3.6 What is the maximum resolution of the screen expressed as horizontal x vertical pixels? 4.5.2.3.7 What are the supported refresh rates of the screen expressed in hertz? 4.5.2.3.8 Specify the number of colors supported on the camera's display screen. 4.5.2.3.9 What is the color gamut or color space of the display? 4.5.2.3.10 What is the viewing angle horizontal and vertically expressed in degrees? 4.5.2.3.11 Does the display screen include any coatings such as anti-glare? Please describe. 4.5.2.3.12 What is the response time of the screen in milliseconds? 4.5.2.3.13 What is the screen brightness measured in candela per square meter or nits? 4.5.2.3.14 What is the aspect ratio of the display? 4.5.2.3.15 What is the native contrast ratio of the screen? 4.5.2.3.16 What is the horizontal tilt range from negative to positive degrees? 4.5.2.3.17 What is the vertical tilt range from negative to positive degrees? 4.5.2.3.18 What information is indicated in the display's screen, describe the functions, or use of the screen? 4.5.2.3.19 How many cameras can be viewed on the screen at one time? 4.5.2.3.20 How many audio sources can be heard at one time? 4.5.2.3.21 Does the in-car display include a speaker? 4.5.2.3.22 What is the size and number of speakers? 4.5.2.3.23 What control functions are installed on the screen, please describe the physical affordances (buttons, indicators) and their functions? 4.5.2.3.24 What is the vehicle mounting options for the display screen?

4.5.2.4 Video Recording Features

13 PAGE 4.5.2.4.1 How many simultaneous, concurrent video streams from individual video cameras can be recorded simultaneously including the number of wired and wireless video interfaces supported? 4.5.2.4.2 Do any cameras support recording at different resolutions simultaneously, if yes, list the resolutions and fps supported 4.5.2.4.3 What codecs are supported by the DVR or VPU for video and audio recording? 4.5.2.4.5 Is the DVR/VPU compliant with H.264 also known as MPEG-4 Part 10, Advanced Video Coding (MPEG-4 AVC) yes, or no? 4.5.2.4.6 List the H.264 profiles supported. 4.5.2.4.7 For each of the video formats listed below, by what camera identified in 4.5.2.4, provide whether supported (yes or no), the Horizontal X Vertical Resolution Supported in pixels, e.g., 1980H x 1080V, the frame rates supported in frames per second (FPS) from lowest to highest, e.g., 24 fps, 30 fps, and 60 fps, and the bit depth per RGB sensor, e.g., 10-bits. 4.5.2.4.7.1 4K Ultra High Definition 4.5.2.4.7.2 1080p Full High Definition 4.5.2.4.7.3 720p Standard Definition 4.5.2.4.7.4 480p 4.5.2.4.7.5 Other supported video formats – specify each. 4.5.2.4.8 Can the frames rates for various video formats be configured by the customer agency? 4.5.2.4.9 For the video formats supported in 4.5.2.4.7, what are the typical compression ratios for common raw bit streams? Describe the compression profiles for each camera identified in 4.5.2.4. (e.g., Scalable High Profile) for each in terms of the raw number of uncompressed bits per second, expressed as megabytes (MB), e.g., 100MB, the compressed number of bits per second, expressed as megabytes (MB), e.g., 50MB, and the computed compression ratio equal to the number of compressed megabytes per second ÷ the number of uncompressed megabytes per second. Each video format may have more than one compression profile, e.g., low, medium, or high compression: 4.5.2.4.9.1 4K Ultra High Definition 4.5.2.4.9.2 1080p Full High Definition 4.5.2.4.9.3 720p Standard Definition 4.5.2.4.9.4 480p 4.5.2.4.9.5 Other supported video formats – specify each.

4.5.2.4.10 Describe any digital rights management capabilities of the camera for protecting access to individual files.

4.5.2.5 Pre- and Post-Event Recording, Background Recording Pre-event recording records video and/or audio prior the putting the camera into a recording state by the end-user. 4.5.2.5.1 For each camera identified in 4.5.2.4, does the camera provide for configurable recording of video and audio prior to the record function being initiated by the end-user? 4.5.2.5.2 For each camera identified in 4.5.2.4, can the length of pre-event video and audio recording be configured separately? 4.5.2.5.3 For each camera identified in 4.5.2.4, what is the total length of pre-event video recording in minutes, and what lengths can be configured? 4.5.2.5.4 For each camera identified in 4.5.2.4, what is the total length of pre-event audio recording in minutes, and what lengths can be configured?

Post-event recording records video and/or audio after setting the cameras recording state to non-recording. 4.5.2.5.5 For each camera identified in 4.5.2.4, does the camera provide for configurable recording of video and audio after to the record function has been turned off by the end-user? 4.5.2.5.6 For each camera identified in 4.5.2.4, can the length of post-event video and audio recording be configured separately? 4.5.2.5.7 For each camera identified in 4.5.2.4, what is the total length of post-event video recording in minutes, and what lengths can be configured? 4.5.2.5.8 For each camera identified in 4.5.2.4, what is the total length of post-event audio recording in minutes, and what lengths can be configured?

Background recording records video and audio while the camera is powered on regardless of whether the camera record button has been initiated. 4.5.2.5.9 For each camera identified in 4.5.2.4, does the camera provide for background recording? 14 PAGE 4.5.2.5.10 For each camera identified in 4.5.2.4, can the background recording be turned on or off? 4.5.2.5.11 For each camera identified in 4.5.2.4, what is the video and audio resolution of background recording, Describe the configuration options of codecs, resolution and frame rates of background video and audio? 4.5.2.5.12 For each camera identified in 4.5.2.4, what is the duration in hours of background recording for the proposed camera? 4.5.2.5.13 For each camera identified in 4.5.2.4, what is the process for transferring background recordings to the evidence library or video storage? Is this part of the normal transfer process by officers, or are there unique controls or circumstances that must be implemented to transfer background recordings? Please describe. 4.5.2.5.14 For each camera identified in 4.5.2.4, describe any features where officers can initiate background recording or recover recordings in the event, they did not initiate recording when expected. What duration of the recording that is recovered from the time recovery recording function is turned on in minutes?

4.5.2.6 Automated Recording Activation, Sensors, Synchronization and Streaming Automated recording activates the recording function of the camera without any input from the officer, 4.5.2.6.1 Method 1 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.2.6.2 Method 2 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.2.6.3 Method 3 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.2.6.4 Method 4 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.2.6.5 Method 5 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.2.6.6 Method 6 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.2.6.7 Describe any end-user reported issues, entries into your helpdesk or support system or known problems with camera automated activation. Examples may include technology pairing or radio frequency caused problems, sensor failure or other issues.

Synchronization includes matching the time signature of active recordings of other cameras in proximity to the camera, including other cameras whether body-worn or in-car. For each camera identified in 4.5.2.4, complete the following: 4.5.2.6.8 Does this camera provide synchronization with other cameras? 4.5.2.6.9 Does synchronization include time synchronization? 4.5.2.6.10 Describe any other synchronization capabilities of the camera. 4.5.2.6.11 Describe any end-user issues, entries into your support system or known problems with camera automated activation or synchronization. Examples may include technology pairing or radio frequency caused problems, sensor failure or other issues.

Streaming sends the compressed video and audio bit stream over a network connection to a remote video streaming service that allows the bit stream to be viewed remotely. 4.5.2.6.12 Does the DVR/VPU provide for bit streaming of the video and audio? 4.5.2.6.13 Is the bit stream transmitted at the camera's source video and audio resolution or frame rate? 4.5.2.6.14 If the bit stream is transmitted at a lower resolution and frame rate that the camera's source resolution and frame rate, indicate the codec used, resolution and frame rate. 4.5.2.6.15 What is the network transfer protocol used to transmit the compressed bit stream? 4.5.2.6.16 What wireless network methods are used for remote streaming? 4.5.2.6.17 Can remote streaming be achieved with camera recording turned off? 4.5.3.6.18 Should remote streaming be implemented with DVR/VPU recording turned off - what are the implications of turning off local camera recording?

4.5.2.7 Audio Recording Features 4.5.2.7.1 Specify the audio codecs supported and audio encoding profile if known. 4.5.2.7.2 How many simultaneous, concurrent audio recording streams can be recorded simultaneously, including the number of wired and wireless audio interfaces supported?

15 PAGE 4.5.2.7.3 What is the frequency response of recorded audio microphones expressed in hertz or megahertz including signal loss in decibels? 4.5.2.7.4 Describe any unique characteristics of the DVR/VPU's audio recording capabilities.

4.5.2.8 DVR/VPU File Storage (Recording Media) 4.5.2.8.1 Does the DVR/VPU have a single storage repository or multiple storage repositories? 4.5.2.8.2 Specify the storage medium types for file storage on the DVR/VPU, including whether they are fixed or removable, and their size, e.g., 2.5” 3.5” eSata HDD, SSD. 4.5.2.8.3 Specify the total amount of useable storage configurations available for each storage drive type in megabytes (MB) 4.5.2.8.4 Specify the computer bus interface types for storage media available for each drive type and their size. 4.5.2.8.5 For each drive type, specify the read/write transfer speed of the storage reads or writes in megabits per second or in the format in MB per second read, in MB per second write. 4.5.2.8.6 Specify any physical or other attributes that increase useful life, or availability of storage drives used within an automobile. 4.5.2.8.7 Describe any redundancy or resiliency features that replicate recording across multiple storage drives to reduce the risk of data loss. Specify any uses of standards for achieving resiliency. 4.5.2.8.8 Does the DVR/VPU provide removable recording media? 4.5.2.8.9 Specify the removable storage type and useable storage. 4.5.2.8.10 Specify the storage capacity in MB of video formats supported by the DPU/VPU. 4.5.2.8.10.1 Specify the total configurable storage capacity of the DVR/VPU for 4K UHD video in hours of recording. 4.5.2.8.10.2 Specify the storage capacity storage capacity of the DVR/VPU for 1080p HD video in hours of recording. 4.5.2.8.10.3 Specify the storage capacity storage capacity of the DVR/VPU for 720p HD video in hours of recording. 4.5.2.8.10.4 Specify the storage capacity storage capacity of the DVR/VPU for 480p SD video in hours of recording. 4.5.2.8.10.5 Other supported video formats 1 - specify - see 4.5.2.4.9.5 above 4.5.2.8.10.6 Other supported video formats 2 – specify - see 4.5.2.4.9.5 above 4.5.2.8.10.7 Other supported video formats 3 – specify- see 4.5.2.4.9.5 above 4.5.2.8.11 Specify the file management system for the DVR/VPU storage media. 4.5.2.8.12 Are files stored on storage medium 'at rest' encrypted? Specify the cypher and key strength.

4.5.2.9 In-Car Video Cameras In the space below describe the types and features of cameras that are installed in-car and connected the DVR or VPU 4.5.2.9.1 Camera Name 1 - 4.5.2.9.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.2 Primary camera viewing angle expressed in degrees. 4.5.2.9.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.4 Secondary camera viewing angle expressed in degrees. 4.5.2.9.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.2.9.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.2.9.7 What is the weight of the proposed camera in ounces? 4.5.2.9.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux 4.5.2.9.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.2.9.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.2.9.11 Does this camera record in complete darkness? 4.5.2.9.12 Does this camera include infrared or IR illumination? 4.5.2.9.13 What camera controls and functions are available directly from the camera? 4.5.2.9.14 What additional controls are available from remote devices such as the display or DVR/VCU? 4.5.2.9.15 Any options for external (outdoor) mounting of video systems to vehicles that cannot accommodate a camera within the interior of the vehicle.

4.5.2.9.2 Camera Name 2 - 4.5.2.9.2.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.2.2 Primary camera viewing angle expressed in degrees. 16 PAGE 4.5.2.9.2.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.2.4 Secondary camera viewing angle expressed in degrees. 4.5.2.9.2.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.2.9.2.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.2.9.2.7 What is the weight of the proposed camera in ounces? 4.5.2.9.2.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.2.9.2.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.2.9.2.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.2.9.2.11 Does this camera record in complete darkness? 4.5.2.9.2.12 Does this camera include infrared or IR illumination? 4.5.2.9.2.13 What camera controls and functions are available directly from the camera? 4.5.2.9.2.14 What additional controls are available from remote devices such as the display or DVR/VCU?

4.5.2.9.3 Camera Name 3 - 4.5.2.9.3.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.3.2 Primary camera viewing angle expressed in degrees. 4.5.2.9.3.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.3.4 Secondary camera viewing angle expressed in degrees. 4.5.2.9.3.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.2.9.3.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.2.9.3.7 What is the weight of the proposed camera in ounces? 4.5.2.9.3.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.2.9.3.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.2.9.3.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.2.9.3.11 Does this camera record in complete darkness? 4.5.2.9.3.12 Does this camera include infrared or IR illumination? 4.5.2.9.3.13 What camera controls and functions are available directly from the camera? 4.5.2.9.3.14 What additional controls are available from remote devices such as the display or DVR/VCU?

4.5.2.9.4 Camera Name 4 - 4.5.2.9.4.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.4.2 Primary camera viewing angle expressed in degrees. 4.5.2.9.4.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.4.4 Secondary camera viewing angle expressed in degrees. 4.5.2.9.4.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.2.9.4.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.2.9.4.7 What is the weight of the proposed camera in ounces? 4.5.2.9.4.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.2.9.4.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.2.9.4.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.2.9.4.11 Does this camera record in complete darkness? 4.5.2.9.4.12 Does this camera include infrared or IR illumination? 4.5.2.9.4.13 What camera controls and functions are available directly from the camera? 4.5.2.9.4.14 What additional controls are available from remote devices such as the display or DVR/VCU?

4.5.2.9.5 Camera Name 5 - 4.5.2.9.5.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.5.2 Primary camera viewing angle expressed in degrees. 4.5.2.9.5.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.5.4 Secondary camera viewing angle expressed in degrees. 17 PAGE 4.5.2.9.5.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.2.9.5.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.2.9.5.7 What is the weight of the proposed camera in ounces? 4.5.2.9.5.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.2.9.5.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.2.9.5.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.2.9.5.11 Does this camera record in complete darkness? 4.5.2.9.5.12 Does this camera include infrared or IR illumination? 4.5.2.9.5.13 What camera controls and functions are available directly from the camera? 4.5.2.9.5.14 What additional controls are available from remote devices such as the display or DVR/VCU?

4.5.2.9.6 Camera Name 6 - 4.5.2.9.6.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.6.2 Primary camera viewing angle expressed in degrees. 4.5.2.9.6.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.2.9.6.4 Secondary camera viewing angle expressed in degrees. 4.5.2.9.6.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.2.9.6.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.2.9.6.7 What is the weight of the proposed camera in ounces? 4.5.2.9.6.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.2.9.6.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.2.9.6.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.2.9.6.11 Does this camera record in complete darkness? 4.5.2.9.6.12 Does this camera include infrared or IR illumination? 4.5.2.9.6.13 What camera controls and functions are available directly from the camera? 4.5.2.9.6.14 What additional controls are available from remote devices such as the display or DVR/VCU?

4.5.2.10 Network and Telecommunications Features 4.5.2.10.1 What methods can be used to read and transfer stored recordings from the DVR/VPU's storage drives? 4.5.2.10.2 How is reading or transfer of stored recordings from the DVR/VPU to the evidence system or enterprise video storage initiated? Manually by the officer, automatically, by other methods? Please describe: 4.5.2.10.2.1 USB, Specify version and transfer speed. 4.5.2.10.2.2 802.3 Ethernet, specify speed supported in megabits per second. 4.5.2.10.2.3 802.11 wireless fidelity, specify the protocols supported, 802.11 a, b, g, n, ac etc. 4.5.2.10.2.4 Does the DVR/VPU include a cellular radio? If yes, is the cellular radio fixed, or installed via a removable SIM card? 4.5.2.10.3 Specify the network compatibility for the SIM cards supported below, yes, or no? 4.5.2.10.3.1 GMS 4.5.2.10.3.2 CDMA 4.5.2.10.3.3 CDMA/TDMA 4.5.2.10.3.4 UMTS 4.5.2.10.3.5 4G LTE and/or LTE Advanced 4.5.2.10.3.6 5G eMBB 4.5.2.10.3.7 5G URLLC 4.5.2.10.3.8 5G mMTC 4.5.2.10.3.9 5G CBRS 4.5.2.10.4. Specify the name of the cellular carriers supported: 4.5.2.10.4.1 Carrier 1 4.5.2.10.4.2 Carrier 2 4.5.2.10.4.3 Carrier 3 4.5.2.10.4.4 Carrier 4 4.5.2.10.4.5 Carrier 5 4.5.2.10.4.6 Carrier 6 18 PAGE 4.5.2.10.4.7 Carrier 7 4.5.2.10.5 Can the DPU/VPU be connected to an in-vehicle Mobile Data Computer or MDC and utilize the MDC's telecommunications capabilities to read and transfer recordings? Please describe the capabilities of using the MDC's data connections. 4.5.2.10.6 Are bit streams sent over a telecommunications network encrypted in transit? If yes, indicate the cypher and key strength. 4.5.2.11 Accessories & Mounts 4.5.2.11.1 Describe any accessories for the in-car system below. 4.5.2.11.1.1 Accessory 1 4.5.2.11.1.2 Accessory 2 4.5.2.11.1.3 Accessory 3 4.5.2.11.1.4 Accessory 4 4.5.2.11.1.5 Accessory 5

4.5.2.12 App Support 4.5.2.12.1 Do you provide a mobile app that can use a device’s internal camera to record video that can be natively uploaded into your video storage environment? 4.5.2.12.2 Does the app support evidence tagging?

4.5.2.13 Additional, Unique Features, and Additional Features 4.5.2.13.1 Describe any additional or unique features of the in-car system specified. 4.5.2.13.1.1 Feature 1 4.5.2.13.2.1 Feature 2 4.5.2.13.3.1 Feature 3 4.5.2.13.4.1 Feature 4 4.5.2.13.5.1 Feature 5 4.5.2.14.1 Please list any features in your proposed in-car camera system which serves to enhance officer safety.

4.5.3 Interview Room Video System (OPTIONAL)

In addition to body-worn and in-car camera video systems, CPD utilizes video and audio recordings within interview rooms at CPD facilities. As such, CPD has in interest in Interview room systems that are integrated with the body-warn and in-car camera systems. In the space below, the Offeror may provide information about its Interview Room Video System Platform. The Offeror shall note that Section 4.5.3. is entirely OPTIONAL and not a required component to be submitted by the Offeror in this BVP. Offerors submitting a response to 4.5.3. will not be awarded any additional points for their submission, nor shall Offerors receive less points for not submitting a response to 4.5.3. Section 4.5.3. is completely voluntary and is an un-scored portion of this BVP.

4.5.3.1 Interview Room Video System (IRVS)

Describe the overall Interview Room video system architecture or configuration. Is there a single or multiple components? What are the basic components, what functions do they provide, and how do they inter-connect with each other? 4.5.3.2 Is video and audio recording for all IRVS cameras recorded to a single device such as a digital video-recorder or DVR or video processing unit? 4.5.3. 3 If video and audio for IRVS recorded by cameras is NOT stored on a separate digital video-recorder or video processing unit, where are video and audio files stored? 4.5.3.4 Describe each of the main system components being proposed, including their name, model number and stock keeping unit for each. Add additional lines if necessary and continue the number system below. The Offeror shall provide individual product specifications, datasheets, technical specification documents or "cut sheets" for each main In-car system component proposed. 4.5.2.4.1 Component 1, Name 4.5.2.4.2 Component 2, Name 4.5.2.4.3 Component 3, Name 4.5.2.4.4 Component 4, Name 4.5.2.4.5 Component 5, Name 4.5.2.4.6 Component 6, Name 19 PAGE 4.5.2.4.7 Component 7, Name 4.5.2.4.8 Component 8, Name 4.5.2.4.9 Component 9, Name 4.5.2.4.10 Component 10, Name 4.5.2.4.11 Component 11, Name

4.5.3.2 Digital Video-Recorder (DVR) or Video Processing Unit (DPU) Systems 4.5.3.2.1 What is the total size of the DVR or VPU expressed as (height, width, and depth) in inches? 4.5.3.2.2 What is the weight of the DVR or VPU expressed in pounds and/or ounces?

4.5.2.3 IRVS Display 4.5.3.3.1 Does the DVR/VPU have a display screen? 4.5.3.3.2 What is the size of the screen expressed as (height, width, and depth) in inches? 4.5.3.3.3 What is the panel type of display screen is included, e.g., LCD, IPS, etc.? 4.5.3.3.4 What is the screen size horizontally, vertically, and diagonally in inches? 4.5.3.3.5 What is the maximum resolution of the screen expressed as horizontal x vertical pixels? 4.5.3.3.6 What are the supported refresh rates of the screen expressed in hertz? 4.5.3.3.7 Specify the number of colors supported on the camera's display screen. 4.5.3.3.8 What is the color gamut or color space of the display? 4.5.3.3.9 What is the viewing angle horizontal and vertically expressed in degrees? 4.5.3.3.10 Does the display screen include any coatings such as anti-glare? Please describe. 4.5.3.3.11 What is the response time of the screen in milliseconds? 4.5.3.3.12 What is the screen brightness measured in candela per square meter or nits? 4.5.3.3.13 What is the aspect ratio of the display? 4.5.3.3.14 What is the native contrast ratio of the screen? 4.5.3.3.15 What is the horizontal tilt range from negative to positive degrees? 4.5.3.3.16 What is the vertical tilt range from negative to positive degrees? 4.5.3.3.17 What information is indicated in the display's screen, describe the functions, or use of the screen? 4.5.3.3.18 How many cameras can be viewed on the screen at one time? 4.5.3.3.1 9 How many audio sources can be heard at one time? 4.5.3.3.20 Does the IRVS display include a speaker? 4.5.3.3.21 What is the size and number of speakers? 4.5.3.3.22 What control functions are installed on the screen, please describe the physical affordances (buttons, indicators) and their functions? 4.5.3.3.23 What are the in-room mounting options for the display screen? Does the Display support Video Electronics Standards Association mount sizes? Please express the size in millimeters vertically and horizontally.

4.5.3.4 Video Recording Features 4.5.3.4.1 How many simultaneous, concurrent video streams from individual video cameras can be recorded simultaneously including the number of wired and wireless video interfaces supported? 4.5.3.4.2 Do any cameras support recording at different resolutions simultaneously, if yes, list the resolutions and fps supported 4.5.3.4.3 What codecs are supported by the DVR or VPU for video and audio recording? 4.5.3.4.4 Is the DVR/VPU compliant with H.264 also known as MPEG-4 Part 10, Advanced Video Coding (MPEG-4 AVC) yes, or no? 4.5.3.4.5 List the H.264 profiles supported. 4.5.3.4.6 For each of the video formats listed below, by what camera identified in 4.5.2.4, provide whether supported (yes or no), the Horizontal X Vertical Resolution Supported in pixels, e.g., 1980H x 1080V, the frame rates supported in frames per second (FPS) from lowest to highest, e.g., 24 fps, 30 fps, and 60 fps, and the bit depth per RGB sensor, e.g., 10-bits. 4.5.3.4.6.1 4K Ultra High Definition 4.5.3.4.6.2 1080p Full High Definition 4.5.3.4.6.3 720p Standard Definition 4.5.3.4.6.4 480p 4.5.3.4.6.5 Other supported video formats – specify each. 4.5.3.4.7 Can the frames rates for various video formats be configured by the customer agency? 4.5.3.4.8 For the video formats supported in 4.5.2.4.7, what are the typical compression ratios for common raw bit streams? Describe the compression profiles for each camera identified in 4.5.2.4. (e.g., Scalable High Profile) for each in terms of the 20 PAGE raw number of uncompressed bits per second, expressed as megabytes (MB), e.g., 100MB, the compressed number of bits per second, expressed as megabytes (MB), e.g., 50MB, and the computed compression ratio equal to the number of compressed megabytes per second ÷ the number of uncompressed megabytes per second. Each video format may have more than one compression profile, e.g., low, medium, or high compression: 4.5.3.4.8.1 4K Ultra High Definition 4.5.3.4.8.2 1080p Full High Definition 4.5.3.4.8.3 720p Standard Definition 4.5.3.4.8.4 480p 4.5.3.4.8.5 Other supported video formats – specify each.

4.5.2.4.9 Describe any digital rights management capabilities of the camera for protecting access to individual files.

4.5.2.5 Pre- and Post-Event Recording, Background Recording Pre-event recording records video and/or audio prior the putting the camera into a recording state by the end-user. 4.5.3.5.1 For each camera identified in 4.5.3.4, does the camera provide for configurable recording of video and audio prior to the record function being initiated by the end-user? 4.5.3.5.2 For each camera identified in 4.5.3.4, can the length of pre-event video and audio recording be configured separately? 4.5.3.5.3 For each camera identified in 4.5.3.4, what is the total length of pre-event video recording in minutes, and what lengths can be configured? 4.5.3.5.4 For each camera identified in 4.5.3.4, what is the total length of pre-event audio recording in minutes, and what lengths can be configured?

Post-event recording records video and/or audio after setting the cameras recording state to non-recording. 4.5.3.5.5 For each camera identified in 4.3.2.4, does the camera provide for configurable recording of video and audio after to the record function has been turned off by the end-user? 4.5.3.5.6 For each camera identified in 4.3.2.4, can the length of post-event video and audio recording be configured separately? 4.5.3.5.7 For each camera identified in 4.3.2.4, what is the total length of post-event video recording in minutes, and what lengths can be configured? 4.5.3.5.8 For each camera identified in 4.3.2.4, what is the total length of post-event audio recording in minutes, and what lengths can be configured?

Background recording records video and audio while the camera is powered on regardless of whether the camera record button has been initiated. 4.5.3.5.9 For each camera identified in 4.5.3.4, does the camera provide for background recording? 4.5.3.5.10 For each camera identified in 4.5.3.4, can the background recording be turned on or off? 4.5.3.5.11 For each camera identified in 4.5.3.4, what is the video and audio resolution of background recording, Describe the configuration options of codecs, resolution and frame rates of background video and audio? 4.5.3.5.12 For each camera identified in 4.5.3.4, what is the duration in hours of background recording for the proposed camera? 4.5.3.5.13 For each camera identified in 4.5.3.4, what is the process for transferring background recordings to the evidence library or video storage? Is this part of the normal transfer process by officers, or are there unique controls or circumstances that must be implemented to transfer background recordings? Please describe. 4.5.3.5.14 For each camera identified in 4.5.3.4, describe any features where officers can initiate background recording or recover recordings in the event, they did not initiate recording when expected. What duration of the recording that is recovered from the time recovery recording function is turned on in minutes?

4.5.3.6 Automated Recording Activation, Sensors, Synchronization and Streaming Automated recording activates the recording function of the camera without any input from the officer, 4.5.3.6.1 Method 1 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.3.6.2 Method 2 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 21 PAGE 4.5.3.6.3 Method 3 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.3.6.4 Method 4 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.3.6.5 Method 5 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.3.6.6 Method 6 - Describe the technology, method, and process of automating the recording function of the camera without any input of the officer, including activation by a sensor or person remotely. 4.5.3.6.7 Describe any end-user reported issues, entries into your helpdesk or support system or known problems with camera automated activation. Examples may include technology pairing or radio frequency caused problems, sensor failure or other issues.

Synchronization includes matching the time signature of active recordings of other cameras in proximity to the IRVS camera, including body-worn cameras. For each camera identified in 4.5.3.4, complete the following: 4.5.3.6.8 Does this camera provide synchronization with other cameras? 4.5.3.6.9 Does synchronization include time synchronization? 4.5.3.6.10 Describe any other synchronization capabilities of the camera. 4.5.3.6.11 Describe any end-user issues, entries into your support system or known problems with camera automated activation or synchronization. Examples may include technology pairing or radio frequency caused problems, sensor failure or other issues.

Streaming sends the compressed video and audio bit stream over a network connection to a remote video streaming service that allows the bit stream to be viewed remotely or includes a wired video interface allowing display of video and audio being recorded in real- time or played back from a recorded video and audio file. 4.5.3.6.12 Does the DVR/VPU provide for bit streaming of the video and audio? 4.5.3.6.13 Is the bit stream transmitted at the camera's source video and audio resolution or frame rate? 4.5.2.6.14 If the bit stream is transmitted at a lower resolution and frame rate that the camera's source resolution and frame rate, indicate the codec used, resolution and frame rate. 4.5.3.6.15 What is the network transfer protocol used to transmit the compressed bit stream? 4.5.3.6.16 What wireless network methods are used for remote streaming? 4.5.3.6.17 Can remote streaming be achieved with camera recording turned off? 4.5.3.6.18 Should remote streaming be implemented with DVR/VPU recording turned off - what are the implications of turning off local camera recording? 4.5.3.6.19. Does the DVR/VPU include a video and audio capability such as composite, component or HDMI? Please describe the number and types of video and audio out ports on the DVR/VPU for the IRVS system. 4.5.3.6.20. For multiple in-room camera systems, describe how separate camera video feeds are aggregated into a single source feed thereby allowing a remote user to see a single composite view of all in-room cameras on a standard 16x19 high- definition monitor or television?

4.5.3.7 Audio Recording Features 4.5.3.7.1 Specify the audio codecs supported and audio encoding profile if known. 4.5.3.7.2 How many simultaneous, concurrent audio recording streams can be recorded simultaneously, including the number of wired and wireless audio interfaces supported? 4.5.3.7.3 What is the frequency response of recorded audio microphones expressed in hertz or megahertz including signal loss in decibels? 4.5.3.7.4 Describe any unique characteristics of the DVR/VPU's audio recording capabilities. 4.5.3.7.5 For multiple in-room camera systems, describe how audio is added to a composite camera image thus ensuring time signature fidelity with the video signals.

4.5.3.8 DVR/VPU File Storage (Recording Media) 4.5.3.8.1 Does the DVR/VPU have a single storage repository or multiple storage repositories? 4.5.3.8.2 Specify the storage medium types for file storage on the DVR/VPU, including whether they are fixed or removable, and their size, e.g., 2.5” 3.5” eSata HDD, SSD. 4.5.3.8.3 Specify the total amount of useable storage configurations available for each storage drive type in megabytes (MB) 4.5.3.8.4 Specify the computer bus interface types for storage media available for each drive type and their size.

22 PAGE 4.5.3.8.5 For each drive type, specify the read/write transfer speed of the storage reads or writes in megabits per second or in the format in MB per second read, in MB per second write. 4.5.3.8.6 Specify any physical or other attributes that increase useful life, or availability of storage drives used within an automobile. 4.5.3.8.7 Describe any redundancy or resiliency features that replicate recording across multiple storage drives to reduce the risk of data loss. Specify any uses of standards for achieving resiliency. 4.5.3.8.8 Does the DVR/VPU provide removable recording media? 4.5.3.8.9 Specify the removable storage type and useable storage. 4.5.3.8.10 Specify the storage capacity in MB of video formats supported by the DPU/VPU. 4.5.3.8.10.1 Specify the total configurable storage capacity of the DVR/VPU for 4K UHD video in hours of recording. 4.5.3.8.10.2 Specify the storage capacity storage capacity of the DVR/VPU for 1080p HD video in hours of recording. 4.5.3.8.10.3 Specify the storage capacity storage capacity of the DVR/VPU for 720p HD video in hours of recording. 4.5.3.8.10.4 Specify the storage capacity storage capacity of the DVR/VPU for 480p SD video in hours of recording. 4.5.3.8.10.5 Other supported video formats 1 - specify - see 4.5.2.4.9.5 above 4.5.3.8.10.6 Other supported video formats 2 – specify - see 4.5.2.4.9.5 above 4.5.3.8.10.7 Other supported video formats 3 – specify- see 4.5.2.4.9.5 above 4.5.3.8.11 Specify the file management system for the DVR/VPU storage media. 4.5.3.8.12 Are files stored on storage medium 'at rest' encrypted? Specify the cypher and key strength.

4.5.3.9 Interview Room Video Evidence System Video Cameras In the space below describe the types and features of cameras that are installed in-car and connected the DVR or VPU 4.5.3.9.1 Camera Name 1 - 4.5.3.9.1.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.1.2 Primary camera viewing angle expressed in degrees. 4.5.3.9.1.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.1.4 Secondary camera viewing angle expressed in degrees. 4.5.3.9.1.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.3.9.1.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.3.9.1.7 What is the weight of the proposed camera in ounces? 4.5.3.9.1.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux 4.5.3.9.1.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.3.9.1.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.3.9.1.11 Does this camera record in complete darkness? 4.5.3.9.1.12 Does this camera include infrared or IR illumination? 4.5.3.9.1.13 What camera controls and functions are available directly from the camera? 4.5.3.9.1.14 What additional controls are available from remote devices such as the display or DVR/VCU, , such as pan, tilt, zoom?

4.5.3.9.2 Camera Name 2 - 4.5.3.9.2.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.2.2 Primary camera viewing angle expressed in degrees. 4.5.3.9.2.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.2.4 Secondary camera viewing angle expressed in degrees. 4.5.3.9.2.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.3.9.2.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.3.9.2.7 What is the weight of the proposed camera in ounces? 4.5.3.9.2.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.3.9.2.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.3.9.2.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 23 PAGE 4.5.3.9.2.11 Does this camera record in complete darkness? 4.5.3.9.2.12 Does this camera include infrared or IR illumination? 4.5.3.9.2.13 What camera controls and functions are available directly from the camera? 4.5.3.9.2.14 What additional controls are available from remote devices such as the display or DVR/VCU, such as pan, tilt, zoom?

4.5.3.9.3 Camera Name 3 - 4.5.3.9.3.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.3.2 Primary camera viewing angle expressed in degrees. 4.5.3.9.3.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.3.4 Secondary camera viewing angle expressed in degrees. 4.5.3.9.3.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.3.9.3.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.3.9.3.7 What is the weight of the proposed camera in ounces? 4.5.3.9.3.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.3.9.3.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.3.9.3.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.3.9.3.11 Does this camera record in complete darkness? 4.5.3.9.3.12 Does this camera include infrared or IR illumination? 4.5.3.9.3.13 What camera controls and functions are available directly from the camera? 4.5.32.9.3.14 What additional controls are available from remote devices such as the display or DVR/VCU, , such as pan, tilt, zoom? ?

4.5.3.9.4 Camera Name 4 - 4.5.3.9.4.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.4.2 Primary camera viewing angle expressed in degrees. 4.5.3.9.4.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.4.4 Secondary camera viewing angle expressed in degrees. 4.5.3.9.4.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.3.9.4.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.3.9.4.7 What is the weight of the proposed camera in ounces? 4.5.3.9.4.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.3.9.4.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.3.9.4.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.3.9.4.11 Does this camera record in complete darkness? 4.5.3.9.4.12 Does this camera include infrared or IR illumination? 4.5.3.9.4.13 What camera controls and functions are available directly from the camera? 4.5.3.9.4.14 What additional controls are available from remote devices such as the display or DVR/VCU, such as pan, tilt, zoom?

4.5.3.9.5 Camera Name 5 - 4.5.3.9.5.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.5.2 Primary camera viewing angle expressed in degrees. 4.5.3.9.5.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.5.4 Secondary camera viewing angle expressed in degrees. 4.5.3.9.5.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.3.9.5.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.3.9.5.7 What is the weight of the proposed camera in ounces? 4.5.3.9.5.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux.

24 PAGE 4.5.3.9.5.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.3.9.5.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.3.9.5.11 Does this camera record in complete darkness? 4.5.3.9.5.12 Does this camera include infrared or IR illumination? 4.5.3.9.5.13 What camera controls and functions are available directly from the camera? 4.5.3.9.5.14 What additional controls are available from remote devices such as the display or DVR/VCU, , such as pan, tilt, zoom?

4.5.3.9.6 Camera Name 6 - 4.5.3.9.6.1 Primary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.6.2 Primary camera viewing angle expressed in degrees. 4.5.3.9.6.3 Secondary camera lens resolution expressed as horizontal by vertical pixels. 4.5.3.9.6.4 Secondary camera viewing angle expressed in degrees. 4.5.3.9.6.5 What are the dimensions (height, width, and depth) of the proposed camera in inches? 4.5.3.9.6.6 What are the dimensions (height, width, and depth) of the proposed camera in inches when mounted? 4.5.3.9.6.7 What is the weight of the proposed camera in ounces? 4.5.3.9.6.8 Describe the low light capabilities of the camera's ability to reliably record video in low light conditions including its rating in lux. 4.5.3.9.6.9 What is the operational temperature range of the camera from lowest temperature to highest temperature in degrees Fahrenheit? 4.5.3.9.6.10 What is the connection type (wired or wireless) and type to the DVR/VPU? 4.5.3.9.6.11 Does this camera record in complete darkness? 4.5.3.9.6.12 Does this camera include infrared or IR illumination? 4.5.3.9.6.13 What camera controls and functions are available directly from the camera? 4.5.3.9.6.14 What additional controls are available from remote devices such as the display or DVR/VCU, such as pan, tilt, zoom?

4.5.3.10 Network and Telecommunications Features 4.5.3.10.1 What methods can be used to read and transfer stored recordings from the DVR/VPU's storage drives? 4.5.3.10.2 How is reading or transfer of stored recordings from the DVR/VPU to the evidence system or enterprise video storage initiated? Manually by the officer, automatically, by other methods? Please describe: 4.5.3.10.2.1 USB, Specify version and transfer speed. 4.5.3.10.2.2 802.3 Ethernet, specify speed supported in megabits per second. 4.5.3.10.2.3 802.11 wireless fidelity, specify the protocols supported, 802.11 a, b, g, n, ac etc. 4.5.3.10.2.4 Does the DVR/VPU include a cellular radio? If yes, is the cellular radio fixed, or installed via a removable SIM card? 4.5.2.10.3 Are bit streams sent over a telecommunications network encrypted in transit? If yes, indicate the cypher and key strength. 4.5.3.11 Accessories & Mounts 4.5.3.11.1 Describe any accessories for the IRVS system below. 4.5.3.11.1.1 Accessory 1 4.5.3.11.1.2 Accessory 2 4.5.3.11.1.3 Accessory 3 4.5.3.11.1.4 Accessory 4 4.5.3.11.1.5 Accessory 5 4.5.2.11.2 Describe the mounting options for each of the cameras identified above in 4.5.2.9.1 through 4.5.2.9.6 . 4.5.3.11.2.1 Camera 1 Mounting options, e.g., wall, pendant, etc. 4.5.3.11.2.2 Camera 2 Mounting options, e.g., wall, pendant, etc. 4.5.3.11.2.3 Camera 3 Mounting options, e.g., wall, pendant, etc. 4.5.3.11.2.4 Camera 4 Mounting options, e.g., wall, pendant, etc. 4.5.3.11.2.5 Camera 5 Mounting options, e.g., wall, pendant, etc. 4.5.3.11.2.6 Camera 6 Mounting options, e.g., wall, pendant, etc.

4.5.3.12 Additional, Unique Features, and Additional Features 4.5.3.12.1 Describe any additional or unique features of the IRVS specified. 4.5.3.12.1.1 Feature 1 25 PAGE 4.5.3.12.1.2 Feature 2 4.5.3.12.1.3 Feature 3 4.5.3.12.1.4 Feature 4 4.5.3.12.1.5 Feature 5 4.5.3.11.2 Please list any features in your proposed IRVS which serves to enhance officer safety.

4.5.3.14 Integration with Body-Worn or In-Car Camera Systems 4.5.3.14.1 Describe any common components of the IRVS that are shared with your company’s Body-Warn or In-Car Camera systems proposed in this BVP. 4.5.3.14.2 Describe any components of the IRVS that are unique to the IRVS that must be purchased for the IRVS components separately that are not needed with the Body-warn or In-car system components. Exclude cameras and DVRs/VPUs from this response.

4.5.4 Evidence Management

4.5.4.1 Describe the overall solution for video and audio recording evidence management, the name of the solution and its modules and functions. 4.5.4.2 What is the current version of your Evidence Management solution? 4.5.4.3 Did your firm develop and owns the source code for your evidence management platform, or did you build your solution on another software publisher's platform technology? If you used another provider's solution or any third-party components, please indicate the original publisher of the platform and describe the components used and current version supported. 4.5.4.4 Only if your firm wrote its own source code, describe the development framework to write the evidence management solution, for example, .Net. 4.5.4.5 Only if your firm wrote its own source code, list the number of full-time equivalent staff and contractors who write or support the application. 4.5.4.6 As a separate attachment provide a logical architecture that illustrates the components and relationships among them of your evidence and streaming platform. 4.5.4.7 As a separate attachment, provide a chronological listing of major functional releases to the evidence management solution in a PDF, Word, or Excel format. 4.5.4.8 What options do you provide for evidence management and operations? Is evidence management and operations provided as a software-as-a-service in a commercial cloud offering, as an on-premises offering, or in a hybrid cloud configuration that integrates a commercial cloud offering with an on-premises offering? 4.5.4.9 If your evidence platform is SaaS, is it configured as a unique instance - separate servers whether physical or virtual, and separate storage - for each customer, or do all customers share the same instance. The former is a multi-tenant, multi-instance, the latter is multi-tenant, single instance. 4.5.4.10 If you evidence solution is SaaS, please indicated whether the service is hosted in your data center or whether it is hosted by a commercial cloud provider. For the latter, please indicated the provider and hosting locations in North America. 4.5.4.11 If your evidence solution is SaaS, is it configured as a unique instance - separate servers whether physical or virtual, and separate storage - for each customer, or do all customers share the same instance. The former is a multi-tenant, multi-instance, the latter is multi-tenant, single instance. 4.5.4.12 Describe any major planned functional releases of the evidence management solution in 2021, 2022 and 2023. 4.5.4.13 Describe the features, functions, and processes for redacting video and or audio from recordings. 4.5.4.14 Describe the process for maintaining source recording originals and their derivatives. 4.5.4.15 Describe the identity and access management capabilities, including customization and automation of individual permissions, group policies, customizable permissions, and access to video and audio data, recording devices, and systems capabilities. 4.5.4.16 Describe the process and methods available for exporting or transferring recordings to prosecutors, courts, and attorneys, including transcoding capabilities, use of transfer portals or internet-sites, or support of DVD burners. 4.5.4.17 Data retention management. Describe the process and capabilities for establishing a data retention schedule, including automated transfer of data to storage archival, or destruction of data, based on user defined daily, weekly, or monthly retention rules defined by the customer.

4.5.5 Operational Management

26 PAGE 4.5.5.1 Describe how GPS data is displayed and used by your solution. 4.5.5.2 Does your solution provide the meta-data for recordings as separate data files? Please describe the data elements and format. 4.5.5.3 Does meta-data include geo-spatial data? If yes, describe what data is provided. 4.5.5.4 Please describe any GIS mapping capabilities of your solution 4.5.5.5 Please describe the APIs to integrate external data sources with your GIS mapping solution. 4.5.5.6 Please describe the APIs your solution supports to integrate data from your system with external GIS mapping platforms such as ESRI's ArcGIS, or other third-party applications such as CAD or RMS. 4.5.5.7 Describe any dashboard and reporting capabilities of your system including dashboard configuration and reporting tools. 4.5.5.8 Does your solution integrate with Tableau? If yes, what APIs are supported and are any Tableau templates available as part of your solution. 4.5.5.9 Does your solution integrate with Splunk? If yes, what APIs are supported and are any Tableau templates available as part of your solution. 4.5.5.10 Describe any data analytics capabilities of your solution. 4.5.4.10.1 The city desires to implement an officer early-wellness system which utilizes data from multiple sources to analyze patterns of community interaction. Please describe any data sources of your solution which could be utilized for this purpose and how you may envision supporting this use. 4.5.4.10.2 Describe any analytics that provides analysis of language (linguistics) use which can be applied to officer and community interactions such as an analysis of paralinguistic or vocalic. 4.5.5.11 Please describe the APIs to integrate external data sources with your data analytics solution. 4.5.5.12 Describe any APIs your solution supports to integration data from your system with external data analytics platforms. 4.5.5.13 Does the management system report overall health status (e.g., Normal, Degraded, Failed) in a single pane of glass? 4.5.5.14 What metrics does the management system report (for example, raw storage capacity, usable capacity, CPU utilization, current IOPS, etc.)? 4.5.5.15 Where is monitoring data saved? How long is data saved, and can this be changed by administrators? Can monitoring data be exported in a standard format (e.g., CSV)? 4.5.5.16 Can the system report alert when metrics cross administrator- or user-defined thresholds? If so, can thresholds be dynamic (i.e., adjusted automatically based on other monitored metrics)?

4.5.6 Video Streaming Capability

4.5.6.1 Which cameras provide video and audio streaming capabilities? Body-worn, In-car or both? List the camera models or SKUs that can be live-streamed. 4.5.6.2 For cameras that can stream, what network protocol is used to stream video from the source cameras or DVR/VPU to the streaming server? 4.5.6.3 Did your firm develop and owns the source code for your live streaming server platform, or did you build your solution on another software publisher's live streaming platform technology? If you used another provider's solution, please indicate the original publisher of the platform, and describe the components used and current version supported. 4.5.6.4 Only if your firm wrote its own source code, describe the development framework to write the streaming server. 4.5.6.5 Only if your firm writing its own source code, list the number of full-time equivalent staff and contractors who write or support the application. 4.5.6.6 As a separate attachment provide a logical architecture that illustrates the components and relationships among them of your streaming platform. 4.5.6.7 Describe any major planned functional releases of the video streaming solution in 2021, 2022 and 2023. 4.5.6.8 As a separate attachment, provide a chronological listing of major functional releases to the video streaming solution in a PDF, Word, or Excel format.

4.5.7 Streaming Server, aka Live Streaming Server

4.5.7.1 Does your solution include a streaming server, also referenced as a live streaming server? 4.5.7.2 Did your firm develop and owns the source code for your live streaming server platform, or did you build your solution on another software publisher's live streaming platform technology? If you used another provider's solution, please indicate the original publisher of the platform, and describe the components used and current version supported. 4.5.7.3 What options to you provide for live streaming server? Is live streaming provided as a software-as-a-service in a commercial cloud offering, as an on-premises offering, or in a hybrid cloud configuration that integrates a commercial cloud offering with an on- premises offering? 4.5.7.4 If you streaming server is SaaS, please indicated whether the service is hosted in your data center or whether it is hosted by a commercial cloud provider. For the latter, please indicated the provider and hosting locations in North America. 27 PAGE 4.5.7.5 If your streaming server is SaaS, is it configured as a unique instance - separate servers whether physical or virtual, and separate storage - for each customer, or do all customers share the same instance. The former is a multi-tenant, multi-instance, the latter is multi-tenant, single instance. 4.5.7.6 Are any portions of your streaming service hosted outside of North America? 4.5.7.7 If no, indicate what portions are hosted and where hosted outside of North America. 4.5.7.8 Please indicate whether the hosting locations for your video streaming servers are currently FedRamp certified. 4.5.7.9 How many incoming bit streams can your server support simultaneously? 4.5.7.10 What codec, resolution and frame rates does your streaming server support for broadcast bit streams? Describe the protocol, resolution as vertical pixels and frame rates supported. 4.5.7.11 Does your server use adaptive bit rate streaming to stream media over various networks?

4.5.7.12 Transcoding is the process of converting a bit stream from one encoding format to another format as a file conversion (post-event processing) or while live streaming.

4.5.7.12.1 Does your streaming server support transcoding? 4.5.7.12.2 Does your streaming support live transcoding where a broadcast source format is transcoded to a destination format in real- time, or near real-time? 4.5.7.12.3 How many simultaneous transcoding live sessions can your server support at one time? 4.5.7.12.4 What client viewing (destination) devices do you support? 4.5.7.12.4.1 Microsoft Windows Operating System, personal computers 4.5.7.12.4.2 Microsoft Xbox system software 4.5.7.12.4.3 Google Chrome Operating System, personal computers 4.5.7.12.4.4 Google Android Operating System, smartphones, smart TVs, Tablets 4.5.7.12.4.5 Adobe Flash 4.5.7.12.4.6 Apple OSX 4.5.7.12.4.7 Apple iOS 4.5.7.12.4.8 Real Networks Real Player 4.5.7.12.4.9 IP Television or IPTV 4.5.7.12.4.10 Other Operating Systems - specify 4.5.7.12.5 Does your streaming server also store recordings to direct attached storage, a storage area network, or network attached storage? 4.5.7.12.6 Does your streaming server provide transcoding of recordings by converting a recording file from one format to another? 4.5.7.12.7 List the file formats that can be transcoded from one format to another. 4.5.7.12.8 Is your streaming server able to transcode a proprietary native file from another body-worn or in-car camera provider from its original source format directly to your source format in one operation? If yes, list the file formats from other providers that you can transcode. 4.5.7.12.9 If your streaming server cannot transcode the proprietary native file format but can convert the file format to an industry standard format such as mpeg4, list the file formats and what industry formats they can be converted to.

4.5.7.12.10 Streaming Viewing Management

4.5.7.12.10.1 How many live camera streams can be viewed at one time on the operational display? 4.5.7.12.10.2 Can the number of live streams exceed the number that can viewed on the operational display? How is this managed? 4.5.7.12.10.3 Describe the decision rights around enabling live streaming to be broadcast or transmitted from individual officer- assigned body cameras or in-car systems. Describe how access is granted, by whom and to whom, including any policy administration capabilities. 4.5.7.12.10.4 How is viewing of video streams streaming administered? Describe how access is granted, by whom and to whom, including any policy administration capabilities. 4.5.7.12.10.5 How is identity and access management handled, within the server or through directory integration? Provide a list of the directory services the server platform integrates with. 4.5.7.12.10.6 Describe how live camera streams can be configured or group by substation, geographically, numerically or by other means. 4.5.7.12.10.7 Describe the decision rights around enabling live streaming to be broadcast or transmitted from individual officer- assigned body cameras or in-car systems. 4.5.7.12.10.8 Does your management interface and what active file management, dashboards, and other operational data? 4.5.7.12.10.9 Describe in application programming interfaces (APIs) and whether they are proprietary, or standards based.

28 PAGE 4.5.7.12.10.10 Does your streaming server provide for fulfillment of publics records requests? If yes, describe how publicly made records are fulfilled including file or folder access management, publishing of links to files, link expiration capabilities and recipient password management. 4.5.7.12.10.11 Does your streaming server allow for video streams to be publicly live streamed on platforms such as YouTube and Facebook? 4.5.7.12.10.12 Can live streaming be achieved with camera recording turned off? 4.5.7.12.10.13 Can live streaming be achieved with local camera recording turned off? 4.5.7.12.10.14 Should live streaming be implemented with camera recording turned off - what are the implications of turning off local camera recording? 4.5.7.12.10.15 In what circumstances are recordings transferred from the camera and live streamed, or stored on a video server at a lower quality (reduced video resolution, frame rate or lost information) than the source video recorded on the camera's local storage? 4.5.7.12.10.16 Describe what skill level and training are recommended to administer the proposed evidence and/or video streaming solution. 4.5.7.12.10.17 What documentation, self-help or knowledge base resources are available for the product? 4.5.7.12.10.18 What product-specific training is included or available for the product? Indicate whether training is for a fee, or if it is available at no additional charge. 4.5.7.12.10.19 Additional and Unique Features - Describe any additional ease-of-use and management capabilities you offer that differentiate your solution.

4.5.8 Existing Body-Worn Camera Systems

4.5.8.1 Does your solution support the city's current WatchGuard Vista and Vista XLT cameras, if so, how? 4.5.8.2 Describe how the city's existing WatchGuard Vista and Vista XLT cameras are used in your solution. 4.5.8.3 Does your company offer a trade-in program for the city's existing body-worn and in-car systems? 4.5.8.4 Does your proposed body-worn camera require new city uniforms? 4.5.8.5 Does your proposed body-worn camera require new mounts? 4.5.8.6 Does your solution require a new evidence management and operations solution? 4.5.8.7 Does your solution require a different video storage solution than the city's current storage environment? 4.5.8.8 Does your solution allow for the city's existing video storage arrays to be used in any way? 4.5.8.9 Does your company offer a trade-in program for the city's existing video storage arrays? 4.5.8.10 Existing Recordings 4.5.8.11 The city has approximately 1.58 million body-worn camera recordings in the following format – .MP4 4.5.8.11.1 The total amount of storage of the above is 538TB. 4.5.8.11.2 The storage rate is growing at a rate of .09% per day. 4.5.8.12 Please describe the process for transcoding 4.5.7.12 in the above to a format that allows them to be stored in your proposed evidence management solution. 4.5.8.13 Can transcoded videos be viewed, edited, and managed by your solution? 4.5.8.14 Provide a time estimate in hours to transcode and transfer the recordings to your proposed solution for archival and management. 4.5.8.15 Additional and Unique Features 4.5.8.15.1 Describe any additional ease-of-use and management capabilities you offer that differentiate your solution regarding use of existing body-worn camera systems owned by the city.

4.5.9 Security 4.5.9.1 Access Control - Does the solution provide role-based access control (RBAC) supported? If so, what role(s) are default or predefined? 4.5.9.2 What security audit logs are available? If so, what events are recorded in the audit log? Can audit logs be exported or audit alerts sent to other systems? 4.5.9.3 What security features (e.g., SSH, SSL) are available with the management console, API and/or CLI? 4.5.9.4 What integrations with third-party identify management tools (e.g., LDAP, Active Directory) are available, including support for Active Directory and Azure Directory Services. 4.5.9.5 What integration or support is available for antivirus/anti-malware software? 4.5.9.6 Does the system support data erasure or system wiping? What is the mechanism? 4.5.9.7 Does the authentication system support multifactor authentication? 4.5.9.8 What interfaces (hardware ports, management consoles, APIs, etc.) can be disabled by the administrator? 4.5.9.9 Encryption - Does the system support encryption? Can encryption be enabled/disabled? 4.5.9.10 Is encryption performed by hardware or software at rest and/or in motion? If hardware, what hardware? 29 PAGE 4.5.9.11 Specify the cyphers and key-strengths supported in 11.1.2 and whether FIPS compliant, PCI, HIPPA, CJIS, and IRS publication 1075 compliant. 4.5.9.12 Where can data encryption be applied (VMs, data at rest, data in transit, etc.)? At what granularity (e.g., VM, VM group, host, cluster) can encryption be controlled by the administrator? 4.5.9.13 How does encryption work when backups are created? 4.5.9.14 How are encryption keys managed (e.g., on-premises, off-site, in the IaaS cloud) if applicable? 4.5.9.15 What key management standards or third-party key management products does your system support, natively or with plug- ins? 4.5.9.16 CJIS Compliance 4.5.9.17 Is your solution end-to-end CJIS compliant? 4.5.9.18 Is your firm willing, upon request, to allow the city to inspect your system security controls documentation? 4.5.9.19 Additional Security Features 4.5.9.20 Is there a plug-in for Splunk SIEM? 4.5.9.21 Describe any additional security capabilities you offer that differentiate your solution.

4.5.10 Availability and Disaster Recovery

4.5.10.1 Availability

4.5.10.1.2 How do you ensure there is no single point of failure (SPOF) in your product architecture? Specify capabilities for "fault tolerant" type virtual machines, both within each data center and between the data centers, such that running VM's can experience a hardware failure and continue to operate without interruption to the user. 4.5.10.1.3 What impact does drive, disk, or controller failure have on availability and performance? 4.5.10.1.4 What impact does failure of domain controllers, DHCP, and DNS have on system availability? Can your solution function independently without these resources as a standalone solution, if so, how? 4.5.10.1.5 Can firmware and software be updated within a cluster with no service disruption? 4.5.10.1.6 Can nodes or hardware (such as disk drives) be added or removed from a cluster with no service disruption? Specify capabilities for planned outages by non-disruptively migrating virtual machines to other hosts within a data center or to another data center without interruptions in service. 4.5.10.1.7 How is metadata distributed across the cluster, and how do you ensure high availability of metadata?

4.5.10.2 Disaster Recovery 4.5.10.2.1 Do you have native disaster recovery capabilities? If so, describe how it works, and what is required (e.g., additional licenses, number of nodes, etc.) 4.5.10.2.2 Specify "high availability" capabilities for disaster recovery in the event of a hardware or hypervisor failure both within a data center and between the two data centers. 4.5.10.2.3 What is the range of RTOs and RPOs supported?

4.5.10.2.4 Data Protection and Data Backup 4.5.10.2.4.1 Do you support RAID schemes? If so, what RAID levels do you use/support? 4.5.10.2.4.2 Do you support erasure coding? If yes, what are the required number of drives, volumes and/or nodes? What administrator-configurable options are available to control erasure coding ratios? 4.5.10.2.4.3 Describe how your solution prevents unauthorized deletion and/or encryption (e.g., CryptoLocker) of backup data. (Air gap, or two-factor authentication, etc.?) 4.5.10.2.4.4 Specify methods to modify the storage policy (RAID type, failures to tolerate, etc.) of a virtual machine and its impact on the VM. 4.5.10.2.4.5 What replication factors (RFs) do you support in your product? Do you support GFS Retention Schemes? 4.5.10.2.4.6 Describe any additional features in your product for detecting or preventing data corruption. 4.5.10.2.4.7 Describe any additional features that automates a full back-up copy of the City's data, or equivalent, in a 48-hour period. 4.5.10.2.4.8 Describe the snapshot capabilities embedded within your product, including how to perform a snapshot restore from a secondary on-prem data center instance or the public cloud. 4.5.10.2.4.9 Describe whether the snapshot capabilities embedded within your product supports individual file restoration from the snapshot and the process for restoring an individual or group of files. 4.5.10.2.4.10 Additional and Unique Features - Describe any additional availability and data protection capabilities you offer that differentiate your solution.

30 PAGE 4.6 Section Four – Support, Maintenance, and Warranty (15 points): The ability of the Offeror to perform the required service competently and expeditiously as indicated by the Offeror's workload and the availability of necessary personnel, equipment, and facilities.

4.6.1 Support, Maintenance and Warranty

4.6.1.1 Describe the warranty and system maintenance proposed, including coverage hours, service type, and any response time or time-to-repair commitments. If any warranty terms vary by location or country, answer for each location indicated in the BVP instructions. 4.6.1.2 For the hardware and software covered under warranty, when does the warranty or maintenance period start? Upon receipt of a purchase order, after configuration and testing or at 'go-live'? 4.6.1.3 What third parties, if any, are responsible for delivering any aspect of support? For example, if camera hardware support comes from a third party, list those vendors. 4.6.1.4 Specify the standard warranty periods for all solution hardware and software. Note if any components (such as storage devices) have different warranty periods or terms. Do you offer different levels of warranty or service (e.g., Bronze, Silver, Gold)? If so, which level of service are you proposing? Give a description of each level of service. 4.6.1.5 All equipment in the Offeror’s proposal must be warranted by the manufacturer to be free of defects in equipment, software, support and services, and workmanship for a period of at least five years following final completion by Offeror and acceptance by the City. The warranty period will commence when an individually warranted item, i.e., a camera, is placed into City’s production environment. 4.6.1.6 During the warranty period, and any subsequent maintenance agreement, any defective hardware and software components shall be repaired or replaced at no cost to the City. 4.6.1.7 During the implementation period, the Offeror must supply no more than a 30-minute response to major problems directly with the equipment manufacturer, 24 hours a day, and 7 days a week. 4.6.1.8 Post implementation and for the duration of the agreement, the selected Offeror must have technical support services available. The City prefers this support be on a toll-free basis, 24 hours a day, 7 days a week, during the entire contract period with a ½ hour (30 minutes) or less response time to major problems, with a clearly defined priority escalation process. The selected Offeror shall also provide on-site technical support when required. This on-site support may be requested when problems are escalated without resolution and normal operations cannot be reasonably retained or restored. 4.6.1.9 Offeror must provide a 24 hour or less hardware Return Material Authorization response for all components in the solution. 4.6.1.10 Technicians must be certified by the original equipment manufacturer to support any hardware and software implemented as a part of this project. 4.6.1.11 The City staff shall have the ability to call the manufacturer directly during the support and warranty period of all components of the proposed solution. If it is determined the problem cannot be corrected by telephone support. Proposers shall include description in the proposal response outlining the support services offered and any limitations thereof. 4.6.1.12 List the location(s) of the support center(s) that will deliver remote or phone-based support. 4.6.1.13 Describe support escalation stages, if any (e.g., L1, L2, L3) and the roles and level of capability delivered at each stage. 4.6.1.14 If support entitlement or delivery varies by issue severity level, include a matrix defining severity levels and entitlements. 4.6.1.15 If hardware parts are included as part of a warranty, list where parts depots are located, or sources and timeline for shipping parts on-site. 4.6.1.16 If on-site service is included as part of the warranty or maintenance, describe the titles and locations of the people who will perform services. If they are from a third-party company, list the company name. 4.6.1.17 List any components that the client is expected to repair themselves. For example, if the warranty includes shipping parts to the site, but the client must install those parts. 4.6.1.18 Does the warranty or maintenance include the rights to software updates? If so, describe what software is included. 4.7.1.19 What resources must the buyer provide to receive warranty or maintenance support? For example, any remote connectivity, physical access to data centers, etc. 4.6.1.20If there is a self-maintainer program, indicate the availability, cost, reimbursement, spare parts requirements, training, and certification requirements. 4.6.1.21 Please provide a soft copy of your standard, Software License Agreement, Maintenance Services Agreement and Service Level Agreements

4.6.2 Implementation and Project Management

4.6.2.1 Please submit a detailed Project Management Plan for implementing the proposed solution and supply a complete description of the key activities and responsibilities required for the installation of the proposed system(s). The plan shall include narrative information and detailed work breakdown structure, project milestone and schedule information presented in Microsoft Project file 31 PAGE format, Excel spreadsheet, or SmartSheet. The Offeror shall include an estimated start time and completion date for the project, and a Gantt chart. 4.6.2.2 Project Management: Provide a description of the Offeror’s management team for this project. List all key personnel and their qualifications, including their resumes and relevant work histories. 4.6.2.3 Project Schedule: Provide an implementation schedule for the proposed service, including delivery dates, implementation milestones, task relationships and dependencies, and a timeline. The Project schedule also consist of a work responsibility matrix, identifying the tasks the vendor will perform and the tasks the City is expected to perform to successfully implement the proposed system(s). 4.6.2.4 The offeror will provide Incident management and provide reports online, weekly, upon request. 4.6.2.5 The City reserves the right to require the awarded vendor to replace the assigned project manager at any time, without additional costs to the City, if it is in the best interest of the overall implementation.

4.6.3 Solution Implementation Requirements

4.6.3.1 Primary installation crew(s) must be the same group of individuals for the entire implementation process for all sites. 4.6.3.2 All provider provided support staff must pass City background checks. 4.6.3.3 New feature testing, failover testing, performance testing, validation, and documentation 4.6.3.4 Hardware implemented to be updated with the most recent fully supported firmware version. 4.6.3.5 Software implemented to be the most recent version available from the manufacturer. 4.6.3.6 Bidders shall provide details of all maintenance and switch over activities and how assistance will be provided to City users. 4.6.3.7 The installer will be made aware, in writing, of any outstanding problems with an installation within fourteen days of the presentation of the installation for acceptance. The installer will correct any outstanding problems within thirty days from the date of notification. No payment will be made until the City accepts the installation according to proposal specifications.

4.6.4 Training and Documentation

4.6.4.1 All associated costs for formal training classes; training and reference materials, travel and expenses, and any other associated costs must be included in the submitted proposal. 4.6.4.2 Deliver training necessary for 20 City employees to fully administer the solution, migrate data (recordings) on City premises prior to the solution being placed in production. 4.6.4.3 Deliver training necessary for 25 City employees to operate as super-users on City premises prior to the solution being placed in production as a train-the-trainer model of training. 4.6.4.4 For each aspect of the proposed solution, provide a detailed description of the training the vendor will provide along with pricing and syllabus. 4.6.4.5 Provide credits for live, instructor led, classroom or remote training from the manufacturer for each solution, for 5 days each for 2,000 city employees. 4.6.4.6 Prior to implementation, provide a physical and logical diagram of the proposed solution architecture. Drawing in Microsoft Visio format. 4.6.4.7 Provide configuration documentation pertaining to all critical aspect of the solution and access to knowledge systems for the duration of the warranty. 4.6.4.8 Provide City staff with documentation on standard operating procedures required to operate the new solution.

32 PAGE 4.7 Section Six – Cost (25 points) – Overall cost for the proposed solution, expressed as a total cost of ownership over a period of five-years.

The City will negotiate a term with the selected vendor for a term of up to three (3) years with an option for two successive annual extensions for a potential total contract award of no less than three (3) years and no longer than (five) 5 years. While the city may purchase in different lots and quantities throughout the term of the agreement, the pricing provided below should include a purchase of 2300 body-worn cameras and 400 in-car systems.

4.7.1 Offeror must provide a bill of materials (BOM) that includes full and complete line-item-level pricing in the tables below. Specify the hardware, software, storage, other components, and services to meet the requirements herein. Include any recurring payments, such as warranty or maintenance payments, and specify their term lengths. A single figure for "total cost of solution" will be rejected. This pricing table must be provided in an unlocked and editable spreadsheet. 4.7.2 If the pricing offered is based on any existing contracts or purchasing agreements (such as a federal or state government or consortium pricing contract), list the contract number(s) purchasing organization(s), or any other contract reference information with your response. 4.7.3 The offeror shall include their current, valid government price list, either specific to this BVP or based on any existing contracts identified 4.8.2. and a stated discount level for all quantitates of stock keeping units listed on said price list. 4.7.4 Escalator Clause: For items identified in 4.8.1., no adjustment of the discount shall be granted during the first twelve (12) months duration of an awarded contract. Thereafter no more than two such adjustments may occur during the life of the contract, one in each subsequent contract year. In the event the supplier receives a general price increase in the cost of the finished product contracted for, due to increase in the cost of raw materials, labor, freight, etc., upon giving thirty (30) days prior notice and proper documentation as proof, said adjustment in addition to the price quoted herein, may be permitted, subject to the sole discretion of the City of Columbus Finance Director. In the event any such adjustment is granted; no adjustment shall be permitted on orders received by supplier which are in process or filled but awaiting shipment prior to the increase. All price decreases shall inure to the benefit of the City of Columbus. The written notice and following documentation shall be sent to: City of Columbus Department of Finance Director or designee. 4.7.5 Are any parts of the proposed solution subject to import tariffs and if yes, how are tariffs factored into 4.8.4? 4.7.6 For each software license, what is the unit of license? For example, is the software licensed per user, per camera, per system, etc.? 4.7.7 How many months/years of licenses and support are included? List any additional recurring charges that are not included in the BOM table below. 4.7.8 Shipping/freight terms (if applicable) — All shipping should be FOB Columbus, Ohio to either of the city's two data centers.

4.7.9 Warranty and License Extensions

4.7.9.1 After the warranty term is complete (4.6.1. above), are warranty or license extensions available? If so, list the items that require extensions past the stated term. 4.7.9.2 What are the prices of these extensions? If prices are not fixed, how are they determined? If prices can change over time, what is the maximum rate at which these prices can rise (e.g., x% per year)? 4.7.9.3 If any licenses are not renewed at the end of the standard period (1.4 above), what rights does the buyer have to continue using the product? Are there any cases when if the warranty expires, the customer does not have the right to continue to use the product?

4.7.10 Operating Cost Assumptions or Consumption-Based Offerings

4.7.10.1. Is this product available on a consumption-based (pay-per-use) basis? If "no," ignore the rest of the questions in this subsection. 4.7.10.2 Is the recurring payment fixed or metered? What is the payment frequency (monthly/quarterly/etc.)? 4.7.10.3 If payments are metered, what is the unit of measure? 4.7.10.4 If payments are metered, how is consumption measured? 4.7.10.5 What additional software or services, beyond those listed in the BOM table below, are included or required in a consumption-based offering? 4.7.10.6 Are there minimum, maximum, or required term lengths? List any termination notice requirements and penalties. 4.7.10.7 What are the minimum payments? 4.7.10.8 For the quoted configuration, list the minimum and maximum payments for a 3-year term, and separately for a 5- year term. Include any assumptions made about consumption rates, growth rates, price changes, etc. 33 PAGE 4.7.10.9 List any circumstances under which the seller may unilaterally adjust prices or minimum payments during the contract term. 4.7.10.10 If pre-deployed resources such as "buffer stock" are deployed, how are these resources initially sized, and what triggers additional capacity to be added? Can resources be returned to the buffer stock if they are no longer needed? 4.7.10.11. Is technology refresh included with the consumption-based offering? If so, what triggers replacement?

4.7.11. to 4.7.13. Bill of Products and Services – Year 1

4.7.14. to 4.7.16. Bill of Products and Services – Year 2

34 PAGE 35 PAGE 4.7.17. to 4.7.19. Bill of Products and Services – Year 3

36 PAGE 4.7.20. to 4.7.22. Bill of Products and Services – Year 4

37 PAGE 4.7.23. to 4.7.25. Bill of Products and Services – Year 5

38 PAGE 4.7.26. Five-Year Total Cost of Ownership

Summarize 4.7.11to 4.7.25 in the table below.

39 PAGE PERFORMANCE QUESTIONNAIRE – Public Safety Video

To:

………………………………………………………………… ……….. (Name of person completing survey)

Phone: ………………………………… E-mail: …………………………….

Subject: Past Performance Survey of: ………………………………………… (Name of Company) ………………………………… ……….. (Name of individuals)

City of Columbus (the City) is implementing a process that collects past performance information on firms and their key personnel. The information will be used to assist the City in the selection of firms. The Offeror listed above identified you as someone for whom the Offeror either currently provides a service and/or product or for whom the Offeror has provided this service and/or product in the past. Please take a moment to tell us about this Offeror’s performance. The City may contact you to gather further information about the Offeror.

HOW SATISFIED. Rate each of the criteria on a scale of 1 to 10, with a 10 representing highly satisfied and a 1 representing highly dissatisfied. Use a number in between to show different degrees of satisfaction. Please rate each of these criteria to the best of your knowledge. If you have no knowledge of past performance in a particular area, leave it blank.

NO CRITERIA UNIT YOUR SCORE 1 Ability to meet customer expectations (1-10) 2 Ability to financially perform in the best interest (1-10) of the client and citizens 3 Ability to maintain schedules and meet deadlines (1-10) 4 Ability to increase value (1-10) 5 Quality of service (1-10) 6 Ability to identify and minimize the user’s risk (1-10) 7 Leadership ability (minimize the need of (1-10) owner/client direction) 8 Your comfort level in hiring the firm/individual (1-10) again based on performance

Printed Name (of Evaluator) Signature (of Evaluator)

Thank you for your time and effort in assisting us in this important endeavor. Please e-mail survey back to (Vendor enter your e-mail here).

40 PAGE