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 installationKeia Method· Level 2 · 2.1 · idea 1 of 5
Start from the building
Keep one record of every place and what is in it, and attach all other work to it.
Start from the building
- Instead of
- piecing together what is in a room from memory and vendor consoles.
- You
- keep one record of every space, the devices in it and what they connect to, and attach every job to a space or a device.
- You'll know it's working when
- anyone can say what is in a room, and what has happened to it, without asking.
In Keia Atlas: each office is a floor plan; select a room, then a device, then its port.
In the morning story, this is 07:52: The video bar in 3.09 goes offline, and the team's monitoring tool raises an alert. The record already lists what is in the room, what each device plugs into, and the 9:00 booking. Read the story
In full, with no software
- Instead of
- Knowing a room from memory, a drawing from the fit-out and a console per vendor. Facilities tools hold the floors, IT tools hold the devices, and the join between them lives in someone's head. Network teams run 4 to 10 monitoring tools, and none surveyed has reached one view (EMA, 2026).
- You
- Model the places first: region, office, floor, space (any place technology lives, including a home office), then the devices in each space and what they connect to. The record calls one physical device a unit. Every other record (incident, change, project, contract, knowledge) attaches to a place or a unit. A space type is the standard a kind of space is built to; the gap between the standard and the real space is the work.
- The moves
- Record each space, the units in it and what they connect to
- Attach every job, change and document to its space or unit
- Compare each space with its space type, and list the gaps
- You'll know it's working when
- The share of spaces with a complete record rises; fewer devices turn up on the network that the record does not know; a new space has a usable record soon after handover. Measure all three.
In Keia Atlas
The zoom: region to port
Region: Europe, Middle East and Africa: each office a point; Dublin holds the device.
- Region. Europe, Middle East and Africa: each office a point; Dublin holds the device.
- Office. The Dublin office: the third floor holds the device.
- Floor. The third floor, to scale: 3.09 Whooper Swan holds the device.
- Space. 3.09 Whooper Swan: two displays, the video bar under them, the table.
- Device. The video bar: one unit, with its model, settings and history.
- Port. Its network port, and the cable to the space's switch.
Three ways to move through the record. Zoom goes from region to port and back, each step a real page. Lens switches one floor plan between Network, Support, Projects, Vendors and Knowledge. Trace draws a service from the internet circuit to the device, lit by health. Every object has the same page shape: where it is and what it connects to, what is happening now, discussion, history, then its own detail. The same health circle, with a word beside it, is used everywhere.
Why it works, and its limits
- Why it works
- Nobody else joins the space, the device, the change, the owner and the vendor in one record; today the join lives in someone's head. Facilities tools own floors; IT tools own devices; the room's technology belongs to neither.
- Limits
- Real estate and property services (leases, space planning, moves, cleaning and catering) are another profession's record; Keia exchanges space data with those systems and never owns it. Laptops and phones are out of scope.
What it maps to
| On screen | Plain meaning | Maps to |
|---|---|---|
| Space, Space type | Any place technology lives; the standard it is built to. "Room" stays where people say room | Composite profile |
| Unit, Model, Device type | One physical thing; one product; a kind of device | ITIL asset management |
| Relationship, Service map, Confidence | How things connect; the drawn picture; how sure the record is, from its source and age | CI, CMDB |
Try it in the demo
Opens as Liam, the Dublin technician. Everyone in the demo is made up; nothing you do leaves this browser.
- Open the Dublin office: the floor plan shows every space.
- Select a space on the plan, then open it: its drawing, its devices, its bookings.
- In the space, open the video bar: its unit page lists its ports and its history.