allowed user
An allowed user of a Genetec Mission Control™ profile is a user to whom the profile
can be assigned, as long as the user is connected to Security Center through Security
Desk.
automation
Automation is a series of activities associated to an incident
type. These activities are performed by the system during the life cycle of an incident.
The activities can change the incident state and properties, affect other entities in
the system, or simply wait for a condition to become true. The automation workflow helps
automate simple tasks, such as exporting the incident when it is resolved, so operators
can focus on more complex ones. (Replaces the term incident workflow)
collaborative incident
A collaborative incident is an incident type that
requires the collaboration of multiple teams to resolve. Each team has specific tasks to
follow, which are represented by sub-incidents. The collaborative incident is resolved
when all its sub-incidents are resolved.
dynamic user procedure
A dynamic user procedure (or dynamic SOP) is a standard
operating procedure where the step sequence depends on the response provided by the
operator at each step. The dynamic SOP is represented by a flowchart in Config
Tool.
Also known as: dynamic
SOP
failover
Failover is a backup operational mode in which a role (system
function) is automatically transferred from its primary server to a secondary server
that is on standby. This transfer between servers occurs only if the primary server
becomes unavailable, either through failure or through scheduled downtime.
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.
Genetec Mission Control™
Genetec Mission Control™
is a collaborative decision management system that provides organizations with new
levels of situational intelligence, visualization, and complete incident management
capabilities. It allows security personnel to make the right decision when faced with
routine tasks or unanticipated situations by ensuring a timely flow of information. To
learn more about Genetec Mission Control™, refer to the
Genetec™
resource center.
Genetec Mission Control™ Web API
The Genetec Mission Control™ Web API
is a suite of development tools with which our partners and customers can enhance their
collaborative decision management systems by integrating additional software and custom
functionality.
High availability
High availability is a design approach that enables a system
to perform at a higher than normal operational level. This often involves failover and
load balancing.
incident (Genetec Mission Control™)
A Genetec Mission Control™
incident is an undesirable or unusual situation that needs investigation and resolution,
or a routine, scheduled task that requires monitoring.
incident category
An incident category is an entity that represents a
grouping of incident types that have similar characteristics.
Incident configuration
The Incident configuration
task is an administration task that you can use to configure the incident types, the
incident categories, and the support documents for Genetec Mission Control™. You can also use this task to
generate reports on the changes made to incident types.
Incident Manager
The Incident Manager is the central role that recognizes
situational patterns, and triggers incidents in a Genetec Mission Control™ system. This role manages the
automation workflows and keeps track of all user activities that are related to
incidents.
Incident monitoring
The Incident monitoring task is
an operation task that you can use to monitor and respond to incidents. From this task,
you can see the incidents displayed on a map, thus improving your situational
awareness.
incident owner
The incident owner is the incident recipient who took
ownership of the incident. Only the incident owner can take actions to resolve the
incident. An incident can only have one owner at a time.
incident recipient
An incident recipient is a user or user group that the
incident has been dispatched to. Incident recipients can see the incident in the
Incident monitoring task.
Incident report
The Incident report task is an
investigation task that you can use to search, review, and analyze Genetec Mission Control™ incidents.
incident supervisor
An incident supervisor is a user who sees an incident
in the Incident monitoring task because they supervise the incident
recipients. Incident supervisors are not incident recipients themselves. A user cannot
be both supervisor and recipient of the same incident.
incident trigger
An incident trigger is an event or a sequence of events
that can trigger an incident. The Genetec Mission Control™ Rules Engine looks for specific combinations of events (type, time, correlation, and
frequency) to determine whether to trigger an incident.
incident type
An incident type entity represents a situation that
requires specific actions to resolve it. The incident type entity can also be used to
automate the incident detection in Genetec Mission Control™ and to enforce the standard operating procedures that your security team must
follow.
Monitoring
The Monitoring task is an operation task
that you can use to monitor and respond to real-time events that relate to selected entities.
Using the Monitoring task, you can also monitor and respond to
alarms.
profile
A profile in Genetec Mission Control™ is an incident filter used to
distribute active incidents among the operators who are currently logged on to the
system. Profiles filter incidents by type and by occurrence location.
Rules Engine
The Rules Engine is the component of the Genetec Mission Control™ system that analyzes and correlates
the events collected by Security Center, based
on predefined rules. The Rules Engine uses these events to detect and trigger incidents
in the Genetec Mission Control™ system.
simple user procedure
A simple user procedure (or simple SOP) is an ordered list of
steps that do not involve multiple-choice questions. Operators might be allowed to
resolve the incident without validating all the steps, or to complete the steps out of
sequence, depending on the configuration.
Also known as: simple
SOP
standard operating procedure
A standard operating procedure (SOP) or user procedure is a series
of steps that the operator must follow before changing an incident state to
Resolved. Each step can range from a simple task, such as Call 911, to
a complex task that requires support documents to accomplish. All actions taken by the
operator are logged by the system in the incident history for audit
purposes.
standard operating procedure (SOP)
Acronym:
SOP
Also known as: user
procedure
threat level
Threat level is an emergency handling procedure that a Security
Desk operator can enact on one area or the entire system to deal promptly with a
potentially dangerous situation, such as a fire or a shooting.
Time To Response or Time To Resolution
Time To Response or Time To Resolution (collectively TTR) are
metrics used in Genetec Mission Control™ that refer to
how long it takes to respond to incidents, and resolve incidents and dynamic standard
operating procedure steps.
Time To Response or Time To Resolution (TTR)
Acronym:
TTR
user procedure
Replaces the term "incident procedure". See "standard
operating procedure".
validated step
A validated step in an standard operating procedure (SOP)
is a step that is either completed or skipped with a justification.
Vault
The Vault is a tool that displays your saved snapshots and
exported G64, G64x, and GEK (encrypted) video files. From the Vault, you can view the video
files, encrypt and decrypt files, convert files to ASF, or package files with the Genetec™ Video
Player.