Sentinel SiteGuard
Camera monitoring, restricted-area alerts, staff and visitor access, and collection authorizations for company facilities.
Company security managers, control rooms and front-desk teams
Camera events and access decisions with records that can be reviewed.
The reception desk, control room and facilities team need different views of the same site. Sentinel SiteGuard connects company camera monitoring, visitor and staff credentials, explicit building-access permissions and collection-authorisation records in a facility-focused workflow.
Register a visitor and prepare the current badge assignment.
Group cameras by area, review alerts and inspect detection readiness. Configure supported people and vehicle policies for the assigned coverage.
Supported feeds and uploads support configured object detection and operator review. The camera wall supports reviewing several feeds.
The front desk registers permitted visitors, coordinates bookings and assigns or returns visitor badges.
Register floors, doors linked to floors and lifts with served destinations. Grant explicit points to the current card assignment.
The API checks a credential and issues a short-lived decision. The same integration key consumes it once before a trusted adapter calls the mapped vendor driver.
Collection permits link plates, dispatch references and a bounded validity window for supervisor review.
Application screenshots show fictional front-desk records, inactive camera fixtures and isolated access-control test data. No live door or lift was operated.
Register a visitor and prepare the current badge assignment.
Review badge holders, permitted areas, validity and assignment status.
Organise configured camera sources; feeds shown here are inactive demonstration fixtures.
Manage registered access points and explicit permissions for the assigned credential.
Review the API contract and the adapter responsibilities before connecting hardware.
Reception registers the visitor, checks the visit details and issues a named card or assigns an available reusable badge. The record connects the credential to its current holder, permitted areas and validity window.
Returning a reusable badge closes the earlier assignment. The next visitor receives their own permissions, rather than inheriting the previous holder’s route. At the entry point, the guard compares the wearer with the registered holder and follows the organisation’s verification procedure.
Application preview with demonstration data.
An ID-card QR and its signed NFC copy refer to the same current credential and permission record. The administrator registers floors, doors and lifts, links doors to floors and identifies the destinations a lift serves. Grants specify which points the current assignment may use.
Area access alone does not grant a door or lift. A lift decision also needs the requested served floor. The integration checks the credential, receives a short-lived decision and consumes it once before a trusted local adapter calls the mapped controller driver. Manufacturer-specific commissioning is required for physical operation.
Application preview with demonstration data.
The control room organises cameras by area and reviews supported observations and configured alerts. Source context matters: an operator checks the captured image, time and location before deciding which site procedure to follow.
Camera monitoring and physical-access rules serve different purposes and are configured separately. Retain the relevant observation and incident context for supervisor review. Image quality, model performance, network behaviour and the selected camera connection need validation at the actual site.
Application preview with demonstration data.
Configure areas and detection policies, register doors/lifts/floors and manage current-assignment permissions.
Register visitors and manage bookings, card issuance and badge returns within assigned permissions.
Review camera alerts and check signed credentials at registered points.
Use a scoped API key and commissioned vendor driver for mapped controller operations.
A visitor has an approved appointment at reception.
Practical value: An ungranted destination remains blocked.
Requirements: Booking state, card validity, area clearance and point grants must all permit the request.
An employee needs Floor 2 but not the executive floor.
Practical value: Lift permission does not enable every floor.
Requirements: A commissioned driver and correct controller mappings are required.
The front desk reuses a physical visitor badge.
Practical value: The previous visitor’s permissions do not carry over.
Requirements: The desk must complete return and reassignment; readers must request live decisions.
An operator reviews a vehicle at the loading area.
Practical value: The local permit record supports accountable review.
Requirements: ERP, weighbridge and physical load checks require separate arrangements.
These scenarios explain workflows using fictional examples.
Monitoring, visitors and current-assignment management.
Card, booking, area, clearance, point and floor decisions.
MongoDB and protected configured evidence storage.
Single-use decisions and an administrator-mapped vendor driver.
Supported configured camera source or ingestion connection.
Validate image quality, source identity and monitoring rules.
Installation-issued signed text and a compatible reader.
A bare UID or generic card serial is not an authenticated application credential.
Manufacturer API, SDK or supported gateway behind the adapter.
No universal driver or vendor certification is claimed.
Commissioned floor-output/command integration with explicit destination mapping.
Preserve emergency egress and certified safety functions.
Scoped X-API-Key, HTTPS and the OpenAPI contract.
Successful decisions expire in five seconds and require one consumption by the same key.
Review the selected scope, source records and intended audience. Confirm which staff may export or retain the output and protect downloaded files under your organisation’s policy.
Explore information handling and access →Confirm users, workflows, inputs and the outcome your team needs.
Set up accounts, sources, devices and the agreed integration scope.
Exercise normal and failure cases with representative inputs.
Train the responsible staff and agree recovery, maintenance and support.
Yes, with explicit permissions for its current assignment. QR and NFC share those permissions.
No. A manufacturer-supported API, SDK or gateway and commissioning are required.
The built-in flow uses signed QR/NDEF text. Other secure-card protocols require explicit integration.
A trusted adapter must consume the decision and call the configured mapped driver.
No. Physical confirmation needs controller contacts or other authorised telemetry.
The permit register supports supervisor review. ERP, weighbridge and load validation require separate work.
Sentinel SiteGuard is the facility-security product. It is separate from the national identity system, Sentinel Assure workspaces and Sentinel SkyWatch. Collection permits are a review register, not an ERP or weighbridge integration.
Tell us who will use the product, which inputs or devices you need to connect and how you want to deploy it. We can then define a demonstration and a separate product-specific quotation.
Capabilities, practical examples and deployment requirements for this product.
Review the implemented capabilities and their operating conditions.
Explore features →Follow illustrative workflows and the records needed for review.
Explore use cases →Understand supported connections and the work needed to commission them.
Explore integrations →Review access boundaries and operational responsibilities.
Explore security →Plan a pilot, acceptance tests, training and support.
Explore deployment →Read the full proposal and use the editable presentation.
Explore proposal & slides →