Skip to content
SENSE&VALUE
Seven-layer architecture

One data spine. Two products: operations and valuation.

Every layer below is a real engineering surface with its own protocols, contracts, and failure modes. The stack is designed so operations pays for the sensors, and valuation emerges as a signed by-product of data we were already paid to collect.

End-to-end flow

Cumulative flow across all seven layers

L-0Field sensingInputs
Physical phenomena: vibration, tilt, voltage, current, water, CO₂, temperature, motion.
Process
On-node ADC sampling → thresholded encoding → LoRaWAN uplink; gateway buffers on WAN loss.
Outputs
Compact binary frames tagged with devEUI, timestamp, and RSSI/SNR — ready for decoding.
L-1Ingestion & market da…Inputs
LoRaWAN frames from gateways + nightly market-data files and APIs.
Process
Decode → validate → dedupe → insert into hypertable; ETL normalises leases and comps onto property_id.
Outputs
Unified time-series rows: readings, leases, transactions, comparables.
L-2Asset & twin modelInputs
Component catalogue, documents, maintenance history, incoming readings.
Process
Map readings to components → apply subsystem weights → compute per-subsystem and composite BHI.
Outputs
Versioned BHI score with subsystem breakdown and confidence flags.
L-3Valuation engineInputs
BHI · NOI (measured) · comparables · cost baseline.
Process
Run three estimators independently → weight by data quality → blend → emit CI.
Outputs
Valuation + confidence interval + explainable contribution breakdown.
L-4Trust & complianceInputs
Readings, computed scores, valuation snapshots.
Process
Hash → batch → Merkle root → anchor → valuer signs.
Outputs
Signed, anchored report with verifiable hash path.
L-5ApplicationsInputs
User role · organisation · query parameters.
Process
RLS view materialises role-appropriate slice → UI composes KPIs.
Outputs
Role-scoped dashboard, alerts, exports, and signed reports.
L-6Roll-outInputs
Design-partner buildings and pilot KPIs.
Process
Instrument → measure → publish · widen coverage each phase.
Outputs
Case evidence, portfolio benchmarks, open signed city index.
InputsProcessOutputsTap a row to open its layer
100%
L-2

Asset & twin model

Component registry, documents, maintenance history, and a versioned Building Health Index (BHI) methodology.

TwinBHI-1.0 weightsStructural30%MEP25%Envelope15%Energy15%Safety10%Finish5%
100%

Every building is modelled as a tree of components across six subsystems — Structural, MEP, Envelope, Energy, Safety, Finish — each carrying design life, install date, criticality, and links to raw sensor channels. A document vault stores drawings, warranties, and inspection reports next to the components they cover. Scores are computed against BHI-1.0, a versioned methodology whose weights (30/25/15/15/10/5) are published, hashed, and cited by every score the platform emits. Older reports remain verifiable against the exact methodology version they were signed under.

Specifications
  • Subsystems: Structural 30 · MEP 25 · Envelope 15 · Energy 15 · Safety 10 · Finish 5
  • Methodology: BHI-1.0 · SHA-256 pinned · versioned
  • Registry: component tree · criticality · design life
  • Vault: drawings, warranties, inspections
  • History: maintenance events · work orders · downtime
  • Twin refresh: event-driven on new readings
Inputs

Component catalogue, documents, maintenance history, incoming readings.

Process

Map readings to components → apply subsystem weights → compute per-subsystem and composite BHI.

Outputs

Versioned BHI score with subsystem breakdown and confidence flags.

3 / 7