GeoWorkTrack

Article Title"GeoWorkTrack " Pankaj Tile,Abhishek Prajapati,Hitesh Patil,Sairaj Sonawane1 Department of Computer Engineering, Sandip Institute of Technology and Research Centre, Nashik, Maharashtra, India2 Department of Computer Engineering, Sandip Institute of Technology and Research Centre, Nashik, Maharashtra, India 3 Department of Computer Engineering, Sandip Institute of Technology and Research Centre, Nashik, Maharashtra, India 4 Department of Computer Engineering, Sandip Institute of Technology and Research Centre, Nashik, Maharashtra, India Department of Computer Engineering, Sandip Institute of Technology and Research Centre, Nashik, Maharashtra, India Under the guidence of : Prof. Aashish Jagneet Abstract This paper presents a GPS-based employee monitoring and attendance management system designed to automate attendance tracking, improve workforce management, and enhance employee productivity. The system utilizes real-time location tracking and geofencing techniques to monitor employee locations during office hours. It records entry and exit times, calculates attendance percentages, and detects overtime activities. The solution integrates Spring Boot, Hibernate, and Thymeleaf to create a robust web application with WebSocket for real-time updates. Results demonstrate effective tracking with minimal delays, although GPS accuracy and battery consumption remain as limitations. This system is suitable for corporate monitoring, field service management, and military applications, showcasing its versatility.Keywords: GPS tracking, employee monitoring, geofencing, real-time updates, attendance management. Introduction Employee monitoring and attendance management are critical for efficient workforce management, especially for organizations with a mobile workforce. Traditional manual methods are often prone to errors and inconsistencies, making automated solutions increasingly necessary. This project proposes a GPS-based system that tracks employee location in real-time, monitors adherence to predefined geofences, and automates attendance tracking. The technology stack includes Spring Boot, Thymeleaf, and WebSocket to create a responsive and interactive platform, supported by MySQL for data storage. This paper outlines the system architecture, algorithms, and implementation details. We evaluate its performance, identify strengths and limitations, and discuss its potential applications across various sectors, including corporate, military, and educational institutions. Materials & Methods The system will built using the following components: Hardware: Standard GPS-enabled mobile devices for location tracking. Software: Spring Boot for backend services, Thymeleaf for frontend rendering, MySQL for database management, and WebSocket for real-time communication. Methods: Geofencing Algorithm: A point-in-polygon approach is used to verify if an employee is within the geofence boundaries set by the employer. Real-Time Updates: WebSocket is employed for seamless updates on employee location. Database Management: MySQL stores user data, geofence parameters, and historical attendance records. The system automatically logs entry and exit times and calculates attendance percentages. The development process follows an iterative approach, testing each component for accuracy and performance. Performance metrics, such as GPS accuracy and response latency, were recorded to evaluate the system's effectiveness. ANALYSIS MODELS: SDLC MODEL TO BE APPLIED Agile Model: o The development follows the Agile methodology, which allows for iterative development, continuous testing, and the integration of feedback. o Each sprint focuses on developing and testing core functionalities, ensuring that the system evolves with regular improvements and meets the requirements effectively. o Sprints Overview: Sprint 1: User authentication and role-based access control. Sprint 2: Real-time location tracking and geofencing. Sprint 3: Integration of WebSocket for live communication between client and server. Sprint 4: Development of admin dashboards and reporting features. o The Agile model facilitates flexibility, allowing the development team to respond to changes and continuously refine the product based on stakeholder feedback. o SYSTEM IMPLEMENTATION PLAN The implementation plan is structured in phases, ensuring a systematic and organized approach to developing and deploying the system. · Phase 1: Develop the User Authentication Module: Implement secure login and registration for both employees and admins using role-based access. Integrate session management and user identity verification for secure access control. · Phase 2: Implement Real-Time Location Tracking and Geofencing: Develop the geofencing feature using OpenStreetMap API to create dynamic geofences. Implement location tracking functionality, ensuring real-time updates and geofence compliance monitoring. · Phase 3: Integrate Real-Time Communication Using WebSocket: Establish a WebSocket connection between client devices and the server to enable continuous, low-latency data exchange. Ensure that location updates, alerts, and notifications are synchronized in real-time. · Phase 4: Develop the Admin Dashboard for Monitoring and Reporting: Create a comprehensive admin dashboard, integrating map features and tools for viewing live employee locations, managing geofences, and generating reports. Implement reporting modules that allow admins to access historical data and analyze employee attendance and behavior patterns. Data Flow Diagrams (DFDs) Data Flow Diagrams provide a visual representation of how data moves through the system. They illustrate the processes, data stores, and external entities interacting with the system. · Level 0: High-Level Overview: The Level 0 DFD presents a high-level overview of the system, showing interactions between the primary components: Employees: Share their location data via GPS-enabled devices. Database: Stores and retrieves data such as user credentials, geofence configurations, and attendance logs. Admins: Manage the system by configuring geofences, monitoring employee locations, and generating reports. The diagram captures the basic flow of information, focusing on how employees' locations are sent to the database and monitored by admins Report Generation Process · Level 1: Detailed Data Flow: The Level 1 DFD breaks down the processes into more specific actions: Location Sharing: Employees share their GPS location, which is sent to the server through WebSocket connections. Geofence Monitoring: The system checks if an employee’s location falls within the designated geofence. Attendance Logging: When an employee enters or exits the geofence, the system logs the timestamp and calculates the presence percentage. Report Generation: Admins request reports that aggregate attendance data and display behavior patterns. This detailed flow emphasizes the sequential and concurrent processes involved in real-time monitoring, data storage, and report creation. Location Tracking Entity Relationship Diagrams (ERDs) Entity Relationship Diagrams illustrate the structure of the database and the relationships between different entities within the system. The key entities and their relationships include: · Users: Represents both Employees and Admins. The system differentiates them based on roles and permissions. Attributes include ID, name, email, role, and login credentials. · Geofences: Defines the geographical areas within which employees must remain during office hours. Attributes include ID, latitude, longitude, radius, start time, and end time. Geofences are associated with Admins, who have permissions to manage them. · Attendance Records: Stores employee attendance data, such as entry and exit times, the percentage of time spent within the geofence, and any logged overtime. Each record is linked to an Employee and a specific Geofence. · Admins: Have permissions to create and manage geofences, view employee attendance records, and generate reports. The relationship between Admins and Geofences shows the management rights and authority of each admin over the areas they supervise. This ERD provides a comprehensive view of how data entities are connected and interact within the system. ER Diagram UML Diagrams UML Diagrams provide a detailed blueprint of the system’s architecture, showing the components, their interactions, and relationships. The key UML diagrams for this system include: · Use Case Diagram: Outlines the interactions between different users (Admins and Employees) and the system: Admins: Can create geofences, monitor employee locations, and view attendance reports. Employees: Share their location data, check their geofence status, and view attendance history. The use case diagram defines the various functionalities available to each user type and the interactions necessary for managing geofences and tracking employee attendance. · Sequence Diagram: Focuses on the flow of data and actions between system components for key operations: Location Tracking: Shows the sequence of data flow from employee devices to the server, how the server processes the location, and updates the database. Report Generation: Details how an admin requests a report, the system retrieves data from the database, and the report is generated and displayed. This diagram provides a step-by-step illustration of how system components work together to achieve each task. · Class Diagram: Outlines the core classes within the system and their relationships, including: Employee: Attributes include ID, name, role, and methods for location sharing. Adm