Adding Genetec™ events as TSS entities - Security Center Traffic Sensor Management 2.3

Security Center Traffic Sensor Management Plugin Guide 2.3
Applies to
Security Center Traffic Sensor Management 2.3
Last updated
2020-11-20
Content type
Guides
Guides > Plugin and extension guides
Language
English (United States)
Product line
City applications > Security Center Traffic Sensor Management
Version
2.3

Before you can monitor Genetec™Security Center events as traffic sensors in Security Center, you must add Genetec™ model TSS units as TSS entities to the plugin. You can use this model to transform any Genetec™ event into TSS data.

Before you begin

Create the GenetecVSO macro.

What you should know

By transforming Genetec™ events into TSS data, you can, for example, use Access Control events and input triggers to enable people or parking occupancy counts inside an instrumented area.

Procedure

  1. From the Config Tool home page, open the Area view task.
  2. Click Add an entity () and select TSS.
  3. From the TSS model list, select Genetec, and then enter an entity Name.
    Tip: For better search indexing, it is a best practice to include the location of the sensor in the name.
  4. Select the new TSS entity. Click the Properties tab and configure the entity properties:
    Stale data age
    If the system does not receive data for a zone by the time indicated here, it considers the data to be stale.
    Analytics schedule
    (Optional) If the TSS device sends alerts only, select a schedule to receive alerts. Alerts received while the schedule is inactive are discarded.
    Maximum cached data age
    Specifies the maximum time within which data from the TSS zone can be reused.

    When the TSS plugin is restarted, it stops storing the last known status of each zone. If the status is more recent than the time specified, it is used as the initial zone status for the zone. If it is older, the zone initializes with no data available.

    Override icon traffic parameter
    If enabled, select the data type that controls the color of the zone icon.

    For people counting, if the default traffic icon parameter is not set to Volume in the plugin properties, select Volume.

    Zone icon size
    Size of the zone icon displayed on maps, in pixels.
    No data threshold
    If the TSS entity does not receive data from the device by the time indicated here, it triggers the custom TSS no data event.
  5. Click the Communications tab and set the communication settings:
    Period
    Period, in seconds, for collecting and displaying data.
  6. Click the Zones tab.
  7. Click , and in the Add/Edit Genetec™ Zone dialog box, configure the zone's properties:
    ID
    This ID is for identification only and is automatically assigned by increments.
    Zone description
    (Optional) Enter a description for the zone.
    Lane ID
    Enter a lane ID for the zone.
    Classification
    (Optional) Enter an object classification.
    Travel time node ID (Optional)
    Enter the corresponding node ID from the Travel Times Engine where the average speed data is sent to. Travel time detection must be configured for the TSS plugin.
    Direction
    Select the direction of traffic. If you are using analytic confirmation macros, this setting can be configured to find all zones that are the same or opposite direction of the zone that triggered the analytic.
  8. Click OK.
  9. Select the new zone. On the right of the Zone list, set the Zone thresholds.
    When enabled, threshold persistence prevents the zone state from changing rapidly when data is fluctuating around the threshold point.
  10. Repeat steps 7-9 for each zone configured with a third-party traffic sensor system.
  11. Click Apply.
  12. In the entity tree, right-click the TSS entity and select Put Online.
    Security Center starts polling or accepting data from this sensor.

After you finish

Create an event-to-action using the GenetecVSO macro.