EarthState

AIoT and sensors

Sensors connected to the model, automatically

A sensor reading means little until it is tied to the member it sits on and checked for faults. EarthState does that connection for you: from the sensor list to a calibrated twin that is compared with measurement before anyone relies on it.

EarthState Twin: strain gauges being registered on the model one by one, each with its height and model channel, and each step sent to audit.
EarthState Twin · registering sensors on the model · each step goes to audit
Step by step

One instruction, the whole chain

You ask in plain language: register the sensors installed on the tower, then ingest the sensor data and check its quality. The assistant runs the platform's own skills in order, and every value on screen comes from one of those skills.

  • Reads the sensor interface list: sensor, member or node, height, data file and data source
  • Registers each gauge on its model member and gives it a model channel
  • Strain gauges and an anemometer on the demonstration tower

The sensor chain

From a sensor list to a twin you can trust

01RegisterEvery sensor is placed on a member or node of the model and mapped to the quantity it measures.
02IngestSensor records are read from the project folder, event by event.
03Check qualityGaps, duplicated records and outliers are found, handled and written to the audit record.
04Convert and correctWind is converted to the basic wind velocity of EN 1991-1-4. Baseline and temperature trend are removed from strain.
05CalibrateThe model is fitted on monitoring events and validated on an event it has not seen.
06WatchMember utilisation follows the wind. A watch level can raise an inspection job in the asset data.
EarthState Twin: wind and strain over an event, with the quality checks listed as an audit record with pass verdicts.
EarthState Twin · sensor data and quality checks · demo data, labelled on every plot
Quality before use

Every record is checked, and the check is kept

For each event and each gauge the platform reports the outlier ratio, whether temperature compensation was applied, whether the wind-induced response can be observed at all, and which model channel the gauge was mapped to. The verdicts stay in the audit record with the result.

The demonstration uses synthetic strain records and labels them as demo data. Today the twin reads sensor records as files in the project folder.

FacilityNexus: zone temperatures, carbon dioxide and comfort for one floor beside a 3D building model with equipment markers and an assistant panel.
FacilityNexus · space and comfort from zone sensors · building model from an open dataset (CC BY 4.0)
In buildings

The same idea for a facility in operation

FacilityNexus ties zone temperature, carbon dioxide and occupancy sensors, smart meters and equipment points to the rooms and plant they belong to, on a 3D twin of the building.

  • Complaints traced to a likely cause on the same supply branch
  • Equipment health and planned maintenance in one view
  • Wearable badges for staff working alone on site
Explore FacilityNexus

Sensors installed, but no one trusts the numbers?