Usage of the Datapoint Hierarchy Screen

This page explains the Datapoint Hierarchy screen in detail — how the tree is structured, what information is shown for each datapoint, how to read and use the status and command panels, and how to interpret the per-datapoint event history. The Datapoint Hierarchy screen is the primary tool for engineers to inspect, diagnose, and control individual points in the connected security subsystems.

A datapoint in SIWENOID v2 represents a single physical or logical monitoring or control point — for example, a detector, a zone, a door contact, a relay output, or a panel. Every datapoint has a type, a status, and a set of possible commands. The hierarchy screen organises all datapoints into a navigable tree structure so the engineer can locate and inspect any point in the installation quickly.

Prev ← The Starting Screen of SIWENOID v2 Next → SIWENOID v2 Intrusion Detection System

The left side of the Datapoint Hierarchy screen displays the full tree of all datapoints connected to SIWENOID v2. The tree has two parallel structures that can be navigated independently:

• Physical tree — reflects the actual hardware structure of the installation. The top level contains the physical containers — one for each connected control panel (for example: a Siemens fire alarm panel, a Bosch intrusion panel, a Hikvision CCTV system). Each physical container expands into the datapoint tree that was imported from that panel's configuration file or fetched via online connection. The physical tree is built automatically during the import process and mirrors the section, zone, and detector hierarchy that exists in the physical panel. It cannot be freely reorganised because it reflects real hardware topology.
• Logical tree — a user-defined organisational structure that groups datapoints by any criteria the engineer chooses, regardless of their physical location. For example, all detectors on the second floor of a building can be grouped into a logical container called “Floor 2”, even if they belong to different physical panels. Logical containers are created manually by the engineer. A datapoint can appear in both its physical location and in one or more logical containers simultaneously — it is the same datapoint, not a copy. For more details on creating and managing logical containers, see Logical Containers.

Clicking on any node in the tree selects it and updates all information panels on the right side of the screen with data for that selected item.

The current status of each node in the tree is indicated visually. Nodes with a non-normal status are highlighted according to their event category colour, allowing the engineer to spot problem areas in the tree at a glance without reading individual datapoint names.

When a datapoint is selected in the tree, the information panel displays four identifying properties:

• 1 — Name in SIWENOID — the name assigned to this datapoint within the SIWENOID v2 software. Engineers can rename datapoints freely to use site-specific naming conventions (for example: “Reception door contact” instead of the panel's default “Zone 01”). This is the name that appears in the signal log and event log.
• 2 — Name in the physical container — the original technical name of the datapoint as it exists in the connected subsystem or panel. This name is read directly from the hardware and cannot be changed from SIWENOID. Displaying this name alongside the SIWENOID name ensures the engineer can always identify which physical point they are looking at, even after renaming.
• 3 — Datapoint type — the functional type of the datapoint as defined by its subsystem driver. Examples include: Zone, Detector, Output, Panel, Loop, Door, Camera. The type determines which statuses and commands are available for this datapoint.
• 4 — Physical parent container — the name of the physical container (control panel) that this datapoint originates from. Every datapoint in SIWENOID v2 always retains its physical origin, regardless of how it has been organised in the logical tree. This means that even when a datapoint is viewed inside a logical container — far from its original position in the physical tree — this field always shows which panel it belongs to. This allows the engineer to trace any datapoint back to its originating hardware at any time, and to move it back to its physical location in the tree if needed. This property is set during import and cannot be changed manually.

The statuses panel shows all possible states (called treatments in SIWENOID v2) that the selected datapoint can have. The current active status of the datapoint is highlighted. If the datapoint is in its normal state, no status is highlighted — normal is the baseline and is not shown as an active condition.

The available statuses depend on the type and physical container of the datapoint. Different device types report different conditions:

• A fire detector may have statuses such as: normal, pre-alarm, alarm, fault, excluded, test mode.
• A zone in an intrusion panel may have statuses such as: normal, alarm, tamper, fault, armed, excluded.
• An output relay may have statuses such as: off (normal), on, fault.

Each status icon is styled according to the event category it belongs to. The event category determines the colour and icon used to represent this status throughout the entire SIWENOID v2 interface — in the signal log, on maps, and in this panel. This ensures visual consistency across all views.

The commands panel shows all commands that SIWENOID v2 can send to the selected datapoint or its parent subsystem. Commands are actions that are transmitted through the subsystem driver to the physical security system — they result in real changes to the connected hardware.

The available commands depend on the datapoint type. Examples:

• A smoke detector may support commands such as: exclude from monitoring, include in monitoring, reset alarm.
• A zone in an intrusion panel may support: arm, disarm, exclude, include.
• An output relay may support: activate output, deactivate output.

To send a command, click the icon of the desired command in the commands panel. The command is transmitted immediately to the connected subsystem through the configured driver. The result of the command will be reflected in the datapoint's status after the subsystem responds.

Important: commands sent from SIWENOID v2 are real operational commands that affect the physical security system. Only trained and authorised engineers should send commands from this screen. All commands are recorded in the event log with the username of the operator who sent them.

The event history panel shows all events recorded for the currently selected datapoint in the last 24 hours. This is a filtered extract from the main event log, automatically scoped to the one selected datapoint. It allows engineers to quickly review recent activity for a specific point without navigating to the full event log and applying filters manually.

Each row in the event history shows:

• 1 — Time — the exact timestamp of the event, recorded with one-second accuracy.
• 2 — Status received — the status that the datapoint transitioned to at that moment (for example: alarm, normal, fault).
• 3 — Acknowledged by — the name of the operator who acknowledged this event in SIWENOID v2, and the time of acknowledgement. If the event has not yet been acknowledged, this field is empty.

For events older than 24 hours, use the main event log with the datapoint name as a filter criterion.

The screenshot above shows the complete Datapoint Hierarchy screen with all panels visible simultaneously. In normal engineering use, the engineer selects a datapoint in the tree on the left, and all four right-side panels update instantly to show the information, statuses, commands, and recent events for that selected point. This single screen provides everything needed to inspect, diagnose, and control any point in the installation without switching to a different view.

—

Prev ← The Starting Screen of SIWENOID v2 Next → SIWENOID v2 Intrusion Detection System