Overview
Demonstrations built by Stackline on simulated data. Each one shows a typical workflow and the technical approach behind it. None of them is a client deployment.
Scenario
By default, a simulator plays three terminals in two branches with fictional employees. On a local network, the same panel connects to a real UNV terminal by its IP address and shows only that terminal's data.
Challenge
Face-recognition terminals record every entry, but each record stays inside its device. Finding out who arrived, who was late and why someone was refused means checking one terminal at a time.
Solution
One browser panel receives terminal events as they happen, links them to people and branches, flags lateness and refused attempts, and manages the face library and the door remotely. The same code works with the simulator and with a real terminal.
Architecture overview
- Your systems
- Entrances & doors · Access devices · Access-control software
- Stackline software
- Collect entry events · Match to people & zones · Flag exceptions
- Where the data goes
- Attendance reports (Excel / PDF) · Business systems · Review dashboard
- UNV terminal / simulator
- LAPI push events
- Stackline panel: people, branches, lateness- Stackline
- Today's overview and exceptions
- Stackline panel- Stackline
- LAPI with Digest authentication
- Face library / remote door opening
Built with
Node.js · UNV LAPI · Docker · Chart.js
This demonstration relates to Access Control & Attendance.