mail@mabbaz.com Abu Dhabi, UAE

Building Management Systems · Building automation suite

EcoStruxure Building Operation

by Schneider Electric

Schneider Electric building management software for large buildings, formerly StruxureWare Building Operation, engineered as one system with the SpaceLogic automation server and controller family.

On-premises, Hybrid Commercial Last reviewed 7 November 2026 Documentation-based
Visit product site

What it is

EcoStruxure Building Operation, often abbreviated EBO and formerly marketed as StruxureWare Building Operation, is Schneider Electric building management software. Schneider describes it plainly as building management system software for large buildings, with the purpose of increasing energy and operational efficiency through monitoring, management and control of building systems from one mobile-enabled control centre.

It is genuinely software, but it is sold and engineered inside a hardware system and Schneider own pages blur the boundary. The software tier is an Enterprise Server plus two clients, the thick WorkStation engineering client and the browser-based WebStation, and Schneider notes secure web clients that need no software installation. Around it sits the SpaceLogic family that the current launch page actually leads with: AS-P and AS-B Automation Servers, MP-C Plant Room Controller, RP-C and MP-V Room Controllers, IP/IO and Central I/O expansion modules, Advanced Display and Operator Display, plus an optional Sustainability Pack. Schneider own words on a regional page are that a building management system is comprised of software and a collection of hardware. That is why this profile classifies EBO as an integrated vendor automation suite rather than a vendor-neutral head-end, although the Enterprise Server alone does function as a classic supervisory head-end and a reviewer could reasonably argue the other way.

On openness, Schneider states the broadest open-protocol list of any vendor page read in this research and is the only major head-end vendor to name MQTT on its own page: BACnet, LonWorks, Modbus, web services and MQTT, plus Smart Connector APIs with an SDK and EcoStruxure Web Services as Schneider own interchange standard. Domain coverage is unusually wide at the energy end, reflecting Schneider power base: HVAC, lighting, security and fire alongside power, microgrids, renewables, EV charging and metered energy data, with customisable dashboards giving views from device to portfolio level and automation servers providing local alarm supervision.

Security is the most concretely described of the major head-ends: a secure development lifecycle, BACnet SC certificate management, stated compliance with current industry cybersecurity requirements, and web clients that need no local install. Data modelling is modern too, with Brick Schema semantic tagging and open-source-format databases, which eases analytics and downstream integration.

The diligence problem is real and should be weighed. The official product help portal at ecostruxure-building-help.se.com returned HTTP 403 Forbidden to automated access, the iportal.se.com specification-sheet host returned 403, and the se.com download path for the Enterprise Server specification sheet returned 404. Buyers can read marketing but cannot verify specifications without a login or a Schneider contact. The publicly circulating Enterprise Server specification sheet dates from 2019 while firmware 6.0.1 is indexed against a 2024 BACnet PICS, and the current US launch page does not even list Enterprise Server, Enterprise Central, WorkStation or WebStation, presenting SpaceLogic hardware instead. No point counts, server-tier limits or concurrent-user ceilings appear on any reachable page.

Capabilities

Each capability carries its own verification status. “Not verified” means exactly that: it has not been checked, and must not be read as absent.

CapabilityStatusNotes
Third-party system integration Integration with systems outside HVAC, such as fire, access control, CCTV or CMMS. Yes Native open protocol support out of the box plus Smart Connector APIs with an SDK. source
Multi-building and enterprise scale Operating a portfolio of buildings from one platform. Yes Dashboards give views from device to portfolio level. source
Edge controller management Managing and programming edge or field controllers from the platform. Yes SpaceLogic AS-P and AS-B automation servers, MP-C plant room controller, RP-C and MP-V room controllers, IP/IO expansion modules. source
Remote and browser access Browser or remote client access for operators. Yes Mobile-enabled control centre; secure web clients requiring no software installation. source
Cybersecurity features Documented security features such as encryption, authentication and hardening guidance. Yes Secure development lifecycle, BACnet SC certificate management, stated compliance with current industry cybersecurity requirements, secure web clients with no install. source
Historical data and archiving Long-term historical storage beyond short-term trend buffers. Yes Trend and log viewing plus open-source-format databases. source
Dashboards and graphics Operator graphics and configurable dashboards. Yes Customisable dashboards from device to portfolio level. source
Energy metering Metering and consumption measurement, including submetering. Yes Metered energy data, power, microgrids, renewables and EV charging, plus an optional Sustainability Pack. source
Trending and logging Configurable trend logs for point data. Yes Scheduling, trend and log viewing. source
Alarm management Alarm generation, prioritisation, routing and acknowledgement. Yes source
HVAC control Control sequences and scheduling for heating, ventilation and cooling plant. Yes Integrates HVAC, lighting, power, microgrids, renewables, security, fire and EV charging; automation servers provide control and alarm supervision. source
MQTT support MQTT publish or subscribe for telemetry and cloud integration. Yes Named in the open-protocol list: BACnet, LonWorks, Modbus, web services and MQTT. source
Modbus support Modbus TCP or RTU communication. Yes source
BACnet support Native BACnet IP or MSTP communication with field devices. Yes source
OPC UA support OPC UA client or server for industrial interoperability. Not verified OPC and OPC UA are not named on any Schneider page that could be opened.
KNX support KNX integration for building control devices. Not verified KNX is not named on any Schneider page that could be opened.

Deployment

ModelSupported
Cloud (vendor hosted) Not verified
On-premises / self-hosted Yes
Hybrid Yes

Integrations

Protocol

Licensing and pricing

ItemValue
Licensing modelCommercial
Free versionNo
Trial availableNot verified
Published priceContact vendor for pricing
NoteNo figure published, and unlike Siemens or Johnson Controls no licence structure is published either. The only commercial calls to action on the launch page are Get a Quote and Contact Sales. Sold through Schneider and its system-integrator channel.
Pricing last checked7 November 2026

Prices move and discounting is common. Treat anything here as a starting point and confirm with the vendor before budgeting.

Strengths and limitations

Strengths

  • The broadest openly stated open-protocol list among the major head-ends and the only one naming MQTT on its own page: BACnet, LonWorks, Modbus, web services and MQTT, plus Smart Connector APIs with an SDK. verified source
  • The most specific public cybersecurity posture in this category: secure development lifecycle, BACnet SC certificate management and installation-free secure web clients. verified source
  • Scope extends past classic BMS into power, microgrids, renewables, EV charging and metered energy on one platform, with Brick Schema semantic tagging for downstream analytics. verified source

Limitations

  • Technical documentation is closed to public access: the official help portal and the specification-sheet host both returned HTTP 403 Forbidden, so buyers cannot verify specifications without a login or a Schneider contact. verified source
  • The software and hardware boundary is not published clearly. Enterprise Server, Enterprise Central, WorkStation and WebStation are not listed on the current US launch page, which presents SpaceLogic hardware instead, so a buyer cannot tell from vendor pages what they are licensing. editorial
  • No published point counts, server-tier limits or concurrent-user ceilings on any reachable page, so sizing depends entirely on a Schneider or integrator quote. editorial

Who it suits

Organisation sizes: Enterprise

Who it fits. Large buildings and campuses, which is Schneider own stated target, and particularly estates where the electrical side matters as much as HVAC: power distribution, metering, microgrids, renewables and EV charging on the same platform as building control. The audiences Schneider names include building owners, facility managers, IT managers, property managers and system integrators, and commissioning tooling for integrators is a stated selling point. Organisations with a security review to pass will find more to work with here than with most competitors, given the published SDL and BACnet SC certificate management.

Who it does not fit. Small and mid-size buildings, and buyers who need to verify specifications before engaging a vendor. With the help portal and specification host both returning 403, no published capacity figures, no price and no public licence structure, this is a product you cannot evaluate at arm length. Anyone wanting a vendor-neutral head-end that is clearly separable from the vendor controller family should also compare against Desigo CC or Niagara.

Typical use. Integrator-delivered large commercial, campus and mixed building-plus-electrical estates, on premises, with Schneider cloud and connected services layered over the top. Insist on the current specification sheet at quote stage rather than the 2019 version that is findable online.

Alternatives

Metasys Johnson Controls The closest structural match, since both are automation suites sold as software plus a matched controller family. Metasys is the better choice when you must verify before buying: capacities, licence tiers and per-protocol application notes are public, where the Schneider help portal and specification host return HTTP 403. Metasys publishes less energy and power scope and licenses archival, FIPS, two-factor authentication and BACnet/SC separately.
Desigo CC Siemens A supervisory platform rather than a stack, so it leaves you freer at the field layer, and the most publicly verifiable protocol matrix in the category including a northbound BACnet IP server and OPC DA server. Pick it when fire and security must be first-class disciplines or a UL-listed fire variant is required. Watch the edition fragmentation: KNX and other drivers are in Connect but not Compact DMS.
Honeywell Enterprise Buildings Integrator (EBI) Honeywell Comparable enterprise multi-discipline positioning with native fire, life safety, security and video, and a distributed node architecture so a campus does not depend on one server. Both vendors keep documentation effectively closed, so neither improves your diligence position. EBI is the thinner profile of the two: no datasheet, no docs portal and no capacity figure of any kind could be found.
WebCTRL Building Automation System Automated Logic (Carrier) For BACnet-led estates that want the operational burden moved off site. WebCTRL Cloud is a vendor-hosted subscription on AWS including hosting, server maintenance, site-reliability monitoring, database redundancy, backups and upgrades, which Schneider does not publish an equivalent of, and it confirms MQTT, Modbus IP and SNMP. Narrower protocol breadth, with KNX, LonWorks and OPC UA not on the published list, and no open documentation portal.
Niagara Framework Tridium The alternative if you want to own the integration layer instead of accepting a vendor product boundary at the field layer. Understand what it is: a framework, not a finished BMS, so every deployment is bespoke engineering by an integrator or delivered as an OEM distribution. Strengths are the single runtime across edge and supervisor, a real third-party driver marketplace, and the deepest published security posture. Tridium driver list cannot be publicly verified.

See the full EcoStruxure Building Operation alternatives guide

Compared with other products

Frequently asked questions

Yes. It was marketed as StruxureWare Building Operation before the EcoStruxure rebrand, and Schneider regional product pages still carry the formerly known as wording.

Yes. Schneider names MQTT in the open-protocol list on its own building management system launch page, alongside BACnet, LonWorks, Modbus and web services. It is one of very few head-ends in this category to state MQTT support on a vendor page.

Largely no. The official help portal and the specification-sheet host both refuse automated access, and the Enterprise Server specification sheet path returns 404, so protocol detail, capacity and OS requirements require a login or a Schneider contact.

Sources and review basis

  • Evaluation basis: vendor documentation and public sources, not hands-on testing
  • Last reviewed: 7 November 2026
  • Vendor: Schneider Electric

References

Disclosure

Alongside advisory work I also build a CMMS and CAFM platform, so I have a commercial interest in enterprise software generally. No vendor in this directory has paid for inclusion, placement or wording, and there are no reseller or affiliate arrangements. Weigh the analysis accordingly.

Evaluating EcoStruxure Building Operation?

Independent help testing it against your actual requirement, and designing the data integration it will depend on. 22+ years across ERP, EAM, CAFM and enterprise integration. No reseller arrangements.

Book a conversation

At a glance

  • Vendor
    Schneider Electric
  • Category
    Building Management Systems
  • Primary use
    Building automation suite
  • Deployment
    On-premises, Hybrid
  • Licensing
    Commercial
  • Status
    Active

Need a second opinion?

Independent evaluation help, with no vendor relationships.

Get in touch
MAbbaz.com
© MAbbaz.com