Attachment_B_-Bid_Specification_Number_6720-4910_Rev_A.docx

State of California Bid Specification Commodity Title <optional: agency name/location> Spec #, Rev # Event ID Attachment/Exhibit #

State of California Bid Specification Automated License Plate Reader (ALPR)

6720-4910, Rev A Attachment B

Document Summary

Revision History Bid Spec Rev Level Revision Date

3.1.1 3.1.10 3.3.2 3.3.6 Added section 3.1.12

Table of Contents

SCOPE

This specification describes the requirements of a mobile Automated License Plate Reader (ALPR) system for use in California Highway Patrol (CHP) vehicles.

APPLICABLE LAWS and INDUSTRY STANDARDS Specifications, standards and regulations referenced in this document, in effect on the opening of the invitation for bid, form a part of this specification.

1.1 Laws and Regulations

1.1.1 California Vehicle Code including, but not limited to, the requirements noted in Division 12, Chapter 2.

1.2 Industry Standards

1.2.1 ANSI/IEC 60529 American National Standard for Degrees of Protection provided by Enclosures (IP Code), latest edition.

1.2.2 SAE J1477 Measurement of Interior Sound Levels of Light Vehicles, latest edition.

SYSTEM REQUIREMENTS

1.3 Hardware

1.3.1 The ALPR system shall be a 3-camera system configured to monitor front traffic, rear traffic and side parking simultaneously. Each camera shall be capable of infrared detection and color overlay.

1.3.2 Cameras, cabling and bracketry shall be flat black in color.

1.3.3 The ALPR system shall be capable of being operated, with an adequate power supply, 24 hours a day, 365 days a year.

1.3.4 The ALPR system shall be capable of operation on all of the CHP’s current touch screens. All icons shall be of sufficient size to allow operation via the touch screen without the use of a stylus.

1.3.5 Cameras and cable connectors used by the system shall be housed in weatherproof housings rated at IP67 or equivalent. The system shall be sealed to prevent damage from the elements and prevent moisture from depositing inside the camera lens.

1.3.6 If mounted on the exterior of the vehicle, cameras shall be low profile and be small enough in size as to not interfere with existing equipment (e.g., light bar).

1.3.7 Cameras, cabling and bracketry shall be capable of mounting on a Whelen Liberty light bar. The mounting method and shall be approved by Whelen Engineering Company, Inc.

1.3.8 When mounted on a Whelen Liberty light bar, the cameras, cabling and bracketry shall not block primary warning lights or affect light bar integrity at vehicle speeds up to 120 mph.

1.3.9 When installed, cameras, cabling and bracketry shall not increase the vehicle’s interior (cabin) noise greater than +5 dB at 65 mph when measured per SAE J1477 guidelines.

1.3.10 Mounting systems shall be capable of horizontal (rotational) and vertical movement to ensure optimum camera alignment. Once secured, the camera shall not move under normal operating conditions, including extreme wind pressures, rough terrain and mechanical car washing.

1.3.11 The ALPR system shall be in compliance with the California Vehicle Code including, but not limited to, the requirements noted in Division 12, Chapter 2.

1.3.12 The operating temperature range of the ALPR system shall be a minimum of -5 to 130 degrees Fahrenheit.

1.4 Functional

1.4.1 The ALPR system shall read and record the Vehicle License Plate (VLP) of a target vehicle whether it is approaching or receding from the camera.

1.4.2 The ALPR system shall read the VLP of the target vehicle while the patrol vehicle is stationary or mobile. Additionally, the system shall read the VLP of a target vehicle while the target is stationary or mobile.

1.4.3 The ALPR system shall read VLP’s where the speed differential between the patrol vehicle and the target vehicle is up to 110 mph without degradation.

1.4.4 The ALPR system shall be able to read plates from all 50 states (compliant with appropriate state legislation).

1.4.5 The ALPR system shall have the ability to read those plates that remain readable to the human eye where some characters are partly obscured (e.g. tow hitch).

1.4.6 The ALPR system shall present within its Graphic User Interface (GUI) a cropped image of each plate (hereafter referred to as a “plate-patch” image) alongside the digitized read to allow for operator verification.

1.4.7 The plate-patch image and digitized read shall be presented to the operator at sufficient size to be readable (on a 10” or greater screen) from a distance of up to 4 feet.

1.4.8 The ALPR system shall present within the GUI an uncropped color image of each plate read (overview). The overview image shall be of sufficient dimension to allow the operator to identify the vehicle type and color.

1.4.9 The ALPR system shall allow the operator to search the captured plate database for vehicle license plates. All matches to the search shall display the vehicle plate-patch image, vehicle overview image, date and time stamp and Global Positioning System (GPS) location.

1.4.10 The running log shall have a scroll function allowing the operator to look through previous reads. Any previous reads, when selected by the operator shall be presented in the GUI with the overview and plate-patch images, alongside a timestamp and GPS location of the selected read.

1.4.11 The ALPR system shall be capable of displaying an on-screen map of the GPS coordinates associated with selected reads for both mobile and office environments.

1.4.12 The ALPR system shall provide the operator the ability to display an on-screen visual map of the location of a read on all screens where a GPS location is provided (hit, read, and search screens) for both mobile and office environments.

1.4.13 At all times, the operator shall have the opportunity to correct any misreads by the system. The option to correct a plate shall be presented as a single or double touch icon in the GUI and shall not require the use of sub-menus.

1.4.14 The correction of any plate shall be included in an audit trail and the corrected plate shall be sent to the database for matching.

1.4.15 Once the VLP of the target vehicle has been read, the ALPR system shall search all relevant databases for the VLP.

1.4.16 Only one context-compliant result shall be reported for each license plate read and sent to the database for searching.

1.4.17 If there is no record of the VLP on any such database, the ALPR system shall record the reading and log the read and the image in a running log. This log of plate reads shall be available for review by the operator.

1.4.18 All VLP’s that DO NOT match a record in the loaded database shall be stored as a “read” or “detection”, which shall contain information, at a minimum, of operator’s identity, GPS location and timestamp and the relevant plate-patch and overview images.

1.4.19 The ALPR system’s GUI shall present a single-touch icon to the operator for the manual entry of a license plate for checking. Any plates entered by this method shall be sent to the database for matching and the transaction recorded in an audit trail.

1.4.20 If the reading of the vehicle is matched against any of the VLP’s that are held on any of the databases within the ALPR system, it is considered to be a match. The operator shall be provided with an image of the VLP and the vehicle in order that he/she can make a comparison and verify the match.

1.4.21 The ALPR system shall automatically trigger an audible alarm and display a “hit screen” when a match is made against the database. The system shall simultaneously provide the operator with a report from the database relating to the VLP match.

1.4.22 The hit screen shall contain the plate-patch, VLP interpretation, color overview, time of capture, database source identification, vehicle and other details from the database.

1.4.23 The ALPR system shall allow for a customizable audible alarm/tone specific to the alert type from which the match was generated.

1.4.24 The ALPR system shall maintain a record of the number of hits made and the details of all matches.

1.4.25 The ALPR system shall be capable of sending an information alert (not a JPEG compressed image) via e-mail to a destination configurable by the system administrator, of the originating video source from such an alert within a few seconds as a verification of the remote alert in section 3.3.7.

1.4.26 The ALPR system shall utilize GPS data to log where and when the match against a VLP was made.

1.4.27 The ALPR system shall continue to read VLP’s while the operator is dealing with a current match or dealing with any other menu or sub-menu of the system.

1.4.28 For all VLP’s that match an alert type in the loaded database, the ALPR system shall display the alert type description code on the GUI.

1.4.29 The ALPR system shall recognize license plates that are compliant with California legislation for the current style and manufacture of license plates.

1.5 Software

1.5.1 The ALPR application software (SW) shall be capable of running on standard computers and Mobile Data Computers running Microsoft Windows 10 or later.

1.5.2 The ALPR application SW shall be able to be configured, if required, by State information technicians with the assistance of the supplier, to meet current security policies, (e.g., desktop restrictions).

1.5.3 The ALPR application SW shall allow for multiple alert types of target VLP’s. The databases shall allow for the entry of both license plates and associated data. The associated data field shall accommodate not less than 200 characters of entry.

1.5.4 The ALPR application SW shall allow the assignment of priority levels to different alert types. The priority level of each alert type shall be definable by the system administrator. While an operator is dealing with a match on the device, should a further match be made it shall, depending on whether its alert type priority is higher or lower than that being dealt with, place the new match “behind” or “in-front” of the current match.

1.5.5 The ALPR application SW shall offer different levels of privilege and access to the system and alert types for users which can be configured by the system administrator.

1.5.6 In terms of Homeland Security and the policing of serious and organized crime, the ALPR application SW shall include the ability to set up and protect alert types that are extremely sensitive in nature, and are only accessible and alerted to those operators with the appropriate privileges.

1.5.7 The ALPR application SW shall be configurable to run such databases as “covert” databases for general users – not alerting general operators to those vehicles that match on those databases, but capable of remotely alerting interested parties with the appropriate privileges via GSM text message or email. Such remote alerts shall include GPS timestamp, the originating system ID and type of alert (Stolen, Amber, Sliver, ETC). No license plate information is sent in this email or text message.

1.5.8 The ALPR application SW shall be able to provide, in the exported data, an audit trail capable of being presented in evidence including, as a minimum the following: log on/log off data, database upload information, details of vehicles checked and ‘hits’ generated.

1.5.9 The ALPR application SW shall support Lightweight Directory Access Protocol (LDAP) authentication to integrate with CHP active directory system.

1.5.10 The ALPR application SW data shall be stored on a local server running on Microsoft SQL Server version 2016 or later.

1.5.11 The ALPR application SW shall be able to run on a Virtual Machine (VM).

1.5.12 The ALPR application SW shall provide automatic data transfer between the mobile and office environment via Wi-Fi and cellular network.

1.5.13 The ALPR application SW shall be able to store (hold) its data when the vehicle is offline or loses wireless connectivity. Once the vehicle is back online or wireless connectivity is re-established, data transfer between the mobile and office environment will resume automatically.

ADDITIONAL REQUIREMENTS

1.6 System compatibility testing

The California Governor’s Office of Emergency Services (Cal OES) Public Safety Communications will be responsible for verifying the compatibility of the ALPR system with existing radio systems.

1.6.1 The ALPR system shall not cause or be affected by any Electromagnetic Interference (EMI) or Radio Frequency Interference (RFI) including but not limited to the following radio frequencies currently in use by CHP vehicles:

Vehicle radio system description table

1.6.2 The ALPR system shall not cause more than one (1) dB of radio degradation at the antenna whether it be radiated or conducted RFI or EMI. If the system causes any two or all three types of interference, the total combined allowable receiver degradation is 1 dB at all CHP frequencies.

1.7 Consolidated Patrol Vehicle Environment

1.7.1 In the future, the ALPR system may be controlled by a third party control device known as the Consolidated Patrol Vehicle Environment (CPVE). Should the CHP choose to integrate the ALPR into the CPVE environment, the ALPR supplier shall cooperatively work with the CHP and the CPVE contractor to successfully accomplish this integration effort.

1.8 Vendor support

1.8.1 Any software application related issues shall be mitigated with vendor support staff availability in order to assist CHP with resolution.

image1.emf