/

Ambitwin · source-available, not open source · © 2026 Nicolò Ghignatti

Telemetry Ingestion

Keywords on this page
WordMeaningExample
SensorA device connected to a roomThermometer T-204 in Lab 2
MetricA kind of thing we measureTemperature
ReadingOne value from one room at one momentLab 2, 14:05, 27 °C
LimitThe range a metric should stay in18 to 26 °C
Limit SetAll the limits of one buildingScience Hall’s limits
BreachThe time a room spends outside a limitLab 2, from 14:05 to 14:20
WindowA time range for looking at historyLast week
Building ReadyNews that a new building can be usedScience Hall is ready

Question: what is happening in each room, and is it OK? Kind: Core. Needs: Building Management, a reading needs a room.

Turns noise from devices into facts the platform can trust.


In the real world

Lab 2 has a thermometer. Every few seconds it says a number.

So three jobs: check it, keep it, judge it.


The model

classDiagram
    class Sensor {
        name
        room
    }
    class Reading {
        room
        metric
        time
        value
    }
    class LimitSet {
        building
        buildingLimits
        roomLimits
    }
    class Limit {
        metric
        min
        max
    }
    class Breach {
        room
        metric
        startedAt
        endedAt
    }
    LimitSet "1" *-- "many" Limit
    Reading "many" ..> "1" Sensor : comes from
    Breach "1" ..> "1" Limit : broke

A reading’s path

flowchart TD
    A["Reading arrives"] --> B{"Sensor connected?"}
    B -- no --> X["Rejected, with the reason"]
    B -- yes --> C{"Values make sense?"}
    C -- no --> X
    C -- yes --> D["Recorded"]
    D --> E["News: Reading Recorded"]
    D --> F{"Inside the limit?"}
    F -- "yes, and a breach was open" --> G["News: Breach Ended"]
    F -- "no, and no breach was open" --> H["News: Breach Started"]
    F -- "no change" --> I["Nothing else"]

Rejected readings never enter the platform. The sender is told why, so a broken device can be found.


Which limit applies?

The room’s own limit wins. Otherwise the building’s.

RoomOwn limitBuilding limitLimit usedReadingVerdict
Lab 218 to 2616 to 2818 to 2627Breach
Corridornone16 to 2816 to 2827OK

A building has exactly one Limit Set. A new one replaces the old, so nobody asks which limit was active.


One breach, many readings

A breach is a period, not a reading. This is what makes “one problem, one alert” true.

TimeValueLimit 18 to 26BreachNews
14:0025InsideNone
14:0527AboveStartsBreach Started
14:1027.5AboveStill open
14:1526.5AboveStill open
14:2025InsideEndsBreach Ended
stateDiagram-v2
    Inside --> Outside: reading breaks the limit
    Outside --> Outside: still breaking it
    Outside --> Inside: reading is back in range

Why here, and not in Alerting? Whether 27 °C is bad depends on the room, and that is this domain’s knowledge. Who hears about it is about people. That is Alerting’s.


Rules

  1. Only a connected Sensor is listened to. Disconnect it and its next reading is rejected.
  2. A Reading is never changed or deleted. A correction is a new Reading.
  3. A Reading says which building, which room, and when. Missing one means rejected.
  4. Each Metric has a name and a unit.

How a metric describes itself

name:  Temperature
unit:  °C

Telemetry Distribution collects these into its catalog. Describe Noise tomorrow and people can pick it right away.


Looking back

History comes from recorded readings.

Lab 2, temperature, Monday, average over the day
Readings:  22, 24, 27, 23
Average:   24 °C

What leaves this domain

WhatHowTo whom
Reading RecordedNewsDistribution
Breach StartedNewsAlerting, Distribution
Breach EndedNewsDistribution
Metric descriptionsShared listDistribution
Current values and limitsAnswer to a questionKnowledge & Assistance

Open questions