Access control and gatehouse for an industrial complex
Visitor and cargo scheduling with approval, QR code badges, vehicle control and site occupancy, connected to the access control equipment.
Case summary
An industrial complex hosting several companies controlled visitor and cargo entry by email and spreadsheet. We built a system in which each company schedules its own access, an approver clears it, the gatehouse checks the QR code badge and management sees site occupancy. The system talks to the access control equipment.
What the system does
- Visitor and cargo scheduling
- Approval by department
- Badge with QR code and validity
- Registry of people, companies and vehicles
- Safety briefing
- Entry and exit log at the gatehouse
- Site occupancy map
- Status of access equipment
- Reports in spreadsheet and PDF
What was the problem?
An industrial complex receives employees of resident companies, contractors, visitors and trucks every day. Authorization for each entry went by email between the company hosting the visit and the administration, and the gatehouse worked from printed lists. When the list was out of date, the person stood waiting at the gate.
What was built?
A system in which the resident company schedules the access, stating who is coming, when, with which vehicle and to which location. The request goes to the approver of the responsible department, who approves or denies with one click. Each status change is recorded with date and author.
Once access is approved, the visitor receives a badge with a QR code and a validity period. The registry clearly separates company types, between the complex owner, the resident clients and the contractors, and each one sees only its own records.
How does it work day to day?
At the gatehouse, the operator scans the QR code and the screen shows whether access is cleared, to which location and until when. Entries and exits are logged. Vehicles have their own registry and are linked to the booking.
The administration follows site occupancy on a map, by location and by company. A separate screen shows which access control devices are online, comparing the system's registry with what the device server reports.
What changed in the operation?
The gatehouse now decides based on what is approved right now. The resident company follows its own requests without calling the administration, and the administration knows how many people from each company are on site.
This case is a typical custom web system: registry, approval flow, field operation and reporting. For a similar setting in a port, see port operations. If the system you have today already does part of this, see support and modernization.
Services used in this case
Updated on