InnerWeb
Skip to main content

Request for quotation for cards and readers: access control integration requirements

Purchasing and IT teams that ask for card and reader prices often leave out integration with time recording, and later pay to add it outside the offer. Below are the requirements worth putting into a request for quotation, so that time recording and reports continue after the replacement.

12 h
validity of the integration JWT token
Source: integration specification
13 h
limit for pairing entry with exit
Source: integration specification

Why integration requirements belong in the request

A request for quotation for cards and readers usually describes the technology: card type, reader protocol, number of units. It rarely describes what happens to a punch on the server side. If the plant records working time from punches, the lack of such a description means a risk that reports will stop matching after the replacement.

InnerWeb is a software producer and does not supply readers. It receives punch events from the access control system and links them to working days. The requirements below allow the access control vendor to pass these events on without additional negotiation.

Recommendation 1: HTTPS POST from the access control server

Write a requirement that for every punch the access control system server sends an HTTPS POST message to the indicated address. This way no inbound ports need to be opened in the plant network, because the traffic is outbound. The vendor should confirm in the offer whether its server sends such a message.

Authentication of the integration uses a technical account and a JWT token valid for 12 hours, so the request should state that the vendor must support token renewal.

Technical limits of the punch integration

Technical limits of the punch integrationHorizontal bar chart: token valid for 12 hours, pairing limit 13 hours051015hoursJWT token validityJWT token validity: 12 hours12Entry-exit pairingEntry-exit pairing: 13 hours13
Source: Specification of the punch integration with the access control system

Recommendation 2: content of the message

The message should contain the punch time from the controller, the reader identifier, the person, the card number in the form object_code-number and, optionally, the direction and the event identifier. The controller time matters, because the offline queue during a link failure delays sending.

The event identifier (idempotency) and the controller time protect working days from distortion caused by resending. Put this point into the request as a requirement or, if the vendor cannot provide it, as a deviation that requires justification.

Recommendation 3: entry and exit direction

Ask the vendor to state whether the system passes the direction. When it does not, InnerWeb pairs an entry with an exit in the software, with a limit of 13 hours between them. This works correctly, but it requires a description of the readers: separate readers for entry and exit are recorded in the reader dictionary.

Recommendation 4: card export and reader list

To be agreed with the access control vendor before integration: whether its server sends HTTPS POST messages, the reader list, and the export of cards (object code and number) to personnel numbers. Attach to the contract a card export in CSV format with the object code, the number and the personnel number.

Cards can be assigned to people through a CSV import, so the vendor's export is the fuel for the whole process. Without an export, assignment is manual and the schedule is delayed.

Recommendation 5: what the offer excludes and what stays with the plant

State in the request that the access control logic stays unchanged: the vendor does not take over the counting of working days, schedules, exceptions or reports. All processing (entry and exit recognition, grouping into working days, schedules, exceptions, reports) takes place on the InnerWeb side.

Also state costs outside the software scope: a QR code reader at the gatehouse costs around 1,000 PLN net per unit, outside the InnerWeb offer (indicative ranges from 2025-2026 deployments; individual quotation). The vendor should give unit prices for cards and readers separately.

Recommendation 6: unknown cards and acceptance evidence

Add an acceptance criterion: the list of punches from unknown cards after the replacement must be empty or explained. A punch from an unknown card goes to the "card to be assigned" queue instead of creating an account from an unknown punch, so the queue is a ready-made measure.

Video

Frequently asked questions

Does the request have to name InnerWeb?

No. A description of the requirements is enough: HTTPS POST, message content, card export. The vendor will meet them regardless of the name of the recipient.

Do ports have to be opened in the plant network?

No. The access control server sends an HTTPS POST message, so the traffic is outbound.

Who counts working days?

InnerWeb, on the software side. The access control logic stays unchanged.

Sources

Add the integration requirements to your request

We will provide the punch specification for the access control vendor and check whether the offer covers the time recording needs. Book a conversation with InnerWeb.

Let's talk