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

Module

Vendors is switched off

The companies that install and repair, and who looks after each. This demo has the Vendors module switched off in Organisation settings.

Organisation settings

Engagement · Maintenance vendorAG-SVC-2026-01Simulated

Aigna and Keystone Service

In force · 10 sites shared · 3 jobs openchecked just now

The scope

Sites

  • Dublin office
  • London office
  • Copenhagen office
  • New York office
  • Chicago office
  • Toronto office
  • Juneau office
  • Singapore office
  • Tokyo office
  • Melbourne office

What flows

  • Offices and spaces in scope
  • Jobs handed to the provider
  • Visit readiness

Keystone Service sees a record of Aigna's only when it sits inside this scope, and work only when it was handed to Keystone Service. Change the scope and the next record follows the new one.

What is shared, and who owns it

14 records cross this engagement now
RecordsOwned byOver this engagement
Offices and spaces in scopeThe client owns them; the provider reads themAignaShared · 10 now
Jobs handed to the providerBoth marks: the client owns the state and priority, the provider its own status and referenceBoth marksShared · 4 now
Visit readinessBoth marks: the provider books, the client confirms accessBoth marksShared
As-builtsThe provider sends; it lands in the client's record as a reviewed changeBoth marksNot in this engagement
HandoversBoth marks: the provider hands over, the client acceptsBoth marksNot in this engagement
Design proposalsThe provider drafts in its own Keia and proposes it; the client decidesKeystone ServiceNot in this engagement
Floor plans, IP addresses and switch portsRestricted: never shared with a providerAignaNever shared
Crews and rotasThe provider's own: never sharedKeystone ServiceNever shared
Work notesThe provider's own: never sharedKeystone ServiceNever shared
Internal costs and marginThe provider's own: never sharedKeystone ServiceNever shared

Shared records carry both marks. Field by field, the owner's value wins, as the connector model sets out: Aigna owns the job's state and priority; Keystone Service owns its own status and reference, and both are shown. An as-built Keystone Service sends lands in Aigna's record as a reviewed change, captured, not asked for.

Activity

signed, and held in both audit logs
  1. Aigna · Handed INC0041215 to Keystone Service: codec stuck after a power cutSigned by Aigna · in both audit logs
  2. Keystone Service · Booked an engineer for tomorrow morning on INC0041214Signed by Keystone Service · in both audit logs
  3. Aigna · Engagement signed by both sides, with the data processing agreementSigned by Aigna · in both audit logs

Revoke

Stops the flow at once: Keystone Service receives nothing new and can send nothing back. Each side keeps its copy of what was shared before, and the revoke is written in both audit logs.

Simulated: nothing is saved

How the two Keias connect

Aigna runs Keia in repo mode: what it shares leaves as a signed export, and what Keystone Service sends back arrives as a pull request a person reviews.

Keystone Service runs Keia in database mode: it shares and receives over the API and events, each one signed.

No shared database: each side keeps its own Keia and its own copy.

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 Engagement with Keystone Service

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