EcoStruxure Building Operation Enterprise Central is the top-tier EcoStruxure BMS server in a large Building Management System and is intended for system specific tasks and supervision. Enterprise Central can host several Enterprise Servers, which in turn can host multiple SpaceLogic™ automation servers. As the dedicated server at the top of the system architecture hierarchy, Enterprise Central provides an entry point from which you can configure, control, monitor, and search the entire system. Enterprise Central collects site-wide data for aggregation and archiving and serves as a single point of administration through WorkStation or WebStation.
For Corporate Facility Managers, Senior Engineering Managers, Chief Space Planners and others who need to manage their buildings in a global, aggregated, and efficient manner, Enterprise Central is an EcoStruxure BMS server that allows users to scale operations management across the largest buildings, campuses, and multi-site corporate real estate portfolios from a single location by generating aggregated reports, standardizing critical security policies, normalizing alarm presentation and prioritization, and auditing activity across the entire organization.
Unlike other BMSs which focus on a single location or on a single aspect of the operation, Enterprise Central provides a single pane of glass across all aspects of a large real estate portfolio.
Enterprise Central has the following main features:
Global view, access, and search of the system
Centralized alarms and data management:
Alarms from multiple servers
Event logs from multiple servers
Extended trend logs from multiple servers
Historical data storage from multiple servers
Scalability
User and domain management
Windows Active Directory integration
Enterprise Server and Enterprise Central come with built-in support for modelling of the “digital twin” of the building, site, campus, and region using Brick Schema. WorkStation and WebStation provide enhanced human understandability through the additional context that is given to alarms and points through the “digital twin”. The required graph database is included in the installation packages. WorkStation can be used to create the model, or it can be imported using the graph database user interface.
The entire system, including all mid-tier Enterprise Servers and the base-tier automation servers with their associated Central IO modules, field controllers, and other field devices, can be accessed and configured through Enterprise Central. When logged on to Enterprise Central, you can also search the entire system, and view alarm and event data from all associated Enterprise Servers and automation servers. In short, with the exception of not hosting its own layer of field bus devices, Enterprise Central carries the same full feature set as the Enterprise Servers.
Alarms from the Enterprise Servers, automation servers, and their associated devices throughout the site, are collected by Enterprise Central for centralized logging, display, and management. Alarms can trigger email, SNMP, file, or client notifications, which can include alarm, point value, or trend log data. Notifications can also be triggered periodically by schedules or other binary values.
Users can also view event logs and trend logs from multiple Enterprise Servers and automation servers. The historical event data is collected from the multiple servers and stored in a central database.
EcoStruxure BMS servers can be configured to automatically store all historical data, trend log data, event log and audit trail data, in an external database. If data needs to be available for longer periods of time, an external log storage can be incorporated into the EcoStruxure BMS without the need for extensive engineering work. The supported databases are TimescaleDB, which is built on PostgreSQL, and Microsoft SQL Server. The data in the external log storage is available natively to the viewers built into the EcoStruxure Building Operation clients and to the built-in reporting functionality.
You can use the powerful Log Processor functionality for custom processing of trend data for viewing in charts, dashboards and for inclusion in reports. The Log Processor enables advanced calculations on one or multiple trend logs and point values.
Examples of advanced calculations:
Energy usage normalization
Virtual submeters and summaries
Calculation of Mean Kinetic Temperature
Unit conversions
Average, maximum, and mini m um over custom periods
The output of the Log Processor can be saved in the database, including the External Log Storage or calculated automatically on demand.
Selected trend logs and the event log can be sent to AVEVA PI System directly without the need for intermediate storage or specialized PI System connectors. The EcoStruxure BMS server can also be the front-end client to AVEVA PI System and obtain data from the PI System that can be included in reports, graphics, and dashboards.
Enterprise Central is available in three different sizes, which are differentiated based upon the maximum quantity of Enterprise Servers that can be hosted. The available sizes are two Enterprise Servers, five Enterprise Servers, and ten Enterprise Servers. When using Enterprise Central, an EcoStruxure BMS can include anywhere from a handful of automation servers on up to 50 Enterprise Servers, where each Enterprise Server is connected to another 250 automation servers (with a maximum of 2,500 automation servers in total per system), and each automation server is connected to the full complement of BACnet/IP controllers and field bus devices.
You can use Enterprise Central to create and configure domains, user groups, and permissions.
With the meter management functionality, EcoStruxure Building Operation offers improved methods to ensure data is accurate and meter changes are automatically detected. In addition, purpose-built functions enable easier handling of the following concepts:
Aggregations
Virtual metering
Apportioned metering
Unit conversions
Meter hierarchies enable powerful visualization of sub-meter structures or categorizations. A web-based editor with intelligent help functions enables efficient construction of meter hierarchies.
The normalization functions help with benchmarking, and the signature function enables automation and/or alerting when resource usage is too high or low. This enables early detection of faulty equipment and misused building functions, resulting in energy savings and higher occupant satisfaction.
The system includes easy-to-use tools for regression analysis and powerful methods for time-period classification, that is, differentiation of workdays versus holidays.
Using the built-in security features within the EcoStruxure Building Operation software, you can comply with 21 CFR Part 11 and other Life Sciences regulations, restricting access to authorized and qualified individuals and with full audit trail. In addition, the built-in access and security settings can be enhanced by applying further restrictions and limit access by time-of-day or geographic location.
The change control features extend the basic activity logging provided by the EcoStruxure Building Operation software by enhancing the functionality of the standard log, enabling efficient and fully configurable change control with the following features:
Single or dual electronic signature application
Change control that can be restricted only to specific objects in the system
Change control that can easily be applied to all objects
Every associated action is logged with the parameter that was changed
Before and after parameter values including meta data
For each signature event, the change control signatures contain:
The unique identifier of the person executing the signature
The full name of the user who performed the action
The geographical date and time stamp
The meaning of the signature, such as approval, review, responsibility, and authorship
The EcoStruxure BMS servers provide built-in functionality for basic reporting that can deliver reports in any text format and XLSX, without any dependencies to other external software. Reports for XLSX can be enriched by using advanced functionality such as formulas, conditional formatting, charts and sparklines.
Reports can be generated on schedule, on an alarm event or other custom conditions, and you can get the output delivered via email or written to file.
Using Enterprise Server and Enterprise Central, reports can be converted to PDF, and you can elevate the data security and traceability even further by automatically signing PDF reports with a digital certificate upon generation. This validates that the content has not been altered after the report was generated.
An EcoStruxure BMS provides a powerful permission system that is easy to manage, flexible, and adapts to all kinds of system sizes. The permission system provides a high standard of authentication. Authentication is done against the built-in user account management system, against Windows Active Directory Domains, or via SAML 2.0 single sign-on. The built-in account management system allows an administrator to establish password policies that meet stringent cybersecurity guidelines. In addition, multi-factor authentication (MFA) according to RFC 6238 is supported and enforceable. Applications such as Google Authenticator and Microsoft Authenticator can be used as part of the user authentication. When Windows Active Directory or SAML 2.0 authentication is used, the administration costs are lower because users do not have to be managed in multiple directories.
With Enterprise Central, the password policies are standardized across all hosted Enterprise Servers.
It is important to log more than basic activity. In an EcoStruxure BMS, every action is logged with a timestamp, the user who performed the action, and the values that were changed.
Through any client, the user experience is similar regardless of which EcoStruxure BMS server the user is logged on to. The user can log directly on to an Enterprise Central to commission, supervise, and monitor the Enterprise Servers and automation servers with their attached Central IO modules, field controllers, and other field devices. For more information, see the WorkStation and WebStation specification sheets.
Enterprise Central supports the use of Web Services based on open standards, such as SOAP and REST, to consume data into the EcoStruxure BMS. Use incoming third-party data (temperature forecast, energy cost) over the Web to determine site modes, scheduling, and programming.
EcoStruxure Web Services, Schneider Electric’s Web Services standard, is natively supported in the EcoStruxure BMS servers. EcoStruxure Web Services offers extra features between compliant systems whether within Schneider Electric or other authorized systems. These features include access to semantic model, system directory browsing, read/write of current values, alarm receipt and acknowledgement, and historical trend log data. EcoStruxure Web Services requires user name and password to log on to the system.
The EcoStruxure BMS servers communicate using the networking standards. This makes installations easy, management simple, and transactions more secure.
IP addressing
TCP communications
DHCP for easy network configuration
DNS for simple lookup of addresses
HTTP/HTTPS for internet access through firewalls, which enables remote monitoring and control
NTP (Network Time Protocol) for time synchronization throughout the system
SMTP or SMTPS with support for SSL/TLS based authentication, enables sending email messages triggered by schedule or alarm
SNMP enables reception of application alarms in designated network management tools
Communication between clients and the EcoStruxure BMS servers , and between EcoStruxure BMS servers, can be encrypted using Transport Layer Security (TLS ). The servers are delivered with a default self-signed certificate. Commercial Certification Authority (CA) server certificates are supported to lower the risk of malicious information technology attacks. Use of encrypted communication can be enforced for both WorkStation and WebStation access.
Hardware requirements | |
Processor power, memory, and storage capacity should be scaled upwards to accommodate targeted system size as impacted by the total quantity of Enterprise Servers, automation servers, and expected historical archiving. Enterprise Central is tested on a server with an 8-core 3.6 GHz processor, a 16 GB of memory, and an SSD storage capacity of 4 TB. | |
Processor
|
Minimum: Intel Core i5 @ 3.0 GHz or equivalent
|
Recommended: Intel Core i5 @ 4.0 GHz or better
|
|
Memory
|
Minimum: 8 GB
|
Recommended: 16 GB or higher
|
|
Storage capacity
|
Minimum: 1 TB
|
Recommended: 4 TB
|
|
Storage device
|
Recommended: Enterprise Solid State Drive (SSD)
|
An Enterprise SSD is recommended to maintain the necessary speed and stability. The database and the binaries should both be installed on the Enterprise SSD. | |
Other devices
|
Microsoft mouse or compatible pointing device is required.
|
Software requirements | |
Operating systems – Enterprise Central for Windows
|
Microsoft Windows 10 (64-bit)
|
Microsoft Windows 11
|
|
Microsoft Windows Server 2016
|
|
Microsoft Windows Server 2019 (not supported for I/NET integrated system)
|
|
Microsoft Windows Server 2022 (not supported for I/NET integrated system)
|
|
The following Microsoft Windows 10 editions are supported: Pro and Enterprise. | |
The following Microsoft Windows 11 editions are supported: Pro and Enterprise. | |
The following Microsoft Windows Server 2016 editions are supported: Datacenter, Standard, and Essentials. | |
The following Microsoft Windows Server 2019 editions are supported (not supported for I/NET integrated system): Datacenter, Standard, and Essentials. | |
The following Microsoft Windows Server 2022 editions are supported (not supported for I/NET integrated system): Datacenter, Standard, and Essentials. | |
Operating systems – Enterprise Central for Linux
|
OCI compliant container runtime on Linux x86-64
|
Quality assurance testing has been performed on, and support is provided with, Ubuntu 20.04 and 22.04 with Docker Engine version 20.10.00. Other deployment scenarios have not been tested by Schneider Electric. Product Support Services may require that potential issues can be reproduced in tested and supported environment for full support. | |
Required additional software – Enterprise Central for Windows
|
Microsoft .NET Framework 4.7.2 and later
|
The Microsoft .NET Framework is required by Software Administrator. | |
External log storage PostgreSQL option
|
Supported versions of PostgreSQL (
www.postgresql.org
) with matching version of TimescaleDB extension (
www.timescale.com
).
|
Note: To use compression for trend data, TimescaleDB 2.11 or later is required.
|
|
Quality assurance testing has been performed by Schneider Electric with TimescaleDB and PostgreSQL installed natively in Windows 10, Windows Server 2012, 2016, and 2019. Other deployment scenarios have not been tested by Schneider Electric. | |
External log storage Microsoft SQL option
|
Microsoft SQL Server versions under full support by Microsoft (
www.microsoft.com
).
|
The following Microsoft SQL Server editions are supported: Enterprise, Standard, and Express. | |
External log storage AVEVA PI System option
|
PI Web API 2021 SP3 and database compatible with that version
|
Quality assurance testing has been performed by Schneider Electric with PI Web API 2021 SP3, and database compatible with that version, installed on Windows Server 2019. Other deployment scenarios have not been tested by Schneider Electric. | |
Communication | |
TCP
|
Binary, port fixed, 4444
|
HTTP
|
Non-binary, port configurable, default 80
|
HTTPS
|
Encrypted supporting TLS 1.3, 1.2, 1.1
a
, and 1.0
a
, port configurable default 443
|
a) Disabled by default. | |
SMTP
|
Email sending, port configurable, default 25
|
SMTPS
|
Email sending, port configurable, default 587
|
SNMP
|
version 3
|
Application alarm distribution using trap
|
|
NTP
|
Time synchronization
|