LAURANKA
ROC Watch Integration
ROC Watch Integration BETA RELEASE
Seamless Attendance Tracking with AI-Powered Surveillance
FORWORD
What is ROC Watch and what is this Integration? - ROC Watch is a smart video surveillance platform that uses artificial intelligence (AI) to recognize people and monitor movement through camera feeds. We’ve integrated with ROC Watch to automatically track when individuals enter or exit specific areas, allowing us to generate reliable attendance data without the need for manual sign-ins or swipe cards.
-
ROC Watch Website: www.roc.ai
What is required to have ROC Watch Integration? - In order to have ROC Watch Integration, a few things are required -
-
Lauranka's optional add-on ROC Watch Integration Software License (plus Version 4.030 or later)
-
A fully licensed (and setup) version of ROC Watch (plus their latest version -Version Number TBA) - www.roc.ai/watch
Plus setting up / importing the following Workflow into ROC Watch that will create the required CSV File used below. The Workflow file (ROC_Watch-Lauranka-CSV_Attendance_File.json) can be downloaded from our Dropbox here.
Once downloaded, you can import this into ROC Watch via their - 'Workflow' - 'Import' function.
Please Note: Currently the file being created by ROC Watch is called -
face_match_log.csv
As the face_match_log.csv file resides on a Linux system, you will need to set up a routine to automatically transfer it to the Windows folder C:\MTX where the import process takes place.
This can be achieved using tools such as:
- WinSCP (with scripting or automation)
- PuTTY’s pscp (used in batch scripts with Task Scheduler)
- SFTP/SCP automation via PowerShell, cron jobs, or SSH key-based scripts
We recommend configuring a scheduled task on Windows or a cron job on Linux to ensure the file is consistently delivered to C:\MTX without manual intervention.
____________________________
Lauranka Time Clock Integration - Setup and Key Considerations - Firstly, please note the following features are only enabled and will work if the ROC Watch Integration License has been enabled within your Lauranka Time Clock Software.
Overview of Integration - When the ROC Watch Integration is active, Lauranka Time Clock can import, sort, and process a special Time Log file generated by ROC Watch.
Because this log may record hundreds of daily movements per person, Lauranka uses built-in logic to select relevant entries for Attendance and discard irrelevant ones. These assumptions and processing rules are explained in the sections below.
The Time Log File Requirements - To ensure proper processing, your ROC Watch system must output the Time Log file in the following format:
-
File Type: .CSV
-
File Name: Can be any name, but must have a .CSV extension
-
Default Folder: C:\MTX
-
If using a different folder, ensure only ROC Watch CSV files are stored there.
-
All .CSV files in the folder will be imported.
-
Configuring Import Settings in Lauranka - To review or adjust import settings:
-
Go to Main Menu
-
Select Setup
-
Choose Import Setup
-
Select ROC WATCH
Notes:
-
Unless otherwise required you should ensure that the option 'Keep Only First and Last Clocking' remains ticked. If you untick this box ALL movements on the Time Log file will be converted to Attendance Records and NOT processed according to the special Group Rules detailed below.
-
As this file is using EPOCH time, if you need to add an offset to index the Time correctly for your location please select your required 'Time Zone'.
-
If you have multiple ROC Watch geographical locations feeding into Lauranka with different Time Zones and can't consolidate into a single Time Zone, please create 'New' Import Setup functions copying the below features, but making specific to the source / conversion location.
-
The logic for using and/or discarding data is applied during the Import of Punches into Lauranka. When Punches are Imported, data is only appended or updated if two conditions are met:
-
The data must be specific to the employee in question, and
-
The data must relate to an open week.
If both conditions are satisfied, then any relevant data - whether newly imported or already existing - will be appended and/or updated according to the Rules detailed below.
When generating the Time Log Transaction from ROC Watch it must be in the following format:
Sample Time Log Transaction Line:
"ROC_Internal_ID","First_Name","Surname","Lauranka Test","Camera_Details",1756675800,"FaceMatch"
Where:
-
"ROC_Internal_ID" = Required - Must match Lauranka's "Card No/Unser ID"
-
"First_Name" = Not required (but must have a filler if not used)
-
"Surname" = Not required (but must have a filler if not used)
-
"Lauranka Test" = Not required (but must have a filler if not used)
-
"Camera_Details" = Not currently required (but must have a filler if not used)
-
1756675800 = Required - EPOCH Date/Time
-
"FaceMatch" = Not required (but must have a filler if not used)
____________________________
How Lauranka Handles Multiple Daily Clockings (from ROC Watch)
Lauranka applies rules to determine which clocking times to keep and which to discard when processing attendance data from ROC Watch. These rules depend on two settings found in each employee’s assigned Group (Rules):
Extend Hours
Maximum Shift
How It Works
1. Extend Hours = NO
Maximum Shift = 00:00 (not set)
Only the first and last clockings for the defined day are kept.
All other clockings for that day are deleted.
____________________________
2. Extend Hours = NO
Maximum Shift is set (greater than 00:00)
Only the first and last clockings within the following window are kept:
-
From the first clocking of the day, up to:
-
The end of the day, or
-
First clocking + Maximum Shift,
-
Whichever comes first
-
All other time logs outside this window (or between the first and last within it) are deleted.
Note: This setting allows for multiple sets of clockings to be recorded in the same day — if additional clockings occur after the Maximum Shift period, but still before the Day Change Time.
In those cases, Lauranka will apply the same rule again to the new set — keeping only the first and last clockings within the next valid window.
____________________________
3. Extend Hours = YES
Maximum Shift must be set (greater than 00:00)
Only the first and last clockings within this extended window are kept:
-
From the first clocking of the day, up to:
-
The end of the day + Extend Hours period, or
-
First clocking + Maximum Shift,
-
Whichever comes first
-
All other time logs outside this window (or between the first and last within it) are deleted.
Note: Like Rule 2, this setting allows for multiple sets of clockings to be tracked if they occur after the initial Maximum Shift window, but still before the Day Change Time.
Each new set is processed the same way: Lauranka keeps only the first and last clockings in that window.
What is a “DAY”?
A DAY is defined as the 24-hour period starting from the configured 'Day Change Time'. For example, if the Day Change Time is 2:00 AM, then a new day runs from 2:00 AM to 1:59 AM the following day.
