A complete ESD access-control system normally combines identity verification, wrist-strap and left/right footwear testing, rule evaluation, a controlled door or gate, and networked records. The person identifies first, so the terminal can load the assigned test mode and area permission. It then captures the required test results and evaluates them under the approved site rules. Only a valid test and valid area permission should generate one release command, with the person, time, device, test and passage outcome retained. A stand-alone tester does not provide this complete control loop.
What is often missing from a purchase list
Selecting a tester is only one decision. The project must also establish who is being tested, which items apply to that role, where the decision is made and what happens when a person passes the test but lacks permission for the area.
Without those responsibilities, a site may have a pass lamp with no person record, or a door event with no evidence of the wrist and footwear checks behind it.
Five functional parts
- Identity device: binds the current test to an employee record.
- Wrist-strap and left/right footwear components: capture the items required for this person.
- ESD test terminal: guides the test and applies the rules approved for the project.
- Gate, lock and controller: execute one release only for the current approved transaction.
- Management software: maintains people, test modes, area permissions, devices, records and reports.
Configure for the entrance
A single entrance may use an integrated terminal connected to a lock or gate. A shift-change entrance should be evaluated against the full identity, testing and passage sequence. Multiple areas require consistent device identities, personnel ownership and record routing.
- Verify the control signal, one-person release, status feedback and emergency behaviour before retaining an existing gate.
- Assign wrist, footwear or combined modes by approved role rules rather than applying one mode to everyone.
- Identity options, test combinations, connectivity and interfaces remain product- and project-specific.
Recommended operating sequence
Verify identity → load validity, test mode and area permission → complete the required wrist, left-foot and right-foot checks → retain measured results and decisions → verify area permission → issue one release → capture available passage feedback → upload the test and access record.
- Failed, incomplete, unauthorised and offline conditions need distinct messages and procedures.
- Retesting or manual review should follow the site policy and remain auditable.
Confirm before procurement
- Required tests for each role and who approves the rules.
- Whether identity, testing and release belong to one access transaction.
- Control and feedback available from the passage device.
- Procedures for outages, faults, failed or missed tests and emergencies.
- Required record fields, search rights and retention period.
Frequently asked questions
Do a tester and a gate constitute a complete ESD access system?
Not by themselves. Identity binding, assigned test mode, evaluation, area permission, one-time release and records must operate as one workflow.
Must every entrance use an ESD flap barrier?
No. The project may evaluate an integrated terminal with a lock, retain a suitable gate or use an ESD flap barrier.
Is management software optional?
Networked management becomes important when the site requires personnel traceability, multiple entrances, exception review or reporting. The delivered modules remain project-specific.