Skip to content
View cota7's full-sized avatar

Block or report cota7

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
cota7/README.md

Biometric Attendance & Offsite Productivity System

1. Project Overview

Objective: Implement a dual-system solution that accurately tracks attendance and working hours for 70 onsite staff via facial recognition, while simultaneously monitoring the actual productivity and activity of 10 offsite workers to prevent unnecessary overtime costs.

Scope:

  • Onsite: Hardware supply, installation, and biometric registration for 70 employees.
  • Offsite: Software deployment for 10 remote workers to track activity and productivity.
  • Admin: Centralized dashboard for reporting and management.

2. Phase 1: Onsite Biometric Attendance System (70 Users)

Goal: Replace manual or insecure check-ins with a frictionless facial recognition system at the entrance.

A. Hardware & Installation

  • Device Procurement: Supply of a high-capacity facial recognition terminal (supports 70+ users with local storage or cloud sync).
  • Installation: Mounting the device at the main entrance, configuring power and network connectivity (Ethernet/Wi-Fi).
  • Setup: Configuration of the device IP, server connection, and time zone settings.

B. User Registration

  • Enrollment Drive: Capture high-quality facial data for all 70 employees.
  • Profile Creation: Assigning unique IDs, names, and department tags to each user.
  • Testing: Live test runs to ensure recognition speed and accuracy during peak arrival times.

C. Attendance Logic

  • Check-In/Check-Out: Employees simply look at the device upon arrival and departure.
  • Data Sync: Real-time transmission of attendance logs to the central admin software.
  • Working Hours Calculation: Automatic calculation of total hours worked per day/week.

3. Phase 2: Offsite Productivity & Activity Tracking (10 Users)

Goal: Monitor actual work activity for remote staff and eliminate "ghost" overtime caused by idle systems being left on.

A. Software Deployment

  • Agent Installation: Install lightweight tracking software on the 10 offsite workers' desktops/laptops.
  • Configuration: Set up individual profiles for the offsite team.

B. Activity Monitoring Features

  • Active vs. Idle Time: The system must distinguish between system active (screen on) and user active (mouse/keyboard input).
  • Application Usage: Track which apps are being used (e.g., Excel vs. YouTube).
  • Screenshots (Optional): Periodic random screenshots for verification of work.
  • Productivity Scoring: Categorize apps/websites as "Productive," "Neutral," or "Unproductive."

C. Overtime Control Logic

The Requirement: Overtime must only be counted when actual work is being performed, not just when a system is left on.

The Solution:

  • Idle Detection: If the user is idle for more than X minutes (e.g., 10 mins), the system stops counting "Work Time" even if the computer is on.
  • Active Work Overtime: Overtime will only be calculated when there is active input and productive application usage after hours.
  • Auto-Logout/Shutdown (Optional): Configure the system to alert the admin if a machine is left on and idle for extended periods.

4. Phase 3: Centralized Admin & Reporting

Goal: Provide management with a single view of both onsite and offsite workforce data.

A. Admin Dashboard

  • Onsite View: Real-time presence (who is in the building right now).
  • Offsite View: Real-time status (who is active, who is idle).
  • Attendance Reports: Daily, weekly, and monthly attendance sheets for onsite staff.

B. Productivity Reports

  • Daily/Weekly Reports: Automated reports generated for the 10 offsite workers.
  • Actual Hours Worked: Reports will show "Total Hours Logged In" vs. "Total Active Productive Hours."
  • Overtime Audit: A specific report highlighting overtime claims that were flagged as "Idle" or "Low Activity" to prevent fraudulent payouts.

5. Implementation Timeline (Estimated)

Week Milestone
Week 1 Procurement of hardware and software licenses.
Week 2 Onsite installation and configuration of biometric device.
Week 3 Enrollment of 70 onsite staff (facial registration).
Week 4 Installation of offsite tracking agents on 10 machines.
Week 5 Admin training and system handover.

6. Deliverables

  • 1x Facial Recognition Terminal (installed & configured).
  • 70x Registered user profiles.
  • 10x Offsite productivity tracking licenses (installed).
  • 1x Admin management system (web-based or desktop).
  • Automated reporting system for attendance and overtime.

7. Success Criteria

  • Onsite: 100% of staff registered and using facial check-in daily.
  • Offsite: Accurate distinction between "System On" and "User Working."
  • Financial: Reduction in unnecessary overtime payouts by identifying idle time after hours.

Popular repositories Loading

  1. cota7 cota7 Public

  2. KalahariPulse KalahariPulse Public

    Forked from HiEventsDev/Hi.Events

    Open-source event management and ticket selling platform — perfect for concerts, conferences, and everything in between 🎟️ If you find this project helpful, please consider giving us a star ⭐️

    PHP