Skip to content

General Options

How to use the general options?

Password Options

The password requirements can be used to ensure that all users of the system comply to the same set of rules to increase security.

Password options

Minimum length

The users password must be equally long or longer than the specified minimum length. Use the checkbox or set it to 0 to disable the check of the password length.

Maximum length

The maximum length can be used to restrict the chosen password length to the specified number. In general this should not be used, except the password has to be used in a different system as well for some reason.

Number of contained features

  • Unchecked means disabled, all password features below have to be present independently.
  • If greater than 0: The sum of present password features must be equal or larger than this number.

Example: Value set to 2, all password features are checked. The password "smartgrid676" contains lower case letters and numbers and therefore contains two features and is compliant. The password "0978238" contains only numbers and therefore only one feature and doesn't match the rule.

Password features

Activated password features must be contained in the password.

  • Lower case
    The password must contain lower case letters out of a,b,c,...,x,y,z

  • Upper case
    The password must contain upper case letters out of A,B,C,...,X,Y,Z

  • Numbers
    The password must contain digits out of 0,1,2,3,4,5,6,7,8,9

  • Special characters
    The password must contain letters out of the characters specified in the text field.


Password expiration

Number of stored passwords

Use this to adjust the length of the password history. Passwords are stored in an encrypted form in the database. The old passwords will be kept, and the user is not allowed to change his password to any password that is found in the password history.
E.g. the number of stored passwords is set to 3. The user had chosen "abc123", "abc234", "abc345" in the past. His next password cannot be any of those. He uses "abc456". His next password now can be "abc123" again, because his password history contains now "abc234", "abc345", "abc456".

Expiration time of passwords in days

After the specified number of days, the user has to define a new password that complies to the password requirements. If unchecked the passwords will never expire. The password history has to contain at least one element when enabling an expiration time.

Failed logins until lock out

Specify the number of failed logins that will lead to a lock out of the user. This means he will not be able to login again, until his account has been unlocked by the administrator or he uses the password reset functionality to set a new password.

If the number of failed logins is not 0, but the user manages to log in again, he will be displayed a warning before he can proceed to use the software. The failed logins will be reset in that case.


ADFS via SAML2

Setting up ADFS for SSO

You can use ADFS to ease the login process for your users and to centralize your account management. Each user that is granted authentication by the ADFS server still needs an Adaptricity user profile with a matching email address.

In SAML terminology Adaptricity acts as the service provider. Your ADFS server acts as an identity provider. You can only specify one identity provider for one entire Adaptricity instance.

The Service Provider Entity ID is used to identify the adaptricity software on your ADFS server. Your ADFS server is described by the Identity Provider Description SAML2 XML document.
Please note: In case you can save the changes only basic checks are carried out, such as XML validation and construction of a test client. But no actual test request is performed. You need to logout and login via the ADFS button to see if the configuration is valid.

Note, that in general you can use any SAML2 identity provider not only ADFS.


Password Guessing Attack Prevention

The password guessing attack prevention temporarily blocks IP addresses from accessing Adaptricity.Mon after the specified number of failed log-in attempts.
If enabled, you can set the number of failed log-ins after the IP address will be blocked and the duration for how long (in minutes) the block will remain.

Map Layer Configuration

In addition to the map layer provided by Adaptricity you can define your own map layers.
If there are additional maps defined, the layers can be selected in the bottom right corner on the map using the map layer selector.

Map Layer Configuration

Map Layer Types

In the map layer configuration you can define two types:

  • Base Maps: These replace the default map layer in the background.
  • Overlay Maps: These can be additionally displayed on top of the selected base map.

Layer Properties

Each layer has the following properties:

  • Name by which it can be selected in the map layer selector.
  • Coordinate reference system (CRS) that the map layer uses.
  • Tile type: The type of the layer. Can be WMS or xyz.
  • Options: Key-value properties that the layer requires can be added here.
    Use the key opacity to set the opacity of the layer (choose a value between 0 and 1, with 1 showing the layer with full opacity, a lower value denoting less opacity).

Examples

WMS:

  • CRS: epsg3857
  • Type: WMS
  • URL: http://ows.mundialis.de/services/service?
  • Options: "layers": "TOPO-OSM-WMS"

xyz:

  • CRS: epsg3857
  • Type: xyz
  • URL: http://{s}.tile.osm.org/{z}/{x}/{y}.png
  • Options: none

Please note that you are responsible for appropriate licensing of the used layers.

API Options

This option allows you to select the target project that will be used when making calls to the Connection Request API.

API options

Line Owners

Each branch in the grid model can be assigned an owner. The selectable owners can be configured here.

Line owners

For each owner, you can specify whether the associated branches are to be ignored when evaluating connection requests. These branches are referred to as "ignored" in the following.

Behavior of Ignored Branches

Ignored branches are handled differently:

  • In Hosting capacity / Adaptricity.Connect:
    A bus is ignored when calculating the hosting capacity if it is connected exclusively to ignored branches.
    As a result, these buses are not available as possible connection points in Adaptricity.Connect.
    If the Hosting capacity on lines option has been selected, hosting capacities are not calculated either on ignored lines.

  • In the custom-defined connection request:
    During the automatic selection of potential connection buses, the buses connected exclusively to ignored branches are ignored.

Owner Name Management

Customer names should be changed with care.
When changing a name here, the respective names in the grid models will not be adjusted.
Thus, the branches will have an invalid owner attribute and will be handled as branches without an owner.

Miscellaneous

This section allows you to configure general system preferences:

  • Default Currency: Choose the currency symbol to be used across the platform (e.g., €).
  • Default Language: Set the default language for the user interface.
  • External GIS System: Specify an external GIS system (e.g., Smallworld).
    When selected, it can be accessed via the GIS button in the grid viewer.
  • EPSG: Define the EPSG code for spatial reference (e.g., 25832).

These settings can be customized to match your organization's standards and integration needs.

Miscellaneous

Grid Viewer

Branch Style

Change the default style of how branches are drawn in the grid.

Voltage Levels

Customize the coloring of voltage levels within certain voltage ranges. This setting is used in the map view when coloring the grid by voltage level. Voltage levels

Legend Settings

Configure the settings of various legends such as "Loading [%]" or "Voltage [pu]" to be used across all users and static calculation pages. Legend settings