Adding conditions when creating event-to-actions for license plate reads - 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 creating event-to-actions for license plate reads, you can specify additional conditions based on Sharp analytics to trigger an action. For example, you can specify that an action occur only when the plate number contains “123”, or the vehicle is traveling at a certain speed.

What you should know

  • Conditions must be typed as an expression that contains an identifier, operator, and a value (not case sensitive). For example, [PlateNumber] = "ABC123". To know more about the operators and identifiers that can be used, see Elements used in event-to-action conditions for license plate reads.
  • Identifiers must be typed in square brackets: [PlateNumber].
  • Text values must be typed in quotation marks: "ABC123".
  • You can use AND and OR to combine multiple expressions. When doing this, it's preferable to use parentheses to force the order of the evaluation. For example, if you type ([Speed] > 20 AND [Speed.unit] = "mph") OR ([Speed] > 50 AND [Speed.Unit] = "km/h") the AND operator takes precedence.
  • You can use the exclamation point (!) to exclude an expression. For example, if you type [PlateNumber] contains "123" AND !([PlateState] = "QC"), any plate reads with a plate number that contains the value "123" and a plate state other than "QC" will trigger an action.
  • Sharp analytics are not generated 100% of the time. An event-to-action might not be executed if the Sharp is not able to generate the analytic specified in the condition. For example, if the condition is [Speed] > 50 and the Sharp cannot produce a value for speed, Security Center will evaluate the condition as being false and the action will not be executed.

  • When the outputs of an ALPR Processing Unit are used to control building access through event-to-actions in Security Center, rebooting the ALPR Processing Unit causes the outputs to activate which could lead to the opening of the access point. This output behavior is not ideal for access control, but is required in order to power the in-vehicle computer on vehicle startup. Create an event-to-action in Security Center that will send a "Normal" state to the outputs following a "Unit Connected" event. The access points will still open, but will close shortly afterward.

Procedure

  1. Open the System task, and click General settings view.
  2. Click the Actions tab, and click Add an item ().
  3. From the When drop-down list in the Event-to-action dialog box, select License plate read.
  4. Click Specify a condition, and type the expression.
    Tip: Hover your mouse over the field for examples of valid expressions. The field will appear in red if the expression you enter is invalid.
  5. In the From drop-down list, select the ALPR unit that triggers the event.
  6. In the For drop-down list, select the desired entity.
  7. From the Action drop-down list, select an action type and configure its parameters.

    For example, if you select Send an email, then you must also select the email recipients.

  8. In the Effective option, click Always, and select a schedule when the event-to-action is active.

    If the event occurs outside of the defined schedule, then the action is not triggered.

  9. Click Save.

    The Save button is only available when all the arguments required by the event-to-action type are specified.