Introduction
The gate knows only what the system can check
A reader receives an identifier. The system then checks available rights and status. If approved conditions are met, a command can be sent. This mechanism requires precise definitions and a procedure when information is missing or challenged.
Definitions
Write the logic in ordinary language before configuration.
For each user class, document the accepted identifier, required steps, duration, relevant sites and the person allowed to grant an exception. Have the responsible authority validate the policy.
- Source of wash status
- Relevant watercraft or record
- Validity period
- Sites recognizing the status
Response at access
Every denial should lead to a next action.
Missing status can direct the user to the station; an incomplete record to the kiosk; an expired right to renewal; and a technical problem to support. A useful message does not need to expose sensitive information.
Degraded operation
Decide in advance what happens without network service or with failed equipment.
The organization weighs the risk of opening, closing or manual processing for the site. Emergency and manufacturer release procedures remain separate from commercial logic.
Review
Keep a trace of correction without erasing context.
If a right or record needs correction, permissions determine who can act and what notes are required. A camera or alert can support review but does not replace the authorized person.
