InnerWeb
Skip to main content

RCP and access control: costs and savings when time records use card taps

RCP (working time recording) and access control (KD) are two different systems with different purposes, but both rely on the same event: a card tap at a passage. When a plant runs them separately, HR and security do the same work twice. Below are the differences in terms and a sample calculation of the hours that can be recovered.

28 h
recoverable per month in HR and security (illustrative calculation)
Source: illustrative calculation
13 h
pairing window between an entry and an exit
Source: product sheet
180 s
threshold for discarding duplicate card taps
Source: product sheet

Two systems, one event

Access control answers the question: may this person enter here. RCP answers a different one: how many hours did this person work. The card tap event, meaning the carrier number, the time and the passage point, serves both systems, but it is often recorded separately because each comes from a different vendor or department.

Gate scans create working time records (RCP) with daily, monthly and yearly views, exception queues and period closing. As a result, an event recorded once at the gate serves both security and hours settlement.

Where the cost of double recording arises

The cost of double recording has several elements that are easy to overlook, because they are spread across different departments.

The first is manual settlement of exceptions in HR, for example a missing exit tap. The second is a separate entry list kept by security. The third is mutual explanation of discrepancies between these two records during a dispute about working time.

What tap pairing does

When the reader in the client's access control system does not report the direction of passage, the rules for pairing entries with exits and discarding duplicates are set in the specification with the access control vendor, for example a pairing window of 13 hours and discarding duplicates within 180 seconds. Well-defined pairing reduces the number of exceptions that a person has to resolve.

Monthly HR and security hours: separate recording vs card taps from access control

Monthly HR and security hours: separate recording vs card taps from access controlComparison of monthly hours: HR 10.5 hours against 3.15, and security 31.5 hours against 10.5 with card taps from access control010203040hSeparate recording (HR: exceptions): 10.5 h10.5 hCard taps to RCP (HR: exceptions): 3.15 h3.15 hHR: exceptionsSeparate recording (Security: entry list): 31.5 h31.5 hCard taps to RCP (Security: entry list): 10.5 h10.5 hSecurity: entry list
  • Separate recording
  • Card taps to RCP
Source: Illustrative calculation based on the assumptions in the calculation table

How card taps from access control reach RCP

InnerWeb receives card tap events from the client's access control system via a webhook and links them with qualifications, permits, attendance and RCP. InnerWeb is a software maker: it does not produce or replace card readers or access cards, but integrates with the access control system the client already has.

For the plant this means readers do not have to be replaced or duplicated. What is required is a specification from the access control vendor that sends the events, and an agreement on which passages count as working time recording points.

Sample calculation of HR and security hours

The calculation is illustrative. A plant with 250 employees, 21 working days per month and 2% of days with a missing exit tap has 105 exceptions a month. At 6 minutes per exception, HR loses 10.5 hours. A separate entry list kept by security takes 1.5 hours a day, which gives 31.5 hours a month. Together, 42 hours.

Assuming that pairing resolves 70% of exceptions automatically, HR spends 3.15 hours on them, and security reduces list keeping to 0.5 hours a day, which is 10.5 hours. Together, about 13.7 hours. The difference is about 28 hours a month.

Limits of the calculation

The calculation does not include the cost of the integration or the time needed to set the period closing rules. The share of exceptions and the share resolved automatically are assumptions that the plant should verify on its own data from several weeks.

Pairing entries and exits does not resolve cases where an employee enters through one passage and leaves through another, if the exit passage is not a time record point. Such cases go to the exception queue and require a human decision.

Example calculation

Monthly HR and security hours

Assumptions
ParameterValue
Employees covered by RCP250 people
Working days21 days/month
Days with a missing exit tap2 %
Time to resolve one exception6 min
Exceptions resolved automatically by pairing70 %
Security entry list: without taps / with taps1.5 / 0.5 h/day

Result: Separate recording: 10.5 + 31.5 = 42 h. Card taps to RCP: 3.15 + 10.5 = 13.65 h. Difference: about 28 h a month.

Note: Illustrative calculation; it does not include the integration cost. Replace the assumptions with the plant's own data.

Video

Frequently asked questions

Are RCP and access control the same thing?

No. Access control assesses the right to enter, and RCP settles working time. What they share is the tap event, which both systems can use.

What about a reader that does not report the direction of passage?

The rules for pairing entries with exits and discarding duplicates are set in the specification with the access control vendor, for example a window of up to 13 hours and a duplicate threshold of 180 seconds.

Do the access control readers have to be replaced?

No. InnerWeb integrates with the client's existing access control system via a webhook and does not produce readers.

Let us count the hours on your data

Together with HR and security we will review several weeks of card taps and show how many exceptions can be resolved automatically. We invite you to a conversation.

Let's talk