Alarm Routing Configuration to Two Servers for a Sigma - Building Operation Transition

[Product_Support]

Issue

Ensuring correct alarm routing when operating both Sigma and EcoStruxure Building Operation (EBO) together following a transition

Product Line

Satchwell BAS & Sigma

Environment

• Satchwell Sigma
• Building Operation

Cause

During a transition, alarms must be routed to both the Sigma Client and the SBO Enterprise Server (ES). Misconfiguration can lead to alarms not being received correctly.

Resolution

To route alarms to both systems:

1. Add the ES Server to the Sigma Network

   • In addition to the main Sigma Server, manually add the Enterprise Server (ES) as a Server (node).
   • Use the actual ES server name for clarity and consistency.
   • Example:
     • Server 101: Sigma Server
     • Server 102: ES Server

       

2. Create a Dummy Sigma Client for the ES

   • Manually add a dummy Sigma Client representing the ES.
   • Assign the ES server to this client. 

3. Verify Sigma Server Settings

   • Ensure the Sigma Server configuration is correct and supports dual routing.

     

4. Configure RouteSets

   • Add both the Sigma Client and the dummy ES Client to the RouteSets.
   • This enables alarms to be sent to both servers.

     

5. Distribute Configuration Files

   • Download and distribute the following files to all outstations:
     • routeset.rec
     • att.set

---

⚠️ Important Notice

Sigma is not supported in EBO 2022 and later.
To continue supporting Sigma devices, you can implement a multi-version system:

• Keep Enterprise Servers with Sigma devices on Building Operation 3.2.
• Add a Building Operation 2022 or later Enterprise Central
• Upgrade the rest of the system to Building Operation 2022 or later.

You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.