Schneider EcoStruxure Server Driver for Tridium Niagara

The Schneider EcoStruxure Server driver turns a Tridium Niagara instance (JACE or Supervisor) into an EcoStruxure Web Services (EWS) server. EcoStruxure AS-P / AS-B controllers and Enterprise Server (ES) software discover the Niagara station as if it were another EcoStruxure source, then read points, write set-points, pull histories, and subscribe to alarms via the standard EWS protocol – without any reconfiguration on the Niagara side or extra Schneider licenses.

The use case is reverse-direction integration. Most Niagara projects pull data from Schneider equipment using the EcoStruxure Driver. The Server driver is for the less common scenario where Schneider’s EcoStruxure system is the supervisory front-end and Niagara is the data source – typically because the customer has standardised on EcoStruxure as the corporate BMS but has Niagara-managed sites or buildings that need to feed data upward into that supervisory layer.

A common deployment pattern is corporate estate consolidation. The customer runs EcoStruxure at headquarters as the global BMS standard but has subsidiary or recently-acquired sites built on Tridium Niagara. Rather than rip and replace those sites, the Server driver lets each Niagara station expose its full point catalogue to the EcoStruxure ES, so the corporate operations centre sees every site’s data in a single platform.

Another pattern is multi-protocol gateway. A Niagara station fronts non-Schneider field equipment – Automated Logic WebCTRL, Siemens Apogee P2, Cylon Unitron, Trend IQ, OCPP chargers, or any other Niagara-supported protocol – and republishes the unified data to EcoStruxure as if it were native. Schneider integrators get full multi-vendor reach without re-engineering EcoStruxure itself or maintaining parallel BMS systems.

Technically, the driver implements the EWS specification over HTTP. On the EcoStruxure side, configuration consists only of pointing AS-P, AS-B, or ES at the Niagara station’s IP address and EWS port. From there, EcoStruxure discovers the published Niagara points, names, and structures the same way it discovers any other EWS source. The driver auto-publishes Niagara points selected by the integrator – typically through Niagara station hierarchy or tagging – so the EcoStruxure side sees only what the integrator wants to expose. Niagara station logic, schedules, and histories continue running unchanged; the EWS server is purely additive.

Authentication and transport security follow the EWS specification. There are no licensing dependencies on Schneider PME or SmartStruxure, and no agent or middleware on the Schneider side. Existing Niagara installations can be retrofitted by adding only the EWS server module; AS-P and ES already speak EWS natively.

If your project goes the typical direction – EcoStruxure as the source, Niagara as the destination – see the main Schneider EcoStruxure Driver.