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

Applications

Seven dashboards ordered by who pays: FM, Bank, REIT, Insurer, Developer, Valuer, Platform admin.

Data spineRLS · viewsFMBankREITInsurerDeveloperValuerAdmin
100%

Seven role-scoped surfaces sit on top of the same spine. Facility Managers see BHI, alerts, work orders, and silent devices. Banks see LTV headroom against a live-measured value. REITs see portfolio-level BHI benchmarks. Insurers see risk deltas tied to loss expectancy. Developers see fit-out vs occupancy signals. Valuers get a workbench that assembles the signed report. Platform admins manage tenancy, policies, and integrations. Every surface reads through Postgres row-level security views — no bespoke API glue, one policy layer, seven experiences.

Specifications
  • Surfaces: FM · Bank · REIT · Insurer · Developer · Valuer · Admin
  • Isolation: RLS-scoped views per role
  • Auth: email + Google · MFA optional
  • Access: org-scoped multi-tenant · audit-logged
  • Exports: PDF · CSV · signed reports
  • APIs: read-only for portfolio, gated for writes
Inputs

User role · organisation · query parameters.

Process

RLS view materialises role-appropriate slice → UI composes KPIs.

Outputs

Role-scoped dashboard, alerts, exports, and signed reports.

6 / 7