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

Roll-out

One tower → ten-building portfolio → API and city-level index.

Pilot · 1 towerQ4 2026Portfolio · ≤10Q1–Q2 2027API + city indexQ3 2027+Dubai · KLGCC + SEAOpen index
100%

The commercial motion mirrors the technical one. A single Demo Tower A pilot (Q4 2026) validates BHI, MTTR, and payback against pilot targets. A portfolio phase (Q1–Q2 2027, ≤10 buildings) proves cross-asset benchmarks and RLS scale. From Q3 2027 onwards, the platform opens a read API and publishes a city-level index — an open, signed, hourly-updating measure of built-environment health for Dubai and Kuala Lumpur.

Specifications
  • Phase 1 · Pilot: 1 tower · Q4 2026
  • Phase 2 · Portfolio: ≤10 buildings · Q1–Q2 2027
  • Phase 3 · API + city index: Q3 2027+
  • Targets: payback < 12 mo · MTTR −50%
  • Geographies: Dubai, Kuala Lumpur (first) · GCC + SEA (next)
  • Open surface: signed hourly city-level BHI index
Inputs

Design-partner buildings and pilot KPIs.

Process

Instrument → measure → publish · widen coverage each phase.

Outputs

Case evidence, portfolio benchmarks, open signed city index.

7 / 7