AV Fault Evidence Pack for Remote Support

A support evidence checklist for AV faults covering screenshots, logs, firmware versions, signal path, room state, reproduction steps, and safe vendor escalation.

Remote AV support is only as strong as the evidence sent from the vessel. A ticket saying 'saloon TV not working' forces the vendor to guess. A support pack that includes room state, source selected, signal path, logs, firmware, recent changes, and guest impact lets the support desk diagnose faster and reduces the risk of unnecessary changes.

The evidence pack should be gathered before reboots, uploads, firmware changes, or remote-control sessions wherever the operational situation allows. It protects technical continuity and gives management a record of what was approved, what the vendor changed, and whether the fix was proven through the normal user path.

• Room, zone, source, display, audio path, lighting scene, control entry point, and exact symptom.
• Photos or screenshots of control UI, display errors, source warnings, rack LEDs, endpoint pages, and app/profile prompts.
• Reproduction steps and whether the issue is constant, intermittent, time-based, load-based, content-specific, or user-specific.
• Firmware/software versions for affected control processors, touch panels, AV-over-IP endpoints, DSP, lighting processor, display, and source.
• Recent changes: yard work, account changes, firmware, switch config, cable work, power events, edits by another vendor, or crew change.
• Network evidence where relevant: endpoint IP, VLAN, switch port, link speed, port errors, multicast/QoS status, and clock status.
• Operational impact: owner space, charter guest area, crew-only area, event commitment, safety-adjacent area, workaround available, and time sensitivity.

1. Prepare and freeze evidence: Collect the pack before rebooting or changing settings unless the situation requires immediate recovery. Mark what evidence was captured before intervention.
2. Approve access: Record supplier, named technician, access method, systems in scope, start time, expected duration, onboard contact, and approval owner.
3. Observe the session: Keep a live note of commands, file uploads, firmware changes, reboots, config edits, account changes, and tests performed.
4. Test user impact: After technical status looks healthy, run the normal guest user path from control point through source, video, audio, lighting, and shutdown.
5. Close out securely: Disable temporary access, store revised backups, export new logs where useful, record fix details, and list follow-up actions.

• Display fault: Route, EDID/HDCP clue, source output setting, direct test result, display error, and endpoint status.
• Audio fault: Zone, source level, DSP mute/route, amplifier channel, networked-audio clock status, and snapshot/preset state.
• Lighting fault: Scene name, keypad/control point, load affected, diagnostics/event logs, and recent scene edits.
• Control fault: Panel/tablet used, button sequence, processor/project version, macro result, and manual-route comparison.
• Network fault: Switch port, VLAN, multicast group, QoS/clock status, link errors, and whether other rooms fail under load.

A vendor support session can alter yacht systems as much as an onboard visit. Approve the scope, watch the changes, save the new baseline, and close access when the session ends.