TOOL / EVIDENCE CHECK

What backs up the promise?

Choose a claim from an offer. Get three things to check and specific supplier questions for your project.

01 / Brightness

“Readable even in sunlight.”

A shop window, transit stop or outdoor wayfinding point: put the actual location in the requirement before comparing a figure.

Request documentation

Request luminance for the exact model, including measurement conditions, operating mode and temperature-related derating. Document glass, orientation, shading and the intended viewing position.

Test within the project

Sample real content from the worst intended position at relevant times of day. Check a price, destination name or action prompt with intended readers. Record weather, reflections and settings.

Record the limits

Luminance in cd/m² does not describe readability on its own. A brief test under overcast skies does not cover all agreed operating conditions.

Questions to put in the inquiry

Which exact model, mode and measurement conditions does the figure cover?
What luminance remains available under the expected thermal load?
How will we agree a readability test using our content on site?

Use in the project brief ↗

Request model-specific approvals from the supplier.

Read the background

Foundations & scope

BIPM — Principles governing photometry (2019)
Photometric terms and the SI unit of luminance. No recommended brightness figure for display installations.

02 / 24/7 operation

“Suitable for continuous operation.”

A duty-cycle claim needs to match installation and use. A display alone does not keep an entire site available.

Request documentation

Request written approval for the exact model, orientation, temperature range and intended content. Clarify warranty terms and the treatment of persistent static elements.

Test within the project

Agree a pilot observation period appropriate to the use. Check a scheduled restart, power interruption and player recovery. Define in advance which content should appear after startup and who handles failures.

Record the limits

24/7 is not a promise of a specific lifetime or a failure-proof system. A successful restart test does not prove long-term reliability.

Questions to put in the inquiry

Does the approval cover our orientation and content?
Which conditions and exclusions apply to continuous operation?
How do we test recovery and who takes responsibility for an outage?

Use in the project brief ↗

Request model-specific approvals from the supplier.

Read the background

Foundations & scope

Planning advice: check the model-specific documents for your use. Procurement documents

03 / IP protection

“The unit is weatherproof.”

Move from the marketing word to the installed assembly: identify the enclosure, connectors and service openings precisely.

Request documentation

Ask for the stated IP classification and its test report or traceable test basis for the exact configuration. Request information on seals, cable entries, orientation and required maintenance condition.

Test within the project

Have the installed configuration checked against the documents: are the specified closures, seals and entries present? Record deviations and request an assessment. Standardized protection testing needs an appropriate specialist; do not perform an improvised hose test.

Record the limits

IEC 60529 classifies enclosure protection. An IP marking alone does not establish thermal suitability, UV resistance or protection from every form of condensation.

Questions to put in the inquiry

Which exact assembly and condition were tested?
Which connectors and openings belong to the documented configuration?
What additional evidence do we need for heat, UV and condensation?

Use in the project brief ↗

Request model-specific approvals from the supplier.

Read the background

Foundations & scope

IEC 60529 — Degrees of protection provided by enclosures (IP Code)
Public standard description for classifying enclosure protection. No specific display was tested. Consult the full standard for test procedures.

04 / CMS & outages

“Content keeps playing offline.”

“Offline” may mean local playback. Live data, schedules and remote management can behave differently.

Request documentation

Have the provider and content owner document which content types are held locally, which data needs a connection and how long fallback content may be used. Clarify storage limits, time source, update process and ownership.

Test within the project

Disconnect the network during an agreed pilot. Observe a schedule change and restart the player without connectivity. Reconnect it and check that current content returns. Document behavior for stale prices or live data.

Record the limits

One locally stored video does not prove offline support for every content type. Device updates remain a separate operational task; BSI update guidance does not replace product-specific CMS testing.

Questions to put in the inquiry

Which of our content types remain usable without connectivity?
What appears after a restart without a connection?
Who decides when stale content must be replaced by a safe fallback?

Use in the project brief ↗

Request model-specific approvals from the supplier.

Read the background

Foundations & scope

BSI — Setting up a smart home securely
General advice on connected devices, updates and security. Not a signage-specific standard; establish update and access requirements for the particular system.

05 / Touch & interaction

“The touchscreen works with gloves.”

The real task defines the test: glove, glass, application and environment belong together.

Request documentation

Ask for supported input methods and the tested combination of controller, sensor, glass and software. Document the actual gloves, cleaning products and environmental conditions for your project.

Test within the project

Have intended users complete the full task with their actual gloves: select, correct, confirm and cancel. Check edge areas, unintended inputs and reach to controls. For public devices, test session reset too.

Record the limits

A touch-technology name does not approve every glove type. A web target-size criterion does not automatically assess physical reach to an installed kiosk.

Questions to put in the inquiry

Which exact glove and glass combination was tested?
Can our users complete a whole task without input errors?
What alternative is available when input is not recognized?

Use in the project brief ↗

Request model-specific approvals from the supplier.

Read the background

Foundations & scope

EIZO — A basic understanding of touch panels
Manufacturer explanation of sensing principles. Article dated September 2010; performance and trend comparisons are not treated as current. Does not approve a specific assembly.
W3C — WCAG 2.2, Target Size (Minimum)
Requirements and exceptions for target sizes in web interfaces. Does not certify a kiosk or this guide as a whole.

Supplier questions in your brief.

Take these questions into your project brief. Record which answers are missing and who will check them. An export does not send an inquiry.

Create a project brief