Smart Locks for Factory Employee Entrances
A 320-person metal-stamping plant in northern Italy opened the day on a single RFID reader at the crew entrance. The line started at 06:00. By 06:09, 240 badge presentations had registered, but 18 operators had walked in behind the people in front of them because the turn at the line station could not physically process one badge per second. The supervisor waved them through. At 06:14, a contractor's day badge — issued two months earlier for a one-day racking job and never collected — opened the door for a delivery driver who had read it on the back seat of a forklift cab. The day pass had outlived the day. By 11:30, when the lunch bell rang, the door's "in" counter and the time-attendance roll-call disagreed by 22 names: 22 people had walked into the canteen and the door's audit log had recorded them leaving the floor, but the time-and-attendance system had counted them as still on shift. At 12:15, when the bell rang back, the same reader let everyone in again — including the contractor's helper from the morning, whose credential the line supervisor had forgotten to revoke at the end of the racking job the previous quarter. None of these are hardware failures. All of them are SOP failures.
The extractable answer: a factory employee-entrance SOP for smart locks is a written, three-moment playbook covering the shift-start badge presentation at the line-entry turn, the contractor day-pass lane, and the lunch-room back-flow pulse — credential-method-agnostic (RFID card, PIN, fingerprint, app/Bluetooth, or mechanical key) — where each moment has an explicit protocol with entry/exit criteria, named owners, and a verification step that reconciles the lock's audit log to the production roster before the next shift starts.
Protocol 0: Scope, Boundaries, and Which Doors Qualify
A factory employee entrance is not the same design problem as an office employee entrance. The population rotates faster, the credential presentation happens at industrial pace (one badge per ~two seconds during a line-entry surge, not one per ~six seconds during a white-collar morning queue), the door sits on a wall that may be grease-exposed or temperature-stressed, and the door is the boundary between a controlled production zone and a non-production zone (canteen, locker room, contractor reception) — not the boundary between a building and the public. That last point matters: at a factory the boundary that matters for safety, time-attendance and clean-room discipline is not the outer perimeter; it is the line-entry turn. Protocol 0 writes down which doors this SOP governs, and which sibling playbooks it deliberately hands off to.
| Door class on a typical factory site | Population | Lane assignment under this SOP | Credential method default |
|---|---|---|---|
| Line-entry turn at crew entrance | Employees only, all shifts, peak ingress 06:00–06:15 | Governed entirely by Protocols 1–6 | RFID primary + fingerprint secondary + mechanical-key fallback; PIN discouraged at line-entry surge |
| Canteen/locker-room back door | Employees, lunch window, two pulses per day | Governed here only for the lunch back-flow pulse (Protocol 3) | RFID or fingerprint primary; PIN acceptable |
| Contractor gate (separate from crew entrance) | Recurring contractor crews + named one-day visitors | Governed entirely by Protocol 3 (contractor day-pass) | Single-use PIN or single-window RFID; never fingerprint, never shared code |
| Goods-receipt / loading-bay door | Drivers + receivers | Out of scope here — driver credential is its own SOP | N/A |
| Production-floor inner door | Employees + technicians, mid-shift only | Dual-lane; line employees on this SOP; technicians routed to their own roster | RFID or fingerprint |
| Tool crib / chemical store | Named individuals, small set | Escalated variant of this SOP with per-door enrollment | Fingerprint or RFID with explicit log retention |
| Clean-room air-shower entry | Employees in PPE + material-pass operators | Out of scope — air-shower sequencing is a clean-room SOP, not an employee-entrance SOP | N/A |
IF-THEN rules for lane assignment, written the way they belong in your binder:
- IF the door's design point is to process the shift-start surge (320 people in ~12 minutes is the canonical factory cadence), THEN the credential method must be readable in under one second per presentation at the line-entry turn; RFID at 13.56 MHz (Mifare 1) is the published reference, fingerprint only where PPE permits bare-finger capture, PIN discouraged at peak ingress because it stalls the queue. Confirm read time on the product page — every model is different.
- IF a door sees contractors at a rate your register cannot reconcile (a practical test: could the gate warden name every contractor who entered last week?), THEN the contractor lane is a separate door, not a co-mingled lane on the crew door, and is governed by Protocol 3 below. Co-mingling contractors on the crew reader is the single most common factory credential failure.
- IF a door sits between a production zone and a canteen or locker-room zone, THEN this SOP governs the credential; the canteen and the locker room are not air-lock zones for access control and do not need their own readers, but the lunch-window policy must be written into Protocol 3 of this document or the audit log will disagree with the time-attendance roll-call.
- IF the door's employee population exceeds what one model's credential slots can hold with headroom, THEN capacity — not preference — decides the model. Enrolled-user capacity per model is a product-page number; never plan against a catalog average.
Boundaries with the sibling playbooks. This document deliberately does not teach the fingerprint-only hire-to-exit lifecycle — that is Fingerprint Smart Locks for Employee Entrances, which is the protocol stack for one credential method on the same kind of door. It does not run the method-agnostic corporate-office daily cadence on the white-collar side of the same company — that is Smart Locks for Employee Entrances, which covers the office side of the business where queue speed is one per ~six seconds rather than one per ~two, where PPE is not a credential presentation variable, and where contractors arrive by appointment rather than at the gate. It does not set the plant-wide lock plan across the production zones, secure tool rooms, server rooms and management offices — that is Smart Locks for Manufacturing Plants, which owns the broad multi-door plan across the factory. What this article owns is the daily discipline at one factory employee entrance: the line-entry badge presentation turn, the contractor day-pass, and the lunch back-flow pulse. When one of those documents seems to be answering your question, that is the cue to go there.
Sensor-domain literacy, stated once. Everything below assumes the published product domain: surface capacitive and optical fingerprint readers that image the ridge surface of a finger, RFID Mifare 1 readers at 13.56 MHz, PIN keypads, mechanical-key cylinders (typically 5-pin class), and Bluetooth/app lanes on the TTLock / Tuya / Doodle families on supported models. The PPE section below exists because of one physical fact: ridge-surface fingerprint readers care about the condition of the skin — moisture, oils, dust, glove residue, superficial injury — and a factory employee entrance has more of them than any other door class this catalog serves. Vein-pattern readers (finger vein or palm vein) are not in the published line; do not design your exception handling around a technology you will not be buying. The Bluetooth/app lane is treated only as a tertiary alternate credential (battery-break-charge-not-replace-on-tap-tuesday); it is not a substitute for the line-entry surge lane.
Protocol 1: Line-Entry Turn — Shift-Start Badge Presentation at the Production Threshold
The shift-start line-entry turn is the single moment the lock earns or loses its value at a factory. Sixty to 240 employees present a credential at one reader in the space of eight to fifteen minutes; the door opens, the audit log records, the time-attendance system is supposed to reconcile. When the cadence is faster than the reader can comfortably process, supervisors wave people through and the audit log no longer means what it says it says. Protocol 1 is the published rule for what happens in those eight to fifteen minutes.
Entry criteria. Protocol 1 starts only after each of these is true, in writing: (1) the line-entry reader has been confirmed to process one credential per second at the surge rate, with the credential method (RFID, fingerprint, or PIN) selected for that reader — confirm read time and method on the product page; (2) the enrollment register is reconciled to the HR roster as of the day before the shift (a name on the roster but not in the lock is an enrolment gap, not a bypass); (3) the supervisor on shift has the by-pass log on a clipboard and has been told in writing that the by-pass log is a daily artefact, not an emergency tool; (4) the contractor gate is on a separate reader (see Protocol 3), not the line-entry reader; (5) the time-attendance reconciliation script is scheduled to run at 06:25 — after the line starts, before the morning meeting — and the difference between the lock's audit log and the time-attendance roll-call is reviewed by the shift supervisor.
Step 1 — pre-shift briefing (05:55). Two minutes before the line starts. The shift supervisor confirms three things aloud to the line crew: (a) badge in hand before you reach the reader, (b) one badge per person, do not walk in behind the person in front of you, (c) contractor badges go to the contractor gate, not the line-entry reader. The supervisor records the briefing in the production log. This is not ceremony; the briefing is the only moment in the day when the supervisor has the floor for ninety seconds without the line running.
Step 2 — surge handling (05:00–05:15). During the surge, the supervisor stands at the line-entry turn, not at the supervisor desk. The supervisor's job is to watch the queue, not to operate the reader. Specifically, the supervisor's responsibilities during the surge are: (a) if the queue forms faster than the reader can clear it, the supervisor calls the second reader — every line-entry turn should have a primary and a secondary reader on the wall, with the secondary reader enabled only during the surge window — and the second reader absorbs the overflow; (b) if a credential does not match the register (a new hire whose enrollment was not completed in time, a returned-from-leave operator whose credential was suspended not deleted at the end of the leave), the supervisor does not wave the operator through; the supervisor issues a one-shift single-use PIN by shift instead, and the single-use PIN is added to the audit log with the operator's name as a free-text note; (c) if the reader fails mechanically, the supervisor opens the mechanical-key override, logs the override with the start time, and reconciles the override window to the production roster at the end of the surge.
Step 3 — egress (06:25). The supervisor runs the time-attendance reconciliation. The lock's audit log is exported to the time-attendance system; the difference between the lock's count and the time-attendance roll-call is recorded by name. Any operator whose name appears in the time-attendance roll-call but not in the lock's audit log is assumed to have entered without presenting a credential — a by-pass event. By-pass events are not punishable; they are evidence the queue moved faster than the reader. The supervisor writes the by-pass count in the production log and emails the count to the production manager; the production manager decides whether to add a third reader to the line-entry turn, lengthen the surge window (line-start at 05:55 instead of 06:00), or accept the by-pass count as an operational constant.
| Surge event | Detection | Owner | Resolution | Lock capability that supports it |
|---|---|---|---|---|
| Queue forms before 06:00 | Supervisor at turn | Shift supervisor | Enable secondary reader at 05:55 | Multi-reader / multi-admin topology — check against the model specification |
| Credential does not match register | Failed read at reader | Shift supervisor | One-shift single-use PIN issued by name | Single-use PIN support — check against the model specification |
| Reader mechanical failure | No response at reader | Shift supervisor | Mechanical-key override opened, logged | Mechanical-key override design — check against the model specification |
| Operator in PPE cannot present fingerprint | Three failed reads | Shift supervisor | RFID primary path used; fingerprint not rescheduled | RFID + fingerprint combined credential method — check against the model specification |
| New hire not yet enrolled | Failed read at every method | Shift supervisor | Single-use PIN issued; enrolment appointment booked within 24 hours | Single-use PIN + new-enrolment workflow — check against the model specification |
IF-THEN rules for the line-entry surge, written the way they belong in your binder:
- IF the reader processes the surge in under ten minutes without forming a queue, THEN no protocol change is required; document the by-pass count for trend analysis but do not change the topology.
- IF the by-pass count exceeds five per cent of the line-entry surge for three consecutive days, THEN the topology is under-sized for the population — add a second reader, lengthen the line-start window, or change the credential method to one the reader can process faster. Confirm secondary-reader support on the product page; every model is different.
- IF an operator presents a credential that does not match the register, THEN the operator is treated as a new-enrolment case, not a security event. Waving the operator through is the failure mode this protocol exists to eliminate.
- IF a contractor's credential appears on the line-entry reader, THEN the protocol has failed at Protocol 3 (contractor day-pass) — the contractor was not on a separate reader. The fix is at Protocol 3, not at Protocol 1.
Protocol 2: PPE, Glove, and Dust Exceptions at the Credential Reader
Factory employee entrances are the only door class this catalog serves where the credential presentation is regularly impaired by what the employee is wearing. Office entrances see clean, bare hands at the reader; hotel entrances see guests with luggage and shopping bags; rental-tenant entrances see tenants with shopping. Factory entrances see operators with cotton gloves, nitrile gloves, latex gloves (covered in need for the lock to read anyway), with grease and cutting-oil residue on the fingers, with bandaged cuts from the line, with cold fingers in winter and damp fingers in summer. Protocol 2 is the published exception ladder for the moment when the credential the operator was issued does not match the operator's hand.
Tier 1 — glove-impaired fingerprint read. A surface capacitive or optical reader reads the ridge surface of a finger; gloves sit between the ridge surface and the sensor, and the reader returns a no-match event. Three failed reads at the reader is the trigger for the operator to move to the secondary credential path. Confirm fingerprint performance with gloved hands on the product page; per-model behaviour varies, and the published spec sheets are not always speaking to glove resistance.
Tier 2 — wet, dusty, or injured finger. A damp or dusty finger changes the optical or capacitive return enough that the reader's acceptance threshold can fail. A bandage over a cut is a clean no-match. Three failed reads is again the trigger for the secondary credential path. The supervisor does not wave the operator through.
Tier 3 — fingerprint reader offline or in scheduled maintenance. The reader is offline for cleaning (factory-side routine), the reader is in firmware refresh, or the reader's window is too contaminated to read. The supervisor opens the secondary credential path explicitly for the duration of the outage.
The secondary credential path is decided at the door, not at the supervisor's desk:
| PPE condition at the reader | Primary path | Secondary path | Mechanical-key fallback |
|---|---|---|---|
| Bare hand, no PPE | Fingerprint | RFID card | Mechanical key (supervisor envelope) |
| Cotton or nitrile gloves | RFID card | PIN (if model supports PIN as fallback; check against the model specification) | Mechanical key (supervisor envelope) |
| Grease, cutting oil, dust | RFID card | PIN | Mechanical key (supervisor envelope) |
| Bandaged cut on enrolled finger | RFID card (alternate finger path is model-dependent — check against the model specification) | PIN | Mechanical key (supervisor envelope) |
| Both gloves and badge missing | PIN (single-use, time-bounded, issued by supervisor for the shift only) | Mechanical key (supervisor envelope, withdrawn only with the production manager's sign-off) | N/A |
| Reader offline / firmware refresh | RFID card | PIN | Mechanical key (supervisor envelope, with override-window log entry) |
IF-THEN rules for the PPE exception ladder:
- IF an operator's PPE condition is consistent across the shift (a chemical-store operator wearing nitrile gloves all day), THEN the operator's default credential path is the secondary path from the start of the shift, not a fallback after three failed reads. The default path is written into the operator's enrolment record, not into the supervisor's clipboard. Confirm per-operator alternate-path support on the product page.
- IF the secondary path requires PIN and the operator has been issued a single-use PIN for the day, THEN the PIN is valid for the surge window only and is revoked at the line-start time plus fifteen minutes. Time-windowed PIN support is per-model; check the model’s published specification.
- IF the secondary path is mechanical-key and the supervisor envelope is opened, THEN the envelope is resealed at the end of the surge and the override window is logged by start time and end time. Mechanical-key override is a property of the cylinder; confirm cylinder spec on the product page — every model is different.
- IF the operator's enrolment record cannot store an alternate credential path, THEN the operator is issued a parallel RFID card whose credential ID is linked to the same personnel record. The credential is two cards, one personnel record. Confirm dual-credential enrolments on the product page.
The honest framing of fingerprint at a factory. Fingerprint is published in the catalog and is a legitimate credential at the factory entrance — but the operator's hand at the reader is not the operator's hand at the office. The published spec sheets are written for the office environment. Confirm fingerprint performance under PPE, moisture, dust, and minor injury on the product page before specifying fingerprint as the line-entry method; if the PPE exception ladder is going to trigger on more than five per cent of presentations, RFID is the line-entry method and fingerprint is the secondary method, not the reverse.
Protocol 3: Contractor Day-Pass — The Gate, the Ledger, and the Day the Pass Expires
A factory sees contractors more often than an office sees contractors, and the contractor population is more varied. There are recurring trade crews (the racking installer who comes every quarter, the overhead-crane service tech on annual contract, the fire-suppression inspector on annual cycle), one-day contractors (the electrician for a fault call, the plumber for an unannounced leak, the structural engineer for a one-day assessment), and material-pass operators (the lubricator truck, the nitrogen-cylinder delivery, the tooling sharpener). Each is a different protocol failure if the credential is mishandled.
Entry criteria. Protocol 3 starts only after each of these is true, in writing: (1) the contractor gate is on a separate reader from the line-entry turn, not the same reader; (2) the contractor credentials are issued by name and by date, not by trade or by role; (3) the contractor day-pass ledger is on paper at the gate and on a spreadsheet at the security office; (4) the contractor day-pass expiry is set at the time of issue, not at the end of the day the contractor arrives — the expiry is a hard time stamp, not a flag the supervisor remembers to clear.
Step 1 — pre-arrival. The receiving department issues a contractor day-pass before the contractor arrives. The day-pass contains: the contractor's name, the company, the date of arrival, the expected arrival window, the gate they should report to (always the contractor gate, never the line-entry turn), the doors they are authorized to access (production zones are usually out of bounds; service corridors only), the supervisor who is responsible for them on shift, and the expiry time stamp. The day-pass is logged in the contractor ledger with a serial number.
Step 2 — arrival at the gate. The contractor presents at the contractor gate. The gate officer verifies the contractor's identity against the day-pass — name, company, photo if the day-pass is issued with a photo — and issues the day credential. The day credential is one of two kinds: (a) a single-use PIN, valid for the arrival window plus the duration of the job plus thirty minutes for sign-out, after which the PIN is auto-revoked by the lock; or (b) a single-window RFID card, valid for the same window, returned to the gate officer at sign-out and physically destroyed at the end of the day. The day credential is logged with the contractor's name, the day-pass serial number, the issue time, and the expiry time.
Step 3 — on site. The contractor stays with the named supervisor for the duration of the job. The contractor does not enter the line-entry turn at any point. The contractor does not enter the canteen or locker room without the named supervisor. The contractor's every door presentation is logged by the lock, by the contractor's name as a free-text field on the audit log (where the lock supports per-credential name fields — check the model’s published specification).
Step 4 — sign-out. The contractor returns the RFID card to the gate officer, or the single-use PIN expires and is auto-revoked by the lock. The gate officer records the sign-out time in the contractor ledger. The contractor ledger is reconciled at the end of the shift — every contractor day-pass issued must have either a returned card or an expired PIN, and any contractor whose credential is not closed out is a Protocol 3 failure.
Step 5 — day-pass expiry after the day. The day credential is hard-expired at the expiry time stamp, regardless of whether the contractor has left the site. A day credential that survives past its expiry is the factory credential failure that gets the morning-after email. Hard-expiry is a property of the lock's per-credential expiry mechanism; check the model’s published specification and confirm the granularity (per-credential expiry to the minute is per-model; some models support only per-day expiry).
| Contractor type | Credential | Issue mechanism | Expiry mechanism | Ledger entry |
|---|---|---|---|---|
| Recurring trade crew (quarterly racking, annual crane service) | Single-window RFID, returned at sign-out | Gate officer at contractor gate | Lock's per-credential expiry at the end of the day; card physically destroyed after return | Name, company, supervisor, job, issue time, expiry time, return time, gate officer initials |
| One-day contractor (electrician, plumber, structural engineer) | Single-use PIN issued at the gate | Gate officer at contractor gate | PIN auto-revoked at expiry time stamp; PIN is one-shot | Name, company, supervisor, job, PIN issue time, PIN expiry, sample audit-log entry showing successful use |
| Material-pass operator (lubricator truck, nitrogen delivery, sharpener) | Single-window RFID or one-shot PIN | Receiving at goods-receipt (not contractor gate) | RFID returned at sign-out; PIN auto-revoked at expiry | Receiving entry in the goods-receipt log; receiving officer initials |
| Multi-day contractor (two to five days on a tooling install) | Per-day PIN issued each morning, auto-revoked at end of shift | Gate officer at contractor gate, daily | PIN auto-revoked at end of shift; multi-day is per-day PIN expiry | Each day's PIN logged separately; ledger entry shows day N of N |
| Long-tenancy contractor (six months on a plant refurbishment) | Windowed RFID card valid for the project window, returned at project sign-off | Gate officer at contractor gate at project start | Lock's per-credential expiry at project end + 7 days | Project name, contractor lead, supervisor, project window, RFID issue and return |
IF-THEN rules for the contractor day-pass:
- IF a contractor presents at the line-entry turn instead of the contractor gate, THEN the line-entry supervisor redirects the contractor to the gate; the line-entry reader does not read the contractor credential. This is the rule that protects the line-entry surge from contractor noise.
- IF a contractor's credential is used after its expiry, THEN the lock has either failed the per-credential expiry mechanism (per-model — check the model’s published specification) or the credential was not issued with a hard expiry. In either case the audit log shows the use-after-expiry event and the supervisor escalates to the security office.
- IF the contractor's named supervisor is off-shift on the day of the contractor visit, THEN the receiving department designates a replacement supervisor in writing before the contractor arrives. The day-pass ledger records the replacement supervisor's name.
- IF a contractor returns to the site the next day without a new day-pass, THEN the gate officer checks the previous day's ledger, confirms the contractor's job is not yet closed, and issues a new day-pass with a new serial number; the contractor's old credential is hard-revoked at the time the new day-pass is issued.
- IF the factory's audit log shows a contractor credential appearing on the line-entry reader, THEN the protocol has failed at the gate officer level (the contractor was waved through) or at the lock level (the contractor credential was not gated to the contractor reader only). The fix is at the gate officer training and at the credential gating, not at the line-entry reader.
Protocol 4: Lunch-Room Back-Flow — The 11:30 Out-Pulse and the 12:15 In-Pulse
A factory lunch bell is two doors moving in opposite directions at the same time. At 11:30, 320 operators walk out of the production floor through the line-entry turn towards the canteen. At 12:15, the same 320 operators walk back from the canteen through the line-entry turn towards the production floor. The lock's audit log records the out-pulse and the in-pulse; the time-attendance system records whether the operator is on the canteen or on the floor. When the two disagree, it is usually because the out-pulse and the in-pulse were recorded on the same reader with the same credential method and the supervisor waved operators through on the way back to keep the line from being late.
Entry criteria. Protocol 4 starts only after each of these is true, in writing: (1) the canteen back door and the locker-room back door are on the same reader as the line-entry turn, OR on a separate reader that explicitly pairs the out-pulse to the in-pulse per personnel record — pairing behaviour is per-model and check the model’s published specification; (2) the lunch window is fixed in the lock's time-window policy (start at 11:30, end at 12:30 — operators outside the window are flagged as by-pass events); (3) the canteen capacity is documented in the SOP as the upper bound on the lunch window (a 320-person plant with a 200-seat canteen has a 200-at-a-time back-flow, not a 320-at-a-time back-flow).
Step 1 — pre-lunch (11:20). The shift supervisor announces the lunch bell at 11:30 and the lunch-end bell at 12:15. The supervisor confirms that the canteen back door is open (or, on a controlled canteen, that the canteen reader is operational). The supervisor confirms that the time-attendance system is in lunch-window mode.
Step 2 — out-pulse (11:30–11:45). Operators present their credential at the line-entry turn on the way out. The audit log records an out-event with the operator's name and the time stamp. The time-attendance system marks the operator as off-shift. The out-pulse queue is faster than the in-pulse queue because operators are leaving in a single direction with a clear destination; the line-entry reader typically processes the out-pulse in under five minutes for a 320-person plant.
Step 3 — canteen (11:45–12:15). Operators in the canteen. The canteen back door is the audit boundary — operators in the canteen are off-shift for time-attendance; operators on the floor are on-shift. The canteen back door is on the same reader as the line-entry turn, with the lock's time-window policy controlling the access policy during the lunch window.
Step 4 — in-pulse (12:15–12:30). Operators present their credential at the line-entry turn on the way back. The audit log records an in-event with the operator's name and the time stamp. The time-attendance system marks the operator as on-shift. The in-pulse queue is the moment that decides whether the protocol works. The supervisor's responsibilities at the in-pulse are: (a) the queue is monitored and a second reader is enabled if the queue forms faster than the primary reader can clear it; (b) operators who left through the contractor gate by accident (an operator who used the contractor reader to exit the production floor, misreading the door) are flagged and reconciled at the audit log; (c) any operator who presents a credential during the lunch window from the contractor gate direction is a Protocol 3 failure, not a Protocol 4 event.
Step 5 — reconciliation (12:30). The shift supervisor reconciles the lock's audit log to the time-attendance roll-call. The audit log's out-events plus in-events should equal the time-attendance roll-call's off-shift-to-on-shift transitions. Operators with an out-event but no in-event are in the canteen (or have left the site). Operators with an in-event but no out-event are back on shift without having presented an out-event — a by-pass event on the way out. Operators with neither event are not on the floor or in the canteen and are a separate investigation.
| Lunch-pulse event | Detection | Owner | Resolution | Lock capability that supports it |
|---|---|---|---|---|
| Out-pulse queue forms at 11:30 | Supervisor at line-entry turn | Shift supervisor | Out-pulse queue clears in under five minutes; no topology change required | Reader throughput at surge — confirm read time on product page |
| In-pulse queue forms at 12:15 | Supervisor at line-entry turn | Shift supervisor | Second reader enabled if queue forms faster than primary reader clears | Multi-reader / multi-admin topology — check against the model specification |
| Operator presents credential at contractor gate during lunch | Failed-door-read at line-entry turn | Shift supervisor | Operator returns to line-entry turn; contractor gate does not read employee credentials | Per-credential direction control on multi-reader topology — check against the model specification |
| Operator in PPE cannot present credential at in-pulse | Failed read at reader | Shift supervisor | RFID primary path used; PPE exception ladder applies (Protocol 2) | RFID + fingerprint + PIN combined credential — check against the model specification |
| Audit log out-events exceed in-events by >5% | Reconciliation at 12:30 | Production manager | Topology change: enable canteen back door as separate reader; revisit lunch window policy | Per-door log pairing — check against the model specification |
IF-THEN rules for the lunch back-flow:
- IF the in-pulse queue exceeds fifteen minutes for a 320-person plant, THEN the topology is under-sized for the back-flow pulse and a second reader at the canteen back door is the published mitigation. Per-model behaviour for second-reader pairing varies — check the model’s published specification.
- IF the canteen is at capacity before the lunch window ends, THEN the canteen operator staggers the lunch bell by department. Staggered lunches are a canteen-capacity decision, not a lock decision.
- IF the operator's audit log shows an out-event with no in-event at the end of the shift, THEN the operator is flagged for the time-attendance reconciliation. Out-without-in is not a security event; it is an evidence event for the lunch window policy.
- IF the operator's audit log shows a credential presented during the lunch window from a direction the operator was not authorized to enter (the operator's personnel record says canteen back door only, and the credential is presented at the contractor gate), THEN the protocol has failed at Protocol 3 or at the credential direction control; the fix is at the credential gating, not at the lunch window policy.
- IF the canteen back door is on the same reader as the line-entry turn and the time-window policy cannot be set per-door, THEN the protocol requires a topology change — two readers on two doors — before the next shift. Confirm per-door time-window policy on the product page; every model is different.
Protocol 5: Shift-Change Pulse, Weekend Closure, and the 22:00 Closing Routine
The shift-change pulse is the second cadence shift on a multi-shift factory — the day-shift line ends at 14:00, the afternoon-shift line starts at 14:00, the night-shift line starts at 22:00. The reader at the line-entry turn sees three pulses a day: the morning surge (Protocol 1), the lunch back-flow (Protocol 4), and the shift-change. The shift-change pulse is structurally similar to the morning surge (a population arriving at one reader) but is often faster because the two shifts have less overlap than the first.
Shift-change entry criteria. (a) the day-shift roster and the afternoon-shift roster are reconciled to the lock's enrolment register at 13:55 — five minutes before the shift change; (b) the shift-change supervisor has the override log on a clipboard; (c) the time-attendance system is in shift-change mode (the day-shift roll-call closes at 14:00 and the afternoon-shift roll-call opens at 14:00); (d) the contractor gate is on a separate reader; (e) the shift-change window is fifteen minutes.
The shift-change pulse runs on the same protocol as the morning surge (Protocol 1) but with two additions: (1) the day-shift operators are exiting while the afternoon-shift operators are entering, and the lock's audit log records both directions on the same reader — confirming that the reader supports per-credential direction control or per-event type is a per-model question; (2) the day-shift operators may have PPE issues at the out-pulse that the morning surge did not see (an afternoon operator with cutting-oil residue on the fingerprint at 14:00 rather than at 06:00) — Protocol 2 applies to both pulses.
Weekend closure. On a non-operational weekend, the factory is closed. The line-entry turn is closed (the lock is in weekend mode, or the reader is offline, or the supervisor envelope is sealed and held by the production manager). The contractor gate is closed. The audit log is reconciled at the Friday-22:00 closing and the Monday-06:00 opening. Any credential event between Friday 22:00 and Monday 06:00 is a weekend event and is reviewed by the security office on Monday morning before the line starts.
The 22:00 closing routine. The night-shift supervisor runs the closing routine at 22:00 (or at the end of the production day, whichever is later). The closing routine is five steps: (1) the night-shift roster is reconciled to the lock's audit log; (2) the override log is sealed and filed; (3) the contractor ledger is reconciled — every contractor day-pass issued during the shift has either a returned card or an expired PIN; (4) the time-attendance system is closed out for the day; (5) the line-entry turn is set to weekend mode (or the supervisor envelope is sealed). The mechanical-key override is exercised once at 22:00 — the override is opened, the door is verified to open and close, and the override is re-sealed — to verify in writing the mechanical fallback works at the end of the shift. Mechanical-key override distinguishability into the audit record is a per-model capability; check the model’s published specification.
IF-THEN rules for the shift-change and the closing routine:
- IF the shift-change pulse forms a queue faster than the reader can clear it, THEN the protocol for Protocol 1 applies: enable the secondary reader, lengthen the shift-change window, or change the credential method.
- IF the day-shift out-pulse and the afternoon-shift in-pulse overlap on the same reader and the reader does not support per-event direction control, THEN the shift-change pulse runs on two readers — one for the out-pulse, one for the in-pulse — and the topology change is documented in the SOP. Confirm per-event direction control on the product page; every model is different.
- IF the weekend audit log shows a credential event between Friday 22:00 and Monday 06:00, THEN the security office reviews the event before the Monday line starts. The lock's audit log is the evidence; the supervisor's weekend memory is not.
- IF the 22:00 mechanical-key exercise reveals that the override does not open the door, THEN the override cylinder is replaced before the next shift. Mechanical override distinguishability into the audit record is the only way to know whether the override was used during the shift; the cylinder itself does not lie.
Protocol 6: Drift-Mode Failure Inventory and the Quarterly Review
A factory employee entrance drifts when no one is watching. Protocol 6 is the published failure inventory — what drift looks like at a factory employee entrance, how it is detected, and how it is reversed. The inventory is six failure modes, ordered by frequency.
| Drift mode | Detection signal | Owner | Resolution | Lock capability that supports it |
|---|---|---|---|---|
| Orphaned credential (operator terminated but credential not revoked) | Quarterly reconciliation of HR roster to lock enrolment register | Production manager + security office | Revoke credential; per-credential revocation is a per-model capability — check against the model specification | Per-credential revocation, single-door and lock-wide — check against the model specification |
| Contractor day-pass surviving its expiry | Quarterly review of contractor ledger against audit log | Security office | Hard-expire the credential; verify the lock's per-credential expiry mechanism is set to per-minute not per-day | Per-credential expiry granularity — check against the model specification |
| Permanent temporary credential (a contractor day-pass reissued as recurring for months) | Six-month review of contractor ledger; supervisors interview | Security office | Reissue the contractor's credential under the long-tenancy contractor protocol; verify the lock supports per-credential window update | Per-credential window update — check against the model specification |
| Shared credential (an operator lends their RFID card to a colleague) | Audit log shows the same credential ID at the door when the operator is off-shift | Shift supervisor | Credential is suspended (not deleted) on first event; HR interview on second event | Per-credential suspension vs deletion — check against the model specification |
| Mechanical-key override out of envelope | Quarterly mechanical-key drill | Production manager | Re-seal the envelope; verify the cylinder is not worn | Mechanical-key envelope custody; cylinder replacement policy — check against the model specification |
| Lunch back-flow disagreement with time-attendance | Monthly time-attendance reconciliation | Production manager | Topology change: enable canteen back door as separate reader; revisit lunch window policy | Per-door log pairing — check against the model specification |
The quarterly review is a two-hour meeting at the end of each quarter: the production manager, the security office, the HR roster owner, the time-attendance administrator, and the shift supervisors review the drift-mode inventory, the by-pass log trend, the contractor ledger reconciliation, and the audit-log retrieval test (the audit log is retrieved from the lock and reconciled to the time-attendance roll-call for a sample week). The mechanical-key drill is exercised during the quarterly review — the override is opened, the door is verified to open and close, the override is re-sealed. The audit log retrieval test confirms that the lock's read-out path works (USB export, app export, software export — every model is different; check the model’s published specification).
Protocol 7: Per-Model Reconciliation — Model specification check
The factory employee entrance SOP is method-agnostic; the lock you specify is not. Protocol 7 is the published reconciliation between the protocol and the model. Check the model’s published specification for the model you shortlist: every cell in the table below, in writing, before the order is placed.
| Protocol step | Capability the lock must support | Check against the model specification |
|---|---|---|
| Protocol 1 line-entry surge | Multi-reader / multi-admin topology; per-event type; read time at surge rate | Yes — confirm multi-reader topology and read time |
| Protocol 1 by-pass handling | Per-operator single-use PIN issued by name; single-use PIN time-bounded to surge window | Yes — confirm single-use PIN support and time-window granularity |
| Protocol 2 PPE exception ladder | RFID + fingerprint + PIN combined credential; per-operator alternate credential path | Yes — confirm combined credential support and per-operator alternate-path enrolment |
| Protocol 2 mechanical-key fallback | Mechanical-key cylinder override (5-pin class reference) with envelope custody policy; cylinder replaceable on site | Yes — confirm cylinder spec and replacement policy |
| Protocol 3 contractor day-pass | Per-credential expiry to the minute; per-credential window update; per-credential revocation (single-door and lock-wide); per-credential direction control | Yes — confirm per-credential expiry granularity, per-credential window update, and per-credential direction control |
| Protocol 4 lunch back-flow | Per-door time-window policy; per-event direction control; per-door log pairing | Yes — confirm per-door time-window policy and per-door log pairing |
| Protocol 5 weekend closure and 22:00 mechanical exercise | Mechanical-key override distinguishability into the audit record; cylinder replaceable on site | Yes — confirm override distinguishability and cylinder replacement policy |
| Protocol 6 drift-mode inventory | Audit-log retrieval path; audit-log capacity; audit-log fields per event (credential ID, time, direction, by-pass flag); per-credential suspension vs deletion | Yes — confirm audit-log retrieval path, capacity, and fields per event; confirm per-credential suspension vs deletion |
| Protocol 6 quarterly mechanical-key drill | Mechanical-key cylinder; replaceable on site | Yes — confirm cylinder replaceable on site |
| PPE exception handling | Fingerprint performance under glove / moisture / dust / minor injury; secondary credential path per operator | Yes — confirm fingerprint performance under PPE on the product page; per-model behaviour varies |
| App / Bluetooth lane | TTLock / Tuya / Doodle app family on the model; per-operator credential binding; per-operator credential revocation from the app | Yes — confirm app family on the product page |
| Battery and dead-battery rescue | Battery type (4×AA reference from the hotel-class spec block); battery-low warning channel (in-app, on-device, both); dead-battery mechanical rescue | Yes — confirm battery type and dead-battery rescue on the product page |
| Audit log retention | Audit-log capacity per model (the hotel-class spec block lists up to 1,000 records on that one model — this is a property of that model, not to be transposed to a factory-entrance model) | Yes — confirm audit-log capacity on the product page; do not transpose figures across models |
The honest framing. Every per-model capability in the table above is a confirmation step on the product page, not an assertion in this document. The published spec sheets are written for the office environment and the hotel environment; the factory entrance is the most demanding door class this catalog serves, and the published numbers will be different. Palm vein-pattern, Matter, Zigbee, Apple Home Key, and UWB are stated as not offered — do not design your exception handling around a technology you will not be buying. Pricing, MOQ, lead time and warranty are explicitly out of scope for this document; the per-model confirmation is the technical confirmation, not the commercial one. For the commercial confirmation, route to Request a quote; for the sample-evaluation plan, route to Order samples.
Illustrative Scenario — A 320-Person Metal-Stamping Plant Through One Quarter
Consider a 320-person metal-stamping plant in northern Italy running three shifts (06:00–14:00, 14:00–22:00, 22:00–06:00). The plant has two production lines (Line A and Line B), one canteen (200 seats), one contractor gate (separate from the line-entry turn), and a goods-receipt bay. The line-entry turn is on an RFID reader at 13.56 MHz (Mifare 1) with a fingerprint reader and a PIN keypad as secondary paths; the lock is a multi-method model supporting per-credential expiry and per-event direction control. The plant has been running for nine months. The first quarter under the SOP runs as follows.
Week 2 — first by-pass event. The morning surge queue forms at 05:58 because the day-shift supervisor opened the line early. The primary reader processes the surge in seven minutes, but 18 operators walk in behind the people in front of them (by-pass). The supervisor records the by-pass count in the production log. The supervisor enables the secondary reader at 05:55 for the next shift. By week 4, the by-pass count is under five per shift.
Week 5 — PPE exception ladder triggers. A chemical-store operator with high-solvent gloves presents the fingerprint reader and fails three times in two minutes. The operator moves to the RFID path; the RFID is the operator's primary path because the operator's enrolment record has been updated to put the RFID first. The supervisor writes the enrolment update into the enrolment register and emails it to the security office.
Week 7 — contractor day-pass survives expiry. A racking installer's day-pass issued on Friday for a Saturday overtime is not collected. The contractor presents the day-pass on Monday morning at the contractor gate. The contractor gate officer checks the contractor ledger, sees the day-pass is expired, and re-issues a new day-pass with a new serial number. The old day-pass is hard-revoked at the time the new day-pass is issued.
Week 9 — lunch back-flow disagreement. The 12:30 reconciliation shows the audit log out-events exceed the in-events by 31 operators. The supervisor reviews the audit log by name. Twenty-eight operators are in the canteen (their in-event is after 12:30 because they took a longer lunch). Three operators have no in-event at all — they left the site without presenting an in-credential. The production manager decides to lengthen the lunch window from thirty minutes to forty-five minutes for the next quarter.
Week 12 — quarterly review. The production manager, the security office, the HR roster owner, the time-attendance administrator, and the shift supervisors run the quarterly review. The drift-mode inventory is reviewed: no orphaned credentials, no permanent temporary credentials, no shared credentials, no mechanical-key out of envelope. The contractor ledger is reconciled. The mechanical-key drill is exercised — the override is opened, the door is verified to open and close, the override is re-sealed. The audit-log retrieval test confirms the lock's read-out path works.
Week 13 — drift-mode inventory catches a permanent temporary credential. The contractor ledger shows a structural-engineering assessment contractor whose day-pass has been reissued every quarter for two years. The contractor is reissued under the long-tenancy contractor protocol; the lock's per-credential window update is exercised, and the contractor's RFID is set to a six-month window with a hard-expiry on the project end date plus seven days.
Closing posture. The lock at the line-entry turn is the same lock it was at the start of the quarter. The protocol is not. The by-pass count is below five per shift, the PPE exception ladder is updated for two operators, the contractor ledger is reconciled at every shift, the lunch back-flow is reviewed monthly, the shift-change pocket is empty, the mechanical override is exercised at 22:00 every night and during the quarterly review. The factory employee entrance is no longer a door with a credential on it; it is a documented production rhythm. That is the value of the SOP.
Closing Position
This document is a factory employee-entrance SOP for smart locks. It is not the plant-wide lock plan (that is Smart Locks for Manufacturing Plants, article 362). It is not the fingerprint-only hire-to-exit lifecycle (that is Fingerprint Smart Locks for Employee Entrances, article 285). It is not the corporate-office daily discipline for the white-collar side of the same company (that is Smart Locks for Employee Entrances, article 347). What it owns is the daily production rhythm at one factory employee entrance: the line-entry badge presentation turn, the contractor day-pass gate, and the lunch back-flow pulse, governed by an explicit protocol at each moment, reconciled to the time-attendance roll-call at every shift, and reviewed at every quarter. Where this article makes a capability claim — a per-credential expiry to the minute, a per-event direction control, a per-door time-window policy, a multi-method credential, a per-credential revocation, an audit-log retrieval path, a mechanical-key envelope custody — that claim is carried as Check the model’s published specification. Where this article touches pricing, MOQ, lead time, warranty, certification, IP rating, fire-rating, or factory-direct figures, the article routes to Request a quote and to Order samples, and makes no claim in text.
For a factory-grade sample-evaluation plan to run against this SOP, request samples and a written confirmation of the per-model capability set against Protocol 7's reconciliation table at Order samples. For a quote on the full lock set against this protocol stack, route to Request a quote. For the broader plant-wide lock plan that this article deliberately does not own, read Smart Locks for Manufacturing Plants. For the corporate-office daily discipline on the white-collar side of the business, read Smart Locks for Employee Entrances. For the fingerprint-only hire-to-exit lifecycle on the same kind of door, read Fingerprint Smart Locks for Employee Entrances.

