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 3 · part 4
How it fits
The Keia Method is a companion to the frameworks IT people already know, not a rival.
ITIL tells you what service management is; the Keia Method shows how to run workplace technology that way, day to day.
9 frameworks, and how Keia relates to each
| Framework | What it is for | How Keia relates |
|---|---|---|
| 4.1 ITIL | Managing IT products and services, from strategy to support | Implements part of it: the everyday practices, for workplace technology |
| 4.2 ISO/IEC 20000-1 | A service management system an organisation can be certified against | Companion: keeps records an audit can read; certification stays yours |
| 4.3 PMI: the PMBOK Guide | Delivering projects, through principles and performance domains | Companion: project records on the same record as the building |
| 4.4 PRINCE2 | Running a project in managed stages | Companion: phases, gates and lessons on the record |
| 4.5 Agile, DevOps and SRE | Delivering change in small, safe steps and running services by measured reliability | Companion: standing rules and the learning loop borrow their habits |
| 4.6 AVIXA standards | Designing, documenting and verifying audiovisual systems | Companion: the record holds the evidence; the standards say what good is |
| 4.7 ISO 41001 and ISO 55001 | Managing facilities; managing assets over their life | Companion to ISO 55001: for technology assets; ISO 41001 is out of scope |
| 4.8 ISO/IEC 27001 and NIS2 | Managing information security; the EU's cybersecurity law | Companion: keeps evidence for some controls and duties |
| 4.9 COBIT | Governing and managing enterprise IT | Out of scope: Keia sits under your governance, not in place of it |
How to read each page
It is far smaller than any of them: five ideas and one record, for the rooms, devices and networks in a building and the kit in a home office. Each page says what the framework is, which of its practices each Keia idea serves, what it covers that Keia does not, and where the words differ. The names of practices, processes and standards are the frameworks' own; every description is ours and short. For their definitions, read the frameworks themselves.
Trademarks
ITIL® and PRINCE2® are registered trademarks of the PeopleCert group. Project Management Institute, PMI® and PMBOK® are trademarks or registered trademarks of Project Management Institute, Inc. COBIT® is a registered trademark of ISACA. AVIXA® is a trademark or registered trademark of AVIXA, Inc. ISO is a registered trademark of the International Organization for Standardization, and ISO and IEC standards are protected by copyright. None of these bodies endorses Keia, and Keia uses none of their text.
Try it in the demo
- Open Standards: the house rules integrators follow, why, and how each is checked.
- Open one: it names the outside standard each rule rests on, with a link.