Summary
Technical bulletin for LEARN release 7.0.211 released on 2/7/23
Reference
VIGILANT VEHICLEMANAGER 7.0.211 UPDATES
EFFECTIVE DATE: FEBRUARY 7, 2023
February 7, 2023 @ 12:00 AM CST/ACST [minor disruption to services 12-2 AM CST/ACST but no widespread outage required for maintenance updates]
The hosted Vigilant VehicleManager 7.0 servers are scheduled to be updated with new user and administrative features to allow for the improved management of LPR data. We will be deploying a series of updates that enhance the user interface, expand our analytical tool offerings, and introduce best practices into our Vigilant VehicleManager security. Here are the affected production URLs scheduled to receive the updates. Please update your URLs to these production links if using older URL links:
https://learn-nvls.com/learnmobile
https://learnfl.vigilantsolutions.com/learn
https://learnfl.vigilantsolutions.com/learnmobile
https://learnau.vigilantsolutions.com/learn
https://learnau.vigilantsolutions.com/learnmobile
THE LATEST VIGILANT VEHICLEMANAGER 7.0.211 HAS THE FOLLOWING USER IMPACTING IMPROVEMENTS AND FIXES:
1. Vehicle Registration State Validation [LRN-30010] (Figure 1)
• Validate Registration State is a new hot list alert filtering option that was added to the Setup Alert Management window of the User Permissions page in version 7.0.207.
• By default, Vigilant Vehicle Manager assigns the registration state to license plate detections with OCR when available. If the state cannot be read off of the plate, the state reported by the detecting system’s GPS is used. Some U.S. states have the same license plate numbering scheme as one or more other states. Rarely, this can create the potential for two different license plates that have the same numbering, but different registration states, to generate an alert.
• Vehicle Registration State validation prevents such plates from generating alerts. When enabled, this option will provide a hot list alert only if the registration state read by OCR from a captured plate matches the state of the hot list records it is matched with. The GPS reported state will not be used.
2. Addition of the GMT+13 Time Zone to L6Q Camera Settings [LRN-31075] (Figure 2)
• An option to select the GMT +13 time zone has been added to the Time Zone drop down menu in standalone camera settings.
• Countries in the GMT+13 time zone include:
» Kiribati: Phoenix Islands
» New Zealand (during Daylight Saving Time)
» Samoa
» South Pole (during Daylight Saving Time)
» New Zealand: Tokelau
» Tonga
3. Case Management and CommandCentral Evidence Publication [LRN-24805] (Figure 3)
• New case management features have been implemented to allow the storage of .pdf reports created for each case, publishing cases and .pdf reports to CC Evidence, and searching by CaseID in VehicleManager.
• When searching by CaseID in auditing, all reports generated for that case will be displayed with their corresponding output report audits.
• Three new options have been added when creating reports where a case audit is required:
» Multi Report - PDF
» Send copy to case file
» Send to “CC Evidence”
4. OpenALPR Integration for Fixed Camera Systems [LRN-31107] (Figures 4-6)
• The OpenALPR proxy camera Integration has been expanded, and new options are available to make it easier for agency managers to configure it. VehicleManager administrators must grant agency access to this integration.
Agency managers can add new proxy systems and can edit existing proxy systems and settings without the disrupting data flow from cameras to VehicleManager.
» New OpenALPR options have been added to the Fixed Camera LPR Systems interface:
+ Agent ID: ID of the OpenALPR Agent that is linked to customer cameras. Customer may have multiple agents.
• Camera ID: ID of the fixed camera using OpenALPR. Multiple cameras can be associated to a single agent ID.
• Camera Name: The name of the fixed camera. This can be changed safely without breaking the OpenALPR integration.
5. System Names for L5Q and L6Q Cameras [LRN-31545] (Figure 7)
• Agency managers now have the ability to rename L5Q and L6Q cameras under a single “system” name.
• This feature prevents the need to search for each previous camera name independently when searching for all detections that came from that camera when it was named something else.
• To retain the naming scheme, the system name can only be changed if the camera is deleted.
• New camera names can be easily added, changed, and deleted under the same system name with the New Camera Name drop down menu and add/delete buttons.
• In QuickSearch, any of the camera names will be included in the search results for searches that include the system name.
6. Plate/Car Tip with Color/Make/Model Analysis [LRN-30841] (Figures 8-9)
• The “Vehicle Capture Submission” tool allows the user to upload an image where it will analyze the vehicle image and license plate to provide suggestions on the following:
» Year, Make and Model
» Possible License Plate Combinations
» License Plate Number and State, and Orientation
7. Machine ID Reset for Mobile Systems [LRN-31069] (Figure 10)
• Agency managers now have the ability to reset the Machine ID of Mobile Systems. » This action appears in Auditing as audit type: System management (Reset Machine ID)
THE LATEST VIGILANT VEHICLEMANAGER 7.0.211 HAS THE FOLLOWING USER IMPACTING IMPROVEMENTS AND FIXES:
• Upgraded an internal service to ASP.NET 6.0. LRN-29945
• Fixed an issue with LEARN Mobile that caused license plate queries to be out of date-time order. LRN-30256
• Fixed an issue with QuickSearch where the incorrect number of records were being returned for different Make/Model/Color filters. LRN-30312
• Modified the L6Q API to only send settings that have been changed. LRN-30465
• Added an alert settings option to send email alerts when the GPS coordinates of an L6Q camera change. LRN-30690
• Fixed an issue where agency affiliation was not properly set when a user account is upgraded to an agency manager. LRN-30555
• Fixed an issue with Stakeout Queries timing out when no search radius was defined, but the query was limited by the current or previous. LRN-30662
• Changed the color of hot list information for hits in the Map It function for better visibility. LRN-30717
• The Agency field in the QuickSearch results grid will now display as “Commercial Data” when searching for Commercial Data in VehicleManager. LRN-30750
• Modified the Vendor Agency Manager role to limit access and changed to the Agency Manager Support role. LRN-30543
• Anywhere speed is labeled as “Minimum Speed (mile/h)” in VehicleManager, the label will now instead read “Approximate Speed (mph).” LRN-29522
• Re-enabled the ability of the HealthStatus functionality to update certain L6Q camera attributes. LRN-31016
• Implemented fallback to GPS location for plate registration state recognition for L6Q cameras when state recognition with OCR is not available. This allows Make/Model/Color to be added to the detection record for up to 30% more detections. LRN-30558
• Created a new service to allow upload of detections as zip files to LPRD/DEASIL. LRN-31350
• Fixed an issue causing filterless searches to time out for the “Splendora Police Department” Agency. LRN-30988
• Removed the QR code from the Standalone Cameras UI for L6Q cameras. LRN-31353
To view the pdf version of this article Click Here