add-on
An add-on is a software package that adds tasks, tools, or
specific configuration settings to Security Center systems.
access rule
An access rule entity defines a list of cardholders to whom
access is either granted or denied based on a schedule. Access rules can be applied to
secured areas and doors for entries and exits, or to intrusion detection areas for
arming and disarming.
alarm
An alarm entity describes a particular type of trouble situation
that requires immediate attention and how it can be handled in Security Center. For example, an alarm can indicate
which entities (usually cameras and doors) best describe the situation, who must be
notified, how it must be displayed to the user, and so on.
asset
An asset entity represents any valuable object with an RFID tag
attached, thus allowing it to be tracked by an asset management
software.
Card and PIN
Card and PIN is an access point mode that requires a cardholder to
present their card, and then enter a personal identification number (PIN).
cardholder
A cardholder entity represents a person who can enter and
exit secured areas by virtue of their credentials (typically access cards) and whose
activities can be tracked.
Cardholder access rights
The Cardholder access rights
task is a maintenance task that reports on which cardholders and cardholder groups are
granted or denied access to selected areas, doors, and elevators.
Cardholder activities
The Cardholder activities task
is an investigation task that reports on cardholder activities, such as access denied,
first person in, last person out, antipassback violation, and so on.
Cardholder configuration
The Cardholder
configuration is a maintenance task that reports on cardholder
properties, such as first name, last name, picture, status, custom properties, and so
on.
credential
A credential entity represents a proximity card, a biometrics
template, or a PIN required to gain access to a secured area. A credential can only be
assigned to one cardholder at a time.
entity
Entities are the basic building blocks of Security Center. Everything
that requires configuration is represented by an entity. An entity can represent a
physical device, such as a camera or a door, or an abstract concept, such as an alarm, a
schedule, a user, a role, a plugin, or an add-on.
event
An event indicates the occurrence of an activity or incident, such
as access denied to a cardholder or motion detected on a camera. Events are
automatically logged in Security Center. Every
event has an entity as its main focus, called the event source.
event-to-action
An event-to-action links an action to an event. For example, you
can configure Security Center to trigger an
alarm when a door is forced open.
expansion server
An expansion server is any server machine in a Security Center
system that does not host the Directory role. The purpose of the expansion server is to
add to the processing power of the system.
Federation™
The Federation™ feature
joins multiple, independent Genetec™ IP
security systems into a single virtual system. With this feature, users on the central
Security Center system can view and control entities that belong to remote
systems.
cardholder group
A cardholder group is an entity that defines the common
access rights of a group of cardholders.
iFob
An iFob entity represents a physical cylinder that attaches
permanently to a key, set of keys, or an asset. The iFob has an electronic chip that
gives it a unique identity. It is inserted into a receptor in a cabinet until released
by an authorized user.
Maps
The Maps task is an operation task that
heightens your situational awareness by providing the context of a map to your security
monitoring and control activities.
plugin
A plugin (in lowercase) is a software component that adds a
specific feature to an existing program. Depending on the context, plugin can refer
either to the software component itself or to the software package used to install the
software component.
Plugin
Plugin (with an uppercase, in singular) is the role
template that serves to create specific plugin roles.
plugin role
A plugin role adds optional features to Security Center. A plugin role is created by using
the Plugin role template. By default, it is represented by an orange puzzle piece
in the Roles view of the System task.
Before you can create a plugin role, the software
package specific to that role must be installed on your system.
Plugins
The Plugins task is an administration
task that you can use to configure plugin-specific roles and related
entities.
role
A role is a software component that performs a specific job within
Security Center. To execute a role, you must assign one or more servers to host
it.
Service Release
A Service Release (SR) is a standalone release that
includes minor functionality improvements, bug fixes, and the integration of new
hardware, intrusion devices, and plugins.
Service Release (SR)
Acronym: SR
Traka Asset Management
The Traka Asset Management plugin integrates Traka
users, cabinets, and iFobs into Security Center.
Traka cabinet
A Traka cabinet entity represents a physical Traka cabinet,
which holds the iFobs and associated keys or assets.
Traka monitoring
The Traka monitoring task is an
operation task in Security
Desk that shows
the current content of the Traka cabinets and lists past activity. You can use this task
to see when an asset is in its cabinet, when it is out, and who last had the
asset.
Traka report
The Traka report task is an investigation
task in Security
Desk. You can use it to
investigate Traka user activities at the cabinets and assets (iFobs).