Support begins with the actual screen map and ends with a recoverable project record. The sequence below keeps decisions visible without turning the page into a generic claim of “full service.”
Provide active width and height in pixels, source formats, expected frame rates, switching topology and cabinet/receiver mapping. The review identifies scaling steps, unsupported assumptions and where a native-resolution test source is required. It does not replace the approved model sheet or the integrator's signal-flow drawing.
Keep controller settings, receiver-card files and cabinet mapping under a named revision. A useful package records who approved the change, which screen it belongs to and how to restore the last accepted state. Firmware changes remain conditional on model compatibility and a rollback plan.
Before a full wall is available, validate a representative cabinet chain with intended sources. Check address order, scaling, low-gray rendering, motion, communication stability and the selected redundancy behavior. Sample results cannot prove a finished installation, but they expose integration conflicts while access is still easy.
After the display reaches a stable operating temperature, run mapped test patterns, representative content and controlled failure exercises. Record brightness and color targets with the measurement method and environment. Outdoor light, broadcast cameras and close-view rooms require different acceptance conditions; one number does not cover every venue.
Walk operators through source selection, preset recall, alarm interpretation, safe restart and escalation contacts. The handover should distinguish routine recovery from actions reserved for trained service personnel. Store the approved files outside the controller so a failed workstation does not remove the recovery copy.
When behavior changes, compare firmware, configuration, cabling, source timing and thermal conditions against the accepted baseline. Avoid replacing multiple variables at once. A controlled review narrows the cause and leaves a record for the next event, maintenance window or module batch.
Attach the canvas map, source list, controller model, firmware information and the symptom or project constraint. Unknown fields can be marked for verification.