Standalone CCU Operation

| Introduction

The Standalone CCU operation mode is an enhancement added to the Airoverse system. With this, the CCU can operate in a standalone mode without an internet connection, able to monitor and control equipment at terminal and system levels.

The CCU standalone operation mode is a whole new concept built within the Airoverse ecosystem where the system works just like the online mode but without the need for remote monitoring and control cloud connection on portals & apps.

| Standalone Operation Trigger

The standalone operation mode enablement is provisioned in the installer options screen in the CCU, as below.

| Change in CCU Registration Process

To enable a CCU in standalone operation mode, the CCU needs to be registered. 

The registration is done with an internet connection, and once the registration is done the standalone mode can be enabled from the installer option screen, as below:

The CCU standalone operation mode is driven from the newly added point in the system "offlinemode".

The offlinemode point is created with every CCU registration. Based on whether the offline mode toggle is enabled or disabled, a different enum is assigned to the point for the system to understand whether the CCU is enabled for a standalone operation or connected to a cloud operation.

This point and the change in the enum value of the point lets the portals accommodate the changes for a CCU when enabled for standalone operation.

Once the toggle is enabled the CCU enters standalone mode with the cloud connection status changed to offline in the notification bar and the zones page, as below:

Despite the CCU having access to an active internet connection before it could completely cut off that access.

| Change in the Schedules

With the standalone mode, the users can edit the schedules, set vacations, and edit building limits.

The CCU registers with the default named schedule just like any other CCU, but with the standalone mode enabled the default named schedule becomes editable, as below.

Note: Post migration to scheduler revamp whenever a new zone is paired, the same will have the default named schedule as its default schedule

The same can be edited from the scheduling screen in the CCU, as below.

Users can modify schedules, as below.

Modify and set user limits, as below.

No other named schedule available for the site is editable, as below.

| Change in the Building Occupancy & Building Limits

Users can edit the building occupancy while in the standalone mode from the installer options screen, unlike the online mode as below.

Users can add or edit occupancy, as below.

Users can also edit the building limits from the installer option screen as below.

Note: All The validations for building limits hold with the data that is available locally.

| Change in the Backfill

The Backfill time is auto-set to none when the Standalone mode is enabled as below and remains editable though.

| CCU Deletion Icon for Standalone Mode

If a CCU is offline for more than 6 days and above, the CCU is eligible for deletion. But the same isn't applicable to a CCU in a standalone mode. Hence no delete icon is available when a CCU is present in standalone mode.

| OAO

The OAO operation in the HSS and other profiles also is dependent on the weather data to provide free cooling. and since the weather data from the internet is not available for a standalone mode. The OAO operation is handled based on alternate sensors available, or other data approaches.

| Mechanical Lockout

Mechanical Cooling/heating lockout is disabled if the standalone mode is enabled.

Considering the standalone operation of the CCU, the weather data from the internet is not available.

Hence the Mechanical lockouts are handled based on alternate sensors available or the prescribed default values that are measured before the CCU was enabled for the standalone operation.

| WatchDog Timeout Tuner

The tuner CCU Network Watchdog Timeout (MIN) is auto-set to 0 with the standalone mode enabled, as below.

Note: This tuner defines the time after which the CCU auto reboot needs to be triggered when the CCU is been offline. Since the CCU here is set to standalone operation mode, there is no need for an auto-reboot of the CCU, hence the same is set to "0".