← Curriculum
AV InstituteAV Institute LLC
07Week 7 · 5–7 hours

Installation, Commissioning & Troubleshooting

Field practices, acceptance, and fault isolation

The design and the code meet reality on site. Learn pre-install coordination, cable schedules, rack elevations, and power planning; installation practices and site safety; commissioning and acceptance; fault isolation for the classic AV failures; and client handover with documentation and training.

Key Competency

Plan an install, commission a system, and isolate field faults.

AV Institute
AV Institute · Week 7Installation, Commissioning & Troubleshooting
Lesson

System Commissioning Checklists & Acceptance Tests

Est. 55 minCompetency: Commission a system and run acceptance tests.

Learning objectives

  • Run a commissioning checklist systematically.
  • Define acceptance criteria for each function.
  • Verify audio, video, control, and network together.
  • Capture sign-off.

Vocabulary

Commissioning
On-site testing, tuning, and verification to spec.
Acceptance test
A formal test confirming a function meets the criteria.
Punch list
Items to fix before final acceptance.
Sign-off
Client confirmation the system is accepted.

Lesson content

Commissioning is where the design and code are proven against the spec. A checklist ensures every function is tested, tuned, and accepted — not left to 'it seemed to work.'

Commissioning checklist (by subsystem)

  1. 1Power: every device powers on; PoE delivering; UPS charged.
  2. 2Network: every device reachable on its IP; VLANs correct; Dante clocked.
  3. 3Video: every source displays on every intended output at the right resolution; EDID/handshakes clean.
  4. 4Audio: every mic heard; AEC verified by test call; no clipping; level comfortable.
  5. 5Control: every panel button does its action; feedback reflects real state; error states work.
  6. 6Conferencing: dial/hang; content share; far-end audio both ways; camera presets.

Acceptance criteria

  • Write a pass/fail criterion for each function before testing.
  • Test from the user's perspective (press the button, look at the result).
  • Record results on the checklist; raise a punch list for any fail.
  • Get client sign-off once the punch list is closed.
Acceptance is a contract

Acceptance is not 'the integrator feels done.' It is the client confirming each criterion passes. A signed checklist protects both sides and defines the start of the warranty period.

Worked example

Commissioning the conference room: power up; ping each device; display laptop on both displays at 1920×1080; speak into each ceiling mic and confirm no echo on a test call; run the Start/Join/Share/Shutdown sequence from the panel; confirm error states by pulling a cable. Every line checked and signed by the client.

Implementation checklist

  • ✓Commissioning checklist run per subsystem.
  • ✓Acceptance criteria defined and tested.
  • ✓Punch list raised and closed.
  • ✓Client sign-off captured.

Downloadable study guide

study-guide.txtcopy-paste ready
01. Commissioning checklist by subsystem: power, network, video, audio, control, conferencing.
02. Define pass/fail criteria before testing; test from the user's perspective.
03. Raise a punch list; close it; capture client sign-off.