Minimum Requirements

• OS: Ubuntu (preferred) + Docker
• HDD: 20GB + 80 GB
• RAM: 8 GB
• CPU: 2x

• Desktop
  • Safari
  • Google Chrome
  • Firefox
  • Opera
  • IE (>11)
  • Edge
• iOS
  • Safari
  • Google Chrome
  • Mobile Application
• Android
  • Google Chrome
  • Mobile Application

This section outlines the system requirements and supported technologies for configuring alerts and notifications (Push and Email) within a Mervis SCADA On-Premises environment.

To enable mobile push notifications in an on-premises deployment, please note the following architectural requirements:

• Installation on Request: The push notification service is currently not included in the main Mervis SCADA installation package. It is installed on request as a separate system component.
• Dedicated Account Routing: You must configure a separate, dedicated account to route these notifications. This account must not be connected to your standard Mervis account.
• Firebase Account & Network Access: The server hosting the notification service requires an active outbound internet connection to communicate securely with the Firebase API. Additionally, your company must set up its own Google Firebase account and provide the necessary project credentials to enable this routing.

Mervis SCADA supports both standard and modern authentication methods for sending automated email alerts.

• Basic SMTP Auth: Traditional SMTP authentication using a standard username and password is fully supported out of the box. Note: Your company must provide its own SMTP server (e.g., an internal mail server or a third-party email provider). Energocentrum does not provide an SMTP server for on-premises installations.

For IT environments that mandate strict modern security standards, Mervis supports OAuth 2.0. This is specifically required for modern cloud email providers like Microsoft Office 365 and Google Workspace.

To use OAuth 2.0 with Office 365, you must register Mervis as an application in the Microsoft Entra ID (formerly Azure AD) portal.

1. 1. Enable SMTP Auth: First, ensure that authenticated client SMTP submission is enabled for the specific mailbox you intend to send emails from.
2. 2. App Registration: Register a new application in the Microsoft identity platform.
3. 3. Configure Redirect URIs: Navigate to the Authentication tab and add the appropriate Redirect URIs (Note: localhost is required for .NET core):
   • .NET desktop: https://login.microsoftonline.com/common/oauth2/nativeclient
   • .NET core / .NET 5+: http://localhost

1. 4. Configure API Permissions: Navigate to the API permissions tab. Click Add a permission, select Microsoft Graph, choose Delegated permissions, and add the following required scopes:
   • email (View users' email address)
   • offline_access (Maintain access to data you have given it access to)
   • IMAP.AccessAsUser.All (Read and write access to mailboxes via IMAP)
   • POP.AccessAsUser.All (Read and write access to mailboxes via POP)
   • SMTP.Send (Send emails from mailboxes using SMTP AUTH)
   • User.Read (Sign in and read user profile)
2. 5. Grant Admin Consent: Once the permissions are added, you must click the Grant admin consent button for your domain to fully authorize the application.

Once consent is granted, ensure that all the required permissions show a green “Granted” status:

Google accounts are also supported via OAuth 2.0. Similar to Microsoft, this requires setting up an OAuth Client ID in the Google Cloud Console and generating the appropriate tokens to allow Mervis to send emails on behalf of the Gmail account.