During the mapping process, detector data from the graphic import (CAD graphic objects) is merged with data from the alarm systems (alarm system objects). Mapping must be performed in cases where an object is saved multiple times in the Siveillance Control database. During the mapping process, the file attributes for one data source are merged with the file attributes for another data source for the selected MOT (Managed Object Type). A typical mapping application is the transfer of GIS coordinates from placeholders.

Mapping Objects

  • The Device Mapping perspective is displayed.
  • The graphic has been calibrated and mapped.
  • The GIS positions for all graphical objects has been entered.
  • If necessary, a backup copy of the database exists, since mapping is an irreversible process.
  1. Select a MOT for which you want to map the attributes:
  • Candidate From: Select a data source.
  • Candidate Into: The attribute values are transferred to this data source.
  1. Select the relevant data source for both MOTs.
  1. Identify identical objects in both the Candidate From and Candidate Into lists. The following options are available:
  • Merging individual objects: You can merge only individual objects.
  • Merging related objects: You can merge individual and multiple objects.
  • Mass merging: You can merge a large number of objects if the object names derived from the graphic import deviate from the object names derived from the alarm systems.
  1. In the Merge Preview list, carefully check the accuracy of the objects that are identified as related.
  1. If you are satisfied with the results, click Commit Merge. Otherwise click Cancel Merge.
  1. Repeat this process until all related objects are mapped.

Editing Object Lists

You can edit the displayed columns for the object lists in both Candidate From and Candidate Into.

  • The Device Mapping perspective is displayed.
  1. In the Candidate From data source, select Display.
  1. Mark attributes you want to display as columns.
  1. Click OK.
  1. In the Candidate Into data source, select Display.
  1. Mark attributes you want to display as columns.
  1. Click OK.

Defining Transfer Attributes

  • The Device Mapping perspective is displayed.
  1. In the Candidate From data source, select Transfer.
  1. If the objects from Candidate From already exist in the Location Tree, you can define the following behavior in the Handle references drop-down list:
  • Delete: The objects from Candidate From in the Location Tree are deleted from the Location Tree and have to be repositioned after the mapping.
  • Move: The objects from Candidate From in the Location Tree are replaced by the mapped objects from Candidate Into.
  1. In the Conflict Resolution Strategy, you have the following options:
  • Keep: The attribute values in the data source on the right are retained without exception.
  • Add: If an attribute value is set in the data source on the right, retain this value. If no attribute value is set in the data source on the right, take the attribute value from the data source on the left if available.
  • Force Overwrite: Overwrites attribute values in the data source on the right with the attribute values from the data source on the left.
  • Overwrite: Functions as Force Overwrite. If no attribute value is set in the data source on the left, any attribute value set in the data source on the right is retained.
  1. Click OK.

Merging Individual Objects

  • The Device Mapping perspective is displayed.
  1. Select an object in the Candidate From list.
  1. Drag this object to the related object in the Candidate Into list.
  • The object is removed from both object lists and transferred to the preview list.

Merging Related Objects

  • The Device Mapping perspective is displayed.
  1. Select one or more objects in the Candidate From object list.
  1. Select the related objects in the Candidate Into list.
  1. Click Correlate Selected.
  • The object is removed from both object lists and transferred to the preview list.

Mass Merging

  • The Device Mapping perspective is displayed.
  1. Click Device Mapping: not selected for Candidate From.
  1. Select the attribute to be filtered from the Device Mapping Attribute drop-down list.
  1. In the Device Mapping Pattern field, enter a regular expression or name.
  1. Click OK.
  • The objects that correspond to the device mapping patterns are highlighted.
  1. Click Device Mapping: not selected for Candidate Into.
  1. Select the attribute to be filtered from the Device Mapping Attribute drop-down list.
  1. In the Device Mapping Pattern field, enter a regular expression or name.
  1. Click OK.
  • The objects that correspond to the device mapping patterns are highlighted.
  1. Click Autocorrelate.
  • Objects with identical expression or name are removed from both object lists and transferred to the preview list.

Mapping with Patterns

You can use a mapping pattern to compare object names that were imported to existing names. The following sections give an overview of the usage of mapping patterns and are only intended as an example. Various other options for using regular expressions can be found in tutorials on the Internet.

  • The MOT object and the data source have been selected.
  • The attributes to be displayed have been selected using Display.
  • The transfer method Move or Delete has been selected.
  • In the Transfer dialog box, the conflict resolution strategy has been selected.
  1. To edit the character string and asterisk (*), enter the following expressions:
  • Character string: Enter a character string you want to filter preceding (.*).
  • Asterisk: Add *\ to the mapping pattern filtered in the previous step.
  1. To edit the spaces and slashes, you have the following options:
  • Spaces: Enter the expression (.*) for any character and then enter the spaces to be removed.
  • Slashes: Add / to the mapping pattern filtered in the previous step.

Mapping Collective Detector Lines

  • The Device Mapping perspective is displayed.
  1. Select a MOT for which you want to map the attributes:
  • Candidate From: Select TBS Object.
  • Candidate Into: Select Collective Detector Line.
  1. Select the relevant data source for both MOTs.
  • Candidate From: Select vu_dp-[gateway_name]-[component_name]-[vu_unit_name]-[unit_name].xml.
  • Candidate Into: Select manuallyCreated.
  1. In the Candidate From data source, select Transfer.
  1. In the Handle references drop-down list, select Move.
  1. In the Conflict Resolution Strategy, select Force Overwrite for the External ID, External source and Fix GIS position attributes. If necessary, transfer other parameters of the detector zone.
  1. Click OK.
  1. Identify identical objects in both the Candidate From and Candidate Into lists and merge them.
  1. In the Merge Preview list, carefully check the accuracy of the objects that are identified as related.
  1. If you are satisfied with the results, click Commit Merge. Otherwise click Cancel Merge.
  1. Repeat this process until all related objects are mapped.