InnerWeb
Skip to main content

Checklist for accepting a service entry to a water facility

Accepting a service entry path is the moment to check whether the scan, qualifications, work permit, register entry and evacuation list work as one whole. It is better to find a gap at acceptance than after the first incident. Below is a checklist with comments on what exactly to check and what evidence to keep.

4
components of the verdict at the scan
Source: card
6
groups on the evacuation list
Source: card
13 s
refresh of the evacuation list
Source: card

How to use this checklist

The checklist is run on a real facility with a person from security or operations present, preferably using a test account for a service engineer. For each point, record the result and the evidence: a screenshot, a register entry or a short note. Acceptance without evidence is a declaration, not an acceptance.

At distributed sites, run acceptance separately for each type of facility: water treatment station, pumping station, wastewater plant. The layout of entries differs, so a result from one does not transfer to another.

Scan and verdict at the gate

The first block concerns the scan itself. Scanning a QR badge or RFID card on the security screen gives a verdict on whether the person may be on site: valid training, qualifications for hazardous work, a permit in progress and an active account. Check that the verdict appears in each of the four cases, including the negative one.

The scan at the gate is itself a control act and records the entry. Confirm that after the scan the entry appears in the register with the correct time and place.

Parameters to check at acceptance

Parameters to check at acceptanceHorizontal bar chart: 180 seconds, 13 seconds, 13 hours and 12 hours.050100150200value in the stated unitDuplicate rejection (s)Duplicate rejection (s): 180 value in the stated unit180Evacuation list refresh (s)Evacuation list refresh (s): 13 value in the stated unit13Entry and exit pairing window(h)Entry and exit pairing window (h): 13 value in the stated unit13Token validity (h)Token validity (h): 12 value in the stated unit12
Source: Card sheet: access control event integration and evacuation list

Qualifications and work permit

The second block links the scan with authorisations. When a permit is created, the system automatically checks whether the assigned workers hold the required, valid authorisations. Run a test: try to assign a person with an expired authorisation and confirm that the system shows it.

Also check the path for external companies. The request of an external company and a permit issued to a contractor work on the same permit, visible on both sides. Confirm that the client and the contractor see the same document and the same status.

Register entry and access card events

The third block is the register. If the facility has an access control system, check that card swipes reach InnerWeb. Events arrive through an HTTPS message initiated by the plant on port 443, with a technical account and a token with limited validity, renewed automatically by the integration. Make a test swipe and check whether the entry appears with the event time from the reader.

Check edge cases according to the integration specification agreed with the access control vendor: the event must carry direction and identifier, and the rules for pairing entries with exits and rejecting duplicates are described there. Make two swipes in a row and confirm that one entry is created.

Remember that the integration needs no replacement of cards or readers. If an entry is missing, the cause is usually the configuration of the entry and exit reader list on the access control vendor's side.

Evacuation list and change trail

The fourth block is evacuation. The evacuation list is built from QR scans at the gate, refreshes every 13 seconds and divides people into six groups, including external companies and uncertain people. After a test entry by the engineer, check that they appear on the list in the right group, and after exit that they disappear.

The last element is the change trail. Changes to permits, the taxonomy of hazardous work, training results, automation rules and inspection routes are saved with author and time. Make a test change and confirm that the author and the hour were recorded.

Acceptance evidence

The acceptance report contains the result of each point and the evidence attached. For the next facility of the same type, the protocol is the template to repeat.

Checklist

Video

Frequently asked questions

Who should carry out the entry path acceptance?

Ideally a person from security or operations together with a representative of the access control vendor, on a real facility and with a test service engineer account.

How often should this acceptance be repeated?

After every change to gate, reader or access control integration configuration, and when a new facility starts operating. For distributed sites, acceptance is run separately for each type of facility.

What to do when an entry is missing after a card swipe?

Check whether the reader is on the entry or exit reader list given to the access control vendor, and whether the HTTPS message reaches the plant on port 443.

Run acceptance at your facility

Book a conversation with InnerWeb and walk through this checklist at your water treatment station or pumping station together with our team.

Let's talk