← All cases

Enterprise platformNodes & servicesOperational UX

Node and media service configuration platform

Connected monitoring, orchestrator, and configuration in one IA: operators see fleet health at entry; engineers reach nodes, devices, and services without losing context.

Context

Corporate platform for media infrastructure operations: hundreds of devices, several environments, connection orchestrator and active services. Users are engineers and operators switching between monitoring, node setup, and media flow control.

Design platform entry and cross-navigation: not isolated screens but a model where fleet health is visible, module boundaries are clear, and critical configuration flows are fast.

Problem

Without aligned IA each module lived alone and operators lost time orienting:

Fragmented entryMonitoring and orchestrator unlinked — unclear where to start a shift.
Status buried insideAgents, PTP, and RDS visible only deep in modules, not on overview.
Complex node hierarchyDevices, essences, and services — different entities without clear nav links.
RBAC without explanationLocked sections looked broken, not permission-limited.
Long transitionsFrequent flows (nodes → Connect → services) needed extra clicks.

Process

  1. Mapped roles and shift scenarios with product: what operators check first, where engineers go in incidents, which metrics must be visible.
  2. Designed home IA: section tiles with live metadata (devices, dashboards, nodes, services) and quick links for cross-module jumps.
  3. Unified platform shell — topbar, branding, profile, sound, notifications — and module sidebar for deep flows (nodes, resources, Connect, services).
  4. Defined status model: agent dots, PTP/RDS badges, tile warnings — critical signals readable on first screen.
  5. Built clickable prototype and specs to align scope with engineering and roadmap.

Solution

Platform home

Entry point with fleet overview, not menu for its own sake.

Composition
Monitoring and Orchestrator tiles with device, dashboard, node, and service counts.
Solution
Live metadata and status on tile — operator knows where to go without opening every module.

Nodes and resources module

Single shell for infrastructure configuration.

Composition
Sidebar nav, node screens, media devices, Connect, and services in one wrapper.
Solution
Project and standard context (ST 2110 · NMOS) visible in header — engineer keeps domain across jumps.

Quick links and statuses

Cross-module navigation and honest availability model.

Composition
Quick links block, agent dots, PTP OK / RDS Ready, disabled states with explanation.
Solution
Frequent routes in one click; locked sections clearly marked (Coming soon, No access).

Diagram: platform entry

Not final UI but logic: overview → module → action. Status and counts follow the user at each level.

Monitoring 512 / 1000 · 8 dashboards 1 unavailable
Orchestrator 5 nodes · 12 services · 15 connections PTP OKRDS Ready

Result

Aligned platform model: team got prototype and IA for scope estimates, module prioritization, and consistent operational UX between monitoring and orchestrator.

4Home sections

Monitoring, orchestrator, scheduler, analytics — hierarchy and MVP boundaries fixed.

4Configuration screens

Nodes, media devices, Connect, services — unified shell and sidebar nav.

4Quick links

Devices, essences, Connect, services — frequent routes without extra hops.

3Status signals

Agent dots, PTP, and RDS — critical infrastructure health on overview.

NDA & AI

Anonymized case without production data. AI accelerated prototyping; IA, priorities, and final copy are by the designer.

First case Get in touch