Configuring incident triggers for RSA Surveillance targets in Genetec Mission Control™ - Restricted Security Area Surveillance 4.2

Restricted Security Area Surveillance Plugin Guide 4.2

Applies to
Restricted Security Area Surveillance 4.2
Last updated
2022-06-27
Content type
Guides > Plugin and extension guides
Language
English (United States)
Product
Restricted Security Area Surveillance
Version
4.2

You can configure Genetec Mission Control™ to automatically trigger incidents when an RSA Surveillance target is detected or created.

Before you begin

  • Configure the Incident Manager role.
  • Configure all entities that can generate events in Security Center: video cameras, ALPR cameras, door sensors, alarm panels, zones, and so on. The Genetec Mission Control™ Rules Engine relies on these events to detect and trigger incidents.

Procedure

  1. From the Config Tool home page, open the Incident configuration task.
  2. Click Incident.
    A new incident type named New incident is added.
  3. Click the Identity page, enter a name and description, and choose an icon and a color for this incident type.
    Genetec Mission Control™ entities share the same set of custom icons. You can use any PNG or JPG file as an icon. A PNG file with transparent background works best.

  4. Click the Properties tab and configure the General properties and the Response and resolution time properties as required, and then click Apply.
  5. Click the Recipients tab and configure to whom incidents of this type should be dispatched. You can configure an advanced dispatch of incidents based on additional criteria such as user's assigned work area, schedule, online status, and so on.
  6. Click the Triggers page, and then click Add event ().
    The Event-qualifying rule dialog box opens.
  7. Choose the RSA event type and event source that must occur to trigger this incident.
    1. From the When list, select any of the following RSA events ():
      • Intrusion detected
      • Target created
      • Target active
      • Target inactive
      • Target detected
      • Target hostile
    2. From the From list, select the source of the event:
      • For an Intrusion detected event, select either Any source or a sub-device of a tracking system.
      • For any RSA target event, select either Any source or an RSA zone ().
      • Do not choose the RSA plugin role () as the source.
      • Do not choose an RSA event that has the orange plugin icon (). These events are listed if you upgraded from Restricted Security Area Surveillance plugin 4.0 or earlier.
      IMPORTANT: Make sure that the correct event source is selected for the event type. An RSA zone reports RSA events, such as Target created and Target detected; and a tracking system sub-device reports Intrusion detected.
  8. If multiple events can trigger the incident, click the plus button () beside Events to add more events.
    You can also specify multiple event types and multiple sources. In the following example, the incident is triggered when the Target created event occurs in Alarm zone 1 or when any Target detected event occurs in any zone (any source).

  9. (Optional) To configure a particular type of RSA target to trigger an incident:
    1. Enable Advanced event filtering.
    2. Select Event property path.
    3. Type Message.Type.
    4. Select Number.
    5. Select an operator.
    6. Type the number that corresponds to an RSA target type.
      Tip: Refer to the following list for the RSA target type numbers.
      • 0 = Unknown
      • 1 = Animal
      • 2 = Person
      • 3 = Vehicle
      • 4 = Boat
      • 5 = Aircraft
      • 6 = Drone
      • 7 = Commercial aircraft
      • 8 = Helicopter
      • 9 = Bicycle
      • 10 = Motorbike
      • 11 = Truck
      • 12 = Train
      • 13 = Maintenance
      • 14 = Birds
      • 15 = Wild animal
      • 16 = Non-motorized boat
      • 17 = Small boat
      • 18 = Sail boat
      • 19 = Big boat
      • 20 = Police
      • 21 = Doctor
      • 22 = Technician
      • 23 = Terrorist
      • 24 = Military
      • 25 = Fiber cut
      • 26 = Buoy
  10. (Optional) To configure an RSA target that is traveling in a particular direction to trigger an incident:
    1. Enable Advanced event filtering.
    2. Select Event property path.
    3. Type Message.Direction.
    4. Select Number.
    5. Select an operator.
    6. Type a number from 0 to 360, where 0 degrees and 360 degrees represent North.
      Tip: Refer to the compass to find the number that corresponds to the direction you need.
      alt="Compass degrees and cardinal directions.
  11. (Optional) To configure an RSA target that is traveling at a particular speed in kilometers per hour to trigger an incident:
    1. Enable Advanced event filtering.
    2. Select Event property path.
    3. Type Message.Speed.
    4. Select Number.
    5. Select an operator.
    6. Type a number from 0 to 99999.
  12. (Optional) To configure an RSA target of a particular threat level to trigger an incident:
    1. Enable Advanced event filtering.
    2. Select Event property path.
    3. Type Message.Threat.
    4. Select Number.
    5. Select an operator.
    6. Type a number that corresponds to the threat level, where 0 is Friend and 100 is Hostile.
      Tip: Threat levels are listed in the Restricted Security Area Surveillance plugin role Properties page, under the Threat definition section.
  13. (Optional) Click beside Conditions to add event correlation constraints.
  14. Click Save.
    A summary of your first event-qualifying rule is displayed on the Triggers page.
  15. (Optional) Click Add event to add more event-qualifying rules.
    The event-qualifying rules are evaluated in sequence by the Genetec Mission Control™ Rules Engine. The first rule must be satisfied before the second rule is evaluated. You can add as many rules as you need.
    CAUTION:
    For subsequent event-qualifying rules, you can specify Previous source as the event source for your event qualifiers. If you do this, select an event type that is compatible with the event source, or no event will qualify. For example, an RSA event () can only occur in an RSA zone ().
    Tip: If you are not sure, select Specific source and verify that the previous source is found in the list of available entities, then change it back to Previous source.
  16. Click Apply.
  17. Click the Automation tab and configure the automation workflow that defines the life cycle of the incident.
  18. Click the User procedure tab and configure the standard operating procedure (SOP) that the operator must follow before resolving the incident.

After you finish

  • Test your incident triggers and workflow.
  • Train your response team on the standard operating procedures.