System Manager

| Overview

The System Manager is a new system profile that enables centralized configuration and management of system-level devices from a single interface. Unlike the traditional Default System Profile, which manages device types independently, System Manager combines multiple communication and control technologies into a unified configuration workflow.

The profile provides integrated support for:

• Modbus devices
• BACnet devices
• Connect Modules

This consolidated approach simplifies deployment and lays the foundation for future system-level control sequences involving multiple equipment types.

| Purpose

System Manager provides a centralized configuration environment where administrators can:

• Configure multiple communication protocols from a single profile.
• Pair Modbus devices.
• Initialize and configure BACnet devices.
• Add and manage Connect Modules.
• Build complex system-level integrations that span multiple device technologies.

The feature is designed to support future advanced equipment management and sequencing capabilities while maintaining the existing device pairing experience.

| Prerequisites

Before configuring devices in the System Manager profile, ensure that:

• The controller is online.
• Required communication hardware is connected.
• USB-to-RS485 adapters are connected when pairing Modbus devices.
• BACnet has been initialized before attempting BACnet device configuration.
• Appropriate user permissions are available.

| Accessing System Manager

• Navigate to System Configuration.
• Select System Profile.
• Choose System Manager.

The System Manager page displays three independent configuration sections:

• Modbus
• BACnet
• Connect Modules

Each section can be configured independently while remaining part of the same system profile.

| System Manager Layout

The System Manager interface is divided into three functional areas.

Modbus

Provides configuration and pairing of Modbus devices.

Available action:

• Add Modbus Device

The pairing workflow remains identical to the existing Modbus pairing process to ensure a familiar user experience.

BACnet

Provides BACnet network configuration.

Before any BACnet device can be configured, the BACnet stack must first be initialized.

If BACnet has not yet been initialized, the interface displays an initialization prompt instead of the device configuration options.

After successful initialization, BACnet device configuration becomes available.

Connect  Modules

Provides configuration of Connect Modules.

Available action:

• Add Connect  Module

The Connect  Module workflow is unchanged from previous implementations.

| Pairing a Modbus Device

• Open System Manager.
• Navigate to the Modbus section.
• Select Add Modbus Device.

• Complete the standard Modbus pairing workflow.

• Select the model to add as a Modbus device from the select model drop-down.

• Configure the points for display and schedulable points.

• Click Save to save the configuration.

The Modbus device configuration gets saved as below.

• Use the edit Icon to reconfigure or modify the set configuration details, and delete icon to delete the configuration.

• Click Save to confirm the Modbus device configuration in the profile, and start exploring in the site explorer in the portals.

| Configuring a BACnet Device

• Open the BACnet section.

If BACnet has not been initialized, the interface prompts the user to initialize BACnet.

• Complete BACnet initialization.
• Set the required parameters for more information on how to configure the required details, refer to CCU as BACnet IP Client
• Click Initialize BACnet to initialize.

BACnet configuration options are unavailable until initialization completes successfully.

• Configure BACnet devices.
• Click Add BACnet Device.

• Select the model to add as a BACnet device from the select model drop-down.

• Configure the points for display and schedulable points.

• Select the communication mode IP.

• Select the Auto Address setting mode.

• Select the device to auto-set the addresses.

The details are auto-set based on the device selected.

• Click Save to save the configuration.

The BACnet device configuration gets saved as below.

• Use the edit Icon to reconfigure or modify the set configuration details, and the delete icon to delete the configuration.

• Click Save to confirm the BACnet device configuration in the profile, and start exploring in the site explorer in the portals.

| Adding a Connect  Module

• Open the Connect  Module section.
• Select Add Connect  Module.

• Configure the module as required.
• Pair the Connect Module device using the steps provided.
• Click Pair to start pairing

Once paired and saved, the Connect Module device configuration gets saved as below.

• Use the edit Icon to reconfigure or modify the set configuration details, and the delete icon to delete the configuration.

• Click Save to confirm the Connect Module device configuration in the profile, and start exploring in the site explorer in the portals.

| System Details

Once all the deivces are paired the data for the devices can be visulaized in the system screen in CCU, as shown below.

Modbus device data

BACnet device data

Connect Module device data

| Pushing Sequences to Connect Module 

Note: The Connect module device data is empty since there are no sequences pushed for the module from the sequencer. For information on how to create and push a sequence to a Connect module, refer to the Device Configuration in Site Sequencer section in Connect Module as Zone

• Push the sequence to the configured Connect module.

• Click Push to Devices in the pop-up window displayed.

• Select the Connect module paired in the device selection window.
• Click Apply Sequence to confirm.

The sequence gets puhsed to the Connect module successfully as below.

| Connect Module Device Data in System Page

To visualize the connect module device data in system page.

From the System Config screen, Connect module device configuration section.

• Use the edit Icon to set sequencer pushed parameters for display.

• Enable schedulable points and points for display.

• Click Save to confirm the configurations.

The configurations get saved successfully as below.

• Click Save to finish.

Once saved, the same can be visulaized in the system page in CCU as below.

| USB Connection Validation

When pairing a Modbus device, the system validates the presence of a USB communication interface.

Connect and configure the USB via USB manager as shown below.

If no supported USB communication device (for example, an RS485 interface) is detected, the system displays a warning.

Example warning:

No communication port detected. Please verify the USB connection in USB Manager.

This warning informs the user that communication hardware is unavailable.

Important

The warning is non-blocking.

Users are still permitted to save the configuration, allowing offline or staged configuration before physical hardware is connected.

| Capabilities

System Manager provides the following capabilities:

| Validations

Modbus Validation

The system validates that a communication interface is available.

Validation performed:

• USB communication interface detected.
• RS485 interface available

If validation fails:

• A warning message is displayed.
• User may continue configuration.
• Save operation remains available.

BACnet Validation

The system validates whether BACnet has been initialized.

If BACnet is not initialized:

• Device configuration is unavailable.
• Initialization prompt is displayed.

Once initialization completes:

• BACnet configuration becomes available.

Connect  Module Validation

Connect  Module configuration follows the existing validation rules currently implemented for Connect  Modules.

| User Experience Considerations

The feature intentionally preserves existing workflows wherever possible.

For example:

• Modbus pairing remains unchanged.
• Connect  Module configuration behaves exactly as before.
• Only BACnet introduces a prerequisite initialization step.

This minimizes user retraining while introducing additional capabilities.

| Usage Notes

• System Manager does not replace the underlying protocol implementations.
• Each protocol continues to function independently within a unified configuration interface.
• Users can configure only the sections relevant to their deployment.
• Missing communication hardware does not prevent saving configuration.
• BACnet must always be initialized before BACnet devices can be configured.

| Expected Behaviour

Successful Modbus Pairing

• User selects Add Modbus Device.
• Device pairing completes.
• Configuration is saved successfully.

Missing USB Communication Interface

• User starts Modbus pairing.
• No USB communication interface is detected.
• Warning message appears.
• User may still save the configuration.

BACnet Not Initialized

• User opens the BACnet section.
• Initialization prompt is displayed.
• Device configuration remains unavailable until initialization completes

Connect  Module Configuration

• User selects Add Connect  Module.
• Existing Connect Module workflow opens.
• Configuration behaves as in previous releases.

| Future Expansion

System Manager has been designed as the foundation for future system-level equipment orchestration.

Planned and anticipated use cases include:

• Boiler control
• Chiller control
• Pump sequencing
• Advanced equipment sequencing
• Connect Module-based system control
• Multi-device control algorithms
• Integrated system-level automation

As these capabilities become available, additional Connect Module profiles and system control sequences can be incorporated into the System Manager framework without requiring changes to the overall user experience.

| Acceptance Criteria

The feature is considered successful when:

• A System Manager profile is available in System Configuration.
• Modbus, BACnet, and Connect Modules are accessible from a single profile.
• Modbus pairing functions identically to the existing implementation.
• BACnet configuration is gated behind successful initialization.
• Connect  Module configuration remains unchanged.
• Missing USB communication hardware generates a warning.
• The warning does not prevent configuration from being saved.
• Existing functionality for each supported protocol remains backward compatible.