Write the requirement so it can be tested
An acceptance plan links a requirement to the object under test, method, operating conditions, decision rule and evidence. Begin with the viewer's task and the system's required behaviour. Convert each into a test that can be repeated on the supplied configuration.
SID's IDMS provides display measurement methods. It does not assign universal passing values to every display. Select the relevant complete method and establish project limits separately. Record the edition and section used, along with any deviations and their effect on comparability.
| Field | Example of what to specify |
|---|---|
| Object and configuration | Finished assembly, firmware, preset and installed glazing. |
| Requirement | Readable critical text from the agreed viewing positions. |
| Method | Defined content, viewing task, lighting and observation sequence. |
| Decision rule | Agreed pass/fail criterion and handling of borderline results. |
| Evidence | Raw readings, content revision, setup record and result. |
| Responsibility | Who performs, witnesses, resolves deviations and signs off. |
Separate measurement from operational acceptance
Luminance, colour, uniformity and temporal behaviour characterize the image. Power recovery, source switching, content scheduling, alarms and replacement workflow characterize operation. Installation checks cover mounting, access and the required environmental boundary. Give each its own requirement and result rather than relying on one demonstration.
Factory acceptance can establish the configured system baseline before shipment. Site acceptance adds the actual structure, power, signal route, room lighting and viewing geometry. Specify which results must be repeated after installation and which factory records remain applicable.
Decide how uncertainty affects the result
Record instrument calibration, repeatability and the uncertainty information applicable to the chosen measurement. Set the decision rule before seeing results. If a measured value sits near a limit, the plan should say whether to apply an agreed guard band, repeat the measurement, improve the method or classify the outcome for review. Avoid deciding the rule after the result is known.
Use the same source files and retain their version or checksum. Store configuration exports, firmware versions and instrument settings with the raw readings. A screenshot of a rounded number is weaker evidence than the original measurement record and setup description.
Make retesting part of the contract
Define the consequences of a failed test, the repair scope and the regression tests required after a change. A replacement module may need image matching; a firmware change may require timing and recovery tests; a new protective layer may require another optical and thermal evaluation.
- Requirement matrix and approved deviations.
- Factory/site test records and outstanding actions.
- Final drawings, topology and configuration backups.
- Operating instructions, service access and spare-part register.
- Named project roles for acceptance and support.
Use the downloadable blank record as a starting point. It is a VITREVIA project worksheet; selecting a formal standard procedure requires the complete referenced document.
Sources and further reading
- SID / ICDM: Information Display Measurements Standard, v1.3 (2025)
- IDMS v1.3: measurement-topic index
- Handbook of Visual Display Technology, 2nd ed. (Springer, 2016)
Calculations use the stated assumptions. Project procedures and acceptance limits must be defined for the supplied configuration.