Version 1.0

Effective from May 07, 2025

Service-Specific Terms

These Service-Specific Terms are an integral part of Fentrica’s overall Terms and Conditions.

Platform Services

1. Edge Devices

Definition and Ownership
Edge Devices are hardware components either manufactured by Fentrica or certified by Fentrica. These devices are owned by the customer and are installed on-site by the customer.

Access and Authorization
Fentrica does not have access to the Edge Device unless the customer, or someone acting on behalf of the customer, authorizes access and the necessary authorization keys are exchanged.

Functionality
The Edge Device establishes a secure tunnel to the Fentrica Cloud and is responsible for caching data, as well as directly controlling and monitoring Technical Systems on-site.

Security Connection
Fentrica ensures that authorization must also be established on the Edge Device to ensure secure access. Fentrica ensures that connection is be done over a secure tunnel.

Technical System Connection Configuration
Fentrica stores information about Technical System connection details, such as protocols and authentication information. However, the configuration of these Technical System connections is performed by the customer or someone acting on behalf of the customer. Fentrica is not responsible for these configurations, and it is the customer’s responsibility to verify their accuracy and functionality.

Error Handling
If device connection fails or is offline, Fentrica will provide an error alarm on the platform to notify the customer. Fentrica is not responsible when device connection fails or is offline except where otherwise provided under the applicable Terms and Conditions.

2. Technical Systems

Visualization and Real-Time Control Interface
Fentrica provides a visualization and real-time control interface for technical systems. This interface connects directly over a secure tunnel using an Edge Device to the technical system (e.g., solar panel inverter, HVAC unit).

Scheduling Capabilities
Technical systems can be configured with both dynamic and static schedules. Dynamic schedules allow for the adjustment of technical system datapoints based on predefined rules. For example, a schedule can be set to turn off a technical system at specific times and dates.

Alarm Monitoring
Fentrica offers alarm monitoring for technical systems, enabling the detection and notification of system anomalies.

Connection Responsibility
Fentrica is not responsible for establishing or restoring the connection to the technical system except where otherwise provided under the applicable Terms and Conditions. Connections are facilitated solely through the customer’s Edge Device located on-site. Fentrica ensures that the platform alerts the customer if the connection to the device or technical system is unavailable.

Configuration Responsibility
All configurations are to be performed by the client or on behalf of the client. Fentrica is not liable for any configuration errors. If Fentrica performs the configuration, the customer must verify and approve the configurations.

Data Retention
Data collected from technical systems is retained on the Fentrica platform for a period of 12 months. After this period, data may be archived or deleted in accordance with Fentrica’s Privacy Policy.

3. Dynamic Schedules

Rule Definition
For technical systems with dynamic schedules, each rule can be defined by the client or on behalf of the client. These rules are based on data stored on the platform (e.g., data from App Integrations) and can be defined using Fentrica Expression Language (FEXL), a context-based expression parser and evaluator.

Scheduling Granularity
Dynamic schedule rules can be defined with an hourly step granularity.

Examples of Dynamic Schedule Rules

• If the Energy Prices App Integration indicates negative energy export prices, the system can be configured to disallow energy export during those hours.
• If the Weather Forecast App Integration predicts significantly warmer weather for the next day, the system can be set to turn off the outdoor pool heater.

Error Handling
If the generation of dynamic schedule rules fails, Fentrica will provide an error alarm on the platform to notify the customer.

Responsibility for Rule Definitions
Fentrica is not responsible for errors in the definition of dynamic schedule rules.

Data Retention
Data utilized for dynamic schedule rules is retained on the Fentrica platform for a period of 12 months. After this period, data may be archived or deleted in accordance with Fentrica’s data retention policies.

4. App Integrations

Third-Party Integrations
The Fentrica platform offers several third-party app integrations. These integrations allow data to be sent from the Fentrica platform to an App Service or stored in the Fentrica platform from an App Service. App Integrations are available on the platform under the “App Integrations” section. App Integrations are created by the client or on behalf of the client.

Personal Data Handling
If an app integration involves the exchange of personal data, the customer must have agreed upon data storage and exchange information by App Integration provider and is responsible for the data. Fentrica acts as a data processor and processes only the data that the customer has configured and only with the client’s consent.

Examples of App Integrations
App integrations can include, but are not limited to, Weather Forecasts, Energy Prices, Hotel Bookings, Rental Agreements, Energy Forecasts, Metering Data, and Demand Response Bids. Each integration specifies the data exchanged between the App Integration and the Fentrica platform.

Error Handling
Fentrica will inform the customer through the platform with an alarm if the app integration is not working or is offline. Fentrica is not responsible when app integration is not working or is offline except where otherwise provided under the applicable Terms and Conditions.

Responsibility for Rule Definitions
Fentrica is not responsible for inaccurate data from App Integrations.

Data Retention
Data obtained from App Integrations is retained on the Fentrica platform for a period of 12 months. After this period, data may be archived or deleted in accordance with Fentrica’s data retention policies.

5. Virtual Cloud Meters

Virtual Cloud Meters
The Fentrica platform can utilize virtual cloud meters that generate metering data based on existing data.

Metering Granularity
Cloud meters can be defined with an hourly step granularity.

Definitions
Cloud meters can be defined using Fentrica Expression Language (FEXL), allowing for complex calculations and data transformations based on existing platform data.

Examples of Cloud Meters

• Calculating carbon footprint based on actual energy usage and carbon factor.
• Calculating revenue based on exported energy and energy market prices.

Error Handling
If the generation of cloud meter data fails, Fentrica will provide an error alarm on the platform to notify the customer.

Responsibility for Definitions
Fentrica is not responsible for errors in the definition of cloud meters.

Data Retention
Data generated by cloud meters is retained on the Fentrica platform for a period of 12 months. After this period, data may be archived or deleted in accordance with Fentrica’s data retention policies.

Limitation of Liability

To the fullest extent permitted by applicable law, Fentrica’s total cumulative liability arising out of or related to these Service-Specific Terms, whether in contract or otherwise, shall not exceed the total fees paid by the customer to Fentrica.