Warning: file_put_contents(): Only 0 of 20802 bytes written, possibly out of free disk space in /var/www/bluespice/w/extensions/BlueSpiceVisualDiff/includes/HTMLDiffEngine.class.php on line 113

Warning: file_put_contents(): Only 106496 of 110567 bytes written, possibly out of free disk space in /var/www/bluespice/w/extensions/BlueSpiceVisualDiff/includes/HTMLDiffEngine.class.php on line 113

Warning: file_put_contents(): Only 0 of 64 bytes written, possibly out of free disk space in /var/www/bluespice/w/extensions/BlueSpiceVisualDiff/includes/HTMLDiffEngine.class.php on line 68

Warning: file_put_contents(): Only 0 of 108 bytes written, possibly out of free disk space in /var/www/bluespice/w/extensions/BlueSpiceVisualDiff/includes/HTMLDiffEngine.class.php on line 173

Warning: file_put_contents(): Only 0 of 7073 bytes written, possibly out of free disk space in /var/www/bluespice/w/extensions/BlueSpiceVisualDiff/includes/UnifiedTextDiffEngine.class.php on line 24

Warning: file_put_contents(): Only 0 of 64 bytes written, possibly out of free disk space in /var/www/bluespice/w/extensions/BlueSpiceVisualDiff/includes/UnifiedTextDiffEngine.class.php on line 67

Warning: file_put_contents(): Only 0 of 108 bytes written, possibly out of free disk space in /var/www/bluespice/w/extensions/BlueSpiceVisualDiff/includes/HTMLDiffEngine.class.php on line 173
Gate ~ FMCU ~ management dashboard/en: Unterschied zwischen den Versionen – Maxcrc MediaWiki

Gate ~ FMCU ~ management dashboard/en: Unterschied zwischen den Versionen

(Markierung: 2017-Quelltext-Bearbeitung)
(Authorization)
(Markierung: 2017-Quelltext-Bearbeitung)
 
(149 dazwischenliegende Versionen von 5 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
{{translate|Gate ~ FMCU Galaxy Gate ~ management dashboard}}
+
{{translate|Wanzl Access Manager ~ Management Dashboard}}
  
==Connectivity Board==
+
{{DISPLAYTITLE:Wanzl Access Manager ~ Management Dashboard}}
 +
 
 +
__TOC__
 +
 
 +
<br />
 +
<br />
 +
<br />
 +
<br />
 +
 
 +
=General=
 +
<br />
 +
The Wanzl Access Manager offers a central dashbaord for access controls in a homogeneous interface, displays the corresponding states and supports the user in the administration of these components. The Wanzl Access Manager is a leading platform for monitoring and managing access controls of security areas.
 +
<br /><br />
 +
 
 +
=Sign Up=
 +
<br />
 +
Please enter the login information provided by support here to log in to the central dashboard.
 +
<br />
 +
[[Datei:Signupfmcu.png|800x800px]]
 +
<br />
 +
 
 +
=Headline=
 +
<br />
 +
[[Datei:FMCU_Headline.png|links|rahmenlos|1000x1000px]]
 
<br />
 
<br />
 
{| class="wikitable"
 
{| class="wikitable"
!Contact
+
!Number
!Modbus Value/Flag
+
!Function
!Type
+
|-
!Impulse
+
|1
!Description
+
|Button Management Dashboard
 +
|-
 +
|2
 +
|Administration
 +
|-
 +
|3
 +
|Events Button
 
|-
 
|-
|'''A8'''
+
|4
|0x47
+
|Cards Button
|Output
 
|Yes (200ms)
 
|Person has entered
 
 
|-
 
|-
|'''A9'''
+
|5
|0x48
+
|Statistics Button
|Output
 
|No
 
|Alarms*
 
 
|-
 
|-
|'''E3'''
+
|6
|0x004
+
|Logged in User
|Input
 
|No
 
|Fire Alarm
 
 
|-
 
|-
|'''E4'''
+
|7
|0x008
+
|Log out Button
|Input
 
|No
 
|Emergency State button**
 
 
|-
 
|-
|'''E6'''
+
|8
|0x020
+
|Languages menu
|Input
 
|Yes (200ms)
 
|Card is valid, open the gate
 
 
|-
 
|-
|'''E7'''
+
|9
|0x040
+
|Adjust the display to entire width of the screen
|Input
 
|Yes (200ms)
 
|Card is invalid, do not open the gate  
 
 
|}
 
|}
<nowiki>*</nowiki>A9 Alarms:
+
<br />
  
*Gate is out of order, when a mandatory device is broken or a connection to the server is broken (if the server is used in the solution).
+
=Menu items=
*Tailgating or other unwanted actions.
+
<br />
*Entry barcode scanner is broken or it is a stub.
+
==Facilities==
*Gate in in the '''Fire Alarm''' or '''Emergency''' state. The alarm is produces as a repetitive pulse signal (700ms).
+
<br />
*Gate is open only for exit.
+
<syntaxhighlight>
 +
https://<dns-name or ip-address>/gates
 +
</syntaxhighlight>
 +
In this view, all access controls are displayed in an intuitive interface. There are grouping options in two categories. First, you can group by '''Location'''. Within the location you can then summarize different '''Locations'''.
 +
<br />
  
After the Emergency State button pressed, the gate switches to the Emergency State. Then only exit from this state is to restart the gate.
+
Individual gates can be added via the menu item "'''New'''".
 +
<br />
 +
[[Datei:FMCU_Facilities.png|800x800px]]
 +
<br />
  
The signal can be set/received to/from a contact from any of the halves of the gate.
+
When the light view is off, the access controls are shown in the list.
 +
<br />
 +
[[Datei:FMCU_GridView.png|800x800px]]
 +
<br />
  
==Configuration Management==
+
When one or more facilities are selected with the control,
<br />User Interface
+
<br />
 +
[[Datei:FMCU-Server-Check-Select.png|ohne|link=]]
 +
<br />
 +
the facilities can be controlled with the following buttons:
 +
<br />
 +
{| class="wikitable"
 +
|+
 +
!'''Symbol'''
 +
!'''Description'''
 +
!'''Note'''
 +
|-
 +
|[[Datei:FMCU_Normal_Lock_Button.png|rahmenlos|160x160px]]
 +
|change to normal state, lock the doors in both directions
 +
|
 +
|-
 +
|[[Datei:FMCU Lock OpenService Single.png|rahmenlos]]
 +
|open the door permanently or open it for a single person
 +
|towards the entrance
 +
|-
 +
|[[Datei:FMCU Lock OpenService Single.png|rahmenlos]]
 +
|open the door permanently or open it for a single person
 +
|toward the exit
 +
|-
 +
|[[Datei:FMCU_On_Off_Button.png|rahmenlos|98x98px]]
 +
|Turn the '''Cleaning''' mode on and off
 +
|cleaning
 +
|-
 +
|[[Datei:FMCU_On_Off_Button.png|rahmenlos|98x98px]]
 +
|Toggle '''Emergency Open''' mode on and off
 +
|Emergency
 +
|}
 +
<br />
  
The Galaxy Gate is configured through the '''/configuration''' page. If the server is running at 192.168.1.221 and port is 8888, the url is:
+
<br />
<nowiki>http://192.168.1.221/configuration</nowiki>
+
The Gate display contains the following controls:
[[Datei:gg-configuration-main.png|zentriert|rahmenlos|configuration page]]
 
<br />There are two buttons on the page:
 
 
{| class="wikitable"
 
{| class="wikitable"
!Name
+
|+
!Description
+
!'''Symbol'''
!Action
+
!'''Description'''
 +
!'''Note'''
 +
|-
 +
|[[Datei:FMCU-Server-Check-Select.png|ohne|link=]]
 +
|choose the gate
 +
|to activate the buttons above ('''Normal''', '''Lock Out''', etc.)
 +
|-
 +
|[[Datei:FMCU-Server-Link-Gate.png|ohne|link=]]
 +
|Navigate to the '''Facilities''' page
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Button-Gate-View.png|ohne|link=]]
 +
|Navigate to the page'''Gate-View'''
 +
|
 +
|-
 +
|[[Datei:FMCU Normal Button.png|rahmenlos|212x212px]]
 +
|change to Normal state
 +
|
 +
|-
 +
|[[Datei:FMCU Lock Button.png|rahmenlos|210x210px]]
 +
|lock the doors in both directions
 +
|
 +
|-
 +
|[[Datei:FMCU Single Free Button.png|rahmenlos|126x126px]]
 +
|open the door in the direction of entrance/exit for a single person
 +
|
 
|-
 
|-
|'''Save'''
+
|[[Datei:FMCU Single Free Button.png|rahmenlos|126x126px]]
|Saves the modified configuration to the server
+
|lock the door in the direction of entrance/exit
|Post
+
|
 
|-
 
|-
|'''Reset'''
+
|[[Datei:FMCU Open Service Button.png|rahmenlos|125x125px]]
|Discards any changes by reloading the configuration from the server
+
|permanently open the door in the direction of entrance/exit
|Get
+
|
 
|}
 
|}
The configuration is split into sections and subsections:
 
  
*General
 
**Dispatcher
 
**Miscellaneous
 
*Devices
 
**Barcode Reader Entry
 
**Barcode Reader Exit
 
**Gate
 
**Tracking Camera
 
**Audio Player
 
**Camera
 
*Displays
 
**Display Gate Entry
 
**Display Gate Exit
 
**Display Entry
 
**Display Exit
 
**Display TimeInfo
 
  
Here are some screenshots:
+
 
[[Datei:gg-general.png|zentriert|904x904px]][[Datei:gg-barcode-reader-gate.png|zentriert|952x952px]]<br />
+
 
[[Datei:gg-audio-player-camera.png|zentriert|841x841px]]
 
 
<br />
 
<br />
[[Datei:gg-tracking-camera.png|zentriert|809x809px]]
+
The symbols under the gate convey various information about it:
[[Datei:gg-displays.png|zentriert|811x811px]]
+
{| class="wikitable"
 +
|+
 +
!'''Symbol'''
 +
!'''Description'''
 +
!'''Note'''
 +
|-
 +
|[[Datei:FMCU-Server-Disconnected.png|ohne|link=]]
 +
|No connection to the gate
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Icon-Normal.png|ohne|link=]]
 +
|The gate is in the Normal state
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Icon-Locked.png|ohne|link=]]
 +
|The gate is in the Locked state
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Icon-Firealarm.png|ohne|link=]]
 +
|The gate is in the fire alarm state
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Icon-Emergency.png|ohne|link=]]
 +
|The gate is in the emergency open state
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Icon-Clearance.png|ohne|link=]]
 +
|The cleaning mode is active
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Icon-Alarm.png|ohne|link=]]
 +
|Alarm is active at the gate
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Icon-Service.png|ohne|link=]]
 +
|The gate is permanently open
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Failed-Device.png|ohne|link=]]
 +
|One or more devices at the gate have failed
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Configuration.png|ohne|link=]]
 +
|Current selected configuration of the gate
 +
|Only if there are two or more configurations at the gate
 +
|}
  
 +
<br />
 +
====Gate-View====
 +
<br />
 +
In this view, you can observe the state of each gate, control the gate, and apply the gate's configurations (if there are two or more).
 +
<br />
 +
[[Datei:FMCU_GateView.png|800x800px]]
 +
<br />
  
A subsection is often has a structure with a combo box named '''Type''' at the top and some fields that follow. This structure is used for configuring an entity that can have several implementations. What is important is that the implementation can differ in type and number of controls. For example, a simulator of the gate has only two properties:
 
 
<br />
 
<br />
[[Datei:gg-gate-simulator.png|zentriert|810x810px]]
+
These buttons allow you to perform various actions:
 +
{| class="wikitable"
 +
|+
 +
!'''Symbol'''
 +
!'''Description'''
 +
!'''Note'''
 +
|-
 +
|[[Datei:FMCU Clearance Button.png|rahmenlos|159x159px]]
 +
|Turn cleaning mode on and off
 +
|
 +
|-
 +
|[[Datei:FMCU Emergency Button.png|rahmenlos|172x172px]]
 +
|Manually switch the emergency open state on and off
 +
|
 +
|-
 +
|[[Datei:FMCU Restart Button.png|rahmenlos|81x81px]]
 +
|Restart the gate
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Combo-Configuration.png|ohne|link=]]
 +
|Choose a new configuration of the gate from the combo box
 +
|Only if there are two or more configurations at the gate
 +
|-
 +
|[[Datei:FMCU-Server-Button-Apply.png|ohne|link=]]
 +
|Apply the new configuration
 +
|
 +
|-
 +
|[[Datei:FMCU-Server-Button-Cancel.png|ohne|link=]]
 +
|Do without the new configuration
 +
|
 +
|}
 +
 
 
<br />
 
<br />
  
=== Architecture ===
+
====<big>Set up a new Gate</big>====
The picture below gives a bird's eye view of the configuration management.
+
<br />
 +
Please click the button '''New'''
 +
<br />
 +
[[Datei:FMCU MainPage new.png|800x800px]]
 +
<br />
 +
In this view you create a '''New''' gate. The fields '''Names''', '''Displayed''' '''Name''' and '''Position''' of the Gate must be verified with values. Press Save then click on Facilities.
 
<br />
 
<br />
[[Datei:gg-architecture-configuration-management.png|zentriert|1150x1150px]]
+
[[Datei:FMCU_TestGate_P1.png|800x800px]][[Datei:FMCU_NewGate_PressFacilities.png|800x800px]]
 
<br />
 
<br />
 +
You can now see in the view that you have created a '''NEW''' gate,
  
When the gate starts and the Configuration.json is present it is created from the Initial Configuration (base.py or other .py configuration file).
+
in this case the sixth gate in this view.
The Schema  contains a set of data for describing controls in form components:
+
<br />
 +
[[Datei:FMCU_NewGate_View.png|800x800px]]
 +
<br />
 +
In the next step you connect the gate to the server.
 +
<syntaxhighlight>
 +
https://<IP-Adresse des Dashboards>
 +
</syntaxhighlight>To do this, check on the '''General''' tab that the correct gate name has been entered.
  
* Which controls should contain a component
+
<br />
* Validations rules if any
+
[[Datei:Gate General Configuration.png|800x800px]]
 +
<br />
 +
Then check the following points on the '''Server''' tab.
 +
<br />
 +
[[Datei:Gate Server Configuration.png|800x800px]]
 +
<br />
 +
Server#0 (server)- must be set to remote.
 +
 
 +
Activated slide-switch is activated.
 +
 
 +
Your server should be entered under Name*.
 +
 
 +
Your URL should be entered under URL*.
  
E.g. a form component can contain a text box and an input for integers. The data range for integer should 1-100.
+
Gate should be entered under Username*.
  
The Default Data contains the initial data for controls in form components.
+
Your password should be entered under Password*.
  
Edit this section
+
'''Save''' at the end.
<span name="Roadmap"></span>
 
  
=== Roadmap ===
 
The features are planned for the upcoming release:
 
  
* Configurations page allows you to see the list of available configurations. You can:
+
In the next step, please click on System in the top bar.[[Datei:Gate PressSystem.png|800x800px]]
** Clone an existing configuration to a new one
 
** Delete a configuration
 
** Make a configuration active. Only one configuration can be used by the server and it is called ''active''.
 
* Apply button. This should apply changes on-the-fly.
 
* Restart button. This should restart the docker container and apply settings, which cannot be applied on-the-fly.
 
* Extend the vue form generator library:
 
** Make the switch control consistent with the switch controls on other pages
 
** Add a control which allows you to manage an array of items (e.g. the list of connected gates). E.g. <nowiki>https://codepen.io/safx/pen/AhCtk</nowiki>
 
* Import/Export of a Configuration.json.
 
* Reset any configuration to the default one (by removing the json file
 
  
 +
You will now see the following display, here please press restart once. Now your new gate should be connected.
 
<br />
 
<br />
 +
[[Datei:Gate System Restart.png|800x800px]]
 +
<br />
 +
Finally, you can check the connection in the '''Status''' tab. '''CONNECTED''' must now appear under State.
 +
<br />
 +
[[Datei:Gate Status Check.png|800x800px]]
 +
<br />
 +
====Edit existing Gate====
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/gates
 +
</syntaxhighlight>
 +
You are in the same view as where you would create a new gate.
 +
Please move the slide switch "Grid view" to the left.
 +
<br />
 +
[[Datei:FMCU GridV TestGate.png|800x800px]]
 +
<br />
 +
In the view click on the name of the gate which you want to edit (in the example TestGate_P1).
 +
<br />
 +
[[Datei:FMCU GridView TestGate.png|800x800px]]
 +
<br />
 +
In this view, please press the "Edit" function.
 +
<br />
 +
[[Datei:FMCU Gate View.png|800x800px]]
 +
<br />
 +
You can now edit the gate in this view.
 +
<br />
 +
[[Datei:FMCU Editing Page.png|800x800px]]
 +
<br />
 +
====Remove Gate====
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/gates
 +
</syntaxhighlight>
 +
You are in the same view as where you would create a new gate.
  
== Management of Events ==
+
Please move the slide switch "Grid view" to the left.
The following sections contains the term '''Path''', which means the path is part of the URL. E.g., path '''/events''' for the FMCU Server running under '''<nowiki>https://server.maxcrc.de/</nowiki>''' means
 
<nowiki>https://server.maxcrc.de/events</nowiki>
 
  
== Events ==
+
<br />
Web path:
+
[[Datei:FMCU GridV TestGate.png|800x800px]]
/events
+
<br />
The page shows a filterable and sortable list of events:
+
In the view click on the name of the gate which you want to delete (in the example TestGate_P1).
 +
<br />
 +
[[Datei:FMCU GridView TestGate.png|800x800px]]
 +
<br />
 +
In this view, please press the "Delete" function.
 +
<br />
 +
[[Datei:FMCU Delete Gate.png|800x800px]]
 +
<br />
 +
To be on the safe side, you will now be asked again whether you really want to delete the element? Please confirm this.
 +
<br />
 +
[[Datei:FMCU Delete Gate Accept.png|800x800px]]
 +
<br />
 +
After deleting, you will automatically be shown the next gate (in the example P1_TestGate2). Please click on Facilities here.
 +
<br />
 +
[[Datei:FMCU GoTo Facilities.png|800x800px]]
 +
<br />
 +
You will then see in the Grid View that Gate TestGate_P1 is missing and has been successfully deleted.
 +
<br />
 +
[[Datei:FMCU GridView Deleted Gate.png|800x800px]]
 +
<br />
 +
=Administration=
 +
<br />
 +
==User==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/users
 +
</syntaxhighlight>
 +
On this page you can see an overview of all users
 +
<br />
 +
[[Datei:FMCU Users Tab1.png|800x800px]]
 +
<br />
 +
{| class="wikitable"
 +
!Number
 +
!Function
 +
|-
 +
|1
 +
|Create new user
 +
|-
 +
|2
 +
|Filter users by location
 +
|-
 +
|3
 +
|Filter users by position
 +
|}
 +
<br />
 +
===Set up new User===
 +
<br />
 +
Press under [[#Users| User]] on the button '''New'''
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/new-user
 +
</syntaxhighlight>
 +
<br />
 +
[[Datei:FMCU Create New User.png|800x800px]]
 +
<br />
 
{| class="wikitable"
 
{| class="wikitable"
!Name
+
!Field Name
 
!Description
 
!Description
 
|-
 
|-
|Date
+
|Id
|Date and time when the event occurred
+
|Automatically generated unique number of the user
 
|-
 
|-
|Name
+
|Username*
|Translated name of the event
+
|Username of the user to login
 +
|-
 +
|Password*
 +
|User's password for login
 
|-
 
|-
|Gate
+
|Email
|Gate if appropriate where the event occurred
+
|Email address of the user for sending log messages
 
|-
 
|-
|State
+
|First name
|The state of the event if supported
+
|User's first name
 
|-
 
|-
|Category
+
|Last name
|Category to which the event belongs to
+
|Last name of the user
 
|-
 
|-
 
|Info
 
|Info
|Additional info about the event
+
|Description of the user
 +
|-
 +
|Superuser
 +
|The highest rights are assigned to the user
 +
|-
 +
|Locked
 +
|The user's login is blocked
 +
|-
 +
|Disable notifications
 +
|The user does not receive any notifications in the FMCU Management Dashboard
 
|}
 
|}
Edit this section
+
'''*''' Strictly required fields
 +
Through the button '''Save''' the new user is created.
 +
===Edit existing User===
 +
<br />
 +
Press under [[#Users | User]] a user to edit
 +
<br />
 +
[[Datei:FMCU Edit User.png|800x800px]]
 +
<br />
 +
====Event Notifications====
 +
<br />
 +
Under this tab, the notifications can be selected which the user should receive.<br />'''Note:''' If the checkbox '''Disable notifications''' is set, no notifications are displayed regardless of these settings.
 +
<br />
 +
[[Datei:FMCU Events Notifications.png|800x800px]]
 +
<br />
 +
====Locations & Positions Tab====
 +
<br />
 +
You can set different locations in countries and cities. Separate access rights can be defined for each location via the authorization model.
 +
<br />
 +
[[Datei:FMCU Locations Positions.png|800x800px]]
 +
<br />
 +
====Groups Tab====
 +
<br />
 +
This tab allows you to customize the user's group memberships.
 +
<br />
 +
[[Datei:FMCU Groups Tab.png|800x800px]]
 +
<br />
 +
====Permissions Tab====
 +
<br />
 +
The user's permissions are displayed under this tab
 +
<br />
 +
[[Datei:FMCU Groups User Permissions.png|800x800px]]
 +
<br />
 +
All changes are applied by clicking the '''Save''' button.
 +
 
 +
<br />
 +
==Groups==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/groups
 +
</syntaxhighlight>
 +
On this page you can see an overview of all groups
 +
<br />
 +
[[Datei:FMCU_Groups_Tab.png|rahmenlos|1133x1133px]]
 +
<br />
 +
===Set up new Group===
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/new-group
 +
</syntaxhighlight>
 +
Click under [[#Gruppen | Gruppen]] the button '''New'''
 +
<br />
 +
[[Datei:Bildschirmfoto 2022-02-24 um 11.03.34.png|800x800px]]
 +
<br />
 +
please enter a group name, optional you can write a description to the group
  
== Event Definitions Page ==
+
<br />
Path:
+
[[Datei:FMCU New Group.png|800x800px]]
/event-definitions
+
<br />
The page shows a list of definitions of events:
 
 
{| class="wikitable"
 
{| class="wikitable"
!Name
+
!Field Name
 
!Description
 
!Description
 +
|-
 +
|Id
 +
|Automatically generated unique number of the group
 
|-
 
|-
 
|Name
 
|Name
|Name
+
|Name of the Group
 +
|-
 +
|Info
 +
|Description of the Group
 +
|}
 +
'''*''' Strictly required fields
 +
<br />
 +
 
 +
The new group is created by clicking the '''Save''' button.
 +
 
 +
<br />
 +
 
 +
===Edit existing Group===
 +
<br />
 +
Click under [[#Gruppen | Gruppen]] the Group you want edit
 +
<br />
 +
[[Datei:FMCU_Groups_Tab.png|rahmenlos|1133x1133px]]
 +
<br />
 +
====Users Tab====
 +
<br />
 +
This tab allows you to customize the members of the group.
 +
<br />
 +
[[Datei:FMCU Groups userstab.png|800x800px]]<br />
 +
<br />
 +
====Permissions Tab====
 +
<br />
 +
The permissions that are inherited by the members of the group are displayed under this tab.
 +
<br />
 +
All changes are applied by clicking the '''Save''' button.
 +
<br />
 +
[[Datei:FMCU Permissions user edit.png|800x800px]]
 +
<br />
 +
==Positions==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/cities
 +
</syntaxhighlight>
 +
On this page you can see an overview of all positions
 +
<br />
 +
[[Datei:FMCU Administration Positions.png|800x800px]]
 +
<br />
 +
===Set up new Position===
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/new-city
 +
</syntaxhighlight>
 +
Under [[#Positions | Positions]] click on the button '''New'''
 +
 
 +
Enter the name of the position and assign the position to a location using the dropdown field.
 +
<br />
 +
[[Datei:FMCU Create New Position.png|800x800px]]
 +
<br />
 +
Click on the '''Save''' button to create the position
 +
 
 +
<br />
 +
===Edit existing Position===
 +
<br />
 +
Under [[#Positions| Positions]] click to edit the position
 +
<br />
 +
[[Datei:FMCU Edit Position.png|800x800px]]
 +
<br />
 +
Here you can edit the position name and location
 +
<br />
 +
[[Datei:FMCU Position Edit Interface.png|800x800px]]<br />
 +
<br />
 +
==Locations==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/countries
 +
</syntaxhighlight>
 +
On this page you can see an overview of all locations
 +
<br />
 +
[[Datei:FMCU Locations View.png|800x800px]]
 +
<br />
 +
===Set up new Location===
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/new-country
 +
</syntaxhighlight>
 +
Press under [[#Locations | Locations]] the button '''New'''
 +
<br />
 +
[[Datei:FMCU Create New Location.png|800x800px]]
 +
<br />
 +
[[Datei:FMCU Create NewLocation.png|800x800px]]
 +
<br />
 +
{| class="wikitable"
 +
!Field Name
 +
!Description
 
|-
 
|-
|Event Definition Groups
+
|Id
|Groups to which the event belongs to if any
+
|Automatically generated unique number of the location
 
|-
 
|-
|Supported States
+
|Name*
|Can be empty (for impulse events) or '''On, Off''' (for the events with states)
+
|Location name
 
|-
 
|-
|Category
+
|Info
|Category to which the event belongs to
+
|Description of the location
 
|}
 
|}
Edit this section
+
'''*''' Strictly required fields
 +
 
 +
<br />
 +
Click on the '''Save''' button to create the position
 +
 
 +
===Edit existing Location===
 +
<br />
 +
Under [[#Location| Location]] , click the location you want to edit
 +
<br />
 +
[[Datei:FMCU EditExisting Location.png|800x800px]]
 +
<br />
 +
Here you can edit the name, code and info of the location
 +
<br />
 +
[[Datei:FMCU Editing Location.png|800x800px]]
 +
<br />
 +
==Locations & Positions==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/locations
 +
</syntaxhighlight>
 +
Here you can see an overview of all positions and their assigned locations
 +
<br />
 +
[[Datei:FMCU Locations Positions.png|800x800px]]
 +
<br />
 +
==Configuration==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/configurations
 +
</syntaxhighlight>
 +
<br />
 +
[[Datei:FMCU Administration Configuration.png|800x800px]]
 +
<br />
  
== Event Definition Groups ==
+
=Events=
Path:
+
<br />
/event-definition-groups
+
==Events==
The page shows a list of event groups:
+
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/events
 +
</syntaxhighlight>
 +
In this view, the events of all access controls are shown in an intuitive list view. There are filtering options and a name search for the events.
 +
<br />
 +
[[Datei:FMCU Events9.png|800x800px]]
 +
<br />
 +
The following filters can be set:
 +
 
 +
#Location
 +
#Position
 +
#Facility
 +
#Search by Event name
 +
#Time Period
 +
 
 +
==Event Definitions==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/event-definitions
 +
</syntaxhighlight>
 +
In this view, all events that the FMCU contains are listed and their event definition groups, supported states and categories are assigned.
 +
<br />
 +
[[Datei:FMCU Event Definitions.png|800x800px]]
 +
<br />
 +
==Event definition Groups==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/event-definition-groups
 +
</syntaxhighlight>
 +
All event definition groups are listed under this tab.
 +
<br />
 +
[[Datei:FMCU Event definition groups.png|800x800px]]
 +
<br />
 +
===Create a new Event definition Group===
 +
<br />
 +
Click [[#Event defenition groups|Event defenition groups]] on the Button '''New'''
 +
<br />
 +
[[Datei:FMCU PressNew Eventdg.png|800x800px]]
 +
<br />
 +
[[Datei:FMCU_Create_New_definition_Group.png|800x800px]]
 +
<br />
 
{| class="wikitable"
 
{| class="wikitable"
!Name
+
!Fieldname
 
!Description
 
!Description
 +
|-
 +
|ID
 +
|Automatically generated unique group number
 
|-
 
|-
 
|Name
 
|Name
|Name
+
|Name of the group
 
|-
 
|-
|Events
+
|Info
|Event definitions assigned to the group
+
|Group description
|-
 
|Delete
 
|Delete button
 
 
|}
 
|}
An event definition group allows you to group one or more events so that it can be bound to a user group. See '''Event Subscriptions''' below
+
'''*''' Absolutely required fields
  
Edit this section
+
Under the '''Event defenition''' tab select the event definitions that are to be assigned to the group.
  
== Event Subscriptions ==
+
<br />
Web path:
+
 
/event-subscriptions
+
==Event Subscriptions==
The page shows a list of event definition groups bound to a user groups.
+
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/event-subscriptions
 +
</syntaxhighlight>
 +
There is the possibility to link groups of alarm messages with groups of users. As a result, only group members are notified of alarm messages that are also grouped,
 +
<br />
 +
[[Datei:FMCU Event Subscriptions.png|800x800px]]
 +
<br />
 
{| class="wikitable"
 
{| class="wikitable"
!Name
+
|+
 +
!Fieldname
 
!Description
 
!Description
 +
|-
 +
|ID
 +
|internal value
 
|-
 
|-
 
|Group
 
|Group
|User group
+
|Summary of users
 
|-
 
|-
|Event definition group
+
|Ereignisdefinitionsgruppe
 
|Event definition group
 
|Event definition group
 
|-
 
|-
 
|Locked
 
|Locked
|When locked, events are not sent to the users of the group
+
|Notifications deactivated/activated
 
|-
 
|-
 
|Info
 
|Info
|Any informative text
+
|Description field
 +
|}
 +
 
 +
==Notifications==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/notifications
 +
</syntaxhighlight>
 +
Sent notifications are displayed in this overview. You can adjust the view accordingly using a date filter.
 +
<br />
 +
[[Datei:Notifications FMCU.png|800x800px]]
 +
<br />
 +
=Cards=
 +
<br />
 +
==Cards==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/cards
 +
</syntaxhighlight>
 +
This view shows an overview of the RFID cards in the system with the gates enabled for access.
 +
<br />
 +
[[Datei:FMCU Cards Page.png|800x800px]]
 +
<br />
 +
==Edit Cards==
 +
<br />
 +
<syntaxhighlight>
 +
https://<dns-name or ip-address>/cards-edit
 +
</syntaxhighlight>
 +
In this view, cards can be added / removed and authorizations for individual gates can be defined.
 +
<br />
 +
[[Datei:FMCU Edi Cards1.png|800x800px]]
 +
<br />
 +
After you push the Add Button you will be shown the following window
 +
<br />
 +
[[Datei:FMCU Add New Card.png|800x800px]]
 +
<br />
 +
{| class="wikitable"
 +
|+
 +
!Field
 +
!Description
 +
|-
 +
|Barcode
 +
|Card content that is captured by the reader
 +
|-
 +
|Employee
 +
|Description field
 +
|-
 +
|Employee ID
 +
|Description field
 +
|-
 +
|Quantity
 +
|Number of accesses for this card
 +
|}
 +
 
 +
=Statistics=
 +
<br />
 +
In this view, all activities for the assigned access controls are shown. You can adjust the view with date filters. It is possible to group the screen output, e.g. only to evaluate the number per day or month. Finally, the data can be exported in Excel format or CSV-format.
 +
<br />
 +
[[Datei:FMCU Main Statistics.png|800x800px]]
 +
<br />
 +
 
 +
<br />
 +
 
 +
{{DEFAULTSORT:FMCU Galaxy Gate ~ Management Dashboard}}
 +
 
 +
<br /><span name="Roadmap"></span>
 +
[[Kategorie:Galaxy Gate EN]]
 +
 
 +
=Additional Topics=
 +
<br />
 +
 
 +
==Authorization==
 +
 
 +
 
 +
Access to certain resources provided by the application, e.g. facilities, actions, user interface elements, can be limited or unlimited. Access is unlimited if the user is a superuser. Any superuser can set or remove the '''Superuser''' property for any other user. Access for non-superuser users can be restricted by their groups ('''group-level permissions''') and/or locations ('''location-level permissions''').
 +
 
 +
 
 +
===Group-Level Authorization===
 +
 
 +
Group-level authorization is implemented through group permissions, which are a set of boolean values (true/false) that allow/deny group users access to various resources. The permissions are divided into categories and subcategories for easier navigation.
 +
 
 +
<br/>
 +
 
 +
[[Datei:FMCU-Server-Group-Permissions.png]]
 +
 
 +
<br/>
 +
 
 +
The image shows the permissions for the '''Manager''' group. If a checkbox is set, the resource is allowed for the users, otherwise it is denied.
 +
 
 +
<br/>
 +
 
 +
Here are some examples of permissions:
 +
 
 +
<br/>
 +
 
 +
* '''Actions / Facility / Mode / ServiceEntry'''. If the action '''ServiceEntry''' is set, the users of this group can open the gate in the entry direction, otherwise they cannot.
 +
 
 +
<br/>
 +
 
 +
[[Datei:FMCU-Server-Group-Permissions-ServiceEntry.png]]
 +
 
 +
<br/>
 +
 
 +
* '''Tables / audit / Read'''. The '''Administration | Audit''' page displays data from the '''audit''' database table. By default, access to the '''audit''' table is denied to all groups. This means that the data on the '''Administration | Audit''' page is only displayed to superusers.
 +
 
 +
<br/>
 +
 
 +
[[Datei:FMCU-Server-Group-Permissions-Audti-Read.png]]
 +
 
 +
<br/>
 +
 
 +
 
 +
* '''Views | Menu | Administration | Groups'''. If the '''Groups''' checkbox is set, the menu item is shown to the users, otherwise it is hidden.
 +
 
 +
<br/>
 +
 
 +
[[Datei:FMCU-Server-Group-Permissions-View-Groups.png]]
 +
 
 +
<br/>
 +
 
 +
The permissions are divided into the following top categories:
 +
 
 +
{| class="wikitable"
 +
|+
 +
!Category
 +
!Description
 +
!Example
 
|-
 
|-
|Delete
+
|Actions
|Delete button
+
|Actions, the user can execute from the dashboard
 +
| '''ServiceEntry''', allow/deny users to permanently open facilities in entry direction
 +
|-
 +
|Tables
 +
|Create, read, update and delete records in database tables
 +
| Allow/deny users to access the '''audit''' table
 +
|-
 +
|Views
 +
|Show/hide user interface elements
 +
|Show/hide the '''Administration / Groups''' menu
 
|}
 
|}
When a event definition group is bound to a user group and not locked, new events from the event definition group are sent to the users from the user group. The user must have a valid email address.
 
  
Example. A user group '''Alarm events''' with two members '''user1''' and '''user2''' is bound to an event definition group '''Alarm events''' with two events '''GateTailgating''' and '''GateStateFireAlarm'''. When either or both of these events occur, both users '''user1''' and '''user2''' receive an email notification about that.
 
  
Edit this section
 
  
== Configuration ==
+
 
Path:
+
{{ Box_Note | Note Text = If the user belongs to more than one group and access to a resource is allowed in one of the groups, the user can access the resource }}
/configuration
+
 
In order the emails with events can be sent out, the '''Email''' section with the information like the hostname, port etc. of the outgoing server and credentials should be properly configured.
+
<br />
 +
 
 +
{{ Box_Note | Note Text = The configuration of items in the ''Views'' category should be consistent with items in the ''Tables'' category. For example, if a menu for a page is configured to be displayed, but the database table whose data is displayed on the page is configured to be denied, the data will not be displayed }}
 +
 
 +
 
 +
===Location-Level Authorization===
 +
 
 +
Location-level authorization means that some location-aware resources, such as facilities, groups, and users, can be assigned to one or more ''locations'' and/or ''positions,'' so that the user can access only those resources that have the same locations.
 +
 
 +
For example, there are two locations: '''Standort1''' with positions '''P1''' and '''P2''' and '''Standort2''' with positions '''P3''' and '''P4''':
 +
 
 +
 
 +
[[Datei:FMCU-Server-Locations1.png]]
 +
 
 +
In the above picture, '''All positions''' means '''P1''' and '''P2''' for '''Standort1''' and '''P3''' and '''P4''' for '''Standort2'''.
 +
 
 +
If we take the user '''manager''' and select locations and positions like in the picture below
 +
 
 +
<br/>
 +
 
 +
[[Datei:FMCU-Server-Locations2.png]]
 +
 
 +
<br/>
 +
 
 +
then the user '''manager''' will have access to other location-aware resources (users, groups and facilities) as follows:
 +
 
 +
 
 +
{| class="wikitable"
 +
|+
 +
!Position
 +
!Access allowed
 +
|-
 +
|P1
 +
|Yes
 +
|-
 +
|P2
 +
|Yes
 +
|-
 +
|P3
 +
|Yes
 +
|-
 +
|P4
 +
|No
 +
|}
 +
 
 
<br />
 
<br />

Anhänge

Diskussionen