Seven plan years from the record: what projects have committed, what the refresh policy says is due, and the envelope where one is set.
One afternoon
Deliver it
A new floor, set up in batches and checked by the record: the Dublin fourth floor, 37 devices in 16 spaces, as an integrator fits it out. Keia reads each unit back; a person fixes only the exceptions. The floor and its kit are real sample data; the integrator, the day and the readings are simulated.
Video bars4
Displays10
Touch controllers6
Scheduler panels5
Batch 1 · Video bars4 units · one configuration
Hostname
dub-401-vc01from the naming standard
Room name
Dublin 4.01 Kingfisherfrom the space record
Network
VLAN 30 · 10.20.0.53from the network standard
Time
ntp1.aigna.examplefrom the house values
Shown for 4.01 Kingfisher; each of the 4 gets its own.
Checked by the record0 of 37 devices
Online on its switch port from the switch0 of 37
In device management from Poly Lens0 of 37
Settings match the standard from the unit0 of 37
On its reserved address from the DHCP server0 of 37
4.05 Goldcrest · display not on its reserved address. The one row a person opens.
Handover16:40
37 devices, every port and setting: already the record the Dublin team runs from tomorrow. Nothing is typed twice.
The fourth floor as planned: 16 spaces to equip, 37 devices, no kit on the floor yet.checked just now
Every night
Maintain it
Standing rules run inside their windows, read back what they did and write it down. The record says what is coming before it becomes a fault.
Last night · 22:00 to 06:004 done automatically · 1 not run · 0 unable to complete
22:0000:0002:0004:0006:00
Firmware rule · Wave 1 · 5 video bars, LondonUpdated to the standard firmware and made a test call on each.Done automatically under the Firmware rule (owner: Sofia) ·
Read
Each unit's version, the standard and its Lab result, and the room's bookings
Did
Sent the update, let the unit restart, read the version back and made a test call
Ruled out
Any room booked before the update would end; any version the Lab has not passed
Not checked
Each accessory's own firmware (each is its own run)
Way back
Firmware cannot be put back by software, so a person confirms every run.
Caps
5 units a wave · never in a booked meeting · never in a change freeze · halted after 1 unable to complete
Firmware rule · Wave 2 · 5 units, CopenhagenUpdated and read back; every test call connected.Done automatically under the Firmware rule (owner: Sofia)
Firmware rule · Wave 3 · 4.02 Kingfisher, DublinNot run: the room is booked until 01:00. Tonight instead.Not run under the Firmware rule (owner: Sofia): a condition held
DNS rule · dub-309-vc01, renamed on its build sheetDNS record updated and read back; the old record kept for Roll back.Done automatically under the DNS rule (owner: Nora)
Calendar re-sync rule · 2.02 Heron's booking panelPanel re-synced with the space's calendar; Undo puts the old link back.Done automatically under the Calendar re-sync rule (owner: Sofia)
The rules, their owners, windows, caps and ways back are the ones on record. The night's runs are simulated.
One morning
Fix it
The fault the hero found, as Liam sees it. Five clicks, every one on the record; take each step yourself. Simulated: the room, the unit and the fault are made up.
Incident · P2from Poly Lens, 07:52
Video bar offline3.09 Whooper Swan · third floor
Offline since 07:52. Booked 09:00, 8 people.
Unit
Poly Studio X72 · dub-309-vc01 from the build sheet
Last change
Firmware 4.6.1 · 02:10 today from the change log
Status
Reachable; the codec is not responding read at 08:11
Known error
Codec hang after firmware 4.6.x · used on 14 installs matched from the last change
Done automatically
Restarted · under the restart rule (owner: Nora)
The rule read the unit from the build sheet, sent a restart over its management port, waited 40 s and read the status back. Roll back returns the unit to how it was.
Test
Test call connected · camera and audio fine read at 08:13
What fixed it?
Restart under the restart rule; codec hang after firmware 4.6.x.
Every connector is read first and shows you what would change before it writes. Two import today; the rest come one at a time, and the kit is open.
SpreadsheetCSV, one row per deviceImport today
NetBoxsites, racks, devices, cablesImport today
ServiceNowincidents and changesNext · named in the demo
Microsoft 365room calendars, Teams RoomsNext · named in the demo
Google Workspaceroom calendarsNext
Slacka room reports itselfNext
Poly Lensvideo bars, controllersNext · named in the demo
Logitech Syncbars, cameras, panelsNext · named in the demo
Crestron XiO Cloudroom systemsNext
Q-SYS Reflectaudio and controlNext
UniFiswitches, access points, portsNext · named in the demo
Merakiswitches, access pointsNext
Datadogmonitoring signalsNext
Entra IDpeople and sign-inNext
Oktapeople and sign-inNext
Build your ownin an afternoon: read an export, show the diff, write YAMLThe connector kit →
"Named in the demo" means the simulation stands in for that system's figures; nothing in the demo is connected to anything real. Live, two-way connectors are on the roadmap after the API and export.
For each person
One record, a different first screen for each of you.
Vault references, never passwords, in the YAML; the validator and the CI secret scan both check. Automatic work runs only under a rule a named owner approved, with the least access it needs, and every run has its full trace in the audit log.
Every device that senses people carries a privacy record: what it captures, where that is processed, who may see it. Occupancy is a count, never a person, and a small room shows "fewer than five".
Evidence mapped to ISO/IEC 20000 and 27001, ITIL and PMI vocabulary alongside ours, NIS2 incident timers where they apply. Supported, never claimed: certification is yours to earn.
Apache 2.0 for the code, CC BY-SA 4.0 for the method. Your record is YAML in your own repository, readable without us; export is a copy, and there is no tier that keeps your data.
