Справочник Пользователя для Checkpoint Systems Inc. EVOLVEF10
F10 Installation Manual
Rev. *60
46 of 71
Japan I: 8.2=9.5 and Japan II: 8.2, 9.5
These applications detect both the 8.2 and 9.5 tags with the same priority. In the Japan I
application, detection of either tag causes an identical alarm response (and is logged identically).
In the Japan II application, each tag causes a different alarm response (and is logged separately).
This application is being used to support a transition from predominantly 9.5 MHz tags on
merchandise to 8.2 MHz tags. These specialized applications are intended to aid in a smooth
transition during the change-over period.
application, detection of either tag causes an identical alarm response (and is logged identically).
In the Japan II application, each tag causes a different alarm response (and is logged separately).
This application is being used to support a transition from predominantly 9.5 MHz tags on
merchandise to 8.2 MHz tags. These specialized applications are intended to aid in a smooth
transition during the change-over period.
Alarm Severity
Alarm severity levels are assigned to particular tag / frequency bands based on different priority or
severity requirements (according to customer needs). This approach bases the alarm response on
the severity level of the alarm, rather than the frequency of the tag.
severity requirements (according to customer needs). This approach bases the alarm response on
the severity level of the alarm, rather than the frequency of the tag.
A total of four (4) levels of Alarm Severity are supported: Low, Medium, High, and Critical.
Default alarm responses for each severity level are explained below. However, specifics such as
lighting patterns and audible alarms can be customized using Smart Alarm Management (SAM)
(refer to “Configuring SAM (Smart Alarm Management)”).
Default alarm responses for each severity level are explained below. However, specifics such as
lighting patterns and audible alarms can be customized using Smart Alarm Management (SAM)
(refer to “Configuring SAM (Smart Alarm Management)”).
Alarm Severity= Low: An alarm with a low severity is considered informational only. The alarm
will be logged in the event history as “Low.” No other alarm response (no lights, no sounder, no
output trigger, etc.) is associated with this level.
will be logged in the event history as “Low.” No other alarm response (no lights, no sounder, no
output trigger, etc.) is associated with this level.
Alarm Severity = Medium: An alarm with a medium severity is a “standard” alarm. Lights and
Sounder are activated. The relay associated with a group alarm (voice alarm) is also activated.
This is the alarm level typically assigned to 8.2 MHz tags. An alarm event logged as “Medium”
appears in the Event History display.
Sounder are activated. The relay associated with a group alarm (voice alarm) is also activated.
This is the alarm level typically assigned to 8.2 MHz tags. An alarm event logged as “Medium”
appears in the Event History display.
Alarm Severity = High: An alarm with a high severity is typically of higher priority than the
medium alarm. Default behavior is a different light or sound pattern from the medium alarm (set
up in DMS) so that it may be differentiated from a medium priority alarm. The relay associated
with the group alarm (voice alarm) is activated for this alarm. An alarm event logged as “High”
appears in the Event History display.
medium alarm. Default behavior is a different light or sound pattern from the medium alarm (set
up in DMS) so that it may be differentiated from a medium priority alarm. The relay associated
with the group alarm (voice alarm) is activated for this alarm. An alarm event logged as “High”
appears in the Event History display.
Alarm Severity = Critical: An alarm with a critical severity the highest priority alarm and is
typically a covert or silent alarm. Default behavior is no light, no sound response and no group
alarm (voice alarm) trigger. Specialized Alarm behavior, if desired, must be set up in SAM. An
alarm event logged as “Critical” appears in the Event History display.
typically a covert or silent alarm. Default behavior is no light, no sound response and no group
alarm (voice alarm) trigger. Specialized Alarm behavior, if desired, must be set up in SAM. An
alarm event logged as “Critical” appears in the Event History display.
Note: The behavior specified here for alarm severity of High or Critical is slightly different than the behavior
for the Evolve family because NGL does not have the Relay1 or Relay 2 dry contact relays that were
previously used for the Video relay.
Table 5.1 (on the following page) shows the Applications that are currently supported along with
the tag frequencies detected and the alarm severity assigned to each of the tag frequencies. In the
table “M” represents Medium Severity, “H” represents High Severity, and “C” represents Critical
Severity. There is no application that currently uses the Low Alarm Severity level.
the tag frequencies detected and the alarm severity assigned to each of the tag frequencies. In the
table “M” represents Medium Severity, “H” represents High Severity, and “C” represents Critical
Severity. There is no application that currently uses the Low Alarm Severity level.