What is a cost and what is not in the bill
InnerWeb is a software vendor and neither manufactures nor replaces access control readers. It integrates with the client's existing access control system, so the bill contains no readers, cards or cabling. InnerWeb is an independent system that complements the existing systems: access control, RCP, HR and ERP, which means the integration is an addition, not a replacement.
The integration cost therefore consists of people's work: an analyst, a developer on the access control vendor side, a developer on the InnerWeb side, a tester and the person accepting the work on the plant side. Each of these items can be estimated, and the largest uncertainty concerns the response time of the access control vendor.
Scope of work step by step
Below are five items that appear in every integration of card swipes with time and attendance records. The order follows the actual course of the project.
1. Event specification for the access control vendor
The card swipe webhook receives events in real time: the event time from the reader, the location, the person's data, the company and the number of the active card. It authenticates with a token of limited validity, renewed automatically by the integration. The specification for the access control vendor also describes the entry/exit direction and the event identifier, as well as the rules for pairing and rejecting duplicates. This item is inexpensive, but it determines the rest of the project.
2. Extension on the InnerWeb side
The extension on the InnerWeb side covers accepting the direction and the event identifier, filtering out duplicates according to the agreed rules, and linking the event to the employee's record, so that the swipes feed the time and attendance records. This item is priced individually, because it depends on the data format of the access control vendor.
3. Work on the access control vendor side
The access control vendor sends events to the agreed address and adds new fields. Handling of resends and a queue for the case when the recipient is unavailable are required. The time of this item is often the hardest to predict, so it is worth recording it in the schedule as a separate risk.
4. Tests with the plant's cards and gates
The tests cover entries, exits, double swipes, a change across midnight and an external company. For an external company, the automatic checkout after the limit is exceeded records an exit, and the default maximum stay is 12 hours, so this path is checked separately.
5. Acceptance and training of the HR staff
HR and supervisors must see the exception queues on real data. The module can first be enabled for a list of testers, and only then for everyone.
Sample integration effort (upper limit of the ranges)
Sample effort and ranges
These are indicative ranges from deployments in 2025-2026; individual quote. We give them in person-days, because the hourly rate is a matter of the contract, not of the technology. The sample calculation assumes one access control system, one event format and one plant location.
- Specification and agreements with the access control vendor: 2-4 person-days.
- Extension on the InnerWeb side (direction, identifier, duplicates): 5-10 person-days.
- Work on the access control vendor side: 3-8 person-days, depending on whether the events are already available.
- Tests with cards and gates: 3-6 person-days.
- Acceptance and training: 2-3 person-days.
What determines the upper limit
Several factors raise the upper limit: no possibility of adding fields on the access control vendor side, several access control systems across a group of plants, no test environment, and many gates requiring separate trials. The lower limit is reduced by the availability of the access control vendor's documentation and a ready way of sending events.
When purchasing, it is worth asking the access control vendor for a written answer to three questions: whether a direction can be added, whether each event has a stable identifier, and how the system behaves when the recipient is unavailable. These answers significantly narrow the ranges before the scope is signed.
Integration effort of one access control system with time and attendance records
| Parameter | Value |
|---|---|
| Number of access control systems | 1 system |
| Replacement of readers and cards | 0 pcs |
| Event format | one, agreed |
| Access control vendor test environment | available |
Result: Total of items: from 15 to 31 person-days, of which the largest items are the extension on the InnerWeb side and the work on the access control vendor side.
Note: Sample calculation; indicative ranges from 2025-2026 deployments; individual quote. It is not an offer.
Video
Frequently asked questions
Do readers need to be replaced to feed time and attendance records?
No. InnerWeb integrates with the client's existing access control system and does not replace readers or cards.
What is the most common source of delays?
The response time of the access control vendor in adding the direction and event identifier fields. It is worth recording it in the schedule as a separate risk.
Are these ranges an offer?
No. They are indicative ranges from 2025-2026 deployments; an individual quote follows the analysis of the access control system.
Let us start with the specification for the access control vendor
We will prepare a list of fields and questions for your access control vendor, so that the ranges can be narrowed quickly. Arrange a talk with the InnerWeb team.
Let's talk