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

Decision 0008Accepted

Device models from vendor documents, read twice

Accepted 27 Sept 2026 · in force

0008. Device models from vendor documents, read twice

  • Status: Accepted
  • Date: 2026-09-27

Context

Step 3 needs the physical facts of 27 device models: size, weight, power, and every port with its connector, signals, direction and side. These come from vendor datasheets and manuals, which are long, sometimes contradict themselves, and are easy to misread. A wrong port count or PoE class would break every wiring diagram built on it.

Decision

  • Schema first. schemas/ext/device-model.schema.yaml fixes the vocabulary: connector types, signals, directions, faces, PoE standards, and naming rules for port ids. Conventions (HDMI lists video and audio; an HDBaseT port’s direction is the way the picture flows) are written into the schema descriptions.
  • Two independent readings. Two separate AI readers extracted every model from the vendor documents, each value with a citation, without seeing each other’s work. A script compared the readings field by field. Every disagreement was settled against the quoted source text, preferring the document that labels its axes or units explicitly, and raw document text over summaries.
  • Gaps, not guesses. Anything no source states is left out and listed under gaps. A port’s face is optional for this reason, and not-stated is a valid connector.
  • Every model cites its sources, which are Keia source entries in data/sources/. Where a vendor site blocked downloads, a third-party copy of the vendor’s own document is used and marked as such.

Consequences

  • Five models (Netgear, Cisco, Dell, INOGENI, Sound Control Technologies) had only one reading, because a usage limit stopped the second; each was spot-checked against its primary source instead. One spot check (Cisco) caught a web summary that had dropped two ports; the raw datasheet confirmed the full count.
  • Conflicts inside vendor documents are kept visible in each model’s notes rather than hidden.
  • Port positions for drawing are not here; they belong to device looks, a later step.

Sources: Barchard and Pace, Double entry is superior to visual checking.

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 0008 Device models from vendor documents, read twice

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