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 · How it fits · 4.3
PMI: the PMBOK Guide
PMI's guide to delivering projects, built on principles and performance domains, not fixed steps.
- How Keia relates
- Companion: project records on the same record as the building
- Which version
- Mapped to the Seventh Edition (2021): 12 principles and 8 performance domains. PMI published the Eighth Edition in November 2025; a short note on it follows the table.
How the ideas map
Each Keia idea, the performance domains and principles it serves, and what Keia adds.
| Keia idea | PMBOK Guide (7th edition) domains and principles | What Keia adds |
|---|---|---|
| Start from the building | Domains: Planning, Delivery. Principle: Systems thinking | A project names the spaces and units it changes, so its scope is a list of real rooms and devices. The as-built record becomes the operational record the day after handover |
| Capture, don't ask | Domains: Measurement, Project Work | Status is read from the work: a deploy batch verifies each unit against its build sheet instead of a person ticking a box, and each phase shows baseline against actual |
| Answer first | Domains: Measurement, Stakeholder. Principle: Value | A project opens with three lights (schedule, cost, scope), each with a one-line reason, then the next gate and what is stuck. Nobody collates a status report |
| Own it, hand it on | Domains: Team, Uncertainty. Principles: Stewardship, Leadership | Every task has one named owner. Risks, issues, decisions and dependencies sit in one log. Integrators and vendors work in the same record, with access that ends when the job closes |
| Learn as you go | Domain: Development Approach and Life Cycle. Principles: Tailoring, Adaptability and Resiliency | Each kind of project follows a playbook. Lessons at close become proposals to the playbook and the setup guides, so the next project starts from them |
The Eighth Edition
PMI published the Eighth Edition in November 2025. It keeps the idea of principles and performance domains but changes both: six principles, among them focus on value, embed quality and integrate sustainability, and seven domains (Governance, Scope, Schedule, Finance, Stakeholders, Resources, Risk). It also brings process guidance back. The Keia ideas map the same way: Start from the building to Scope; Capture, don't ask and Answer first to Schedule and Finance; Own it, hand it on to Governance, Resources and Risk.
Use your normal process here
PMBOK covers much that Keia leaves to you.
- The business case, benefits and the decision to fund a project
- Procurement and contract negotiation (Keia records the contract and its end date, not the deal)
- Earned value and detailed cost control
- Schedule modelling: critical path, resource levelling
- Stakeholder engagement and communications planning
- Building and leading the team
Words side by side
Where Keia's words differ from PMBOK's.
| Keia says | PMBOK Guide says |
|---|---|
| Playbook (the phases and steps for one kind of project) | Tailored development approach and life cycle |
| With Anna (who holds the task now) | Assignment; a responsibility assignment matrix sets it in advance |
| Deploy batch (units set up and verified together) | No single term; the work sits in the Project Work and Delivery domains |
| Lesson, proposed to the playbook | Lessons learned |
Sources
Official source. PMI: The Standard for Project Management and the PMBOK Guide
Checked 30 September 2026.
Try it in the demo
Opens as Anna, a delivery engineer. Everyone in the demo is made up; nothing you do leaves this browser.
- Open Projects: delivery work at each office, each following a playbook.
- Open one project: three lights for schedule, cost and scope, each with its reason, then the next gate.