Annotation and Collaborative Markup

Shared, persistent annotations let the crew point at the same thing, capture judgment, and hand off context across shifts and between control room and mobile.

Making the team's knowledge visible

A great deal of what keeps a machine safe lives in operators' heads: 'this diagnostic reads low after conditioning', 'watch this region during ramp-up'. Left tacit, that knowledge is lost at every shift change. L6 lets the crew annotate live surfaces — the 3D overlay, a KPI trend, an alert, a component — with notes that persist, are attributed, and are shared across the control room, mobile, and replay.

Annotations that travel

An annotation is bound to what it describes, not to a screen. A note left on a REBCO winding region in the 3D walkthrough appears when anyone inspects that component, shows up in the relevant dashboard tile, and is present in incident replay of that period. This binding is what makes annotations useful rather than clutter: context reaches the person who needs it because it lives on the thing it is about.

• Bound to a component, region, signal, or time window — not to a screen
• Attributed and time-stamped, part of the accountable record
• Visible across control room, mobile, walkthrough, and replay
• Types: observation, caution, follow-up action, resolved

Collaboration under pressure

During an upset, annotation becomes lightweight pointing: a session leader can flag the region of concern so every operator's view highlights the same spot, aligning the room without a spoken description that could be misheard. This shared deixis — everyone literally looking at the same marked thing — is a small feature that pays off most in the worst minute.

Annotations feed shift handover (open follow-ups carry forward), enrich incident replay (what the crew noted as it happened), and become part of the audit record. Persistent component notes also surface in the 3D walkthrough.