Integration should start with a stable person identifier shared across the approved systems. The workflow then joins the verified iris identity, current location-card assignment, shift or entry permission and actual passage under one traceable transaction. The iris terminal verifies the person; the location system owns card and positioning operations; attendance owns shifts or attendance events; and the access controller or gate executes passage. Fields, direction, timing and the final release authority must be confirmed against the real systems and implementation scope.
Separate the four data responsibilities
- Personnel data supplies the stable person ID, valid status and necessary organisation fields.
- The location system owns card identifiers, current assignments and location operations.
- Attendance owns shifts and attendance events; an attendance event is not automatically an entry approval.
- Identity and passage services retain verification, comparison, release and available physical passage evidence.
Compare person and card inside one transaction
Create the passage transaction first, attach the live identity result and the card read at that portal, then query the current valid assignment. Two unrelated success records with similar timestamps do not prove person-card consistency.
Recommended data exchange
- The personnel owner supplies the necessary person identity and valid status.
- The location system supplies the current card assignment; any location-state return remains system-specific.
- Attendance supplies shifts or receives defined events without replacing the entry decision.
- The gate controller accepts one release for the approved transaction and returns only the states it can actually provide.
Assign one admission decision point
One component must evaluate identity, current card assignment, entry permission and other mandatory checks together. Missing, stale or conflicting inputs must enter a defined deny, retry or staffed-review path.
Recommended integration sequence
- Inventory systems, data owners, person identifiers and available interfaces.
- Model valid, mismatched-card, no-permission, offline and staffed-review cases.
- Agree query, delivery and write-back fields, timing, duplicate control and recovery.
- Pilot one portal and verify that every decision can be traced end to end.
Confirm before implementation
- Data ownership, update timing and proven interfaces for each system.
- How a passage transaction ID is created and carried across components.
- The distinction among recognition, gate release, physical passage and final mine-entry state.
- Access, retention and security boundaries for biometric data.
Frequently asked questions
Does an attendance-capable iris terminal automatically integrate with an existing attendance platform?
No. Interfaces, fields, identifiers, direction, failure handling and ownership still require verification.
Can a successful iris check be recorded as completed mine entry?
No. Final status also depends on permission, other mandatory checks, physical passage evidence and the relevant location state.
Why do separate successful card and iris events not prove a match?
They do not establish that the verified person was compared with the current card assignment inside the same passage transaction.