Keia Atlas

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 installation

Keia Method· Level 3 · How it fits · 4.4

PRINCE2

A method for running a project in managed stages, from PeopleCert.

How Keia relates
Companion: phases, gates and lessons on the record
Which version
PRINCE2 7 (2023), now called PRINCE2 Project Management (Version 7): seven principles, seven practices (called themes before version 7) and seven processes, with people at the centre.

How the ideas map

Each Keia idea, the PRINCE2 principles and practices it serves, and what Keia adds.

Keia ideaPRINCE2 principles and practicesWhat Keia adds
Start from the buildingPrinciple: focus on products. Practices: plans, qualityThe products are real spaces and units, each with a build sheet; quality is checked against the space type and the setup guide, unit by unit
Capture, don't askPractice: progressProgress is read from the work: units verified, phases against their baseline
Answer firstPrinciples: manage by stages, manage by exceptionEach phase ends at a gate. A project opens with three lights and what is stuck, so the exception is the first thing anyone reads
Own it, hand it onPrinciple: define roles, responsibilities and relationships. Practices: organizing, risk, issuesOne named owner per task, risk and issue; vendors are peers in the record, scoped to the job
Learn as you goPrinciple: learn from experienceLessons at close become proposals to the playbook, so the next project starts with them

Use your normal process here

  • Business justification and the business case
  • Directing a project: the board's decisions and authorisations
  • Setting tolerances, and exception reports to the board
  • Starting up and initiating a project

Words side by side

Keia saysPRINCE2 says
PhaseStage
GateStage boundary
Hand to (a peer, with the record)Escalate (to the level with authority, when a tolerance would be exceeded)
PlaybookTailoring the method to the project

Sources

Try it in the demo

Opens as Anna, a delivery engineer. Everyone in the demo is made up; nothing you do leaves this browser.

  1. Open Playbooks: the phases each kind of project goes through, in order.
  2. Open one: a gate ends each phase.
Open Playbooks

View as

See Keia Atlas the way someone else does. A demo: nobody signs in.

Viewing asAnna ByrneAV and IT delivery engineer · EMEA

Suggested

Delivery

  • Delivery engineerDesigns and commissions spaces, from survey to handover
  • Project managerRuns projects day to day: dates, suppliers and who does what
  • On-site technicianInstalls and fixes kit in the offices
  • Programme managerPlans the year of projects across every region
  • Engineering managerLeads the delivery engineers
  • Project management leadLeads the project managers
  • On-site services managerLeads the on-site technicians
  • Delivery managerThe whole delivery team, every region

Support and service

  • Service desk analystTakes incidents as they arrive and routes them
  • Network engineerPorts, VLANs and patching
  • Service manager, AVOwns the AV standard and its service
  • Service manager, networkOwns the network standard and its service

The Lab

  • Innovation engineerTests new kit before it ships

Leadership

  • Head of AV and ITThe whole service, every region

Partners

  • Integration vendorSees their own installations only
  • Service vendorRepairs under the service contract

Overview

  • EveryoneEvery role's first screen at once, to see the whole picture

Settings

Appearance
LookStudio
Text size
Default

Report

Tell the team

About PRINCE2 (the Keia Method)

Goes to Sofia Reyes, Service manager, AV. Reviewed within five working days.