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

NIAGARAUI / PROJECT RESOURCES

The right dashboard.
For your next host.

Compare application, page structure and operational focus. Choose the interface that fits your project, then explore its demo before you buy.

One license. One selected template. One Niagara host ID.

Prices below are the current product prices. Page counts describe the supplied main dashboard views; detail pages, reusable widgets and project configuration vary. Page count alone does not define product depth.

THE COLLECTION / 08 DASHBOARDS

Compare at a glance.

Start with your application.
Then explore the workflow.

Dashboard application, page count, operational focus and current price per host ID
Dashboard / applicationPages & operational focusLicenseExplore
ATRIUMSchools & education
11 + detail pages

Site, building, floor and equipment navigation; conditions, alarms, schedules and reports.

$995.00/ host ID
NODEData center operations
8 main views

Command overview, cooling, power, rooms, equipment, alarms, trends and settings.

$1,195.00/ host ID
LUMACommercial offices
11 main views

Comfort and floors/zones, HVAC/IAQ, energy, occupancy, access, elevators and operator tasks.

$1,395.00/ host ID
THERMAChiller plants
8 main views

Plant efficiency, chillers, cooling towers, pumps/hydronics, optimization inputs, analytics and alarms.

$1,495.00/ host ID
SOLAR IQSolar & storage
9 main views

Renewable generation, energy flow, batteries, analytics, maintenance and sustainability.

$1,595.00/ host ID
NEXALaboratories & pharma facilities
8 main views

Room conditions, cleanroom suites, stability chambers, AHUs, alarms, histories and audit records.

$1,695.00/ host ID
PULSECampuses & portfolios
16 main views

Campus/building comparisons, energy, water, comfort, sustainability, alarms, schedules and reports.

$1,795.00/ host ID
MESHDetailed data center operations
8 main views

Electrical power chain, cooling, rack thermal maps, alarm/history detail, networks and station views.

$1,895.00/ host ID

Page counts describe the supplied main views. Review the full inventory below for detail pages, reporting and project inputs.

DATA CENTERS

NODE or MESH?

Start with NODE for a coordinated power, cooling, rooms and equipment operations interface. Review MESH when the project calls for more explicit electrical-chain, rack thermal, network and station detail. Both have eight main views; compare the actual workflows and source requirements in their demos.

Explore NODE ↗Explore MESH ↗

BUILDINGS & PORTFOLIOS

ATRIUM, LUMA or PULSE?

ATRIUM organizes school facilities around buildings, floors and equipment. LUMA focuses on commercial office conditions and daily operator tasks. PULSE adds a campus/portfolio-oriented view with building comparisons and wider resource reporting.

Request a guided walkthrough ↗

THE ACTUAL PAGE INVENTORY

Count the views. Compare the work.

Each inventory below describes the supplied main task pages. Example and unconfigured starting sets are alternate routes into the same interface, not extra applications. Open a dashboard to review its reporting depth and project inputs.

ATRIUM11 main views · Schools & education
  • Dashboard
  • Alarm Summary
  • System View
  • Charts
  • Schedules
  • Reports
  • Remote Access
  • Files
  • History
  • Users
  • Settings

Three additional detail PX pages accompany the eleven main task views.

Reporting depth

Dedicated Reports, Charts and History pages provide routes to configured resources and records. Available report results, scheduling and editing depend on the project's Niagara services and permissions.

Required project inputs

  • Building, floor and equipment relationships with the school's own plans.
  • Mapped points, histories and alarm records for the intended scope.
  • Configured report, schedule, directory or remote-connection resources where those pages are used.
  • The correct host-bound license, signed modules, certificates and operator permissions.
LUMA11 main views · Commercial offices
  • Command
  • Floors
  • HVAC
  • Energy
  • Occupancy
  • Security
  • Elevators
  • Work
  • Alarms
  • Settings
  • User Database

The User Database view is separate from the ten main operating navigation destinations.

Reporting depth

Energy views include configured load/history context and applicable CSV or print outputs. LUMA's eleven supplied PX views include a User Database page; this is not a separate automated reporting platform.

Required project inputs

  • Property, floor, zone and equipment models connected to real station sources.
  • Correct point units and history coverage for comfort, demand and air quality.
  • Existing account, alarm and work-resource permissions appropriate to the project.
  • Workbench setup, a licensed Niagara host and the package's documented modules and certificates.
PULSE16 main views · Campuses & portfolios
  • KPI Overview
  • Campus Map
  • Buildings
  • Equipment
  • Floorplan
  • Alarms
  • System Health
  • Energy
  • Water
  • Comfort
  • Sustainability
  • Reports
  • History
  • Schedules
  • Users
  • Settings

Sixteen main pages organize campus operations and resource-review workflows.

Reporting depth

Dedicated Reports and History pages sit alongside Energy, Water, Comfort and Sustainability views. The project must supply the relevant sources, report resources and permissions; displayed sustainability scores are not independently certified outcomes.

Required project inputs

  • A campus/building model with suitable area, capacity and location inputs.
  • Consistent metric definitions, units and periods across the compared buildings.
  • Mapped histories and configured resource/report providers with coverage understood.
  • A host-bound license, matching modules and project-specific operator permissions.
NODE8 main views · Data centers
  • Command / Overview
  • Cooling
  • Power
  • Rooms
  • Equipment
  • Alarms
  • Trends
  • Settings

Eight main views use a site, room and equipment-centered navigation structure.

Reporting depth

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.

Required project inputs

  • 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.
MESH8 main views · Data centers
  • Overview
  • Power Chain
  • Cooling
  • White Space
  • Alarm Console
  • Trends & Histories
  • Drivers / Networks
  • Station Config

Eight views give power-chain, hall/rack and station-oriented detail. NODE also has thermal and power views; compare the actual navigation and commissioning model.

Reporting depth

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.

Required project inputs

  • 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.
THERMA8 main views · Chiller plants
  • Plant Home
  • Chillers
  • Cooling Towers
  • Pumps & Hydronics
  • Optimization
  • Analytics
  • Alarms
  • Settings

Eight main pages are supplied in example-bound and unconfigured sets; the sets are alternative starting routes, not sixteen different main views.

Reporting depth

Analytics, recorded plant trends and available export controls support plant review. Baseline, cost or avoided-energy displays depend on configured inputs and are not independent savings verification.

Required project inputs

  • Mapped plant, chiller, tower and pump measurements in consistent units.
  • Actual cooling-load and power sources with a comparable time basis.
  • The existing controller sequence and eligible, authorized command targets.
  • Matching modules, the target host's license and the supplied installation guide.
SOLAR IQ9 main views · Solar & storage
  • Energy Home
  • Solar Arrays
  • Energy Flow
  • Battery Storage
  • Analytics
  • Alarms
  • Maintenance / Work Plan
  • Sustainability
  • Settings

Nine main pages are accompanied by a separately placeable KPI example. Example and unconfigured page sets are alternative starting routes.

Reporting depth

Analytics, daily-report resources, generation histories and Sustainability views organize the available records. Forecasts, risk values and sustainability indicators depend on project inputs and calculation scope.

Required project inputs

  • Actual generation, site-load, battery and grid-exchange sources.
  • Consistent power/energy units and configured battery/grid sign conventions.
  • Mapped asset, history, alarm and maintenance resources for the intended scope.
  • A host-bound license and project-specific permissions for any eligible operating requests.
NEXA8 main views · Laboratories & pharma
  • Environmental
  • Cleanroom Suites
  • Stability Chambers
  • HVAC & AHUs
  • Alarms
  • Trends
  • Audit Trail
  • Settings

Eight main views connect the configured facility, room, chamber and air-handler model.

Reporting depth

Trends and Audit Trail views organize available histories and audit records. NEXA does not by itself supply validated electronic-record compliance, instrument calibration, regulatory certification or a complete quality-management process.

Required project inputs

  • The facility's actual room, suite, chamber, instrument and AHU relationships.
  • Approved project thresholds, units, instrument inputs and source mappings.
  • Available native alarm, history and audit-record resources with appropriate user access.
  • A confirmed target host and license, plus the facility's own commissioning and validation procedures.

NODE VERSUS MESH

Eight views each. Different operating structures.

Both include power, cooling, thermal context, alarms and histories. Choose around the navigation and data model your team needs, rather than assuming one is the other with extra pages.

NODE and MESH workflow comparison
Selection questionNODEMESH
Primary organizationOverview, Cooling, Power, Rooms and Equipment organize the facility around site and equipment investigation.Overview, Power Chain, Cooling and White Space organize the facility around electrical paths and hall/rack context.
Power investigationReview power distribution and facility/IT load context from the Power view.Use the dedicated Power Chain page for utility, switchgear, ATS, UPS and PDU paths with mapped branch information.
Thermal investigationRooms and Cooling provide thermal and cooling-system context.White Space emphasizes rack/cabinet thermal and capacity context alongside Cooling. Thermal views are not exclusive to MESH.
Station and integration contextA Settings page accompanies the core operating views.Separate Drivers / Networks and Station Config pages expose more explicit station and network context.
Recorded data and reportingTrends, alarm records and applicable export/report workflows use configured source coverage and permissions.Trends & Histories and Alarm Console use configured sources, intervals and permissions. An interface does not create missing history providers.
Commissioning briefMap the intended site, room and equipment relationships, relevant points, histories and alarm sources.Map the intended hall/rack and electrical-chain relationships, corresponding measurements and applicable station/network providers.

THE VALUE OF A STARTING POINT

Put a value on your engineering time.

Compare the interface work, configuration effort and host license for your next project.

Build the interface

Plan navigation, design pages, assemble components and develop the required views.

Start with a template

Select the application and supplied views, then configure them for the project.

Map, test and hand over

Both approaches need real sources, permissions, verification and operator handoff.

/ hour

Editable planning rate. Use your actual engineering cost or quoted charge-out rate.

hours
hours

Use comparable project scopes, including mapping, testing and handoff in both estimates. For repeat projects, enter the effort to adapt your existing in-house standard.

View selected template

ONE PROJECT / ONE HOST ID

Engineering hours to cover the license—

License price ÷ your hourly rate. Rounded up to the next tenth of an hour.

Estimated project cost difference

Enter your hoursCompare your own build and configuration estimates.
Build / in-house effort
—
Template configuration effort
—
Host license
—
Template project total
—

Configuration effort is additional to the license cost.

How the estimate works & research sources

The math: build cost = build hours × hourly rate. Template project cost = configuration hours × hourly rate + the current selected host license. The difference is an estimate of project cost under your inputs. It is not a measurement of achieved savings.

The initial $150/hour is an editable planning assumption informed by public labor-rate examples. Contract rates vary by role, scope and purchasing terms; these examples do not establish a market average. Build and configuration hours are left for your project estimate.

Research reviewed November 20, 2026. Estimates exclude taxes, hardware, unlisted software and project-specific extras. Each additional host requires its own applicable license. No volume discount is assumed.

Preview data is illustrative.

Readings, reports, histories and permitted actions depend on your actual Niagara sources, configuration and access rights. NEXA does not by itself establish regulatory compliance. THERMA and other dashboards do not guarantee energy savings.