Routing Matrix
Main operational surface for Sender × Receiver links.
- Composition
- Filters, single/multi-select, Take / Release / Lock / Schedule.
- Solution
- Compatibility check and explicit statuses before critical actions.
Enterprise mediaNMOSMVP prototype
Media stream router for IP broadcast
Aligned the UX model before costly backend integration — the team got a prototype and specs for effort estimates and roadmap.
Context
Product module for media routing in IP broadcast: Sender → Receiver links in SMPTE ST 2110 and AMWA NMOS. Dense domain, industry standards, high cost of on-air mistakes, several professional roles.
Needed a shared product model before expensive backend work: how operators and engineers see the network, make routing decisions, use presets, and check compatibility — a consistent action language, not a set of screens.
Problem
Without a unified UX model, backend scope and priorities could not be estimated: a wrong action can affect broadcast; equipment integration is costly and risky.
SenderMedia stream source.
ReceiverMedia stream destination.
NMOS / ST 2110Standards for discovery, description, and routing of media streams.
Cost of errorWrong routing can break live broadcast infrastructure workflows.
Process
- Mapped the domain with product: engineer, operator, and ops roles; critical Take / Release / Lock / Schedule actions and scene-change scenarios.
- Competitive review (Nevion VideoIPath, EVS Cerebrum, Haivision StreamHub): matrix density, resource tree, presets, monitoring — market expectations without copying UI.
- Designed IA: matrix as default entry, devices as source of truth, Salvo as preset layer, journal as audit layer.
- Built clickable prototype with intentionally mocked actions and text specs — to align critical branches before development.
Solution
Devices
Source of truth for nodes, Sender/Receiver, and technical parameters.
- Composition
- NMOS tree, manual add, scan, cards and SDP.
- Solution
- Engineer sees the technical foundation without unnecessary magic.
Salvo and Journal
Presets and journal connect fast operations with control and incident review.
- Composition
- Presets, editor, immediate or scheduled run, live events.
- Solution
- Events and presets are part of the product model, not a secondary list.
Diagram: routing matrix
Link is selected, checked, applied, and logged — operational meaning of actions, not a decorative grid.
R-AR-BR-CR-D
S-01Take
S-12Lock
S-18Sched
S-24Ready
Result
Aligned UX vision for an enterprise module: prototype and specs as basis for product review, effort estimates, and backend prioritization.
4Key surfaces
Routing Matrix, Devices, Salvo, and Journal — IA and scenarios aligned before backend integration.
4Prototype screens
Clickable HTML/CSS/JS mocks — matrix, devices, Salvo, and journal.
4Critical actions
Take, Release, Lock, and Schedule — unified operation language with compatibility check before risky steps.
3Roles in model
Engineer, operator, and ops — scenarios and priorities fixed in specs for scope estimates.
NDA & AI
Anonymized case without production data. AI was used to accelerate research and draft prototyping; product decisions and final copy are by the designer.