Did the client have to replace their access-control hardware?

No. The portal was built on top of the existing Hikvision devices and uses their data as the source of truth.

.NET Core 3.1 with Microsoft SQL Server on the back end and Angular 12 on the front end, deployed to the client's server.

Were savings measured?

No. The project delivered the workflows and reporting; time or cost savings were not instrumented, so none are claimed.

Industrial, IoT & Operational SystemsPoultry production company · 2023 engagement

Centralised Attendance & Reporting Portal on Access-Control Device Data Poultry production company

A food-production business running Hikvision access-control hardware across its sites that needed employee operations, attendance and reporting managed in one system instead of per-device portals. The client is not named.

Duration: 2023 engagement

Platform: .NET Core 3.1, Microsoft SQL Server, Angular 12

Channels: OT device data to operational reporting

Build Something Similar What we built

Scope, visualised

What the portal covers

Portal modules9

Source of truth (device data)1

Role-based access with audit logRBAC

Capture

Monitor

Alert

Act

Report

Overview

Access-control terminals already recorded who entered and left each site. Technovier built a centralised management system on top of that device data: an attendance summary interface, adjustment and log reports, sign-off request handling, user and permission management, person and group entry/exit configuration and contracted hours. It was deployed to the client's server and integrates the HikCentral device data as its source of truth.

.NET Core 3.1, Microsoft SQL Server, Angular 12, Quagga2 (barcode scanning), ng-bootstrap, HikCentral device data

Problem, Constraints, Baseline, Approach, Results

Problem

Device logs lived in the access-control system; HR and management had no single place to review attendance, approve adjustments or audit changes.

Constraints

Existing Hikvision hardware had to stay in place; the portal had to respect roles and keep a log of every change; deployment was to the client's own server.

Baseline

Attendance and adjustments were handled outside the device system, with no sign-off trail.

Approach

A .NET Core API over SQL Server with an Angular front end, exposing modules for dashboard, new adjustment reports, submitted attendances, sign-off requests, log reports, users, persons, group entry/exit and contracted hours.

Results

A working centralised reporting portal deployed for the client. Attendance and adjustment workflows now run against the device data with role-based access and an audit log. Quantified time or cost savings were not measured and are not claimed.

RBAC

Role-based access with audit log

Portal modules

Source of truth (device data)

RBAC

Role-based access with audit log

Portal modules

Source of truth (device data)

RBAC

Role-based access with audit log

Key metrics shown: 9 Portal modules; 1 Source of truth (device data); RBAC Role-based access with audit log.

Challenges

1. Device data in a silo: Entry and exit records existed only inside the access-control system, unusable for attendance approval or reporting.

2. Change control for attendance: Adjustments to attendance needed a request, a sign-off and a log, not an edit in a spreadsheet.

Responses

Device data as the source of truth: The portal reads HikCentral data rather than re-keying it, so attendance summaries reflect what the terminals recorded.
Adjustment and sign-off workflow: New adjustment reports, submitted attendances and sign-off requests are separate modules with a log report behind them.
Roles, persons and groups: User permissions, person records, group entry/exit settings and contracted hours are configured in the portal, not on the devices.

Why it matters for industrial systems

This is OT/IT integration in its simplest form: a device layer that already produces reliable data, and an IT layer that turns it into governed reporting. The same shape applies to PLC, historian and sensor data.

• Read the device, don't replace it: The hardware stayed; the value came from the reporting layer built on its data.

• Auditability by design: Every adjustment carries a request, a sign-off and a log entry, the same discipline alarms and set-point changes need in a plant.

Conclusion

A centralised, role-based reporting portal built on access-control device data for a production facility. It is a direct precedent for the OT/IT integration work in Technovier's industrial practice.

Related systems