DO-160 Display Qualification | A-P02 — Draft / Not Released

Learning objective: Create traceability from requirement to test and installation limitation.

A matrix is an argument, not a checklist of ticks

Each row should state what is required, why the environment applies, how the condition is represented, what performance is acceptable and where the evidence can be found. Keep applicability, planned method and completed evidence separate. “Planned” is not “passed,” and a report issued with unresolved deviations may not close the row.

Do not hide unresolved inputs

If maximum operating altitude or the power category is unknown, assign an owner and due point. A provisional category may be useful for quoting, but label it and state the cost/schedule consequence of change. A supplier cannot finalize every installation allocation from the display data sheet alone.

Allocate test articles

Multiple articles can be used where permitted, but respect sequence and cumulative-exposure requirements. Maintain an exposure history per serial number and record repairs, replacements and software changes. A report assembled from results on different hardware needs a clear representation and configuration argument.

Exercise

Your matrix says vibration passed, but the cited report tested an earlier mounting bracket. Worked response: keep the result as existing evidence, mark the current configuration credit unresolved and assess the difference. Close the row only with justified applicability or affected retesting. The report's pass word does not settle configuration relevance.

Deliverable

Create all 23 section rows, then expand the applicable sections into subtests. Add during/post/survival criteria, article allocation and installation constraints. Use a separate unresolved-input list to prevent empty fields being misread as intentional exclusions. The contract lesson shows how to make this matrix part of the purchased deliverable.