About federated entities - 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

A federated entity is any entity that is imported from an independent system through one of the Federation™ roles.

Federated entities do not belong to your local system but you can view and manipulate them in your local system. Starting in Security Center 5.8 GA, you can also change the native settings of a federated entity using the Remote configuration task.

In Config Tool, federated entities have a yellow arrow superimposed on their entity icon (for example, here is a federated alarm entity — ). In Security Desk, the yellow arrow is not displayed on federated entities.

What entities are federated in Security Center

The following entities can be federated from a remote Security Center system:
Component Entities
Video
  • Cameras
  • Camera sequences
  • Virtual cameras (Omnicast™ Federation™ only)
Access control
  • Access control units
  • Doors (Security Center Federation™ only)
  • Elevators (Security Center Federation™ only)
  • Cardholders (Security Center Federation™ only)
  • Cardholder groups
  • Credentials (Security Center Federation™ only)
  • Intrusion detection units
  • Intrusion detection areas
ALPR
  • ALPR units
  • Genetec Patroller™ units
General
  • Alarms
  • Areas
  • Cash registers
  • Networks
  • Maps
  • Zones
  • Output behaviors
  • Custom events
Limitation: ArcGIS maps are only federated in version 5.7 and later. If you federate an older system (5.6 and earlier) that federates a system with an ArcGIS map, you will not be able to see the ArcGIS map in your system.

Entities not listed in the table, such as roles, servers, partitions, visitors, and visitor groups, are not federated.

What you can do with federated entities in Security Desk

You can perform the following operations on federated entities in Security Desk:
  • View live or playback video from federated cameras.
  • Add bookmarks, start and stop recording, and export video from federated cameras.
  • Control federated PTZ cameras (except PTZ locking).
  • Switch cameras on CCTV matrices using virtual cameras federated from Omnicast™ 4.x.
  • View, start and stop cycling, pack and unpack federated camera sequences.
  • Receive, acknowledge, snooze, forward, start and stop cycling, pack and unpack federated alarms.
  • View and control federated tile plugins.
  • Unlock federated doors of an area.
  • Sound and silence reader buzzers.
  • Arm and disarm federated intrusion detection areas.
  • Arm and disarm federated zones.

What you can configure with federated entities

You can make the following changes to federated entities on your local system:
  • Assign logical IDs to federated entities. The logical ID is a local attribute associated with the federated entity to uniquely identify it within the Federation™.
  • Assign local entity names to federated entities. The original entity names remain visible in Config Tool for troubleshooting purposes.
  • Update the custom fields associated to federated entities. Custom fields are local to the Federation™ host.
  • Choose what events you want to receive from the federated system. Based on these events, you can define event-to-actions for federated entities. The actions can either be executed on the Federation™ host or on the federated system.
  • View their activity and audit trail reports in the report pane.
  • Control the visibility of the federated entities to your local users using partitions.
  • Configure visual tracking for cameras federated from Omnicast™ systems.
  • Use federated entities to configure local entities, such as attaching federated cameras to local entities, or using them to define local alarms and camera sequences.

Limitations of federated entities

You cannot do the following with federated entities:
  • You cannot view the custom fields defined on the remote system. Custom fields are not federated.
  • Actions performed on federated entities, such as arming a zone or adding a bookmark to a camera, are not logged in the activity trails of the federated system.
    NOTE: There is one exception to this limitation. Export video actions are logged in both activity trails. On the Federation™ host (local system), the user who performed the activity is logged as the initiator. On the federated system (remote system), the initiator is the Federation™ user, and the user who performed the activity on the Federation™ host is logged as the original initiator. Remote activity logging only works if the federated system is running Security Center 5.7 or later.

Exceptions for federated alarms

Not all alarm properties are federated. Most properties pertaining to the alarm display in Security Desk must be configured locally on the Federation™ host.

The exceptions for federated alarms are the following:
  • The alarm schedule follows the original configuration of the remote system. Because schedule entities are not federated, the default schedule Always is shown instead.
  • Alarm priority:
    • Omnicast™: Original value is not federated. You can configure it (default=1) locally on the Federation™ host.
    • Security Center: Original value is federated and cannot be modified.
  • Reactivation threshold is an inherent property of the alarm and cannot be modified.
  • Entity cycling is a local property to the Federation™ host. You can change its setting and it will not affect the federated system.
  • Automatic acknowledgment is an inherent property of the alarm and cannot be modified.
  • Create an incident on acknowledgment is a local property to the Federation™ host. You can change its setting and it will not affect the federated system.
  • Automatic video recording is an inherent property of the alarm and cannot be modified.
  • Protect recorded video is an inherent property of the alarm and cannot be modified.
  • Video display is a local property to the Federation™ host. You can change its setting and it will not affect the federated system.
  • Alarm procedure (URL):
    • Omnicast™: Original value is not federated. You can configure it locally on the Federation™ host.
    • Security Center: Original value is federated and cannot be modified.
  • Entities that are associated to the federated alarm (cameras, doors, and so on) are inherent properties of the alarm and cannot be modified.
  • Alarm recipients must always be configured locally for the Federation™ host.