Note: Please note that this user manual may not always reflect the current state of the software version. With software updates, it may happen that the present description is no longer accurate in some points. In this case, please contact us directly or use the current version of the user manual, which you can find on our website www.a-eberle.de.

Publisher:

A. Eberle GmbH & Co. KG Frankenstraße 160
D-90461 Nuremberg

Phone: +49 911 62 81 08 0
Fax: +49 911 62 81 08 99
Email: info@a-eberle.de
Internet: www.a-eberle.de

The company A. Eberle GmbH & Co. KG assumes no liability for damages or losses of any kind resulting from printing errors or changes in this user manual.

Likewise, the company A. Eberle GmbH & Co. KG assumes no liability for damages and losses of any kind resulting from the use of the software or from devices modified by the user through the software.

Copyright 2025 A. Eberle GmbH & Co. KG. All rights reserved.

1. User Guidance

The user manual summarizes all important information for installation and operation. Read the user manual completely and only use the product once you have understood the user manual.

1.1. Target Audience

This user manual is intended for trained professionals as well as trained and certified operating personnel. The content of this user manual must be made accessible to the persons responsible for the installation and operation of the system.

1.2. Warnings

• Structure of the warnings

Warnings are structured as follows:

	Type and source of danger!
	Consequences of non-compliance.
Signal word	Measure to avoid the danger.

• Grading of the warnings

Warnings differ according to the type of danger as follows:

	Warns of an imminent danger that will result in death or serious injury if not avoided.
Danger

	Warns of a potentially dangerous situation that will result in moderate or minor injury if not avoided.
Warning

	Warns of an imminent danger that will result in death or serious injury if not avoided.
Caution

	Warns of a potentially dangerous situation that will result in property or environmental damage if not avoided.
Note

1.3. Tips

	Tips for proper handling of the software and recommendations.
Note

1.4. Other Symbols

• Instructions

  Structure of the instructions:

  Instruction for an action.

  Result indication if necessary.

• Lists

Structure of bulleted lists:

• Level 1

  • Level 2

Structure of numbered lists:

1. Level 1

2. Level 1

   1. Level 2

   2. Level 2

1.5. Applicable Documents

For the safe and correct use of the software, also observe the additionally supplied documents as well as relevant standards and laws.

1.6. Storage

Keep the user manual, including the applicable documents, readily available near the system.

2. Scope of Delivery, Order Features, and System Requirements

2.1. Scope of Delivery

• Installation file

• License agreements

• License file (JSON file)

2.2. Order Features

WebPQ® database software including PostgreSQL database for fully automated processing and evaluation of power quality data in your IT environment! Basic versions always include 3 units – unlimited expansion possible via add-ons.

2.2.1. Functionality

• Automated reading of measurement data from PQI-LV / PQI-DA smart and PQI-DE devices via SSH and CCCI interface

• Web server for visualizing measurement data and disturbance records in level-time diagrams / histograms / bar charts / vector diagrams / ITIC / and more

• Responsive live data display from one or more devices simultaneously

• Automated alarm management in case of disturbances

• Automated reports according to EN50160 and IEC61000-2-2 / IEC61000-2-4 / IEC61000-2-12, switchable to up to 65 standard templates

• Parameterization and management of measuring devices via the web server

• IT security through a comprehensive user rights management system with audit logging, password policies, and more

• Visualization of measurement data from PQI-D and PQI-DA devices

• Integration of WinPQ into WebPQ® to support PQI-Ds

• CSV and Comtrade export functionality

2.2.2. Licenses

WebPQ Initial Order - Number of Units

Available WebPQ Add-ons

Additional Units

Maintenance Agreements

2.3. System Requirements

**Note:** The following pages contain the system requirements for the WebPQ software. Please note that these requirements may not always reflect the current state of the software version. With software updates, it may happen that the present description is no longer accurate in some points. In this case, please contact us directly or use the current version of the system requirements, which you can find on our website [www.a-eberle.de](http://www.a-eberle.de).

Publisher:
A. Eberle GmbH & Co. KG Frankenstraße 160 D-90461 Nuremberg

2.3.1. Supported Operating Systems & Browsers

• Windows 10 64-bit

• Windows 11

• Windows Server 2016

• Windows Server 2019

• Windows Server 2022

• Windows Server 2025

• WebPQ: Chrome, Firefox, Microsoft Edge, Safari

2.3.2. Supported Database Systems

• PostgreSQL 14.*

• MS-SQL (ab Version 2022)**

*PostgreSQL is supported from WinPQ > 6.2. **Individual order process and license key are necessary! Consultation required.

2.3.2.1. Special Database Settings

2.3.2.1.1. Database Settings / Special Considerations for Microsoft SQL

If WebPQ is to be operated with MS-SQL, the MS-SQL server must be configured to support Mixed-Mode Authentication. This is necessary so that WebPQ can access the database. Alternatively, a Windows user with appropriate permissions can be used for database access. This user must then be stored as a user in the WebPQ service.

2.3.3. Minimum System Requirements

• CPU: 4 cores

• RAM: 8 GB memory

• Storage: two partitions - 20 GB for WebPQ installation and an additional 1 GB per year per connected measuring device (using standard profiles)

• Network: Ethernet adapter for communication with TCP/IP PQ devices

• Display: Remote desktop connection or monitor with at least 1280 x 1024 pixel resolution

• Browser: Chrome, Firefox, Microsoft Edge, Safari

• SMTP Mail Server: acces to a mailserver from the application for alerting, notifications, and user management

2.3.4. Recommended System Configuration

• Hardware: Server designed for 24/7 operation / Virtual server system (more cost-effective!)

• CPU: CPU with 6 or more cores

• RAM: 8 GB or more memory

• Storage: two partitions - 20 GB for WebPQ installation and an additional 1 GB per year per connected measuring device (using standard profiles) with redundancy and automatic backup

• Disk: Solid-state disk for the database on a second partition

• Network: Ethernet adapter with high data throughput for communication with TCP/IP devices

• Display: Remote desktop connection or monitor with high resolution (e.g., 1920 x 1200 pixels)

• Browser: Chrome, Firefox, Microsoft Edge, Safari

• SMTP Mail Server: acces to a mailserver from the application for alerting, notifications, and user management

2.3.5. Operation in a Terminal Server Environment

Running WebPQ in a terminal server environment is technically possible, but generally not required, as WebPQ is provided as a web application via an integrated web server. Installation is performed directly on the terminal server; the configuration directory is stored by default in the system folder %programdata%.

Administration Notes:

• Initial configuration and administrative adjustments of the WebPQ backend application should only be performed by a user with local administrator rights via remote desktop connection. This ensures that configuration changes are made consistently and securely.

• Access rights to the configuration directory should be assigned restrictively to prevent unauthorized changes by other users.

User Access Model:

• Use of WebPQ (user management, device management, data analysis, and other functions) is exclusively via a web browser. Users do not require direct access to the terminal server or backend application, but connect to the WebPQ web interface over the network.

• The terminal server environment does not affect operation of the web interface. Users can access WebPQ from any supported device (PCs, notebooks, thin clients) with a compatible browser.

• Simultaneous access by multiple users to the web interface is possible, as WebPQ is designed for multi-user operation.

• Access to the web interface is via the web server URL, which is provided to users—this can, if necessary, also be local to the terminal server (e.g., https://localhost:8443).

Technical Recommendations:

• The terminal server must have sufficient resources (CPU, RAM, network bandwidth) for running WebPQ and any additional applications.

• Permissions and security settings of the %programdata% directory should be reviewed.

• Network configuration and firewall rules must allow access to the WebPQ web server; the path to the web interface should be communicated to users.

• For optimal performance, use the latest browser versions on client devices.

2.3.6. Recommended Tools

• PDF reader

• Installed browser: Chrome, Firefox, Microsoft Edge, Safari

• Database tools such as DBeaver (universal for all supported databases) or PG Admin for PostgreSQL

2.3.7. Recommended Certificates

• for the WebPQ WebServer: SSL certificate for secure communication in PEM format - see Informationen about SSL- Certificates

2.3.8. Typical System Configuration / System Diagram / Terminology

• WebPQ Server

  Virtual machine or PC where WebPQ runs as a service along with the database (PostgreSQL).

• WebPQ Client

  Host where the actual analysis of measurement data and management of measuring devices takes place via a browser. This host is often found in the office network.

• SMTP Server

  Mail server necessary for alerting and functions such as password reset, system messages, and automated alerting.

• NTP Server

  NTP server for synchronizing devices and the WebPQ server.

  	It is also possible to install the database on another server!
  Note

Required Port Numbers for Communication:

Releases in gateways and firewalls must be configured from row to column (e.g., from the WebPQ Client, port 8443 - HTTPS must be enabled to the server to allow data usage on the client).

* 1701...170X: Range for specific ports for PQI-Ds, depending on configuration.

Typical Data Volumes in Communication

Connecting a measuring device to the WebPQ database generates approximately 20 MB per week in the standard configuration. Since the readout process is continuous, the data transfer requires a minimum speed of only 200 kbit/s.

2.3.9. Customer Checklist – System Information & Requirements

The following checklist is used to collect system information and requirements for the WebPQ installation to ensure smooth and fast service. Please fill in the relevant fields and send the completed checklist to your contact at A. Eberle.

2.3.9.1. WinPQ Information

• Are you already using WinPQ?
  ☐ Yes ☐ No

• Which WinPQ version are you currently using? ______________________

• Please provide your WinPQ license number or license details: ______________________

2.3.9.2. General Database Information

• Which database type are you currently using?
  ☐ MSSQL ☐ MySQL ☐ PostgreSQL ☐ Other: _____________

• Which version of the database is in use? ______________________

• What is the size of your database (in GB)? ______________________

• Where is your database located?
  ☐ Local ☐ Server ☐ Other: _____________

• Do you have a backup routine in place?
  ☐ Yes ☐ No
  If yes, please briefly describe where the backups are stored: ______________________

• For a smooth process, please create a complete system backup (snapshot/backup) before installation. Please confirm: ☐ Yes ☐ No

2.3.9.3. General Device Information

• How many devices are integrated into the system? ______________________

• Which device types do you use?
  ☐ PQI-DA Smart
  ☐ PQI-DA DE
  ☐ PQI-DA LV
  ☐ PQI-D
  ☐ PQI-DA

• How many users will work with the system? ______________________

Note: The sum of devices and users determines the required number of units for WebPQ. If you have any questions, please contact your A. Eberle representative.

• Is an NTP server available? ☐ Yes ☐ No - IP address: ___________

2.3.9.4. General Server Information

• Does your server meet the current system requirements for WebPQ? See System Requirements ☐ Yes ☐ No

• Which operating system is installed on the server? ______________________

• Have the required ports for communication with the WebPQ database and devices been enabled?
  ☐ Yes ☐ No
  If yes, please specify which ports have been enabled: ______________________

• Is it a physical or virtual server?
  ☐ Physical ☐ Virtual

• What type of hard drive is installed in the server?
  ☐ SATA ☐ SSD

• Is the server joined to a domain? ☐ Yes ☐ No

• Is the server designed for 24/7 operation? ☐ Yes ☐ No

• Is an SMTP server available for alerts and user management? Recommended function ☐ Yes ☐ No
  Are the access credentials available? ☐ Yes ☐ No

  Server address: ______________________
  Port: ______________________
  Username: ______________________ (Required for commissioning – please do not provide here!) Password: ______________________ (Required for commissioning – please do not provide here!) Encryption: ☐ TLS ☐ SSL ☐ None

• Which partitions are available on the server (e.g., C:, D:, etc.)? It is recommended to store the database and temporary files on separate partitions. C: Size: _______________ D: Size: _____________

2.3.9.5. General Service Information

• Is a server migration planned or desired?
  ☐ Yes ☐ No

• Do you want to integrate new devices into the system?
  ☐ Yes, number ______ ☐ No

• Is remote access via TeamViewer or another tool possible?
  ☐ Yes ☐ No
  Are the access credentials available? ☐ Yes ☐ No

3. Safety Instructions

• Follow the operating manual.

• Always keep the operating manual during installation.

• Ensure that only trained personnel operate the software.

• Ensure that the software is only operated only in its original state.

• Ensure that the software runs in a secure system operation.

• Ensure that the software is regularly backed up.

• Ensure that the latest version of the software is always installed.

	For information on patch management, register on the homepage in the customer center or contact your sales partner!
Note

4. Intended Use

The product WebPQ is exclusively used for the evaluation of Power Quality measurement data and energy measurement data in the power grid at low, medium, and high voltage levels. If the software is used in a manner not specified by the manufacturer, it may potentially cause damage!

5. Installation

The installation of WebPQ is carried out in several steps, including installation, administrative configuration, and initial setup. As of 2025, with WebPQ taking over many functions from WinPQ, various installation options and operating modes are available.

5.1. Installation and Operation of WebPQ as a Standalone Version

This option is suitable if the basic functions of WebPQ, which continue to evolve, are sufficient and there are no special requirements for export formats or integration of devices from the classic platform (PQI-D / PQI-DA).

5.2. Operating WinPQ Software parallel to WebPQ

• Required if PQI-D or PQI-DA (see illustration in the software) needs to be integrated.

• Required if special reports from WinPQ are needed.

• Required if special exports, such as PQDIF, are necessary.

• Required if PQ Box data needs to be imported into the database.

WinPQ software is always included in the license and delivery of WebPQ software and can be selected or deselected during installation.

A separate uninstallation assistant is available for uninstalling WinPQ software, which is described here.

	Please make sure to check the compatibility information and versions of the supported databases in the chapter System Requirements
Hint

5.3. Activation of WebPQ via Activation Key

Starting with WebPQ version 2.1 the installation must be activated with an Activation Key. Until activation a notice dialog or the activation window is shown at the top. The software can be used for a maximum of 30 days without activation; within this period the Activation Key must be applied.

The activation file is generated using the hardware ID of the host and is only valid on this host. No direct internet connection is required for activation, but you must transfer a file from the host to another PC with internet access to activate the key at https://activate-license.powerquality.cloud/.

If the host hardware changes later, the stored activation is no longer valid and the activation process must be repeated. In that case, support may first need to reset the previous activation.

Proceed as follows:

1. Download the file LicenseActivationRequest.json via the button Save to file or copy its content via the button Copy to clipboard.

2. Open https://activate-license.powerquality.cloud/ and submit the activation request (either upload the file or paste the copied content).

3. After successful activation you receive an activation token for the license. Copy this token and paste it into the field to activate the installation, or alternatively use the file selection dialog to choose the activation file you downloaded from the activation page.

If you plan a system migration or the host hardware changes, a new activation is required. Repeat the process described above. For questions contact our support at pqsys-support@a-eberle.de.

For later license replacement, renewal, or reactivation details inside the running application, see the License Management chapter.

5.4. Installation variants

1. WebPQ Installation with Database (PostgreSQL) - Standard Case

   The PostgreSQL database is installed directly on the host along with the WebPQ application. This installation type is particularly recommended for small to medium-sized systems (up to 200 devices). The PostgreSQL database is also installed during setup. Individual directory structures can be adjusted during installation.

2. WebPQ Installation Without Database and Connection to an Existing Database or Installation of a PostgreSQL Database on a Dedicated Server

   This option is suitable if an existing database infrastructure is to be used or if the PostgreSQL database is installed on a separate server.

3. WebPQ Installation with Parallel WinPQ Installation with or Without a Database

   This installation type should be selected if WinPQ software functions need to be retained. It must be decided which instance (WinPQ or WebPQ) will handle communication with the devices.

5.5. Installation

The WebPQ software is delivered securely via our portal https://software.a-eberle.de using a dedicated one-time access with SHA256 hash sum verification. Please verify the checksum for security purposes.

5.5.1. Start and Language Selection

The installation process starts by double-clicking the "WebPQ_Setup_x.y.z.exe" file. The installation must be confirmed in the User Account Control with "YES." Next, a language selection for the assistant must be made.

5.5.2. License Agreement

Acceptance of the license terms is required. More details on the terms and maintenance contract can be found in the delivery documents.

5.5.3. Target Directory

A target directory for installation can be specified. All necessary operational data will be stored in this directory. User-specific data can be found in %programdata%/aeberle/webpq.

5.5.4. License File

A license file is required for the software to operate. This JSON-format file is provided during initial delivery or with a maintenance contract. The JSON file can be selected via "Browse" and is validated by the assistant. If the file is lost, please contact A. Eberle with your order and customer number.

5.5.5. Selecting WinPQ

If the WinPQ software is to be installed, it must be selected here. Information on why this might be necessary can be found under Operating WinPQ Software Parallel to WebPQ.

5.5.6. Database Installation

The appropriate mode must be selected based on the Installation Variants.

• Install PostgreSQL

In this mode, the following steps are performed:

• The PostgreSQL database is installed with the following default parameters:

  Parameter Name	Value
  Directory	C:\ProgramFiles\ WebPQDatabase
  Port	5432
  Database Service Name	WebPQDatabase
  WebPQ Server Service Name	WebPQServer
  WebPQ Client Service Name	WebPQClient

  • The database is installed with the following default passwords and users:

  Role	Username	Password
  Administrator	PQDBA	admin
  User	PQID	PQID

	The default passwords should always be changed to avoid significant security risks. It is recommended to use the advanced installation to set custom passwords.
Note

5.5.6.1. Advanced PostgreSQL Installation (Recommended)

In this mode, PostgreSQL is installed with custom settings:

• Port number for database access

• Target directory for the database (e.g., on another drive like an SSD)

• Custom usernames and passwords for "Database Administrator" and "Database User"

5.5.6.2. Installation Without PostgreSQL

This mode is suitable if an existing database is used, either running on another server or already available on the host. After completing the assistant, the following connection details must be available. Pay attention to case sensitivity in parameter names!

• Database name

• Username with database access

• Password for the database user

• Database schema name

5.6. PostgreSQL Backup Mirror with Streaming Replication

For installations with a dedicated PostgreSQL server, an additional continuously updated backup mirror can be set up. In this setup, a second PostgreSQL server runs as a replica of the production system.

5.6.1. Backup Philosophy

A replication server increases resilience, but it does not replace a classic backup strategy.

The recommended setup is therefore a combination of:

• one primary server for production,

• one backup server as a continuously updated mirror,

• and additional classic backups for retention, version history, and restoration of older data states.

Replication helps protect against server or hardware failure. Classic backups additionally protect against operator errors, logical data errors, and accidental deletion of data that would otherwise also be replicated.

5.6.2. Prerequisites

You need:

• one primary server with PostgreSQL and WebPQ,

• a second backup server or virtual machine,

• PostgreSQL on both systems,

• a working network connection between the two servers,

• and an administrator with PostgreSQL knowledge.

5.6.3. Goal

The backup server is a continuously updated copy of the primary server. Changes from the production system are transferred automatically. During normal operation, the backup server is read-only.

5.6.4. Simplified Overview

Server A = Primary server / production system
    -> WebPQ application
    -> PostgreSQL primary database
    -> active write operations

Server B = Backup server / mirror
    -> PostgreSQL replica
    -> continuous transfer of changes from Server A
    -> read-only operation during normal use

5.6.5. Step 1: Prepare the Primary Server

On the primary server, open the file postgresql.conf and set at least the following values:

wal_level = replica
max_wal_senders = 5

Then open the file pg_hba.conf and allow replication access for the backup server or the corresponding network. Example:

host replication replicator 192.168.1.0/24 md5

Then create a user for replication:

CREATE ROLE replicator WITH REPLICATION LOGIN PASSWORD 'password';

Restart PostgreSQL on the primary server afterward.

5.6.6. Step 2: Set Up the Backup Server

Stop PostgreSQL on the backup server.

Then clear the PostgreSQL data directory on the backup server. No old data residue should remain there.

After that, copy the database base state from the primary server using pg_basebackup:

pg_basebackup -h SERVER_A_IP -D /var/lib/postgresql/data -U replicator -P -R

Replace SERVER_A_IP with the address of the primary server and adjust the target directory to your PostgreSQL installation.

5.6.7. Step 3: Start the Backup Server

Start PostgreSQL on the backup server. Synchronization begins automatically after startup.

5.6.8. Verify the Setup

On the primary server, the replication status can be checked, for example, with:

SELECT * FROM pg_stat_replication;

If the backup server appears there as an active connection, replication is running.

5.6.9. Behavior During Operation

• Changes on the primary server are transferred automatically to the backup server.

• The backup server remains read-only during normal operation.

• The backup server is intended as a failover reserve and not as an additional working server.

5.6.10. Behavior in an Emergency

If the primary server fails, the backup server can be manually promoted to the new primary server:

pg_ctl promote

After that, the former backup server continues operating independently as the primary server.

There is no automatic failback to the original primary server. If the old primary server is to be used again later, it must be set up again as a replica or as a new primary system.

5.6.11. Notes

• Streaming replication does not replace regular file-based backups or PostgreSQL backups.

• Before updates and larger system changes, additional backups should still be created.

• For sizing, architecture, or recovery strategy questions, coordinate the database configuration with your IT department or system integrator.

5.7. Initial Setup of WebPQ

The WebPQ must be initially set up with an administrator in the application layer and certain basic settings such as global password policies. The initial setup must always be performed when a new database connection to an existing WinPQ database is created in the administrative layer! Normally, the initial setup dialog appears automatically after the installation.

The basic settings are divided into eight areas:

1. Welcome page

2. Language and layout

3. Time zone setting

4. Password policy

5. User identification and data

6. Privacy policy

7. Backup of the encryption key

8. Summary

9. Data adoption

Explanations of the sub-areas:

5.7.1. Step 2: Language and Layout

The language and layout are stored in the user account but can be adjusted again after login.

5.7.2. Step 3: User Time Zone

The user's time zone must be set to display times correctly in different time zones. Each measuring point also receives its own individual time zone. The user can choose between different time zone views.

5.7.3. Step 4: Password Policy and Company / Tenant Name 1

In the area of KRITIS, password policies per company are usually set by central IT. The setting here applies to all created passwords within the further administration. The setting can be changed individually afterward. See also: Tenant Settings

The following settings are possible:

• Minimum password length

• Password expiration time

• Number of lowercase letters

• Number of uppercase letters

• Number of special characters

• Number of digits

1

Tenants are used to isolate resources (users, devices) through administrative rights and data storage. Each resource in WebPQ™ is held by its own tenant. A tenant typically represents a real company or a department/project within a company. Tenants are organized in a tree structure, so a tenant can have sub-tenants, and the sub-tenants can have their own sub-tenants. All administrative tasks can be performed by the administrators of a tenant and by the administrators of all higher-level tenants in the tree structure. Devices and users of sub-tenants are visible and accessible to the owning tenant in addition to the tenant's own devices. Tenant capability is a licensed module in the system.

5.7.4. Step 5: User Identification

Here, the main administrator of the system is defined. The used passwords must be kept secure. Recovery of the root account is only possible with data loss.

	The entered administrative password must be kept secure and must not be lost! Recovery without data loss is not possible!
Note

5.7.5. API and Swagger Access

The static Swagger and OpenAPI assets of WebPQ are not public download URLs. The customer API description at /swagger.html, /swagger.json, and /integration-swagger.json requires an authenticated WebPQ session or a valid bearer token.

For administrators and developers this means:

• open the developer documentation from inside the authenticated WebPQ application when you need the current API entry points,

• use the shown Swagger UI or JSON description only after login or with an explicit API token,

• optional public user documentation in a deployment does not make the Swagger or API endpoints public.

If an SMTP server is configured in the advanced settings, the password can be recovered using the password reset function with the entered email address.

Information on password reset can be found under: Forgot Password

5.7.6. Step 6: Privacy Policy

If you want to create an individual privacy agreement for your employees or customers, you can do so directly here. The software logs the required information automatically on the server as per the requirements, e.g., from the BDEW whitepaper.

Information on audit logging can be found under: Audit Logging

5.7.7. Step 8: Data Adoption & Backup of the Master Key

The application encrypts sensitive data with a central encryption key using the AES-256-CBC method, known as the Master Encryption Key. This key is stored in the configuration file settings.json and is encrypted with the security functions of your operating system. Since the functionality of these security features may change due to operating system upgrades or migration to another computer, there is a certain risk of losing data encrypted with the Master Encryption Key. It is very important that you download or securely store this information NOW! There will be no further opportunity to do so.

After all data has been entered, it is transferred to the database, and the application is restarted.

5.8. Uninstallation / Removal of the Software

The WebPQ software is usually installed together with a locally running PostgreSQL database. Therefore, both the software and the database must be uninstalled in two separate steps if necessary.

5.8.1. Uninstallation of WebPQ Software

The uninstallation of WebPQ software is done through the Windows built-in uninstallation assistant. This can be accessed either through the Control Panel or by searching in the Windows Start menu.

5.8.2. Uninstallation of the Database

The database must be uninstalled through the Windows Services Management. The "WebPQDatabase" service must be stopped and removed. Then, the database files can be manually deleted.

Follow these steps:

1. Open the Windows Services Management.

2. Stop the "WebPQDatabase" service.

3. Uninstall the "WebPQDatabase" service.

4. Delete the database files in the database installation directory (default: C:\Program Files\WebPQDatabase).

Alternatively, the uninstallation can also be done via the command line. Open the command line with administrator rights and enter the following commands:

sc stop WebPQDatabase
sc delete WebPQDatabase

5.8.3. Deleting Temporary and Exported Files

The WebPQ software stores temporary files and exported files in the directory %programdata%/aeberle/webpq. These files can be manually deleted after uninstalling the software. However, ensure that no important data is lost. Similarly, files of exports and reports may be stored in directories set within the application. These should also be deleted.

5.9. Administrative Configuration / Backend of the Software

The administrative interface or backend may open with pre-configured connection settings during the initial installation. It can be accessed anytime on the host via the taskbar (next to the clock) by right-clicking the "WebPQ" icon and selecting "Administration."

During the initial setup of the software, usually only the hostname of the database server, the database name, and the username and password of the database need to be configured in the "Database" section. If the database is installed on the same host as the WebPQ software, the default values can usually be retained.

After correctly entering all settings, the processes restart by clicking the "Update" buttons. Then, you will be asked if the application should be started with the embedded web browser. Clicking "Yes" opens the frontend in the app.

The administrative interface itself is generally divided into six main areas, which can be accessed by clicking on the name.

5.9.1. Part 1 - Service

In the "Service" section, the user can monitor (#1), restart (#2), and stop (#3) the status of the background services "WebPQService.exe," which runs under the "System" account.

Generally, the service that provides the web server for the clients should be both installed (Installed: YES) and continuously running (Running: YES).

The service starts automatically when the host starts and runs in the background. It is responsible for communication between the clients and the web server.

5.9.2. Part 2 - Processes

The "Processes" section shows the running processes of the software. Here, the processes can be monitored and restarted if necessary.

5.9.3. Part 3 - Database

The settings in the database section are necessary to establish a connection with the database server. The database connection settings can be found in WinPQ under "System Management >> Database" if an existing WinPQ database is to be used for WebPQ.

2

Licensed feature for MySQL and MS-SQL - We recommend using the standard PostgreSQL solution in any case.

	For MSSQL databases, the database schema dbo should be used.
Note

For a connection to a WinPQ system installed with its default settings, the following settings should be used.

5.9.3.1. Settings for installation up to WinPQ v6.1*

5.9.3.2. Settings for installation up to WinPQ v6.2*

	We recommend changing "default passwords" in any case and using appropriate secure passwords according to your company policies! Instructions for changing passwords can be found in the WinPQ user manual.
Note

5.9.4. Part 4 - Network

The settings in this section refer to the web server installed on the host (server) in the form of the WebPQ application and the clients (evaluation PCs) that provide the interface.

The default settings are "security by default." For example, the web server on the installed PC is only accessible by clients via HTTPS on port 8443 (#2) by default. The service of an unencrypted connection is disabled by default (HTTP).

To use "HTTPS," i.e., the encrypted connection from the client (evaluation PC) to the web server, without a warning of an unknown certificate in the browser on the client (evaluation PC), it is recommended to store your own certificates protected with a password (#6) in the WebPQ application (#3 & #4).

To store the certificates, they must be in PEM format. More information can be found under PEM Certificates.

The certificates can be stored at the specified path and selected in the program interface by clicking (#5) on the path.

	Using "unencrypted" connections and unknown certificates can lead to "data theft" and "data loss"! We always recommend using the "secure" default configuration (HTTPS)!
Note

5.9.5. Part 5 - Installation Paths

In this section of the software, all paths where the software stores data are listed. This includes exports of reports in PDF format, data exports in various formats such as CSV and COMTRADE, as well as NEQUAL, log files like the audit log, and temporary files.

5.9.6. Part 6 - Other

This section of the software specifies the path where the settings made in points #1, #2, #3, #4, and #5 are stored (settings.json). For example, if you want to set up a new server or plan a migration, this file can be used to transfer the settings from PC A to PC B. Passwords for the database connection and certificates are excluded from this.

6. Operation & Usage

6.1. Accessing the Software Locally or via Client

The WebPQ software is opened on workstations via a web browser by accessing a specific link. This link may vary depending on the IT environment and installation. To ensure smooth use of the software, it must be ensured that the port defined in the installation is accessible from the workstation PC and a connection to the server with the installed WebPQ software can be established.

Examples:

Local Installation

If the server on which WebPQ is installed is also the workstation PC, the software can be opened in the browser using the following link.

https://localhost:8443/

Client-Server Architecture

If the WebPQ software is installed on a different PC (server) than the workstation PC (client), the address of the server (in this example, the server has the IP address 10.10.1.20) must be entered.

https://10.10.1.20:8443/

System Login:

Enter the username and password to log in directly to the system!

6.1.1. Change Password

The user can set their login password directly via the Change Password function before logging in by entering their username and current password. The password policy set for the tenant must be observed!

6.1.2. Forgot Password

If the system in the local installation has access to an SMTP server / mail server, it is possible to recover the password using the Forgot Password function and the email address assigned to the user.

	In case of incorrect login attempts, the user will be blocked for five minutes after five incorrect attempts. The incorrect login attempts are also logged in the system.
Note

6.2. Software Layout and Functions

• General Layout of the WebPQ Software
  Overview of the user interface and its structure for easy navigation in the software.

6.2.1. Analysis - Types and Options

The software is divided into the following areas for PQ and other analyses:

• Visualization Pages
  Description of the pre-configured dashboards that enable quick and targeted display of PQ measurements.

• Usage in Analysis
  Guide to efficient use of analysis functions, including available tools and settings.

• Analysis Cockpit
  The central analysis tool for creating individual dashboards. More than 20 different analysis types are available to perform customized evaluations.

• Device Analysis
  Detailed & pre-configured analysis functions for individual measuring devices to specifically access their data. A quick and easy way to keep track of individual measuring points.

• Dashboard Analysis
  Individual dashboards can be created via the Analysis Cockpit, which can be directly or automatically converted into scheduled reports. It is possible to create any number of dashboards and flexibly adapt them to different analysis requirements.

6.2.2. Reporting - Types and Options

The "Reporting" area includes all settings required for creating normative reports (PQ standard templates). It also offers the possibility to define automated tasks (automation tasks) to execute reports and data exports on a scheduled basis.

• PQ Standard Templates #1
  Here, all templates for calculating statistical values can be managed. This includes standardized templates such as EN50160, IEC61000-2-4, and IEC61000-2-2, which are regularly updated by A. Eberle. Based on these standard templates, the user can create their own templates and apply them to specific measuring points.

• Reporting Automation #2 Allows the configuration of automated reports, email dispatch of reports and disturbance records, as well as the automatic data export and import management. The function links predefined tasks with measuring points and templates to ensure efficient report generation.

6.2.3. Import / Export

The Import/Export area includes all interfaces for data and report exchange between the WebPQ platform and external systems. Here, measurement data can be imported, reports and raw data can be exported, and synchronization processes can be monitored. Additionally, functions for manual download of PDF reports as well as CSV and measurement data import are available.

• Data Import#1

  Allows manual import of measurement data from the devices PQI-DA smart, PQI-LV, and PQI-DE into the WebPQ database.

• Data Export#2

  Management of exports in various formats (CSV, NEQUAL, COMTRADE, PQDIF), both manually and automatically via Reporting Automation.

• Data Synchronization#3 Synchronization of measurement data from one WebPQ instance to another by means of files.

• Print & PDF Export#4

  Generation and provision of PDF reports, either manually or automatically via Reporting Automation.

• Device Synchronization#5

  Status display of device synchronization. Shows which measuring devices have been synchronized with the WebPQ database, including detailed status information and log files for error analysis.

6.2.4. Settings / Administration

The Settings area includes all administrative functions of the software. This includes the configuration of measuring points, user and rights management, and tenant management. Additionally, other central settings are available here, such as device tagging, license management, and – if licensed – fleet management.

• Devices#1

  Management and configuration of measuring devices. Here, measuring devices can be viewed, added, administered, and deleted. Additionally, you have access to versioned parameter sets and the ability to read log files. This area also contains measuring point-specific parameters such as NEQUAL and allows access to the device web pages within the WebPQ software.

• Fleet Management#2

  Mass management and configuration of measuring devices via the licensable fleet management. It allows simultaneous updating of many measuring devices with new firmware or limit value sets, significantly facilitating the management of large device fleets.

• Users & Rights#3

  Management of users, groups, and access rights. In this area, tenant-wide settings such as email server, company name, logos, or password policies can also be configured.

• Device Tagging#4

  Management of the hierarchical display of measuring points through categories and tags.

• License Management#5

  Overview and management of the software license, including the number of users and measuring points (units).

• Data Protection#6

  Management of data protection agreements in accordance with GDPR guidelines within your company.

6.3. User Interface of the WebPQ Software

The WebPQ application is divided into three main areas:

1. Navigation Bar: The navigation bar #1 is located on the left side. For smaller screen resolutions, it is moved to the top area. In this case, the navigation can be opened by clicking on the three lines.

1. Header – The header contains important controls and information:

   • Navigation Bar (#2): Shows the current position within the application and allows quick navigation.

   • Account Settings (#3): Here you can manage personal settings and view user information. See:

     Account Settings

   • System Status / Syslog (#4): Provides information about the current state of the application, such as connection status or system messages. See: System Messages / System Status or Logfiles

1. Workspace: The central area #5 of the application, where the actual content and functions are displayed and edited. This is where data entry, analysis, and visualization take place.

To use the workspace as efficiently as possible, you can reduce the navigation bar to compact buttons. To do this, the Always Expand option #1 must be deactivated. This way, the navigation is only displayed when needed, providing more space for the actual workspace.

6.3.1. System Messages / System Status

To organize the system with connections to many measuring points and to operate the system in a stable fashion, the software lists all messages centrally and clearly via #1.

If the exclamation mark turns red , new system messages – such as connection interruptions or messages about the battery status of the measuring devices – have occurred. If the exclamation mark is green , all messages have been acknowledged (#3) or no new critical messages have occurred.

All messages can be acknowledged as a whole (#3) or individually by clicking on the message as shown in the screenshot below (#1) for each device / globally and per user or globally. To do this, select the option under device or user in the dropdown list and confirm this via #3.

It is also possible to "silence" individual messages. This may be necessary, for example, when shutting down a connection for maintenance purposes. To do this, select function #2 "Silence Message". This function can also be set per device or globally for the message type per user or for all users. The "silenced messages" button allows you to view and reactivate the silenced messages. To do this, simply click on in the respective row of the message to be reactivated.

6.3.2. Account Settings

Each user can customize individual settings such as language, theme, and password directly in their user profile.
To open the settings, click on your username at the top right:

6.3.2.1. My Account

In the Account Settings section, personal data such as name and email address are displayed and can be edited.
The timezone can also be configured here, which is important for the correct display of timestamps throughout the software.
Changes are applied immediately after clicking Save and apply to all logged-in devices.

Technical Notes:

• Changes to email or password require re-authentication (JWT token is updated).

• The timezone setting affects all time information in reports and notifications.

6.3.2.2. Theme Settings

In the Theme Settings section, the appearance of the software can be customized:

• Font size: Choose between three predefined sizes (Standard, Large, Extra Large)

• Color scheme: Switch between Blue, Black, or Light theme

• Language: Select the software language (e.g., German, English)

Technical Notes:

• Theme and language settings are stored locally in the browser and server-side in the user profile.

• Changes to color scheme and font size take effect immediately in the UI (without reloading).

• The language setting controls all UI texts and system notifications.

6.3.2.3. User Permissions

The permissions assigned to the user are displayed here clearly and in read-only mode.
Typical permissions include Admin, Read, Write, Device Management, etc.
Managing and assigning user permissions is only possible in the separate administration area of the software.

6.4. Visualization Pages

6.4.1. Grid > Overview

6.4.1.1. Grid Overview – Heatmap

The homepage of the Grid > Overview software provides the user with a quick overview "Heatmap" of all devices connected to the WebPQ software. This overview spans a selected time period, #1, typically a calendar week. The landing page is automatically updated every 60s to always display the latest disturbances. Using the #2 function, the interface can be sorted into custom hierarchy levels, allowing many measurement points to be displayed hierarchically according to the application. More information can be found under Hierarchy Settings

The devices are sorted by default according to the number of disturbances in the #3 area. Disturbances are color-coded:

• Red: Unacknowledged disturbances

• Green: Acknowledged disturbances

Clicking on an OSC or TRMS record opens the Analysis Cockpit. Subsequently, the button color with the number of records changes from red to green.

In the PQ – Events#4 area, the number of power quality events is listed based on the power quality standard stored and set in the measuring device – e.g., EN50160 or IEC61000-2-4.

Clicking on the -/+ allows the individual areas to be expanded or collapsed. In the collapsed state, the maximum values of the subordinate measurements are always used for the display.

In the Long-term Data#5 area, the statistical data is calculated according to the standard stored in the measuring device. These include:

• Frequency[F]

• Voltages[U]

• THD (Total Harmonic Distortion)

• Flicker[PLT]

• Voltage Unbalance[UU]

When the mouse pointer hovers over an abbreviation, an explanation is displayed via a tooltip.

Clicking on the designation, e.g., PLT, sorts the display either from the worst to the best measurement point or vice versa. This function facilitates the identification of the most noticeable measurement points for the respective measurement value.

Clicking on the respective measurement values – e.g., THD – opens the Analysis Cockpit. This allows the abstract representation of the measurement values to be converted into a temporal representation for detailed analyses.

In the Harmonics#6 area, all harmonics from H2 (100 Hz) to the 50th harmonic (2500 Hz) as well as the Supraharmonics#7 are listed in relation to the respective limit value. The color scale in the statistical measurements shows the proximity to the limit value:

• Green: Values well below the limit

• Yellow/Orange: Values approaching the limit

• Red: Values exceeding the limit

To quickly find a desired measurement point, the name of a measuring device can be entered in the Search Bar#8 area. The display is then interactively filtered.

Clicking on a device name#9 switches the application from Grid >> Overview to the Analysis >> Device page.

6.4.1.2. Grid Overview – Tile View

In the second area Grid Overview – Tile View, all devices with their essential live values are displayed within the configured hierarchy levels.

With Enable Edit Mode #1 the tile arrangement can be changed via drag & drop and devices or groups can be assigned to other hierarchy levels. After Save the adjustments are stored persistently and loaded on next access. Changes apply system-wide for all users and can be centrally managed by the administrator.

Via Change Default Displayed Measurements you can define which live data appear in the tiles. All real-time values provided by the measuring device are available. Settings can be made

• globally (all devices),

• per group,

• or per device (#3) in edit mode.

Usage:

• Displayed Data for the Group: Applies to all devices in the group.

• Displayed Data for the Device #3: Individual device configuration.

The refresh interval of the live data is configurable. The hierarchy order can be adjusted using drag & drop in the upper right corner.

A tile contains the following elements in live operation:

#1 Connection status: Red = no connection, Green = connection active
#2 Link to the Power Quality report (e.g., EN50160, IEC61000-2-4)
#3 Link to device parameterization
#4 Display of the configured live data

6.4.1.3. Grid Overview - Map View

Map View allows users to see devices on a map and combine the geographical view with threshold utilization, fault records, and PQ events for the selected time range. It is intended for quickly locating affected areas and then jumping to the relevant analysis or device settings.

6.4.1.4. Setup

Prerequisites

• Maps zip package provided by Application Support

• Access to the WebPQ backend running on the WebPQ server

• A folder on the WebPQ server where map data will be stored. By default, C:\ProgramData\aeberle\webpq\maps is preconfigured. The next section explains how to change this path.

Configure the path in the WebPQ backend

1. Open the WebPQ backend.

2. Scroll to Paths.

3. Set the Maps Storage Folder field to the desired folder.

4. Save the change (Update) so the setting is applied.

Place the maps package in the maps folder

• Extract the zip file to the configured maps folder.

• Two files must now exist in the root of the maps folder: map.mbtiles, which contains the actual map data, and map-info.md. This file contains information about the region and detail level of the maps package, which helps when downloading a newer package later.

• Restart the WebPQ Server service after a new package was extracted or replaced so the tiles are loaded again.

Verification

• In WebPQ, navigate to Grid > Overview > Map View.

• If no map package is loaded yet, a message box explains the required setup steps.

• The documentation link in the upper right corner of Map View opens this documentation section.

Troubleshooting

• No map loads: verify the maps folder path, folder permissions, and restart the WebPQ Server service.

• Map does not render: ensure the zip file was extracted and map.mbtiles is present in the folder root.

• No device pins: confirm latitude/longitude are configured for the device (see Device Settings).

• A device appears in tables but cannot be focused on the map: the device does not yet have valid geodata. Open Device Settings and update the location.

6.4.1.5. Functionality

6.4.1.5.1. Device Settings

To display a device in Map View, the device geocoordinates must be configured first. Open Device Settings and select a device. The device position can be configured in the General tab. Enter latitude and longitude, or set the coordinates by clicking on the map.

6.4.1.5.2. Map View

Map View is divided into three areas:

• View settings

• The map with tooltip

• Information panels

View settings

Contains the following UI elements:

• Show All resets the map to the initial overview of all devices with geodata.

• Time interval filters threshold utilization, fault records, and PQ events. The default range is the last 7 days.

• Show only visible devices limits the bottom panels to the devices currently visible in the map viewport. The setting is stored and restored when Map View is opened again.

• Show Hierarchy controls whether hierarchy tags are shown in tooltips and bottom-panel tables. This setting is shared with the overview-page hierarchy display.

• The documentation link in the upper right corner opens the corresponding customer-documentation anchor for Map View.

Map

Initially, Map View shows all devices that have a configured geolocation. Multiple nearby devices are shown as a cluster with the number of devices. Clicking a cluster zooms in until individual devices are visible.

Marker colors can reflect the currently calculated threshold utilization, which helps identify critical areas immediately on the map.

Each device is shown with a pin and the device name. Clicking a pin opens a tooltip with information about the device:

• Device name and links to the PQI app, reporting page, and device parameterization

• Hierarchy tags, if Show Hierarchy is enabled

• Last synchronized data point and how long ago the last data import occurred

• Address configured for the device

• Threshold utilization as a table overview

Selecting a device from one of the bottom-panel tables centers the map on that device and opens the tooltip. Devices without configured geodata remain visible in the tables, but they cannot be focused on the map until a location is configured.

Information Panels

At the bottom of Map View there is a panel with four columns. Above each column there is a heading with relevant links to other areas of the application.

Clicking any device name centers the map on that device and opens the tooltip. Each information panel column can be expanded or collapsed using the small arrow button in the column header. Collapsed columns appear as narrow tabs on the left side. Column width can be adjusted by dragging the separators. The overall panel height can also be resized. Column widths, collapsed states, panel height, and the Show only visible devices setting are saved and restored when Map View is opened again.

Devices:

Shows the currently relevant devices together with the configured address. Depending on the Show only visible devices toggle, this is either the current map viewport or the complete device set. The table supports sorting and filtering by device name and hierarchy tags.

Fault Records:

Shows recorded fault records for the selected time range and the currently relevant devices. The heading contains a direct link to the Fault Records page.

The table shows the time, device, type, and trigger-related information. Clicking a fault-recording type opens the detail view directly in the panel.

Thresholds and utilization:

The header contains a shortcut to the corresponding cockpit analysis for the selected time range.

Utilization of the user-defined thresholds of the devices.

Users see the maximum utilization of the thresholds defined for each device. Clicking a utilization percentage opens the Analysis Cockpit with the corresponding threshold data. Clicking a threshold value opens the related threshold settings, if a reporting setting is available.

The application is able to assign a threshold to each measured value and display the utilization here as a maximum value. More in the chapter "customer-specific thresholds". @Fabian insert link to new Threshold chapter here.

PQ Events:

Lists PQ events for the selected time range and the currently relevant devices. The heading contains links to the PQ Events over Time analysis and the PQ Events page.

The table shows the event time, device, linked OSC/TRMS recordings, event type, and the measured value. Sorting and filtering can be used to narrow down the list to specific event types or devices.

6.4.2. Grid > Fault Records

In the Grid > Fault Records area, all disturbances within a freely selectable time period #1 are displayed in a list.

The display offers the following functions:

• Date-range jump buttons for quickly switching by week and jumping back to the current day

• Hierarchy display for showing or hiding the configured device-tag hierarchy in the device column

• Search function#2 for targeted search of disturbances

• Device filtering via the device tree in the table header

• Ability to open fault records via the OSC and TRMS#3 links in a Quick View

In the #4 area, the user can set individual filters. In the shown example, a filter on duration > 50 ms is set, displaying only disturbances in this range. The table can also be sorted by type, time, device, trigger, duration, and other available columns.

The device column supports both free-text search and selection through the device tree. If hierarchy display is enabled, the configured device tags are shown directly in the list so that disturbances can be grouped more easily by location or structure.

Clicking on OSC or TRMS#1 opens the Quick View window from the right.

For advanced analysis options, setting markers, or describing the disturbance, the Analysis Cockpit can be opened via #2.

Clicking a device entry opens the corresponding device page at the event time. This helps when the fault record needs to be checked together with device details or configuration.

To view two or more fault records in parallel, multiple disturbances can be selected via the selection function. The selected records can then be loaded together into the analysis view for direct comparison.

6.4.3. Grid > PQ Events

In the Grid > PQ Events area, all Power Quality Events (not disturbance records!) within a freely selectable time period #1 are displayed in a table.

The display offers several search and filter functions#2:

• Filter by disturbance record (#3): Shows only PQ events where a disturbance record was triggered according to IEC

• Filter by type (#4): Allows free text search for the type of event

• Filter by device (#5): Convenient device narrowing via device selection

• Filter by value range (#6): Setting an upper and lower limit value

• Filter by duration (#7): Restriction to events of a certain duration

Above the table, the same date-range jump buttons as in the fault-record view are available. The table also provides a hierarchy toggle so that configured device tags can be shown or hidden in the device column.

The device filter only offers devices that actually have PQ events in the selected time range. This makes it easier to narrow large installations down to the relevant sources quickly.

Additionally, existing disturbance records can be opened directly in a Quick View via the OSC and TRMS#8 links.

The Description column is derived from the PQID metadata of the event type. This means the table shows the translated event description that belongs to the stored PQ event.

The current result set can be exported directly via the Export button above the table.

Clicking on OSC#1 opens the Quick View window from the right.

For advanced analysis options, setting markers, or describing the disturbance, the Analysis Cockpit can be opened via #2.

6.4.4. Operation in the Analysis

6.4.4.1. Zooming in the Analysis – Zoom In / Zoom Out

To zoom, use the left mouse button or, on a touch display, the standard two-finger zoom gesture.

• Zoom In: Hold down the left mouse button and drag left or right.

You can save the zoomed area using the "Keep Zoom" function #1. To reset the zoom to its original value, use "Reset Zoom".

6.4.4.2. Submenu in the Analysis #2

• View in Full Screen Mode: Expands the graphic to fill the entire monitor, which is especially useful for tablets or phones.

• Export as CSV: Saves the measurement data as a CSV file.

• Export as PDF: The disturbance record is saved as a PDF and can be downloaded from the server via (Import/Export >> Print) after creation.

• Export as JPG / SVG or PNG: Exports the graphic in various image formats.

• Export as Comtrade: Converts the disturbance record into a Comtrade file, which is also available on the server via (Import/Export >> Export).

• Export as PQDIF: The disturbance record or measurement data (depending on the analysis) is saved as a PQDIF file and can also be provided on the server via (Import/Export >> Export).

Note:
Exports, including PDFs, are stored on the server. The storage location is defined in the server settings in the WebPQ backend and can only be changed by the administrator. Installation Paths

6.4.4.3. Show & Hide Measurements on the Y-Axis

By clicking on a measurement#1, individual measurements can be selected or deselected. Deselected measurements are automatically moved to the bottom. Measurements are always displayed in order of their height on the Y-axis.

6.4.4.4. Analysis Cockpit

The Analysis Cockpit can be accessed and opened at any time via the button .

More information about the Analysis Cockpit can be found under Link

6.5. Analysis

The Analysis Cockpit is the central workspace and analysis area, offering various types of analysis, including:

• Level-time diagrams

• Bar charts

• Histograms

• Pre-configured reports for creating custom dashboards and reports

6.5.1. Analysis Cockpit

You can open the cockpit in several ways:

• Via the main menu under "Perform Analysis"

• Via the analysis dashboard by selecting "Add Analysis"#1

• By clicking a measurement value in the statistics under "Network > Overview"

• Via the shortcut from any analysis

6.5.1.1. Structure of the Analysis Cockpit

The Analysis Cockpit is divided into two sections:

• Left section: Configure settings here

• Right section: Visualise measurement data here

Key functions in the Analysis Cockpit:

• Basic settings#1:

  • Select the analysis type

  • Define the device selection

  • Set the evaluation periodSettings

  • Choose the measurement variables

• Analysis evaluation#2:

  • Set and display markers

  • Comment and prioritise disturbances

  • Display limit and extreme values

• Analysis layout#3:

  • Group measurement variables

  • Scale the display

  • Select colours for measurement values

• Widget settings#4:

  • Adjust the size and title of an analysis widget

  • Save the widget to the analysis dashboard

• Save#5:

  • Permanently save the analysis in the analysis dashboard.

  • The dashboard is stored for the user in the database, allowing all created analyses to be recalled and restored.

• Auto synchronisation#6:

  • When enabled, changes are immediately shown in the right section

• Apply#7:

  • Applies the selected measurement variables and displays them in the right frame

• Cancel#8:

  • Closes the Analysis Cockpit without saving data

Note:
The Analysis Cockpit settings are saved in the browser cache. This means data is retained even if the analysis is not saved in the dashboard.

6.5.2. Basic analysis settings

6.5.2.1. Analysis settings

Under #1, select the desired analysis type. By default, the level-time diagram is pre-selected. Alternatively, other types such as histograms or, for power quality event analysis, the ITIC graph can be chosen as the evaluation type.

With the time setting#2, you can open a dialog to configure the analysis period. If an absolute period has been defined in the

menu, it can be set either by directly entering the start and end time under #3 or via the input fields.

In the device section #3, select the devices to be evaluated. This can be done by entering the device ID or using the selection list by clicking #3. The list shows all devices available in the database.

Using the measurement variable tree#5, select the measurement values recorded by the chosen devices during the selected period and transferred to the database. The selection can be reset with #4.

Depending on the analysis type, specific parameters must be considered for correct evaluation. These are explained in the following sections.

6.5.2.2. Analysis types

6.5.2.2.1. Level-time diagram

The level-time diagram displays selected measurement values as a line chart over a defined period. It is ideal for temporal analysis of measurement values and their changes.

A special feature is the integration of flagging according to IEC61000-4-30 Class A. If enabled, flagging information is shown directly in the measurement variable tree #1 within the measurement series.

Measurement variable selection is dynamic: It is based on the intersection of available data, restricted by parameters such as period and selected devices.

See also: Time settings for experts

6.5.2.2.1.1. Displaying Thresholds

In the "Analysis Evaluation" tab, you can display the thresholds stored in the measuring device for the selected measurement variables. From version v2.1, alternative threshold sets can also be selected and applied to the measurement data.

To show thresholds, select either the standard thresholds #1 or the extended threshold sets #2. Thresholds are then automatically displayed in the chart.

Extended threshold sets can be customised and managed in Reports > PQ Standard Templates. You can create, edit, or delete threshold sets there.

6.5.2.2.1.2. Display of flagging status

Flagging is visualised as a normal measurement value and displayed in the measurement series.

6.5.2.2.1.3. Setting markers for detailed analysis

In the level-time diagram, up to two markers can be set for detailed examination:

1. Set marker:

   • A left-click on a data point adds a marker.

   • Up to two markers can be set at once to compare differences between measurement values.

2. Remove marker:

   • Clicking a set marker again removes it.

Marker values are automatically displayed in analysis evaluation and can be used for further analyses.

6.5.2.2.2. PQ events over time

The PQ events over time diagram visualises recorded and selected power quality (PQ) events within the defined time range.

6.5.2.2.2.1. Interactive analysis

• Retrieve detailed information:

  • Hovering the mouse over an event displays additional info, such as the height or depth of the event or other relevant measurement values.

• Compare multiple PQ events:

  • The temporal view makes it easy to identify patterns and clusters of events.

  • Notable events can be further investigated via the Analysis Cockpit.

6.5.2.2.3. Histogram

The histogram shows the statistical distribution of a selected measurement variable within a defined period.

6.5.2.2.3.1. Functions and analysis

• Select measurement variable:

  • In this example, frequency#1 was chosen.

• Calculate distribution:

  • Data was grouped into 10-mHz bins over the selected period #2 and displayed as a frequency distribution.

• Application areas:

  • The histogram helps identify deviations from expected values.

  • Unexpected peaks or asymmetries may indicate anomalies or systematic errors.

6.5.2.2.4. Scatter plot

The scatter plot visualises the relationship between two selected axis values as a cloud of points. Each point represents one individual measurement record. This analysis type is especially useful for spotting correlations, clusters, outliers, and distributions quickly.

Unlike the level-time diagram, the scatter plot focuses on the relationship between two characteristics instead of their temporal progression. This makes it easier to compare measurement variables directly or structure data by device, tag category, or plot group.

6.5.2.2.4.1. Typical use cases

• Compare two measurement variables, for example active power against reactive power

• Identify typical operating states through cluster formation

• Find outliers or unusual operating states

• Compare multiple measuring points or groups in one shared chart

6.5.2.2.4.2. Important settings

• X axis and Y axis: define which values are plotted against each other

• Plot groups: allow multiple data sources or configurations to be combined in one view

• Color axis: adds another visual distinction for points, for example by measurement variable, device, or group

• Shape axis: provides an alternative visual grouping through different marker symbols

• Automatic gap cutouts: compress large empty axis areas so relevant point clusters stay readable

6.5.2.2.5. FFT Spectrum

The FFT Spectrum analysis is used to inspect the frequency spectrum of oscilloscopic measurement data. It is useful when periodic signal components, resonances, or dominant frequency bands need to be identified directly from time-domain recordings.

6.5.2.2.5.1. Prerequisites

• The selected device must provide oscilloscopic measurement data.

• FFT-specific options become available only when suitable oscilloscopic data types are selected in the measurement-variable selection.

• Historical FFT uses the selected analysis interval. Live FFT requires an active live-data stream.

6.5.2.2.5.2. Historical FFT

Historical FFT is based on stored oscilloscopic data in the selected time range. It is suitable for analysing already recorded events or archived oscilloscopic measurements.

• Select the device and the oscilloscopic measurement variables to evaluate.

• Define the analysis interval in the Analysis Cockpit.

• The resulting chart shows the frequency on the X-axis and the magnitude on the Y-axis.

• Multiple selected data types are displayed together in the same spectrum view.

This analysis helps identify characteristic frequencies after a disturbance and compare the spectral content of different oscilloscopic channels.

6.5.2.2.5.3. Live FFT

In addition to historical FFT, WebPQ also provides Live FFT as a dedicated live analysis type.

• Live FFT subscribes to live oscilloscopic data of one selected device.

• The spectrum updates continuously as new live samples arrive.

• The chart can be zoomed horizontally to focus on relevant frequency ranges.

• Device naming follows the currently configured device-name and hierarchy display settings.

Live FFT is useful for observing changing spectral content while a signal is still being streamed.

6.5.2.2.5.4. FFT options

Depending on the selected oscilloscopic data, additional FFT options are available in the parameter area:

• Time Window Mode controls how the FFT window is derived from the signal.

• A fixed time window width can be configured when the fixed-window mode is selected.

• If no suitable oscilloscopic data is selected, FFT-specific controls remain hidden.

6.5.2.2.5.5. Application areas

• Detect dominant harmonic or interharmonic components in oscilloscopic signals.

• Compare live and recorded spectral behaviour.

• Investigate resonances, converter-related frequencies, and recurring oscillations.

• Narrow down disturbance sources before switching to a more detailed time-domain analysis.

6.5.2.2.6. Custom Threshold Utilization Report

The Custom Threshold Utilization Report compares the maximum measured values of the selected interval with the configured maximum values of custom threshold settings. It is intended for quickly identifying devices that already use most of their individual threshold reserve.

6.5.2.2.6.1. Prerequisites

• At least one device and a valid analysis interval must be selected.

• At least one custom threshold setting must also be selected.

• A custom threshold only produces usable results if it is assigned to the device and matching data class, and if a maximum threshold value is configured.

6.5.2.2.6.2. Display and content

The analysis is shown as a table. Depending on the selected view, it includes in particular:

• the title of the evaluated measurement value,

• the assigned threshold name,

• the unit,

• the measured maximum value in the selected interval,

• the configured threshold maximum,

• the utilization in percent,

• and the remaining reserve.

The default sorting is by the highest utilization. With Advanced view, additional columns such as the unit can be shown.

6.5.2.2.6.3. Interactive functions

• Clicking the threshold name opens the corresponding custom threshold settings.

• Clicking the measured maximum value opens the Analysis Cockpit with the corresponding time-series analysis and custom thresholds already enabled.

• Sorting and filtering are available as long as the analysis is not rendered as a printed report.

6.5.2.2.6.4. Color logic

Utilization is shown as a colored progress bar:

• below 60%: green

• 60% to 74%: yellow

• 75% to 84%: orange

• 85% or more: red

This makes it easy to identify critical devices at a glance.

6.5.2.2.6.5. Reasons for unavailable values

If a value cannot be calculated, the table shows a warning indicator with the corresponding explanation. Typical reasons are:

• No valid measurement data is available in the selected interval.

• No maximum threshold is configured in the selected custom threshold.

• No matching custom threshold is assigned to the device and data class.

• The available threshold data is not sufficient to calculate the result.

6.5.2.2.6.6. Application areas

• Identify measurement points with little remaining reserve to custom thresholds.

• Compare several devices within one common time interval.

• Jump directly from the overview into the matching time-series analysis or the threshold settings.

6.5.2.2.7. Voltage and current harmonics as bar charts

Voltage and current harmonics are displayed as bar charts to provide a quick overview of the entire frequency spectrum to be monitored.

6.5.2.2.7.1. Display and interpretation

• Colour-coded bars for quick analysis:

  • The red area of a bar shows the percentage quantile set by the standard.

    • For low voltage, this is typically 95% of measurement values per week for harmonics.

  • The blue area represents the maximum measured value in the selected period.

• Interactive detail view:

  • Clicking a specific harmonic switches from the bar overview to a detailed temporal view.

• Switch between voltage and current harmonics:

  • Via #1, switch between voltage and current view.

  • The display can be adjusted depending on the measurement variable:

6.5.2.2.7.2. Visualisation methods

Voltage:

• Relative to the fundamental wave [%] – Used in normative contexts.

• As absolute value [V] – Used for troubleshooting.

Current:

• Relative to nominal current [%] – Used in IEEE standards.

• Relative to the fundamental wave [%] – Used in IEC standards.

• As absolute value [A] – Used for troubleshooting and filter technologies.

6.5.2.2.7.3. Dynamic settings

Depending on the selected visualisation method, additional settings are shown or hidden to optimise analysis.

6.5.2.2.7.4. Application areas

This analysis is useful for:

• Detecting and evaluating harmonics that may cause disturbances or power quality issues.

• Comparing harmonics over different periods to identify long-term trends.

• Evaluating compliance with standards, e.g., EN 50160 or IEC 61000-2-4.

6.5.2.2.7.5. Limits in analysis

Measuring devices from A. Eberle GmbH provide current limit sets directly to the database. These limit sets form the basis for analyses and reports.

6.5.2.2.7.6. Dynamic adjustment of limits

Since harmonic limits are percentage values based on recorded aggregation levels, alternative limit sets can be applied to existing data in the UI.

Select limit set:

• Via #4, select a specific limit set for analysis.

• In "Reports" > "PQ Standard Templates", limit sets can be customised and managed.

Display limits in visualisation:

• When a limit set is selected under #3, it appears in the graphical view.

• Users can see at a glance whether and to what extent values exceed limits.

Switch between representations:

• With #5 and #6, switch between:

  • Tabular view (with or without limits)

  • Bar chart view.

6.5.2.2.7.7. Application areas for voltage and current harmonic bar chart analysis

• Evaluate power quality: Ensure network parameters remain within standard limits (e.g., EN 50160, IEC 61000-2-4).

• Compare limits: Apply different limit sets to the same data to analyse various criteria.

• Detect limit violations: Identify critical deviations indicating disturbances or network problems.

6.5.2.2.8. Supraharmonic analysis

The "Supraharmonics" analysis shows – depending on device data – the supraharmonics in the context of the selected standard template and time range.

6.5.2.2.8.1. Determination of supraharmonics

Determination follows IEC 61000-4-7 in 200-Hz frequency bands.
In the software, centre frequencies are always shown.

Example of frequency band division:

• Centre frequency:2.3 kHz

• Includes all 5-Hz spectral lines from 2205 Hz to 2400 Hz

Supraharmonics are visualised as bar charts.
The display can be adjusted according to standard requirements and analysis goals.

6.5.2.2.8.2. Functionality of analysis

Supraharmonic analysis has the same functions as harmonic analysis:

• Switch between visualisation types

• Compare with limits

• Tabular or bar chart view

• Zoom and marker function for detailed analysis

6.5.2.2.8.3. Application areas for supraharmonic analysis

• Detect supraharmonics: Investigate higher frequency disturbances in the network.

• Compare with standard limits: Check if measured supraharmonics are within permissible values.

• Identify disturbance sources: Analyse frequency ranges with excessive supraharmonic voltages or currents.

• Optimise filter solutions: Evaluate filter effectiveness to reduce disturbances.

6.5.2.2.9. Interharmonic analysis

Interharmonic analysis investigates voltage and current components not in an integer ratio to the fundamental frequency.

6.5.2.2.9.1. Display of interharmonics

Interharmonics are visualised as bar charts.
Various display types can be selected:

• Relative to the fundamental wave [%]

• As absolute value [V] or [A]

• Compared to defined limits

This analysis is relevant for evaluating harmonic distortions caused by frequency converters, electronic loads, or nonlinear consumers.

6.5.2.2.9.2. Functionality of analysis

Functionality matches harmonic analysis and offers:

• Comparison with limits

• Zoom and marker function for detailed analysis

• Switch between visualisation types in the drill-in process

6.5.2.2.9.3. Application areas for interharmonic analysis

• Detect nonlinear network loads

• Evaluate network quality according to IEC 61000-4-7

• Identify disturbances from frequency converters and inverters

• Evaluate network resonances and unexpected oscillations

6.5.2.2.10. Normative report - Voltage quality (e.g., EN50160)

The normative report summarises all values required for evaluation according to the set standard templates in a clear analysis.

6.5.2.2.10.1. Display and functions

Results are available in two formats:

• Bar chart – normalised to the respective measurement variable

• Tabular report with detailed values

If no dedicated standard template is assigned to the selected device, the template provided by the device is used automatically.
The title is generated from the stored standard template of the device.

6.5.2.2.10.2. Adjustment of measurement variables based on the standard template

Depending on the template, specific measurement variables are included or excluded.

Examples:

• A current EN50160 template contains individual harmonics up to H25 and no supraharmonics.

• The IEC61000-2-2 standard for low voltage considers supraharmonics.

In the example shown, a combined template of EN50160 and IEC61000-2-2 is active, so supraharmonics are also displayed.

6.5.2.2.10.3. Evaluated parameters in the normative report

Various parameters are evaluated according to the set standard template. Each parameter is displayed with its limits.

6.5.2.2.10.4. Frequency (#3)

Network frequency must be between 49.5 Hz and 50.5 Hz according to EN and IEC.

• The blue bar shows the maximum deviation from the upper or lower limit relative to the nominal limit.

• The red bar shows the 99.5-percentile deviation of the frequency.

6.5.2.2.10.5. Voltage (#4)

Network voltage is evaluated relative to the nominal value.

• Limits are based on the standard (e.g., ±10% of nominal voltage according to EN50160).

• Blue marking shows maximum deviations.

• Red marking represents 95% percentile values.

6.5.2.2.10.6. Unbalance (#5)

• Evaluates voltage unbalance between three phases.

• Permissible limits depend on network level (e.g., max. 2% in low voltage).

6.5.2.2.10.7. Long-term flicker (PLT) (#6)

• Measures visual voltage fluctuation (flicker).

• Standard limit is usually PLT ≤ 1 for low voltage networks.

6.5.2.2.10.8. THD (Total Harmonic Distortion) (#7)

• THD evaluates overall harmonic distortion of network voltage.

• Standard limit depends on voltage level, typically max. 8%.

6.5.2.2.10.9. Individual harmonics (maximum values per phase) (#8)

• Shows highest values of individual harmonics.

• Maximum value is displayed

• Each harmonic is evaluated according to limits (e.g., H5 ≤ 6%).

6.5.2.2.10.10. Supraharmonics (maximum value per phase) (#9)

• Shows distortions in the frequency range > 2 kHz.

• Evaluation follows IEC61000-2-2 or other standards.

6.5.2.2.11. Comment box

The comment box is used to add extra information or explanations to analyses created in the dashboard.

6.5.2.2.11.1. Functionality

• Add notes to an analysis.

• Supports simplified Markdown for formatted text.

• Comments can be saved, recalled, or edited later.

6.5.2.2.11.2. Markdown support

For simple formatting, Markdown syntax is used.
Examples:

• Bold Text:**Bold Text** → Bold Text

• Italic:*Italic* → Italic

• Inline code:`Inline code` → Inline code

• link → [link](https://example.com)

• Lists:

• - Item 1

• - Item 2

A full overview of Markdown syntax is available in the Markdown Cheatsheet.

6.5.2.2.11.3. Application areas

• Document specific descriptions and labels within an analysis.

• Notes for other users or future evaluations.

• Structure and comment on analysis results.

6.5.2.2.12. ITIC (CBEMA) curve

The ITIC (CBEMA) curve describes an AC input voltage typically tolerated by most information technology equipment (ITE).

6.5.2.2.12.1. Functionality

• All PQ events within the envelope curve should not cause interruption or damage to connected equipment.

• The display is logarithmic on the X-axis and in percent on the Y-axis relative to the set nominal voltage of the device.

• This allows both medium voltage and low voltage devices to be evaluated in parallel.

6.5.2.2.12.2. Analysis settings

• Multiple measuring points can be defined.

• An individual period can be set.

• Users can select and analyse specific PQ events.

6.5.2.2.12.3. Interactive evaluation

• If a power quality event such as a voltage dip triggers a disturbance record,
  it can be opened and investigated directly by clicking the event.

• This interactive display enables detailed fault analysis and quick problem identification.

6.5.2.2.13. FRT Curve

6.5.2.2.13.1. General Information about the FRT Curve and Application Areas

The FRT curve (Fault Ride Through) illustrates how generation units such as photovoltaic or wind power plants can continue feeding into the grid during voltage dips. WebPQ enables graphical visualisation and analysis of FRT curve compliance according to country-specific grid codes. In "Report → Standard Templates → FRT Curve", the appropriate FRT curve for different countries and grid levels can be selected or defined. Measured voltage events are plotted against the FRT curve, making it easy to see whether the plant meets requirements. The FRT curve is an important tool for grid operators and plant owners to ensure grid stability and compliance with legal and regulatory requirements.

The FRT curve is typically displayed as a percentage of nominal voltage over time. It shows permissible voltage dips and the required duration for which a plant must continue feeding during these dips. The curve starts at 100% of nominal voltage and drops during an event. Depending on the grid code, requirements for depth and duration of the dip vary.

Plotted events are interactive: Clicking an event opens the corresponding disturbance record for detailed analysis.

6.5.2.2.13.2. Adding a Custom FRT Curve

• In "Reports", go to "Standard Templates" and select "+Add"

• Choose "FRT Curve" as the template type

• Assign a name to the template, e.g., "My FRT curve"

• Enter a time point (#1) and a voltage level (#2) to define curve coordinates

• Use "+" to add another coordinate (#3)

• Use the "bin" icon to remove a coordinate (#4)

• Use "+" to add new curves to the chart (+7)

• Save the FRT curve (#6) to store it for future analyses

• Delete the entire FRT curve using "Delete" (#5)

6.5.2.2.13.3. Applying the FRT Curve in Analysis

• Select analysis type "FRT Curve" in the Analysis Cockpit under "Analysis Type"#1

• Choose measurement points and analysis period #2 and #3

• Select the created FRT curve from the template list #4

• Click Apply to start analysis and plot events against the FRT curve #5 ==> Events are displayed in the diagram, showing depth and duration of voltage dips

• Click an event to open the associated disturbance record for detailed analysis #6

• Save the analysis in the Dashboard for later access #7

6.5.2.2.14. Event matrix

The PQ event matrix is based on EN50160 and correctly assigns power quality events according to the standard by depth and duration.

6.5.2.2.14.1. Functionality

• For medium and high voltage devices, only line-to-line PQ events (dips and swells) are considered.

• For low voltage measurements, phase-to-earth PQ events are used.

• According to IEC61000-4-30, these are always network events with a certain depth and duration.

6.5.2.2.14.2. Standard-dependent display

Depending on the regional standard, different tabular display forms exist:

• In South Africa, NRS048 applies.

• In the Netherlands, Netcode is used.

The correct assignment and display can be selected via the standard template. Only the correct template needs to be selected.

6.5.2.2.14.3. Flexibility of analysis

• The analysis period can be freely chosen.

• The analysis can be applied to one or more measuring points.

Example: Netcode

Example: NRS048

6.5.2.2.15. Live values

All directly connected device classes of types PQI-DA smart, PQI-DE or PQI-LV are live retrievable via direct data connection using TCP/IP streaming.

Measurement value display can be done in various analysis forms with a good data connection.

Important notes

⚠ High data consumption: Displaying live values generates very high data transfer!

⚠ Prioritisation of live data:

• Live values have lower priority than continuous readout of disturbance records and long-term data.

• This can cause delays in display.

• Live values do not replace SCADA protocols such as IEC60870-5-104 or IEC61850, which offer real-time capability.

6.5.2.2.15.1. Live oscilloscope image

The oscilloscope image is fully downloaded from the device and displayed in regular quasi-stationary states.

6.5.2.2.15.2. Live measurement values

This analysis type is ideal for parallel comparison of multiple measuring points.

• Any number of measuring points can be displayed with power in 1s measurement values or other data classes.

6.5.2.2.15.3. Live time series

This analysis type is well suited to quickly visualise reactions at measuring points to switching actions or direct influences.

• All measurement values available in streaming can be displayed live from multiple measuring points in parallel.

• The maximum time frame determines how long data is retained in the display.

6.5.2.2.15.4. Live harmonics

This analysis type shows all harmonics relative to the fundamental wave live.

• Blue bar: Maximum value since streaming started

• Red bar: Current value

• Clicking a harmonic switches to the live time series of that harmonic.

• The same settings as in historical harmonics analysis are possible:

  • Switch between current and voltage display

  • Various display types such as relative to the fundamental wave or absolute value can be selected.

6.5.2.2.15.5. Live interharmonics and harmonics

This analysis type works identically to live harmonics analysis:

• Blue bar: Maximum value since streaming started

• Red bar: Current value

• Clicking a harmonic leads to the live time series of that harmonic.

• Switch between current and voltage as well as various display types.

6.5.2.2.15.6. Live vector diagram

The vector diagram (phasor diagram) displays voltage and current phase angles in a three-phase system.

It is especially useful for checking device connections, as wiring errors or unsuitable consumer characteristics can be detected.

What does the vector diagram show?

• Voltages and currents are displayed as vectors (phasors).

• Each vector shows the amplitude (arrow length) and phase angle (arrow angle) of an electrical quantity.

• Vectors are displayed for phase-to-phase (L-L) and phase-to-neutral (L-N).

How to interpret the vector diagram?

1. Phase shift between voltage and current
The phase angle between voltage and current indicates the load type:

• Inductive load (e.g., motor, transformer)

  • Current lags behind voltage.

  • Typical for inductive consumers like motors or transformers.

  • Vector diagram: Current vector lags behind voltage vector.

• Capacitive load (e.g., capacitor banks, long cables)

  • Current leads voltage.

  • Typical for capacitive consumers like capacitor banks for reactive power compensation.

  • Vector diagram: Current vector leads voltage vector.

• Resistive load (e.g., heating resistors)

  • Current is in phase with voltage.

  • Typical for heating devices or incandescent lamps.

  • Vector diagram: Current and voltage vectors point in the same direction.

2. Detect wiring or connection errors

• Reversed phase sequence

  • If phases are connected incorrectly, vectors appear in an unusual arrangement.

  • This can cause problems, e.g., motor rotation direction errors.

• Missing or incorrect neutral conductor

  • An incorrect or missing neutral can cause asymmetries in voltages and currents.

Application areas of the live vector diagram

• Check phase angle of voltages and currents

• Identify load types (inductive, capacitive, resistive)

• Diagnose wiring errors or rotation direction problems

• Check network quality and asymmetries

6.5.2.2.16. Analysis evaluation

Analysis evaluation offers various options for detailed examination of analysed measurement values.

6.5.2.2.16.1. Display marker values (#1)

• Markers can be set in various analysis types.

• Markers allow targeted examination of individual measurement points.

• In analysis evaluation, marker values are clearly displayed.

6.5.2.2.16.2. Display extreme values (#2)

• Extreme values of the selected measurement series are displayed:

  • Minimum values

  • Maximum values

  • Average values

• This helps to quickly identify key measurement deviations.

6.5.2.2.16.3. Analyse limit values (#3)

• Limit values stored in measuring devices can be viewed.

• This allows a quick check if values are within permissible limits.

• For disturbance records, trigger conditions are displayed here.

6.5.2.2.16.4. Application areas

• Analyse voltage fluctuations and deviations in real-time.

• Identify critical values for quick fault diagnosis.

• Compare measured values with standard specifications stored in the system.

6.5.2.2.17. Analysis layout

In "Analysis Layout", grouping methods #1, scaling #2, and colours #3 of measurement values can be defined.

Using "Group by", measurement values can be displayed individually:

• Each value is shown in a separate level-time diagram.

• Group by device and data type (unit).

• Group across multiple devices by data type in different diagrams.

Using "Settings for device names"#4, device names can be set via tags and categories in analyses.

In the screenshot, an example of a local network station with feeder display. Feeder names are assigned to a device via category "device"#5.
Feeders are displayed and labelled in the diagram via "assigned slave name"#6.

6.5.2.2.18. Widget settings

Under "Widget settings", you can adjust the title and size of the widget.
These settings are relevant when the analysis is transferred to the dashboard and saved permanently.

6.5.3. Analyze Device

This view offers detailed and pre-configured analysis functions for individual measuring devices to specifically access their data.

The view is divided into three areas:

• Power Quality Report#1

• Historical Data#2

• Live Data#3

As a user, you have the option to switch the measuring device via #4 and switch between the data weekly.

The Power Quality Report consists of four types of analysis:

1. Summary of the necessary measured variables according to the set norm template in a clear bar chart based on the limit values.

2. Explanation of the EN50160-relevant measured variables.

3. List of disturbances recorded by the measuring device.

4. List of PQ events in the EN50160 matrix.

By clicking on the bars, the drill-in procedure opens to display the measurement data in detail.

In the "Analyse Device"#2 tab, there are pre-configured level-time diagrams, histograms, and the ITIC curve.

In the Live Data#3 area, the user has the option to visualize the live data of the device if the selected measuring device is directly connected.

6.5.4. Analysis > Dashboard

The Analysis Dashboard, which can be found in the navigation bar on the left side under "Analysis > Dashboard" #1, is used for the permanent storage of analyses in widgets that were created via the Analysis Cockpit. Using the Add analysis function #2, it is possible to open the Analysis Cockpit, define an individual analysis, and transfer it to the Analysis Dashboard.

With the "Tab settings" function #3, the time period for all analyses stored in the tab can be changed. For example, in one widget, you can select performance, and in another widget, you can select maximum currents, voltages, and THD (Total Harmonic Distortion). To compare the dependencies of the variables with each other weekly, the time period for all widgets can be adjusted via the Tab Settings. Click on "Tab Settings" and change the time range for the tab and all analyses contained within it.

The "Save Tab" function #4 saves settings such as window sizes, zoom levels, markers, etc. If changes have been made, the user will be prompted to save or discard the changes when leaving the Analysis Dashboard. Unsaved tabs are marked with a "*", making them easy to find again to complete the saving process.

With the #5 function, tabs can be duplicated and saved under a new name. The #6 function deletes the tab directly. However, if a tab is closed via the X next to the tab name, it is not deleted but can be displayed again at any time via the tab menu #7 in the tab bar.

The Tab Menu opens the tab menu. In the "Load Saved Tabs" area, all tabs can be transferred back to the interface from the background storage. To create a new tab, click on "+ Create New". To save the tab copied using function #5 into a new one, use the "Add Tab" function and paste the content into the empty field using CTRL+V.

6.5.4.1. Group Dashboards

In addition to personal dashboard tabs, WebPQ also supports shared Group Dashboards. The page is available in the left navigation under Analysis > Group Dashboards and shows the dashboard tabs of all groups the current user belongs to.

Create a Group Dashboard

Group dashboards are created by transferring an already saved personal dashboard tab:

1. Open Analysis > Dashboard.

2. Save the tab first. Unsaved tabs cannot be transferred.

3. Click Transfer to Group Dashboards in the tab toolbar.

4. Select the target group.

5. Confirm the transfer.

After a successful transfer, the tab is removed from the personal dashboard and becomes a shared group dashboard tab.

Open and find Group Dashboard tabs

• The Analysis > Group Dashboards page loads all tabs that are visible to the current user through group membership.

• The tab title includes the group name, which helps distinguish tabs with the same business purpose in different groups.

• If many shared tabs exist, the page shows additional discovery controls with a Group filter and a Search field.

• Search matches the group name and the tab title.

Edit shared tabs

Once a shared tab is opened, it behaves like a normal analysis dashboard tab:

• analyses can be added or adjusted,

• tab-wide settings can be changed,

• the current state must be saved explicitly,

• and deleting the tab removes the shared group tab.

This makes group dashboards suitable for shared team views that should stay identical for all members of the same group.

Conflicts while saving

If another user saves the same group dashboard tab before your changes are stored, WebPQ detects the version conflict and offers three options:

• Reload latest discards the local state and loads the newest saved version.

• Keep local copy keeps your current local changes open so you can review them against the latest saved version.

• Overwrite saves your current local state immediately as the new shared version.

The dialog also shows which user last edited the tab and when the latest change was saved.

Notes

• The transfer action is only available for users who are members of at least one group in the current tenant.

• Group dashboards are intended for collaborative reuse. Personal scratch tabs should remain in Analysis > Dashboard until they are ready to be shared.

6.6. Time Settings in Analysis

The time setting#1 in the analysis allows the user to open a dialog window for configuring the analysis period and to define extensive time options relevant for the analysis of equidistant measurement values.

In general, four different modes are available:

• Absolute period:
  In this mode, the user can specify a fixed start and end time for the analysis. This is especially useful when a clearly defined time range needs to be examined, such as analyzing measurement data within a specific project or event. Selection is made via a calendar and time dialog, allowing precise input. This enables targeted analysis and comparison of data from the desired time window.

• Relative period to current time:
  Here, the user can define a period that dynamically relates to the current time, such as “the last 24 hours” or “the last 7 days.” This mode is particularly practical for ongoing analysis of current events and is ideal for dashboards that should always display the latest data. Using the software’s automation feature, the analysis can be configured to automatically evaluate and report on the current period. This enables dynamic and continuous reporting without manual adjustment of the time range.

• Relative period to last measurement value:
  With this option, the user can set a period based on the last available measurement value. This is helpful when the analysis should always be based on the most recent data, regardless of when it was recorded. It is especially beneficial for measurement series that are not recorded continuously but at irregular intervals. For example, analyses can always be performed retrospectively from the last measurement value for a specified period.

• Relative to end:
  In this mode, the period is set relative to the end of the available data. This means the analysis focuses on the last segment of the measurement data, regardless of the current time or last measurement value. This is particularly useful for reviewing data history, such as identifying trends or changes in the last section of data. The user can flexibly determine how far back the analysis should reach, starting from the end of the data series.

6.7. Reporting - PQ Standard Templates

In the menu under "Templates & Tasks >> Reporting Templates", templates for evaluating various power quality parameters are available. These templates are updated and expanded with each software update to stay current. Additionally, you can create your own templates and save them in the list or base them on an existing template.

Each template can be applied to one or more devices to generate reports with the corresponding threshold values. You can also work with threshold sets in analyses and use them as templates, or use threshold sets for event-based monitoring.

1. Using Templates in Analyses and Event-Based Monitoring

Currently, the following standards and threshold sets are supported:

• Customer-specific thresholds – measurement monitoring

• Power quality standards such as EN50160 for low, medium, and high voltage, or IEC61000-2-2

• Fault Ride Through (FRT) curves – for evaluating feed-in systems

To view the thresholds of a template, simply click on the corresponding name of the standard or threshold template. A detail window will open with the relevant information.

Using the free text search, you can search for standards or categories such as countries or continents.

Standard templates can be applied directly to devices and individually adapted to customer-specific requirements.

6.7.1. Adding Custom Threshold Sets

Clicking "+ Add" #1 opens a wizard for adding or configuring your own template. You can select the following modes:

• Copy: Select and copy an existing template

• Customer-specific threshold / measurement monitoring: Create a completely new template for measurement monitoring or as a fully custom template. For example, you can create a threshold set for any parameter. Use cases include monitoring individual harmonics, current values, or other analog measurements such as maximum values for local substations and their fuse sizes in current or power.

• FRT Curves: Create your own FRT curves, e.g., for evaluating feed-in systems.

After selecting the mode, you enter the template name and description in the next step #3.

Explanation and usage of the individual sections:

6.8. Power Quality Standards (limits uharm)

This standard template includes the most common power quality parameters and their thresholds. It can be applied to all devices that record power quality data. This is also possible afterwards, even if the measuring device was previously operated with another template. The template can also be used in analyses to display the thresholds in the charts.

The template has the following parameters in the General section:

• Harmonics evaluation: Set which harmonics should be included in the report. Either up to the 25th, 40th, or 50th harmonic.

• Supraharmonics evaluation: Set whether supraharmonics should be included in the report (2-9kHz) or beyond.

• PQ Events: Specify which standard to use for ITIC output

  • EN50160

  • NRS048

  • Netcode

• Flagged Events: Set whether flagged measurements should be included in the report or excluded.

The current reporting template also affects the generated print output:

• The selected harmonics limit controls how many harmonics appear in the report tables and charts.

• Harmonics and supraharmonics sections that are not enabled by the template are omitted from the generated report.

• WebPQ applies the current pagination and page-break handling again in the PDF output, so page numbering and report splits remain consistent.

For report branding and page format, WebPQ additionally uses the report settings of the current tenant:

• A tenant-specific report logo can be stored for PDF generation.

• The page orientation can be configured as portrait, landscape, or inherit from the parent tenant.

• These settings are resolved before report generation and are used for both manual prints and automated reports.

6.9. Fault Ride Through (FRT) Curves ()

Configuration in the "Analyses" section FRT Curves.

6.10. Customer-Specific Thresholds – Measurement Monitoring

This feature can be used to work with customer-specific thresholds in analyses or event-based monitoring.

The following parameters can be set:

Name sets the template name to find it in analyses and event-based monitoring of automation tasks. Unit sets the unit for the template, e.g., V, A, kW, kVAr, Hz, etc., to which the threshold refers. Data classes sets the data class for the template, e.g., "Voltage", "Current", "Power", etc., to facilitate assignment of measurements. Multiple data classes can be selected that match the chosen unit. Devices sets which devices the template should be available for. Multiple devices can be selected. Minimum lower threshold for triggering Maximum upper threshold for triggering Absolute sets whether the threshold is considered as an absolute value or with sign Hysteresis sets how far the value must fall below or exceed the defined threshold for retriggering

Click Save to add the template to the list of available templates and apply it to the relevant devices. Click Remove to delete the template.

Thresholds can then be used in analyses – see Thresholds in Analyses – and for event-based monitoring – see Automation Tasks.

Example Use Case:

As a grid operator, I want to monitor local substations and the feeders of a grid area for compliance with EN50160, and also be notified by the system when the current reaches 90% of the NH fuse rating.

The procedure is as follows:

1. Add several customer-specific threshold templates – e.g., with the name of the fuse size and the definition of the current value at 90% of the NH fuse

• Name: NH Fuse 63A – 90%

• Unit: A

• Data class: Current

• Devices: Select all substations or feeders with an NH Fuse 63A

• Minimum: empty

• Maximum: 56.7 (63A * 0.9)

• Absolute: yes

• Hysteresis: 2 (i.e., when the current drops to 54.7A, the trigger is reset)

Info: Customer-specific thresholds can also be added in the device settings under the "Thresholds" tab. This allows the template to be applied directly to the device, rather than via device configuration. This is especially useful if the template should only apply to a single device or if you want to control which devices use the template.

1. Create a dashboard for automated reporting with custom analyses and time selection

• Go to Dashboards >> Add New Analysis

• Select the desired analyses and configure them with a calculated period (e.g., last 7 days, last month, etc.)

• Add the analyses to a new dashboard

• Save the dashboard with a meaningful name

1. Add an automated report in Automation Tasks as event-based monitoring

• Go to Templates & Tasks >> Add New Task

• Assign a meaningful name to the task and select the task type "Report"

• Select the desired devices or device groups to apply the task to

• Select the previously created dashboard and configure the recipients

• Set triggers in the "Thresholds" section to be notified when defined thresholds are exceeded

• Save and activate the task to start automated reporting and notifications

1. Result

If the defined thresholds for one or more devices are exceeded, the recipient automatically receives a notification with the freely configured dashboard as a PDF via email.

6.10.1. Printed Report Behavior

Generated reports and print views are prepared server-side. WebPQ waits until the included charts and report elements have finished loading before the PDF is created. During that preparation, the report page shows a loading state instead of exporting a partial page.

For EN-style table reports, WebPQ uses a dedicated print mode:

• interactive table paging is disabled for the print output,

• the print layout applies explicit page breaks and page numbering,

• dashboard analyses are printed in their saved layout order.

6.11. Reporting - Automation & Tasks

A central feature of WebPQ is the automated, targeted provision of information for various users or applications. For this purpose, the software has a module for task automation.

A key advantage of the software is its ability to regularly and automatically generate compliance reports, such as those according to EN50160 or VDE-AR user guidelines. Additionally, the software can automatically inform affected customers in the event of network disturbances. In many use cases, the software solution also requires the automatic storage and export of measurement data in open file formats. All these settings and tasks can be configured and managed in the "Tasks" section.

The main tasks enabled by the software's automation functions are listed below:

1. Fault records This module allows automatic alarm notifications to be sent or fault records to be stored, for example, in the event of power grid disturbances. Notifications can be sent via email and include all relevant information about the disturbances. This ensures that users or system administrators are directly and efficiently informed, enabling a quick response to network issues.

2. Reports This function allows standard reports to be created and sent regularly and automatically. Examples include reports according to the EN50160 standard or other industry standards. These reports can be created in various formats, such as PDF. Additionally, the tabs created in the Analysis Dashboard can be used as a basis for automated reports. This enables regular, standardized reporting without manual intervention.

3. Export The export module allows the automatic and regular export of measurement data for one or more devices. The exported data can be stored in open file formats needed for further analysis or archiving. This function ensures that all relevant measurement data is always available in a structured and accessible format without requiring manual exports.

All these tasks and automation processes can be centrally managed in the "Automation tasks" section of the software, allowing for easy configuration and regular execution of automated processes.

6.11.1. Backup and Download of Generated Data

The complete reports and exports created in the automation tasks are stored both in the file system of the WebPQ server and in the specified folders that can be configured in the WebPQ backend. More information about the backend can be found at Link. These data can be retrieved at any time.

Additionally, the created data is also available in the "Import / Export" section under "Export" in the client and can be downloaded directly via the browser.

6.11.2. Activation / Deactivation of Tasks

Each task can be activated or deactivated as needed. This allows flexible control over whether a task should be executed or not.

6.11.3. Creating Tasks

By clicking the "Add Task" button, the user can create new tasks. In the first step, the task name and a description must be specified under which the task will be saved. These details are necessary to uniquely identify and correctly assign the task later.

In the next step, the type of task is determined. This type defines how the task will be executed and which specific parameters need to be configured.

Depending on the task type, the affected measurement points can be selected not only through individual devices, but also through tags and tag categories. This makes it possible to define automation tasks for logical device groups without selecting every device individually.

A typical example is a recurring report for all devices with the "highvoltage" tag. If the automation task is defined through this tag, it will automatically also apply to newly added devices as soon as they are assigned the "highvoltage" tag as well. In that case, the report does not need to be adjusted manually just because additional matching devices were added.

The practical benefit is that existing jobs do not need to be parameterized again for every newly created device. As soon as a new device is assigned to the selected tag or tag category, it is implicitly included in all matching automation jobs of this section.

6.11.3.1. Creating a Disturbance Record Task

A commonly used task is the disturbance record. This task allows for automatic notification or logging in the event of a disturbance. The disturbance record is usually sent as an email to defined recipients as soon as a network disturbance is detected. This ensures that responsible persons are immediately informed, allowing for a quick response.

With #1, the task name is specified. Under #2, settings can be made regarding which devices, tags, or tag categories are eligible for sending and which reporting format (e.g., PDF or COMTRADE) should be chosen. Additionally, the type of record can be set in the settings, such as oscillographic or TRMS record (True Root Mean Square), which affects the type of measurement data representation.

The same advantage applies here: if the selection is based on tags or tag categories, newly created and correspondingly assigned devices are included automatically. Existing disturbance-record jobs therefore do not need per-device follow-up parameterization.

In the email settings, the recipients, subject, and formats must be specified. It is also possible to include variables to create individual subject lines or email texts. This function offers high flexibility as the content of the emails can be tailored to specific requirements and circumstances.

In the time settings section, specific parameters can be set, such as how far back the disturbance record should be considered. This allows defining the period in which disturbances can be processed or analyzed retrospectively and determining how long historical data should be sent.

6.11.3.2. Creating a Report Task

Using the reporting templates and the analysis dashboard, the WebPQ software offers the ability to automatically generate PDF reports according to standards from over 65 different templates. These reports can be created for device groups or individual devices.

In the automation task settings, the affected devices, tags, or tag categories as well as the report template must be selected. These templates can be customized in the reporting editor either according to standard specifications or customer-specific requirements.

This is especially useful in growing installations: when a report is defined through tags or tag categories, newly added devices become part of the existing job automatically after they are assigned accordingly, without reopening and extending the report configuration.

For more customized reports, the software offers the ability to create free reports from various types of analysis using the individually configurable tabs in the analysis dashboard. To do this, simply select the desired tab under point #2.

In the time settings section, specific parameters can be set, such as frequency, day of the week, and time at which the regular report should be generated. This function enables complete automation and scheduling of report generation without manual intervention.

For automated report emails, WebPQ supports placeholders that are filled during task execution. Depending on the task and the available device metadata, placeholders can insert values such as the report ID, report description, station ID, group, plant, field, device, recorder information, trigger time, or generated file name into the subject or body text.

Automated reports use the same generation pipeline as manual print jobs. Therefore:

• tenant-specific report logo and page orientation are applied automatically,

• the report is rendered only after the required report elements finished loading,

• the generated output can later be checked through the regular Import / Export > Export overview when the task stores files there.

6.11.3.3. Creating an Export Task

Unlike reports, the export task mainly differs in the settings. While the selection of affected measurement points is similar to reports and can also be done through devices, tags, or tag categories, the export format must also be selected here. The export allows measurement data to be stored in various formats.

Export tasks benefit from the same pattern. If the selection is made through tags or tag categories instead of single devices, newly added devices are picked up automatically as soon as they belong to the configured group.

Currently, the following export formats are available:

6.11.3.3.1. CSV

For CSV export, after selecting the format, the data class or data points to be exported must be specified. This provides the flexibility to export only the relevant data in a structured CSV format.

6.11.3.3.2. NeQual

For NeQual export, the number of weeks, the country, and the start time of the export period must be specified. These settings allow data to be exported for specific periods and geographical regions.

After an automation task starts an export, the generated file also appears in the regular Import / Export > Export overview. This is where completed files can be downloaded and failed exports can be checked together with their error text.

6.12. Import of Measurement Data

6.12.1. General Information

To import measurement data into the WebPQ software, various options are available. The import can be performed either manually via the client or automatically through direct connection via TCP/IP.

A manual import is used when there is no direct connection to the measuring device or if such a connection is not desired. Additionally, measurement data from other systems or from end customers can be imported this way.

6.12.2. Manual Import

In the Import / Export >> Import section, you will find the function for manual import. This allows you to upload data that has been exported, for example, via SD card, WebServer, or WinPQ Lite.

This page describes the import of measurement data. To transfer devices that already exist in WinPQ into WebPQ, use Administration > Devices > + Import from WinPQ instead. The device import workflow is described in Devices under Importing Devices From WinPQ.

6.12.2.1. Importing PQ-Box Data

To import PQ-Box data, first select the PQ-Box import type in the import wizard. After that, choose the directory that contains the exported files.

During PQ-Box import, WebPQ processes supported .pqf measurement files and assigns their contents to the data classes used in WebPQ. Sidecar files such as parameter, info, or comment files may be present in the selected directory. Unsupported log files are not imported as measurement data.

Imported cyclic data and recorder data use the same data-class names as PQI device data. This means PQ-Box data is available consistently after import in analyses, exports, reports, and synchronization views.

6.12.2.2. Importing COMTRADE Data

To import COMTRADE data, select the Comtrade import type in the import wizard. This option is visible only when the COMTRADE import add-on is enabled in the license.

Each COMTRADE import group must contain at least a .cfg file and a matching .dat file. Optional .hdr, .inf, and .cff files are also considered when they belong to the same COMTRADE group.

On the file side, WebPQ uses the Rec-ID from the COMTRADE metadata, more precisely the identNumberOrDeviceName field, as the identifying value. This value can be used in the wizard to group related files. The actual assignment inside WebPQ, however, is not based only on this identifier. It is made in the mapping step by assigning the import to a specific COMTRADE device.

In the mapping step, WebPQ shows the channels from the configuration file. These channels must be assigned to a COMTRADE device and to the target channels in WebPQ. If no suitable COMTRADE device exists yet, create it directly from the import dialog or beforehand in device management.

If a channel mapping has already been stored for that COMTRADE device, WebPQ can reuse that mapping in later imports with matching channel names. In this context, the Rec-ID is mainly used for grouping and recognition of import files, not as a complete replacement for the device selection in the wizard.

Missing .cfg/.dat pairs, unreadable configuration files, or files with too many analog channels are shown in the wizard before upload. Warnings and import errors from the actual import run are also written to the import log.

6.12.2.3. Import Process

The manual import is carried out in several steps:

6.12.2.4. Step 1: Start the Import Wizard

• Click on "Import data for devices" (#1).

• A wizard will guide you through the import process.

6.12.2.5. Step 1a: Select the Import Type

Select the import type that matches the source files. For PQ-Box imports, select PQ-Box before choosing the files from the SD card or export directory.

For COMTRADE imports, select Comtrade. This option is visible only when the COMTRADE import add-on is enabled in the license.

6.12.2.6. Step 2: Select Directory with Measurement Data

• Click on "Browse" to select the directory with the measurement data.

• Confirm the security message regarding the trustworthiness of the application.

Note: You must agree to the security message!

6.12.2.7. Step 3: Assign Measuring Devices

• Files must be assigned to the respective devices.

• Known devices are automatically recognized by the serial number.

• Manual assignments or changes can be made in the table.

• If the device does not yet exist, it can be newly created as an "Offline Device".

• For PQ-Box imports, WebPQ reads supported .pqf measurement files and assigns their content to WebPQ data classes. Sidecar files such as parameter, info, or comment files can be part of the selected directory, but unsupported log files are not imported as measurement data.

• PQ-Box cyclic and recorder files are displayed with the same data-class names that are used for PQI devices. This means imported PQ-Box data appears together with other device data in analyses, exports, reports, and synchronization status views.

• For COMTRADE imports, each import group must contain a .cfg file and a matching .dat file. Optional .hdr, .inf, and .cff files are included when they belong to the same COMTRADE group.

• The Rec-ID contained in the file (identNumberOrDeviceName) can be used to group COMTRADE files. The assignment to the WebPQ device is then made in the wizard through a COMTRADE device and its channel mapping.

• The COMTRADE mapping step shows the channels from the configuration file. Assign the channels to a COMTRADE device and to the target WebPQ channels. The wizard can group COMTRADE files by directory, Rec-ID, or equal channel structure.

• If no suitable COMTRADE device exists yet, create one from the mapping step or in Administration > Devices before completing the import. Check the device time zone and channel mapping carefully, because they determine the timestamps and channel names used after import.

• Missing .cfg/.dat pairs, unreadable configuration files, and files with too many analog channels are shown in the wizard before upload. Import warnings and database-side messages are written to the import log after the import job has run.

6.12.2.8. Step 4: Upload and Import

• The data is uploaded to the server.

• Subsequently, the automatic import into the database takes place.

6.12.2.9. Step 5: Progress and Verification

• The progress of the import can be viewed in the Import / Export >> Import section.

• A LOG file is created for each import process to trace the process.

6.13. Export of Measurement Data

6.13.1. General

The WebPQ software offers both manual and automated export options for measurement data.

In the Import / Export > Export section, you can:

• Create manual exports,

• View and download already created exports,

• Manage exports from the Automatic Export.

Exports are created as background jobs on the server. This means the export can continue even when larger data ranges take longer to prepare, and the result becomes available in the export overview as soon as processing finishes.

6.13.2. Manual Creation of an Export

A manual export is carried out in several steps:

6.13.2.1. Step 1: Open Export Dialog

• Click on "New Exports" to open the export creation dialog.

6.13.2.2. Step 2: Assign Export Name

• Define a meaningful export name for later identification.

6.13.2.3. Step 3: Choose Export Format

• Select the desired export format:

  • CSV (Text-based table format)

  • Nequal(license required)

  • PQDIF(Power Quality Data Interchange Format: IEEE 1159)

Tip: For the formats PDF and Comtrade, other methods for creating reports and exports are available. For more information, see Export via Burgermenue.

6.13.2.4. Step 4: Select Devices

• Select the measuring devices for which the export should be created.

6.13.2.5. Step 5: Define Time Period

• Set the desired export time period.

6.13.2.6. Step 6: Determine Data Classes

• Select the relevant data classes for the export.

Depending on the selected export type, additional validation rules apply:

• CSV and PQDIF require at least one device, at least one data class, and a valid time range.

• The end date must not lie in the future.

• The selected time period must have a positive duration.

• NeQual additionally requires the country and the permitted number of weeks for that country.

As long as the parameter set is incomplete or invalid, the confirmation button remains disabled.

6.13.3. Export Process and Management

After all settings have been made, the export is started on the server by confirming with "OK".

While exports are in status Pending or In Progress, the overview refreshes automatically more frequently so that progress changes and completed downloads appear without a manual reload.

6.13.3.1. Export Overview and Download

• The status of all exports is displayed in a table.

• Historical exports are also available in the overview.

• After the export is completed, the data can be downloaded via the download button.

The overview contains both manually created exports and files created by automation tasks. Each completed export is provided as a ZIP file, even if the selected export format inside that ZIP is CSV, PQDIF, or NeQual.

The status column shows the current processing state:

• Pending: The export job has been created and is waiting to run.

• In Progress: WebPQ is currently processing the export and shows a progress bar.

• Completed: The ZIP file is ready and can be downloaded directly.

• Failed: The export did not finish successfully. The table provides the failure message in the status field.

For supported formats, the New from row action can be used to open a new export dialog with the parameters of an existing export already prefilled. This is useful for repeated exports with the same scope.

Finished or obsolete exports can be removed from the table again. This deletes the export entry and the associated server-side export data for the selected rows.

If an export fails, WebPQ also writes a corresponding Syslog error entry. This makes failed exports traceable in operational monitoring in addition to the error text shown in the export table.

6.13.3.2. Note on Server Configuration

• The storage of exports is configured on the server-side.

• It is recommended to choose a directory with sufficient storage space.

• Regular backups of export data are recommended to avoid data loss.

6.14. Data Synchronization

6.14.1. General

With data synchronization, the measurement data is automatically written to a file when it is stored in the database. This file can then be read by another WebPQ instance to synchronize the data.

It is possible to perform either a one-time synchronization or to set up a regular synchronization so that the data is synchronized continuously.

Measurement data backups can also be created in this way. However, it is important to note that synchronizing measurement data should not be considered a replacement for a full database backup, because it only secures the measurement data and not the entire database structure or other important information.

6.14.2. Technical Requirements

For data synchronization to work, the following technical requirements must be met:

• Both WebPQ instances must have access to the same file system. File locking is not required.

• The source system requires write permissions for the directory in which the synchronization files are created.

• The target system requires read permissions for the directory in which the synchronization files are created.

• To prevent the synchronization files from overflowing, sufficient storage space should be available.

• The required storage space varies depending on the amount of synchronized data and the selected data classes. As an upper limit, up to 7.5 GB per day per device and data class can be expected when the highest resolution is used.

• In addition, approximately 960 files are created per day for each device and data class. This should be taken into account when planning storage capacity.

• Old files are currently not deleted automatically. Therefore, it is important to check regularly whether enough storage space is available and, if necessary, delete old files with a cron job. Once the target system has read the files, they can be deleted.

6.14.3. Setting Up Synchronization

Synchronization is configured via the administration interface of the WebPQ instance. The settings for export and import can be configured there separately. It is also possible to filter the selection of devices using a regular expression so that, for example, only specific devices are synchronized.

To make selecting the devices to be synchronized easier, regular expressions can be used. For example, the regular expression .* can be used to synchronize all devices, or Plant.* can be used to synchronize only devices whose name begins with "Plant".

Attention: The screenshot is provided only to illustrate the synchronization settings. Exporting and importing data at the same time on the same WebPQ instance is not possible, because the devices are detected there as already existing and the synchronization does not start. Therefore, it is important to set up synchronization on two different WebPQ instances in order to ensure that the functionality works correctly.

6.14.4. Licensing

Data synchronization is a special feature that is generally not included in the standard license. It requires a separate license because it involves additional resources and maintenance effort. Measurement data synchronization will only start if a valid license for this feature is available. Without the corresponding license, the synchronization processes will not start and no data will be synchronized.

6.14.5. Synchronization Status

The synchronization status on the source system can be monitored using log files that contain information about possible errors. If export is not possible - for example because the file system is full - this is recorded in the log file as a syslog message. It is therefore important to check the log files regularly in order to ensure that the synchronization works smoothly and to detect possible problems at an early stage.

On the target system, the synchronization status can be viewed on the "Device Synchronization" page in the "Import / Export" section. The current synchronization status is displayed there, including information about the last synchronized files and possible errors. Further details on the synchronization status can be found in the documentation under Synchronization Status. Syslog messages are also logged on the target system if import is not possible - for example because the files cannot be read or because the database has changed and is no longer in the same state as during export. Therefore, it is also important on the target system to check the log files regularly in order to ensure that synchronization works smoothly and to detect possible problems at an early stage.

The status page is refreshed regularly. It shows whether synchronization is active for a device, whether errors are present, when the latest synchronized data point arrived, and whether files are currently still waiting in the upload queue.

6.14.6. Synchronization Details

Export takes place at the moment when the data is written to the database. The export is started only after the read operation from the device has finished, to ensure that the data can be written to the file completely and consistently.

The import process scans all existing files in the import directory every 15 minutes in order to detect new devices or data classes. As soon as a device-data-class combination is known, the files are read directly and checked every 5 seconds to determine whether the next expected file is available. As soon as the next file is found and complete, it is read and the data is written to the database.

All devices created by means of device synchronization automatically receive the tag "syncimport" so that they can be distinguished from other devices. However, this tag can be removed or changed without any problems if it is not needed.

6.14.7. FAQ and Troubleshooting

6.14.7.1. What can I do if no data arrives in the IT system?

Check the following points in order:

1. Verify that data synchronization is licensed on the source and target tenant. Without the DataSync feature, export or import remains disabled and no files are processed.

2. Verify that the configured export folder on the source system and the import folder on the target system really exist and are directories.

3. Verify that the source system has write permissions and the target system has read permissions for the shared folders.

4. Verify that the source and target systems are two different WebPQ instances. Import and export on the same instance is not the supported setup for this workflow.

5. Verify that the configured device filter regular expression actually matches the expected device names.

6. Check the Device Synchronization page on the target system and the Syslog on both systems.

6.14.7.2. What should I look for in the Device Synchronization page?

The page gives the fastest overview of whether the target system is still catching up or whether it is blocked:

• Active indicates whether synchronization is currently running for the device.

• Errors shows whether the device has a current synchronization problem.

• Latest synced data point shows how recent the imported data is.

• A yellow or red latest-data indicator means the imported data is older than expected.

• The queue banner above the table shows how many files are currently being processed and how many are still waiting.

If the queue warning stays visible for a long time, this points to a backlog in database upload processing on the target system.

6.14.7.3. Which errors are reported directly by WebPQ?

The code paths for synchronization write explicit operational messages for several important failure cases:

• The configured export folder is not a directory: export is disabled.

• The configured import folder is not a directory: import is disabled.

• The temporary folder for sync export cannot be created.

• A file cannot be written on the source system.

• A sync file cannot be imported on the target system.

• The DataSync license feature is missing for export or import.

These messages are written to the Syslog and should be checked first when synchronization stops unexpectedly.

6.14.7.4. What if the target system shows an error for a data class?

Open the device in Import / Export > Device Synchronization and inspect the detail view:

• The DB Sync Details section shows the current error text per data class.

• A data class can enter the state Blocked by error if the last file for that class could not be imported.

• In that case, select the affected data class row and use Download files again to schedule a re-download of the failed file and the following files.

This is the intended recovery path when the target system knows which data class is blocked and the source files are still available.

6.14.7.5. What if the queue on the target system does not decrease?

If the synchronization page shows many files waiting in the upload queue for a longer period, this indicates that the target system is importing slower than files arrive. In this case:

1. Check whether the warning about too many files in queue remains visible.

2. Check the Syslog for repeated import errors.

3. Check whether storage, database performance, or administrative limits are slowing down the upload pipeline.

4. If necessary, ask an administrator to review the system setting for maxParallelUploads.

6.14.7.6. What if files exist on disk but are still not imported?

The target system scans the import directory periodically for new device-data-class combinations and then continues to check for the next expected file. Because of this behavior, the following points matter:

• New device or data-class folders may not appear immediately in the status page because the scan cycle is periodic.

• Only files for device names matching the configured regex filter are considered.

• Incomplete or unreadable files are not imported successfully and lead to error entries instead.

6.14.7.7. How can I distinguish synchronized devices from locally created ones?

Devices created automatically by the synchronization import receive the tag syncimport. This makes it easier to recognize imported devices during troubleshooting.

6.15. Reports and Printing

All reports generated by users as PDFs can be found in the "Import / Export >> Print" section. Here you can view, download, and manage the reports.

Reports generated through the following functions can be found there:

• Manual creation of a report from the analysis cockpit

• Automatic creation of reports from automation tasks

The PDF files are stored on the server in the directory specified in the WebPQ backend. On the client, the reports are displayed in a table containing the following information:

By downloading the report #1, the user has the option to download the PDF from the server and save it locally.

With #2, the user can select multiple reports. Via #3, the user can either download multiple reports in parallel or delete multiple reports via #4.

6.16. Synchronization Status

Measuring devices that are continuously read out automatically by the database software are displayed in the "Import / Export" section under "Device Synchronization".

The exact status of the synchronization is shown there.

The page displays the following information, which can be expanded with details for a measuring device by clicking on #1. Additionally, a hierarchical view can be selected via #2. The table itself contains the following information:

6.16.1. Details of the Synchronization Status

6.16.1.1. Device Synchronization

Device synchronization displays the download status from the device to the server. In addition to the current synchronization status, such as "Inactive", the following information is also shown:

• The last transmission rate

• The current file being downloaded

• All pending files to be downloaded

If, for example, there is a connection issue with the measuring device, this error will be displayed under "Device Synchronization Error".

6.16.1.2. Database Synchronization

Database synchronization shows the upload status from the WebPQ instance to the database. Here, the individual data classes are listed, along with the files that were last uploaded to the database. The section "End timestamp for the most recent file" displays the timestamp recorded as the last measurement point in the most recently uploaded file.

Additionally, users have the option to selectively check data classes to see which data was last uploaded to the database.

If the user wants to change the settings for a measuring point, he can directly switch to the configuration of the measuring point by clicking on Settings #1. Additionally, #3 allows for expanded logging to obtain more information. This function is sometimes used in the support area upon request.

6.16.2. Synchronization Intervals and Data-Class Priority

Automatic device synchronization checks active devices repeatedly. A quick check normally runs every 30 seconds. A more thorough check normally runs every second quick-check cycle, so with the standard settings it runs about every 60 seconds. These intervals are configured by the system administrator in the WebPQ instance settings.

When several data classes are waiting for download or upload at the same time, WebPQ processes them by data-class priority. Fault recorder and long-term classes are prioritized before lower-priority classes. This helps important disturbance and EN 50160 data arrive before less urgent data when a device or database has a larger backlog.

6.17. Administration

6.17.1. Devices

6.17.1.1. Overview and General Information

Through the Device Management, devices can be viewed, added, managed, and deleted.

The interface is divided into three sections:

1. Add and delete devices

2. Tabular and hierarchical representation of all existing devices

3. Detailed device view, which is displayed after clicking on a device under #5

• "+ Add new device" #1 –
  Creates a new device through a guided wizard.

• "+ Import from WinPQ" #2 –
  Imports PQI-DA smart, PQI-LV, and PQI-DE from WinPQ into WebPQ through a wizard.

• "Delete device" –
  Deletes one or more selected devices through a background job.
  All measurement data, parameters, and settings are removed from the database.

All functions require the permission "Create and delete devices",
which is configured in the rights management at the user group level.

Additional Functions

• Test connection #4 –
  Continuously checks the active connection of all devices.

  • If a connection is present, a symbol appears under #5 directly on the device.

• Show hierarchy #5 –

  • Displays the devices in the hierarchical structure of the default settings.

  • The user can customize categories individually through drag & drop.

  • Changes remain saved for the duration of the login.

Operation with WinPQ in parallel mode

When the WebPQ software is operated together with the WinPQ software, the following measuring devices are automatically transferred from WinPQ to WebPQ after installation. An automated synchronization occurs in the background every 60 seconds. These devices are then added to the user group root_default_users, root_default_operators, root_default_administrators, and the root tenant.

• PQI-DA

• PQI-D UU (Voltage / Voltage)

• PQI-D UI (Voltage / Current)

• PQ-Boxes

For these measuring devices, WebPQ serves as a pure visualization solution based on the measurement data read out and stored in WinPQ via the PQ Manager process.

For the device generations PQI-LV, PQI-DA smart, and PQI-DE, which are used in parallel operation with WinPQ, the process of transferring the communication layer from WinPQ to WebPQ is partially automated. This can be done via the button +Import from WinPQ.

6.17.1.2. Adding PQI-D Devices

PQI-D devices are added with the same + Add new device wizard as other measuring devices. The PQI-D workflow differs from PQI-DA smart, PQI-LV, and PQI-DE because WebPQ first connects to the PQI-D communication endpoint and detects the measuring devices that are available behind that connection.

PQI-D device creation is available only when WebPQ runs on a Windows server. On other server operating systems, the PQI-D device types are hidden in the device type selection.

To add a PQI-D device:

1. Open Administration > Devices.

2. Select + Add new device.

3. Select PQI-D UI or PQI-D UU as the device type.

4. Select the device time zone and tenant.

5. Enter the PQI-D connection data:

   • Host: IP address or host name of the PQI-D communication endpoint.

   • Port: external communication port.

   • Internal Port: local port used by WebPQ for the internal PQI-D connection.

6. Click Get Devices.

7. Select the detected devices that should be created in WebPQ.

After the devices have been detected, choose the data classes that WebPQ should read automatically. WebPQ preselects the data classes needed for EN 50160 evaluation. The Active switch controls whether the automatic data download is active for the detected device.

When a PQI-D UU device exposes two voltage systems, WebPQ creates the related subdevices from the detected device list. For license counting, the related PQI-D UU pair is treated as one device unit.

6.17.1.3. Importing Devices From WinPQ

The Import WinPQ Devices wizard is intended for systems that already contain devices in a WinPQ installation. It imports the device metadata into WebPQ and supports the transfer of PQI-DA smart, PQI-LV, PQI-DE, and PQI-D devices where the communication layer can be moved into WebPQ.

Use this wizard when devices already exist in WinPQ and should be managed or read directly by WebPQ. After the import, review the detected devices before creating them. Device names, connection settings, and data classes should be checked carefully because they determine how WebPQ stores the imported measurement data and how the devices appear in analyses, exports, and dashboards.

6.17.1.4. COMTRADE Import Devices

COMTRADE imports use WebPQ devices of type Comtrade. This device type is available only when the COMTRADE import add-on is enabled in the license.

A COMTRADE device stores the target channel mapping used by the import wizard. The mapping links channel names from the COMTRADE configuration file to WebPQ data classes and data types. Check the time zone and channel mapping before running regular imports from the same source, because the settings are reused when matching COMTRADE files are imported again.

6.17.1.5. Detail Window

When the detail window is opened by clicking on one or more selected devices in the selection field, the detailed settings of the devices appear.

General #1
In the General section, the most important parameters such as IP address, device time zone, and the assignment of tags and standard templates to the measuring point can be configured.

Connection #2
In the Connection section, in addition to the IP address, the settings for the automatic data class readout process can be managed and their activation and deactivation controlled.
When multiple devices are selected in parallel via the device tree, the tabular and searchable representation allows for quick parameterization and comparison of many devices.

Parameter #3
In the Parameter section, the measuring device parameters can be individually adjusted. This allows the measuring devices to be centrally parameterized directly via the web interface.
All parameters are historized in the database. Various parameter editors allow the application of parameter templates to devices, editing of individual parameters, and importing and exporting parameters – either directly to the measuring device or to the local file system.

Service #4
In the Service section, all functions necessary for device service are summarized. These include, among others:

• Reading device log files and audit log files

• Firmware updates for the devices

Rights #5
In the Rights section, the effective permissions of users for the respective devices can be viewed via rights management and group policies.

NeQual #6
If licensed, the NeQual section allows the configuration of settings for the NEQUAL export once per measuring point.

6.17.1.6. Device / General

• #1 Tenant – Each device can be assigned to its own tenant.

• Device name – WebPQ validates the device name before the settings can be saved.

  • For most device types, only lowercase letters and digits are allowed, with a length of 2 to 12 characters.

  • PQI-D UI, PQI-D UU, and Modbus client devices may additionally use a trailing qualifier such as _1. For these device types, WebPQ allows up to 15 characters.

  • The Save button becomes available only after at least one value was changed and all required fields are valid.

• #2 Host and Port – Each device requires an IP address and a port that must be accessible from the WebPQ server.

  • For the devices PQI-DA smart, PQI-DE, and PQI-LV, port 5040 is to be used.

  • If the devices are connected via SSH (encrypted), port 22 is to be used.

  • The communication from the server to the device can be tested via Test connection.

  • If the test is successful, the button changes from orange to green.

  • WebPQ only enables Test connection while the current form data is valid. Invalid host, port, or required metadata entries must be corrected first.

• #3 Time Zone – Each device can be assigned a time zone in the software.

  • All measuring devices deliver the measurement data in UTC to the database.

  • Therefore, the respective measuring point must be equipped with the locally valid time zone.

  • This parameter affects all reports and analyses in the system.

  • When the time zone is changed for device types with time-zone support, WebPQ asks whether existing statistics should be recalculated before the change is saved.

• #4 Standard Templates – By default, the settings of the measuring device itself are used for the calculation of statistical standard limit values.

  • The standard template is loaded into the database after the first contact with the measuring device.

  • However, the user can also apply other standard templates to the measuring point.

  • These standard templates are managed in the Standard Templates section and can be accessed via the link.

• #5 Tags – After the first reading of the measurement data, each device is automatically equipped with so-called tags.

  • Tags are the basis for labeling and hierarchical representation in all selection dialogs and tables.

  • Clicking on the area displays all existing tags of the tenant.

  • Clicking on a tag assigns it to the device.

  • The Open tag settings button leads to the area where tags and categories can be added.

6.17.1.7. Device / Connection

• #1 Multiple Selection – The user can select multiple devices in parallel.

  • This is particularly advantageous when comparing settings between devices or aligning general device settings.

• #2 Offline – Measuring devices that are operated without direct TCP/IP communication (e.g., through manual file imports via SD cards) must be configured as offline devices.

  • Offline devices are automatically hidden from the live displays of measurement values.

• #3 Active – Devices that are to be automatically read out by the system with the set data classes must be set as active here.

  • If a device is taken out of service and should no longer be read out, the flag can be deactivated.

• #4 Host & Port & SSH – Specification of the IP address and port used for communication between the server and the measuring device.

  • Standard ports for the devices PQI-LV, PQI-DA smart, and PQI-DE:

    • Port 5040 for communication via CCCI (default).

    • Port 22 for encrypted communication via SSH (with user rights management).

    • For SSH connections, the SSH option must also be activated in the corresponding column.

• #5 Data Classes – Here, the data classes are defined that are to be automatically retrieved from the measuring device and stored in the database.

  • Important: On the measuring devices themselves, the desired measurement variables in the respective data classes must be activated in the recording parameters.

  • For slave devices connected to measuring devices via the P3 feature, the mbMaster must always be activated.

  • PQ-Box and PQI devices use a shared WebPQ data-class model. PQ-Box files are mapped to the corresponding WebPQ data classes during import, so the same data-class names are used later in analyses and exports.

6.17.1.8. Device / Parameter

• #1 Import – The import function allows parameter files to be loaded either directly from the device or from the local file system as XML or * .aepq file.

  • Read from device:

    • Establishes a connection to the device and saves the parameterization in the database.

    • If the device has URM with RBAC (user management), credentials are required.

  • Open from file:

    • The user can select an XML file or other supported file formats.

    • If the parameter set contains references to additional files (e.g., certificates for WireGuard or the web server), the user is prompted to add them.

    • A parameter set typically consists of the following components:

      • General parameters (XML parameter file, depending on the measuring device).

      • External parameters, e.g.:

      • IEC61850 ICD file

      • Certificates for the web server

      • Certificates for the WireGuard connection

• #2 Export – The export function allows parameter files to be sent either to the measuring device or saved in standard formats on the client.

  • "Send to device":

    • The selected parameter template is transferred to the device.

    • Before sending, the current device configuration is loaded to display the differences between the old and new template. This ensures that only desired changes are transferred.

  • "Send to fleet"(license required):

    • Forwards the parameter template to fleet management.

    • Opens the dialog for sending to multiple devices.

  • "Save file":

    • Saves the file as a .aepq file on the local file system.

  • "Export as CSV file":

    • Creates a CSV file from the parameters.

• #3 Parameter Historization – Here, the user can historically view and compare imported parameter files.

  • The history includes both imports from files and imports directly from the measuring device.

  • Each import is logged with time and user who loaded the file into the database.

  • Each parameter file can also be historized manually.

  • Changes to the parameters and their historization are displayed under #6.

• #4 Device Parameter View – simplified –
  The simplified view of the parameterization offers a fixed structure with predefined masks for the most important settings.
  The individual settings can be set directly via the input masks and are divided into the following areas:

  • Basic settings – Name and transformer settings of the measuring device

  • Limit values – Used for PQ standard evaluation

  • OSC and TRMS trigger settings – Settings for limit values and duration of the disturbance recorder

  • Time settings – Configuration of time synchronization, e.g., via a central NTP server

  • Differential current – Settings for differential current measurement on the PQI-DE device

  Note:
  Detailed information on device settings can be found in the respective user manuals of the measuring devices.

  The available simplified editors depend on the selected WebPQ device type and on the parameter set that was loaded. For example, PQ Smart devices expose dedicated editors for basic settings, thresholds, trigger settings, time settings, network settings, SCADA, and residual current monitoring, while unsupported sections stay hidden.

  The editors are schema-driven. Required fields, valid value ranges, and option-dependent sub-sections are taken from the loaded parameter schema. Depending on the selected option, WebPQ can therefore show or hide additional fields dynamically.

  Saving and exporting parameter changes follows strict validation rules:

  • Reset is only available after parameters were changed.

  • Save is only available after parameters were changed and all visible parameter editors are valid.

  • If invalid parameter values remain, WebPQ shows an error summary and blocks saving as well as exports that require a valid parameter set.

  Parameter import is also validation-aware:

  • Read from device first verifies the device connection and then stores the downloaded parameter set in the WebPQ history.

  • Open from file creates a new historized parameter set from the selected file.

  • If a PQ Smart parameter archive references additional files such as ICD files or certificates, the import wizard asks for those files before the parameter set is stored.

  In the PQ Smart Basic settings editor, some values are recalculated together:

  • Changing the network type resets the relevant reference-voltage defaults and transformer correction factors.

  • Transformer correction factors are normalized from the entered values. When the derived nominal values would violate the device constraints, WebPQ highlights the corrected target values and blocks saving until the remaining constraint violation is resolved.

6.17.1.9. Device / Service

• #1 Firmware Update – This function allows the firmware of the measuring devices to be updated centrally from the server.

  • Both the measuring devices and WebPQ require the corresponding right for the firmware update.

  • Before the update, the current parameterization of the device can be backed up under #2.

  • With an existing Fleet Management license (#3), multiple measuring devices can be updated in parallel.

• #4 Load Debug Log –

  • Downloads the debug log from the device.

  • Contains the latest log entries useful for troubleshooting and support cases.

• #5 Load Audit Log –

  • Downloads the audit log from the device.

  • Contains all security-relevant log entries.

6.17.1.10. Device / Rights

In this tabular display, all users with rights on the device are shown – including:

• Assigned rights

• Permission details (viewable via the button)

The settings for user rights on devices are made via:

• User groups

• Tenant management

6.17.1.11. Device / NeQual

If a NeQual license is available, general settings for the export must be configured per measuring point.

• These settings are persistently stored in the database and used for each export (manual or automatic).

• Mandatory fields are marked with a * and must be filled out.

6.17.2. Fleet Management

With Fleet Management, many devices can be managed in parallel.
This requires at least WebPQ Professional with the additional license "Fleet Management" or WebPQ Enterprise, which includes this function by default.

This function significantly facilitates the management of many measuring devices and enables more efficient use of working time. Especially in the area of patch management and security updates, fleet management offers great advantages.

6.17.2.1. Access and Permissions

Fleet management can be found under "Settings > Fleet Management".
The permission "Device Management" is required for use.

6.17.2.2. Functions of Fleet Management

Three central functions are available:

1. Download the current parameter file

2. Transfer an existing power quality standard template to multiple devices

3. Firmware update for multiple devices simultaneously

4. Send individual parameters to many devices

The user is guided through the first three functions by a wizard that facilitates all necessary steps.
At the end, the task is handed over to the server, which executes it in the background depending on the selected devices.

Logging out does not interrupt the job!

Each task receives a unique name, which is then displayed in a clear table with the respective status.

For the fourth option – "Send individual parameters to many devices" – access is via a device using the export function.
Detailed information can be found under Devices >> Parameterization.

6.17.2.3. Job Management and Error Handling

• By clicking on a job, the user can view detailed information about the respective task.

• If a task fails – e.g., due to unreachable devices, individual devices can be specifically reprocessed. This can be done by simply repeating the job under #1.

6.17.3. Access Concept with Users and Rights

Access is regulated by users, devices, tenants, device groups, and permissions. Users, devices, and device groups are "owned" by a tenant. Additionally, each user can have permissions for specific devices. They can only interact with objects that belong to their tenant and for which they have the necessary permissions.

Starting with WebPQ V2.1, the WebPQ application will also feature an LDAP interface that enables importing and synchronizing users and groups from an LDAP directory (e.g., Microsoft Active Directory). This allows you to centralize user management and enhance security. For more information, see the chapter LDAP Integration.

6.17.3.1. Permissions

Every data access to users, devices, or tenants requires a permission. For example, to read the measurements of a device, the user and the device must be granted the "Read Measurements" permission.

A permission can be valid for all objects within a tenant or only for a single device. To distinguish between these two types of permissions, we call them tenant permissions or device permissions.

Tenant Permissions

• Change device metadata:
  Allows changing the description or location of a device. Equivalent to granting the device permission Change Metadata for every device in your tenant.

• Change user metadata: Change the password or contact information of a user.

• Create and delete devices

• Create and delete sub-tenants

• Create and delete users

• Migrate users and devices:
  Changes the owner tenant of a user or device to another sub-tenant of yours.

• Change permissions on any tenant device:
  This permission is different from all other permissions a user can have. When granted, the user can grant any device permission of any device in their tenant to any user in their tenant, including themselves.

• Manage tasks

• Grant license management permissions

• Grant tenant management permissions

• Migrate users and devices

Device Permissions

• Read measurements:
  The most important permission on WebPQ. It is required to perform an analysis of device measurement data.

• Change metadata:
  Like the tenant permission Change device metadata. Allows changing the description or location of a specific device.

• Publish measurements:
  This permission currently has no effect. It will be used in the future to allow services to publish measurement data.

• Delete measurements:
  This permission currently has no effect. It will be used in the future to allow the deletion of past measurement data points.

• Update firmware:
  This permission is necessary if a user or user group needs to update the firmware on the devices.

• Parameterize devices:
  This permission is necessary if a user or user group needs to set parameters on the devices.

Permission States

Sometimes it is not enough to just grant a permission. If you want to grant a permission to your colleague, you must also be authorized to grant this permission to someone else. In this case, the permission must be in the state "can grant" or "fully granted".

The four states in which a user's permission can be are as follows:

• Denied:
  The permission is not granted to the user, and they are not allowed to grant it to any other user (including themselves).

• Granted:
  The permission is granted to the user. However, they are not allowed to grant it to other users.

• Can grant:
  The permission is not granted to the user, but they can change the status of the permission for all users in their tenant, including themselves!

• Fully granted:
  The combination of Granted and Can Grant. The permission is granted to the user, and they are also allowed to change the permission status of all users in their tenant.

Device Permissions are Granted in a Three-Tier Model:

• A user can have the permission Change permissions on any tenant device in their tenant permission set. This permission allows editing any other permission of any device in the tenant and its sub-tenants.

• A user can be listed in a user group, and this group grants permissions for specific devices.

• A user can have direct permissions for devices.

All permissions are positive. This means that if a user is granted a permission on a device by a user group or directly, this permission cannot be revoked by another user group.

6.17.3.2. User Management

6.17.3.2.1. Adding a User

This function requires the "Create Users" permission.

• Go to Users. Press "New User" (#1) to create a new user. A dialog will appear asking for details.

• Enter an alphanumeric username and assign a password to the user.

• First name, last name, and email must also be entered correctly.

• Select a tenant in the tenant selection.

• Select one or more devices that the user is allowed to see (optional).

• Press "OK" to create the user.

6.17.3.2.2. Changing User Properties

This function requires the "Change User Metadata" permission.

• Go to Users. Select the user and edit the desired fields. Press "Update".

6.17.3.2.3. Deleting a User

This function requires the "Create and Delete Users" permission.

• Go to Users. Select the user.

• Click on "Delete User" in the upper left corner.

6.17.3.3. User Groups

User groups are used for easy administration of many devices. The WebPQ software has three standard user groups:

• root_default_users

• root_default_operators

• root_default_administrators

6.17.3.3.1. Setting Up a User Group

To use this function, you need the permission to change permissions on any tenant device in your tenant.

• Go to User Group.

• Click on "New User Group" (#1).

• Enter a name, add users and devices (#2 and #3).

• Select a tenant.

• Adjust the permissions for the devices of the user group and click "Update" (#4).

• Press "Update" (#5).

6.17.3.4. Tenants

License Required

Tenants are used to isolate resources (users, devices) through administrative rights and data storage. The global settings for tenant management are also defined in the tenant settings. These settings are:

• Password policies for the tenant and sub-tenants

• Email settings for the tenant and sub-tenants

• Report settings for the tenant and sub-tenants

6.17.3.4.1. Creating a New Tenant

This function requires the permission to create and delete sub-tenants.

• Go to Tenants. Press "New Tenant" #1 to create a new tenant.

• Enter the parent name.

• Select your own tenant as the parent tenant.

• Press "OK" to complete the creation of the tenant.

6.17.3.4.2. Deleting a Tenant

This function requires the permission to create and delete sub-tenants.

• Go to Tenants. Select a tenant.

• Click on "Delete Tenant" in the lower left corner (#7) and confirm the process.

Only tenants without assigned users and devices can be deleted.

6.17.3.4.3. Password Policies

This function requires the permission to change tenant settings.

• Go to Tenants. Select a tenant.

• Click on Password Policies.

• Enter the desired password policies.

• Click on Update Tenant.

Note on Default Password Policies

If the password policies for a tenant are deactivated, the default password policies will automatically apply.
These default values are configured as follows:

• Minimum password length: 20 characters

• At least 6 lowercase letters

• At least 5 uppercase letters

• At least 4 special characters

• At least 3 digits

• No minimum interval for password changes

• Maximum password validity: 3650 days

6.17.3.4.4. Email Settings

This function requires the permission to change tenant settings.

• Go to Tenants. Select a tenant.

• Click on Email Settings.

• Enter the SMTP server data.

• Select the port and encryption method.

• Enter the login credentials.

• Click on Update Tenant.

Using the Test Email function, you can send a test email to the specified address.

6.17.3.4.5. Report Settings

This function requires the permission to change tenant settings.

Here, the logos for the reports are globally defined for the tenant.

• Go to Tenants. Select a tenant.

• Click on Report Settings.

• Choose whether the report should inherit the settings from the parent tenant or use a different logo.

• If you want to use a different logo, you can upload it via "Browse".

6.17.4. LDAP Integration

Note: This feature is available in the Enterprise Edition starting from WebP V2.1.

LDAP integration allows you to import and synchronize users and groups from an LDAP directory (e.g., Microsoft Active Directory). This enables centralized user management and simplifies user administration.

6.17.4.1. How LDAP Integration Works

After enabling LDAP integration, users can log in to WebPQ directly using their LDAP credentials (username and password). Authentication is performed via the connected LDAP server. On first login, users are automatically assigned to the WebPQ group root_default_users.

Each LDAP user is counted as a separate unit and is included in the license calculation—licensing for LDAP users is identical to regular users.

Note: Automatic synchronization of LDAP groups is currently not supported. All LDAP users are added exclusively to the root_default_users group. Permissions for LDAP users must be assigned manually via groups in the WebPQ application, as the LDAP server cannot manage application-specific permissions.

6.17.4.2. LDAP Configuration

Basic Settings LDAP integration is configured in the WebPQ backend under Settings > LDAP. The following settings are available:

• Enable LDAP: Activate this option to enable LDAP integration.

• Host - LDAP Server: Enter the address of your LDAP server (e.g., ldap.example.com).

• Port: Enter your LDAP server's port (default: 389 for unencrypted LDAP, 636 for LDAPS).

• Use TLS: Enable this option if your LDAP server uses SSL/TLS for the connection.

• Ignore certificate errors: Enable this option if you use self-signed certificates and want to ignore certificate errors.

• Custom CA certificate (optional): Add a custom CA certificate here if your LDAP server uses a certificate not issued by a widely recognized certificate authority.

• Connect Timeout: Specify the connection timeout in seconds (default: 10 seconds).

• Close Client after: Specify the time in seconds after which the LDAP connection will be closed if no longer needed (default: 300 seconds).

LDAP Search Settings:

• Bind DN: Enter the Distinguished Name (DN) of the user used to bind to the LDAP server (e.g., cn=admin,dc=example,dc=com).

• Password: Enter the password for the bind user. Leave blank for anonymous binding.

• Base DN: Enter the base DN from which the search for users and groups starts (e.g., dc=example,dc=com).

• Search filter: Define an LDAP filter to find users, e.g., ((&(objectClass=user)(sAMAccountName={{username}}))).

Note: Some LDAP servers have case-sensitive attribute names. For example, cn and CN may be treated differently. Make sure to write the attributes exactly as they are stored on the LDAP server.

User Properties Mapping: Use the test function below to view all available LDAP properties from your LDAP server.

• Username Attribute: Enter the LDAP attribute containing the username (default: uid). Note: "sAMAccountName" is recommended for Microsoft Active Directory.

• First Name Attribute: Enter the LDAP attribute containing the first name (default: givenName).

• Last Name Attribute: Enter the LDAP attribute containing the last name (default: sn).

• Email Attribute: Enter the LDAP attribute containing the email address (default: mail).

With Test Connection, you can test the connection to the LDAP server and verify if the configuration is correct. With Save, the settings are applied.

Test Username (testing only): Enter a username to test the LDAP search.

Test Result: Displays the results of the LDAP search for all parameters. If the user is found, the mapped attributes are shown.

6.17.5. OAuth Integration

Note: This feature is available in the Enterprise Edition starting from WebPQ V2.1.

OAuth integration allows you to use an external OAuth 2.0 / OpenID Connect provider (e.g., Microsoft Entra ID, Keycloak, Okta) for user authentication in WebPQ. This enables single sign-on (SSO) and centralizes identity management with your existing identity provider.

When OAuth is enabled, the login page will display an additional button allowing users to authenticate via the configured OAuth provider:

6.17.5.1. How OAuth Integration Works

After enabling OAuth integration, users can log in to WebPQ by clicking the OAuth login button on the login page. They will be redirected to the configured OAuth provider for authentication. Upon successful authentication, users are redirected back to WebPQ and automatically logged in.

If autoRedirect is enabled, WebPQ redirects users to the OAuth provider automatically when they open the login page. The regular login page is then only shown again if WebPQ has to display an OAuth error message or after an explicit logout.

On first login, OAuth users are automatically created in WebPQ and assigned to the root_default_users group. Each OAuth user is counted as a separate unit and is included in the license calculation—licensing for OAuth users is identical to regular users.

On later logins, WebPQ compares the returned OAuth user data with the locally stored OAuth user and updates the stored first name, last name, and email address if they changed at the provider.

Note: Automatic synchronization of groups from the OAuth provider is currently not supported. All OAuth users are added exclusively to the root_default_users group. Permissions for OAuth users must be assigned manually via groups in the WebPQ application.

If a local non-OAuth user already exists with the same username, the OAuth login is rejected. The same applies if an existing OAuth user is found with the same username but a different external ID than before.

If WebPQ is configured to require acceptance of the current privacy policy, the user is taken to the normal application startup first, but the application remains blocked by a consent dialog until the privacy policy is accepted. If the user declines, WebPQ logs the user out again.

6.17.5.2. OAuth Configuration

Unlike LDAP, OAuth integration is not configured through the WebPQ user interface. Instead, it must be configured by manually editing the settings.json file.

Where to find the settings.json file:

The location of the settings.json file depends on your installation. You can find the path in the WebPQ administrative backend under Other (see Installation - Part 6). Typical locations include:

• Windows (Electron): %ProgramData%\WeSense\WebPQ\settings.json

• Docker / Kubernetes: Mounted as a volume or configured via environment variables

To enable OAuth, add or modify the oauth section within the settings.json file. After making changes, restart the WebPQ service for the new configuration to take effect.

Example configuration:

{
    "oauth": {
        "clientId": "your-client-id",
        "clientSecret": "your-client-secret",
        "scope": "openid profile email",
        "discoveryUrl": "https://your-provider.com/.well-known/openid-configuration"
    }
}

6.17.5.3. OAuth Settings Reference

The following settings are available in the oauth section of settings.json:

Required Settings

• clientId(string, required): The OAuth client ID used to identify WebPQ with the OAuth provider. You receive this value when registering WebPQ as an application in your OAuth provider.

• clientSecret(string, required): The OAuth client secret used to authenticate WebPQ with the OAuth provider. Keep this value confidential. You receive this value when registering WebPQ as an application in your OAuth provider.

• scope(string, required): The scopes to request from the OAuth provider, as a space-separated list. Common values include "openid profile email". The openid scope is typically required for OpenID Connect providers.

Server Discovery

You must configure either a discoveryUrl or the server property, but not both.

• discoveryUrl(string, optional): The OpenID Connect discovery URL (typically ending in /.well-known/openid-configuration). When provided, WebPQ will automatically retrieve all necessary endpoint information from the OAuth provider. This is the recommended approach.

  Example: "https://login.microsoftonline.com/{tenant-id}/v2.0/.well-known/openid-configuration"

  Note: Replace {tenant-id} with your actual Microsoft Entra ID (Azure AD) tenant ID.

• server(object, optional): If your OAuth provider does not support discovery, you can provide the server metadata directly. The following three endpoint properties are required when using this option:

  • authorization_endpoint(string, required): The URL where users are redirected for authentication.

  • token_endpoint(string, required): The URL used to exchange the authorization code for tokens.

  • userinfo_endpoint(string, required): The URL used to retrieve user profile information.

  Additionally, you can provide any other properties supported by the OpenID Connect server metadata specification. Common optional properties include:

  • issuer(string): The issuer identifier of the OAuth provider.

  • jwks_uri(string): The URL of the JSON Web Key Set for token signature verification.

  • end_session_endpoint(string): The URL to redirect users to for logout at the OAuth provider.

  • scopes_supported(string[]): The list of scopes supported by the OAuth provider.

  • response_types_supported(string[]): The response types supported by the OAuth provider.

  For a complete list of available properties, see the openid-client ServerMetadata documentation.

  Example:

  {
      "server": {
          "issuer": "https://your-provider.com",
          "authorization_endpoint": "https://your-provider.com/oauth2/authorize",
          "token_endpoint": "https://your-provider.com/oauth2/token",
          "userinfo_endpoint": "https://your-provider.com/oauth2/userinfo",
          "end_session_endpoint": "https://your-provider.com/oauth2/logout"
      }
  }

User Field Mapping

These settings control how user information from the OAuth provider is mapped to WebPQ user properties. The values refer to field names in the response returned by the OAuth provider's userinfo endpoint.

• customUsernameField(string, optional): The field in the user info response that contains the username. Defaults to "sub".

• customEmailField(string, optional): The field that contains the user's email address. Defaults to "email".

• customExternalIdField(string, optional): The field that contains an external ID for the user. Defaults to the same value as the username field.

• customPreNameField(string, optional): The field that contains the user's first name. Defaults to "given_name".

• customSurNameField(string, optional): The field that contains the user's last name. Defaults to "family_name".

Tip: If you are unsure which fields your OAuth provider returns, enable the debug option (see Advanced Settings below). This will log the full userinfo response from the OAuth server to the authentication log, including all available fields and their values, making it easy to identify the correct field names for the mapping above. Search for the log message containing [OAUTH Debug] Retrieved user info to find the relevant log entry.

Behavior Settings

• oauthOnly(boolean, optional): When set to true, the standard login form for local user authentication is hidden, and only the OAuth login option is shown. Defaults to false.

• autoRedirect(boolean, optional): When set to true, users visiting the login page will be automatically redirected to the OAuth provider instead of seeing the login page. Defaults to false.

  WebPQ suppresses this automatic redirect while it is handling a just-finished OAuth login, an OAuth error, or an explicit logout. This prevents immediate redirect loops.

• skipLogoutRedirect(boolean, optional): When set to true, logging out of WebPQ will not redirect the user to the OAuth provider's logout endpoint. The user will only be logged out of WebPQ, but their OAuth session may remain active. Defaults to false.

  If skipLogoutRedirect is false, WebPQ only redirects to the OAuth provider when the provider metadata contains an end_session_endpoint. Otherwise WebPQ falls back to a local logout and returns to the login page.

• loginText(string, optional): Custom text to display on the OAuth login button instead of the default "Login with OAuth" text.

Advanced Settings

• redirectUriBase(string, optional): The base URL used for constructing the OAuth redirect URI. The full redirect URI will be this base URL followed by /authenticate/oauth/callback. Only set this if the redirect URI is not detected correctly by WebPQ automatically.

• debug(boolean, optional): When set to true, detailed debug information about the OAuth login process is written to the authentication log. This is helpful for troubleshooting issues or identifying the correct field names for user mapping. Defaults to false.

  Warning: Enabling this option causes sensitive information (such as tokens, user details, and other authentication data) to be written to the authentication log. Only enable it temporarily for troubleshooting and disable it again afterwards.

6.17.5.4. Debug Log Location

The debug log messages are located in the logs folder at %PROGRAMDATA%\aeberle\logs\. If the audit log feature has been enabled, the log messages are found in the audit subfolder. Otherwise, they are written to the main log file, where they are prefixed with auth-logger.

Example log output:

[master-data-auth-logger][2026-03-25T22:02:58.987Z][INFO] [OAUTH Debug] Starting OAuth authentication flow
[master-data-auth-logger][2026-03-25T22:02:59.113Z][INFO] [OAUTH Debug] Parsed OAuth server configuration: {
  "token_endpoint": "https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/oauth2/v2.0/token",
  "token_endpoint_auth_methods_supported": [
    "client_secret_post",
    "private_key_jwt",
    "client_secret_basic",
    "self_signed_tls_client_auth"
  ],
  "jwks_uri": "https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/discovery/v2.0/keys",
  "response_modes_supported": [
    "query",
    "fragment",
    "form_post"
  ],
  "subject_types_supported": [
    "pairwise"
  ],
  "id_token_signing_alg_values_supported": [
    "RS256"
  ],
  "response_types_supported": [
    "code",
    "id_token",
    "code id_token",
    "id_token token"
  ],
  "scopes_supported": [
    "openid",
    "profile",
    "email",
    "offline_access"
  ],
  "issuer": "https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/v2.0",
  "request_uri_parameter_supported": false,
  "userinfo_endpoint": "https://graph.microsoft.com/oidc/userinfo",
  "authorization_endpoint": "https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/oauth2/v2.0/authorize",
  "device_authorization_endpoint": "https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/oauth2/v2.0/devicecode",
  "http_logout_supported": true,
  "frontchannel_logout_supported": true,
  "end_session_endpoint": "https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/oauth2/v2.0/logout",
  "claims_supported": [
    "sub",
    "iss",
    "cloud_instance_name",
    "cloud_instance_host_name",
    "cloud_graph_host_name",
    "msgraph_host",
    "aud",
    "exp",
    "iat",
    "auth_time",
    "acr",
    "nonce",
    "preferred_username",
    "name",
    "tid",
    "ver",
    "at_hash",
    "c_hash",
    "email"
  ],
  "kerberos_endpoint": "https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/kerberos",
  "mtls_endpoint_aliases": {
    "token_endpoint": "https://mtlsauth.microsoft.com/12345678-1234-1234-1234-123456789012/oauth2/v2.0/token"
  },
  "tls_client_certificate_bound_access_tokens": true,
  "tenant_region_scope": "EU",
  "cloud_instance_name": "microsoftonline.com",
  "cloud_graph_host_name": "graph.windows.net",
  "msgraph_host": "graph.microsoft.com",
  "rbac_url": "https://pas.windows.net"
}
[master-data-auth-logger][2026-03-25T22:02:59.115Z][INFO] [OAUTH Debug] Using OAuth parameters: {
  "redirect_uri": "https://my-webpq.example.com/authenticate/oauth/callback",
  "scope": "openid profile email",
  "code_challenge": "...",
  "code_challenge_method": "S256",
  "state": "..."
}
[master-data-auth-logger][2026-03-25T22:02:59.122Z][INFO] [OAUTH Debug] Redirecting user to URL: https://login.microsoftonline.com/12345678-1234-1234-1234-123456789012/oauth2/v2.0/authorize?redirect_uri=https%3A%2F%2Fmy-webpq.example.com%2Fauthenticate%2Foauth%2Fcallback&scope=openid+profile+email&code_challenge=...&code_challenge_method=S256&state=...&client_id=...&response_type=code
[master-data-auth-logger][2026-03-25T22:02:59.122Z][INFO] [OAUTH Debug] Saving OAuth session data to cookie: {
  "codeVerifier": "...",
  "state": "...",
  "redirectPath": "https://my-webpq.example.com/"
}
[master-data-auth-logger][2026-03-25T22:03:09.869Z][INFO] [OAUTH Debug] Starting OAuth callback
[master-data-auth-logger][2026-03-25T22:03:09.870Z][INFO] [OAUTH Debug] Parsed OAuth session data from cookie: {
  "codeVerifier": "...",
  "state": "...",
  "redirectPath": "https://my-webpq.example.com/"
}
[master-data-auth-logger][2026-03-25T22:03:09.870Z][INFO] [OAUTH Debug] Using callback URL to parsed OAuth information: https://my-webpq.example.com/authenticate/oauth/callback?code=...&session_state=...
[master-data-auth-logger][2026-03-25T22:03:10.117Z][INFO] [OAUTH Debug] Retrieved tokens: {
  "token_type": "bearer",
  "scope": "email openid profile",
  "expires_in": 3941,
  "ext_expires_in": 3941,
  "access_token": "...",
  "id_token": "..."
}
[master-data-auth-logger][2026-03-25T22:03:10.346Z][INFO] [OAUTH Debug] Retrieved user info: {
  "sub": "...",
  "name": "...",
  "family_name": "...",
  "given_name": "...",
  "email": "...",
  "picture": "https://graph.microsoft.com/v1.0/me/photo/$value"
}
[master-data-auth-logger][2026-03-25T22:03:10.347Z][INFO] [OAUTH Debug] User ... already exists in local storage, checking external source...
[master-data-auth-logger][2026-03-25T22:03:10.349Z][INFO] [OAUTH Debug] User details changed for ..., updating...
[master-data-auth-logger][2026-03-25T22:03:10.369Z][INFO] [OAUTH Debug] Authenticated with username: ...
[master-data-auth-logger][2026-03-25T22:03:10.372Z][INFO] [OAUTH Debug] Redirecting user to URL: /?oauth-redirect=https%3A%2F%2Fmy-webpq.example.com%2F&oauth-success=1
[master-data-auth-logger-USER][2026-03-25T22:03:11.169Z][INFO] <13>1 2026-03-25T22:03:11.169Z localhost - - 100 - [IP: ...]: User ... logged in successfully

6.17.5.5. Full Configuration Example

Below is a complete example configuration using Microsoft Entra ID (formerly Azure AD) with discovery.

Note: Replace {tenant-id} with your actual Microsoft Entra ID (Azure AD) tenant ID.

{
    "oauth": {
        "clientId": "edd6e596-0da2-46dd-9f6b-1be0b3e9b9c3",
        "clientSecret": "your-client-secret-here",
        "scope": "openid profile email",
        "discoveryUrl": "https://login.microsoftonline.com/{tenant-id}/v2.0/.well-known/openid-configuration",
        "debug": false
    }
}

6.17.5.6. Troubleshooting

• OAuth login button does not appear: Ensure that clientId, clientSecret, and scope are all set in the configuration. All three fields are required for OAuth to be enabled.

• The login page immediately jumps to the OAuth provider: This is expected when autoRedirect is enabled. To keep the local login form visible for troubleshooting, disable autoRedirect temporarily.

• Users are not being created: Enable debug mode and check the authentication logs for details about the OAuth login process and the user info response from the provider.

• OAuth login fails although the provider login was successful: Check whether a local user with the same username already exists as a non-OAuth user, or whether the provider now returns a different external ID than during the first login. In both cases WebPQ rejects the login to avoid linking the OAuth account to the wrong local user.

• Wrong username or email is assigned: Use debug mode to inspect the fields returned by the OAuth provider's userinfo endpoint, then adjust the customUsernameField, customEmailField, and other field mapping settings accordingly.

• Redirect URI mismatch: Ensure the redirect URI registered in your OAuth provider matches the one used by WebPQ. The redirect URI follows the pattern https://<your-webpq-host>/authenticate/oauth/callback. If needed, set redirectUriBase to override the detected base URL.

• Logout returns to WebPQ, but the next login signs the user in again immediately: This usually means the OAuth provider session is still active. Either configure an end_session_endpoint in the provider metadata or disable skipLogoutRedirect=false so WebPQ can send the user to the provider logout endpoint.

• Users are asked for privacy-policy consent after OAuth login: This is expected when the WebPQ instance requires consent to the current privacy policy and the user has not yet accepted the currently stored statement. The user must accept the dialog before the application becomes usable.

6.17.6. Device Tagging

6.17.6.1. Tagging Concept in WebPQ

To provide users with a flexible way to organize and classify devices, the WebPQ software features a universal tagging system.

The concept includes the following core components:

• Categories: These are divided into free categories and system categories.

• Tags: Tags consist of system tags and free tags.

Each tag can be assigned to a category, and each device can receive one or more tags.

6.17.6.2. System Tags and System Categories

System tags and system categories depend on the connected device. An example is the system category Firmware, which is specifically used for measuring devices. Each measuring device has a system tag where the firmware version is automatically entered – either at the first contact with the device or after connection.

6.17.6.3. Tagging Settings

The settings for tagging and categories require the permission Change device metadata and are located in the menu Settings >> Device Tagging.

6.17.6.4. Adding a New Category

1. Click on "+ Create new category".

2. Enter a name for the new category, e.g., "Voltage Level".

3. Enter a unique description, e.g., "Category for defining the voltage level".

4. Select the tenant for which the category should be available, e.g., "root".

5. Assign a color to the category, e.g., "Black".

6.17.6.5. Setting a Standardized Hierarchy of Categories – System-wide

In the Categories section, the user can set the system-wide order of the hierarchical listing under #1.

Procedure:

1. Click in the field #1 → All available categories will be displayed.

2. Enter the desired category in the dialog box.

3. Select the desired category.

4. Remove unnecessary categories if needed.

Example:

With these settings, all selection dialogs would be sorted in the following order:

1. Nominal voltage

2. Device name

3. Associated slaves in Modbus master mode

This standardized hierarchy ensures a uniform and logical sorting throughout the application.

6.17.6.6. Adding a New Tag

To add a new tag, follow these steps:

1. Click on "# Create new tag".

2. Enter a name for the new tag, for example, "11kV".

3. Enter a unique description, such as "All devices with nominal voltage 11kV".

4. Select the tenant for which the tag should be available, for example, "root".

5. Assign the tag to a category, such as "Voltage Level".

6. Assign a color to the tag, for example, "Black".

After creating the tag, it can be found in the table and assigned to the corresponding devices by clicking on it. This allows efficient management and classification of devices based on the defined tags.

6.17.7. License Management

The License Management page shows the currently stored WebPQ license and is the central place for updating or reactivating it.

The page is primarily relevant for administrators with permission to manage licenses. Regular users can see the effects of a missing or inactive license, but they cannot complete the licensing steps themselves.

6.17.7.1. License File

WebPQ uses a signed JSON license file that is provided via the A. Eberle licensing process.

The file name typically contains the product, order information, and a timestamp. Keep this file stored safely because it is needed again for updates, renewals, or support cases.

Example:

License-WebPQ Basic-2025-12-10T11_40_43.408Z.json

6.17.7.2. Uploading or Replacing a License

In License Management, a new license file can be loaded via + Add License.

Procedure:

1. Click Browse and select the new JSON license file.

2. Confirm the displayed license content.

3. Store the license in WebPQ.

If the new license belongs to a different license ID than the activation already stored in the system, WebPQ shows a warning before replacing it. This warning means the system must be activated again for the new license.

If the license is updated but keeps the same license ID, the existing activation can remain valid.

6.17.7.3. Activation Workflow

Starting with WebPQ 2.1, the installation must also be activated in addition to storing the license file.

Activation is hardware-bound:

1. WebPQ generates a LicenseActivationRequest.json file for the current host.

2. This request is uploaded or pasted into the activation portal at https://activate-license.powerquality.cloud.

3. The portal returns an activation token or activation file.

4. That activation token is pasted back into WebPQ, or the activation file is imported there.

The activation request can be copied to the clipboard or saved as a file directly from WebPQ.

If the currently stored activation does not match the host hardware anymore, WebPQ reports a hardware mismatch and requires reactivation.

6.17.7.4. Grace Period and User Experience

After a license has been installed but not yet activated, WebPQ allows a grace period of up to 30 days.

• Administrators with license-management permission receive the activation dialog and can complete the process.

• Other users only see a notice telling them to contact an administrator.

• After the grace period has expired, the application is blocked until a valid activation has been entered.

6.17.7.5. Reactivation After Host Changes

The activation is tied to the hardware fingerprint of the host system. If the host is moved, replaced, or changed substantially, the stored activation is no longer valid.

In that case:

1. Generate a new activation request from WebPQ.

2. Try to activate it through the activation portal.

3. If the activation has already been used for the previous hardware, contact A. Eberle support so the activation can be reset.

4. Repeat the activation process with the reset license.

6.17.7.6. Validity Period and Update Eligibility

WebPQ distinguishes between:

• the validity of the currently stored software license for using the product, and

• the time window in which patches and software enhancements may be installed.

For standard licenses, updates are generally covered for 12 months from purchase. If this update period has expired, the installed software can continue to run, but WebPQ shows a warning that patches and software enhancements are no longer covered.

Administrators can hide this warning temporarily. WebPQ shows it again later after a longer period.

If you want to install a newer version after the update entitlement has expired, you need a renewed license or maintenance extension.

6.17.7.7. SaaS and Infinite Licenses

Some product variants, especially SaaS-oriented licenses, can be issued as infinite licenses. In that case WebPQ stores the license without a calendar expiration date.

For users, this means:

• the license validity itself does not end on a specific date,

• the product is shown as permanently valid instead of displaying a normal expiry date,

• but activation and product-specific feature checks still continue to apply.

6.17.7.8. What Happens During Updates

If an update requires a renewed or different license, load the new JSON license first or during the update process.

If the new license uses a different license ID than the previous one, expect WebPQ to request a fresh activation after the replacement.

For the installation-side activation flow, see the installation chapter.

6.17.7.9. Practical Notes for Support Cases

• Keep the currently used license file available.

• Note the visible license ID from WebPQ when contacting support.

• For host migration or hardware replacement, mention that reactivation is required.

• For update entitlement extensions, send the current license information or license ID to A. Eberle.

6.17.8. Data Protection

6.17.8.1. Overview and General Information

In the data protection settings, it is possible to store company-specific data protection policies in the software.

The software offers multilingual templates to document the exact circumstances of data storage and processing in the system.

Users can edit the data protection policies in multiple languages directly in the editor and save them in the system.

After saving, the updated data protection agreement is automatically applied as the default.
It is visible both in the login area and in the footer of the software.

7. Knowledge Base / FAQ

7.1. Working with the Browser

7.1.1. Troubleshooting Connection Issues

The WebPQ application typically loads a large amount of data to provide a comprehensive and detailed display of the content. However, if an error occurs, such as when the connection to the server is interrupted, the browser may not be able to load further data. In such a case, it can be helpful to press the F5 key or the CTRL + R key combination. This will reload the webpage and send a new request to the server, restoring the data connection and reloading the content.

7.1.2. Recommended Browser Settings

7.1.2.1. Caching

To ensure smooth operation in the browser, cookies should be allowed on the PC being used. The cache should be persistently stored at least for the "WebPQ" application. The WebPQ application stores metadata and customer-specific settings, such as those of the "Analysis Cockpit," locally in the "local storage." This prevents unnecessary data transfers from the server to the client and enables quick analyses. If cookies are deleted after leaving the browser, settings are not persisted and may need to be reconfigured. To prevent this, we recommend setting exceptions in the browser for the application.

Procedure (example using the "Firefox" browser):

1. Open the settings in the browser

   

2. Go to the "Privacy & Security" settings

   

If the checkbox "Delete cookies and site data when Firefox is closed" is checked, the "local storage" will be deleted when the browser is closed, and the above-mentioned case may occur. It is recommended to add an exception for the application (domain).

7.2. WebPQ Service

The WebPQ service can be started via the command line with the --console extension. This option displays all log outputs directly in the console instead of being saved in a separate log file. This can be particularly useful for monitoring errors or important system messages in real-time and quickly responding to issues. Administrators or developers can immediately see which processes are running in the background and intervene if necessary.

7.3. Logfiles

The WebPQ application logs all events of the various processes by default in the directory specified in the WebPQ backend.

7.3.1. Location of logfiles

By default, the log directory can be found under Windows here:
C:\ProgramData\aeberle\webpq\logs

7.3.2. Types of logfiles

WebPQ distinguishes the following log types:

• WebPQService.err.log
  → Contains log entries of the Windows service

• Folder Services
  → Contains logs of the various processes within the application

• Folder audit
  → Stores auditable events, such as:

  • User logins to the system

  • Incorrect password entries

  • Changes to user and rights management

These audit logs serve traceability and security by documenting all relevant changes and activities in the system.

7.3.3. Limiting the number of logfiles

To limit the number of stored logfiles, a maximum retention period in days for logging can be set in the system.

7.3.4. Configuration in the settings.json

The settings for the logfile retention period are located in the settings.json file.
By default, logfiles are stored for 50 days.

The relevant parameter for limiting is:

"pruneLogsAfterDays": 50

The WebPQ service must be restarted once on the server to activate the setting.

7.3.5. Reading the logfiles

To also access the logfiles on the client, there is an option in the "Syslog" section to download all logfiles from the system.

By clicking the "Download Logfiles" button, all logfiles can be downloaded directly from the system. Additionally, a special logfile with user-specific information can be downloaded via the "Download Audit Logfiles" button.

	The availability of the "Download Audit Logfiles" button depends on the user rights. Depending on the permission, the button may be shown or hidden.
Note

7.3.5.1. Embedding in an iframe

By default, WebPQ sends additional HTTP security headers that prevent the application from being embedded in a third-party iframe. This is the secure default and primarily protects against clickjacking.

For special on-premise scenarios, embedding can be adjusted through the settings.json file if required.

The relevant parameter is:

"allowEmbeddingInIframe": false | "same-origin" | true

Example in the settings.json file:

"http": {
  "httpAccessLogging": false,
  "allowEmbeddingInIframe": "same-origin"
}

Notes:

• The default value is false, which sends X-Frame-Options: DENY and Content-Security-Policy: frame-ancestors 'none'.

• The value "same-origin" sends X-Frame-Options: SAMEORIGIN and Content-Security-Policy: frame-ancestors 'self'.

• The value true removes the framing restrictions and should only be used if WebPQ must be embedded in a trusted parent application from another origin.

• After changing the setting, the WebPQ service must be restarted on the server.

7.3.5.2. HTTP Strict Transport Security HSTS

WebPQ can additionally send the Strict-Transport-Security header. This instructs browsers to keep using HTTPS for the application for a longer period after the header has been received once.

The relevant parameter is:

"strictTransportSecurity": true

Example in the settings.json file:

"reverseProxy": {
  "https": {
    "strictTransportSecurity": true
  }
},
"http": {
  "httpAccessLogging": false,
  "allowEmbeddingInIframe": false
}

Notes:

• The standard on-premise HTTPS-only defaults enable this setting.

• This setting should only remain enabled when the installation is intended to stay HTTPS-only.

• If HTTP and HTTPS are both enabled, WebPQ will not emit the HSTS header even when this setting is true.

• If browsers have already cached HSTS and you want to allow HTTP again later, keep HTTPS reachable until the cached browser state has expired or has been cleared intentionally.

7.4. Backup and Restore

7.4.1. Overview of Backup Options

In practice, there are three useful backup strategies for WebPQ. The right option mainly depends on whether the installation is intended to be simple or highly resilient.

7.4.1.1. Option 1: Full backup of the complete virtual machine

This option is especially suitable for simple installations where the WebPQ application is installed on drive C: and the database is installed on drive D: of the same virtual machine.

In this setup, the complete virtual machine is backed up including all attached disks. This means the backup contains the operating system, the WebPQ installation, configuration, user data, certificates, and the database on drive D: together.

Advantages:

• Very simple recovery if the complete machine fails.

• The complete system configuration remains available in one consistent backup.

• Well suited when recovery on the same or a new hypervisor should be completed quickly.

Notes:

• Make sure that the VM backup really includes all disks relevant to WebPQ, especially the data disk D:.

• A VM snapshot or VM backup does not replace a planned retention strategy with multiple restore points.

• Before updates or major system changes, an additional dedicated backup point should be created.

7.4.1.2. Option 2: Machine backup plus separate database backup

For many production systems, this is the recommended standard approach. In this model, the machine or virtual machine is backed up and the database is additionally protected by its own database backup concept.

The advantage is that the system environment and the database can be restored separately. This makes it possible, for example, to restore a server to a known-good state while recovering the database from a newer or specifically selected backup point.

This concept usually includes:

• Backup of the WebPQ machine or the WebPQ system partition.

• Regular PostgreSQL backups with defined retention.

• Separate backup of important configuration files, certificates, licenses, and keys.

This option is usually more robust than relying on a machine backup alone because logical database errors or accidental changes can be corrected more precisely.

7.4.1.3. Option 3: Advanced concept with database mirror and classic backups

For installations with higher availability requirements and short downtime targets, an advanced concept with an additional PostgreSQL backup mirror via streaming replication and complementary classic backups is recommended.

In this model, the existing backup mirror is operated as a continuously updated copy of the production database. In an emergency, the backup server can be promoted to the new primary server. The setup details are described in the installation chapter under PostgreSQL Backup Mirror with Streaming Replication.

The important point is:

• Replication increases resilience.

• Replication does not replace classic database backups.

• Regular database backups are still required for older restore points and protection against operator errors.

This option is the best basis when restoration should be possible within a few hours or faster.

7.4.1.4. Position of existing WinPQ backups

An existing automatic backup via WinPQ can still be useful, especially for device parameters or device-specific configurations. However, it should not be treated as the only strategy for the complete restoration of a WebPQ system.

For full restoration, at least the server or VM backup, the database backup, and the backup of relevant configuration and key material are also required.

7.4.2. Restore Path and Recommended Approach

Fast and complete restoration requires not only a backup itself but also a clear restore procedure.

The recommended approach is:

1. Choose a backup strategy that allows the operating system, the WebPQ application, the database, and the configuration data to be restored together or in a coordinated way.

2. Ensure that certificates, license information, passwords, connection data, and exported keys are stored securely in addition to the database contents.

3. Perform test restores regularly so that no unknown steps remain in a real emergency.

4. Store backups outside the productive server or datacenter so that they remain available even in the event of hardware failure or site damage.

Depending on the selected strategy, the typical restore path is as follows:

• With option 1, the complete virtual machine is restored from the last consistent backup or snapshot.

• With option 2, the machine or server is restored first and then the database is recovered from the planned PostgreSQL backup.

• With option 3, the preferred emergency path is to switch to the replication server first and rebuild the original primary server afterward.

For minimum downtime, option 3 is usually the best choice. For smaller or simpler installations, option 2 is usually the best compromise between effort, safety, and recovery time. Option 1 is practical for simple single-server installations, provided that all relevant disks and configuration data are really included in the VM backup.

7.5. Information about the SSL Certificate of the WebPQ Web Server

The application you are using requires certificates and keys in PEM format (Privacy-Enhanced Mail). PEM is a standardized format for storing and transmitting cryptographic data, such as certificates, private keys, and public keys.

What is the PEM format?

The PEM format is a text format that encodes cryptographic data and represents it as Base64-encoded strings. These data are surrounded by "Begin" and "End" markers to denote the different types of cryptographic information.

Example:

A certificate in PEM format looks like this:

-----BEGIN CERTIFICATE----- MIIDdzCCAl+gAwIBAgIEU1mW... ...klrjDffKwF2MnPxgt1h0DA== -----END CERTIFICATE-----

A private key in PEM format looks like this:

-----BEGIN PRIVATE KEY----- MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQ... ...jJTZMOyPyjxVrM52mf6w== -----END PRIVATE KEY-----

Why PEM?

The PEM format is often used because it is easily readable and simple to handle. It allows for easy storage of certificates and keys in a text file that can be used in various applications and servers. How to use certificates and keys in PEM format?

• Provide certificates and keys: Ensure that you have received the appropriate certificates and keys in PEM format. These are usually provided by a Certificate Authority (CA) or your IT security system.

• Embed files: To use the certificates and keys in your application, you need to insert them into the appropriate configuration files or specify the path to the files in the application settings.

• Observe security: Ensure that private keys are stored securely. They should never be placed in insecure areas or made accessible to unauthorized users. The private key can also be protected with a password passphrase to provide additional security.

Encryption:

If the key in PEM format is encrypted, a password can be entered in the application to decrypt and use the key.

Example:

An encrypted private key in PEM format might look like this:

-----BEGIN ENCRYPTED PRIVATE KEY----- MIIEpAIBAAKCAQEA7JzQ+opZX7bPmnB6BBQ5mQgCvZvXq4bD8+Gm3kmK2b7HLkn7 ... -----END ENCRYPTED PRIVATE KEY-----

In this case, the private key is encrypted with a passphrase. When someone tries to access this key, they will be prompted to enter the passphrase to enable decryption.

Common Issues:

• Incorrect Format: If the certificate or key is not in the correct PEM format, the application may not accept it. Make sure you have received the files correctly.

• Invalid or Expired Certificates: Check the expiration date and validity of the certificate to ensure it is still valid.

If you have any further questions regarding certificates or keys in PEM format, please contact support.

8. Updates

The WebPQ software is continuously developed. Within the license period of 12 months, updates are free of charge and can be downloaded directly from the homepage
www.a-eberle.de.

It is recommended to always install the latest version to close security gaps and take advantage of new features. For patch management, A. Eberle GmbH provides a customer portal:
https://www.a-eberle.de/news/anmeldung-kundenportal/

8.1. Installation of the Update

The update can be installed directly via the installation routine. Administrative rights are required for this.

8.1.1. WebPQ Update

To install the update, proceed as follows:

• Download the latest file from the homepage www.a-eberle.de.

• Start the installation routine.

• Follow the instructions of the installation wizard.

• Restart the software to apply the changes.

If the update entitlement of the currently stored license has expired, the installed system can still continue to run, but newer updates require a renewed license or maintenance extension.

If the installer or the running system requests a new license, load the renewed JSON license and complete activation again if WebPQ asks for it.

	Back up your database before each update to avoid data loss!
Note

8.1.2. Database Backup

If the database is operated via PostgreSQL, you can back up the database as follows:

• Open the pgAdmin program.

• Right-click on the database.

• Select Backup.

• Choose the storage location and confirm with OK.

A continuously updated PostgreSQL backup mirror using streaming replication can increase resilience further. However, this replication does not replace a classic backup before updates. For production systems, it is recommended to combine a replication server with additional regular database backups. An example setup of the backup mirror is described in the installation chapter under PostgreSQL Backup Mirror with Streaming Replication.

8.2. Support in Case of Service Issues

If you have problems or questions, please contact A. Eberle Support:

Service Address:

A. Eberle GmbH & Co KG
Frankenstraße 160
D-90461 Nuremberg

Regular updates ensure the security and optimal performance of the software.

9. Product Warranty

A. Eberle guarantees that this product will remain updatable for a period of 12 months from the date of purchase.

The warranty does not cover damages caused by the following:

• Accidents

• Misuse

• Abnormal operating conditions

To claim the warranty, please contact A. Eberle GmbH & Co. KG in Nuremberg.

A. Eberle GmbH & Co. KG Frankenstraße 160
D-90461 Nuremberg
Tel.: +49 (0) 911 / 62 81 08-0 Fax: +49 (0) 911 / 62 81 08 99
E-Mail: info@a-eberle.de

www.a-eberle.de

10. Release Notes

Note: The following pages contain the release notes for the WebPQ software and the REST API. Please note that these release notes may not always reflect the current state of the software version. With software updates, it may happen that the present description is no longer accurate in some points. In this case, please contact us directly or use the latest version of the release notes, which you can find on our website www.a-eberle.de.

Publisher:
A. Eberle GmbH & Co. KG Frankenstraße 160 D-90461 Nürnberg

10.1. WebPQ Releases

10.1.1. Recommended Device Firmware

10.1.2. Database Patches

Patches for the deployed PostgreSQL database are provided via a separate update process. You can find the latest patches in the download center under "WinPQ" in the "PostgreSQL Patches" section, as well as in the program directory under /PostgreSQL Update/ in the update folder of the WebPQ installation. The full version of the WebPQ system software always includes the latest database version available at the time of release.

Starting with this update, it is recommended to use PostgreSQL v14.21.

10.1.3. WebPQ 2.2.0 - Major Release

Primary Tracking Ticket / Topic Reference

• [#9912] Documentation and summary of the main WebPQ user-facing capabilities added since w-2.1.1. No separately labeled epic issues for 2.2.0 could be identified for this version, so the overarching tracking ticket is used as the reference.

News, Features, and Improvements

• PQI-D support: Support for PQI-D devices has been extended. This includes creating PQI-D devices, taking over detected device data, and supporting readout operations for PQI-D devices.

• WinPQ device import: Importing existing WinPQ devices was expanded and aligned more closely with the current device management.

• PQ-Box integration: PQ-Box data can now be integrated into WebPQ with shared data class logic and clearer assignment behavior.

• COMTRADE import: COMTRADE import is available as its own import path and covers add-on visibility, device assignment, supported file groups, and import logging.

• Map View: Map View was expanded functionally and made clearer to use for setup, filtering, and navigation.

• Group dashboards: Shared dashboards for groups were extended so content can be shared and maintained in a more structured way.

• Language support: The supported user interface languages were extended or updated further. This broadens WebPQ's suitability for international use.

• FFT analysis: FFT analysis was expanded for both historical data and live data.

• Custom-threshold utilization analysis: The utilization analysis for custom thresholds was extended and integrated more clearly into the analysis area.

• DFR and PQ events: Working with disturbance records and PQ events was improved in selection, evaluation, and follow-up processing.

• Automation tasks: Automation tasks can now address devices both directly and through tags and tag categories.

• Reporting and printing: Reports and print outputs respect tenant-specific logos and page formats.

• Export system: Automated exports appear in the same export overview as manual exports.

• OT/IT data synchronization: Synchronization between OT and IT systems was refined for current operational requirements.

• OAuth login: OAuth login was extended for current sign-in and consent processes.

• License activation: License activation was aligned with the current product state, including grace-period and reactivation behavior.

• Device settings and parameterization: Device metadata handling, connection tests, time-zone recalculation, and schema-based parameter editors were improved further. For PQ Smart, the import/export behavior and the handling of transformer factors were also extended.

• Swagger/OpenAPI for administrators: Administrative access to Swagger/OpenAPI was clarified and aligned with the current security model.

Additional Important Enhancements

• Export management: Exports that are not yet completed are cleaned up, while older exports that were already completed remain available and can still be downloaded.

• COMTRADE import: Warnings, failure cases, and the integration of COMTRADE import into the general import area were extended.

• Export diagnostics: Failed exports can be traced in the export area and through matching Syslog entries.

Important Bug Fixes

• Printing and reports: Pagination in PDF reports works correctly again, and reports are generated only after the required report elements have fully loaded.

• Automation tasks: Historical disturbance records are sent reliably again after changes to the device time settings.

• Export operations: The traceability of failed exports in the export area and through matching Syslog entries was improved. This simplifies root-cause analysis during operation.

Security-related Content and Adjustments

Applicable or release-relevant security issues:

• [#9729] CVE-2026-33894: classified as a release-relevant security fix related to certificate validation.

• [#9872] GHSA-6v7q-wjvx-w8wg: relevant security fix for a runtime dependency used by WebPQ.

Not applicable or not release-relevant security issues:

• [#9726] CVE-2026-33895: not release relevant because the affected Ed25519 verification path is not used in WebPQ.

• [#9728] CVE-2026-33891: not release relevant because no reachable code path was found where untrusted zero input reaches BigInteger.modInverse().

• [#9730] CVE-2026-33896: not release relevant because pki.verifyCertificateChain() is not used in WebPQ and trust checks rely on X509Certificate.verify.

10.1.4. WebPQ 2.1.8

Security-related content and adjustments

Non -critical security issues fixed in this release:

• [#9801] CVE-2026-35042 - Security fix

• [#9802] CVE-2026-34950 - Security fix

• [#9872] GHSA-6v7q-wjvx-w8wg - Security fix

10.1.5. WebPQ 2.1.7

News, Features, and Improvements

• [#9513] Initialization/Migration command-line script added for migration of Docker containers

• [#9508] Docker image tags extended with release branch prefix

• [#9593] License activation optimized after license update or license upgrade

• [#9459] Error when deleting devices fixed – statement timeout optimized

Security-related content and adjustments

• [#9627] CVE-2026-33036: Security fix - Severity: Medium (4.9) - see Security Advisories

• [#9729] CVE-2026-33894: Security fix - Severity: Low - see Security Advisories

Non-critical security issues fixed in this release:

• [#9402] CVE-2026-27837: Security fix

• [#9426] CVE-2026-2359: Security fix

• [#9425] CVE-2026-3304: Security fix

• [#9453] GHSA-qffp-2rhf-9h96: Security fix

• [#9462] CVE-2026-3520: Security fix

• [#9463] CVE-2026-27601: Security fix

• [#9464] CVE-2026-29063: Security fix

• [#9549] CVE-2026-27904: Security fix

• [#9551] CVE-2026-27903: Security fix

• [#9550] CVE-2026-31808: Security fix

• [#9550] CVE-2026-30951: Security fix

• [#9550] CVE-2026-31802: Security fix

• [#9580] CVE-2026-32630: Security fix

• [#9651] CVE-2026-33349: Security fix

• [#9704] CVE-2026-33672: Security fix

• [#9706] CVE-2026-33671: Security fix

• [#9731] CVE-2026-33916: Security fix

• [#9732] GHSA-c7w3-x93f-qmm8: Security fix

• [#9727] CVE-2026-33750: Security fix

• [#9728] CVE-2026-33891: Security fix

• [#9726] CVE-2026-33895: Security fix

• [#9730] CVE-2026-33896: Security fix

10.1.6. WebPQ 2.1.6

News, Features, and Improvements

• [#9383] Device counting routine for license check optimized for UU devices

• [#9293] API license check for REST API optimized

• [#9328] Improvements in measurement values during import with infinity values

10.1.7. WebPQ 2.1.5

Security-related content and adjustments