Overview

The Telemetry Hub is the central data store for QoS, QoE, and QoI metrics on the Clearshore / 5G-EMERGE platform. It sits under WP 2.3.1 — service monitoring, actionable data and network prediction — with EBU leading and HNR contributing.

This section of the site is the agreed home for shared dashboards and supporting documentation, alongside the Telemetry Project Tracking spreadsheet (TPT) which holds the canonical inventory and the Trello board where in-flight sprint work is managed.

Goals

Telemetry Hub work is anchored to the October 2026 deadline, with DTE Arctic Space as the proof point — success there is what unlocks expansion to other testbeds. Goals are expressed as outcomes measurable on Arctic Space alone.

Agreed so far:

Shared dashboards have a single home — this site. Dashboards are described and linked from this section.

Further goals to be agreed during Sprint 1 close.

Approach

Sprint cadence

Telemetry Hub work runs as a sprint cycle.

Cadence: one-week sprints.
Board: Trello / Jira.
Kickoff / close: each sprint opens and closes with a sprint review and planning meeting

Documentation

The testbed website is the home for all documentation related to the Telemetry Hub, including:

Overview - goals and approach
Sprint Plan
Architecture

Responsibility Assignment

Task	EBU (Hemini)	HNR (Kris)	HNR (Eng)
WP 2.3.1 tech note	X
Trello board ownership	X
Platform-side delivery accountability	X
Architecture		X
Technical design		X
Process definition		X
Current-state documentation		X
Repo-side artefacts		X
Implementation Engineering			X
Product Engineering			X

Todo

Sprint 1 deliverables

Overarching process written up and agreed — covers Approach/Process.
Sprint 2 scope defined — covers Engineering Work, Visualisations/Dashboards, Specs.
Sprint 3 scope defined — covers Engineering Work, Visualisations/Dashboards, Specs.