Ambulance fleet data report

1 Compatibility: protocols, controllers and sensors

Compatibility matrix

Sensors present per subvariant out of all sensors under each protocol and controller.

Check my fleet

Tick the protocols and controllers your fleet uses to see how much of each subvariant is covered.

Protocol, controller and sensor tree

Scope: sensor_profile FINAL, owner_oid 1616, three ambulance tenants; sensors matched by name.

2 Data and charts

2.1 Data coverage

2.2 Fleet

2.3 Captured data per sensor

2.4 Vehicle comparison

Lines per ambulance from entity_rollup windows (mean, with min-max band) drawn at window midpoint on a UTC axis.

2.5 Medical and clinical equipment

Every clinical sensor found in sensor_profile for these tenants, one chart each.

2.6 Sensors on only some subvariants

Non-clinical sensors that exist on one or two ambulance types and are not shown above.

2.7 Surges, drops and steps

Counts come from the surges, drops and steps columns of entity_rollup (events detected inside each 30-reading window), plus sensor_pass and incident tables where present. Surges, drops and steps are always shown separately.

2.8 Tags, rates and quality

Classification, rates, incidents and consistency checks.

2.9 Sensor explorer

2.10 Consistency checks

3 Inferences: how each tenant behaved

Each fact states the stored data it is drawn from.