Most turnstile tenders still compare photographs, steel grades and price per lane. Three engineering decisions determine whether a lane runs for a decade or becomes a maintenance liability: the drive train, the sensor array that counts people, and the failure logic when power, network or credentials disappear.

1. The Drive Train: Solenoid, Stepper or Servo

A solenoid lock is cheap and fast to open, but it slams: every closure is a mechanical impact that drives warranty claims in high-traffic lanes. Brushless DC servo drives with an encoder close under position control: the controller knows the arm angle, decelerates before the end stop, and reverses instantly when a beam is broken. The measurable difference is MCBF (mean cycles between failures) and acoustic signature — a servo lane is quiet at 60 passages per minute, a solenoid lane is not.

2. Anti-Tailgating Is a Counting Problem, Not a Sensor Count

Adding beam pairs does not automatically stop tailgating. What matters is the tracking algorithm: how the controller associates a sequence of beam breaks into one person, how it distinguishes a wheelchair or a rolling suitcase from a second body, and how quickly it decides to close. A 24-beam array with naive logic false-alarms on luggage; a 12-beam array with per-cell occupancy tracking and a calibrated profile threshold does not. Ask for the false-rejection rate measured on a mixed test group — adults, children, wheelchair users, trolley bags — over at least 1,000 passages.

3. Failure Logic Is Where Compliance Lives

Every lane needs a documented answer to four questions: what happens on power loss, on network loss, on fire signal, and on forced push. Fail-safe (open) suits life-safety egress; fail-lock suits asset protection. Neither is universally correct, so the lane must support both and be configurable per installation. Fire release must be hardware-level — a relay dropping power to the brake, not a command sent over TCP/IP that depends on a running controller.

4. Real Projects Setting the 2026 Requirement Bar

5. Specification Checklist for Procurement

• Demand the cycle-test certificate and the test rig description, not a catalogue MCBF figure.
• Require false-rejection data on a mixed pedestrian group, including luggage and wheelchair users.
• Verify the fail-safe mode is a hardware relay path, independent of the network and of the controller OS.
• Confirm offline capacity: credential whitelist size and event buffer depth with timestamps.
• Check integration surface: OSDP, Wiegand, RS485, TCP/IP and REST/MQTT for the deployed platform.