Call us on 01403 783483
You are viewing this site in staging mode. Click in this bar to return to normal site.

How We Work


This document marks the first stage of our ongoing relationship. As soon as the proposed technology infrastructure and budgetary costing are agreed in principle, we will set the wheels in motion.

Naturally, the scope and complexity of a project will dictate the design and delivery process, 

Existing network - 

Wifi / Internet coverage - is there an existing WiFi network? if not, will Airwave be tasked with supplying WiFi infrastructure? Perhaps the most common issue, delaying the successful deployment of guesttoom entertainment tech, is third part WiFi systems. Issues caused include the fundamental weakness of the network, to communication issues between Airwave and third party provider.

Building structure - listed buildings, and even expensive wallpaper can complicate installation!

Room design - template based room design will facilitate both the planning and installation process.

New Build


Naturally, we will look to mitigate the above issues at the various stages of the planning process, ensuring there are no nasty surprises or factors that might delay, or add costs to the deployment process.

but the delivery process will typically run as follows:


[add caveat about AWE/client communication re qualifying information, which would underpin the site survey]



- Are stages 4 and 5, the same visit?

- need to stick it how we organise the installation - maybe in stage 4?  (so, how many rooms, room access etc).,

1. Project initiation

Following the receipt of your purchase order (thank you kindly for this!), your sales manager will initiate the project. An internal 'handover' meeting will be scheduled, involving representatives from the sales, technical and project teams. Here, the scope of your project will be discussed, and relevant resources allocated accordingly - including a dedicated project manager (PM).

The PM will issue a project specific technical document, introduce him/herself to the client and schedule a project handover call, between Airwave and client.


2. Project Handover Call (PHC)

The project handover call is the first opportunity for all project stakeholders to meet. Your PM will lead the call and work through a checklist of tasks, key to which being the alignment of technical and operational contacts, across both the client and Airwave.

Ultimately, the purpose of the PHC, is to fine-tune the project's scope, ensuring all parties are in accordance with the technology implementation process.

Key agenda items will include: technology infrastructure, design items, onsite works & schedule.

We’ll ask lots of questions, and encourage you to do the same. 

The PM will use action points / intelligence from the PHC to produce a preliminary timeline, detailing next steps and a works schedule.

Here - if relevant, the content team will start preparing your GUi and if necessary, liaising with your marketing department.


3. Technical Handover Call (THC)

All relevant intelligence gathered from the PHC will be added to the project's technical pre-requisite documentation, and will underpin a technical handover call between the technical departments of Airwave and client. This focusses predominantly on the hotel's network infrastructure, and necessary configuration required.

The THC offers a chance to exchange queries and plan for / resolve potential deployment challenges, mitigating issues or delays on installation day.

The outcome of the THC will determine the plan of action and agenda for the site meeting.


4. Site Meeting (both techniocal and logistics)

The Project Manager and relevant technical / RF engineers will now attend site, and look to cover off a checklist of tasks. This will typically include:

  • RF reception/cabling infrastructure installation
  • Core equipment and proof of concept installation - this features as per the below, right?
  • Guestroom visits - 
  • Design sign off
  • Full commissioning & handover
  • Sign off on technology pre-configuration

From this point, the PM will consolidate all items and work directly with each stakeholder group to plan the most efficient and effective project deployment to fit your needs. 


5. Proof of concept (POC) and core deployment

The POC deployment is integral to the project’s success.

With the technical pre-requisite sign off, all network design, build and configuration are agreed fully.  This enables our technical team to install the core elements of the system and fully test the planned solution on location.

A small sample of screens and associated auxiliary kit will be installed as per agreed design and testing will be completed.

By signing off on the POC works, we are effectively ready for full deployment and commissioning throughout the property, and this triggers next steps with all hardware being prepared in readiness for install.

Note – any design works will be ongoing and temporary GUI can be deployed in the short-term while the marketing team finalise works with the Airwave studio.



Airwave's installation engineers will follow a pre-determined installation planTheoretically, the actual installation of TVs, whether wall, arm or desk mounted, should be the most straightforward part of the whole process.


The easy bit, the PM will join the installation team for hardware installation and provide introduction the engineers assigned for works at your property.

All works will be completed in accordance with the POC sign off and agreed parameters discussed during the planning process.

Progress onsite will be reported as requested and the PM will update all stakeholders during and on completion of works.

Project documentation, sign-off & training

Ahead of the project’s sign-off, your PM will prepare an installation & technical handover report, this will include the technical topography, hardware & software operation manuals, troubleshooting documention and the terms and conditions of any service level agreements agreed.

comprehensively list all technology installed, including all operation manuals and supporting documentation (troubleshooting etc)

this will include [O&M (supporting documentation / operation manuals) and troubleshooting documentation. Add training etc]