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
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
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
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
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
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
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
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
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.