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

Engagement · Integrator for a projectAG-INT-2025-04Simulated

Aigna and Northlight AV

In force · 4 sites and 1 project shared · 3 jobs open, 1 past targetchecked just now

The scope

Sites

  • New York office
  • Chicago office
  • Toronto office
  • Juneau office

Projects

  • PRJ-14 · Juneau office fit-out

What flows

  • Offices and spaces in scope
  • Jobs handed to the provider
  • Visit readiness
  • As-builts
  • Handovers
  • Design proposals

Northlight AV sees a record of Aigna's only when it sits inside this scope, and work only when it was handed to Northlight AV. Aigna sets the scope; ask your contact to change it.

What is shared, and who owns it

10 records cross this engagement now
RecordsOwned byOver this engagement
Offices and spaces in scopeThe client owns them; the provider reads themAignaShared · 4 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 · 1 now
As-builtsThe provider sends; it lands in the client's record as a reviewed changeBoth marksShared · 1 now
HandoversBoth marks: the provider hands over, the client acceptsBoth marksShared
Design proposalsThe provider drafts in its own Keia and proposes it; the client decidesNorthlight AVShared
Floor plans, IP addresses and switch portsRestricted: never shared with a providerAignaNever shared
Crews and rotasThe provider's own: never sharedNorthlight AVNever shared
Work notesThe provider's own: never sharedNorthlight AVNever shared
Internal costs and marginThe provider's own: never sharedNorthlight AVNever 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; Northlight AV owns its own status and reference, and both are shown. An as-built Northlight AV sends lands in Aigna's record as a reviewed change, captured, not asked for.

Activity

signed, and held in both audit logs
  1. Northlight AV · Marked Tuesday's Chicago survey ready: access booked, kit packedSigned by Northlight AV · in both audit logs
  2. Aigna · TASK-14-2-03 now waiting on switch ports: the clock paused for both sidesSigned by Aigna · in both audit logs
  3. Aigna · Handed TASK-14-2-03 to Northlight AV: record serials and MACs, 2.03Signed by Aigna · in both audit logs
  4. Aigna · Handed SURV-0412 to Northlight AV: survey before the 12.09 refitSigned by Aigna · in both audit logs
  5. Aigna · Handed SNAG-14-02 to Northlight AV: reframe the camera in 2.02Signed by Aigna · in both audit logs
  6. Northlight AV · Sent the as-built for 2.05; it landed in Aigna's record as a reviewed change, accepted by MarcusSigned by Northlight AV · in both audit logs
  7. Aigna · Engagement signed by both sides, with the data processing agreementSigned by Aigna · in both audit logs

Standards

Aigna's standards apply to everything you do for Aigna. You can offer Northlight AV's own as a template: Aigna decides whether to adopt any of it.

Simulated

How the two Keias connect

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

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

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

A provider's own Keia

This is Northlight AV's side of the engagement

Only Northlight AV's people see their own Keia. Aigna holds the same engagement under Vendors.

See Aigna's side

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 Aigna: the engagement

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