The Starting Screen of SIWENOID v2

This page describes the main user interface of SIWENOID v2 as it appears after a successful login. It explains the purpose and function of each screen area, the workspace layout system, the datapoint hierarchy panel, and the event log. Understanding this screen is essential before proceeding with system configuration, as all engineering and operator functions are accessed from here.

Note: SIWENOID v2 is under active development. The appearance of certain screens may differ slightly between software versions. Screenshots in this manual may not match the exact version installed on your system, but the structure and function of each area remains consistent.

Prev ← User Permissions v2 Next → Usage of Datapoint Hierarchy Screen

After a successful login, the SIWENOID v2 main screen is displayed. The layout the user sees depends on any previously saved workspace configuration. On a first login with a new account, the default layout is shown with the signal log open in the foreground.

Every element visible on the main screen is subject to the logged-in user's permissions. A user with limited permissions will see fewer menu items, tabs, and controls than a user with full administrative rights. The signal log and the alarm display are the only views that cannot be hidden from any user — these are always accessible regardless of permission level.

The main screen is divided into five functional areas:

1 — Main Menu

The main menu bar runs along the top of the screen and provides access to all system configuration and management functions. This includes user management, subsystem configuration, category settings, forced actions, tasks, backup, and system preferences. Menu items that the current user does not have permission to access are hidden or greyed out.

2 — Event Categories

The event category bar displays the categories into which all incoming signals from connected subsystems are sorted. Each category corresponds to a type of event — for example: alarm, fault, exclusion, or status. Categories are defined and configured by the engineer during system setup. The category bar gives operators an immediate visual overview of how many unacknowledged events exist in each category, typically using colour coding.

3 — Main Workspace Tabs

The central area of the screen is divided into tabbed workspaces. Three tabs are present by default:

• Signal Log — displays all active signals and events from connected subsystems whose status differs from normal. This includes alarms, faults, exclusions, and communication errors. This is the primary operational view for operators.
• Datapoint Hierarchy — displays the full tree structure of all connected subsystems and their datapoints. Engineers use this view for configuration, diagnostics, and sending commands to individual points.
• Event Log — displays the complete historical log of all events, signals, and commands recorded by the system. Supports filtering, searching, and export.

Additional custom tabs can be created and assigned to any workspace, for example to display site maps or logical container views. Each tab is independently configurable per user workspace layout.

4 — Signal Log Panel

The signal log is the most operationally critical view in SIWENOID v2. It shows every datapoint in the system whose current status is different from normal. This includes:

• Active alarms from intrusion, fire, or other connected subsystems
• Technical faults and communication errors
• Datapoints that have been manually excluded from monitoring
• Any other non-normal status reported by a connected subsystem

Each row in the signal log shows the datapoint name, its current status, the time the status was received, and the event category it belongs to. Rows are colour-coded according to their event category. The signal log updates in real time as new events arrive from connected subsystems.

5 — Bulk Acknowledge Buttons

The bulk acknowledge buttons allow an operator to acknowledge all unacknowledged events within a specific category simultaneously. Acknowledging an event in SIWENOID v2 is a software-level action only — it records that an operator has reviewed the event. No command is sent to the physical security system as a result of acknowledgement. Individual events can also be acknowledged one by one directly from the signal log.

The main screen supports up to four independent workspace panels arranged side by side. The size of each panel can be adjusted by dragging the dividers between them. This allows engineers and operators to customise the screen layout to match their workflow — for example, displaying a site map alongside the signal log.

Each workspace panel can display any of the following views, selected by clicking the + button at the top of the panel:

• Signal Log — the active events display described above
• Datapoint Hierarchy Screen — the full subsystem tree
• Event Log — the historical event record
• Any configured map — a graphical floor plan or site diagram with live datapoint status indicators
• Logical Containers — filtered subtrees of the datapoint hierarchy, useful for focusing on a specific building area or subsystem

When an event has an associated intervention text (a predefined procedure for operators to follow when a specific event occurs), that text is automatically opened in the workspace panel that has been designated for intervention display. This designation is part of the workspace configuration.

Workspace layouts are saved per user account. Each user's layout is restored automatically on their next login.

The datapoint hierarchy screen provides a structured view of all datapoints connected to SIWENOID v2, organised in a tree structure that reflects the physical and logical organisation of the security installation.

The screen is divided into five sections:

Left panel — Hierarchy Tree

The left side of the screen shows the full tree of physical and logical containers, with datapoints as leaf nodes. Physical containers represent the actual hardware structure (for example: panel → zone → detector). Logical containers are user-defined groupings that can cut across the physical structure (for example: grouping all detectors on the second floor regardless of which panel they belong to). A datapoint can appear in both its physical location and in one or more logical containers simultaneously.

Right panel — four information sections

• Section 1 — Datapoint Information: Displays the technical name inherited from the physical container, the datapoint type, and the name of the physical container it belongs to. This information is particularly important because datapoints can be renamed in the software and moved into logical containers — the technical name and physical container name always identify the actual hardware point regardless of any renaming.
• Section 2 — Treatments (Statuses): Lists all possible statuses that the selected datapoint can have. The current active status is highlighted. The normal status is not highlighted since it represents the idle state. Examples of possible statuses include: normal, alarm, pre-alarm, fault, excluded, tamper.
• Section 3 — Selected Datapoint: Shows the currently selected datapoint highlighted within the hierarchy tree, confirming which point the right-panel information refers to.
• Section 4 — Commands: Lists all commands that can be sent to the selected datapoint. Commands are actions that SIWENOID v2 can transmit to the physical security system through the subsystem driver — for example: reset, exclude, include, output on/off. Click the command icon to send the command directly to the connected system.
• Section 5 — Recent Events: Displays all events recorded for the selected datapoint in the last 24 hours. This is a filtered extract from the main event log, scoped to the single selected datapoint. It allows an engineer to quickly review a point's recent history without searching the full event log.

SIWENOID v2 records every incoming signal, outgoing command, operator action, and system event in the event log with one-second timestamp accuracy. The event log is a permanent, searchable audit trail of everything that has happened in the system.

The event log screen has four functional areas:

• 1 — Event List: All events are displayed as rows, colour-coded by their event category. Each row shows the timestamp, the event status, and the name of the datapoint or system component that generated the event. Events are shown in reverse chronological order by default (newest first).
• 2 — Filtering Options: The event log can be filtered by date and time range to narrow the display to a specific period. Each column also has a text input field directly below the column header, allowing the engineer to filter by any combination of datapoint name, status text, or other fields simultaneously. Multiple filters can be active at the same time.
• 3 — Export Buttons: The currently filtered view of the event log can be exported in three formats: .XLSX (Microsoft Excel spreadsheet), .CSV (comma-separated values, compatible with any spreadsheet or database tool), and interactive HTML (a self-contained web page that can be shared and viewed in any browser without additional software). The filtered view can also be sent directly to a printer.
• 4 — Saved Searches (Fast Search): Frequently used filter combinations can be saved as named searches and recalled instantly from the fast search dropdown menu. This is useful for recurring operational tasks such as reviewing all events from a specific door, checking a frequently alerting detector, or pulling the daily alarm report for a specific area.

—

Prev ← User Permissions v2 Next → Usage of Datapoint Hierarchy Screen