InnerWeb
Skip to main content

Barrier and access control vendor specification: checklist for purchasing and IT

The tender for a barrier and vehicle access control decides whether gate events reach the plant system or stay in the vendor's inbox. Below is a list of clauses that purchasing and IT should place in the specification, so that badge scans and entries reach InnerWeb through a webhook.

webhook
way of passing badge events from the access control system to InnerWeb
Source: InnerWeb facts

Division of roles: who does what

InnerWeb is a software vendor, not a device maker. It does not produce readers or barriers and integrates with the client's existing access control system. The InnerWeb feature documentation does not describe reading vehicle registration plates or controlling a barrier, so the plant writes these functions as requirements for the vehicle access control vendor.

The InnerWeb system receives badge events from the client's access control system (webhook) and links them with qualifications, authorizations, attendance and working time recording. The barrier and access control vendor is responsible for the hardware, reading and opening, and InnerWeb for the verdict, the register and the link with the rest of the plant.

Clauses for the specification: integration

The most important clause concerns sending events. Without it the access control system works as an island, and InnerWeb does not learn that someone entered or left.

Event webhook

Require the vendor's system to send every badge event to the plant address through a webhook, with the card identifier, time and direction. Refusal events should be sent in the same way as entry events, because InnerWeb also records blocked attempts.

Access to data without changing readers

State that the integration must not require replacing the readers or cards already used at the plant. InnerWeb integrates with the client's system, so the vendor should not make the webhook dependent on buying its own, more expensive module.

Scope of specification items for the vendor

Scope of specification items for the vendorHorizontal bar chart of specification clauses: integration and webhook four, bookings and deliveries three, plates and barrier three.01234itemsIntegration and webhookIntegration and webhook: 4 items4Bookings and deliveriesBookings and deliveries: 3 items3Plates and barrierPlates and barrier: 3 items3
Source: Number of checklist points on this page in each area, not statistical data

Clauses for the specification: bookings and deliveries

If the plant uses a delivery booking system, add a requirement to make the data of the planned delivery available. After the code of the booking card, InnerWeb fetches the delivery data from the client's booking system via SOAP and pre-fills the form. Integration with a different booking system requires implementation work.

The deliveries and appointments module manages vehicles entering the plant: choice of gate, dock or warehouse, driver and closing the delivery. A delivery with a closed transport in the booking system is treated as having no data, so the specification should require the booking system to return the transport status.

Clauses for the specification: plates and the barrier

If the plant wants the barrier to open after reading a registration number, it must write this for the vendor as a function of plate reading and barrier control, with the response time and the rules of emergency opening. Do not expect this function from InnerWeb: it is outside the scope of the software.

Also record who is responsible for manual opening in the event of a power or connectivity failure. The emergency procedure of the barrier must not depend on the software running on the plant network.

Acceptance: how to check the integration

In the acceptance protocol, record a test: a test card presented at the reader should appear in the plant register within a few seconds, together with the direction and the result. Also check a refusal event, and an event after loss of connectivity, when the vendor is to resend queued events.

It is also worth agreeing who on the vendor side is responsible for webhook failures and how quickly they will react. Without this, the duty officer is left alone when events stop arriving.

Checklist

Video

Frequently asked questions

Does InnerWeb sell readers or barriers?

No. InnerWeb is a software vendor and integrates with the client's existing access control system.

How do access control events reach InnerWeb?

By webhook: the system receives badge events from the client's system and links them with qualifications, authorizations, attendance and working time recording.

Will every booking work without implementation work?

No. Fetching delivery data by the booking card code works with the client's booking system via SOAP, and integration with another system requires implementation work.

Check your specification with InnerWeb

We will review the webhook and booking clauses with your purchasing and IT team before the request is sent. Book a conversation with the InnerWeb team.

Let's talk