Configuring past-read matching on the ALPR Manager - Security Center 5.9

Security Center Administrator Guide 5.9

Applies to
Security Center 5.9
Last updated
2022-09-12
Content type
Guides > Administrator guides
Language
English (United States)
Product
Security Center
Version
5.9

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.

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 perform past-read matching in Genetec Patroller™.

Procedure

  1. Associate the hotlists you want to manage with the ALPR 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 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 is not 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 have associated with the ALPR 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.
  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.