PixelCore

One platform for connected facility operations.

PixelCore connects sensors, meters, gateways and supported building systems, then organises their data around the real-world sites, spaces and assets your teams operate — in a building, a data centre, a depot or a network of small sites. The same shared model supports every dashboard, rule, report, workflow and AI investigation.

Start a Pilot See the capabilities

The shared asset model

Data organised the way operations teams think

A measurement on its own is a number. Mapped to a room, a chiller, a rack row or a meter — with its relationships and history — it becomes a physical thing a team can act on.

Estate · portfolio

├─ Site — Data Centre 1 · location, timezone

│ ├─ Space — Server Room B · floor plan, 3D

│ │ ├─ Equipment — CRAC-02 · serves rack row B

│ │ │ ├─ return_air_temp · °C · 5 min

│ │ │ ├─ fan_speed · % · 1 min

│ │ │ └─ alarm_state · rule: band 18–24 °C

│ │ └─ Asset — Rack row B · 12 racks

│ └─ Space — Plant room · chilled-water loop

└─ Site — Office Tower 3 · 14 floors

What the model holds

Sites, spaces and equipment — the hierarchy your teams already use, not a flat device list.
Typed properties — units, expected ranges, sampling intervals and current state.
Full history — every reading kept with its object, so current state and past behaviour are queried together.
Operating relationships — which equipment serves which space, which meter covers which area.
Rules and conditions — thresholds, bands and derived values evaluated centrally, once.
Permissions — who can see and change which part of the estate.

The model is defined in PixelMonitor and read by every other application, so a change to an asset, a rule or a location is immediately consistent everywhere.

What PixelCore connects

Field sensors and supported building systems

Connectivity is a means, not the product. PixelCore brings readings, states and events into one model — from the field devices you install and from the systems already running on site.

LoRaWAN

Long-range, low-power field sensors across buildings, campuses and distributed sites.

FIELD SENSORS · AVAILABLE

MQTT

Lightweight publish/subscribe telemetry from gateways and edge devices.

TELEMETRY · AVAILABLE

BACnet / Modbus

Building and plant systems mapped into the same asset model, per site and per system version.

BUILDING SYSTEMS · INTEGRATION-DEPENDENT

APIs

A typed GraphQL interface for objects, properties and history, plus webhooks for downstream systems.

QUERIES · SUBSCRIPTIONS · AVAILABLE

Customer-specific bridges

Access control, CCTV events, power and cooling equipment, specialist facility software — scoped per deployment.

SCOPED PER PROJECT · INTEGRATION-DEPENDENT

Enterprise systems

Exports and interfaces towards BI, ERP and reporting tools that already hold the commercial record.

ENTERPRISE · CONFIGURABLE

Ready-made connectors do not exist for every named system. Each integration is confirmed against the actual system, version and site conditions during the pilot.

Existing systems

Designed to complement, not to replace

Most facilities already run systems that do their job well. PixelCore adds the operational context between them, and leaves each system in place.

BMS

Keeps controlling the building. PixelCore reads the points in scope and relates them to spaces and equipment.

DCIM

Remains the specialist system of record. PixelCore provides the facility-side operational view around it.

CMMS

Still owns work orders and maintenance history. PixelCore supplies the condition evidence behind them.

Enterprise systems

ERP, BI and reporting keep the commercial record; PixelCore exports the operational data they need.

PixelCore is not a complete BMS, DCIM or CMMS product, and is not an autonomous facility-management system. Where an integration is required, it is scoped, tested and confirmed per site.

Rules, alarms, Watchers and AI

Everything reasons over the same context

Because logic lives with the model rather than inside each dashboard, an alarm, a report and an AI answer all describe the same asset in the same terms.

Rules and conditions

Thresholds, bands and derived metrics evaluated server-side, consistently for every app and user.

Alarms and notifications

Alarm state carried on the asset itself, with routing to the people responsible for that space.

Scheduled Watchers

Saved checks run on a schedule and report back — a status summary on time, or a notification when something drifts.

AI insights

PixelAssistant surfaces insights from the same objects, properties and history — a drift or an overspend raised before anyone asks, in the same terms as any alarm and just as auditable.

Capabilities

What the platform does — and what it takes to get there

Some capabilities are ready as delivered, some are configured per estate, and some depend on what a specific system exposes. Each one is labelled so expectations match reality.

Available ready in the platform Configurable set up per estate Integration-dependent depends on the target system Planned not available today

Data foundation

4 capabilities · one depends on the target system

Real-time monitoring

Available

Live conditions for connected assets, equipment and spaces across every site in the model.

Historical data

Available

Every reading stored with its object; retention windows agreed per deployment.

Asset and location modelling

Available

Sites, spaces, equipment, typed properties and the operating relationships between them.

Existing building and facility systems

Integration-dependent

BACnet/Modbus points, access-control and CCTV events, power, cooling, DCIM and CMMS bridges — scope confirmed per site.

Views, rules and reporting

5 capabilities · mostly configured per estate

Dashboards, floor plans, maps and 3D

Configurable

Spatial and operational views composed from the shared model. Plans and 3D models are prepared per site.

Rules, alarms and notifications

Configurable

Thresholds, bands, derived metrics and routing — defined for your asset types and teams.

Reporting and exports

Available

Raw and aggregated views, comparisons and exports for BI, ERP and operational reporting.

Remote device control

Configurable

Typed commands through the RPC registry, where the device and its integration support control.

Consumption accounting and billing

Configurable

Metering-based consumption records and billing outputs for utilities and multi-tenant estates.

AI and automation

3 capabilities · one still on the roadmap

Natural-language investigation

Available

PixelAssistant answers operational questions over the same model, with charts, evidence and next checks.

Scheduled Watchers and workflows

Configurable

Saved checks on a schedule; notification and escalation flows configured to your procedures.

Validated predictive models per asset class

Planned

Forecasting is based on observed history. Asset-class models validated against outcomes are not available today.

Bridges, storage, the API layer and hosting options are described on the technical architecture page.

Start with one problem

See the model built on one of your own sites

Start a Pilot See all apps