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 · ManufacturerAG-MFR-POLYSimulated

Aigna and HP Poly

In force · no sites shared · no jobs openchecked just now

The scope

Sites

No sites: this engagement covers the manufacturer's products wherever they are, through support cases.

What flows

  • Jobs handed to the provider

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

What is shared, and who owns it

0 records cross this engagement now
RecordsOwned byOver this engagement
Jobs handed to the providerBoth marks: the client owns the state and priority, the provider its own status and referenceBoth marksShared
Offices and spaces in scopeThe client owns them; the provider reads themAignaNot in this engagement
Visit readinessBoth marks: the provider books, the client confirms accessBoth marksNot in this engagement
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 decidesHP PolyNot in this engagement
Floor plans, IP addresses and switch portsRestricted: never shared with a providerAignaNever shared
Crews and rotasThe provider's own: never sharedHP PolyNever shared
Work notesThe provider's own: never sharedHP PolyNever shared
Internal costs and marginThe provider's own: never sharedHP PolyNever 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; HP Poly owns its own status and reference, and both are shown. An as-built HP Poly sends lands in Aigna's record as a reviewed change, captured, not asked for.

Activity

signed, and held in both audit logs
  1. Aigna · Security assessment renewedSigned by Aigna · in both audit logs
  2. Aigna · Engagement signed by both sidesSigned by Aigna · in both audit logs

Revoke

Stops the flow at once: HP Poly 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 HP Poly sends back arrives as a pull request a person reviews.

HP Poly 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 HP Poly

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