JP7765025B2 - Construction Management System - Google Patents

Description

The present invention relates to the field of construction management, and in particular to construction management systems.

The construction industry is an important backbone of the national economy and one of the main channels for labor employment. To better manage construction workers, worker management platforms have been introduced. Many of these management platforms operate based on a strategy of "real-name system + facial recognition attendance + wage payment based on payroll." However, this management method relies solely on attendance data or manually uploaded data and often lacks other evidence, making it impossible to ensure the authenticity and reliability of the data or to detect potential risks in attendance data or manually uploaded data.

Therefore, there is a demand for a construction management system that enables better construction management.

A construction management system according to one or more embodiments of the present invention includes a report acquisition module arranged to acquire input reports including at least a task list and a time attendance record; a report check module arranged to check the input reports; and a report determination module arranged to determine target reports including at least one of a target attendance record and a target pay slip based on the checked input reports.

The present invention will be further explained by way of exemplary embodiments, which are illustrated in detail in the drawings, and are not intended to be limiting, and in which the same reference numerals denote the same structures.
1 is a diagram showing an application scene of a construction management system according to some embodiments of the present invention; 1 is a block diagram illustrating a construction management system according to some embodiments of the present invention. 10 is a flowchart illustrating a task list check according to some embodiments of the present invention. 10 is a flowchart illustrating a time sheet check according to some embodiments of the present invention. 10 is a flowchart illustrating the automatic creation of a target attendance table according to some embodiments of the present invention. 1 is a flowchart illustrating a determination of a worker's income risk according to some embodiments of the present invention. 1 is a flowchart illustrating an implementation of a risk alert according to some embodiments of the present invention. 1 is a flowchart illustrating management of wage payments according to some embodiments of the present invention. 1 is a flowchart illustrating a target pay slip determination according to some embodiments of the present invention.

In order to more clearly explain the technical solutions of the embodiments of the present invention, the drawings necessary to describe each embodiment are briefly introduced below. Obviously, the drawings in the following description are only some examples or embodiments of the present invention, and those skilled in the art can also apply the present invention to other similar cases according to these drawings without any creative work. Unless otherwise clear from the context or otherwise explained, similar component symbols in the drawings represent similar structures or operations.

It should be understood that the terms "system," "device," "unit," and/or "module" used herein are a way of distinguishing between different assemblies, elements, components, parts, or assemblies at different levels. However, other terms may be substituted for said terms if they achieve the same purpose.

As used herein and in the claims, unless the context clearly indicates otherwise, words such as "a," "one," "one," "one kind," or "the," do not specifically refer to the singular but may include the plural. Generally speaking, the terms "comprise" and "include" only indicate the inclusion of specifically identified steps and elements, and these steps and elements do not constitute an exclusive list; a method or apparatus may also include other steps or elements.

The present invention uses flowcharts to describe the steps and operational means performed according to embodiments of the method of the present invention. Note that the steps included in the method do not necessarily have to be performed in exact order; they may be performed in reverse order or simultaneously. Other steps may also be added to these processes, and some steps may be omitted from these processes.

Figure 1 is a diagram showing an application scenario of a construction management system according to some embodiments of the present invention. The application scenario 100 of the construction management system may include a construction-related object 110, a construction document 120, and a server 130.

Construction-related objects 110 are objects participating in a construction project.

A construction project may be divided into multiple sub-departments or sub-tasks. Each sub-department or sub-task may be further divided into multiple sub-tasks. Construction-related objects may be divided into different hierarchies depending on the degree of granularity of the tasks for which they are responsible. For example, a hierarchy of construction-related objects may include, from top to bottom, prime contractors, subcontractors, teams, groups, workers, etc.

A prime contractor is the party that coordinates a construction project. The prime contractor is the highest level in the hierarchy of construction-related entities.

A subcontractor is a company or contractor responsible for one or more sub-departments/sub-processes.

A team is a core work group belonging to a supplier or contractor, responsible for completing production tasks for a sub-department/sub-process. Each team has a team leader. The team leader can manage administrative tasks within the team, such as distributing team task lists to the team or workers, and organizing and checking time sheets, attendance sheets, or pay slips.

A group is a subdivision created by further dividing a team, and is responsible for completing production tasks that belong to a sub-department/sub-process. Each group has a group leader. The group leader can manage administrative matters within the group, such as distributing task lists to workers in the group, and organizing and checking the time sheets, attendance sheets, and pay slips of workers in the group.

Workers are the basic unit that makes up a group and are the lowest level in the hierarchy of construction-related objects. After receiving a task list, workers enter the site, begin work, and complete the production tasks included in the task list.

Note that, depending on the actual needs of the construction project, the construction-related objects 110 may include only some of the prime contractors, subcontractors, teams, groups, and workers. For example, the construction-related objects 110 may not include groups and/or subcontractors.

The construction document 120 may be various documents created during the progress of a construction project, such as a task list, timesheet, attendance sheet, pay slip, etc.

Task lists are used to assign construction tasks. The task list assignment process involves assigning tasks hierarchically according to the hierarchy of construction-related objects, for example, from the prime contractor to subcontractors, from subcontractors to teams, from teams to groups, and from groups to workers.

After the task list is distributed, workers enter the site and perform their work, and time sheets, attendance sheets, and pay slips are created as the project progresses. Workers only enter the site and perform their work when there is a task, and time sheets are created only after the work is completed. If there is a time sheet, work records and acceptance inspections are carried out, and wages are not paid without work records and acceptance inspection certificates. For this reason, there is a data association relationship between each field within the construction document and the document, and based on this, it is possible to prove the interrelationship and mutual validation between construction documents.

After construction documents such as task lists, time sheets, attendance sheets, and pay slips are created, they are uploaded to server 130 via the network, and server 130 may manage construction work based on this data.

Server 130 refers to a system with computing capabilities, such as a computer, industrial computer, or computing cloud platform. The server may include a processing unit, such as a CPU.

In some embodiments, the construction management system and its modules may be located within a processing unit of a server and perform the functions described in one or more embodiments of the present invention.

Construction management systems according to some embodiments of the present invention may be applied to various construction management scenarios, such as checking construction documents, automatically creating attendance schedules and/or attendance lists, determining and issuing alerts for worker income risks, and managing wage payment flows.

For a more detailed description of the construction management system and its modules, and the implementation of construction management based on the construction management system, please refer to the relevant descriptions of Figures 2 to 9 of the present invention.

Figure 2 is a block diagram illustrating a construction management system according to some embodiments of the present invention. As shown in Figure 2, in some embodiments, the construction management system 200 may include at least a document acquisition module 210, a document check module 220, and a document determination module 230.

The report acquisition module 210 is configured to acquire input reports. In some embodiments, the input reports include at least a task list and a time sheet.

The report check module 220 is configured to check input reports.

In some embodiments, the document check module 220 may obtain first verification data related to the task list, check the task list based on the first verification data, and determine the checked task list when the check result satisfies a first predetermined condition. The first verification data may include internal data of the task list.

In some embodiments, the document check module 220 may further perform a first validation of the task list based on pre-defined association relationships and task list internal data.

In some embodiments, the pre-defined association relationships include at least one of a worker-to-job relationship, a task item-to-job relationship, a job-to-labor cost relationship, and a project-to-area relationship.

In some embodiments, the first verification data further includes externally related data for the task list. The document check module 220 may perform a second verification on the task list based on the externally related data and the task list internal data.

In some embodiments, the report check module 220 can acquire second verification data, perform a timesheet check based on the second verification data, and determine a checked timesheet when the check result satisfies a second preset condition. The second verification data includes at least a checked task list. The checked task list is at least a task list that has passed the first verification.

In some embodiments, the second verification data further includes time record information and payroll information related to the checked task list. The report check module 220 may perform a time record check based on the checked task list, time record information, and payroll information.

The document determination module 230 is configured to determine a target document in response to the checked input document. In some embodiments, the target document includes at least one of a target attendance table and a target pay slip.

In some embodiments, the form determination module 230 may automatically generate a target attendance form based on the checked task list and the checked attendance form when the input form does not include an attendance form, perform an attendance form check based on the checked task list and the checked attendance form when the input form includes an attendance form, and determine a target attendance form when the result of the attendance form check satisfies a third predetermined condition.

In some embodiments, the attendance schedule check includes an attendance schedule authenticity check. The attendance schedule authenticity check includes at least one of a project authenticity check, a quantity/price authenticity check, and a time authenticity check.

In some embodiments, the document determination module may automatically generate a target pay statement based on the checked task list, checked attendance sheet, and target attendance sheet when the input document does not include a pay statement, perform a pay statement check based on the checked task list, checked attendance sheet, and target attendance sheet when the input document includes a pay statement, and determine the target pay statement when the result of the pay statement check satisfies a fourth preset condition.

In some embodiments, the pay slip check includes at least one of a check for authenticity of expenses, a check for reasonableness of expenses, and a check for correlation of pay slip-related data.

In some embodiments, the construction management system 200 may further include at least one of an assessment module 240 and a risk module 250.

The assessment module 240 is configured to verify whether worker income is at risk in the target attendance schedule.

In some embodiments, the evaluation module 240 may determine the worker's income range for at least one work recording day based on the checked task list and the checked attendance sheet, and may determine that the worker's income recorded in the target attendance sheet is at risk in response to the income for any one work recording day in the target attendance sheet not being within the income range.

A work record date refers to a natural day on which a worker enters a work site and performs work, and for which there is corresponding work record data. Different work record dates may be distinguished by the date that corresponds to the work record date.

In some embodiments, the evaluation module may determine distributable income based on the checked task list and determine that the worker income recorded in the target attendance table is at risk when the worker income in the target attendance table is greater than the distributable income.

The risk module 250 is configured to determine the type of risk in response to the worker's income failing the reasonableness verification, determine collateral information based on the risk type, and manage the flow of wage payments to the worker based on the collateral information.

For a detailed description of the construction management system 200 and each of its constituent modules and functions, please refer to the relevant descriptions of Figures 3 to 9 herein.

The above description of the construction management system 200 and its modules is provided solely for the convenience of explanation and is not intended to limit the scope of the embodiments of the present invention. Those skilled in the art will be able to understand the principles of the system and combine modules arbitrarily, or configure subsystems and connect them to other modules, without departing from these principles. In some embodiments, the document acquisition module, document check module, document determination module, evaluation module, and risk module shown in FIG. 1 may be different modules in a single system, or a single module may perform the functions of two or more of the above modules. For example, each module may share a single storage module or have its own storage module. All such variations are within the scope of the present invention.

Figure 3 is a flowchart illustrating a task list check according to some embodiments of the present invention. As shown in Figure 3, the task list check may include the following: In some embodiments, the task list check may be performed by the document check module 220.

In some embodiments, the document check module 220 may obtain first verification data 320 related to the task list 310, perform a task list check 330 based on the first verification data 320, and determine the checked task list 350 in response to the check result satisfying a first predetermined condition 340.

The first verification data refers to data for checking the task list. In some embodiments, the first verification data 320 may include data associated with the existence of the task list 310, such as at least one of task list internal data 321 and task list external related data 322.

A task list is a document that records and transcribes construction tasks. Construction tasks may be recorded in the task list in the form of task items. Each task list may contain one or more task items. A task list may further contain various information related to the execution of the task items, including, but not limited to, the construction area, contract performance target, construction period, disclosure content, quantity and price information, etc. The construction area may indicate the area in which the task item will be constructed. The contract performance target may indicate who will complete the task item. The construction period may indicate the execution time or planned completion time of the task item. Disclosure content is normative content related to the construction work techniques and construction safety of the task item. The quantity and price information is content related to the cost and cash flow of the task item.

In some embodiments, construction tasks are typically transferred between different departments or personnel in the form of a task list. Task lists are typically created by an entity with management authority over construction-related objects, such as a prime contractor, subcontractor, team, group, etc.

In some embodiments, task lists may be hierarchically divided by their creator or distribution. For example, a prime contractor task list is created by a prime contractor, a subcontractor task list is created by a subcontractor, a team task list is created by a team, and a group task list is created by a group. Note that group task lists may also be referred to as worker task lists, as they are distributed directly to workers.

After task lists with different levels are created, they are assigned to the relevant entities at lower levels required to execute the task lists, for example, from the prime contractor to the subcontractor, from the subcontractor to the team, from the team to the group, and from the group to the worker.

Unless otherwise specified in the surrounding text, the task list in some examples of this specification refers to a worker task list.

In some embodiments, a task list has a status tag associated with it. The status tag can be determined based on the transfer and execution status of the task list. For example, the status tags for a task list may include: waiting to be assigned, assigned, waiting to be executed, running, executed, etc.

In some embodiments, the report acquisition module 210 can acquire the task list by communicating with the user terminal.

Task list internal data refers to data related to construction tasks listed within the task list.

In some embodiments, the report checking module 220 can obtain task list internal data by reading at least one entry in the task list.

In some embodiments, the task list internal data may include multiple entries, such as at least one of the following: construction projects belonging to the task list, construction areas, task item information, execution target information, construction period information, disclosure information, and quantity/price information.

A construction project refers to the production object associated with a task list. A construction project may be divided into multiple sub-departments or sub-processes. A sub-department or sub-process may be divided into multiple construction tasks.

The construction area is information that indicates the scope of the construction task.

Task item information is information that describes the details of construction tasks that need to be completed in a construction project. A construction project may include different task items depending on the type. Taking a construction project for a building process as an example, the task items may include multiple construction tasks such as constructing the foundation, constructing the main structure (e.g., walls, columns, ceilings, etc.), constructing elevators, constructing drainage structures, constructing electrical structures, and decoration. These construction tasks may be gradually divided into specific task items, such as a bricklaying task item in wall construction. In some embodiments, task item information may be divided into different hierarchies. Task item information at a higher level may be divided into task item information at one or more lower levels.

The execution target information represents information related to the person completing the construction task, and may include the worker and their corresponding job type.

Construction period information is information about the progress time of a construction task, for example, the planned construction period. The planned construction period may reflect the planned start time, duration, planned completion time, etc. of a construction project.

Disclosure information is information relating to construction proposals and/or work specifications, such as construction proposals, construction plans, construction contracts, technical disclosure documents, safety disclosure documents, etc., or other related documents.

Quantity and price information includes information about construction task costs and payments, such as unit and total costs for workers of different job types, accounting periods for salary payments, and estimated task quantities.

In some examples, the task list internal data may further include minimum production units. For example, a construction project may be divided into at least one minimum production unit. Each minimum production unit may correspond to a task item at the lowest level corresponding to one structural unit in one spatial unit. In some embodiments, the minimum production unit may exist in the task list instead of a task item in the task list. Note that a spatial unit refers to a spatial range for constructing or manufacturing structural units in a spatial section of a construction project. Each spatial unit may be used to construct or manufacture one or more structural units. A structural unit is an object or structure, such as a wall, handrail, or staircase, that is waiting to be manufactured or constructed in the construction project.

A minimum production unit is the smallest unit obtained by dividing a construction task in a construction project. Note that a minimum production unit cannot be further divided. A minimum production unit is a division of the construction tasks (or construction items) included in a construction project according to spatial dimensions and configuration dimensions. Therefore, each minimum production unit is unique. In some embodiments, all construction tasks in a construction project may be divided into minimum production units. When all minimum production units are completed, the construction project is completed. After a construction project is divided into minimum production units, i.e., the construction project or construction tasks in the construction project are managed according to the minimum production units, thereby achieving fine-grained management.

In some embodiments, the minimum production unit has corresponding construction area and construction period information.

In some embodiments, the minimum production unit may be used during production management to manage the amount of work, cost, construction time, efficiency, etc. of a construction project. For example, a task list may include at least one minimum production unit. A construction manager manages a construction project based on the task list, for example, assigning construction tasks in the form of a task list and determining the completion status of the construction project according to the completion status of the task list.

In some embodiments, the document check module 220 may determine the minimum production unit according to the task list based on the internal task list data. For example, the document check module 220 may obtain construction project and task item information in the internal task list data, determine the task items in the construction project that need to be completed for the construction and manufacturing of component units, gradually divide the task items that need to be completed for the construction and manufacturing of component units by construction task type, obtain the lowest-level task items until they can no longer be divided, and determine the minimum production unit based on the lowest-level task items and the corresponding component units.

Task list external data refers to data generated after a task list is assigned, received, and executed. In some embodiments, task list external data may include, but is not limited to, at least one of attendance information, inspection information, postponement requests, work record information, wage payment information, and higher-level task lists. Note that because task lists have a fixed construction period, external data is continuously generated during the process of executing the task list. At least some of the external data may include corresponding reports. The correspondence between these reports and task lists does not have to be a one-to-one correspondence.

Attendance information is information related to attendance data. Attendance data may include attendance sheets and data related to the creation of attendance sheets. For example, data related to the creation of attendance sheets may include data uploaded from the gate of a construction site.

Inspection information is information related to inspection data. Inspection data refers to data when an inspection is conducted after a task item according to a task list has been completed. Inspection data may include an inspection certificate.

An application for postponement refers to an application to delay the planned construction period.

Work record information is information related to work record data. Work record data may include attendance schedules and data related to the creation of attendance schedules. For example, data related to the creation of attendance schedules may include whether or not work records are required, the specific attendance schedule, the time the attendance schedule was created, the actual creator, etc.

Wage payment information is data related to wage payments. Wage payment data may include pay slips and data related to the determination of pay slips. For example, data related to the determination of pay slips may include whether or not to send them, specific pay slips, the time the pay slips were created, the actual creator, etc.

A higher-level task list refers to a task list assigned by a higher-level object in the hierarchy of construction project-related objects. For example, when verifying a task list distributed to workers by a group, the higher-level task list includes at least the team task list distributed to the group by the team to which it belongs, and may also include subcontractor task lists and prime contractor task lists distributed by subcontractors and prime contractors. During verification, the internal data of the task list, such as task items, construction area, construction period information, and quantity and price information, must not exceed the scope distributed within the higher-level task list.

In some embodiments, the document checking module 220 may determine externally relevant data based on task items or minimum production units.

For example, the document check module 220 determines a task list corresponding to a task item or minimum production unit, obtains the completion status of this task list, and when this task list is completed, obtains the time attendance sheet, attendance sheet, pay slip, inspection data, and higher-level task list related to this task list, and may make an inquiry from at least one of the time attendance sheet, attendance sheet, pay slip, inspection data, and higher-level task list based on the task item or minimum production unit to determine external related data for the task list.

In some embodiments, the document check module 220 may perform a task list check in various forms based on the first verification data, and determine the task list as a checked task list when the result of the task list check satisfies a first predetermined condition.

In some embodiments, task list check 330 may include first verification 331 and second verification 332. Note that first verification 331 refers to verifying the task list based on pre-established association relationships and internal task list data. Note that second verification 332 refers to verifying the task list based on external related data and internal task list data of the task list.

In some embodiments, the task list check items may include an authenticity check and a reasonableness check. Note that an authenticity check refers to checking whether each entry and its numerical value in the task list actually exists. A reasonableness check refers to checking whether the quantity and price information in the task list is reasonable.

In some embodiments, the first preset condition is that the task list is authentic and that the task list is determined to be irrational less than two times.

In the embodiments of the present invention, "authenticity" refers to the actual existence of entries and the numerical values of entries in documents (e.g., task lists, time sheets, attendance sheets, pay slips, etc.), and "reasonableness" refers to the numerical values of entries in documents being within a reasonable range. If the numerical value of an entry is not within a reasonable range, the primary reasonableness check is deemed to have failed. For the reasonable range of numerical values, see the related explanation below.

In some embodiments, the document check module 220 may perform a first verification 331 on the task list based on the pre-defined association relationship 370 and the task list internal data 321.

A pre-defined association relationship refers to the association relationship between different entries in the pre-defined task list internal data.

In some embodiments, the pre-defined association relationships may include at least one of a worker-to-job relationship, a task item-to-job relationship, a job-to-labor cost relationship, and a project-to-area relationship.

In some embodiments, the document check module 220 may determine the association between the worker and the job type based on the past task list. For example, the document check module 220 may obtain the worker's past task list, determine the past task items in this past task list, determine the worker's past job type using a first preset table based on the past task items, compile statistics on the past job types based on the past task items, and determine the job type that meets the preset job type conditions as the job type currently associated with the worker.

The first preset table contains correspondences between different task items and job types, and may be determined based on a priori experience or past data. In some embodiments, the task items in the first preset table may be task items at any one level in the task tree. Note that a task item at the lowest level may correspond to only one job type, and task items at non-lowest levels may correspond to one or more job types. A task item at the lowest level is the last level in the task tree. In some embodiments, task items at the lowest level are task items that cannot be consecutively divided in terms of task type. For more information on task trees, see the description below.

The preset job type conditions are conditions that associate job types with workers. The preset job type conditions may be set manually in advance, and may be, for example, the two job types with the most statistical counts.

In some embodiments, occupations may be represented in a tree structure. This tree structure may include at least one occupation hierarchy. Taking a tree structure including first-level occupations and second-level occupations as an example, the second-level occupations are sub-skills of the first-level occupations. For example, the first-level occupations are represented by codes such as α and β, where α is rebar work and β is plastering, and the second-level occupations include _α1 , _α2 , _α3 , _β1 , etc., where _α1 , _α2 , and _α3 are sub-skills such as "processing,""straightening," and "cutting" included in rebar work α, and _β1 represents a sub-skill included in plastering.

For example, when statistical analysis is performed on the job types according to the past task items of a certain worker, if the statistical results show that the job type _α3 appears three times, the job type _β1 appears twice, and the job types _α1 and _α2 appear once each, the job types that meet the preset job type conditions may be determined to be ( _α3 , _β1 ) associated with the worker.

In some embodiments, the document checking module 220 may adjust the initial job title associated with the worker based on the worker's personal performance data.

Personal ability data refers to data that can represent the individual abilities of a worker. Personal ability data may also include the worker's learning status and the completion status of past task items.

By way of example only, if a worker learns skills in another unrelated occupation, an association may be established between the worker and the unrelated occupation. If a current worker is associated with a certain occupation and the completion status of past task items continues to be unsatisfactory, the association between the worker and the related occupation may be terminated.

Note that a worker's learning status and the completion status of past tasks may also be determined by manual input.

In some embodiments, the document checking module 220 may adjust the job title associated with the worker based on data from other sources. Other data sources may include peer assessments, self-assessments, etc. The details may be determined based on actual needs.

Building an association between workers and job types allows for better determination of the authenticity of a worker's task completion and avoids insufficient task type authenticity.

In some embodiments, the document check module 220 may determine the association relationship between task items and job types based on a task tree. For example, the document check module 220 may obtain a task tree, determine the task items at the lowest level in the task tree, determine the association between the task items at the lowest level and job types, and dynamically adjust the association between the task items at the lowest level and job types.

A task tree refers to a tree structure that shows the dependency relationships between multiple task items.

In some embodiments, the document checking module 220 may obtain a task tree by dividing all work tasks of a construction project by at least one of the following: type of work, sub-division work, sub-work, step, and process. For example, the division may be made from coarse to fine in the order of type of work, sub-division work, sub-work, step, and process, or by sub-work, step, and process only. By way of example only, if the task item is {a, b, c, d, e}, this task item may represent a sub-class a work, a sub-part b work, a section c work in progress, and a process e task within step d.

After a construction task is divided, task items that cannot be further divided may be referred to as task items at the lowest level. For example, if the task items are {a, b, c, d, e}, {e} represents the task item at the lowest level. Taking a construction project as an example, if the task item is building a wall, subtask items such as "cleaning and leveling the masonry area," "wetting the bricks with water," and "drawing lines on the masonry area with an incline" may be considered to be lowest-level task items if they cannot be further divided.

In some embodiments, the document check module 220 may determine the association coefficient between the task item at the lowest level and the job type by querying a second pre-defined table based on the task item at the lowest level.

The association coefficient represents the degree of association between the task item at the lowest level and the corresponding job type.

The second preset table includes association coefficients between the lowest-level task items and the corresponding occupations. The second preset table may be determined based on a priori experience or past data. The sum of the association coefficients between the task items and all the corresponding occupations is 1. For example, if task item {e} corresponds to occupations _α1 and _α2 , and the processor queries the second preset table and finds that the association coefficients between task item {e} and _α1 and _α2 are 0.5 and 0.5, respectively, this indicates that the degree of association between task item {e} and the two occupations _α1 and _α2 is the same.

In some embodiments, the document checking module 220 may dynamically adjust the association relationship between task items and job types.

By way of example only, the document check module 220 matches the job type of the worker in the project with the job type corresponding to the task item of the project to which the worker is assigned. If the job type of the worker in the project is the same as the job type corresponding to the task item, the association coefficient between this task item and this job type is increased. If the job type of the worker in the project is different from the job type corresponding to the task item, the association coefficient between this task item and this job type is decreased. The extent to which the association coefficient is increased and/or decreased may be manually set in advance.

The job type of a worker within a project may be determined by the task list for this project and the job type associated with the worker. The job type corresponding to the task item of the project to which the worker is assigned may be determined by the association between the task item and the job type. For example, if the job type associated with task A is M and this task is actually completed by a worker with job type N, it may be considered that the association between task A and job type M is weak and that the association coefficient between task A and job type M needs to be reduced.

In some embodiments, if the association coefficient between a task item and a job type is lower than an association threshold, the correlation between the task item and the job type may be canceled. The association threshold refers to the minimum value of the association coefficient when an association relationship exists between a task item and a job type. The association threshold may be set manually in advance. If the association coefficient between a task item and a job type is lower than the association threshold, this indicates that the degree of correlation between the task item and the job type is low and the association may be canceled.

By establishing an association between task items and job types, it is possible to more accurately determine whether a worker has the ability to complete a task, and further determine the authenticity of the correspondence between the worker and task item. For example, if the job type associated with task A is M and the only job types associated with the worker are (P, Q), it is determined that the worker does not have the ability to complete task A, and task A corresponds to the worker, the authenticity of this correspondence is questionable.

In some embodiments, the document check module 220 may establish an association between job type and labor costs. For example, the document check module 220 obtains an initial labor cost according to job type and dynamically adjusts the initial labor cost based on at least one of the construction area, construction period information, and task item information related to the task list.

In some embodiments, the document check module 220 may determine an initial labor cost for each job type based on a priori experience or past data. The initial labor cost may include at least one of the minimum labor cost, maximum labor cost, and recommended labor cost for one work day for one job type.

A work day is a unit of measurement that measures the amount of work completed by a worker in time, and represents the amount of tasks completed by one worker within a standard work time. The standard work time can be set based on experience. For example, the standard work time may be 8 hours. In this case, one work day represents the amount of work completed by one worker within 8 hours.

In some embodiments, the report check module 220 may pre-set impact coefficients on initial labor costs based on correlation data such as construction area, construction period information, and task item information. For example, the impact coefficients may include an area impact coefficient, a date impact coefficient, and a task item impact coefficient. The initial value may be set to 1. The area impact coefficient represents the degree of impact on labor costs due to the construction area. The date impact coefficient represents the degree of impact on labor costs due to the construction period. The task item impact coefficient represents the degree of impact on labor costs due to the work content.

In some embodiments, the report check module 220 determines the construction area, construction period information, task item information, and corresponding labor costs according to the task list based on the task list internal data, and may adjust the impact coefficient on labor costs of this job type due to the construction area, construction period information, and task item information based on the statistical price distribution of the construction area, construction period, and task items. For example, the impact on labor costs may be increased for areas and/or time periods with labor shortages. Also, for example, the impact on labor costs may be increased for task items with high difficulty or task items with labor shortages in related jobs.

In some embodiments, the report checking module 220 may determine the adjusted recommended labor cost in various ways. For example, the processor may multiply the initial recommended labor cost by the average value of the area influence coefficient, date influence coefficient, and task item influence coefficient to obtain the adjusted recommended labor cost.

For example, the recommended labor cost for the rebar worker job is 300 yuan, but because it is the busy farming season, workers need to return home to work in the fields. Therefore, the date influence coefficient corresponding to the farming period will be relatively high. The processor can query the fourth pre-set table to obtain the area influence coefficient, date influence coefficient, and task item influence coefficient, as well as obtain the average value α of the area influence coefficient, date influence coefficient, and task item influence coefficient, thereby obtaining 300α as the adjusted recommended labor cost for the rebar worker job.

By establishing an association between job type and labor cost, you can more accurately determine the rationality of labor costs and prevent overpayment or underpayment of labor costs.

In some embodiments, the document check module 220 may obtain the project name of the construction project corresponding to the construction area, authenticate the authenticity of the construction project based on the project name, and determine an association relationship between the project and the area in response to the construction project being authenticated.

In some embodiments, the document verification module 220 queries information such as the safety supervision registration number, quality supervision registration number, and construction permit of the construction project through a third-party platform to ensure that the construction project is a genuine and valid construction item. The third-party platform may include a search engine, a construction-related database, etc.

In some embodiments, the document checking module 220 may determine the initial area division status of a construction project based on data such as the construction project's construction plan permit, construction plan, and construction proposal. For example, the construction area may be divided into a building, basement, foundation pit, leveling work, etc. The document checking module 220 may encode the divided construction areas and determine an initial association between the construction areas and the construction project. For example, in construction project A, construction is required in construction area 1, construction area 2, and construction area 3, i.e., construction project A is associated with construction area 1, construction area 2, and construction area 3.

In some embodiments, the document checking module 220 may further divide the construction area obtained by dividing the initial area according to actual construction needs. For example, a building may be divided into multiple floors, each floor into multiple households, and each household into multiple rooms. Furthermore, an area tree may be constructed with a dependency relationship from larger areas to smaller areas, and each node in the area tree may be encoded. This ensures that spatial information such as projects and areas is unique, authentic, and valid.

By establishing an association between projects and areas, it is advantageous to further divide projects and determine task items, and the corresponding job types can be determined based on the task items, allowing for even more precise management.

In some embodiments of the present invention, more data is associated from the data included in the task list, association relationships are established between different data, and related data are verified against each other to ensure the authenticity of the data.

In some embodiments, the first verification may include verifying whether each entry in the task list internal data truly exists, and if each entry truly exists, determining the authenticity of the task list; verifying whether the quantity pricing information is reasonable based on the non-quantity pricing information in the task list, and if the quantity pricing information is reasonable, determining the reasonableness of the task list.

In some embodiments, during authenticity verification, the authenticity check includes checking entries in the task list internal data, such as construction project, construction area, and task item information.

In some embodiments, the document check module 220 compares the construction project, construction area, and task item information in the task list based on the actual project, construction area, and task item corresponding to the minimum production unit to determine whether they match. If they match, this indicates that the construction project, construction area, and task item information in the current task list is authentic, and the task list is marked with the minimum production unit code.

In some embodiments, the authenticity check further includes checking the execution target and construction time information.

In some embodiments, the document check module 220 compares whether the construction period information according to the task list is the same as the execution target information based on the planned construction period and execution target of the minimum production unit, and if they are the same, indicates that the current task list is authentic with respect to the execution target and construction period information.

In some embodiments, if the above entries in the task list are verified as authentic, the task list may be considered authentic.

Quantity price information refers to information that can be used to determine worker income, such as job type, labor cost, expected task volume, etc.

Non-quantity price information refers to information that does not directly affect worker income, such as task items, construction proposals, construction plans, contracts, etc.

In some embodiments, verifying that the quantity pricing information is reasonable includes checking at least one of the job type, labor cost, and expected task volume.

In some embodiments, the check for reasonableness includes checking the occupation. For example, the document check module 220 may determine whether the worker's occupation is reasonable based on the occupation corresponding to the task item. If the occupation corresponding to the task item differs from the worker's occupation, the worker's occupation is deemed to be unreasonable.

In some embodiments, the reasonableness check further includes checking the labor cost. For example, the report check module 220 may determine a recommended labor cost according to a preset association relationship based on the construction area, construction period information, and task item information in the task list, and check whether this labor cost for the worker is reasonable. If the difference between the recommended labor cost and the labor cost in the task list exceeds a cost threshold, it may be deemed unreasonable. The cost threshold refers to the minimum difference between the recommended labor cost and the actual labor cost within a reasonable range. The cost threshold may be set manually in advance.

In some embodiments, the reasonableness check further includes checking the expected task volume.

In some embodiments, the document check module 220 obtains the true total task volume based on information such as construction proposals, construction plans, and contracts in the disclosed information, and checks whether the expected task volume in the task list is reasonable. If the difference between the expected task volume in the task list and the actual total task volume exceeds the task threshold, the expected task volume in the task list is deemed unreasonable. The task threshold refers to the difference between the expected task list and the actual total task volume within a reasonable range. The task threshold may be set manually in advance.

In some embodiments of the present invention, task lists are verified based on pre-defined association relationships and internal task list data, thereby enabling cross-correlation and cross-verification of internal task list data. This multi-faceted verification can better ensure the authenticity and rationality of task lists, providing reliable data assurance for checking and determining other documents.

In some embodiments, the document check module 220 may perform a second validation of the task list based on external related data and task list internal data.

In some embodiments, in response to a request to accelerate the project's completion schedule based on the task list, the document check module 220 may perform a second verification of the task list.

A request for acceleration of construction schedule refers to the time already spent on a construction project reaching a predetermined point in time. The predetermined point in time may be set according to actual needs and/or a priori experience. One construction project may have one or more predetermined points in time.

For example, construction project A will start on March 1st and is scheduled to be completed within three months, with preset dates being April 1st, May 1st, and June 1st. Depending on the start of construction project, when the time reaches one of the three preset dates, the document check module 220 may perform a second verification on the task list.

In some embodiments, in response to a completion satisfaction request for an item corresponding to the task list, the document check module 220 may perform a second check on the task list.

A completion satisfaction requirement refers to the percentage of completed tasks for a construction project reaching a completion threshold. The completion rate is used to evaluate the completion progress of a construction project and may be a percentage value. In some embodiments, the completion rate may be determined based on the percentage of the number of completed minimum task units relative to the total number of minimum task units in the construction project. The completion threshold represents a completion node that requires second verification and may be set according to actual needs and/or a priori experience. A single construction project may have multiple completion thresholds.

For example, the completion thresholds for a certain construction project may be 25%, 50%, 75%, and 100%, and when the completion thresholds for the construction project reach the above four completion thresholds in response to the start of construction, the document check module 220 may perform a second verification on the task list.

In some embodiments, the second verification includes verifying the authenticity of the task list based on generated reports and the status of the generated reports in the external related data.

In some embodiments, the document check module 220 may verify the authenticity of the task list by comparing it with the execution status of the task list based on external task list data.

For example, the document check module 220 may determine whether the attendance data, inspection data, and work record/wage payment data corresponding to the task list are all present, and if so, determine that the task list is authentic. If not, determine whether a postponement request has been made, and if a postponement request has been made, determine that the task list is authentic. If no postponement request has been made, determine that the task list is inauthentic. Inspection data refers to records that are inspected after a task item has been completed. Work record/wage payment data refers to records of work records and wage payments for past task items.

Furthermore, for example, if a task list passes the planned construction period, the task list lacks attendance data and inspection data, and no extension request is submitted, i.e., it is impossible to determine whether the task list will be completed as planned, the document checking module 220 may determine that the authenticity of the task list has deteriorated.Furthermore, for example, if the task list is completed, i.e., the task item is completed, but there is no corresponding work record or wage payment data even after a long time has passed, the document checking module 220 may determine that the authenticity of the task list has deteriorated.

In some embodiments of the present invention, task lists are checked based on external related data and task list internal data, taking into full consideration various data that may be generated after the task list is executed, as well as task lists at higher levels relative to the task list, and verifying different types of external data to better ensure the authenticity and rationality of the task list.

Figure 4 is a flowchart illustrating timesheet checking in accordance with some embodiments of the present invention.

As shown in FIG. 4, the timesheet check may include the following: In some embodiments, the timesheet check may be performed by the document check module 220.

In some embodiments, the document check module 220 may obtain second verification data 410, perform an attendance record check 420 based on the second verification data 410, and determine a checked attendance record 440 in response to the check result satisfying a second predetermined condition 430.

A timesheet is a document that records the attendance status of workers. In some embodiments, the timesheet may include multiple entries related to a worker's attendance for at least one work recording date, such as the worker and their corresponding entry and exit times, construction projects, task items, or other related data. Furthermore, the timesheet may also include the minimum production unit. The entry and exit times include at least the worker's entry or exit time. The timesheet may be completed and submitted to the system by the team leader or group leader who manages the worker, based on data uploaded from the time clock or gate.

In some embodiments, the report check module 220 may communicate with the report acquisition module 210 to acquire the attendance record. The attendance record in the report acquisition module 210 may be acquired by inputting a construction-related object for which the user has administrative authority.

The second verification data is data for checking the attendance record.

In some embodiments, the second verification data 410 includes at least the checked task list 350. The checked task list is at least a task list that has passed the first verification. In some embodiments, the report check module 220 may obtain the checked task list based on the check results of the first verification performed on the task list.

In some embodiments, the second verification data 410 further includes work record information 411 and payroll information 412 associated with the checked task list.

Work record information refers to actual work information related to the checked task list, and may include, for example, the minimum production unit recorded in the attendance schedule, actual construction period data, and the processing status of the attendance schedule. In some embodiments, work record information is obtained from the checked attendance schedule by the document check module 220, and once checking of the attendance schedule is completed, the attendance schedule may be considered to have been processed.

Payroll information refers to information related to wage payments associated with the checked task list, such as minimum production units for wage payments and work record date data. In some embodiments, payroll information may be obtained from checked pay slips by the document check module 220.

In some embodiments, the report check module 220 may perform various forms of attendance record checks based on the second verification data, and determine that the attendance record is a checked attendance record when the results of the attendance record check satisfy a second preset condition.

In some embodiments, the second pre-defined condition may include that the attendance record is reasonable and authentic.

In some embodiments, the report check module 220 obtains the minimum production unit and planned construction period in the task list based on the checked task list, determines whether the minimum production unit linked to the attendance object in the attendance sheet matches the minimum production unit in the task list, and if they match, determines that the attendance object in the attendance sheet is authentic, determines whether the punched date in the attendance sheet is within the range of the planned construction period in the checked task list, and if it is within the range, determines that the date on the attendance sheet is reasonable.

In some embodiments, if the attendance object in the attendance sheet is authentic and the punch date is reasonable, the document check module 220 may determine that the attendance sheet is reasonable. On the other hand, if the attendance object in the attendance sheet is not authentic or the punch date is not reasonable, the document check module 220 may determine that the attendance sheet is not reasonable.

In some embodiments, the document check module 220 may perform a timesheet check based on the checked task list, work record information, and payroll information. For example, the document check module 220 may check the entry eligibility of the worker corresponding to the timesheet based on the checked task list, work record information, and payroll information, and determine that the timesheet is not authentic if the worker corresponding to the timesheet does not have entry eligibility.

Entry eligibility refers to a worker's eligibility to enter a site and perform work. In some embodiments, the processor may check a worker's entry eligibility in multiple areas, including the construction project blacklist, checked task list, work record information, and payroll information. A worker cannot be determined to be eligible for entry unless he or she simultaneously meets multiple entry eligibility criteria.

In some embodiments, the document checking module 220 may determine the minimum production unit and planned construction period of the checked task list for a construction project, and compare the minimum production unit associated with the worker with the minimum production unit in the checked task list to determine whether this minimum production unit belongs to this construction project and whether this construction project is within the planned construction period at that time. If the minimum production unit associated with the worker belongs to this project and this project is within the planned construction period, the worker may be considered eligible for entry in this area.

In some embodiments, the document check module 220 may check the worker's entry eligibility based on the work record information. If all attendance sheets in the worker's work record information have already been processed but subsequent tasks have not been assigned, this may be determined to be attendance fraud and the worker will be deemed to not meet the entry eligibility in this area.

In some embodiments, the document checking module 220 may check the worker's eligibility for entry based on payroll information. If a worker's pay slip shows that wages have not been paid for a predetermined period of time, this may be determined to be attendance fraud, and the worker will be deemed to not meet this eligibility for entry. Note that the predetermined period refers to the critical length of time when an abnormality occurs during which wages are not paid. The predetermined period is manually set and may be, for example, three months.

In some embodiments, the document check module 220 may determine whether a worker is on a blacklist, and blacklisted workers may be deemed ineligible for entry into this area. The blacklist refers to workers who have committed fraud and are in a correction period. Misconduct may include acts such as attendance fraud and false wage reporting.

Some embodiments of the present invention check attendance records based on the checked task list, work record information, and payroll information, and by correlating and cross-verifying various data in different processes, it is possible to more effectively and accurately verify whether the attendance record is authentic and reasonable, making it more difficult to falsify data, further ensuring the authenticity of the attendance record, and providing reliable data for confirming pay slips.

Figure 5 is a flowchart for automatically creating a target attendance schedule in some embodiments of the present invention. As shown in Figure 5, the automatic creation of a target attendance schedule may include the following: In some embodiments, the automatic creation flow of a target attendance schedule may be executed by the form determination module 230.

In some embodiments, the report determination module 230 may create the target attendance table 550 in various forms.

The attendance table 520 is a table that records the amount of work performed by a worker and the worker's income. The worker's income may include unit income and total income. Unit income refers to the worker's income per unit of work time. The attendance table 520 may include at least the worker's actual amount of work (also referred to as the amount of work recorded) for at least one work recording day.

In some embodiments, the attendance schedule 520 may further include construction task items, workers, working hours, unit prices, totals, construction periods, accounting periods, etc. Additionally, the attendance schedule may further include minimum production units, worker income, accounting periods, etc.

The target attendance list 550 is an attendance list whose authenticity can be verified.

In some embodiments, in response to the input form 510 not including the attendance sheet 520, the form determination module 230 may automatically create a target attendance sheet 550 based on the checked task list 350 and the checked attendance sheet 440.

In some embodiments, the report determination module 230 may modify the planned construction period in the checked task list based on the checked attendance sheet, determine the actual construction period, and determine the actual working hours for each worker based on the actual construction period.

For example, if a worker is part-time, at least the number of work days actually completed by the worker is recorded in the attendance sheet. In this case, the report determination module 230 may calculate the worker's actual workload based on the actual working hours using a preset conversion rule. For example, if the worker's actual working hours are 8 hours and the preset conversion rule is to record every 8 hours worked as 1 working day, the actual workload of the worker may be determined to be 1 working day.

For example, if a worker is a piecework worker, the amount of work actually completed by the worker is recorded at least in the attendance sheet. In this case, the report determination module 230 predicts the amount of work based on the actual working hours in the checked attendance sheet and the daily labor cost in the checked task list. For example, if the actual working hours are 8 hours, the daily labor cost determined based on the checked task list is 300 yuan, and the unit price of work is 30 yuan per square meter, the worker's daily planned amount of work may be estimated to be 10 square meters. If the difference between the completed amount and the planned amount of work in the checked attendance sheet meets the work amount condition, the completed amount is considered to meet the requirement, and 10 square meters is automatically recorded as the worker's actual work amount for that day. If the difference between the completed amount and the planned amount of work in the checked attendance sheet does not meet the work amount condition, further manual inspection is required. Note that the work amount condition may include the difference between the estimated completed amount and the planned work amount being no more than 10% of the planned work amount.

In some embodiments, the report determination module 230 may obtain the minimum production unit, labor cost, and accounting period from the checked task list, determine the worker's income based on the labor cost and the worker's actual work volume, and automatically create a target attendance list based on the obtained actual work volume, minimum production unit, worker's income, and accounting period.

In some embodiments, in response to the input form 510 including the attendance schedule 520, the form determination module 230 may perform an attendance schedule check 530 based on the checked task list 350 and the checked attendance schedule 440, and if the check result of the attendance schedule check satisfies a third predetermined condition 540, may determine a target attendance schedule 550.

In some embodiments, the report determination module 230 may communicate with the report acquisition module 210 to obtain the attendance list.

In some embodiments, the third preset condition may include the authenticity of the appearance list.

In some embodiments, the document determination module 230 may obtain information such as project information, minimum production unit, planned construction period, payment method, worker job type, and labor cost corresponding to the job type based on the checked task list, and may obtain the actual construction period and worker attendance status based on the checked attendance sheet. Note that the actual construction period refers to the date on which the worker actually participates in the work, i.e., the date on which attendance data is available. The worker attendance status may include the worker's number of recorded work days, work record dates, absenteeism rate, etc.

In some embodiments, the processor compares the data in the checked task list and checked time sheet with the data in the manually entered attendance sheet, and if the difference between the two is within a preset difference range, the attendance sheet check passes.

In some embodiments, the form of checking the authenticity of the attendance list by the report determination module 230 includes at least one of a project authenticity check, a quantity/price authenticity check, and a time authenticity check.

Project authenticity check refers to checking whether a project is authentic. In some embodiments, the report determination module 220 may determine whether the project information in the checked task list matches the project information according to the attendance schedule, and whether the area tree and task tree within the project match the area tree and task tree of the project according to the task list. If all of the above information matches, the processor determines that the minimum production unit in the task list is authentic, and the project authenticity check of the attendance schedule passes.

Quantity price authenticity check refers to checking whether the quantity price of the work task completed by the worker is authentic. The quantity price of the work task completed by the worker may be represented by the work record amount. In some embodiments, the ledger determination module 230 needs to check whether the work record amount is authentic. The work record amount is the product of the labor cost and the amount of work. In some embodiments, the ledger determination module 230 may determine the actual amount of work performed by the worker by checking whether the worker's attendance time is authentic, thereby ensuring the accuracy of the actual work record amount.

In some embodiments, the document determination module 230 obtains the corresponding work record amount based on the labor cost and work volume according to the checked task list and the checked attendance sheet, and compares it with the work record amount in the attendance sheet. If the two match, the quantity price authenticity of the attendance sheet is determined to be authentic.

Time authenticity check refers to checking the authenticity of paid hours. Paid hours may be displayed by accounting period on the attendance sheet.

In some embodiments, the ledger determination module 230 may check whether the accounting period recorded in the attendance list meets the time requirements, and if so, determine that the time authenticity check for this attendance list passes. The time requirements refer to rules that the payment time in the task list must meet. The time requirements may be set manually in advance. For example, the time requirement may be that the wage payment time is the next accounting period after the work is recorded. Illustratively, if a task released in March is completed in April, and the work is recorded and settled in May, the wage will be paid in the next accounting period after the work is recorded in May, i.e., June.

In some embodiments of the present invention, the attendance sheet may be checked using the checked task list and checked attendance sheet, and different data may be verified with each other to form a tightly connected data chain, determining that the data in the attendance sheet is supported by the task list and attendance sheet. This can better ensure the authenticity of the data in the attendance sheet and immediately detect possible data tampering.

Figure 6 is a flowchart illustrating the determination of a worker's income risk in accordance with some embodiments of the present invention. As shown in Figure 6, the determination flow of a worker's income risk may include the following: In some embodiments, the determination of a worker's income risk may be performed by the assessment module 240.

In some embodiments, the assessment module 240 may verify whether a worker's income is at risk in the target attendance schedule.

For example, if the worker's income in the target attendance schedule is not within a reasonable range, the assessment module 240 may determine that the worker's income in the target attendance schedule is at risk. Not being within a reasonable range refers to the following: the income for any one work record day in the target attendance schedule is not within the first income interval; the worker's income in the target attendance schedule is greater than the distributable income; or the worker's total daily income is not within the second income interval.

In some embodiments, the assessment module 240 may determine, based on the checked task list 350 and the checked attendance sheet 440, that the worker is in the first income interval 620 for at least one recorded work day, and may determine that the worker income 610 recorded in the target attendance sheet 550 is at risk in response to the income for any one recorded work day in the target attendance sheet 550 not being within the first income interval 620.

The first income interval refers to a range of daily wages. In some embodiments, the first income interval may be pre-set based on industry experience.

In some embodiments, the evaluation module 240 may obtain the worker's actual working time in the checked attendance sheet and the job value range corresponding to the minimum production unit in the target attendance sheet, and determine the first income interval for each work record day based on the actual working time and the job value range.

Actual working hours refer to the time a worker actually works within one work recording day.

In some embodiments, the evaluation module 240 may sort the attendance data chronologically based on the worker's attendance data for one work record day in the checked attendance sheet, determine the work period according to the matching principle, and determine the time remaining after accumulating the work period as the actual work time for that work record day.

The matching principle involves scanning all attendance data to find pairs of entry and exit punch times. For example, search for the first entry punch time from all attendance data, ignoring any exit punch times that appear before the first entry punch time, and then searching for the first exit record according to the order of the attendance data to find the first entry punch time, ignoring the entry punch time that appears before the first exit punch time, and then matching the first exit punch time with the first entry punch time. Repeat the above steps according to the order of the attendance data, and continue searching for pairs of entry punch times and exit punch times until all attendance data has been scanned. The entry punch time refers to the attendance data when the worker starts work, and the exit punch time refers to the attendance data when the worker finishes work.

The work period refers to the time difference between a pair of entry and exit punch times. For example, if the entry punch time is 08:00 and the exit punch time is 11:00, the work period is 3 hours.

In some embodiments, the evaluation module may repeat the above time difference determination step to determine at least one time difference within a work recording day, accumulate the at least one time difference, and determine the worker's actual working time for that work recording day.

The occupational value range refers to the range of income for different occupations on one work recording date.

In some embodiments, the evaluation module 240 may obtain each occupation related to the construction industry based on industry experience, preset upper and lower income limits for each occupation on a single work record day, and determine the preset upper and lower income limits for the occupation on a single work record day as the occupation value range for that occupation. For example, if the upper limit of the daily wage for a rebar worker is 350 yuan and the lower limit is 180 yuan, then the occupation value range for the rebar worker is [180, 350].

In some embodiments, the evaluation module 240 may obtain an initial value range and a past task list, determine a past value range based on the past task list, and determine a job value range based on the past value range and the initial value range.

The initial value range refers to the initially set job value range. In some embodiments, the evaluation module 240 may determine the pre-set upper and lower limits of the job's income on a work record day as the initial value range for this job.

The past task list may include a list of tasks that passed the check within the past time. Note that the past time may be set in advance, for example, one month.

In some embodiments, when assigning a past task list, workers and tasks may be matched based on the association between the worker and job type, and the association between the task item and job type. If the job type corresponding to the worker overlaps with the job type corresponding to the task item, this past task list may be assigned to the worker. The past task list may include at least the task item, the performing worker, quantity price information, etc. The quantity price information may include at least the worker's work volume, unit price, total amount, working hours, etc. The daily wage is the worker's wage for one recorded work day if the worker is a part-time worker, and is the ratio of total income to expected working hours if the worker is a piecework worker.

In some embodiments, the task list may be determined by the worker's manager's settings. Managers may include team leaders, group leaders, etc. In some embodiments, the manager selects workers whose available job functions overlap with the job functions required to complete the task, i.e., the selected workers' available job functions are the same or partially the same as the job functions required to complete the task, and the task list stores a snapshot of the overlap between the worker's available job functions and the job functions required to complete the task, thereby avoiding changes in the worker's available job functions or the job functions required to complete the task that could affect the accuracy of the task list.

The past value range refers to the job type value range of the completed task. In some embodiments, the evaluation module 240 may scan the past task list for daily wages corresponding to the job type, and determine the maximum daily wage as the upper limit of the past value range for this job type and the minimum daily wage as the lower limit of the past value range for this job type. Taking rebar production as an example, the past task list for the previous month stores the past daily wages of 100,000 rebar workers, and the evaluation module 240 may determine the maximum value of 350 yuan out of the past daily wages of 100,000 units as the upper limit of the past value range for rebar workers and the minimum value of 180 yuan as the lower limit of the past value range for rebar workers.

In some embodiments, the evaluation module 240 may calculate the extreme value approach rate for each past daily wage and determine the reliability of the past value range based on the extreme value approach rate. For example, if the proportion of the extreme value approach rate within the extreme value range is greater than a percentage threshold, the evaluation module 240 may determine that the past value range is reliable. Note that the extreme value range and percentage threshold may be set in advance based on past experience.

The extreme value approach rate may represent the distribution of past daily wages within the range of past values. In some embodiments, the extreme value approach rate may be expressed as a number, for example, a number between 0 and 1. The closer the extreme value approach rate is to 0, the closer the corresponding daily wage is to the minimum daily wage, and the closer it is to 1, the closer the corresponding daily rate is to the maximum daily wage.

In some embodiments, the evaluation module 240 may determine the extremum approach rate according to equation (1).
λ=(Pi-Pmin)/(Pmax-Pmin) Formula (1)

Here, λ represents the extreme value approach rate, Pi represents the i-th past daily wage, i ranges from 1 to n, n is the number of all past daily wages, Pmin is the minimum daily wage, and Pmax is the maximum daily wage.

For example, the extreme value approach rate λ may be expressed as a number between 0 and 1, the extreme value range may be set to 0.1 to 0.9, and the percentage threshold may be set to 90% of all extreme value approach rates. If the percentage of extreme value approach rates λ between 0.1 and 0.9 is greater than the percentage threshold, i.e., 90% of extreme value approach rates are between 0.1 and 0.9, the evaluation module may determine that the past value range is reliable.

In some embodiments, the evaluation module may adjust the initial value range based on the difference between the past value range and the initial value range, and determine the adjusted initial value range as the occupational value range. For example, the evaluation module may calculate the difference between the upper limit of the past value range and the upper limit of the initial value range, and if the difference between the upper limit of the past value range and the upper limit of the initial value range does not exceed an error threshold, determine that adjustment of the upper limit of the initial value range is unnecessary and determine the upper limit of the initial value range as the upper limit of the occupational value range.

Furthermore, for example, the evaluation module may calculate the difference between the lower limit of the past value range and the lower limit of the initial value range, and if the difference between the lower limit of the past value range and the lower limit of the initial value range does not exceed the error threshold, it may determine that adjustment of the lower limit of the initial value range is unnecessary and set the lower limit of the initial value range as the lower limit of the job type value range. Note that the error threshold may be set in advance based on past experience.

In some embodiments, the error threshold may be expressed in the form of a percentage, for example, 10%. If the upper limit of the past value range is less than or equal to 110% of the upper limit of the initial value range, or is greater than or equal to 90% of the upper limit of the initial value range, the evaluation module may determine that adjustment of the upper limit of the initial value range is unnecessary and may determine the upper limit of the initial value range as the upper limit of the occupation value range.

In some embodiments, the valuation module may adjust the upper limit of the initial value range using equation (2) in response to the difference between the upper limit of the past value range and the upper limit of the initial value range exceeding an error threshold, and may adjust the upper limit of the initial value range using equation (3) in response to the difference between the upper limit of the past value range and the upper limit of the initial value range being less than an error threshold.
Pt=Pm/(1+a%) Formula (2)
Pt=Pm/(1-a%) Formula (3)

Here, Pt represents the upper limit of the adjusted initial value range, Pm represents the upper limit of the past value range, and a% represents the error threshold.

In some embodiments, the valuation module may adjust the upper limit of the initial value range using equation (2) if the upper limit of the past value range exceeds (1+a%) of the upper limit of the initial value range, and may adjust the upper limit of the initial value range using equation (3) if the upper limit of the past value range is lower than (1-a%) of the upper limit of the initial value range.

In some embodiments, the valuation module may adjust the lower limit of the initial value range using equation (4) in response to the difference between the lower limit of the past value range and the lower limit of the initial value range exceeding an error threshold, and adjust the upper limit of the initial value range using equation (5) in response to the difference between the lower limit of the past value range and the lower limit of the initial value range being less than an error threshold.
Pb=Ps/(1+a%) Equation (4)
Pb=Ps/(1-a%) Equation (5)

Here, Pb represents the lower limit of the adjusted initial value range, Ps represents the lower limit of the past value range, and a% represents the error threshold. If the lower limit of the past value range exceeds (1 + a%) of the lower limit of the initial value range, the evaluation module may adjust the lower limit of the initial value range using equation (4), and if the lower limit of the past value range is lower than (1 - a%) of the lower limit of the initial value range, the evaluation module may adjust the lower limit of the initial value range using equation (5).

In some embodiments of the present invention, the job value range is automatically adjusted by an algorithm based on industry experience and past actual conditions, making the determined job value range more reasonable.

In some embodiments, the assessment module 240 may determine a first earnings interval for a worker's work record day based on the worker's actual work hours and job value range.

In some embodiments, the evaluation module may determine the first income interval based on actual work hours, standard work hours, and job value ranges. In some embodiments, standard work hours, also referred to as one shift, are set in advance based on industry experience and may be, for example, eight hours.

In some examples, if the actual work time does not exceed the standard work time, the evaluation module 240 may determine the first income interval 360 using equation (6).
Y=[Qb*h/hs*P1,Qt*h/hs*P2] Formula (7)

Here, P1 represents the lower limit of the job value range, P2 represents the upper limit of the job value range, h represents actual working time, hs represents standard working time, and Qb and Qt represent the lower limit adjustment coefficient and upper limit adjustment coefficient, respectively.

In some embodiments, the evaluation module may determine the first income interval 360 using equation (7) when the actual work time exceeds the standard work time.
Y=[Qb*(1+(h-hs)/hs)*P1,Qt*(1+(h-hs)*J/hs)*P2] Equation (8)

Here, P1 represents the lower limit of the job value range, P2 represents the upper limit of the job value range, h represents actual working time, hs represents standard working time, Qb and Qt represent the lower limit adjustment coefficient and upper limit adjustment coefficient, respectively, and J represents the overtime coefficient. The lower limit adjustment coefficient, upper limit adjustment coefficient, and overtime coefficient may be set in advance based on past experience.

In some embodiments of the present invention, the first income range is determined depending on the situation by comparing actual working hours with standard working hours, and an adjustment coefficient and overtime coefficient may be added to flexibly determine a more reasonable first income range.

In some embodiments of the present invention, the worker's actual working hours and corresponding job value range for each work day are determined to determine the worker's first income range for each work day, thereby ensuring the worker's wages and making wage distribution more equitable.

In some embodiments, the assessment module may obtain a target attendance schedule and query the work dates included in the attendance schedule. The assessment module 240 may determine that the worker's income in the target attendance schedule is at risk if the worker's income for any one work record day within the work dates is not within the first income interval, i.e., if the income exceeds the upper limit of the first income interval for the work record day or is lower than the lower limit of the first income interval for the work day.

In some embodiments of the present invention, determining whether a worker's income is at risk is performed by determining whether the worker's income exceeds a first income range. This allows the worker's income to be within a reasonable range, better protecting the worker's rights and preventing fraudulent payroll data.

In some embodiments, the assessment module 240 may determine the distributable income 630 using the checked task list 350 and determine that the worker income 610 recorded in the target attendance table 550 is at risk if the worker income 610 in the target attendance table 550 is greater than the distributable income 630.

Distributable income refers to the amount that can be allocated from the income of the checked task list to the target attendance table.

In some embodiments, the evaluation module 240 may determine the distributable income for the checked task list by subtracting the distributed amount from the total expected distribution amount for the checked task list.

The expected total allocation amount refers to the amount the user plans to pay for labor costs for the task list. The evaluation module 240 may be determined by input data from the user terminal.

The total amount that can be distributed in one checked task list is distributed to multiple attendance schedules corresponding to this task, and each time an attendance schedule is created, a consumed amount is generated in the checked task list corresponding to the attendance schedule.

The distributed amount refers to the amount distributed to other attendance schedules. The evaluation module 240 may scan the attendance schedules associated with the checked task list, read the data of all other attendance schedules other than the target attendance schedule, obtain the cumulative value of the amounts distributed in the other attendance schedules, and determine the distributed amount.

In some situations, one attendance schedule may correspond to multiple checked task lists. That is, the attendance schedule includes task completion information for multiple task lists. In this case, the evaluation module 240 obtains the expected total distribution amounts and distributed amounts for the multiple checked task lists, determines the distributable income corresponding to each of the multiple checked task lists, and further obtains the total distributable income for the multiple checked task lists, and may use the total distributable income to determine the worker income risk in the target attendance schedule.

In some embodiments, in response to worker income in the target attendance table being greater than distributable income, the assessment module 240 may determine that the worker income recorded in the target attendance table is at risk.

If the target attendance table corresponds to multiple checked task lists, the evaluation module 240 may determine that the worker income recorded in the target attendance table is at risk in response to the process income in the target attendance table being greater than the total distributable income.

In some embodiments of the present invention, by determining that the worker income in the target attendance table is greater than the distributable income in the corresponding checked task list, it is possible to ensure that the wages paid to the worker are within the planned range and further verify the reasonableness of the worker income in the target attendance table in terms of the total wage payment.

In some embodiments, the assessment module 240 may obtain a plurality of related attendance tables 640 associated with the worker, determine a second income range 660 for each work record date for the worker based on the job type information 650 in the plurality of related attendance tables 640, determine the worker's total daily income 670 based on the attendance table submitted by the worker's manager and the plurality of related attendance tables, and determine that the worker's total daily income 670 is not within the second income range 660, thereby indicating that the worker's income 610 recorded in the target attendance table 550 is at risk.

Related attendance schedules refer to all attendance schedules related to the target worker, other than the target attendance schedule. The target worker refers to the worker corresponding to the target attendance schedule. Note that since a worker can perform multiple types of work within one work recording day, there may be multiple attendance schedules for a worker on one work recording day.

In some embodiments, the evaluation module 240 may query all attendance schedules for attendance schedules that contain the same worker information based on the worker information in the target attendance schedule, and determine the attendance schedules that contain the same worker information as the relevant attendance schedules.

The second income range refers to the range of wages of a worker on one recorded work day.

In some embodiments, the evaluation module 240 may determine the work record date and job type according to the target attendance schedule, query the job type information of at least one attendance schedule and at least one attendance schedule for the same work record date in the related attendance schedules, obtain the union of job types according to all job type information in the target attendance schedule and the related attendance schedules, and determine the upper and lower limits of income per shift for each job type. For example, the upper limit of income per shift for each job type is represented by {Pt1, Pt2, Pt3...Ptn}, with one element in the array corresponding to the upper limit of income per shift for one job type, and the lower limit of income per shift for each job type is represented by {Pd1, Pd2, Pd3...Pdn}, with one element in the array corresponding to the lower limit of income per shift for one job type.

In some embodiments, the evaluation module 240 may determine a second income range for the target worker on a work recording day based on the target worker's actual working hours on that day and the corresponding upper and lower income limits per shift for that job type.

For example, if a target worker works 16 hours in one work record day, i.e., completes two shifts, the upper limit of the target worker's income for this work record day is Ptmax = 2*max{Pt1, Pt2, Pt3...Ptn}, and the lower limit is Ptmin = 2*min{Pd1, Pd2, Pd3...Pdn}.

Daily income refers to the income a worker earns per recorded day of work.

In some embodiments, the related attendance schedule may involve multiple work record dates. The evaluation module 240 may distribute the total income according to one related attendance schedule evenly across each of the multiple work record dates, i.e., determine the average daily income for the related attendance schedules, and determine the target worker's total daily income for a work record date based on the average daily income for the attendance schedules associated with the target worker's work record date.

Illustratively, the evaluation module 240 may determine the target worker's total daily income using equation (9).

Here, Q _d indicates the daily income of the target worker on the dth work record date, Q _d1 , Q _d2 , ..., Q _dm indicate the total income according to the first, second, ..., mth attendance schedules related to the dth work record date of the target worker, and U _d1 , U _d2 , ..., U _dm indicate the number of days according to the first, second, ..., mth attendance schedules related to the dth work record date of the target worker, respectively.
indicates the average daily income according to the first, second, ..., mth attendance schedules related to the dth work record date of the target worker,
refers to the average daily income according to the target attendance schedule.

In some embodiments, the evaluation module 240 may query the work record dates included in the target attendance schedule, obtain the related attendance schedule associated with each work record date and the target attendance schedule, and determine that the target worker's income is at risk if the daily income for any one work record date is not within the second income interval based on the target worker's daily income for each work record date using the above formula.

In some situations, a worker may have multiple attendance records for one work recording day, but the worker's income for one work recording day falls within a reasonable range, and under normal working conditions, the worker's daily income is neither too high nor too low. In some embodiments of the present invention, a reasonable second income range is determined, and whether the worker's daily income exceeds the second income range is determined to determine whether the worker's income is at risk, prevent the worker's wages from exceeding the reasonable range, and ensure fair and equitable wage payments.

FIG. 7 is a flowchart illustrating a risk alert implementation according to some embodiments of the present invention. As shown in FIG. 7, the risk alert flow may include the following: In some embodiments, the risk alert may be performed by the risk module 250.

In some embodiments, in response to a risk to worker income, the risk module 250 may issue an alert to the target user 710.

In some embodiments, if worker income in the target attendance table meets an alert condition, the risk module 250 may determine that worker income is at risk.

The alarm conditions may include at least the worker's income recorded in the target attendance table being greater than the distributable income, and/or the income for any one work recording day in the target attendance table not being within a first income interval, and/or the worker's daily income for any work recording day in the target attendance table not being within a second income interval.

Target users 710 refer to users who need to know that worker income is at risk. In some embodiments, target users may include first user 711 and/or second user 712.

The first user 711 is the manager of the workers. For example, the first user may be a group leader or team leader.

The second user 712 is the administrator of the first user. For example, the second user may be a subcontractor or a user corresponding to the prime contractor.

In some embodiments, the risk module 250 may communicate with a user terminal corresponding to the target user via a network and issue an alert to the target user in the form of voice, text, images, or other forms.

In some embodiments, in response to a risk to worker income, the risk module 250 may determine a risk type 720 for the risk, determine a target user 710 to receive the risk alert based on the risk type 720, and send the risk alert to the target user 710.

In some embodiments, the risk module 250 may determine the risk type of a risk in various ways. For example, risks may be classified as high-level risk, medium-level risk, low-level risk, etc. based on a risk value, and the higher the worker income in the target attendance table exceeds a reference value, the higher the risk value. The reference value may include distributable income, a first income range, and/or a second income range.

In some embodiments, the risk module 250 may categorize risks into different types depending on the risk party.

In some embodiments, risk types may include worker income risk 730 and distributable income risk 740. Note that risk parties refer to parties associated with a risk. In some embodiments, risk parties may include workers, team leaders, etc.

In some implementations, if a worker's daily wage on any one work day exceeds the first income range, the risk is determined to be a risk caused by work time verification, the risk party is the worker, and the risk type is worker income risk. Furthermore, if a worker's daily wage on any one work day exceeds the first income range, it indicates that the worker's attendance hours do not match the daily wage on the attendance sheet. For example, a worker's attendance hours are 1 hour, and the daily wage on the attendance sheet is 10,000 yuan.

In some implementations, if the total daily wage exceeds the second income range, it is determined that the risk is a risk caused by daily wage verification, the risk party is the worker, and the risk type is worker income risk. Furthermore, if the total daily wage exceeds the second income range, it means that the worker's wage for one work day exceeds the worker's ability to complete the work. For example, a worker's wage for one work day is 10,000 yuan, but the worker is unable to complete the amount of work corresponding to his wage within one work day.

In some embodiments, if the total income on the attendance schedule is greater than the income to be distributed on the first related attendance schedule, it is determined that the risk is a risk caused by the total income verification, the risk party is the team leader, and the risk type is distributable income risk 420. Furthermore, when the total income on the attendance schedule exceeds the income to be distributed on the first related attendance schedule, it indicates that the total income on the attendance schedule submitted by the team leader has already exceeded the income available for distribution on the task corresponding to the attendance schedule. For example, the income available for distribution on the task corresponding to the attendance schedule is 1,000 yuan, but the total income on the attendance schedule submitted by the team leader is 10,000 yuan.

In some embodiments, the risk module 250 may determine that the target user 710 includes a first user 711 when the risk type 720 is worker income risk 730, and may determine that the target user 710 includes a second user 712 when the risk type 720 is distributable income risk 740.

In some embodiments, the risk module may determine that the work record information is at risk when the worker's daily wage on any one work day exceeds a first income interval, and may calculate an amount associated with the risk in the work record information. The risk module may determine that the risk in the work record information is a worker income risk when the amount associated exceeds a first impact threshold. Note that the first impact threshold may be preset based on past experience.

In some embodiments, the assessment module may determine that the work record information is at risk when the total income in the attendance schedule is greater than the distributable income in the associated checked task list, and may calculate an amount associated with the risk in the work record information. The risk module may determine the risk in the work record information as a distributable income risk 420 when the amount associated exceeds a second impact threshold. Note that the second impact threshold may be preset based on past experience.

In some embodiments, the assessment module may determine that the work record information is at risk in response to the daily wage exceeding the second income interval and calculate a monetary amount associated with the risk in the work record information. The risk module may determine that the risk in the work record information is a worker income risk when the monetary amount associated with the risk exceeds a third impact threshold. Note that the third impact threshold may be preset based on past experience.

By categorizing target users by risk type, it becomes possible to more clearly define the target users who receive alerts and to clarify the scope of responsibility.

Figure 8 is a flowchart illustrating wage payment management according to some embodiments of the present invention. As shown in Figure 8, the wage payment management flow may include the following: In some embodiments, the wage payment management flow may be performed by the risk module 250.

In some embodiments, in response to a worker's income failing the reasonableness verification, the risk module may determine a risk type, determine collateral information based on the risk type, and manage the flow of wage payments to the worker based on the collateral information.

In some embodiments, if the worker income in the target attendance table exceeds a reference value or is not within a reference value range, the risk module 250 may determine that the worker income has failed the reasonableness verification. The reference value may include at least one of the distributable income of the checked task list, the first income range of the worker income, and the second income range.

For a detailed explanation of distributable income, the first income range of worker income, and the second income range, please refer to the relevant explanation in Figure 6 of the present invention.

In some examples, risk types may include worker income risk and distributable income risk. For a more detailed description, see Figure 7 and its associated discussion.

In some embodiments, the risk module 250 may determine collateral information based on risk type.

The security information is reference information for determining whether wages will be paid. The security information may also include the security amount.

In some embodiments, the risk module 250 may manage the flow of wage payments to workers based on the collateral information. Illustratively, if the worker's income in the target attendance schedule does not exceed the collateral amount, the risk module 250 may send a risk advance request to the target user, and if the target user selects payment of the advance, pay the worker wages based on the target attendance schedule.

In some embodiments, the coverage information may include worker coverage information and team coverage information.

In some embodiments, the risk module 250 obtains worker guarantee information 810 in response to the risk type 720 being worker income risk 730; sends a risk advance request 830 to the first user 711 in response to the worker income risk 730 not exceeding the worker guarantee information 810; performs a wage payment operation based on the target attendance table in response to receiving the advance from the first user 711; refuses to perform a wage payment operation based on the target attendance table 560 in response to not receiving the advance from the first user 711; and refuses to perform a wage payment operation based on the target attendance table in response to the worker income risk 730 exceeding the worker guarantee information 810. In some embodiments, the wage payment operation includes determining whether to proceed to a wage payment flow operation, and after entering the wage payment flow, the system verifies a pay slip related to wage payment. In other embodiments, the wage payment operation may be determining whether to pay wages to workers.

The worker collateral information may be used to determine whether to perform a wage payment operation when the risk is a worker income risk. In some embodiments, the worker collateral information may be a predetermined advance amount. The risk module 250 may determine whether to perform a wage payment operation based on the relationship between the income amount and the advance amount related to the worker income risk.

In some embodiments, if the amount related to the worker income risk does not exceed the worker collateral information 510, this may indicate that the impact of the worker income risk is small and that the risk module 250 sends a risk advance request to the first user. The risk module 250 performs a wage payment operation based on the target attendance table in response to receiving the first user's advance, and refuses to perform a wage payment operation based on the target attendance table in response to not receiving the first user's advance.

If there is a risk to the worker's income, the first user will pay an advance of less than the amount of the worker guarantee information if he/she wishes to insure the risk, so that the risk module 250 can perform the wage payment operation. If he/she does not wish to insure the risk, he/she will refuse to pay the advance, indicating that he/she believes that the impact of the risk is too great to perform the wage payment operation based on the target attendance schedule.

The risk reimbursement request may be intended to present the first user or second user with a request to pay the reimbursement amount.

In some embodiments, if the amount associated with the worker income risk exceeds the worker guarantee information, this indicates that the impact of the worker income risk is significant and the risk module 250 may refuse to perform wage payment operations based on the target attendance schedule.

In some embodiments, the risk module 250 may obtain team collateral information 820 in response to the risk type 720 being distributable income risk 740, send a risk advance request 830 to the second user 712 in response to the distributable income risk 740 not exceeding the team collateral information 820, perform a wage payment operation based on the attendance table submitted by the first user in response to receiving an advance from the second user 712, refuse to perform a wage payment operation based on the target attendance table 560 in response to not receiving an advance from the second user, and refuse to perform a wage payment operation based on the target attendance table 560 in response to the distributable income risk 740 exceeding the team collateral information 820.

The team collateral information 610 may be used to determine whether to perform a wage payment operation when the risk is a distributable income risk. In some embodiments, the team collateral information 610 may be a predetermined advance amount. The risk module 250 may determine whether to perform a wage payment operation based on the relationship between the amount related to the distributable income risk and the advance amount in the team collateral information. See the related description below for an explanation of how the team collateral information 610 is determined.

In some embodiments, if the amount related to the distributable income risk does not exceed the team security information 610, the impact of the distributable income risk is small, and the risk module 250 may transmit a risk advance request to the second user. The risk module 250 may perform a wage payment operation based on the target attendance table in response to receiving an advance from the second user, and may refuse to perform a wage payment operation based on the target attendance table in response to not receiving an advance from the second user.

In addition, if there is a distributable income risk, if the second user wants to insure the risk, he or she will pay an advance of less than the amount of the team guarantee information so that the risk module 250 can perform the wage payment operation; if he or she does not want to insure the risk, he or she will refuse to pay the advance, indicating that he or she believes the impact of the risk is too great to perform the wage payment operation based on the target attendance schedule.

In some embodiments, an amount related to distributable income risk exceeding the team collateral information 610 may indicate that the impact of distributable income risk is significant and that the risk module 250 will refuse to perform wage payment operations based on the target attendance schedule.

In some embodiments, the risk module 250 sends a risk reimbursement request to the first user or the second user if the amount of the advance is less than the worker collateral information or the team collateral information, and does not send a risk reimbursement request to the first user or the second user and directly refuses to execute the wage payment operation if the amount of the advance is greater than the worker collateral information or the team collateral information.

In some embodiments, the amount associated with worker income risk or the amount associated with distributable income may be intended to represent the magnitude of the risk. The higher the amount involved, the greater the risk.

In some embodiments, in response to a worker's daily income on any one work record day exceeding the first income interval, the risk module 250 may determine the portion of the daily income that exceeds the first income interval and determine the amount of this portion as the amount associated with the worker income risk.

In some embodiments, in response to the worker income according to the target attendance table being greater than the distributable income of the checked task list, the risk module 250 may determine the portion by which the worker income exceeds the distributable income and determine the amount of this portion as the amount related to the distributable income risk.

In some embodiments, if the worker's total daily wages exceed the second revenue interval, the risk module 250 may determine the portion of the total daily wages that exceeds the second revenue interval and determine the amount of this portion as the amount associated with the worker's income risk.

In some embodiments of the present invention, the degree of risk is determined based on the amount of risk involved, and the execution of wage payment operations is refused if the degree of risk exceeds the range included in the collateral information, making wage payment decisions more intelligently and efficiently according to actual conditions, reducing human interference and process delays, and favoring standardized and scientific management of the wage payment process.

In some embodiments, the risk module 250 may dynamically adjust the worker commitment information and the team commitment information in various ways. For example, the risk module 250 may periodically obtain an adjustment value for the worker commitment information by a first user and an adjustment value for the team commitment information by a second user, and adjust the worker commitment information and the team commitment information based on the respective adjustment values.

In some embodiments, the risk module 250 may dynamically adjust worker coverage information and team coverage information depending on risk behavior.

Risk behavior refers to actions by workers or team leaders that create or ignore target attendance schedule risks. Creating target attendance schedule risks refers to actions such as inaccurately recording attendance information, inaccurately recording attendance schedules, or falsifying documents, which pose a risk to the target attendance schedule. Releasing risk refers to providing collateral to workers or paying an advance payment when there is a risk to the worker's income at the target attendance schedule terminal.

In some embodiments, the worker guarantee information and the team guarantee information may be preset to initial values. In response to the worker income risk or the distributable income risk in the target attendance schedule, the risk module 250 may adjust the worker guarantee information and the team guarantee information using Equation (10) and Equation (11).
Eg=E1+E3 Formula (10)
Eb=E2+E3 Equation (11)

Here, Eg and Eb represent the adjusted worker guarantee information and adjusted team guarantee information, E1 and E2 represent the initial values of the worker guarantee information and the initial values of the team guarantee information, respectively, and E3 represents the adjustment coefficient for dynamic adjustment. Note that the adjustment coefficients include the real risk coefficient, non-real risk coefficient, and positive coefficient.

In some embodiments, the real risk coefficient and the non-real risk coefficient may be less than 0, and the positive coefficient may be greater than 0. The real risk coefficient, the non-real risk coefficient, and the positive coefficient may be predetermined based on past experience and may be expressed in the form of a number, percentage, function, etc.

In some embodiments, when a worker or team leader initiates a risky behavior (i.e., there is worker income risk or distributable income risk in the work record information) and the first user or second user wishes to make an advance payment, the above formulas (10) and (11) may be the actual risk coefficients so as to reduce the size of the worker collateral information or team collateral information.

Furthermore, if a worker or team leader commits a risky act, the worker or team leader's credibility declines, the size of the worker guarantee information or team guarantee information needs to be reduced, and the first or second user wishes to pay an advance, the risk in this case is confirmed by the first or second user, the wage payment operation is executed (actual result), and the risk is an actual risk.

In some embodiments, the above equations (10) and (11) may be non-substantial risk coefficients to reduce the size of the worker security information or team security information if a worker or team leader causes a risky behavior but the first user or second user refuses to pay the advance.

In addition, if a worker or team leader commits a risky act, the worker or team leader's credibility declines, the size of the worker guarantee information or team guarantee information needs to be reduced, and the first or second user refuses to pay the advance, the risk in this case will be confirmed and rejected by the first or second user, the wage payment operation will not be executed (no actual result), and the risk will be considered a non-real risk.

In some embodiments, if a worker or team leader does not commit another risky act within a certain period of time after committing a risky act, E3 in the above equations (10) and (11) may be a positive coefficient so as to increase the size of the reduced worker guarantee information or team guarantee information without exceeding the initial value of the worker guarantee information or team guarantee information. Furthermore, if a worker or team leader does not commit a risky act within a certain period of time, the worker or team leader's trustworthiness may increase, and the worker guarantee information or team guarantee information may be gradually restored.

In some embodiments, worker commitment information or team commitment information is adjusted so as not to exceed an initial value.

In some embodiments, worker commitment information and team commitment information are dynamically adjusted based on risk behavior, and when adjusting the worker commitment information and team commitment information, the actual situation of the corresponding workers and teams is taken into consideration, thereby further improving the accuracy of the worker commitment information and team commitment information.

In some embodiments of the present invention, collateral information can be periodically adjusted based on the target user's risky behavior to better ensure the time validity of collateral information. This avoids a situation where a target user has a high collateral limit despite having engaged in multiple risky behaviors, or a situation where the collateral limit remains unchanged even though the target user is able to regulate their own behavior, which is advantageous for more accurate collateral limit allocation and ensures standardization of wage payment management flow.

In some embodiments, the risk module 250 may, in response to refusing to perform a wage payment operation based on the target attendance schedule, send a modification request to the first user and obtain a modified attendance schedule from the first user.

In some embodiments, the risk module 250 may determine the correction content of the work record information based on the risk type and may recommend suggested correction information to the first user. The suggested correction information may be used to present to the first user the parts of the attendance schedule that need to be corrected. The correction content may include corrections to daily wages, total income, working hours, etc.

For example, in response to the risk type being distributable income risk, the risk module 250 may determine that the content of the work record information that needs to be corrected is total income, and may recommend to the first user presented information that requires correction of total income.

In some embodiments, after refusing to execute the wage payment operation, feedback is provided to the first user to revise the attendance sheet, and suggested revisions are recommended, thereby immediately updating any content that could lead to risk and preventing the risk situation from continuing.

Figure 9 is a flowchart for determining a target pay slip in accordance with some embodiments of the present invention. As shown in Figure 9, the flow for determining a target pay slip may include the following: In some embodiments, the flow for determining a target pay slip may be performed by the report determination module 230.

In some embodiments, in response to the input report 510 not including a pay slip 910, the report determination module 240 may automatically create a target pay slip 940 based on the checked task list 350, the checked attendance sheet 440, and the target attendance sheet 560.

Pay slip 910 is a document that records the payroll information of a worker. Pay slip 910 may record at least the status of the payroll to be paid to the worker, payroll deductions, bonuses, labor costs, etc. Labor costs are the actual payroll paid to the worker. In some embodiments, the pay slip directly records the task items or minimum production units included in the payroll in the document. In other embodiments, the pay slip may be associated with the task items or minimum production units in a data-associating manner.

The target pay slip 940 is a pay slip whose authenticity can be verified. In some embodiments, the target pay slip 940 may be the final basis for paying wages to workers.

In some embodiments, the form determination module 240 may determine target data for creating a target pay statement based on the checked task list, checked attendance sheet, and target attendance sheet. For example, it may obtain data such as a worker's minimum production unit, payment method, and labor cost from the checked task list, obtain data such as actual construction period, attendance record, and entry qualifications from the checked attendance sheet, obtain data such as work volume, labor costs, and accounting period from the target attendance sheet, and determine the obtained data as target data. The form determination module may automatically create a pay statement based on the target data.

In some embodiments, the ledger determination module 230 may automatically generate an accounting period based on the checked attendance sheet. For example, the ledger determination module 230 may obtain data such as the actual construction period, working hours, and entry qualifications from the checked attendance sheet, and automatically generate an accounting period based on the actual construction period, worker working hours, and entry qualifications. By way of example only, if the actual construction period is from March to June and the pre-set accounting period is to pay salaries once a month, the relevant workers must be paid from April to July. In the above situation, if a worker has entry permission from March to May and his working hours are concentrated in March and April, April and May may be automatically determined as the accounting period for this worker.

In some embodiments, the ledger determination module 230 may automatically create a target pay slip based on the target attendance schedule and accounting period. For example, the ledger determination module 230 obtains the worker's workload and labor costs from the target attendance schedule, calculates the total labor costs to be paid this month, obtains the balance data of the worker's dedicated salary account from the related fund management system, and if the balance in the dedicated account is greater than the total labor costs to be paid this month, automatically creates a pay slip to be paid this period. If the balance in the dedicated account is less than the total labor costs to be paid this month, it sorts the attendance schedules according to their creation date, and labor costs with older dates are paid first.

By automatically creating a target pay slip based on the checked task list, checked time sheet, and target attendance sheet, human interference is reduced and the determined target pay slip is more accurate and objective.

In some embodiments, in response to the input form 510 including a pay slip 910, the form determination module 230 may perform a pay slip check 920 based on the checked task list 350, the checked attendance sheet 440, and the target attendance sheet 940, and may determine the pay slip 910 as the target pay slip 940 in response to the check result of the pay slip check 920 satisfying the fourth preset condition 930.

In some embodiments, the report determination module 230 may communicate with the report acquisition module 210 to obtain a pay slip. The pay slip in the report acquisition module 210 is obtained through user input. By way of example only, the user may include a construction item manager, personnel responsible for worker attendance and payroll, etc. In some embodiments, the user may be the first user.

In some embodiments, the fourth preset condition may include that the pay slip is authentic and reasonable.

In some embodiments, in response to the input document including a pay slip, the document determination module 230 may determine pay slip-related data for checking the pay slip based on the checked task list, checked attendance sheet, and target attendance sheet, and may check the pay slip in accordance with the accounting period.

An accounting period refers to the time period over which workers are paid. In some embodiments, an accounting period may include at least one wage payment cycle. Typically, one cycle is one month, but other periods may be used as one cycle depending on the actual situation.

Pay slip-related data is data used to check pay slips.

In some embodiments, payslip-related data may include minimum production units, payment types, labor costs, actual construction time, worker hours, entry permits, worker workload, and expected payment amounts.

In some embodiments, the ledger determination module 230 may obtain pay slip-related data based on the checked task list, checked attendance sheet, and target attendance sheet. For example, the ledger determination module 230 may obtain information such as the minimum production unit, payment method, and labor cost based on the checked task list, obtain information such as actual construction period, attendance hours, and entry permission based on the checked attendance sheet, and obtain work volume, expected payment amount, and the like based on the target attendance sheet.

For a detailed explanation of how the checked task list, checked time sheet, and target attendance sheet are determined, please refer to the related descriptions of Figures 3 to 5 of the present invention.

In some embodiments, the ledger determination module 230 may check the pay slip based on the pay slip-related data and the accounting period. For example, the ledger determination module 230 may check the above pay slip based on the pay slip-related data within the accounting period. By way of example only, the ledger determination module 230 determines the worker's reference salary based on the checked attendance time and labor cost in the pay slip-related data, and if the difference between the salary amount in the pay slip and the reference salary is smaller than a preset threshold, the pay slip check is passed. Note that the preset threshold represents a reasonable range of the difference between the above salary amount and the reference salary, and may be set according to actual needs.

In some embodiments, the pay slip check includes at least one of an expense authenticity check, a reasonableness check, and a relevance check of pay slip-related data.

Checking the authenticity of expenses refers to checking the authenticity of personnel expenses on a pay slip. As an example, personnel expenses on a pay slip are usually the sum of personnel expenses that should be paid in the current period and personnel expenses that have not been paid in the past. If the above conditions are not met, the personnel expenses will not be considered authentic.

The labor cost to be paid this period refers to the labor cost to be paid to the worker in the current accounting period. In some embodiments, the labor cost to be paid this period may be determined based on the checked attendance sheet for the current accounting period and the checked task list for the current accounting period. For example, the number of recorded work days for the worker may be determined based on the checked attendance sheet for the current accounting period, the daily labor cost may be determined based on the checked task list for the current accounting period, and the labor cost to be paid for the current accounting period may be determined based on the number of recorded work days and the daily labor cost.

Labor costs not paid in the past refer to the total labor costs that should have been paid to workers in at least one past accounting period. The labor costs not paid in each past accounting period are determined by the checked attendance sheet for the past accounting period and the checked task list for the past accounting period, and the past accounting period may be determined by the target attendance sheet. The specific method for determining the labor costs not paid in each past accounting period is similar to the method for determining the labor costs that should be paid in the current period, and reference may be made to the related explanations above.

Checking the reasonableness of costs refers to checking the reasonableness of labor costs on pay slips. As an example only, labor costs on pay slips should be at least equal to the product of the number of days a worker is recorded working and the minimum labor cost per day. If the above condition is not met, the labor costs are not reasonable.

The number of days a worker is recorded working may be determined by the checked attendance sheet, and the minimum labor cost per day may be determined by the checked task list.

A correlation check for pay slip-related data refers to checking the correlation between the checked task list, checked attendance sheet, and target attendance sheet to determine the pay slip-related data. As an example only, if the checked task list, checked attendance sheet, and target attendance sheet are data for the same worker and do not meet the above conditions, it is determined that the pay slip-related data does not meet the correlation requirements and the authenticity of the pay slip-related data is questionable.

The correlation between the checked task list, checked attendance sheet, and target attendance sheet is determined by whether their shared data matches; if the shared data matches, there is a correlation. For example, the checked task list, checked attendance sheet, and target attendance sheet all include the minimum production unit. If the planned construction period data in the checked task list, the actual construction period data in the checked attendance sheet, and the work record date data in the checked attendance sheet theoretically match, the correlation between the checked task list, checked attendance sheet, and target attendance sheet is determined based on whether the similarity of the above data meets the requirements; if the similarity is greater than a preset similarity threshold, there is a correlation. The similarity threshold may be determined according to actual needs.

In some embodiments, in response to the result of the pay slip check satisfying the fourth preset condition, the form determination module 230 determines the pay slip entered in the form as the target pay slip and sets the target pay slip as the final certificate of wage payment.

In some embodiments, if the pay slip check results in the pay slip not meeting the authenticity criteria, the document determination module 230 may issue a control command to block the flow of wage payments. Note that a determination result that does not meet the authenticity criteria may include a case where the labor costs do not meet the authenticity criteria, or a case where the pay slip-related data does not meet the correlation requirements.

In some embodiments, if the pay slip check results in the pay slip not meeting the reasonableness criteria, the report determination module 230 may issue an alarm signal and generate and present to the user an adjustment instruction to proofread the pay slip. If the initial pay slip after proofreading is again determined to be unreasonable, a control instruction may be issued to prevent the flow of wage payments.

Construction management typically involves creating a payroll ledger based on attendance data and paying wages. However, the pay slips obtained in this manner do not have a data basis, so paying wages based solely on attendance data can lead to a variety of problems, such as data falsification and unclear work volumes.

In some embodiments of the present invention, a target pay slip is determined or a pay slip is checked based on the checked task list, checked time sheet, and target attendance sheet. This process allows each data entry to be traced back and repeatedly appear at different stages, ensuring that the data is related and verified in stages to better ensure the authenticity and reasonableness of the data in the target pay slip.

Having thus described the basic concepts, it will be apparent to those skilled in the art that the above detailed disclosure is intended to be presented by way of example only, and not by way of limitation. Although not expressly described herein, those skilled in the art may make various changes, improvements, and modifications to the present specification. These changes, improvements, and modifications are intended to be suggested by the present specification and are within the spirit and scope of the illustrative examples herein.

Furthermore, certain terms are used herein to describe embodiments of the present invention. For example, the terms "one embodiment," "one embodiment," and/or "some embodiments" refer to particular features, structures, or characteristics of at least one embodiment of the present invention. Accordingly, it is emphasized and understood that two or more references to "one embodiment," "one embodiment," or "one alternative embodiment" in various parts of this specification do not necessarily all refer to the same embodiment. Furthermore, particular features, structures, or characteristics may be combined as appropriate in one or more embodiments of this specification.

Furthermore, unless expressly stated in the claims, the order of processing elements and sequences described herein, the use of numbers, letters, or other designations are not intended to limit the order of the processes and methods herein. While the above disclosure discusses certain embodiments of the invention that are presently considered useful through various examples, it should be understood that such details are for illustrative purposes only, and that the appended claims are not limited to the disclosed embodiments; on the contrary, the claims are intended to cover all modifications and equivalent combinations consistent with the spirit and scope of the embodiments herein. For example, the system assembly described above can be implemented by a hardware device, but can also be implemented solely by a software solution, such as by installing the described system on an existing server or mobile device.

It should also be noted that, to simplify the disclosure herein and facilitate understanding of one or more embodiments of the invention, the preceding description of the embodiments herein may group various features together in a single embodiment, drawing, or description thereof. However, this method of disclosure does not imply that the subject matter of this disclosure requires more features than are recited in the claims. In fact, an embodiment may have fewer features than all of the features of a single embodiment disclosed above.

In some examples, numbers are used to describe the quantities of components and attributes. It should be understood that such numbers used to describe the examples are, in some instances, modified using the modifiers "about," "approximately," or "approximately." Unless otherwise specified, "about," "approximately," or "approximately" indicate that the number may vary by ±20%. Correspondingly, in some examples, all numerical parameters used in the specification and claims are approximations, and such approximations may vary based on the characteristics required for a particular example. In some examples, numerical parameters must be calculated using the specified number of significant digits and by employing common digit constraints. While the numerical ranges and parameters used to ascertain the breadth of ranges in some examples herein are approximations, in specific examples, such numerical values are set as precisely as practicable.

Each patent, patent application, patent application disclosure, and other material, including but not limited to articles, books, specifications, publications, and documents, cited herein is hereby incorporated by reference in its entirety, excluding any filing history documents that are inconsistent or contradictory with the contents of this specification, as well as any documents (now or hereafter added to this specification) that contain limitations on the broadest scope of the claims herein. To the extent that statements, definitions, and/or terminology in the accompanying materials are inconsistent or contradictory with the contents of this specification, the statements, definitions, and/or terminology in this specification shall control.

Finally, it should be understood that the examples described herein are used only to illustrate the principles of the examples herein. Other variations may fall within the scope of the present specification. Thus, by way of example, not limitation, alternative arrangements of the examples herein may be considered consistent with the teachings of the present specification. Correspondingly, the examples herein are not limited to those specifically introduced and described herein.

Claims (14)

A construction management system including a server, which manages a project using a task list created before each task is executed and a time sheet created after each task is executed ,
The processing device of the server
Report acquisition module,
Report check module,
Form determination module,
and,
Risk Module
Equipped with the functions of
the form acquisition module acquires an input form including at least the task list and the attendance record;
The form check module extracts predetermined information from the checklist as internal task list data, performs a first verification to compare the extracted internal task list data with a preset association relationship, and sets the data obtained by the first verification as a checked task list, extracts predetermined information from the attendance sheet as work record information, and if the input form does not include an attendance sheet, performs a second verification to check whether the checked task list, the work record information, and predetermined payroll information satisfy preset conditions, and sets the data obtained by the second verification as a checked attendance sheet.
When the input form does not include an attendance sheet, the form determination module determines a target attendance sheet including a worker income, which is the income of each worker, based on the checked task list and the checked attendance sheet;
The risk module obtains the worker's income from the target attendance table, calculates a first income range, which is a range of daily wages, based on the checked task list and the checked attendance table, checks whether the worker's income is within the first income range, and if the worker's income is not within the first income range, determines that the worker's income recorded in the target attendance table is at risk.
A construction management system characterized by: The document check module further
obtaining first verification data for the task list, including task list internal data;
The construction management system according to claim 1, characterized in that a task list check is performed based on the first verification data, and a checked task list is determined in response to the result of the task list check satisfying a first predetermined condition. The construction management system described in claim 2, characterized in that performing the task list check based on the first verification data includes performing a first verification on the task list based on a preset association relationship and the task list internal data. The construction management system described in claim 3, characterized in that the pre-set association relationships include at least one of the following: a relationship between a worker and a job type, a relationship between a task item and a job type, a relationship between a job type and labor cost, and a relationship between an item and an area. The first verification data further includes external related data of the task list;
The construction management system of claim 3, wherein checking the task list based on the first verification data further includes performing a second verification on the task list based on the external related data and the task list internal data. The document check module
Obtain second verification data, check the attendance record based on the second verification data, and determine the checked attendance record according to the check result satisfying the second predetermined condition;
the second verification data includes at least the checked task list;
4. The construction management system according to claim 3, wherein the checked task list is at least a task list that has passed the first verification. The second verification data further includes work record information and payroll information related to the checked task list;
The construction management system of claim 6, characterized in that checking the attendance sheet based on the second verification data includes checking the attendance sheet based on the checked task list, the work record information, and the salary information. The form determination module further
In response to the fact that the input form does not include an attendance sheet, the target attendance sheet is automatically created based on the checked task list and the checked attendance sheet;
In response to the input form including the attendance sheet, checking the attendance sheet based on the checked task list and the checked attendance sheet;
The construction management system according to claim 1, wherein the target schedule is determined in response to the result of the schedule check satisfying a third preset condition. The check of the attendance list includes checking the authenticity of the attendance list;
The construction management system according to claim 8, wherein the authenticity check of the attendance table includes at least one of a project authenticity check, a quantity price authenticity check, and a time authenticity check. further including an evaluation module;
The construction management system of claim 9 , wherein the evaluation module is configured to verify whether there is a risk to worker income in the target attendance schedule. Verifying whether there is a risk to the worker's income in the target attendance schedule includes:
determining a first income interval for the worker for at least one work record date based on the checked task list and the checked time sheet;
The construction management system of claim 10, further comprising determining that the worker income recorded in the target attendance table is at risk in response to the income of any one work record day in the target attendance table not being within the first income interval. Verifying whether there is a risk to the worker's income in the target attendance schedule includes:
determining distributable income based on the checked task list;
The construction management system of claim 10, further comprising: determining that there is a risk in the worker income recorded in the target attendance table in response to the worker income in the target attendance table being greater than the distributable income. The form determination module further
When the input form does not include a pay slip, the target pay slip is automatically created based on the checked task list, the checked attendance sheet, and the target attendance sheet;
The construction management system of claim 8, characterized in that, in response to the input document including the pay slip, a pay slip check is performed based on the checked task list, the checked attendance sheet, and the target attendance sheet, and in response to the result of the pay slip check satisfying a fourth predetermined condition, the target pay slip is determined. The construction management system according to claim 13 , wherein the pay slip check includes at least one of a cost authenticity check, a cost reasonableness check, and a correlation check of pay slip related data.