ALL SYSTEMS ONLINE / NewAHU Graphic Builder — configure any AHU and export native Niagara PX · $749, 25 exports included Try it live →

NIAGARAUI / DATA CENTERS

Understand the load. Follow the detail.

Data center operators need to move between facility indicators and the systems behind them. NODE and MESH approach that task with different page structures. Choose around the investigation workflow, the available data and the people who will use the station.

APPLICATION SCENARIO / NODE

Connecting a PUE indicator with power and cooling context

Explore NODE

Consider a data center overview showing a PUE indicator of 1.313, an IT load of 2.86 MW, a cooling load of 805 tons and four outstanding alarms. The operator's task is to understand the sources and system conditions behind that snapshot, rather than rank the facility from one number.

PUE indicator
1.313
IT load
2.86 MW
Cooling load
805 tons
Outstanding alarms
4

Scenario snapshot. Figures describe the scenario setup. Live readings and available actions depend on the project's configured sources.

NODE dashboard — Read the PUE indicator alongside the active site's power and cooling context.
01 Read the PUE indicator alongside the active site's power and cooling context.
NODE dashboard — Use the Power view to inspect the electrical information behind the overview.
02 Use the Power view to inspect the electrical information behind the overview.

01 / OPERATOR WORKFLOW

Establish the active site

Confirm the selected site and the freshness of the overview sources. Read PUE with IT and facility-power coverage; a comparison is useful only when the inputs and time basis match.

02 / OPERATOR WORKFLOW

Follow Power and Cooling

Use Power for electrical distribution and load context, then Cooling for the associated plant and equipment conditions. Read water temperatures and operating state with the same source interval.

03 / OPERATOR WORKFLOW

Investigate the room or device

Use Rooms and Equipment to move from a facility indicator to a scoped view. Thermal context and equipment records help define the next check without proving a failure mechanism by themselves.

04 / OPERATOR WORKFLOW

Check alarms and trends

Open the relevant alarm records and compare the available recorded histories. Retain the selected site, time range, units and observations in the applicable report/export workflow.

What this workflow helps establish

The operator can connect a headline indicator with a site, system, room and equipment review, then record the evidence supporting the next verification.

Reporting & recorded context

Overview report/export controls and the Trends page support the available data-review workflow. NODE does not include a separate Reports PX page; required report providers, histories and permissions remain project-specific.

What the project supplies

  • A Portfolio/Site model or supported direct point/history bindings.
  • Facility and IT power with matching units and time coverage for PUE review.
  • Room, cooling and equipment data connected to the intended sources.
  • Configured alarms, histories, permissions and a license for the target Niagara host.

APPLICATION SCENARIO / MESH

Following a rack-level concern into the wider facility

Explore MESH

Consider a facility snapshot with 1,842 kW of IT load, 598 kW of mechanical load and a 22.4°C average cold-aisle temperature. Seven active alarms accompany an attention queue. A facility average alone cannot identify which hall, rack or supporting system needs review.

IT load
1,842 kW
Mechanical load
598 kW
Cold-aisle average
22.4°C
Active alarms
7

Scenario snapshot. Figures describe the scenario setup. Live readings and available actions depend on the project's configured sources.

MESH dashboard — Use facility indicators and the attention queue to choose a scoped investigation.
01 Use facility indicators and the attention queue to choose a scoped investigation.
MESH dashboard — Review hall and rack conditions in White Space rather than relying on an aggregate temperature.
02 Review hall and rack conditions in White Space rather than relying on an aggregate temperature.

01 / OPERATOR WORKFLOW

Read the attention queue in context

Start with Overview and confirm the facility, time window and source coverage. Use the attention queue to select a specific concern rather than treating the average cold-aisle value as every rack's condition.

02 / OPERATOR WORKFLOW

Review White Space and Cooling

Follow the selected hall/rack context into White Space and inspect the supporting cooling information. Record which actual sources, sensors and equipment relationships support the displayed map.

03 / OPERATOR WORKFLOW

Trace the relevant power path

Use Power Chain to review the configured electrical relationships and available condition/load data. A drawn chain does not verify electrical topology or establish redundancy certification.

04 / OPERATOR WORKFLOW

Bring the station evidence together

Review Alarm Console and Trends & Histories for the scoped event. Drivers / Networks and Station Config provide station-oriented context where the user's configured access permits it.

What this workflow helps establish

The review can end with a hall/rack/system evidence trail and an actionable handoff, while preserving the distinction between live source readings and integrator-entered context.

Reporting & recorded context

Trends & Histories and Alarm Console support recorded operational review. MESH has no separate Reports PX page. Station and network views require the actual Niagara resources and appropriate access.

What the project supplies

  • Configured facility, hall, rack, cooling and electrical relationships.
  • Mapped power and thermal measurements with correct engineering units.
  • Available alarm/history resources and the intended station/network access.
  • Confirmed host compatibility, signed modules and a license for the deployment host.