If you’re using Security Center 5.12 or later, use the Synergis™ IX intrusion detection area mapping task to configure the mapping of imported intrusion detection areas to Security Center areas.
Before you begin
What you should know
The top section of the task workspace is the mapping
report. Each row in the report describes an intrusion detection area with the
following information:
- Name of the Synergis™ Cloud Link unit.
- Name of the Synergis IX unit.
- Name of the intrusion detection area.
- Name of the secured area mapped to the intrusion detection area.
- Mapping status. Either a mapping error or a blank field when there is no mapping error.
Procedure
-
(Optional) From the Config Tool homepage, open the Area view
task.
This is for your convenience. You’ll frequently need to access the Area view throughout this process.
-
From the Config Tool homepage, open the Synergis™ IX intrusion detection area
mapping task, hereafter referred to as the Mapping task,
and click Search.
The mapping errors (
) found in the system are displayed in the mapping report. Correct mappings are hidden by default.
-
Set the search filters to increase or reduce the number of elements displayed in the
report.
- Display options
- Expand this filter to select what you want to include in the report:
- Include correct mappings
- Correct mappings are excluded by default from the report. Select this option
to include the correct mappings.NOTE: The absence of mapping errors does not mean that your intrusion detection areas are fully configured. We therefore recommend that you display the correct mappings until you’ve gone through the complete list of intrusion detection areas at least once.
For a checklist of what needs to be configured for each intrusion detection area, see Configuring the imported intrusion detection areas in Security Center.
- Include system intrusion detection areas
- An intrusion detection area named System Area is created by default
for each Synergis™ IX controller. The System Area is used to monitor
trouble inputs, which are automatically assigned to this area.NOTE: System areas do not need to be mapped to secured areas, which is why they are excluded by default from the mapping report. However, we recommend grouping all system areas under a single Security Center area for ease of viewing. Select this option to show system areas in the mapping report.
- Entities
- Expand this filter to select which entities or entity types you want to include in the mapping report.
- In the mapping report, click the first row.
-
If the secured area is not defined, click the Secured area
drop-down, select the corresponding area, and click Apply.
NOTE: A given secured area (
) can only be assigned to one intrusion detection area. If no corresponding secured area exists, create one from the Area view task.
The following happens (visible from the Area view task):- Two new configuration tabs, Synergis™ IX and
Intrusion detection rules, are added to the intrusion
detection area. These new settings are also found in the Mapping
task.NOTE: In version 5.13.2.0, the feature previously named Access rules has been renamed to Intrusion detection rules. This is a naming change only. The feature's functionality remains the same across versions.
- The system automatically moves the intrusion detection area under the selected area in the Area view.
- If the assigned area has no door, the system automatically creates a virtual door
(
) named after the Synergis IX unit under that area.
Best Practice: We recommend giving the new door a unique name for easy identification.
- Two new configuration tabs, Synergis™ IX and
Intrusion detection rules, are added to the intrusion
detection area. These new settings are also found in the Mapping
task.
-
If a secured area is assigned but has no perimeter door, do the following:
-
Click one of the Reader on door side drop-down and select a
reader.
The selected reader must be on the same Synergis IX unit as the intrusion detection area.
- Click Apply.
A virtual door () named after the Synergis IX unit is created under the assigned area. Change its configuration as necessary.
-
Click one of the Reader on door side drop-down and select a
reader.
-
If the secured area is marked by a light bulb icon (
), do the following:
The light bulb marker is a reminder that the intrusion detection area is not placed under the secured area in the entity hierarchy. It is not an error, but for ease of viewing, we recommended moving the intrusion detection area () under the secured area (
) in the area view.
-
If the door of the secured area has no reader, do the following:
-
Click one of the Reader on door side drop-down and select a
reader.
NOTE: The selected reader must be on the same Synergis IX unit as the intrusion detection area.
- Click Apply.
-
Click one of the Reader on door side drop-down and select a
reader.
-
If the reader of the secured area door is not on the same Synergis IX unit as the
intrusion detection area, do one of the following and click
Apply.
- If the wrong secured area is assigned to the intrusion detection area, correct the assignment.
- If the wrong door is assigned to the secured area, delete it and add the correct door.
- If the wrong reader is assigned to the door, click the Reader on door side drop-down and select the correct reader.
-
(Optional) Under the Intrusion detection
area - Schedules section, configure the arming and disarming schedules.
There are three schedules that you can configure:
- Arm and disarm
- Schedule that defines the periods when the intrusion detection area is automatically
armed and disarmed. It must be used with the following options that are configured in
the Synergis™ IX Portal under Programming > Areas > Configuration.
- Disarm area when schedule starts
- When enabled, the area automatically disarms when the selected schedule starts.
- Arm area when schedule ends
- When enabled, the area automatically arms when the selected schedule ends.
- Normal arm
- Normal arm schedule. Period 2 of the selected schedule defines the period when the area can be armed. If the area is armed before the start of Period 2, an Early to Arm event is generated. If the area is still disarmed when Period 2 ends, the system generates a Late to Arm event. No event is generated if the area is armed while Period 2 of the schedule is valid.
- Normal disarm
- Normal disarm schedule. Period 1 of the selected schedule defines the time period when the area can be disarmed. If the area is disarmed before the start of Period 1, an Early to Disarm event is generated. If the area is still armed when Period 1 ends, the system generates a Late to Disarm event. No event is generated if the area is disarmed while Period 1 of the schedule is valid.
- Click Apply.
-
Under the Intrusion detection
rules section, configure who can arm and disarm during the controlled access
periods.
-
Select how intrusion detection rules are applied:
- Arming and disarming
- Use the same set of access rules for arming and disarming.
- Either arming or disarming
- Use different sets of access rules for arming and disarming.
-
Under the Intrusion detection rules section, click
Add an item (
), select access rules (and cardholders), and then click OK.
If you assign cardholders or cardholder groups directly to the area, the cardholders can arm or disarm at all times. - If you chose to use different sets of access rules for arming and disarming, then configure the second set of access rules.
-
Select how intrusion detection rules are applied:
-
Click Apply.
There’s no more mapping error. If you chose not to include correct mappings, the row is removed from the mapping report.
- Repeat the same process for all intrusion detection areas.