Configuring past-read matching on the LPR Manager

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

Before you begin

Create a hotlist that will be used to trigger past-read matching.

What you should know

You can trigger past read matching using a hot action, a scheduled task, or an event-to-action.
In the Security Desk Hits report, hits that are generated using past-read matching are indicated in the Post matched column.
If your system includes patrol vehicles, you can run past-read matching in Genetec Patroller™. For more information, see the Genetec Patroller™ Administrator Guide.

To configure past-read matching on the LPR Manager:

Associate the hotlists you want to manage with the LPR Manager.

NOTE: In later steps, you will select specific hotlists from this list on which to perform past-read matching.
1. From the Config Tool home page, click System > Roles , and then click the LPR Manager you want to configure.
2. Click the Properties tab.
3. Under File association, select the hotlists and permits you want the LPR Manager to manage.
4. Click Apply.
Enable past-read matching on the LPR 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 is not part of a hotlist or permit list, turn the Generate “No match” events option to ON.
The Past-read matching section lists all of the hotlists that you have associated with the LPR Manager role. Select the hotlists for which you want to enable past-read matching.

NOTE: Federated hotlists are not supported by past-read matching and are therefore not displayed in the list.
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.
Click Apply.
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. For more information on creating hot actions, see the Security Center User Guide.