An upgrade can assess reliable personnel data, permission software, controllers, locks and cabling for retention instead of assuming full replacement. Equipment that still operates is not automatically suitable. Verify person IDs, permission ownership, control interfaces, one-time release, feedback, network and offline behaviour, fire requirements and emergency egress. Face recognition establishes the current identity; the approved permission and control chain still decides release. A release command does not prove that the person physically passed.
Inventory six layers
- Personnel data and employment status.
- Cards, face or QR credentials.
- Door, time and direction permissions.
- Controller interfaces, communications and offline behaviour.
- Locks, swing gates or flap barriers.
- Verification, approval, release, alarm and physical passage records.
What may be retained
- Stable personnel IDs with a proven exchange path.
- A permission platform that still meets current policy.
- Controllers with adequate interfaces, capacity, safety and maintenance condition.
- Locks or gates that can execute controlled release safely.
- Power, network and cabling suitable for the new equipment.
Three common upgrade patterns
Retain the existing platform and controller while adding a face terminal; retain personnel and passage equipment while replacing the permission and control layer; or operate old and new entrances by zone during a staged migration. Every pattern requires proof of identity synchronisation, permission timing, one-time release, feedback and offline behaviour.
Recommended upgrade sequence
- Inventory people, software, controllers, readers, locks, gates, power, network and interfaces.
- Assign one owner for personnel master data and final permission.
- Associate new face or card credentials with consistent person IDs.
- Design verification, permission, transaction approval, release, feedback and record flow.
- Pilot no-permission, terminated-person, outage, fault and no-passage scenarios at one entrance.
- Confirm fire, emergency and staffed release requirements before staged expansion.
Record verification and passage separately
A face match does not establish door permission. A release command does not establish physical passage. Retain verification, permission, command, device state and available passage evidence separately. If an old device has no feedback, document that limitation rather than inventing a passage event.
Equipment and software
- Face recognition terminal.
- Access or gate controller.
- Standard swing gate, flap barrier or suitable retained lock.
- Personnel, permission, device, passage and exception management.
- Only the data exchange proven necessary for the project.
Confirm before implementation
- Ownership of person IDs, cards, face credentials and employment status.
- Whether old, new or zoned platforms own permission.
- Controller I/O, communications, capacity, offline behaviour and feedback.
- One-time release and emergency modes of locks or gates.
- Fire, egress, network, power, cabling and lane conditions.
Frequently asked questions
Does a relay output guarantee direct compatibility with a face terminal?
No. Signal meaning, permission ownership, release, reset, feedback, faults and safety still require validation.
Can employee cards remain alongside face recognition?
They can be evaluated when both credentials resolve to the same person ID and permission state.
Why might the gate remain closed after a face match?
Permission may be invalid, the control chain or gate may have failed, or a safety condition may not be met.
Must every entrance change at once?
No. Validate one entrance and expand in controlled stages.