Skip to content
The Platforms data plane

Hard-to-get signals.Ready for real work.

A governed collection and delivery layer for devices, shipments, sensors, and operational systems that do not fit cleanly into conventional business software.

Signal orchestration mesh

Source-native ingress · governed multi-consumer output

QoS 1 · retained state · topic contracts

Ingress

MQTT broker active

Policy

Validate · mask · preserve provenance

Output

Canonical event · 3 consumers

Interactive signal transformation

Machine data in.Business meaning out.

Follow two real edge-device inputs through the Platforms data plane: raw collection, decoding, post-processing, canonicalization, and delivery to AI agents or business users.

Guided demo · PulseBit ECG · Raw signal

Comma-delimited waveform

F-0-01,125,II,405,32,45,54,57,63,66,69,85,102,110,
116,118,110,98,85,75,58,42,33,21,7,4,3,2,3,-2,-5,
0,-1,-8,-16,-14,-8,-10,-14,-9,-4,-8,-4,6,8,-3…

The file begins with format, sample rate, lead, and calibration metadata, followed by 23,875 signed waveform values.

Lead

II

Sample rate

125 Hz

Samples

23,875

Duration

191 sec

Minimum

-1,744

Maximum

1,295

Collection plane

Preserve the source.Control the handoff.

Device-native streams and passive infrastructure observations enter through source-specific adapters, but leave through one explainable governance model.

01

Source adapters

Receive supported device, tracker, sensor, gateway, batch, or workflow events without forcing a user-facing application path.

Coverage matrix · payload samples · transport notes

02

Raw landing

Preserve source time, receive time, contract version, gateway context, and audit references outside the customer-facing record.

Lineage · freshness · event ordering

03

Validation

Apply contract, range, duplication, event-time ordering, and completeness checks before a signal becomes workflow-ready.

Accepted · rejected · under review

04

Identity boundary

Keep patient, customer, package owner, or account association outside the default signal path until an authorized workflow joins it.

Association owner · masked identifiers · access review

05

Governed output

Expose observations, condition states, timelines, and AI-ready records with provenance and operating limits intact.

Output schema · API shape · operator state

Device-native streaming

Event-driven frames, timestamped at the source and carried across wide-area transports into governed topics and processors.

Passive infrastructure observation

Network, RF, and operating-system telemetry without an application integration or end-user workflow.

Governance and validation

Trust is a state,not an assumption.

A signal becomes useful when the system can explain its source, time, mapping, completeness, identity posture, and review state.

Source-to-object contract

telemetry.spo2_percentvalues.spo2PercentRange checked · nullable
measurement.measurement_timemeasurementTimeSource time preserved
tracker.temperature_ccondition.temperatureCState generated separately
tracker.light_eventexceptions.lightExposureReview item · not damage proof

Explicit system states

Fresh
Delayed
Unavailable
Under review
Duplicate merged
Late ordered
File pending
Stale

Fresh

Ready for workflow review.

Delayed

Expected cadence has been exceeded.

Unavailable

Not published by the current source contract.

Under review

Hold before workflow use.

Governed outputs

Structured for machines.Legible to people.

Customer-safe records expose enough structure for workflow, analytics, automation, and AI-assisted review without leaking raw device internals or identity-heavy context.

Customer-safe observation

{
  "observationId": "obs_demo_7f42",
  "sourceType": "supported-health-device",
  "measurementType": "pulse_oximetry",
  "measurementTime": "2026-07-20T15:42:18Z",
  "receivedTime": "2026-07-20T15:43:02Z",
  "freshnessState": "fresh",
  "identityState": "unassociated",
  "values": { "spo2Percent": 97, "pulseRateBpm": 68 },
  "provenance": {
    "deviceFamily": "OxyS4",
    "contractVersion": "demo.v1",
    "gatewayRef": "masked"
  },
  "reviewState": "ready"
}

Evaluation

Prove the pathbefore scaling it.

Start with representative inputs, explicit boundaries, a reviewable output, and acceptance criteria your technical and operational owners can sign off.

01

Inventory supported sources and the manual workflow currently used to collect or reconcile them.

02

Review representative data, source timestamps, identifiers, unavailable fields, and required provenance.

03

Define where identity is excluded, where it may be joined, and which customer system owns the association.

04

Expose a bounded output for operators, analytics, automation, or AI-assisted review.

Technical review artifacts

Supported source and device coverage
Representative payload review
Source-to-object mapping table
Identity-association boundary
Freshness and validation rules
Customer-safe output schema
Security and tenancy review
Pilot acceptance criteria