Skip to content
Skip to contentNexus Observatory
Nexus Observatory

/

Insurance and finance

/

Specialized fields

/

Event and claims verification

What happened, verified, so claims settle fast.

After a flood or storm, insurers need to know what happened at each property before loss adjusters can reach them all. Flood depth sensors at insured sites, drone surveys and local weather give a verified record of the event, so claims are prioritised, settled faster and treated fairly.

Plan a deploymentچگونه کار می‌کندStation Builder
صنعت
Insurance and finance
Measurements
4
Sources cited
4

At a glance

Scope the portfolio

The scope reads the insured areas, flood and storm exposure, claims history and adjusting process. Nexus Observatory Inc. returns the sensor and drone plan, event footprint design, claims integration and a price per area and per year. Every assumption in the scope is written down and priced.

مسئله

Thousands of claims at once

After a flood or storm, thousands of claims arrive at once, adjusters cannot reach flooded areas for days, and disputes over depth and duration slow settlement. Insurers must handle claims promptly and fairly, and policyholders need money to recover. Measurement turns that risk into decisions made in time.

Key facts

ابزارها
Flood depth sensors · Weather stations · Drone surveys
Links
LoRaWAN · Satellite · Public cellular
Drawn against
Insurance Core Principles · WMO-No. 168 · WMO-No. 8 · ISO/IEC 27001

Components

  • Pole-mounted edge gateway node
  • ISR quadcopter with a docking station
  • Ultrasonic flood depth sensor on a street light
  • Automatic weather station (AWS) to WMO siting practice
  • LoRaWAN gateway, endpoint and soil probe
  • “AI tower in a box”
  • PTP grandmaster clock with GNSS antenna
  • Hardware security module, 1U, in an edge rack

Interfaces

ابزارها
SDI-12 · RS-485 / Modbus RTU · 4–20 mA
Radio
Ethernet · LTE-M / NB-IoT · LoRaWAN
Time and position
GNSS 1PPS
Security
TPM 2.0
Publishing
MQTT

Where it works

  • Depth, weather and imagery
  • Working in the flood
  • For claims teams and policyholders

In the story below

  1. The system, part by part
  2. Assembly
  3. Installation
  4. Deployment
  5. Connections
  6. Operation
  7. Failure and recovery
  8. Scale and federation
  9. What you get

Scenes · 17

Next steps

Plan a deploymentOpen the Station BuilderOpen the Field Deployment StudioTalk to sales
  1. Insurance and finance · Event and claims verification

    Thousands of claims at once

    After a flood or storm, thousands of claims arrive at once, adjusters cannot reach flooded areas for days, and disputes over depth and duration slow settlement. Insurers must handle claims promptly and fairly, and policyholders need money to recover. Measurement turns that risk into decisions made in time.

  2. From order to operation · Order

    Scope the portfolio

    The scope reads the insured areas, flood and storm exposure, claims history and adjusting process. Nexus Observatory Inc. returns the sensor and drone plan, event footprint design, claims integration and a price per area and per year. Every assumption in the scope is written down and priced.

    Plan a deployment
  3. What is measured

    Depth, weather and imagery

    Flood depth sensors at insured properties and streets record depth and duration, weather stations record local wind and rain, and drone surveys after the event capture imagery where adjusters cannot yet go. Each reading carries its time and its quality flags.

    ابزارها
    Flood depth sensors · Weather stations · Drone surveys
  4. The base node

    The event footprint

    The node records depth and duration at every sensor, builds the event footprint, links it to insured properties and prioritises claims for adjusters. Every record is signed, so insurer and policyholder see the same evidence. Nothing is lost when a link drops; the node keeps it.

  5. From order to operation · Build

    Build and test

    Depth sensors are calibrated, radios paired, gateways, nodes and the drone kit configured and enrolled with their identities, and the event footprint tested with past events. Test results travel with the kit to the site. Nothing ships until the whole kit has passed its tests together.

    Open the Station Builder
  6. Radio and links

    Working in the flood

    Depth sensors reach gateways over a low-power link that keeps working in floods, a satellite path carries data when terrestrial networks fail, and the node and drone uploads use cellular where it works. Each link is chosen for the place, not from a catalogue.

    Links
    LoRaWAN · Satellite · Public cellular
  7. From order to operation · Commission

    Commission with a past event

    Each node proves its identity. Depth readings are checked against manual measures, and the footprint and claims prioritisation are tested by replaying a past event. Results are signed and kept with the site record; acceptance is recorded with the owner before handover.

  8. چگونه کار می‌کند

    From a flood to a settled claim

    A river floods a town overnight. Sensors record depth and duration street by street; by morning the footprint is linked to every insured home. Clear cases are settled from the verified record within days, and adjusters go first to the most damaged homes.

  9. From order to operation · Permits

    Consents and flights

    Property owners and cities approve sensors, drone flights follow aviation and privacy rules, and data sharing with policyholders is agreed. Every consent is kept with the area record; approvals are tracked site by site, so nothing waits unseen. No crew goes to site before its approvals are in place.

  10. شواهد

    Prompt and fair

    Verification supports prompt and fair claims handling under the insurance core principles, depths follow hydrological practice and weather the WMO guide, and records are protected to the information security standard. Every reading and claim record is kept. Records are open to the people who must check them.

    Drawn against
    Insurance Core Principles · WMO-No. 168 · WMO-No. 8 · ISO/IEC 27001
  11. Data products

    For claims teams and policyholders

    Claims and catastrophe teams receive event footprints; loss adjusters receive depth and duration by property; policyholders receive verified event records; adjusters and engineers receive drone imagery, each tied to property and time. Each product carries its site, time and quality flags.

    See the data products
  12. From order to operation · Operate

    Verify and settle

    During and after events, claims teams see depth and duration by property, prioritise visits, settle clear cases from the verified record and send adjusters where judgement is needed. Reports for owners and funders come from the same record. Every alert and action is kept on the record.

  13. From order to operation · Survey

    Survey insured areas

    Crews survey streets and properties for depth sensor positions, weather station sites, gateway coverage and drone flight areas. Findings are mapped; every finding is kept with the site record for the crews who follow. Findings shape the kit for each site before anything is built.

  14. From order to operation · Install

    Install across the area

    Crews install depth sensors at properties and streets, weather stations and gateways, and set up the node. Every sensor is surveyed to ground level and photographed; the site record is updated before the crew leaves. Crews follow the site safety plan throughout the work.

  15. From order to operation · Maintain

    Check before each season

    Sensors are checked and batteries replaced before each flood season, depth references resurveyed, software updated in rings, and every event record kept for review. Spares and procedures travel with the crews. Maintenance history stays with each site for its whole life.

    Book field services
  16. What you get

    Independent measurement feeds for parametric triggers

    Calibrated, tamper-evident measurement feeds that a risk carrier may name as the index source. The group writes no insurance and makes no payout decision. For event and claims verification, it goes to insurers, reinsurers, brokers and risk pools as a data licence, sized to the sites they run.

    Talk to sales
  17. Next step

    Plan event and claims verification with us

    Tell us the site, the measurements and the rules event and claims verification answers to, with a map if you have one. An engineer replies with a survey proposal, a design and a scope for event and claims verification, and the plan grows from one site to the network you need.

    Plan a deploymentOpen the Station BuilderOpen the Field Deployment Studio

More presentations

See it from every side.

Each opens as a full-screen presentation: deeper pages on the same subject, explainers, stories, guided tours of the places, network scenes and the observatories that came before.

All presentations

In depth

Specialized field · Insurance and finance Parametric insurance triggersMoney moves on a numberSpecialized field · Insurance and finance Physical climate risk for portfoliosDisclosure needs evidenceSpecialized field · Insurance and finance Bankable wind and solar resourceFinanced on the resourceISIC section · ISIC T Activities of households as employers; undifferentiated goods- and services-producing activities of households for own useHouseholds as employers and producers for own use

Explainers

Explainer · Energy Energy — SectorsWind and solar campaigns, turbine power curves, microgrids, grid-edge private LTE, line sag and fire-weather stations: an interactive explainer with the method behind every number.Explainer · Government and public safety Government and public safetyWildfire cameras on real terrain, GBON station density, street-flood alert thresholds, CAP alerting with the authority in the loop and the radio horizon of a deployable cell.سکو Digital twins and simulationPlans tested by the first floodسکو Space and satellite systemsOrbit and ground, on different records

Stories

Story · Data provenance chain From sensor to recordA published observation should carry its own history: which instrument made it, when, under which calibration, and every step since. The web already has a…Story · River basin and floods Rising water, counted in metresA flood map is a sentence about the future: this ground lies below that level. Gauges along the valley, a weather station and a terrain model turn the…Story · Forest and wildfire Seeing smoke soonerA fire is cheapest to fight in its first hour. Ridge-top cameras, weather in the stand and satellite hot spots each see it at different times and scales;…

Places and networks

Guided tour · Guided 3D tour Wildfire forestCamera masts on the ridges, a weather station in the stand and a private cell: the red ground is what the ridge camera can see.Guided tour · Guided 3D tour River basinWater-level gauges along a river valley floor, a weather station and an edge node: the red isoline is the ground that lies within a few metres of the lowest point of the reach.Guided tour · Guided 3D tour River and flood plainA radar stream gauge on the road bridge, a water-quality station on the bank and a groundwater well on the plain.Network scene · Backhaul · Fresnel zone Microwave backhaul across a river valleyAn 18 GHz hop from the church tower to a mast on the far side of the flood plain: its first Fresnel zone, clearance over the town and trees, and what a new building in the path…

Heritage observatories

Heritage observatory · United States · 1956 Mauna Loa ObservatoryAt 3,397 metres on a Hawaiian volcano, in air far from any city, a chemist began in 1958 to measure carbon dioxide continuously.Heritage observatory · United Kingdom · 1772 Radcliffe Meteorological Station, OxfordSince 1772 the grounds of the Radcliffe Observatory in Oxford have held a weather station, and its records, kept near one spot with every change written down, are the longest…

Interactive tools

Interactive tool · Configure a station Station BuilderConfigure a station part by part in 3D, check the rules as you go and request a quote for the assembly.

01The place and its hazards

Where it runs, and what can go wrong.

Operating context Insurers must handle claims promptly and fairly under the core principles of insurance supervision. Flood depths are measured to hydrological practice and weather to the WMO guide; drone surveys provide imagery where adjusters cannot yet go.

مخاطرات

  • Thousands of claims arriving at once after an event
  • Adjusters unable to reach flooded areas
  • Disputes over flood depth and duration
  • Fraud and inflated claims
  • Policyholders waiting months for settlement

02What must be measured

What, where, how often, and under which rules.

Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below.

MeasurementWhereCadenceمنابع
Flood depth and durationSensors at insured properties and streetsEvery few minutes during events12
Local wind and rainStations in insured areasEvery few minutes3
Post-event imageryDrone surveys over affected areasAfter each event2
Claims and verification recordsEach claim and its evidenceEach claim24

03The observation stack

From one base unit to a network.

The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol.

  1. 01

    Base unit

    A sensor: a flood depth sensor at a property on a low-power radio.

    Build a station →
  2. 02

    Site

    An area: sensors, a weather station, a gateway, a node and a drone kit.

    Plan a site →
  3. 03

    Fleet

    Insured areas across a portfolio on one event view.

    Managed offers →
  4. 04

    شبکه

    Insurers, adjusters and policyholders share verified event records through open standards.

    The open protocol →
  • 01Water level gauge
  • 02Compact weather station
  • 03Drone (UAS)
  • 04LPWAN endpoint
  • 05LoRaWAN gateway
  • 06Edge node (Wedge)
  • 07Cellular modem/router
  • 08LEO flat-panel terminal
  • 09Solar array

Radio and links

LoRaWAN

Depth sensors across streets reach gateways over a low-power link that keeps working in floods.

Radio and links

Satellite

A satellite path carries data when terrestrial networks fail.

Radio and links

Public cellular

The node and drone uploads use cellular where it works.

Edge compute The node records depth and duration at every sensor, builds the event footprint, links it to insured properties and prioritises claims for adjusters, with every record signed.

Power Sensors run on batteries; gateways and nodes on solar with batteries that outlast power cuts.

04چگونه کار می‌کند

From the instrument to the product.

One observation’s path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks.

Event and claims verification: data path

– of 08

01 Instruments Measurement with sensor identity and calibration 02 Field radio 03 Gateway 04 Node – Wrap in an observation envelope with time quality – Measure quality and uncertainty, attach quality flags – Buffer locally (store-and-forward when the link drops) 05 Backhaul Commit with transactional outbox and publish, delivered at least once 06 Site Consumer inbox deduplicates and applies each record once into governed data 07 Data store Governed product through API, map or export, correction-aware 08 Products OGC SensorThings API GeoJSON ACORD 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to the field equipment 01 Water level gauge SDI-12 · RS-485 · Ethernet 02 Compact weather station SDI-12 · RS-485 · Ethernet 03 Drone (UAS) USB · Video 04 LPWAN endpoint Analogue I/O · SDI-12 · RS-485 Drone ground control station Not in the reference kit 05 LoRaWAN gateway Ethernet · RF · GNSS antenna 06 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 · BMC 07 Cellular modem/router Ethernet · USB · RS-232 08 LEO flat-panel terminal Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Event footprints Depth and duration by property Verified event records Drone imagery 09 Solar array RS-485 SDI-12 SDI-12 MAVLink LoRaWAN Ethernet Ethernet Ethernet Ethernet LTE/NR Satellite IP
From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation.
Bill of materials
ItemEquipmentData portsProtocolsPower in
01Water level gaugeRadar, pressure or float gauge for river, lake, reservoir or tide level.SDI-12 RS-485 EthernetSDI-12, Modbus, MQTT 5, OGC SensorThings API12 V DC
02Compact weather stationAll-in-one or compact station for temperature, humidity, pressure, wind and rain at a site.SDI-12 RS-485 EthernetSDI-12, Modbus, MQTT 5, OGC SensorThings API12 V DC
03Drone (UAS)Uncrewed aircraft carrying sensors or a radio relay, operated within airspace rules.USB VideoMAVLinkInternal battery
04LPWAN endpointBattery-powered endpoint on LoRaWAN, NB-IoT or LTE-M that carries one or more sensors.Analogue I/O SDI-12 RS-485LoRaWAN, OMA LwM2M, CoAPInternal battery, Energy harvesting
05LoRaWAN gatewayMulti-channel LoRaWAN gateway that forwards uplinks to a network server and schedules downlinks within duty limits.Ethernet RF GNSS antennaLoRaWAN, MQTT 5PoE, 12 V DC
06Edge node (Wedge)Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure.Ethernet Fibre USB RS-485 BMCMQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA12 V DC, 24 V DC, 48 V DC, AC mains
07Cellular modem/routerLTE or NR modem or router that uses a public carrier or private network as backhaul.Ethernet USB RS-2323GPP E-UTRA air interface, 3GPP NR air interface, OMA LwM2M12 V DC, PoE
08LEO flat-panel terminalElectronically steered flat-panel user terminal for low-Earth-orbit broadband constellations.Ethernet—PoE, 48 V DC, AC mains
09Solar arrayPV modules with charge controller sized to the site’s load and climate.RS-485Modbus—

How it scales

01 Instruments Arbitrary qualified sensors and instruments whose measurements are ingested with calibration, units, geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, rugged appliance, radio node, sensor gateway, satellite terminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable local governance and failure domain: one or more nodes plus local network, identity, policy, evidence, storage, products and operator surfaces. SITE Node Node Node ×n 04 Cluster An optional scale or specialisation domain for scheduling, shared storage, accelerators or data locality. CLUSTER ×n 05 Fleet Coordinates plans, acknowledgements, convergence evidence, update campaigns and correction propagation across nodes and sites. FLEET Fleet controller ×n 06 Federation An exchange of products, capabilities, events or work across approved, independently administered trust domains, using explicit trust, policy, data-locality, version and correction contracts. TRUST DOMAIN TRUST DOMAIN TRUST DOMAIN ×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange
The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding.
Data in the field
MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
Telemetry
OpenTelemetry OTLP.
Control
TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
Data upstream
At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
شواهد
DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
رویدادها
Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
Exchange
OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.

05From order to operation

Every step, from the first call to a running site.

The same crew and the same record carry the work from scope to maintenance.

  1. 01 Order

    Scope the portfolio

    The scope reads the insured areas, flood and storm exposure, claims history and adjusting process. Nexus Observatory Inc. returns the sensor and drone plan, event footprint design, claims integration and a price per area and per year. Every assumption in the scope is written down and priced. 2

  2. 02 Survey

    Survey insured areas

    Crews survey streets and properties for depth sensor positions, weather station sites, gateway coverage and drone flight areas. Findings are mapped; every finding is kept with the site record for the crews who follow. Findings shape the kit for each site before anything is built. 1

  3. 03 Permits

    Consents and flights

    Property owners and cities approve sensors, drone flights follow aviation and privacy rules, and data sharing with policyholders is agreed. Every consent is kept with the area record; approvals are tracked site by site, so nothing waits unseen. No crew goes to site before its approvals are in place.

  4. 04 Build

    Build and test

    Depth sensors are calibrated, radios paired, gateways, nodes and the drone kit configured and enrolled with their identities, and the event footprint tested with past events. Test results travel with the kit to the site. Nothing ships until the whole kit has passed its tests together.

  5. 05 Install

    Install across the area

    Crews install depth sensors at properties and streets, weather stations and gateways, and set up the node. Every sensor is surveyed to ground level and photographed; the site record is updated before the crew leaves. Crews follow the site safety plan throughout the work.

  6. 06 Commission

    Commission with a past event

    Each node proves its identity. Depth readings are checked against manual measures, and the footprint and claims prioritisation are tested by replaying a past event. Results are signed and kept with the site record; acceptance is recorded with the owner before handover. 1

  7. 07 Operate

    Verify and settle

    During and after events, claims teams see depth and duration by property, prioritise visits, settle clear cases from the verified record and send adjusters where judgement is needed. Reports for owners and funders come from the same record. Every alert and action is kept on the record. 2

  8. 08 Maintain

    Check before each season

    Sensors are checked and batteries replaced before each flood season, depth references resurveyed, software updated in rings, and every event record kept for review. Spares and procedures travel with the crews. Maintenance history stays with each site for its whole life.

06Data products and integration

What it delivers, to whom, and into which systems.

Data products

  • Event footprintsClaims and catastrophe teams
  • Depth and duration by propertyLoss adjusters
  • Verified event recordsPolicyholders
  • Drone imageryAdjusters and engineers

Integration

  • Claims systemsVerified records attach to claims.
  • Catastrophe modelsFootprints calibrate event models.
  • Policyholder channelsPolicyholders see verified records for their property.

Exchanged through OGC SensorThings API, GeoJSON, ACORD.

07Questions buyers ask

Before you scope it.

Can claims settle without a visit?

Clear cases can, from the verified record, where policies allow.

Does it help against fraud?

Measured depth and duration make claims verifiable.

What if networks fail?

Low-power radio and satellite keep data flowing.

Can policyholders see their data?

Yes, for their own property.

08منابع

The sources behind this page.

Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does.

  1. 1WMO-No. 168: Guide to Hydrological PracticesWorld Meteorological Organization
  2. 2Insurance Core PrinciplesInternational Association of Insurance Supervisors
  3. 3WMO-No. 8: Guide to Instruments and Methods of ObservationWorld Meteorological Organization
  4. 4ISO/IEC 27001: Information security management systemsInternational Organization for Standardization

09مرتبط

Use cases and solutions.

Use case

Street flood observatory

Ultrasonic depth sensors on poles report street-level water depth as open data and alerts. The full use case →
Solution

Independent measurement feeds for parametric triggers

Calibrated, tamper-evident measurement feeds that a risk carrier may name as the index source. Solutions for insurance and finance →
Solution

Drone survey and 3D site twins

Survey campaigns planned to the ground sample distance, photogrammetry and LiDAR, and site twins kept current. Solutions for insurance and finance →
Solution

Environmental exposure monitoring for health programmes

Heat, air and water exposure measurements around facilities and communities; no diagnosis or treatment. Solutions for insurance and finance →

10Insurance and finance: specialized fields

Other fields of this industry.

Specialized field

Parametric insurance triggers

Tamper-evident weather and water stations that measure the indices parametric policies pay on, with signed data that insurers, reinsurers and policyholders can all trust. The full field →
Specialized field

Physical climate risk for portfolios

Measured hazards at the sites of a portfolio, from flood and heat to subsidence, so lenders, investors and insurers assess and disclose physical climate risk with evidence. The full field →
Specialized field

Bankable wind and solar resource

Met masts, lidars and irradiance stations that measure wind and solar resources to the standards lenders require, so renewable projects reach financial close on evidence. The full field →

Bring us the site.

Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details.

Plan a deploymentStation BuilderOpen the StudioTalk to salesRequest a quote