Rule engine-based attendance checking method and system and storage medium

Abstract

The invention discloses an attendance checking method and system based on a rule engine and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: establishing an attendance standard data model based on a rule engine in a B / S (Browser / Server) architecture, and outputting attendance information to a target management system in response to a trigger event by the standard data model by taking multi-source data as input; wherein on the basis of the rule engine, the formats of the multi-source data are unified to adapt to the standard data model, and the format of the attendance information is changed to adapt to the target management system. The attendance checking method can effectively solve the technical problems of difficulty in function expansion, high data processing cost, easiness in making mistakes and low iterative maintenance efficiency of an attendance checking method in related technologies, can also effectively solve the problems of poor scene adaptability and poor abnormal management and control capability, and meets the new requirements of enterprise attendance checking management.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to an attendance method, system, and storage medium based on a rule engine. Background Technology

[0002] With the digital transformation of enterprises, the expansion of organizational scale, and the diversification of work scenarios, driven by both organizational expansion and the normalization of hybrid work models, existing systems have exposed systemic bottlenecks such as rigid architecture, low intelligence, and insufficient collaboration efficiency. Most existing systems adopt a monolithic architecture design with high coupling between functional modules, making it difficult to quickly respond to personalized enterprise needs. Modifying attendance rules or integrating with external systems (such as OA and mobile terminals) requires deep modifications to core code, resulting in long development cycles and high maintenance costs. Simultaneously, the phenomenon of data silos across systems is severe, with attendance data modification and approval processes relying on manual synchronization, which is not only inefficient but also prone to errors in attendance statistics due to human error. Furthermore, attendance systems only allow viewing and use by the responsible personnel; employees cannot view their own attendance status, making it difficult for many companies to implement attendance tracking for hybrid scenarios such as remote work and field attendance. In terms of data verification, traditional attendance systems only have the function of displaying attendance-related data and lack intelligent early warning capabilities, making it difficult to detect attendance anomalies in a timely manner, thus exacerbating the risks of enterprise human resource management.

[0003] For attendance systems employed in related technologies, conventional attendance systems are highly coupled, requiring data integration with scheduling systems, office automation systems (OA systems), mobile attendance systems, access control / turnstile systems, and human resources systems to achieve accurate attendance records. They also need to export data to performance management systems, welfare management systems, payroll management systems, job level management systems, and tax filing systems for functions such as payroll calculation, welfare statistics, performance evaluation, and tax filing. The scheduling system needs to define attendance rules, attendance teams, leave rules, and holiday / workday adjustments, and synchronize this information to the attendance system to schedule get off work hours and personnel. The office automation system is responsible for submitting and approving processes for business trips, leave, workday adjustments, and missed attendance, and synchronizing this process information to the attendance system to prevent attendance discrepancies. Mobile attendance terminals are responsible for remote business trips and fieldwork attendance, synchronizing attendance information to the attendance system to prevent attendance discrepancies. The access control / turnstile system is responsible for local office attendance attendance, synchronizing attendance information to the attendance system to prevent attendance discrepancies. The human resources management system needs to synchronize basic information such as employee name, employee number, and department to the attendance system for information exchange related to employee onboarding, offboarding, and job transfer.

[0004] Based on the above technical solution, the following drawbacks exist: 1) Outdated system architecture and poor flexibility in functional expansion: The system adopts a monolithic architecture with highly coupled functional modules. The attendance system has complex dependencies on other systems, and the systems connect through customized interfaces. Each new system requires a separate adaptation layer to be developed. This results in poor compatibility when the system is expanded.

[0005] 2) High labor costs for the attendance system: Data isolation between various business systems is severe, and the modification and approval process for attendance data requires manual intervention for data synchronization. This manual operation mode is not only inefficient, but also prone to errors and omissions in attendance statistics due to human error, significantly increasing human resource management costs.

[0006] 3) Long system development and maintenance cycle and high threshold: The system modules are highly coupled. When adding a new attendance module (such as field work management and flexible working hours), the core code needs to be reconstructed. This model leads to a long function iteration cycle, high system deployment and maintenance costs, and seriously restricts the continuous optimization and upgrading of the system.

[0007] 4) Lack of access control mechanism hinders system intelligence: The existing system only grants access to attendance management personnel, failing to provide personalized data pushes based on the actual needs of different managers. Ordinary employees cannot independently check their personal attendance status. This closed access control model not only limits the system's intelligence level but also poses security risks.

[0008] 5) Weak support for hybrid office scenarios: The system mainly relies on physical attendance devices in fixed locations and lacks technical support for mobile office scenarios. This singular attendance method cannot meet the needs of modern hybrid office work such as remote work and field attendance, which seriously restricts the flexible employment management of enterprises.

[0009] 6) Insufficient intelligence affects system stability: The existing system only provides basic attendance data display functions and lacks an intelligent anomaly warning mechanism. This technical deficiency makes it difficult for the system to detect and handle attendance anomalies in a timely manner, which not only affects management efficiency but also reduces the overall stability of the system.

[0010] Therefore, the attendance systems and methods described above are insufficient to meet the attendance management needs of enterprises as their organizational scale expands and work scenarios become more diversified. Summary of the Invention

[0011] The purpose of this invention is to provide an attendance method, system, and storage medium based on a rule engine. This attendance method can effectively solve the technical problems of difficult function expansion, high data processing cost and easy error, and low iteration and maintenance efficiency in related technologies. At the same time, it can also effectively solve the problems of poor scenario adaptability and lack of abnormal control capabilities, thus meeting the new needs of enterprise attendance management.

[0012] To address the aforementioned technical problems, in a first aspect, embodiments of the present invention provide an attendance method based on a rule engine, comprising the following steps: within a B / S architecture, establishing a standard data model for attendance based on a rule engine, wherein the standard data model takes multi-source data as input and outputs attendance information to a target management system in response to a triggering event; wherein, based on the rule engine, the format of the multi-source data is unified to adapt to the standard data model, and the format of the attendance information is changed to adapt to the target management system.

[0013] Optionally, the target management system includes one or more of the following: performance management system, welfare management system, payroll management system, job level management system, and tax declaration system; and / or, the sources of the multi-source data include, but are not limited to, office automation systems, mobile attendance terminals, access control / turnstile systems, and human resource management systems.

[0014] Optionally, the standard data model is used to perform the following steps: establishing attendance rules, configuring corresponding attendance rules for users according to user levels; calculating and summarizing attendance information for each user level within at least one preset time period based on the multi-source data and the attendance rules; and displaying attendance information below the current user level in response to the current user's request.

[0015] Optionally, the standard data model is further used to perform the following steps: establishing an attendance whitelist, which stores multiple user information; and when the information of the current user is identified to be consistent with the user information, not configuring the attendance rules and / or not calculating the attendance information.

[0016] Optionally, the attendance information includes, but is not limited to, personal attendance records, leave records, business trip records, time off records, future absence plans, attendance exception prompts, and user information.

[0017] Optionally, before displaying the attendance information below the current user level, the method further includes the following steps: assigning the attendance information corresponding to the user level to the auditor based on the audit level; and in response to the current auditor's audit completion instruction, transferring the modified or unmodified attendance information to the auditor of the previous audit level, using the auditor of the previous audit level as the current auditor, repeating the above process until the auditor of the highest audit level completes the audit.

[0018] Optionally, the standard data model is further used to perform the following steps: configuring corresponding usage permissions for the user according to the user level, the usage permissions including but not limited to viewing, modifying, and adding the attendance rules and / or the attendance information and / or the multi-source data and / or the attendance whitelist; and / or configuring corresponding audit permissions for the auditor according to the audit level, the audit permissions including but not limited to modifying and auditing the attendance information.

[0019] Optionally, the standard data model is also used to perform the following steps: in response to the current user's request, within the same user level, displaying the attendance information that is abnormal, under review, or modified in different colors.

[0020] Secondly, embodiments of the present invention provide an attendance system based on a rule engine, the system comprising: a memory storing instructions; and a processor that invokes the instructions in the memory to enable the system to implement the attendance method described above.

[0021] Thirdly, embodiments of the present invention provide a computer-readable storage medium storing instructions, wherein the instructions, when executed by a processor, implement the attendance method described above.

[0022] Through the above technical solutions, the present invention can effectively solve the technical problems of difficult function expansion, high data processing cost and easy error, and low iteration and maintenance efficiency in related technologies. At the same time, it can also effectively solve the problems of poor scenario adaptability and lack of abnormal control capabilities, thus meeting the new needs of enterprise attendance management.

[0023] Other features and advantages of the embodiments of the present invention will be described in detail in the following detailed description section. Attached Figure Description

[0024] The accompanying drawings are provided to further illustrate embodiments of the present invention and form part of the specification. They are used together with the following detailed description to explain the embodiments of the present invention, but do not constitute a limitation thereof. In the drawings: Figure 1 This is a schematic diagram of the attendance method based on a rule engine provided in an embodiment of the present invention; Figure 2 This is a schematic diagram of a data interaction architecture based on a rule engine provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the functional module architecture of the attendance system based on the rule engine provided in an embodiment of the present invention; Figure 4 This is a block diagram of a rule engine-based attendance grading and review mechanism provided in an embodiment of the present invention.

[0025] Figure 5 This is a schematic diagram of the full-process hierarchical architecture of the attendance method based on the rule engine provided in the embodiment of the present invention.

[0026] Explanation of proper terminology OA: Office Automation, Office Automation System B / S: Browser / Server architecture Detailed Implementation The specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the scope of the present invention.

[0027] It should be noted that the acquisition, transmission, storage, use, and processing of data in the technical solution of this application all comply with relevant laws and regulations. In the embodiments of this application, certain existing industry solutions such as software, components, and models may be mentioned. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solution of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0028] Method Implementation Examples Figure 1 This is a schematic diagram of the attendance method based on a rule engine according to an embodiment of the present invention, such as... Figure 1 As shown, this step includes steps S102-S104: Step S102: Within the B / S architecture, establish a standard data model for attendance based on the rule engine. The standard data model takes multi-source data as input and outputs attendance information to the target management system in response to triggering events. Specifically, the rule engine can be a visual low-code programming tool with a rich component library covering multiple fields such as the Internet of Things, network communication, data processing, and storage. It can simplify JavaScript writing in a graphical way, enabling low-code development of the attendance system, lowering the development threshold, and thus reducing the development cycle and achieving low-code development. The standard data model can be used to perform the following steps S1001-S1003 to generate and manage attendance information: Step S1001: Establish attendance rules and configure corresponding attendance rules for users according to their user levels.

[0029] In this embodiment, the user, who may be a super administrator, performs the creation and configuration of rules in the system's attendance rules module. The attendance rules are a complex system, and their creation and configuration process is as follows: First, the administrator configures and enables attendance shifts on the shift management page. Each attendance shift defines the regular clock-in time, rest time, and whether flexible clock-in is allowed, along with the specific flexible clock-in time period. Simultaneously, the administrator sets specific business rules on the attendance rules configuration page, such as overtime rules (e.g., overtime start time and calculation method) and make-up clock rules (e.g., the number of make-up clocks allowed per month and application deadline). Then, the administrator creates and manages attendance groups on the attendance group management page to implement a differentiated attendance mechanism. Each attendance group is a complete rule package, bound to the specific attendance shifts, clock-in methods, and overtime and make-up clock rules configured above. The core of this step is configuring corresponding attendance rules for users based on their user level. Specifically, when creating an attendance group, the administrator must select the employees to whom the attendance group applies. Options include: apply to all employees, apply to employees in a specific department (e.g., configuring flexible work shifts for the "R&D Department"), or apply to certain employees (customizing rules for specific individuals or positions). Through this operation, employees in different departments and positions (i.e., different "user levels") are associated with a set of rules that are appropriate to their job characteristics.

[0030] It should be noted that only users have viewing and editing permissions for the attendance rules module. Company leaders only have viewing permissions, while other personnel do not have access, thus ensuring the centralization and security of rule configuration.

[0031] Step S1002: Based on multi-source data and attendance rules, calculate and summarize the attendance information of each user level within at least one preset time period.

[0032] In this embodiment, after the rule configuration based on step S1001 is completed, the system enters the automated data processing stage: the system continuously receives multi-source data through the data import module based on the rule engine. This data includes original attendance records from mobile attendance terminals and access control / turnstile systems, as well as approved business trips, leave requests, time off in lieu, and missed attendance process data from the office automation system (OA). This data, combined with departmental user information (employee name, employee ID, department, etc.) synchronized from the human resources management system, constitutes the original basis for calculation; then, the system matches and calculates the original data according to the attendance group rules configured for each employee in step S1001, automatically determining the daily attendance status (such as normal, late, early departure, absenteeism, etc.). The calculation results are summarized and displayed on the daily statistics page of the attendance statistics module. During this process, the system's built-in intelligent alert mechanism for anomalies is triggered, including: for calculated abnormal attendance data (such as lateness, early departure, absenteeism, or logically conflicting processes), the system highlights the attendance date, employee name, and abnormal fields in red on the page; for pending confirmation data submitted by employees but not yet approved in the OA process (such as leave applications), the relevant fields are marked in yellow; data manually adjusted by the attendance clerk is marked in green, and normal attendance data is not marked with any special color. The system further summarizes the daily statistics on the monthly statistics page, forming structured attendance information at the individual, department, and company levels, including attendance records, anomaly records, and various process records. The designed intelligent alert mechanism for anomalies helps attendance clerks quickly identify abnormal attendance, significantly improving the efficiency of attendance review while reducing system operating costs.

[0033] Step S1003: In response to the current user's request, display the attendance information of users below the current user's level.

[0034] In this embodiment, when a user logs into the system and sends a viewing request, the system identifies their position and management scope (i.e., "user level"). Further, steps S1001-S1003 include: the standard data model is also used to perform the following steps: establishing an attendance whitelist, which stores information on multiple users; and when the current user's information matches the user information, not configuring attendance rules and / or not calculating attendance information. The attendance system adds a whitelist function and supports multiple attendance modes for different scenarios: For diverse work scenarios within an enterprise, such as office work, remote work from home, and business trips, the attendance system has an adaptive attendance mode for different scenarios. In the office scenario, it supports multiple biometric methods such as facial recognition and fingerprint recognition for clocking in; in the remote work scenario, attendance can be comprehensively determined through data such as VPN login records and usage time of work-related software; during business trips, attendance management is conducted using GPS positioning technology combined with business trip approval information. The system automatically switches to the appropriate attendance mode based on the employee's current work scenario to ensure the accuracy and convenience of attendance.

[0035] In establishing attendance rules and selecting applicable employees based on user level (department / position), while completing the differentiated configuration of the rules, the standard data model also performs the following steps: establishing an attendance whitelist, which stores information on multiple users; and in the process of calculating and summarizing the attendance information of each user level within at least one preset time period, the following steps are also included: when the information of the current user is identified as consistent with the user information, no attendance rules are configured and / or attendance information is not calculated.

[0036] For steps S1001-S1003, the attendance information includes, but is not limited to, personal attendance records, leave records, business trip records, time off records, future absence plans, attendance exception prompts, and user information.

[0037] Furthermore, based on the user level, corresponding usage permissions are configured for the user, including but not limited to viewing, modifying, and adding attendance rules and / or attendance information and / or multi-source data and / or attendance whitelists; and / or based on the review level, corresponding review permissions are configured for the reviewer, including but not limited to modifying and reviewing attendance information.

[0038] Furthermore, in response to the current user's request, within the same user level, the attendance information that is abnormal, under review, or modified is displayed in different colors.

[0039] Step S104, wherein, based on the rule engine, the multi-source data format is unified to adapt to the standard data model, and the format of attendance information is changed to adapt to the target management system.

[0040] Specifically, the multi-source data format refers to the data format between different systems. In this step, based on the rule engine, not only can data from different sources and in different formats be converted into a unified format that the standard model can understand, but the results processed by the standard model can also be converted into specific formats that can be received by different target systems.

[0041] Furthermore, the target management system includes one or more of the following: a performance management system, a benefits management system, a payroll management system, a job level management system, and a tax declaration system; and / or, the sources of multi-source data include, but are not limited to, office automation systems, mobile attendance terminals, access control / turnstile systems, and human resource management systems. The target management system (attendance system) designed in this solution is based on microservice technology. Attendance-related modules are developed independently and customized according to the needs of different enterprises, improving the system's maintainability and scalability, and easily adapting to new needs and changes in the future development of enterprises. Simultaneously, the B / S architecture of microservice technology ensures that the system modules are independent, with low coupling, resulting in efficient system deployment and maintenance. When adding new functional modules, only the code for that module needs to be developed, without extensive code modifications, reducing the development cycle and greatly improving the system's scalability and stability. It should be noted that, Figure 2 This is a schematic diagram of a data interaction architecture based on a rule engine provided in an embodiment of the present invention, such as... Figure 2 As shown in the diagram, this data interaction architecture includes data integration modules for departmental user information, attendance information, and various OA processes; a low-code personalized attendance system; and a data integration module for attendance data export. This data interaction architecture is a B / S architecture based on microservices technology, featuring multi-replica deployment capabilities. The modules within the microservices architecture are loosely coupled, allowing for independent development and deployment of new functional modules without requiring large-scale adjustments to the entire system. During peak usage periods for a particular module of the attendance system, such as clocking in and out, server resources can be increased or optimized for that service without affecting the operation of other services. Since each module is an independent unit, maintaining, updating, or repairing one service will not affect the normal operation of other services. For example, when modifying the leave approval process in the attendance system, only the module responsible for leave approval needs adjustment, while functions such as employee clocking in and out and attendance data statistics remain functional, greatly improving the system's scalability and stability.

[0042] Furthermore, a rule engine is employed to facilitate data interaction between systems. Based on the data formats and business logic of different systems, two data integration modules were designed: a data import module that connects in real-time to various processes of the OA system, mobile attendance terminals, and access control / turnstile systems; and a module that imports departmental employee information from human resources in a single step, updating data on employee changes such as onboarding, offboarding, and job transfers in real-time. Once attendance data is approved, a rule engine-based data export module transforms it into the required data formats for different systems, enabling functions such as performance appraisal, welfare statistics, payroll processing, and tax filing. When a new system needs to be integrated, no core code modification is required. A unified module for system integration can be built using only drag-and-drop graphical operations and minimal code writing. This reduces the strong coupling between systems, shortens the system development cycle, and achieves unified information management of employee attendance data for the enterprise. In addition, by using a rules engine to build a unified data interface module (data export module), the attendance system is deeply integrated with the OA system, mobile check-in terminals, facial recognition terminals, personnel information storage terminals, etc., to achieve comprehensive and centralized information management of the attendance data of the organization's personnel, break down data silos, ensure data consistency and accuracy, and provide solid data support for the company's human resource management.

[0043] For the above steps S102-S104 and the overall steps included therein Figure 3 This is a schematic diagram of the functional module architecture of a rule engine-based attendance system provided in an embodiment of the present invention, as shown below. Figure 3 As shown in the diagram, the attendance system's functional module architecture comprises three parts: the homepage, the attendance management module, and the user management module. The attendance system features a flexible and granular permission configuration mechanism, including job-specific and role-based permission configuration mechanisms. Based on different permission settings, personalized page content is displayed to users. The homepage includes four pages: Workbench, Personnel Schedule, Subordinate Attendance, and My Attendance.

[0044] The workbench displays overall company attendance statistics and macro-level data such as attendance rate comparisons across departments. The personnel schedule displays the attendance, business trips, and leave information for all levels of management this month, and also allows viewing planned business trips or time off in lieu. Subordinate attendance allows viewing detailed attendance statistics for employees in management departments for the current month. "My Attendance" displays employees' monthly attendance records, attendance exceptions, business trip records, and time off in lieu records. The designed job-specific permission configuration mechanism allows the attendance system to personalize the homepage module display.

[0045] For company-level managers, there are four homepages: Workbench, Staff Schedule, Subordinate Attendance, and My Attendance. They can view detailed attendance information for all employees and attendance statistics for each department, allowing them to strategically manage the company's workforce attendance. For department-level managers, there are three homepages: Staff Schedule, Subordinate Attendance, and My Attendance. They can view detailed attendance information for employees in their department, facilitating internal attendance management. Regular employees can view their personal attendance records, remaining leave days, and other closely related information on the My Attendance page.

[0046] The attendance rules module comprises three pages: Attendance Group Management, Shift Management, and Attendance Rules Configuration. Due to the implementation of a permission configuration mechanism, the super administrator has viewing and editing permissions for the attendance rules module; company-level leaders have viewing permissions; other personnel do not have access to the attendance rules module. The Attendance Group Management page implements a differentiated attendance mechanism, allowing users to add multiple attendance groups and select currently active groups. Each attendance group is bound to an attendance shift, check-in method, and attendance rules, and users can select the employees to whom the attendance group applies—either all employees, employees in specific departments, or certain employees. The Shift Management page allows users to configure and enable attendance shifts, which include information such as regular check-in time, rest time, whether flexible check-in is allowed, and flexible check-in time periods. The Attendance Rules Configuration page includes overtime rules and make-up check-in rules.

[0047] The attendance management module includes three sections: Department Users, Attendance Statistics, and Whitelist. The Department Users section displays detailed employee information such as name, employee ID, and department. The Attendance Statistics module comprises nine pages: Daily Statistics, Monthly Statistics, Clock-in Records, Leave Records, Missed Clock-in Records, Domestic Business Trip Records, Local Business Trip Records, International Business Trip Records, and Holidays. The Daily Statistics page displays detailed attendance records for each department employee, including clock-in, leave, business trips, and time off in lieu. For the daily statistics page, this invention designs an intelligent early warning mechanism for anomalies. For abnormal attendance data, the attendance date, employee name, and fields indicating attendance anomalies (e.g., lateness, early departure, absenteeism, or submitting both business trip and time off procedures on the same day) on the daily statistics page are displayed in red to remind the attendance clerk to verify. For employees who have submitted business trip, missed sign-in, time off, and leave procedures but have not yet completed the approval process, the data to be confirmed is displayed in yellow to remind the attendance clerk to confirm. Data that has been manually adjusted by the attendance clerk is marked in green. Normal attendance data has no color marking. That is, when multi-source data does not meet the attendance rules, the attendance information is displayed in red fields; manually modified attendance information is displayed in green fields; and attendance information corresponding to unapproved leave procedures is displayed in yellow fields.

[0048] It should also be noted that, Figure 4This is a block diagram of a rule-engine-based tiered attendance review mechanism provided in an embodiment of the present invention. To optimize the aforementioned attendance management, a tiered review topic is designed within the tiered attendance review mechanism to ensure the accuracy of attendance data. For example... Figure 4 As shown, the tiered attendance verification mechanism is divided into four levels: department attendance clerk, department head, company attendance clerk, and company administrator. Department attendance clerks are responsible for reviewing and modifying the attendance data of their department's employees and submitting it to the department head level. The department head confirms the data reviewed by the department attendance clerk and submits it to the company attendance clerk level. The company attendance clerk summarizes and reviews the attendance data of all employees and submits it to the company administrator level. The company administrator is responsible for confirming the final attendance data.

[0049] In the review mechanism, higher-level authorities have higher authority than lower-level authorities. When data is reviewed outside the designated level, lower-level authorities cannot perform any operations on the attendance data unless the higher-level authority returns the data to the next lower level. When data is returned, it can be returned to the previous level or directly to the department attendance clerk level. For example, after the company attendance clerk reviews the data, department attendance clerks and department heads do not have the authority to modify the data unless the company attendance clerk returns the attendance data to the department head or department attendance clerk level.

[0050] By combining a permission configuration mechanism and a tiered attendance review mechanism, the security and accuracy of attendance data are ensured. Department attendance clerks and department heads can view, modify, and review the attendance data of employees within their respective departments; company attendance clerks and company administrators can view, modify, and review the attendance data of all company employees; other employees in management positions without assigned attendance roles can view the detailed attendance data of their subordinates, but cannot modify the attendance data.

[0051] The monthly statistics page is a summary of detailed attendance data from the daily statistics page. A tiered attendance review mechanism is applied to the monthly statistics page. Department attendance clerks and department heads can summarize and view the monthly attendance data of their department's employees; company attendance clerks and company administrators can view, summarize, and export the monthly attendance data of all company employees.

[0052] Clock-in records, leave records, missed clock-in records, domestic business trip records, intra-city business trip records, and international business trip records are integrated into the attendance system via a data import module, assisting attendance auditors in reviewing attendance data. The tiered attendance review mechanism also incorporates these six pages. Department attendance clerks and department heads can view the clock-in and OA process data of their department's employees; company attendance clerks and company administrators can view the clock-in and OA process data of all company employees. The holidays page displays all statutory holidays and holiday adjustment information for the year, allowing employees to plan their work and life in advance, ensuring efficient work and a well-ordered life. The whitelist module allows adding company administrators exempt from clocking in to prevent attendance irregularities. The attendance system's access control mechanism allows super administrators to view, add, and delete whitelisted personnel; company administrators only have viewing permissions, and other personnel cannot access this page.

[0053] The user management module includes three pages: user information, role configuration, and job configuration. The attendance system designed in this invention only allows the super administrator to view and modify the content of these pages. The user information page contains the login accounts, names, departments, and management departments of all company employees in the attendance system, as well as employee permission information. The super administrator can configure role information, job information, and management departments on this page. When a user forgets their password, the super administrator can reset it on this page. The super administrator can view and create roles and configure different page permissions for each role on the role configuration page. The super administrator can view and create jobs and configure different page permissions for each job on the job configuration page.

[0054] It should be noted that a four-tiered attendance review system is established, comprising department attendance clerks, department heads, company attendance clerks, and company administrators, with clearly defined permissions and responsibilities for each role. Department attendance clerks are responsible for the initial review and editing of their department's daily attendance data, and for verifying and handling attendance anomalies such as employee leave and business trips. Department heads can conduct a secondary review of the data submitted by their department attendance clerks and are responsible for the accuracy and compliance of their department's attendance data. Company attendance clerks can view and review company-wide attendance data and handle cross-departmental attendance issues. Company administrators ensure the accuracy and compliance of all employee attendance data. This tiered review mechanism not only distributes the workload of attendance review, avoiding an overburdened single-person review task, but also improves the accuracy and reliability of attendance data through multi-level review and verification, ensuring the rigor and fairness of attendance management.

[0055] Furthermore, Figure 5 This is a schematic diagram of the full-process hierarchical architecture of the rule engine-based attendance method provided in this embodiment of the invention, as shown below. Figure 5 As shown, the process mainly includes four steps: data access, attendance configuration, permission configuration, and attendance approval. The steps are as follows: First, through a rules-based data import module, departmental user information, employee mobile or facial recognition check-in information, and OA process information are synchronized from the human resources management system, mobile check-in terminals, access control / turnstile system, and office automation system to the attendance system. This process ensures accurate integration of multi-source data, providing a comprehensive and reliable data foundation for subsequent attendance management.

[0056] Secondly, the super administrator configures attendance rules, attendance shifts, and attendance groups in the attendance management module to set up scheduling rules such as clock-in rules, overtime rules, and make-up clock rules for the attendance system, thereby building a standardized attendance management system to adapt to different work scenarios and needs.

[0057] Then, the super administrator configures role permissions and job permissions in the user management module, and adds roles and jobs to users. This operation enables the attendance system to display personalized page content to different users based on the hierarchical permission mechanism, effectively ensuring the security and targeting of system operations, and ensuring that each user can only access and operate functions and data that match their permissions.

[0058] Finally, whitelisted personnel are added to the attendance management module, and attendance data is meticulously reviewed based on a tiered attendance approval mechanism, OA processes, and abnormal attendance alerts. This rigorous review process effectively ensures the accuracy and stability of attendance data, providing a reliable basis for enterprise human resource management decisions.

[0059] System Implementation Examples This invention also provides an attendance system based on a rule engine. The system includes: a memory storing instructions; and a processor that invokes the instructions in the memory to enable the system to implement the attendance method described above.

[0060] This invention also provides a machine-readable storage medium storing instructions that, when executed by a processor, implement the attendance method described above.

[0061] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0062] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0063] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0064] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0065] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0066] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0067] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0068] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0069] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. An attendance method based on a rule engine, characterized in that, Includes the following steps: Within the B / S architecture, a standard data model for attendance is established based on a rule engine. This standard data model takes multi-source data as input and outputs attendance information to the target management system in response to triggering events. Specifically, based on the rule engine, the multi-source data format is unified to adapt to the standard data model, and the format of the attendance information is changed to adapt to the target management system.

2. The attendance method based on a rule engine according to claim 1, characterized in that, The target management system includes one or more of the following: performance management system, welfare management system, payroll management system, job level management system, and tax declaration system; and / or, the sources of the multi-source data include, but are not limited to, office automation system, mobile attendance terminal, access control / turnstile system, and human resource management system.

3. The attendance method based on a rule engine according to claim 1, characterized in that, The standard data model is used to perform the following steps: Establish attendance rules and configure corresponding attendance rules for users based on their user levels; Based on the multi-source data and the attendance rules, calculate and summarize the attendance information of each user level within at least one preset time period; as well as In response to the current user's request, display the attendance information for users at or below the current user's level.

4. The attendance method based on a rule engine according to claim 3, characterized in that, The standard data model is also used to perform the following steps: An attendance whitelist is established, which stores information on multiple users; and If the current user's information is found to be consistent with the user information, the attendance rules are not configured and / or the attendance information is not calculated.

5. The attendance method based on a rule engine according to claim 3, characterized in that, The attendance information includes, but is not limited to, personal attendance records, leave records, business trip records, time off records, future absence plans, attendance exception prompts, and user information.

6. The attendance method based on a rule engine according to claim 1 or 3, characterized in that, Before displaying the attendance information below the current user level, the following steps are also included: The attendance information is assigned to the reviewer according to the corresponding user level based on the review level; and In response to the current auditor's completion instruction, the modified or unmodified attendance information is transferred to the auditor at the next higher level. The auditor at the previous level is then used as the current auditor, and the above process is repeated until the auditor at the highest level completes the review.

7. The attendance method based on a rule engine according to claim 6, characterized in that, The standard data model is also used to perform the following steps: Configure corresponding usage permissions for the user according to the user level. The usage permissions include, but are not limited to, viewing, modifying, and adding the attendance rules and / or the attendance information and / or the multi-source data and / or the attendance whitelist. and / or Configure corresponding review permissions for the reviewer according to the review level. The review permissions include, but are not limited to, modifying and reviewing the attendance information.

8. The attendance method based on a rule engine according to claim 6, characterized in that, The standard data model is also used to perform the following steps: In response to the current user's request, within the same user level, the attendance information that is abnormal, under review, or modified is displayed in different colors.

9. An attendance system based on a rule engine, characterized in that, The system includes: A memory, wherein instructions are stored; and A processor that invokes the instructions in the memory to cause the system to implement the attendance method as described in any one of claims 1 to 8.

10. A computer-readable storage medium storing instructions thereon, characterized in that, When the instruction is executed by the processor, it implements the attendance method as described in any one of claims 1 to 8.

Images