Configuring past-read matching on the ALPR Manager - When a hotlist is updated, the system can search the license plate reads in the ALPR Manager database to see if the new hotlist entries have been previously read. - Security Center 5.12

When a hotlist is updated, the system can search the license plate reads in the ALPR Manager database to see if the new hotlist entries have been previously read.

1. Associate the hotlists that you want to manage with the ALPR Manager.
   NOTE: In later steps, you’ll select specific hotlists from this list on which to perform past-read matching.
   1. From the Config Tool homepage, click System > Roles, and then click the ALPR Manager you want to configure.
   2. Click the Properties tab.
   3. Under File association, select the hotlists and permits you want the ALPR Manager to manage.
   4. Click Apply.
2. Enable past-read matching on the ALPR Manager role.
   1. Click the Properties tab.
   2. Turn the Matching option ON.
   3. (Optional) To generate No match events when a license plate is read by a Sharp and the plate isn’t part of a hotlist or permit list, turn the Generate “No match” events option to ON.
3. The Past-read matching section lists all of the hotlists that you’ve associated with the ALPR Manager role. Select the hotlists for which you want to enable past-read matching.
   NOTE: Federated hotlists aren’t supported by past-read matching and are therefore not displayed in the list.
4. In the Search back time field, set the time interval over which past-read matching takes place.
   NOTE: Performing past-read matching on many or large hotlists and using a long search back time can affect system performance.
5. Click Apply.
6. Trigger past-read matching using the following methods:
   • Create a scheduled task that uses the Trigger past-read matching action.
   • Create an event-to-action that uses the Hotlist changed event and the Trigger past-read matching action.
   • In Security Desk, create a hot action that uses the Trigger past-read matching action.