Everyday operation of Siwenoid - Revision history

SWNadmin2 at 11:36, 31 July 2018

2018-07-31T11:36:09Z

← Older revision		Revision as of 11:36, 31 July 2018
Line 204:		Line 204:


	=== 5) Usage of the event log ===		== 5) Usage of the event log ==

	The event log undeletably holds every event from the software. The content of the event log can be printed or exported in .XLSX, .CSV and interactive HTML format. We can search in the event log variously.		The event log undeletably holds every event from the software. The content of the event log can be printed or exported in .XLSX, .CSV and interactive HTML format. We can search in the event log variously.

SWNadmin2 at 07:22, 14 June 2018

2018-06-14T07:22:38Z

Show changes

SWNadmin2 at 14:51, 13 June 2018

2018-06-13T14:51:15Z

← Older revision		Revision as of 14:51, 13 June 2018
Line 20:		Line 20:
	[[Image:Event_Category_1.jpeg\|left\|thumb\|800px]]		[[Image:Event_Category_1.jpeg\|left\|thumb\|800px]]
	<br style="clear: both" />		<br style="clear: both" />


	* ''' 1; Event categories'''		* ''' 1; Event categories'''
Line 40:		Line 39:

	-When servicing a fire alarm unit many detectors can be "Excluded". This can interfere the visibility of the signal log.		-When servicing a fire alarm unit many detectors can be "Excluded". This can interfere the visibility of the signal log.




Line 52:		Line 49:

	-Many detectors of one connected system can signal simultaneously, for example all detectors of a deactivated zone. In the software these can be acknowledged by one click.		-Many detectors of one connected system can signal simultaneously, for example all detectors of a deactivated zone. In the software these can be acknowledged by one click.

SWNadmin2 at 14:48, 13 June 2018

2018-06-13T14:48:12Z

@@ Line 130: / Line 130: @@
 *For example we don't have to send command to the fire alarm unit if the event were acknowledged on the unit itself.
 *If someone on a different Siwenoid client is acknowledged the signal. (And acknowledgement by clients is setupped in Siwenoid)
-=== 4) Detecting and handling alarms from central units and datapoints ===
+'''Click on the event in the signal log!'''

SWNadmin2: /* Everyday operation of Siwenoid */

2018-06-13T14:37:44Z

Everyday operation of Siwenoid

Show changes

SWNadmin2: Created page with "{{Languages|Everyday operation of Siwenoid}} = Everyday operation of Siwenoid = After starting the software we can see the default screen of Siwenoid (→ The starting scr..."

2018-06-13T13:27:20Z

Created page with "{{Languages|Everyday operation of Siwenoid}} = Everyday operation of Siwenoid = After starting the software we can see the default screen of Siwenoid (→ The starting scr..."

New page

{{Languages|Everyday operation of Siwenoid}}

= Everyday operation of Siwenoid =

After starting the software we can see the default screen of Siwenoid (→ The starting screen of Siwenoid)

On everyday operation this screen is what we use most frequently.

=== 1) The event categories bar ===

On the top of the screen we can see all categories in which every signal from the subsystems are arranged into. The colors of the categories are matched to the colors of the Signal log.

*The bar of the event categories are not part of the Signal log but it makes the use of it easier.
*The event categories are always visible and cannot be hidden no mater what window arangement we use.
*Straight forward colors: On the maps, in the event and signal log we see the colors of the event categories. So we can know that every text with red background is about alarms.
 
[[Image:Event_Category_1.jpeg|left|thumb|800px]]
 

* ''' 1; Event categories'''
- All signals, events, alerts from the subsystems are arranged into these categories.
 
-> "NORMAL" status is not shown in the bar of event categories since it is never shown in the signal log.
 
- Normal status is everything when the datapoint is operational and capable of communicating, like an activated smoke detector, an armed intrusion zone etc.

* ''' 2; Hidden event category '''
-We can hide signals from a specific category by clicking on its name. On this case every signal from the selected category are hidden from the signal log.
 

-> The background of the hidden categories are transparent.
 
-> We cannot hide the "ALARM" category.
 

-When servicing a fire alarm unit many detectors can be "Excluded". This can interfere the visibility of the signal log.

* ''' 3; Currently selected datapoint. ''' - Shown in its place of the hierarchy.

* ''' 4; Commands ''' - The commands what can be send to the datapoint are shown here. You can send commands directly to the system by clicking on the command's icon.

* ''' 5; Commands ''' - All events from the last 24 hours for the selected datapoint are shown here. (This is a filtered extract of the event log and only contain events for the one selected datapoint.)

=== 2) Parts of the main screen ===

* '''Attention!''' In Siwenoid every displayed item and view is bound to permissions. A user with fewer permissions can see fewer option than we show here in the manual.
*Although the signal log and especially the alarms cannot be hidden from any user.

Parts of the main Screen!
 
[[Image:Installer_v2_telepitesvege11.jpeg|left|thumb|800px]]
 

* ''' 1; Main menu ''' - The settings of the system can be accessed here.

* ''' 2; Event categories ''' - The signals and alerts from the connected subsystems all fall into one of these categories. (More in the chapter "Setting up")

* ''' 3; Main windows ''' - Under the main tabs we can find the signal log, the datapoint structure and the event log. We also can define our own tabs with maps (for example).

Default tabs:
->Signal log - the alerts and other events are shown here.
->Datapoint hierarchy - here we can oversee the connected systems in a multi-level tree view
->Event log - the software logs every alert and action. We can check and search in the previous events here.

* ''' 4; Parts of the signal log ''' - The most important view of the software since all signals, events and alerts are shown here what the transmitters ("datapoints") of the connected subsystems are sending.

We can see every datapoint's status here where the status is different from "normal" (alarms, exclusions, line erros etc).

* ''' 5; Bulk acknowledge buttons ''' - With these we can acknowledge every alert in the corresponding category (This is ackknowledgement in the software only, no commands are sent to the security systems).

=== 3) The workplaces of the main screen ===
 
[[Image:Ablakok_helyei_%27.jpeg|left|thumb|800px]]

 

We can arrange 4 workspace on the main screen by dragging their side. On these workplaces we can arrange views of the application as we like.

''' Tabs what can be shown on the workplaces '''

Onto these 4 place we can open different application views with the "+" button on top.

These can be:

-Signal log
 
-Datapoint hierarchy screen
 
-Event log
 
-Any map
 
-Logical containers (Sub-trees of the datapoint hierarchy)

The intervention texts for events also opened on the workplace prevoiusly setupped for it.

=== 4) Overview of the datapoint hierarchy screen ===
 
The Datapoint hierarchy scree shows the physical and logical containers of datapoints in a hierarchical tree view. All important details (→1,2,4,5) of the currently selected datapoint (→3) are shown.

The datapoint hierarchy screen have 4 different sections. The left side shows the logical and physical tree of the datapoints.

The right side of the panel if split into 3 sections.
 

[[Image:Hierarchy_v2.jpeg|left|thumb|800px]]
 

* ''' 1; Datapoint informations ''' - The tecnical name (what is inherited from its physical container), the type and the name of the physical container of the datapoint is shown here.(These informations are necessery since the datapoints can be renamed in the software and can be moved to logical containers.)

* ''' 2; Treatments (statuses) ''' - The possible statuses of the selected datapoints can be seen here. The current status of the datapoint is highlighted (except "Normal").

* ''' 3; Currently selected datapoint. ''' - Shown in its place of the hierarchy.

* ''' 4; Commands ''' - The commands what can be send to the datapoint are shown here. You can send commands directly to the system by clicking on the command's icon.

* ''' 5; Commands ''' - All events from the last 24 hours for the selected datapoint are shown here. (This is a filtered extract of the event log and only contain events for the one selected datapoint.)

=== 5) The event log ===
 
Every incoming and outgoing events, signals and commands are logged in Siwenoid with one second accuracy. So every event can be traced back, can be filtered and can be exported.

[[Image:123.jpeg|left|thumb|800px]]
 

* '''1;''' Every events are shown by the color of its event category. The time, status and the corresponding datapoint is shown.

* '''2;''' Filtering options. We can search and filter the event log by date and time interval, plus we can search for phrases and names with the input fields under the columns.

* '''3;''' Exporter buttons. The filtered event log of the Siwenoid software can be printed or exported in .XLSX, .CSV and interactive HTML format.

* '''4;''' Frequent searches (like a specific door's signals or often alerting smoke detector) can be saved for quick access. These can be loaded instantly from the dropdown menu (fast search).