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 installationEngagement · Managed service on siteFWH-AV-2025-01Made-up clientSimulated
Fenwater Health and Northlight AV
In force · 3 sites shared · 3 jobs open, 1 past targetchecked just now
- 3Sites in scope
- 3Jobs open
- 1Past target
- 94Days left
The scope
Sites
- Boston campus
- Cambridge clinic
- Quincy outpatient centre
What flows
- Offices and spaces in scope
- Jobs handed to the provider
- Visit readiness
- Handovers
Northlight AV sees a record of Fenwater Health's only when it sits inside this scope, and work only when it was handed to Northlight AV. Fenwater Health sets the scope; ask your contact to change it.
Activity
signed, and held in both audit logs- Fenwater Health · Handed FW-INC-2207 to Northlight AV: boardroom display flickersSigned by Fenwater Health · in both audit logs
- Northlight AV · Rooms checked on all three sites before 08:00Signed by Northlight AV · in both audit logs
- Fenwater Health · Handed FW-INC-2201 to Northlight AV: lecture theatre microphonesSigned by Fenwater Health · in both audit logs
- Fenwater Health · Engagement signed by both sidesSigned by Fenwater Health · in both audit logs
Standards
Fenwater Health's standards apply to everything you do for Fenwater Health. You can offer Northlight AV's own as a template: Fenwater Health decides whether to adopt any of it.
How the two Keias connect
Northlight AV runs Keia in database mode: it shares and receives over the API and events, each one signed.
Fenwater Health 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.
A provider's own Keia
This is Northlight AV's side of the engagement
Only Northlight AV's people see their own Keia. Fenwater Health is a made-up client of Northlight AV; Aigna never sees it.