Keia Atlas

Vendor access

This part is for Aigna staff

Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.

Go to your installation

Module

Assets is switched off

Device types, units, models, setup guides, standards, IT stores and cables. This demo has the Assets module switched off in Organisation settings.

Organisation settings

StandardMeeting room AVVersion 1.0

Meeting room AV

Version 1.0, in force since 1 Mar 2026 · 9 rules that must be met

  • 1Space type per room
  • 0.6 sMost echo (RT60)
  • 100%Seats seen and heard
  • 1Way to join a call

The must rules

9 rules every install follows, in the order of this page. 6 more rules are the default with a written exception.

The space type says what goes in a room and the configurations say how each device is set up. This standard covers what sits between them: where things go, how the room is cabled, what it must sound and look like, and how it is handed over.

  1. Build to the space type
  2. Where things go
  3. Cabling and power in the room
  4. Handover

Build to the space type

3 rules
MustHouse choice

Build every room to its space type and build option in Keia Atlas; anything different is a change record before it is installed.

Why
A room built to its space type can be supported by anyone who knows the space type, and its spares are already on the shelf.
How to check
Keia Atlas shows the room matching its space type after commissioning.
Must

Use only devices certified for the room's meeting platform (Google Meet or Microsoft Teams Rooms) in the mode the room uses.

Why
Certified devices get updates tested with the platform; uncertified ones break without warning.
How to check
The model's page in Keia Atlas lists the platform as supported.

Source Google Meet hardware certified devices

MustHouse choice

Configure every device from its configuration in Keia Atlas, in the setup order, and record it in the project's Deploy page.

Why
The same settings everywhere mean a fault in one room is solved once.
How to check
Every device in the room shows Configured in the project.

Where things go

4 rules
MustHouse choice

Mount the camera or video bar directly above or below the main display, centred, with its lens between 900 and 1,300 mm above the floor in a seated room.

Why
People look at the screen, so a camera next to it makes eye contact with the far end.
How to check
Measure the lens height; the camera's view shows every seat with heads in the top third of the frame.
MustHouse choice

Check that every seat is in the camera's field of view and within the microphones' pickup range from the manufacturer's data sheet.

Why
Someone out of view or out of pickup range is out of the meeting.
How to check
Sit in each seat during commissioning; the far end sees and hears you clearly.
ShouldHouse choice

Put the touch controller on the table within reach of the seat nearest the display, with its cable through the table box, not across the table.

Why
The person running the meeting sits there, and a loose cable gets pulled.
How to check
Photo of the table at handover.
ShouldHouse choice

Do not put the camera facing a window, and fit blinds on windows behind the seats.

Why
A bright window behind people turns them into silhouettes.
How to check
Look at the camera image with the blinds open at midday.

How the room must sound and look

3 rules
ShouldHouse choice

Keep the room's reverberation time (RT60) at or below 0.6 seconds, with acoustic panels where it is higher.

Why
An echoey room is hard to hear at the far end however good the microphones are.
How to check
A measurement with a sound level meter or app during commissioning, recorded in the handover pack.
Should

Design ceiling or wall loudspeakers for even sound across the seats, following the AVIXA audio coverage uniformity method.

Why
Everyone should hear the far end at the same level, not loud at one end and faint at the other.
How to check
Measure the level at each seat; the spread is within the design's target.

Source ANSI/AVIXA A102.01

ShouldHouse choice

Light faces evenly from the front, and avoid downlights directly above the seats.

Why
Cameras need light on faces; downlights cast shadows under eyes.
How to check
Look at the camera image with the room's normal lighting.

Cabling and power in the room

3 rules
MustHouse choice

Provide the data and power outlets the space type lists, behind the display and at the table, with every device on its own outlet.

Why
A room built with too few outlets ends up on a desk switch or a power strip under the table.
How to check
The outlet count matches the space type.
MustHouse choice

Label every fixed room lead (HDMI, USB-C, network) at both ends and tie it off in the table box and behind the display.

Why
Leads that are labelled and tied are not borrowed or unplugged.
How to check
Every lead in the room has a label at each end.
Must

Keep passive USB runs within the USB limit (about 5 m for USB 2.0 and less for faster USB); use an active or extended USB link beyond that.

Why
USB beyond its length fails in ways that look like a faulty camera.
How to check
Measure the run; an extender is fitted where needed.

Source USB 2.0 and USB 3.2 specifications

Handover

2 rules
MustHouse choice

Make a test call from the room to another room and to a laptop, share content wired and wireless, and book the room from its panel.

Why
Proves the room works end to end, not just each device on its own.
How to check
The room's verification in Keia Atlas is complete with the test results.
ShouldHouse choice

Put a short printed guide on the table (join, share, call for help) with the room's name and the service desk number.

Why
People who struggle with a room ask for help instead of giving up.
How to check
Guide present at handover.

Sources

Public standards are named and summarised in our own words, never quoted. Most are sold by the bodies that publish them.
Public standardANSI/AVIXA A102.01, Audio Coverage Uniformity in Listener AreasA method for measuring and stating how evenly a sound system covers the listening area, so a design can set a target and prove it was met.AVIXA · checked 29 Sept 2026
Vendor documentGoogle Meet hardware certified devicesThe list of devices certified for Google Meet hardware, which the space types choose from.Logitech · checked 29 Sept 2026
Public standardUSB 2.0 and USB 3.2 specificationsSet the electrical limits that keep passive USB cables short, about 5 m for USB 2.0 and shorter for faster modes.USB Implementers Forum · checked 29 Sept 2026

View as

See Keia Atlas the way someone else does. A demo: nobody signs in.

Viewing asAnna ByrneAV and IT delivery engineer · EMEA

Suggested

Delivery

  • Delivery engineerDesigns and commissions spaces, from survey to handover
  • Project managerRuns projects day to day: dates, suppliers and who does what
  • On-site technicianInstalls and fixes kit in the offices
  • Programme managerPlans the year of projects across every region
  • Engineering managerLeads the delivery engineers
  • Project management leadLeads the project managers
  • On-site services managerLeads the on-site technicians
  • Delivery managerThe whole delivery team, every region

Support and service

  • Service desk analystTakes incidents as they arrive and routes them
  • Network engineerPorts, VLANs and patching
  • Service manager, AVOwns the AV standard and its service
  • Service manager, networkOwns the network standard and its service

The Lab

  • Innovation engineerTests new kit before it ships

Leadership

  • Head of AV and ITThe whole service, every region

Partners

  • Integration vendorSees their own installations only
  • Service vendorRepairs under the service contract

Overview

  • EveryoneEvery role's first screen at once, to see the whole picture

Settings

Appearance
LookStudio
Text size
Default

Report

Tell the team

About Meeting room AV

Goes to Sofia Reyes, Service manager, AV. Reviewed within five working days.