Part of #566 (Secure Inside hand-over). Venue: cloud-seven.
There is no record of what security equipment is installed at Cloud Seven, or who administers it. Everything is held by Secure Inside.
That blocks two things: no replacement supplier can quote without an equipment list, and if the relationship ends we lose the configuration knowledge with it.
This item is not in the venue doc. It is added because the supplier shortlist depends on it.
Record the security as-built for Cloud Seven, before any supplier change.
CCTV: camera count, models, locations, recorder model and location, retention setting, network segment, who holds the admin credentials, how remote and mobile access is granted today.
Access control: controller model, door count and locations, badge technology, PIN usage, where the user and access-right database lives, who can issue and revoke a badge today.
Intercom: units and locations, which doors they release, integration path into the access control system, remote opening path.
Intrusion alarm: panel model, detector count wired and wireless, zones, which monitoring centre receives the alarms, and under which contract.
Contracts: which of Securitas, Octopus, Help Fire and Irisco is contracted through Secure Inside, and which directly with the venue.
Credentials: for each system, where the administrator credentials live today and what has to happen for them to transfer.
Written into the hydravenues Cloud Seven runbook, and reflected on the venue floor plan where the equipment has a physical location. See #145 on the Cloud Seven floor plan.
#545 adds per-venue access to hydravenues via iamnim, so an external partner can build an as-built without the shared admin token. Not a blocker here, an operator can drive the editor meanwhile.