schema_version: 1
model:
  id: iot-telemetry
  name: IoT Telemetry
  description: >
    An arc42 example: a fictional heat pump maker collects device telemetry
    over MQTT, stores it, raises alerts and shows it to operations and customers.
    main.archify holds section 3 business context with cards for sections
    1 goals, 2 constraints, 10 quality, 11 risks and 12 glossary;
    0300-context the technical context; 0500-building-blocks section 5;
    0600-runtime section 6; 0700-deployment section 7; decisions/ section 9;
    the crosscutting concepts of section 8 are a card on level-1.
diagram_type: architecture
meta:
  title: Business context
  output: main.html
components:
  - ref: homeowner
    pos: [40, 60]
    size: [130, 60]
  - ref: ops-engineer
    pos: [40, 160]
    size: [130, 60]
  - ref: installer
    pos: [40, 260]
    size: [130, 60]
  - ref: telemetry-platform
    pos: [280, 160]
    size: [150, 60]
  - ref: heat-pump
    pos: [540, 60]
    size: [130, 60]
  - ref: push-service
    pos: [540, 160]
    size: [130, 60]
  - ref: service-desk
    pos: [540, 260]
    size: [130, 60]
connections:
  - { from: homeowner, to: telemetry-platform, label: checks }
  - { from: ops-engineer, to: telemetry-platform, label: monitors }
  - { from: installer, to: telemetry-platform, label: registers }
  - { from: heat-pump, to: telemetry-platform, label: telemetry, variant: emphasis }
  - { from: telemetry-platform, to: push-service, label: alerts }
  - { from: telemetry-platform, to: service-desk, label: tickets }
cards:
  - dot: cyan
    title: 1 Quality goals
    items:
      - Reliability, no telemetry lost once accepted
      - Timeliness, alert within 60 s of a fault
      - Security, every device authenticated
  - dot: slate
    title: 2 Constraints
    items:
      - Devices speak MQTT only; firmware by a partner
      - Data stays in one EU region
      - Team of six; PostgreSQL skills in house
  - dot: emerald
    title: 10 Quality scenarios
    items:
      - A fault code reaches the homeowner within 60 s
      - Broker restart, devices reconnect, no data lost
      - A stolen certificate is revoked within 15 min
  - dot: rose
    title: 11 Risks
    items:
      - R1 fleet growth beyond one TSDB node
      - R2 partner firmware delays certificate rotation
  - dot: violet
    title: 12 Glossary
    items:
      - Telemetry, readings a device sends
      - Rollup, hourly aggregate of telemetry
      - Provisioning, giving a device its identity
      - Fault code, error number from the device