top of page

Home › Knowledge Center › Specification and RFQ Guide

Outdoor Display Specification and RFQ Guide

An effective outdoor display specification describes the project before it prescribes the product. It tells suppliers what the display must do, where it will operate, how it will be installed and integrated, which evidence is required and how the delivered system will be accepted.
 

This guide helps buyers, consultants, integrators and sales-engineering teams prepare a comparable, evidence-aware request for quotation. It does not supply fixed brightness, ingress, temperature, cooling, power or certification defaults. Those requirements must follow from the application and be answered for an applicable configuration.

Outdoor display RFQ process Project context to an agreed acceptance basis Context Application Site and operation Requirements Mandatory needs Preferences Supplier response Configuration Assumptions Evidence Type and scope Applicability Exceptions Alternative Impact and review Acceptance Method and conditions Responsible owner Agree the requirements, evidence and acceptance basis for this project. The sequence does not imply automatic compliance or acceptance.

Start with the application, not a copied specification

Specifications copied from another project often carry hidden assumptions about environment, viewing, mounting, regulations and evidence. A familiar value can look precise while being poorly matched to the new site.

Define the operational purpose

State what the display will communicate and who depends on it. Advertising, wayfinding, passenger information, menus, public notices and interactive service have different priorities. Identify which information is critical, how quickly it must be understood and what operational consequence follows if it is unavailable.

Identify stakeholders and responsibilities

List the buyer, consultant, supplier, installer, electrical contractor, network owner, CMS owner, operator and maintainer as applicable. Define who provides site information, approves drawings, supplies interfaces, configures systems, witnesses acceptance and owns ongoing support.

Separate requirements from preferences

A mandatory requirement affects compliance or acceptance. A preference may improve usability, appearance or commercial flexibility. Marking the difference helps suppliers propose alternatives without concealing an exception.

Describe the site and environment

The RFQ should give suppliers enough site context to understand exposure and installation constraints.

Location, orientation and surroundings

Record whether the installation is indoor-facing-out, semi-outdoor or fully outdoor; its location and orientation; nearby walls, glass, roofs or heat sources; public access; and any recess, canopy or decorative surround. Site photographs or non-confidential drawings can help when their date and viewpoint are clear.

Climate and environmental exposure

Describe expected sunlight, seasonal conditions, humidity, rain exposure, wind context, airborne dust, salt or industrial contaminants where relevant. Do not convert a general climate description into an exact product rating without an engineering basis.
 

SUNTUNE evaluates environmental requirements according to application conditions. This supports configuration review for the stated site; it is not a universal performance or environmental-resistance guarantee.

Access and operational constraints

Include delivery access, installation hours, lifting or handling constraints, public-area restrictions, maintenance access and any expected coordination with other trades. These conditions can affect enclosure, mounting, segmentation and service planning.

Site information for an RFQ Record the context before requesting a product response Orientation Position and surroundings Sun and weather Exposure and seasonal context Contaminants Dust, salt or industrial context Access Delivery and public-area constraints Structure Known site support interfaces Utilities Power and network boundaries Service route Maintenance access and ownership Generic site plan Display and access context Not a customer site

Define viewing and optical requirements

The specification should describe the viewing task before assigning an optical value.

Viewing context

Provide primary viewing distance and angle, viewer movement, installation height, expected reading time, content type and critical legibility needs. Note likely reflections and whether polarized eyewear is relevant to the audience.

Sunlight and surrounding light

Describe direct sun, sky exposure, shade patterns, glass interfaces and reflective surroundings. If an exact optical requirement is mandatory, identify how it will be evaluated and ask the supplier to state the applicable configuration and evidence.

Screen-size context

Screen size should follow content, viewing distance, layout, site constraints and information hierarchy. State available space, orientation and any multi-screen concept. Do not assume that a nominal diagonal alone defines readable text size or the complete installed dimensions.

Define thermal and operating conditions

Thermal requirements should describe loads and context rather than dictate a cooling method without analysis.

Thermal management requirements

Ambient, solar and installation context

Provide available environmental data, sun and shade exposure, mounting or recess conditions, nearby heat sources and airflow constraints. Ambient air is one input; it does not fully describe sunlit surfaces or internal components.

Duty cycle and operating behavior

State daily and weekly operating schedules, expected continuous periods, planned standby behavior and any critical availability windows. Where display output or content operation materially affects the requirement, describe the assumption.

Cooling architecture response

Ask the supplier to identify the proposed thermal architecture and the assumptions behind it. Do not automatically prescribe passive, fan-assisted or AC-assisted cooling.

 

SUNTUNE offers fan-based and AC-assisted cooling depending on project requirements. The applicable approach depends on configuration, enclosure, environment, installation, duty cycle and engineering review; the statement does not assign a cooling system or capacity to every product.

Define enclosure and environmental protection needs

Environmental protection combines enclosure boundaries, penetrations, drainage, condensation control, materials and maintenance. A single rating does not answer every exposure question.

Ingress and exposure

Describe where water and particles may come from and which surfaces or interfaces are exposed. If an ingress rating is mandatory, state it as a project requirement and ask which complete configuration and evidence support the response. Do not insert a default rating merely because it is common in another application.

Condensation and corrosion context

Identify humidity, temperature cycling, coastal salt, pollutants, cleaning practices and persistent moisture where relevant. Ask how the proposed configuration addresses the applicable mechanisms. Do not treat ingress, condensation and corrosion as interchangeable claims.

Materials, appearance and cleaning

State appearance, finish, cleaning, impact or public-contact requirements when they affect design. Any exact material, coating or corrosion-performance claim should be tied to the proposed configuration and evidence.

Define mounting and physical integration

Mounting requirements connect the display to the site and influence structure, thermal behavior, drainage, cables and service access.

Installation form

Identify wall-mounted, pole-mounted, freestanding, kiosk, recessed, suspended or video-wall intent. Provide known site interfaces and state who is responsible for supporting-structure assessment, fixings, foundations, lifting and installation design.

Dimensions and interfaces

State space constraints and required clearances, but ask the supplier to provide controlled dimensions and interface information for the proposed configuration. Avoid copying a dimension from an unverified page or a different model.

Access and maintainability

Define front, rear or other access constraints, safe working space and any restriction on closures or surrounding finishes. Ask which service items require access and how the proposed arrangement supports maintenance.

Physical interfaces for an RFQ Define boundaries and responsible parties Proposed display Controlled configuration Support structure Assessment and responsibility Site interface Known constraints and ownership Cables Electrical and digital boundaries Airflow Exposure and clearance context Drainage Moisture path and site context Service zones Access and maintenance needs Interface questions only; not an installation drawing or dimension/capacity claim.

Define electrical, network and CMS boundaries

The RFQ should describe interfaces and responsibility without attempting to replace product-specific or regional instructions.

Electrical market and site supply

Identify destination country or market, available site supply, distribution boundary, isolation ownership, grounding or bonding responsibility and relevant project constraints. Ask the supplier for applicable electrical information and documentation for the proposed configuration.

​

​Do not set power consumption, protection devices, conductor sizes or installation procedures without the required design authority and controlled information.

Network and connectivity

State the expected network medium, ownership, addressing or security constraints, remote-access policy and monitoring requirement. Clarify which party supplies gateways, switches, modems or other network equipment.

CMS and content-system integration

Identify the CMS, media player, content formats, scheduling, user roles, data interfaces and acceptance responsibility where known. A network connection does not by itself establish CMS compatibility or integration scope.

Define service, lifecycle and handover needs

A commercially complete RFQ considers what happens after installation without turning public requirements into service procedures.

Maintenance context

Describe access, local service capability, expected inspection ownership, cleaning constraints and any requirement for replaceable service items. Ask for applicable maintenance documentation rather than inventing a universal interval.

Spares, support and change control

If spares or support are required, define the commercial and operational need and ask the supplier to state the offered scope. Changes to components, enclosure, controls or layout should be managed because they may affect the approved configuration.

Handover records

Identify the documents and records required at handover, such as approved drawings, configuration identification, user documentation, acceptance records, applicable certificates or declarations, and responsible contacts. Exact availability depends on the project and proposed configuration.

SUNTUNE can support project-specific documentation and review where applicable. Availability, format and scope depend on the configuration, destination market, project requirements and agreed deliverables.

Define certification and documentation requirements

Certification language should be precise enough to avoid both overclaiming and late-stage surprises.

State the destination and requirement

Identify the destination market, customer standard, tender requirement or authority having jurisdiction. Do not request a generic certification set without checking applicability to the configuration and market.

Ask for scope and applicability

Request the document type, issuing body where relevant, covered product or configuration, revision or validity information, and any exceptions. A certificate for a component or another configuration should not be assumed to cover the complete proposed system.

Protect confidential evidence

Not every supporting document belongs on a public page or in an unrestricted tender appendix. Define how controlled evidence will be reviewed, who may access it and what public statement may be derived from it. Confidential review does not authorize public disclosure.

Requirements, evidence and exceptions Review scope before approving a public statement Requirement State the need and destination Configuration Identify the offered system and revision Evidence Identify type and applicable scope Reviewer Check applicability and review access Exception Record deviation and needed approval Public statement Approved wording within evidence scope Keep demonstration, controlled measurement and certification documents distinct. Confidential evidence review does not authorize public disclosure.

Build acceptance criteria around the project

Acceptance criteria should state what will be checked, under which conditions, by whom and against which approved baseline.

Factory and site acceptance scope

Factory review and site acceptance answer different questions. Define which items are checked before shipment, after installation and during handover. Keep practical demonstrations distinct from controlled tests and certification processes.

Configuration baseline

Acceptance should reference the proposed and approved configuration, including relevant options, drawings and software or control state. This reduces ambiguity when several variants exist.

Exceptions and deviations

Require suppliers to list exceptions rather than hiding them in narrative. Each deviation should identify the affected requirement, proposed alternative, consequence and evidence or approval needed.

Request evidence that matches the claim

Evidence should be proportionate to the requirement and applicable to the response.

Do not treat a marketing page, unlabeled photograph, informal demonstration or unrelated component document as sufficient proof of product-specific performance, ratings, certification or guarantees.

Supplier questions for a governed RFQ

Ask suppliers to answer clearly:

  • What configuration is proposed and what assumptions shape it?

  • Which requirements are standard, configurable or project-specific?

  • How are optical, thermal and environmental needs addressed?

  • What site, structural, electrical, network and CMS responsibilities are excluded or assigned elsewhere?

  • Which documents and evidence apply to the proposed configuration and market?

  • What exceptions, alternatives or dependencies should be recorded?

  • What maintenance, access and handover conditions should the buyer plan for?

  • How will factory review, site acceptance and issue resolution be managed?

Comparable responses require a common question set, a clear exception schedule and traceable evidence—not simply more numbers.

Concise outdoor display RFQ checklist

Before issue, confirm that the RFQ covers:

  • application and critical information task;

  • site, orientation, climate and exposure;

  • viewing context and content assumptions;

  • screen-size and installation-space context;

  • duty cycle and thermal environment;

  • mounting, structure and service access;

  • enclosure, moisture and corrosion requirements;

  • destination electrical market and site interfaces;

  • network, CMS and integration boundaries;

  • documentation, certification and evidence needs;

  • acceptance criteria, handover and exceptions;

  • commercial schedule and responsibility owners.

The checklist is a completeness prompt, not a source of default technical values.

Request a specification and RFQ review

Provide a concise, non-confidential project or RFQ summary covering:

  • application;

  • installation location;

  • environmental conditions;

  • viewing requirements;

  • mounting concept;

  • destination electrical market;

  • network and CMS needs;

  • documentation or certification requirements;

  • target schedule.

Do not submit confidential RFQs, customer drawings, tender documents, site files, private specifications or commercially sensitive attachments through this public intake. Detailed or confidential project documents may be exchanged later through an approved secure channel where appropriate. No upload mechanism is offered or implied by this candidate.

The review can identify missing inputs, hidden assumptions, evidence gaps and supplier questions without prescribing unsupported product values.

Frequently asked questions

Should every outdoor display RFQ specify the same brightness?

No. The requirement should follow from ambient conditions, viewing task, optical stack, content and acceptance method. Ask the supplier to identify an applicable configuration and evidence.

Should an RFQ automatically require IP65?

No. Define the exposure and project requirement, then request an applicable enclosure response and evidence. Do not use a rating as a substitute for condensation or corrosion planning.

Should the buyer choose the cooling system?

Usually the buyer should describe the thermal environment, duty cycle and constraints. The supplier can then state the proposed architecture, assumptions and evidence unless the project has a justified mandatory design requirement.

What site information is most important?

Location, orientation, sunlight, climate, contaminants, mounting, access, viewing geometry, power, network and service constraints are core inputs.

How should certification requirements be written?

Name the destination market or tender requirement and ask the supplier to state which document applies to the proposed configuration, including scope and exceptions.

What makes supplier responses comparable?

A common requirement set, explicit assumptions, a structured exception schedule, identified configurations and evidence linked to each material claim.

Is a factory demonstration enough for acceptance?

It can support agreed practical review, but it is not automatically a controlled test or certification. Define what is being demonstrated, under which conditions and what other evidence is required.

bottom of page