Concept visualisation of an integrated digital signage and LED display environment in Dubai
Solution 04 / 10

AV systems integration

Digital signage & retail displaysin Dubai & the UAE

The right message, on the right screen.

Publish the right information across one screen or a managed display network.

  • Acceptance on your scenarios
  • Documentation and training
  • 12-month workmanship warranty
  • The right messageStart with content, timing and audience.

  • One or many screensMatch management to the display network.

  • Planned publishingAgree schedules and ownership of content.

  • Managed accessDefine publishing and support roles.

01 What we deliver

Plan the publishing workflow as carefully as the displays.

A screen shows the image. A player runs the presentation. A content management system (CMS) distributes media and schedules. Your content team owns the messages, languages and review process. Interactive wayfinding adds a separate application with maps, search and tenant data.

We define these responsibilities before selecting equipment. Display size, brightness and placement follow the viewing conditions; player and software selection follow the actual content. Every managed screen has an identity, a publishing destination and a documented service procedure.

Reference configurations · subject to project design and validation. The examples below describe intended functions and quantities. They are not fixed purchase packages or completed installations. Final software, licences and device compatibility are confirmed for the project.

Background music for a retail space needs its own zones, sources, processing and amplification. Explore hospitality AV for that separate scope. Large display surfaces are also covered in LED & LCD video walls.

Where it is used

Real spaces, the people in them and what matters.

Who works in each kind of digital signage & retail displays space, what they work with, and which typical configuration it usually starts from.

Application register
No.EnvironmentWho uses itWork and contentWhat matters mostTypical systems
A01Shop entrance or receptionStore or reception teamShow opening hours, notices and promotionsReadable content with a simple update procedureDS-01: one locally updated screen
A02Retail store or office networkMarketing or internal communications teamPublish different messages to selected locationsCorrect groups, schedules and accessDS-02: six screens in three groups
A03Shopping centreMarketing and facilities teamsCoordinate campaigns, directories and a feature displaySeparate ownership of promotions and navigationDS-03: eight displays, two kiosks and one LED surface
A04Food court or restaurant counterOutlet operations teamChange prepared menu boards by time of dayCorrect prices and a reviewed scheduleDS-02; live menu data needs a separately agreed connector
A05Transport, healthcare or public waiting areaOperations teamPresent visitor notices or service informationClear messages and a defined response to stale dataDS-01/02 for notices; live queue or operational feeds are additional scope
A06Campus, hotel or event venueCommunications and guest services teamsShow notices, event listings and directionsNamed content owners and legible multilingual layoutsDS-02, or DS-03 where interactive navigation is required

02 Typical configurations

Three starting points, side by side.

Choose the workflow closest to your brief. Compare its scope, interfaces and operating limits before selecting equipment.

AttributeDS-01Single information screenMaintain one screen with reviewed local content.DS-02Managed six-screen networkPublish by time and location to three screen groups.DS-03Retail displays, wayfinding & LEDCoordinate promotions and navigation across eleven playback points.
ScenarioOne indoor information pointSix indoor screens across one siteA retail site with promotions, navigation and a feature surface
Display set1 commercial display6 commercial displays8 commercial displays, 2 touch displays, 1 LED surface
Playback1 player and 1 storage card6 players and 6 storage cards11 players and 11 storage cards
PublishingPrepared media and schedule loaded locallyCMS publishing to 3 groups of 2 screensCMS publishing to 11 endpoints, with separate directory administration
Software allowance1 local authoring installation; no cloud subscription in the base6 CMS endpoint entitlements; service term selected per project11 CMS endpoint entitlements plus an application deployment for 2 kiosks
InteractionNoneNoneTouch search and maps at 2 kiosks
Network lossInstalled local media; next update requires local accessDownloaded media follows its saved schedule; remote changes and monitoring waitDownloaded media plus a separately designed navigation fallback
Main boundaryNo central monitoring or live dataNo touch application, LED surface or guaranteed screen synchronisationNo automatic offline support for arbitrary websites or unverified directory data
Intended outcomeA maintainable information loopControlled publishing by location and timeCoordinated retail information across three display formats

Reference configurations. Example quantities require project selection, compatibility checks and system acceptance tests.

Starting points, not fixed packages: we confirm the room, the platform and the quantities with you, and run the acceptance checks in your space before handover. Not sure which fits? Describe your space →

03 How each option works

Every connection drawn before anything is installed.

Each option with its schematic: the devices and every link between them, the signal paths in plain words, what the system holds, what is agreed separately and how you accept it. Your project gets its own drawings from the site survey.

DS-01

Single information screen

A staff member updates notices and short videos at one indoor entrance, reception or counter.

Reference design · project selection and system tests required

  • One information screen
  • Local storage-card updates
  • Staff check the release on site
DS-01 · system schematic

Signal flow

DS-01 signal flow: An editor prepares a storage card for one player, which sends HDMI video to one display. Staff verify the visible result.
  • USB / KVM
  • Network / data
  • Video / LED data

Typical architecture · not a project drawing

Connection schedule 4 links
  1. L011 staff computer 1 microSD readerUSB file transfer
  2. L021 microSD reader 1 storage cardWrite files
  3. L031 storage card 1 standard playerInsert into player
  4. L041 standard player 1 commercial display1 HDMI video link

Control & power

DS-01 control & power: An editor prepares a storage card for one player, which sends HDMI video to one display. Staff verify the visible result.
  • Control / status
  • Power

Typical architecture · not a project drawing

Connection schedule 3 links
  1. L051 commercial display 1 staff computerStaff visually check release
  2. L06Local power 1 standard playerPower
  3. L07Local power 1 commercial displayPower
Trace routes in the interactive drawing

How it works

Intended result. One screen displays reviewed local content with a documented update and restart procedure.

  1. Local update
    1. Staff computerPrepare content and schedule; write the storage card.
    2. Local playerInsert the reviewed card and start playback.
    3. Information screenStaff visually check the release.

This is a local update workflow. A playback picture is checked by staff; it is not a remote CMS health report.

In the system

One commercial HDMI display, one external player, one local storage card, a mounting set, an HDMI connection and local power. An existing staff computer with a card reader prepares and transfers the presentation. The base workflow uses removable media; local network publishing is an optional alternative.

Commercial displays
1
Media players and local storage
1 player / 1 card
Content publishing software
1 local authoring installation; no cloud subscription
Mounting, cabling and power
1 installation set
Network and service infrastructure
Optional network; local authoring uses the existing staff computer

Example quantities: makes, models and compatibility are confirmed in your BOQ.

Agreed separately

  • Central CMS publishing, remote alerts, live websites, touch interaction and multi-screen operation are outside this configuration.
  • Clock settings and behaviour after an extended power-off period must be checked where timing matters.

How you accept it

Load approved content, read it at the intended position, check the schedule and restart after power loss.

Handover record: Content/version record, display check and local update guide.

These are planned project checks. The reference configuration has not passed physical system acceptance.

Discuss DS-01 with an engineer

Operation

The content owner approves the material before it is loaded. A stored schedule selects the presentation. Staff check the visible result after an update and after a power interruption.

DS-02

Managed six-screen network

An office or store needs different campaigns for three locations, with two screens in each content group.

Reference design · project selection and system tests required

  • Six screens across three locations
  • CMS scheduling and player reports
  • Separate publishing permissions
DS-02 · system schematic

Signal flow

DS-02 signal flow: Editors access a CMS. Six players use the site network to fetch content and return status; each player feeds one display over HDMI.
  • Network / data
  • Video / LED data

Typical architecture · not a project drawing

Connection schedule 5 links
  1. L031 CMS workspace Site firewall + uplinkHTTPS content replies to player requests
  2. L04Site firewall + uplink 1 managed 16-port switchEthernet uplink
  3. L061 managed 16-port switch 6 standard players6 Ethernet access links
  4. L076 local storage cards 6 standard playersOne installed card per player
  5. L086 standard players 6 commercial displays6 HDMI video links

Control & power

DS-02 control & power: Editors access a CMS. Six players use the site network to fetch content and return status; each player feeds one display over HDMI.
  • Control / status
  • Power

Typical architecture · not a project drawing

Connection schedule 6 links
  1. L011 editor workstation 1 CMS workspaceCMS console over HTTPS via site network
  2. L026 CMS endpoint entitlements 1 CMS workspaceOne entitlement per active player
  3. L051 editor workstation 1 managed 16-port switch1 Ethernet access port
  4. L096 standard players 1 CMS workspaceRequests and status via same switch and firewall
  5. L10Local power at each point 6 standard playersPower
  6. L11Local power at each point 6 commercial displaysPower
Trace routes in the interactive drawing

How it works

Intended result. The operations team can publish a campaign to the intended screens, check delivery and recover from a failed update without changing other groups.

  1. Managed publishing
    1. Editor + CMSNamed roles approve content and schedules.
    2. Six playersApproved outbound network access; local saved media.
    3. Three locationsTwo independent screens in each location.

Players request content and report status through the same network. Six active players need six entitlements; service terms and behaviour during an outage must be agreed.

In the system

Six commercial displays, six players, six local storage cards and six CMS endpoint entitlements. Shared infrastructure comprises one managed access switch, the site's firewall and internet connection, an existing editor workstation, and one configured CMS workspace. Each player has its own HDMI output and local power supply.

Commercial displays
6
Media players and local storage
6 players / 6 cards
Content publishing software
6 CMS endpoint entitlements
Mounting, cabling and power
1 installation set
Network and service infrastructure
1 shared deployment

Example quantities: makes, models and compatibility are confirmed in your BOQ.

Agreed separately

  • Three content groups do not guarantee frame-accurate synchronisation.
  • A player screenshot does not prove that the display is powered on or set to the correct input.
  • Touch, live business-data connectors and display telemetry are additional scope.

How you accept it

Publish to one group without altering the other two; deny unauthorised actions; interrupt a download; disconnect and restore WAN.

Handover record: Group/permissions report, schedule evidence, outage and recovery results.

These are planned project checks. The reference configuration has not passed physical system acceptance.

Discuss DS-02 with an engineer

Operation

Editors prepare content; an authorised publisher releases the reviewed version to the chosen group and schedule. The administrator checks player connectivity and download status. The selected CMS must support the agreed group permissions; a formal software approval workflow is specified separately if required.

DS-03

Retail displays, wayfinding & LED

A shopping centre combines eight advertising screens, two visitor navigation kiosks and one LED feature surface.

Reference design · project selection and system tests required

  • Eight screens + two kiosks + LED
  • Campaigns and directory data
  • Wayfinding application is a separate scope
DS-03 · system schematic

Signal flow

DS-03 signal flow: Eight players feed standard displays, two interactive players receive USB touch from kiosks, and one player feeds an LED processor. The directory service supplies data to the kiosk application separately from CMS content publishing.
  • Network / data
  • Video / LED data
  • USB / KVM

Typical architecture · not a project drawing

Connection schedule 14 links
  1. L051 CMS workspace Site firewall + uplinkHTTPS package replies
  2. L061 directory data service Site firewall + uplinkHTTPS data replies
  3. L07Site firewall + uplink 1 managed 24-port switch1 Ethernet uplink
  4. L081 managed 24-port switch 8 standard players8 Ethernet links
  5. L091 managed 24-port switch 2 interactive players2 Ethernet links: packages and directory data
  6. L101 managed 24-port switch 1 LED content player1 Ethernet link
  7. L1111 local storage cards 8 standard players8 cards
  8. L1211 local storage cards 2 interactive players2 cards
  9. L1311 local storage cards 1 LED content player1 card
  10. L158 standard players 8 commercial displays8 HDMI links
  11. L162 interactive players 2 touch displays2 HDMI video links
  12. L172 touch displays 2 interactive players2 USB touch return links
  13. L181 LED content player 1 LED processor1 HDMI video link
  14. L191 LED processor 1 LED surface packageVendor LED data, not CMS Ethernet

Control & status

DS-03 control & status: Eight players feed standard displays, two interactive players receive USB touch from kiosks, and one player feeds an LED processor. The directory service supplies data to the kiosk application separately from CMS content publishing.
  • Control / status

Typical architecture · not a project drawing

Connection schedule 7 links
  1. L012 staff workstations 1 CMS workspaceCMS console / HTTPS via site network
  2. L022 staff workstations 1 directory data serviceDirectory admin / HTTPS via site network
  3. L032 staff workstations 1 managed 24-port switch2 Ethernet access ports
  4. L0411 CMS endpoint entitlements 1 CMS workspaceOne entitlement per active player
  5. L141 navigation application deployment 2 interactive playersSeparate app scope / 2 runtime instances
  6. L201 managed 24-port switch 1 CMS workspaceAll 11 players: requests and status via firewall
  7. L211 managed 24-port switch 1 directory data serviceKiosk data requests via firewall
Trace routes in the interactive drawing

How it works

Intended result. Visitors see current promotions and can use a maintained directory, while staff control publication and know how each part behaves during an outage.

  1. Campaigns and LED
    1. Campaign publishingOne CMS workspace; eleven total endpoint entitlements.
    2. Separate playback devicesEight standard players and one LED player.
    3. Public displaysEight screens; LED processor maps the additional LED surface.
  2. Visitor wayfinding
    1. Directory and applicationVersioned maps and a separately scoped kiosk application.
    2. Two interactive playersReceive directory data and application packages.
    3. Two touch displaysPicture out and USB touch return.

The CMS, directory data and navigation application have separate responsibilities. LED receiver data is not ordinary CMS Ethernet. All eleven players need local power and storage.

In the system

Eight standard players feed eight commercial displays. Two interactive players feed two touch displays over HDMI and receive touch events over separate USB connections. One further player feeds an LED processor over HDMI. The processor drives the LED receiving system. All 11 players have local storage and their own CMS endpoint entitlement. Shared services include the CMS, network, two existing staff workstations and one directory application deployment licensed for both kiosks.

Commercial displays
8
Media players and local storage
11 players / 11 cards; includes 2 interactive players
Content publishing software
11 CMS endpoint entitlements
Touch displays and interactive players
2 touch displays; players counted above
Directory application and data service
1 deployment for 2 kiosk origins
LED display and processor
1 surface / 1 processor; pixel map by designbrowse LED equipment
Mounting, cabling and power
1 installation set
Network and service infrastructure
1 shared deployment

Example quantities: makes, models and compatibility are confirmed in your BOQ.

Agreed separately

  • The navigation application and its hosting are separate from the player and CMS.
  • Its implementation and compatibility require validation with the selected touch controllers and real maps.
  • During a data outage, it must either use an approved local directory snapshot with a visible update date or show a local fallback message.
  • If safe data are unavailable, route guidance is disabled.
  • LED pixel capacity, power and structure are determined after the surface dimensions are known.

How you accept it

Exercise all 11 endpoints, search and update both kiosks, test a directory outage and restart, map the complete LED canvas.

Handover record: Endpoint/licence register, navigation tests, fallback evidence and LED mapping record.

These are planned project checks. The reference configuration has not passed physical system acceptance.

Discuss DS-03 with an engineer

Operation

The marketing publisher owns campaigns; the directory editor maintains tenant names, categories and map positions. The navigation application handles search, language selection and inactivity reset. Directory changes are versioned and checked at both kiosks. LED content is prepared for the agreed canvas and mapping. Campaign screens, navigation kiosks and the LED feed have separate publishing destinations. Each kiosk retains its own starting location for directions. A campaign update must not replace the navigation application; alternating advertising and navigation on a kiosk requires a separately agreed workflow.

04 Engineering

What the design has to get right.

The checks behind every drawing. Rules of thumb are starting points; the project values are confirmed with the people named.

Design parameters
No.ParameterGuidanceRule of thumbConfirmed with
D01Location and operating hoursSelect brightness, orientation and duty rating for each positionRead the agreed sample in actual lighting; check the display datasheetSite team and AV engineer
D02Text and layoutDesign for viewing distance, dwell time and languageReal notices, menus and map labels remain usable at agreed positionsContent owner
D03Media and playerTest the actual codec, frame rate, resolution and HTML workloadApproved content set plays on the selected hardware and software versionSoftware supplier and AV engineer
D04Storage and updatesAllow space for current content, the next release, application data and logsCapacity calculation and interrupted-update testCMS administrator
D05Network capacityBudget content downloads, update windows and telemetry separatelyMeasured delivery time with the site's bandwidth limitsIT team
D06Schedules and clockSet the correct timezone and define conflict, expiry and power-off behaviourOpening, closing, overlap and recovery testsPublisher and IT team
D07Permissions and licencesDistinguish content preparation, release and device administrationPositive and denied-action tests; recorded endpoint and application entitlementsCMS owner
D08Offline behaviourSeparate local media, cached application data and remote websitesWAN, data-service and restart tests for the agreed fallbackOperations team
D09Touch and accessibilityCoordinate reach, approach space, readable controls and interactionTest both kiosks with real maps, mixed-language text and agreed accessibility criteriaFit-out designer and accessibility reviewer
D10LED canvasSelect the processor and receiving system for the complete pixel mapNo cropping or scaling errors on the approved test patternLED engineer
D11Content governanceName the owner; agree language review, permitted use and advertising requirementsApproved templates and a recorded publication processClient and relevant authority
D12Service and recoveryDistinguish player status from visible display operationFault reporting, replacement and restoration exerciseService owner

Common mistakes

And how the design process prevents them.

  1. M01

    Mistake: Every screen receives the same campaign.

    Prevention: Define destinations and test group-specific publishing.

  2. M02

    Mistake: A downloaded video works offline, so the directory is assumed to work too.

    Prevention: Test the application, its data and its fallback separately.

  3. M03

    Mistake: A touch display is connected only by HDMI.

    Prevention: Provide and verify the USB touch return to a compatible player.

  4. M04

    Mistake: A green player status is treated as proof of a working screen.

    Prevention: Verify the panel and input separately; add telemetry only where supported.

  5. M05

    Mistake: A three-group schedule is described as synchronised video.

    Prevention: Specify and test synchronisation separately if the presentation requires it.

  6. M06

    Mistake: Content has no owner after handover.

    Prevention: Assign publication, directory maintenance and licence renewal responsibilities.

How a typical system fits together

Four layers, from the sources to the people operating the system, and the interfaces between them.

  1. L1

    Sources

    Where the content comes from

    • Approved media and schedules
    • Directory application and tenant dataset

    Local files for DS-01; managed library for DS-02/03 DS-03 only; versioned data and maps, with a defined local fallback

  2. L2

    Processing & transport

    How signals are routed and processed

    • External players and local storage
    • Site network and firewall

    One independent HDMI output per endpoint; media formats and application performance verified DS-02/03: wired Ethernet and approved outbound service access; local DC power in the reference designs

  3. L3

    Displays & audio

    What people see and hear

    • Commercial and touch displays
    • LED processor and receiving system

    HDMI video; separate USB touch return on the two DS-03 kiosks DS-03: HDMI input mapped to the selected LED canvas; LED data links are distinct from the CMS network

  4. L4

    Control & operation

    How the system is run every day

    • Publishing and permissions
    • Status and recovery

    DS-01: local staff procedure; DS-02/03: named CMS accounts and tested group access DS-01: visual checks; DS-02/03: player reports plus a defined way to verify the actual display

Connected to the building and its IT

The systems this solution exchanges signals or data with, and why. Each interface is agreed with the system owner.

  • I01

    Site IT

    Ethernet, approved service access, DNS and time services

    Managed publishing and diagnostics in DS-02/03; no inbound internet exposure is assumed

  • I02

    Directory administration

    Versioned export or authenticated HTTPS API

    DS-03 application data; define schema, update cadence, stale-data rule and rollback

  • I03

    Identity and user administration

    Named CMS accounts; optional identity connector

    Group rights must be demonstrated; single sign-on is additional scope

  • I04

    Menu, calendar, queue or business-data source

    Documented HTTPS API or scheduled export

    Optional connector with an owner, credentials and fallback; no universal integration is included

  • I05

    Display operation

    Supported CEC, serial or IP control

    Optional power/input control and telemetry; choose an interface for each display model

  • I06

    Building alerts

    Separately engineered local interface or supported alert service

    Optional override with its own acceptance tests; signage does not replace a life-safety system

  • I07

    Retail sound system

    Separately specified audio feed and zone controls

    Optional integration with hospitality AV; background music is outside DS player counts

  • I08

    Backup and service reporting

    Configuration exports, application packages and selected CMS reports

    Versioned recovery material; report availability and retention depend on the selected software

The references we design to

Equipment documentation, industry guides and project requirements. Applicable editions and acceptance criteria are confirmed for the site.

Equipment documentation and industry guides04

  • WCAG 2.2Project design referenceAgreed accessibility criteria for the navigation interfaceCheck current edition
  • Dubai Universal Design CodeProject design referencePhysical kiosk access and placement; applicability checked with the fit-out designerCheck current edition
  • Dubai Decree No. (6) of 2020Project design referenceAdvertising permissions and template language requirements; applicability confirmed for the placement and contentCheck current edition
  • Manufacturer interface and installation documentationProject design referenceMedia formats, USB touch, LED mapping, mounting, operating environment and powerCheck current edition

05 From brief to handover

Six stages, with what you receive at each.

Start with the people, activities and operating conditions. You approve the design before procurement and accept the system on your own scenarios.

  1. Stage 01

    Scope and architecture

    Map audiences, display points, content types, languages and operating hours. Name the content owners and choose local publishing, a managed network or interactive retail navigation.

    • Display points and audiences
    • Content owners and languages
    • Publishing and navigation scope
  2. Stage 02

    Design and approval

    Issue the display map, readability requirements, signal paths, network and power schedules. Define templates, roles, group destinations, licence scope and fallback behaviour.

    • Display and readability plan
    • Network and power schedule
    • Publishing roles and fallback rules
  3. Stage 03

    Selection and supply

    Confirm displays, players, storage, mounting and software against the agreed content. Validate the touch/application pairing and LED processing where included; record licence terms and supply status.

    • Compatible display and player set
    • Software and licence schedule
    • Checked touch and LED interfaces
  4. Stage 04

    Installation and programming

    Install and label the equipment. Load the local presentation for DS-01; configure CMS groups and schedules for DS-02/03. Deploy and map the navigation and LED content for DS-03.

    • Installed and labelled endpoints
    • Loaded templates and schedules
    • Configured groups and monitoring
  5. Stage 05

    Commissioning and tests

    Publish real content to the intended destinations. Check time changes, permissions, interrupted updates and recovery. Exercise both touch kiosks, stale directory data and LED mapping where included.

    • Destination and schedule tests
    • Publishing permission checks
    • Outage and recovery results
  6. Stage 06

    Handover

    Train editors and administrators. Deliver the display/player register, diagrams, templates, application and configuration backups, licence record, acceptance report and operating procedures.

    • Editor and administrator training
    • Endpoint and licence register
    • Backups and operating guides

Ready to start? Send a plan, a brief or a BOQ — or just describe the space. AV design, programming and commissioning →

Request a project review

06 Questions

What people ask before a digital signage & retail displays project.

Practical answers before the project starts. Anything else, ask an engineer.

Do all three configurations include a cloud CMS?

No. DS-01 uses local authoring and a storage card. DS-02 and DS-03 allow for a managed CMS with six and eleven endpoint entitlements respectively. Cloud or on-premises deployment is selected against IT requirements; a local server is a separate design and cost item.

Who creates the content and maintains the directory?

Your team or agency normally supplies and approves the messages. The project defines templates and publication responsibilities. DS-03 also needs a directory owner for tenant data, maps and route updates. Ongoing content production and application maintenance need an agreed scope.

What continues when the network fails?

Previously downloaded media can follow its saved schedule, subject to a working player, storage and clock. Remote updates and monitoring are unavailable without their network path. Websites, streams and live data need separate fallback handling. DS-03 must demonstrate its local directory snapshot or fallback message, including a restart during the outage.

Why does DS-03 have eleven endpoints?

Eight advertising displays, two touch kiosks and one LED content feed each have an independent player: 8 + 2 + 1 = 11. The LED cabinets do not each need a signage player. CMS entitlements cover all eleven players; navigation software, data hosting and any separate application licences are counted additionally.

Can editors publish only to their own locations?

That is a requirement for the managed configurations. We test both permitted and forbidden actions in the selected CMS, including shared files and device administration. Some platforms need separate workspaces or a different permissions design. An enforced approval workflow is included only when selected and verified.

Can existing screens be reused, and can a standard player drive a touch kiosk?

Existing screens are checked for inputs, operating hours, brightness, orientation and condition. A touch kiosk needs an appropriate player, a compatible USB touch controller and a tested application. HDMI carries the image; it does not return touch events.

Can the screens show Arabic and English?

Templates and navigation can be designed for both languages. We check right-to-left layout, fonts, numerals, mixed text and line breaks using real content. For advertising in Dubai, template language and permit requirements are confirmed with the relevant authority before release.

Are synchronised video, audience analytics and emergency overrides included?

They are separate requirements. The reference designs include local or scheduled playback, with player monitoring in DS-02/03. Frame synchronisation, audience measurement and building-alert interfaces need their own software, hardware and tests. Player logs alone do not prove that a person saw a message.

What helps us reply with substance

  1. Floor plans, screen positions, dimensions, viewing distances and site photographs.
  2. Lighting, sun exposure, indoor/outdoor conditions and operating hours.
  3. Sample videos, notices, menus, maps and required languages.
  4. Content owners, editors, publishers, update frequency and approval rules.
  5. Existing displays, players, CMS, licences and software versions.
  6. Network, internet, security, time-service and power information.
  7. Tenant data, floor maps, API documentation and required offline behaviour for navigation.
  8. Installation windows, accessibility requirements, advertising approvals and the service contact.

Request a project review

Share your signage brief.

Send display locations, sample content and your publishing responsibilities. A floor plan or a short description is enough to start.

  1. 01
    We review your materials

    The system composition, links with adjacent trades and the scope of work.

  2. 02
    We come back with questions

    A preliminary approach to the system and the points that need closing.

  3. 03
    We propose the next step

    The scope of further design and the path to a commercial proposal.

Have a BOQ or tender drawings? Send an RFQ

Digital signage & retail displaysReply from an engineer