Gate ~ FMCU Galaxy Gate ~ management dashboard

De.png En-active.png



General

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.


Headline

Gate ~ FMCU ~ management dashboard Headline.png
Number Function
1 Button Management Dashboard
2 Administration
3 Events Button
4 Cards Button
5 Statistics Button
6 Logged in User
7 Log out Button
8 Languages menu
9 Adjust the display to entire width of the screen

Menu items

Gates

https://<dns-name or ip-address>/gates

In this view, all access controls are shown in an intuitive interface. There are grouping options in two categories. First of all, you can group by location. You can then combine different positions within the location. Individual gates can be added using the "New" menu item.

FMCU1.png

Set up a new Gate

In this view you create a new gate. The fields names, displayed name and Position of the Gate must be verified with values. Then click on Attachments.

FMCU3.png

You can now see in the view that you have created a NEW gate, in this case the fourth gate in this view.

FMCU4.png


In the next step you connect the gate to the server.

https://<IP-Adresse des Dashboards>

To do this, check on the General tab that the correct gate name has been entered.

FMCU5.png

Then check the following points on the Server tab.

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*.

Gate should be entered under Username*.

Your password should be entered under Password*.

Save at the end.

FMCU7.png


In the next step, please click on System in the top bar.

FMCU9.png


You will now see the following display, here please press restart once. Now your new gate should be connected.

FMCU10.png


Finally, you can check the connection in the Status tab. CONNECTED must now appear under State.

FMCU11.png


Edit existing Gate

https://<dns-name or ip-address>/gates

You are in the same view as where you would create a new gate.

Please move the slide switch "Grid view" to the left.

FMCU12.png


In the view click on the name of the gate which you want to edit (in the example P1_TestGate2).

FMCU18.png

In this view, please press the "Edit" function.

FMCU19.png

You can now edit the gate in this view.

FMCU20.png

Remove Gate

https://<dns-name or ip-address>/gates

You are in the same view as where you would create a new gate.

Please move the slide switch "Grid view" to the left.

FMCU12.png

In the view click on the name of the gate which you want to delete (in the example P1_TestGate6).

FMCU13.png

In this view, please press the "Delete" function.

FMCU14.png

To be on the safe side, you will now be asked again whether you really want to delete the element? Please confirm this.

FMCU15.png

After deleting, you will automatically be shown the next gate (here in the example P1_TestGate2). Please click on attachments here.

FMCU16.png

You will then see in the grid view that Gate P1_TestGate6 is missing and has been successfully deleted.

FMCU17.png


Administration

User

https://<dns-name or ip-address>/users

Auf dieser Seite sehen Sie eine Übersicht aller Benutzer Gate ~ FMCU ~ management dashboard Users.png

Nummer Funktion
1 Neuen Benutzer anlegen
2 Benutzer nach Standort filtern
3 Benutzer nach Postition filtern


Set up new User

Klicken Sie unter Benutzer auf den Button Neu

https://<dns-name or ip-address>/new-user

Gate ~ FMCU ~ management dashboard new Users.png

Feldname Beschreibung
Id Automatisch generierte eindeutige Nummer des Benutzers
Benutzername* Benutzername des Benutzers für die Anmeldung
Passwort* Passwort des Benutzers für die Anmeldung
Email Email Adresse des Benutzers zum Versand von Log Nachrichten
Vorname Vorname des Benutzers
Nachname Nachname des Benutzers
Info Beschreibung des Benutzers
Superuser Die höchsten Rechte werden dem Benutzer vergeben
Locked Die Anmeldung des Benutzers ist gesperrt
Meldungen deaktivieren Der Benutzer erhält keine Benachritgungen im FMCU Management Dashboard

* Unbedingt erforderliche Felder Durch den Button Speichern wird der neue Benutzer angelegt.

Edit existing user

Klicken Sie unter Benutzer auf den zu bearbeitenden Benutzer

Event notifications

Unter diesem Reiter können die Benachrichtigungen ausgewählt werden welcher der Benutzer erhalten soll.
Hinweis: Ist die Checkbox Meldungen deaktivieren gesetzt werden unabhängig von diesen Einstellungen keine Benachrichtigungen angezeigt.

Locations & Positions tab

Man kann unterschiedliche Standorte in Länder und Städte festlegen. Über das Berechtigungsmodell lassen sich separate Zugriffsrechte für jeden Standort definieren.

Groups tab

Unter diesem Reiter können Sie die Gruppenmitgliedschaften des Benutzers anpassen.

Permissions tab

Unter diesem Reiter werden die Berechtigungen des Benutzers angezeigt
Durch den Button Speichern werden alle Änderungen angewendet.




Groups

https://<dns-name or ip-address>/groups

Auf dieser Seite sehen Sie eine Übersicht aller GruppenGate ~ FMCU ~ management dashboard groups.png

Set up new group

https://<dns-name or ip-address>/new-group

Klicken Sie unter Gruppen auf den Button NeuGate ~ FMCU ~ management dashboard new groups.png

Feldname Beschreibung
Id Automatisch generierte eindeutige Nummer der Gruppe
Name Name der Gruppe
Info Beschreibung der Gruppe

* Unbedingt erforderliche Felder

Durch den Button Speichern wird die neue Gruppe angelegt.


Edit existing group

Klicken Sie unter Gruppen auf die zu bearbeitende Gruppe

Users tab

Unter diesem Reiter können Sie die Mitglieder der Gruppe anpassen.

Permissions tab

Unter diesem Reiter werden die Berechtigungen angezeigt welche den Mitgliedern der Gruppe vererbt werden.
Durch den Button Speichern werden alle Änderungen angewendet.


Positions


Set up new Position


Edit existing Position


Locations


Set up new Location


Edit existing Location


Locations & Positions

Configuration

Connectivity Board


Contact Type Impulse Description
A8 Output Yes (500 ms) Person has entered
A9 Output Yes (500 ms) Alarms*
E3 Input Yes (500 ms) Open Entry
E4 Input Yes (500 ms) Open Exit
E6 Input Yes (200ms) Card is valid, open the gate
E7 Input Yes (200ms) Card is invalid, do not open the gate  
E8 Input No Emergency State button**
E9 Input Yes (500 ms) Open Entry 70%
E10 Input No Fire Alarm

*A9 Alarms:

  • 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).
  • Tailgating or other unwanted actions.
  • Entry barcode scanner is broken or it is a stub.
  • Gate in in the Fire Alarm or Emergency state. The alarm is produces as a repetitive pulse signal (700ms).
  • Gate is open only for exit.

After the Emergency State button pressed, the gate switches to the Emergency State. Then only exit from this state is to restart the gate.

The signal can be set/received to/from a contact from any of the halves of the gate.

Configuration Management


User Interface

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:

http://192.168.1.221/configuration
configuration page


There are two buttons on the page:

Name Description Action
Save Saves the modified configuration to the server Post
Reset Discards any changes by reloading the configuration from the server 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:

gg-general.png
gg-barcode-reader-gate.png


gg-audio-player-camera.png


gg-tracking-camera.png
gg-displays.png


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:

gg-gate-simulator.png


Architecture

The picture below gives a bird's eye view of the configuration management.

gg-architecture-configuration-management.png


When the gate starts and the Configuration.json is present it is created from the Initial Configuration (base.py or other .py configuration file). The Schema contains a set of data for describing controls in form components:

  • Which controls should contain a component
  • Validations rules if any

E.g. a form component can contain a text box and an input for integers. The data range for integer should 1-100.

The Default Data contains the initial data for controls in form components.

Edit this section

Roadmap

The features are planned for the upcoming release:

  • Configurations page allows you to see the list of available configurations. You can:
    • 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. https://codepen.io/safx/pen/AhCtk
  • Import/Export of a Configuration.json.
  • Reset any configuration to the default one (by removing the json file


Management of Events

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 https://server.maxcrc.de/ means

https://server.maxcrc.de/events

Events

Web path:

/events

The page shows a filterable and sortable list of events:

Name Description
Date Date and time when the event occurred
Name Translated name of the event
Gate Gate if appropriate where the event occurred
State The state of the event if supported
Category Category to which the event belongs to
Info Additional info about the event

Edit this section

Event Definitions Page

Path:

/event-definitions

The page shows a list of definitions of events:

Name Description
Name Name
Event Definition Groups Groups to which the event belongs to if any
Supported States Can be empty (for impulse events) or On, Off (for the events with states)
Category Category to which the event belongs to

Edit this section

Event Definition Groups

Path:

/event-definition-groups

The page shows a list of event groups:

Name Description
Name Name
Events Event definitions assigned to the group
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

Edit this section

Event Subscriptions

Web path:

/event-subscriptions

The page shows a list of event definition groups bound to a user groups.

Name Description
Group User group
Event definition group Event definition group
Locked When locked, events are not sent to the users of the group
Info Any informative text
Delete Delete button

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:

/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.

Anhänge

Diskussionen