Enrollment and synchronization
Use this workflow for initial enrollment, replacement photos, and personnel updates. At completion, the same personnel ID should identify the correct information in the central record and on the intended recognition device.
Before you begin
- The participant is authorized for enrollment. Verify their name and personnel ID; use IDs to distinguish people with the same name.
- The enrollment terminal can reach the central service and is registered to the correct building.
- The recognition device is connected, and the administrator or technician has confirmed the building's device-group relationship.
- The camera works; if reading an identity card, the compatible reader also works.
Four separate checks
Capture name, personnel ID, and live photo at the terminal
↓
Create or update the central personnel record
↓ Verify building, accommodation, and target devices
Create personnel changes for central push or device pull
↓
Confirm device receipt, then perform a real recognition“Submission finished,” “central record saved,” “device received,” and “recognition passed” are separate checks. Verify each to locate any interruption.
1. Verify the ID and capture a live photo
Open Registration and clear the previous person's information. Look up existing residents by floor and room, or enter identity details with the confirmed personnel ID. When using a card reader, check whether the imported name and ID have replaced previously loaded values.
Ask the person to face the camera and inspect the live photo. Use “Take Photo” if automatic capture has not produced an image. Verify name, ID, sex, and photo before selecting “Bind Face.” The card photo and live photo are separate images; the current submission uses the live photo.
2. Check the central record and accommodation
After processing, query the same ID in the console and check the name and photo. Resident Management can show or change personnel photos; Student Info is used for basic student records.
| Situation | Central behavior | What to do next |
|---|---|---|
| The ID already exists as a student in the school | Update the student's name, sex, personnel type, and photo | Check that existing accommodation and target devices remain correct |
| The ID does not exist as a student in the school | Create a student and add them to the terminal's building without a room | Ask the administrator to verify academic affiliation, room assignment, and the building's devices |
| The terminal says complete but the console has no update | The business response needs investigation | Keep the submission time, ID, and error details for the technician |
A selected room is not automatically assigned
The enrollment room selector is used for lookup. The current school interface creates new people with a building relationship and no room; an existing person's update does not move them. In Apartment → Resident Management, select the building, use room adjustment for a person already listed there, save, and check the resulting room.
3. Check synchronization for the intended device
The technician checks personnel-to-device relationships and whether a change exists for the target device. The system supports two processing patterns:
| Delivery pattern | How it works | Technician checks |
|---|---|---|
| Central push | The synchronization service processes queued changes for devices that support active delivery | Worker running, device reachable, and actual device response |
| Device pull | Generic HTTP devices request pending personnel and report their processing result | Pull requests occur, correct data is returned, and results are sent back |
Each target device is processed separately. One device may finish while another waits or fails. Confirm the ID and photo on the actual test device before moving to recognition.
Bulk changes can queue. Check whether processing continues; when uncertain, preserve queue evidence and device responses instead of repeatedly submitting the same person.
4. Perform a real recognition
Have the person use the intended device, verify its result, then follow recognition and display to check the new event and screen. Repeat this check after replacing a photo.
Where to start when synchronization fails
| Symptom | First check | Responsible role |
|---|---|---|
| Empty room list | Central connectivity, rooms on the selected floor, terminal identifier and building mapping | Administrator for records; technician for configuration |
| Missing name, ID, sex, or photo message | Complete the field and check the live photo preview | Enrollment operator |
| Central person exists but the photo is unchanged | Same ID, successful capture, and successful business response | Operator and technician |
| Central record exists but no change targets the device | Correct building and device-group relationships | Administrator and technician |
| Change exists but the device has no person | Connectivity, protocol, queue processing, device response; result callback for pull devices | Device technician |
| Device has the person but recognition fails | Device photo, capacity or format errors, and actual recognition feedback | Device technician |
| Device recognizes the person but the display has no new event | Event receipt and display path for the active mode | Follow the display workflow |
Verify updates and removals too
After a name or photo change, check updates on related devices. Removing a room assignment, removing a building relationship, and deleting a person are different operations. Check device authorization according to the actual business relationship; disappearance from a room list alone does not confirm deletion on a device.
After removal, confirm the relevant person record or authorization has been processed on each affected device. Continue following up any device that has not completed processing.
Treat the central service and the target device as the authority for synchronization status. A terminal notification does not cover every business failure; after enrollment, verify the central record and the device-side record. When a task fails, identify the cause before retrying.