Existing database integration
The application consumes data from the current system without changing how physical attendance devices operate.
- SQL Server
- employees and events
- direct read integration
- consistency checks
CASE / TIME / WEB
LEGACY INTEGRATION / BUSINESS APP
Time attendance for about 300 employees — without replacing the existing infrastructure.
A web application that reads from an existing time-attendance system and gives managers clear, role-based access to working-time data without direct use of the source application.
CONTEXT
The data already existed; secure and usable manager access did not.
The source was an operational time-attendance system backed by SQL Server with roughly 300 employees. The goal was not to replace it, but to add a modern presentation and reporting layer.
Managers needed access only to their assigned organizational units, with calculations for first entry, last exit, working-time norms, overtime-like balances and absences.
Roles and data scope
Managers see only assigned units, while administration controls access and settings.
- Admin
- Manager
- Operator
- organizational scope
Working-time logic
The system calculates first entry, last exit, norms and balances, with explicit handling for absences and the current day.
- entry / exit
- norm
- balance
- absences
Reporting and exceptions
PDF reports and exception markers reduce manual searching for incomplete or inconsistent data.
- HR / manager PDF
- employee report
- unexplained time
- weekends
ENGINEERING TAKEAWAYS
Key lessons from the implementation.
- A source system does not always need replacement; a well-designed integration layer can deliver the required business value.
- Data permissions should reflect organizational responsibility.
- Working-time calculations must model exceptions explicitly.
- Screen and PDF reporting should share the same calculation source to prevent inconsistencies.
CASE / NEXT
SIMILAR ENVIRONMENT?
Discuss the environment