Where coordinator time goes today
Manual recording of external contractors has three sources of lost time. The first is re-typing data from a paper book or an email list into a spreadsheet. The second is agreeing who was actually on site when the gate list and the company list differ. The third is searching for entries and exits when attendance for a given day has to be rebuilt after an incident.
None of these steps adds safety. They follow from the fact that entry information is created in one place (access control) and needed in another (attendance register, evacuation list, service billing).
What receiving access control events changes
InnerWeb receives card swipe events from the access control system through an HTTPS message initiated by the plant's site on port 443, with no inbound ports opened. The message carries the time from the controller, the reader identifier, the person and the card number. The attendance register fills itself at the moment of the swipe.
The access control system sends events with the event time from the reader, the direction and an event identifier. The rules for pairing entries with exits and rejecting duplicates are set in the specification with the access control vendor, so that a double swipe at a gate does not inflate the number of entries. The integration needs no replacement of cards or readers, so the cost on the plant side is mainly agreeing the configuration with the vendor.
The result for the coordinator: the list of people on site is ready without re-typing, and the evacuation list, refreshed every 13 seconds and split into six groups, uses the same data.
Monthly manual attendance recording time
Sample calculation: a site with external contractors
Consider a water and sewage plant where, at 400 contractor entries a month, the coordinator handles manual lists. All figures below are assumptions for a sample calculation, not data from a specific facility.
Manual time: 4 minutes per entry, which covers re-typing, checking and agreeing with the company. Together 400 times 4 minutes gives 1,600 minutes, about 26.7 hours a month.
Time after integration: the register fills from the swipes, and only 10 percent of entries (exceptions, for example a missing exit) need manual handling at 4 minutes each. That is 40 entries times 4 minutes, or 160 minutes, about 2.7 hours a month.
The saving is 1,440 minutes, or 24 hours a month. At an assumed cost of 80 PLN per coordinator hour, this gives 1,920 PLN a month and 23,040 PLN a year. This is a sample figure: with your own numbers the result may be higher or lower.
How to recalculate with your own figures
Count contractor entries from the last three months, time one entry with a stopwatch on a representative sample and estimate the share of exceptions. Three figures are enough to reproduce the calculation.
What this calculation does not cover
The calculation counts only coordinator time. It does not value fewer disputes with contractors over working hours, faster reconstruction of attendance after an incident, or shorter audit preparation. These are real benefits, but their value depends on the site, so they are not included in the result.
The implementation cost is not included either. Indicative price ranges depend on the scope of modules and integrations, and pricing is individual. It is worth comparing the annual saving with the licence cost and with any beacon network, if the site will also use location.
The calculation for distributed sites should be made separately per site: a facility with heavy contractor traffic saves more than a pumping station visited once a week, and an average of the two would distort the picture.
How to collect evidence of savings after rollout
Before the integration goes live, measure the time of manual recording over two weeks. After go-live, measure the time spent on exceptions. The difference is the result for the management report.
Changes to permits, training results and inspection routes are saved with author and time, so when the effect is assessed it is clear when settings changed. A measurement made on rules that keep changing is hard to interpret honestly later.
Coordinator time before and after access control integration
| Parameter | Value |
|---|---|
| Contractor entries | 400 entries/month |
| Manual entry time | 4 min/entry |
| Exceptions after integration | 10 % of entries |
| Coordinator hour cost | 80 PLN/h |
Result: Before: 1,600 min. After: 160 min. Saving 1,440 min, or 24 h a month, 1,920 PLN a month, 23,040 PLN a year.
Note: Sample calculation on the assumptions above; recalculate with your own number of entries, entry time and hourly cost.
Video
Frequently asked questions
Does integration with the access control system require replacing cards or readers?
No. The integration needs no replacement of cards or readers. With the access control vendor, it is agreed whether the system can send HTTPS POST, which reader list means entry and which means exit, and how cards are exported.
Is 10 percent exceptions a realistic figure?
It is an assumption for the sample calculation. The actual share depends on the quality of reader configuration and discipline in swiping cards, so it is worth measuring it on your own data.
What about two swipes for a single entry?
The rules for rejecting duplicates, based on the event identifier, are set in the specification with the access control vendor, so that a double swipe does not inflate the number of entries.
Recalculate the savings on your own figures
Give us the number of contractor entries and the current time of manual recording, and InnerWeb will prepare a calculation for your facility.
Let's talk