Sentinel SiteGuard deployment planning
Agree the infrastructure and pilot scope before committing to production capacity, specialist hardware or integration delivery.
Deployment requirements
- Supported Node.js host, MongoDB and protected evidence storage.
- Trusted HTTPS and the intended browser/reader devices.
- Configured cameras and representative commissioning footage.
- Registered areas, buildings, floors, doors and lift destinations.
- Manufacturer-supported controller interfaces and commissioned drivers for physical operation.
Pilot and implementation
Discovery: confirm the users, scope, source systems and success criteria.
Configuration: provision access, register inputs and prepare the intended workflows.
Pilot: test representative cases, failures and the acceptance criteria.
Handover: train the responsible staff and agree support, recovery and maintenance.
Acceptance criteria
- Area permission alone does not permit door or lift access.
- A door also requires its enabled floor.
- A lift rejects ungranted or unserved floors.
- Expired, revoked, returned and reassigned badges cannot reuse old permissions.
- Wrong-key, stale and repeated decision consumption fails.
- The controller does not operate after a denied or ambiguous response.
- ID-card QR and NFC produce the same current-assignment outcome.
Training and support
- Administrator setup and account/access management for Sentinel SiteGuard.
- Operator training using the product’s own workflow and representative data.
- Integration, backup and recovery handover for the responsible technical staff.
- An agreed support scope, escalation route and change-control process.
Commercial scope
Request a separate Sentinel SiteGuard quote. The agreed scope should list software rights, deployment, users, data sources, hardware interfaces, training and support. Third-party services, hardware, taxes, travel, ongoing infrastructure and optional integration work must be explicitly included or excluded. No price, deployment date or capacity guarantee is implied by this overview.
Frequently asked questions
Can one ID card work at doors and lifts?
Yes, with explicit permissions for its current assignment. QR and NFC share those permissions.
Does every controller work automatically?
No. A manufacturer-supported API, SDK or gateway and commissioning are required.
Can a raw NFC UID open a door?
The built-in flow uses signed QR/NDEF text. Other secure-card protocols require explicit integration.
Does a successful check unlock hardware?
A trusted adapter must consume the decision and call the configured mapped driver.
Does decision history prove attendance?
No. Physical confirmation needs controller contacts or other authorised telemetry.
Are permits an ERP integration?
The permit register supports supervisor review. ERP, weighbridge and load validation require separate work.
A demonstration for your workflow
Discuss Sentinel SiteGuard with your team and agree the relevant scope, input sources, deployment, training and support.