The Electronic Lock That Forgets Itself
A small office has 14 electronic cylindrical locks (standalone, keypad plus mechanical key override) installed on interior doors. Over three weeks, staff report that two locks on the east corridor randomly reject valid codes, and one lock's audit log shows entries with timestamps that jump backward by several hours. The building has no network - the locks are programmed by a handheld programmer at the door. The office manager says the batteries were replaced six months ago on all 14 locks at once. The east corridor doors are next to a kitchenette with a commercial refrigerator and microwave. The locks are rated for indoor use and the manufacturer specifies a minimum operating voltage.
1. Rank the plausible causes for the random code rejections and the timestamp drift, and justify the ranking.
Read the worked answer
Most likely: low battery voltage on the affected locks, possibly aggravated by electrical noise.
Reasoning:
- All 14 batteries were replaced at the same time six months ago, but the east corridor locks are on doors near a kitchenette. Those doors likely see far more traffic (staff going for coffee, lunch) than the others, so those two locks have cycled their motors far more and are closer to end-of-life. A lock that's near its minimum operating voltage will intermittently fail to complete a read/verify cycle and reject a valid code - a classic low-voltage symptom, not a programming error.
- The timestamp drift on a third lock is a separate clue. Standalone locks keep time on an internal clock; if the battery sags or the lock browns out, the clock can reset or drift. A backward jump of several hours is consistent with a brownout/reset, not with a programming mistake.
- Electrical noise from the refrigerator compressor and microwave is a plausible aggravating factor but a weaker primary cause: it would tend to cause sporadic faults only while the appliance is running, and wouldn't explain a persistent timestamp drift.
So: batteries first (age + duty cycle), then check for noise/grounding, and treat the timestamp issue as evidence of the same underlying power problem.
Less likely but worth ruling out: a corrupted user database from a botched programmer session, or a firmware fault. These would usually affect programming consistently rather than randomly.
2. Describe the diagnostic sequence you'd run and the fix, including what you'd tell the manager about the other 11 locks.
Read the worked answer
Diagnostic sequence:
- Measure battery voltage under load on the two failing locks and the drifting one - not open-circuit voltage, which reads high even on a dying cell. Compare to the manufacturer's minimum operating voltage.
- Check the audit log on each lock for the timing of failures and correlate with kitchenette use (appliance cycling).
- Re-test codes immediately after a fresh battery install on one lock - if the fault disappears, that confirms the diagnosis.
- Inspect the door hardware - a binding latch or misaligned strike makes the motor work harder and drains the battery faster, which would explain why these doors specifically are worse.
- Only if the fault persists on fresh batteries would I suspect the programmer/database or firmware, and then I'd reflash or re-enroll users.
Fix: Replace batteries on the affected locks (and honestly, all 14 - they were all installed the same day and are the same age). Correct any binding latch/strike on the east corridor doors so the motor isn't overworked. Re-sync the clock on the drifting lock via the programmer.
What to tell the manager: The other 11 locks are the same age and will fail on a similar timeline. Recommend a scheduled battery replacement program (e.g., every 12 months, or on the lock's low-battery warning) rather than waiting for failures, and note that high-traffic doors may need more frequent changes.