Line/Asset Grouping

[abishekve]

Allow endpoints grouped by Production Line → Machine → Device.
Live board mirrors shop floor layout

ThingConnect Pulse already supports hierarchical grouping of endpoints via YAML-defined Groups that are converted into database entities and used for UI filtering, and Milestone 1.3 specializes this into an explicit Production Line → Machine → Device hierarchy with a live board that visually mirrors the shop-floor layout.

Current grouping
Grouping exists today as hierarchical “Groups” in the YAML configuration, which the ConfigurationParser validates against the JSON Schema and converts into Group and Endpoint entities during the Apply flow.

The data model includes Groups and Endpoints, and the UI already supports searching and filtering by group with a live dashboard and endpoint detail views fed by REST APIs.

The v1 scope explicitly calls out “Groups and organization — hierarchical endpoint grouping,” meaning multiple levels are supported conceptually even if not yet opinionated for plant semantics.

Milestone 1.3 changes
This milestone formalizes the hierarchy as Production Line → Machine → Device, ensuring endpoints are attached at the Device level and rolled up to Machine and Line for status and quick scanning.

The live board will present a nested layout that mirrors the shop floor (Line cards, expandable Machine rows/cards, Device tiles), building on the existing live dashboard foundation.

The change is schema- and UI-focused: same persistence and Apply mechanics, with stricter validation for parent-child relationships and clearer rendering semantics aligned to plant operations.

Data model and YAML
No new storage primitives are required; continue to use Group entities with parent-child links and extend the YAML schema and parser validations to enforce Line → Machine → Device depth and uniqueness where appropriate.

The README’s Configuration Format already includes “monitoring group organization,” so the update is an additive specialization that provides examples and validation rules for the three-tier plant structure.

Apply retains versioning, diff preview, and dry-run validation; changes will appear in the diff, and snapshots will be stored as usual for audit and rollback.

Live board layout
The live dashboard remains the single real-time status view, enhanced to display hierarchical groupings with per-group rollups and 15-minute sparklines where available to aid at-a-glance triage.

API projections will expose nested group structures and rollup summaries so the client can render Line and Machine containers with aggregate status and drill-down into Device details.

This aligns with the roadmap’s emphasis on improved visualization for plant networks while staying consistent with the v1 live status and historical view patterns.

Acceptance focus
YAML with Line → Machine → Device applies cleanly, shows proper diff, and is versioned; UI can filter and navigate by each level without performance regressions.

The live board reliably mirrors the shop floor, with clear UP/DOWN state at each level and fast drill-down to device history using existing APIs.

All changes remain within v1 scope for availability monitoring and do not alter probe semantics, storage rollups, or the zero-dependency deployment guarantees