Automated License Plate Recognition (ALPR)
Does the plate scan identify the color, make and model of the car and save the data to the Mobile Digital Computer (MDC)?
While the software is capable of recognizing the make of the vehicle and the state on the license, the current camera in this solution may not provide enough pixels to provide this for every scan. Color and model are not captured.
What data is saved on the MDC and is accessible by CarDetector Mobile (CDM)?
A License Plate Recognition (LPR) data record consists of the color image of the vehicle, the cropped license plate image, the system's interpretation of the license plate, date/time, and GPS coordinates. This data is available locally on the patrol car until the data is synchronized up to Law Enforcement Archival Reporting Network (LEARN) where it will be accessible for the duration of the agency-defined data retention period.
What additional information can an officer input into CDM about a plate detection to provide more detail about the vehicle?
Users of the system may add comments to an LPR record manually to capture other information that may be useful at a later time. As this is a traffic stop solution, this other information will probably be contained in the traffic stop report itself but the capability does exist. One best practice that may be considered is to add a comment containing the citation number or other searchable reference.
What data can be shared in LEARN between agencies?
Detection data and hotlists may be shared between agencies.
How does a plate detection on a patrol officer’s MDC get shared with other patrol officers in the same agency?
The detection record is synchronized up to the agency's LEARN account where it may be accessible to any agency LEARN user with appropriate permissions. LEARN is accessible via an internet browser and can be viewed on a patrol car MDC.
How are Hot Lists updated on the MDC and how often are they updated?
Hotlist updates are typically automated. Agency managers set up hotlists in LEARN and configure LEARN to monitor the hotlist location (FTP, SFTP, HTTP, etc) on a scheduled basis and compile a record of the changes. These changes are then pushed from LEARN to the patrol vehicle upon the next CDM login. The frequency of updating is largely dependent on the hotlist source - some hotlists may be updated on a regular schedule (once per day, once every 6 hours, etc) while others may be updated on an as-needed basis (such as an agency-managed BOLO list). LEARN allows for the agency manager to set any schedule needed for each hotlist.
Who owns the data detected by the ALPR system?
Data collected by the agency’s ALPR system is the property of the agency. Vigilant is merely a steward of the data, responsible for its safekeeping and accessibility by authorized users.
Is agency data sold or shared?
Vigilant never sells or shares agency data. An authorized individual(s) within the agency controls data sharing permissions from within LEARN. Data may be shared broadly to all law enforcement via the National Vehicle Location Service (NVLS) initiative, or data may be selectively shared with individual agencies. Vigilant does not access agency data expect to provide support or other authorized purposes.
How long is agency data stored?
As the data is the property of the agency, it is held according to the retention policy set forth by the agency manager in LEARN. Retention policies may be adjusted by the agency manager at any time, and different retention policies may be set for “detections” and “hits” to allow for consistency with any agency policy in place and/or legislation. Even if an agency chooses to share its data to the National Vehicle Location Service (for nationwide law enforcement use) or to specific agencies, the data retention policies set by the agency still apply. Data is automatically deleted from the system based on the retention policy, and Vigilant keeps no record of data after deletion unless meta-data archival and classification is requested by the agency.
How secure is the data?
Agency data resides in a data center featuring redundant power sources, redundant fiber connectivity, redundant disk arrays, environmental monitoring, secure access control, physical escorts for onsite visitors, multiple diesel fuel back-up generators, active fire prevention and suppression, and onsite system administrators and engineers.