Management systems are a cornerstone of any automated infrastructure. Regardless of industry, data must be handled with precision — because the information a system surfaces directly shapes the decisions made around it.

In infrastructure automation, the systems that fill this role are broadly classified as SCADA (Supervisory Control and Data Acquisition). Whether we're talking about a BMS (Building Management System), an EMS (Energy Management System), an RMS (Room Management System), a WMS (Water Management System), or any other dedicated management platform, they all share a common thread: data handling.

Each of these systems draws its data from the field devices deployed across a facility — sensors, detectors, and similar instrumentation.

How that data is treated matters enormously. It shapes the entire relationship between the operator and the system: how information is stored (on-premises server vs. cloud), where the computations run, what data actually adds value to operations and maintenance, how alerts are handled, how notifications are managed, and what configuration parameters are exposed. These questions don't arise during commissioning — they have to be answered at the conceptualization stage, and every answer is tightly coupled to the hardware specified during detailed engineering.

In many cases, the right answers depend on the criticality of the systems involved (which drives data refresh requirements), the need to certify the project under an international sustainability standard (which imposes specific data retention and visualization requirements), and the complexity of the calculations needed to aggregate and totalize operational data.

Other factors include the selected equipment's ability to communicate via API, the integration options available through standard protocols, and the degree of customization the management platform allows. Taken together, these answers progressively define the software architecture the project will require.

Typical architecture of an infrastructure management system.

As solution developers, we regularly face a specific kind of challenge: working within the capabilities and constraints of whatever hardware configuration a project presents. The real difficulty lies in building a reporting system that meets the client's requirements and delivers genuinely useful information.

Core Functions of a Management System

Every supervisory system must cover a set of fundamental functional areas. These are the load-bearing elements on which the entire solution is built:

• Monitoring: The system must provide continuous visibility into data from every component it encompasses.
• Configuration: Authorized users must be able to adjust system parameters — setpoints, maximum and minimum values, and similar settings — as needed.
• Alerts and notifications: Often grouped under configuration, but worth treating separately. Establishing the criticality of each alert, tracking them systematically, and building management KPIs from that data are all distinct tasks.
• Report generation: Enables visibility into any controlled system over time. Filtering tools let operators isolate relevant data, track specific processes, and export information for deeper analysis.

These four areas represent the baseline. Any management system that doesn't cover them falls short. From there, the platform can grow — adding capabilities that enrich operations and maintenance and move the project toward genuine facility management.

Reporting panel and data visualization in a management system.

Closing Thoughts

Working through these questions tells you whether a project's requirements can be met with the available hardware and software, or whether a more creative approach is needed — extracting data via alternative methods, routing it to the cloud, and performing the necessary processing there.

No matter how much we'd like to standardize a hardware or software solution across different project types, conditions will always arise that push us outside our comfort zones. Sometimes they challenge us to expand our thinking; sometimes they require breaking with established practice entirely.

Nothing in this field is fixed. Change is not just inevitable — it's essential for staying relevant. Accumulated experience is a strong foundation for answering the demands each project brings, but continuing to study and analyze new cases is what keeps the process of building management systems moving forward.

Data is power. In many automation projects, success ultimately comes down to how well data is managed — and whether it reaches the right people, in the right form, at the right time to support sound decisions.

Jonny Cabrera Director of Operations — jcabrera@innotica.net — LinkedIn