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.6
Start anywhere
There are no stages: start with the idea that would help most, whether the team is one person or a thousand.
The smallest useful start is a list of your spaces and what is in them; Level 1 has a 30-day path. A one-person team has no tiers to remove and lets rules do more; a global team has the same records and the same words.
In Keia Atlas
Switch a module; the sidebar follows
- Device catalogue
Models with cited facts, ports and drawings; standards; setup guides
Units in spaces with build sheets; firmware against the standard; known errors matched to the fleet
- Locations
Floor plans, every device a health circle, who is on site
Incidents lit in their space; the change calendar on the floor
- Services
A map per service; levels within or past target
Incidents, changes and vendors on the map; experience measures
- Support
One queue for incidents, requests, problems and changes; hand-offs; standing rules
The incident story on the space drawing; changes written from work
- Projects
Playbooks; a programme that is always current; deploy work that is verified, not ticked: batches by default; by room, by floor or one at a time where the team works that way
The as-built record becomes the operational record; lessons into setup guides
- Vendors
Contracts and end dates; cases; performance from the record
The vendor as a peer in the flow, scoped to the job
- Knowledge
Runbooks, lessons, guides, glossary, with owners and review dates
Fixes captured where work closes
- In Keia Atlas
- Each module is On, Connected (an outside tool shows its data in the same page shape, with a source mark) or Off, and a team can start with any of them. The smallest useful setup is the device catalogue.
- What Keia Atlas owns
- The record of what is in the building and the work on it. It connects to the systems that run each technology, and leaves alone anything that is a whole product of its own (print queues, DNS, video retention, access credentials, HVAC control, real estate and space planning, endpoint management).
Each module, on its own and with the others on
| Module | On its own | With the others on |
|---|---|---|
| Device catalogue | Models with cited facts, ports and drawings; standards; setup guides | Units in spaces with build sheets; firmware against the standard; known errors matched to the fleet |
| Locations | Floor plans, every device a health circle, who is on site | Incidents lit in their space; the change calendar on the floor |
| Services | A map per service; levels within or past target | Incidents, changes and vendors on the map; experience measures |
| Support | One queue for incidents, requests, problems and changes; hand-offs; standing rules | The incident story on the space drawing; changes written from work |
| Projects | Playbooks; a programme that is always current; deploy work that is verified, not ticked: batches by default; by room, by floor or one at a time where the team works that way | The as-built record becomes the operational record; lessons into setup guides |
| Vendors | Contracts and end dates; cases; performance from the record | The vendor as a peer in the flow, scoped to the job |
| Knowledge | Runbooks, lessons, guides, glossary, with owners and review dates | Fixes captured where work closes |
What it maps to
| On screen | Plain meaning | Maps to |
|---|---|---|
| Module: On, Connected, Off; Connector; Source mark | Built in, fed by an outside tool, or not used; the adapter; "from ServiceNow, 09:14" on a figure |
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 Home as Liam: his first screen is built from the places his work uses.
- Open Settings (the gear): it switches modules on, connected or off. Next: each module On, Connected or Off.