CN111428974A - Audit audit job scheduling method and device - Google Patents

Audit audit job scheduling method and device Download PDF

Info

Publication number
CN111428974A
CN111428974A CN202010171871.5A CN202010171871A CN111428974A CN 111428974 A CN111428974 A CN 111428974A CN 202010171871 A CN202010171871 A CN 202010171871A CN 111428974 A CN111428974 A CN 111428974A
Authority
CN
China
Prior art keywords
audit
data model
task
processed
suspicious
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010171871.5A
Other languages
Chinese (zh)
Inventor
杨君
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Taikang Insurance Group Co Ltd
Original Assignee
Taikang Insurance Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Taikang Insurance Group Co Ltd filed Critical Taikang Insurance Group Co Ltd
Priority to CN202010171871.5A priority Critical patent/CN111428974A/en
Publication of CN111428974A publication Critical patent/CN111428974A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311Scheduling, planning or task assignment for a person or group
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12Accounting
    • G06Q40/125Finance or payroll

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses an audit operation scheduling method and device, and relates to the technical field of computers. The method comprises the following steps: after receiving an audit task to be processed submitted by a user terminal, acquiring the number of suspicious records under each audit data model in the audit task to be processed; determining the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal; and after receiving a personnel scheduling request corresponding to the audit task to be processed, which is sent by the user terminal, generating a personnel scheduling list for executing the audit task to be processed, and returning the personnel scheduling list to the user terminal. Through the steps, personnel scheduling and distribution can be automatically and reasonably performed on the audit task to be processed, and the working efficiency of the whole audit operation is improved.

Description

Audit audit job scheduling method and device
Technical Field
The invention relates to the technical field of computers, in particular to an audit operation scheduling method and device.
Background
With the progress of data science and application technology, companies, organizations and social organizations conform to the background of the big data era, actively innovate and reform businesses, and promote informatization and digital development. Currently, audit work needs to not only face to a voucher and a report form in a practical form, but also investigate a large amount of data and related records integrated by an information system according to the requirement of organizing audit matters, obtain information clues and make business judgment.
The auditing and auditing work is mainly divided into two parts of on-site auditing and off-site auditing. When off-site auditing is carried out, auditing data models are required to be operated on each transaction service system data of an audited organization, the output results of the auditing data models are generally hit results of illegal operation of the audited organization, and if the specific service data of the audited organization have hit results in the auditing data models, an auditor can carry out on-site auditing aiming at the audited organization and regress the specific hit records of the audited organization operation on-site.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: firstly, in the prior art, when the scheduling of the auditors is performed for the audit task, the scheduling scheme of the auditors is determined subjectively based on human experience, for example, several auditors are allocated to the audit task, and the method has the defects of unreasonable scheduling of the auditors, low resource allocation efficiency and the like.
Disclosure of Invention
In view of the above, the invention provides an audit task scheduling method and device, which can automatically and reasonably schedule and distribute personnel for an audit task to be processed, and improve the work efficiency of the whole audit task.
To achieve the above object, according to one aspect of the present invention, an audit trail scheduling method is provided.
The audit operation scheduling method comprises the following steps: after receiving an audit task to be processed submitted by a user terminal, acquiring the number of suspicious records under each audit data model in the audit task to be processed; determining the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal; and after receiving a personnel scheduling request corresponding to the audit task to be processed, which is sent by the user terminal, generating a personnel scheduling list for executing the audit task to be processed, and returning the personnel scheduling list to the user terminal.
Optionally, the determining the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record includes: multiplying the number of suspicious records under an audit data model by the processing time required by a single suspicious record under the model to obtain the workload corresponding to the audit data model; and taking the sum of the workload corresponding to each audit data model in the audit task to be processed as the total workload of the audit task to be processed.
Optionally, the processing time required for the single suspicious record is obtained according to the following manner: acquiring log data of a plurality of historical audit tasks; wherein the log data of the historical audit task comprises: the number of suspicious records under each audit data model in the historical audit task and the actual time consumption for processing all suspicious records in a single audit data model; determining the actual time consumption for processing the single suspicious record under the audit data model according to the number of the suspicious records in the single audit data model in a historical audit task and the actual time consumption for processing all the suspicious records in the audit data model; and calculating the average value of the actual time consumption of processing the single suspicious record under the audit data model in the plurality of historical audit tasks, and taking the average value as the processing time required by the single suspicious record under the audit data model.
Optionally, the generating a staff scheduling list for executing the to-be-processed audit task includes: target completion time limit information of the audit task to be processed is analyzed from the personnel scheduling request; and scheduling personnel according to the target completion time limit information and the information of the auditors to be distributed so as to obtain a personnel scheduling list for executing the audit tasks to be processed.
Optionally, the performing staff scheduling planning according to the target completion time limit information and the information of the auditors to be allocated to obtain a staff scheduling list for executing the audit task to be processed includes: traversing an audit data model in the audit task to be processed; for each audit data model, inquiring the information of auditors to be distributed according to the audit data model identification to obtain the information of the auditors capable of processing the suspicious records under the audit data model; wherein, the auditor information capable of processing the suspicious records under the audit data model comprises: the audit personnel identification of the suspicious records under the audit data model can be processed, and the actual time consumption for processing the single suspicious records under the audit data model by the audit personnel is reduced; determining the auditors distributed to the audit data model according to the auditor information capable of processing the suspicious records under the audit data model and the target completion time limit information; and generating a personnel scheduling list for executing the audit task to be processed according to the information of the auditors distributed to each audit data model.
Optionally, the method further comprises: after the step of returning the information of the total workload to the user terminal, receiving a modified audit task submitted by the user terminal; acquiring the number of suspicious records under each audit data model in the modified audit task; and determining the total workload of the modified audit task according to the number of the suspicious records under each audit data model in the modified audit task and the processing time required by a single suspicious record, and returning the information of the total workload of the modified audit task to the user terminal.
Optionally, the obtaining the number of suspicious records under each audit data model in the audit task to be processed includes: and operating each audit data model in the audit task to be processed aiming at the service data of the audited organization to obtain the number information of the suspicious records under each audit data model.
To achieve the above object, according to another aspect of the present invention, an audit trail scheduling apparatus is provided.
The audit operation scheduling device of the invention comprises: the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring the number of suspicious records under each audit data model in an audit task to be processed after receiving the audit task to be processed submitted by a user terminal; the determining module is used for determining the total workload of the audit task to be processed according to the number of the suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal; and the generating module is used for generating a personnel scheduling list for executing the audit task to be processed after receiving a personnel scheduling request which is sent by the user terminal and corresponds to the audit task to be processed, and returning the personnel scheduling list to the user terminal.
To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.
The electronic device of the present invention includes: one or more processors; and storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize the audit trail operation scheduling method.
To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable medium.
The computer readable medium of the present invention has stored thereon a computer program that, when executed by a processor, implements the audit trail job scheduling method of the present invention.
One embodiment of the above invention has the following advantages or benefits: after receiving the audit task to be processed submitted by the user terminal, the suspicious records under each audit data model in the audit task to be processed are obtained, determining the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal, after receiving a personnel scheduling request corresponding to the audit task to be processed and sent by the user terminal, generating a personnel scheduling list for executing the audit task to be processed, and the personnel scheduling list is returned to the user terminal, so that personnel scheduling and distribution can be automatically and reasonably performed aiming at the audit task to be processed, and the working efficiency of the whole audit operation is improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic flow chart of a scheduling method for audit trail operations according to a first embodiment of the present invention;
FIG. 2 is a schematic flow chart illustrating a scheduling method of audit trail operations according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram of the main modules of an audit trail operation scheduling device according to a third embodiment of the present invention;
FIG. 4 is a schematic diagram of the main modules of an audit trail operation scheduling device according to a fourth embodiment of the present invention;
FIG. 5 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
FIG. 6 is a schematic block diagram of a computer system suitable for use with the electronic device to implement an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
FIG. 1 is a schematic diagram of a main flow of an audit trail operation scheduling method according to a first embodiment of the present invention. As shown in fig. 1, the audit task scheduling method in the embodiment of the present invention includes:
step S101, after receiving an audit task to be processed submitted by a user terminal, acquiring the number of suspicious records under each audit data model in the audit task to be processed.
Wherein the pending audit task may relate to one or more audit data models. The audit data model is used for analyzing the business data of the audited organization to find out or hit suspicious records in the business data. For example, a certain audit task to be processed relates to three audit data models, namely an audit data model a, an audit data model B and an audit data model C, wherein the number of suspicious records in the order of the audit data model a is 100, the number of suspicious records in the order of the audit data model B is 50, and the number of suspicious records in the order of the audit data model C is 35.
In an optional embodiment, the obtaining the number of suspicious records under each audit data model in the audit task to be processed may include: and operating each audit data model in the audit task to be processed aiming at the service data of the audited organization to obtain the number information of the suspicious records under each audit data model. In specific implementation, an audit task initiator can set an audit data model to be called by the audit work and information of an audited organization aiming at the audit work on an audit portal website or an APP on a user terminal, and then submit the information to an audit operation scheduling device in a mode of waiting for processing the audit task, and then the audit operation scheduling device can operate the data models aiming at service data of the audited organization to obtain the number information of suspicious records under each audit data model.
In another optional embodiment, the obtaining the number of suspicious records under each audit data model in the audit task to be processed may include: and querying a database according to the identifier of the audit task to be processed to obtain the number of suspicious records under each audit data model in the audit task to be processed. In specific implementation, one or more audit data models can be operated aiming at the service data of an audited organization in advance to obtain the number information of suspicious records under each audit data model, and the audit task identifiers and the number information of the suspicious records under the audit data models are correspondingly stored in the database. After receiving the to-be-processed audit task submitted by the audit task initiator, inquiring the database according to the identifier of the to-be-processed audit task to obtain the number of suspicious records under each audit data model in the to-be-processed audit task.
Step S102, determining the total workload of the audit task to be processed according to the number of the suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal.
Exemplarily, step S102 may specifically include: multiplying the number of suspicious records under an audit data model by the processing time required by a single suspicious record under the model to obtain the workload corresponding to the audit data model; and taking the sum of the workload corresponding to each audit data model in the audit task to be processed as the total workload of the audit task to be processed.
For example, assuming that a certain to-be-processed audit task relates to the audit data model A, B, C, the number of suspicious records in the audit data model a is 100, the number of suspicious records in the audit data model B is 50, the number of suspicious records in the audit data model C is 35, the processing time required for a single suspicious record under the audit data model a is 1 minute, the processing time required for a single suspicious record under the audit data model B is 2 minutes, and the processing time required for a single suspicious record under the audit data model C is 3 minutes, the workload corresponding to the audit data model A, B, C is 100 minutes, and 105 minutes, respectively, and the total workload of the to-be-processed audit task is 305 minutes.
In the embodiment of the invention, the total workload of the audit task can be quickly and accurately evaluated according to the type of the audit data model called by the audit task to be processed, the number of suspicious records under each audit data model and the processing time required by a single suspicious record under each type of audit data model. Furthermore, according to the calculated total workload of the audit task, the reasonability of subsequent personnel configuration management is improved.
Step S103, after receiving a personnel scheduling request corresponding to the audit task to be processed and sent by the user terminal, generating a personnel scheduling list for executing the audit task to be processed, and returning the personnel scheduling list to the user terminal.
In specific implementation, after the user terminal receives the information of the total workload sent by the audit task scheduling device, the initiator of the audit task can judge whether the workload of the audit task is controllable or not based on the information of the total workload. When the auditing task initiator confirms that the total workload of the auditing task is controllable, a personnel scheduling request aiming at the auditing task can be initiated through an auditing portal website on a user terminal.
After the audit operation scheduling device receives the personnel scheduling request aiming at the audit task, personnel scheduling planning can be carried out through a preset iterative algorithm so as to obtain a personnel scheduling planning result. Illustratively, the personnel scheduling planning result may include: the number of persons required to be equipped, the specific person identification (such as job number, name and the like) of the equipment, the expected time length required for each person to complete the respective work and the like are checked against the suspicious records in each audit model. And then, generating a personnel scheduling list for executing the audit task to be processed according to a personnel scheduling planning result, and returning the personnel scheduling list to the user terminal.
In the embodiment of the invention, after receiving the to-be-processed audit task submitted by a user terminal, the number of suspicious records under each audit data model in the to-be-processed audit task is obtained, and the total workload of the to-be-processed audit task is determined according to the number of the suspicious records under each audit data model in the to-be-processed audit task and the processing time required by a single suspicious record, so that the workload of the audit task can be quickly and accurately evaluated; furthermore, by returning the information of the total workload to the user terminal, an audit task initiator can conveniently and accurately judge whether the workload of the audit task is controllable or not; further, the steps of receiving the personnel scheduling request which is sent by the user terminal and corresponds to the to-be-processed audit task, generating a personnel scheduling list for executing the to-be-processed audit task, and returning the personnel scheduling list to the user terminal can be used for automatically and reasonably scheduling and distributing personnel for the to-be-processed audit task, so that the working efficiency of the whole audit task is improved.
FIG. 2 is a schematic diagram illustrating a main flow of an audit trail operation scheduling method according to a second embodiment of the present invention. As shown in fig. 2, the audit task scheduling method in the embodiment of the present invention includes:
step S201, the user terminal submits the audit task to be processed.
Wherein the pending audit task may relate to one or more audit data models. The audit data model is used for analyzing the business data of the audited organization to find out or hit suspicious records in the business data. For example, a certain audit task to be processed relates to three audit data models, namely an audit data model a, an audit data model B and an audit data model C, wherein the number of suspicious records in the order of the audit data model a is 100, the number of suspicious records in the order of the audit data model B is 50, and the number of suspicious records in the order of the audit data model C is 35.
In specific implementation, an audit task initiator can set an audit data model to be called by the audit work and information of an audited organization aiming at the audit work on an audit portal or APP on a user terminal, and then submit the information to an audit operation scheduling device in a mode of waiting for processing the audit task.
Step S202, after receiving an audit task to be processed submitted by a user terminal, an audit operation scheduling device acquires the number of suspicious records under each audit data model in the audit task to be processed; and determining the total workload of the audit task to be processed according to the number of the suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record.
In an optional example of the step S202, the audit task scheduling device runs each audit data model in the to-be-processed audit task for the service data of the audited organization to obtain the number information of the suspicious records under each audit data model. Then, the audit task scheduling device can determine the total workload of the audit task to be processed according to the following modes: multiplying the number of suspicious records under an audit data model by the processing time required by a single suspicious record under the model to obtain the workload corresponding to the audit data model; and taking the sum of the workload corresponding to each audit data model in the audit task to be processed as the total workload of the audit task to be processed.
For example, assuming that a certain to-be-processed audit task relates to the audit data model A, B, C, the number of suspicious records in the audit data model a is 100, the number of suspicious records in the audit data model B is 50, the number of suspicious records in the audit data model C is 35, the processing time required for a single suspicious record under the audit data model a is 1 minute, the processing time required for a single suspicious record under the audit data model B is 2 minutes, and the processing time required for a single suspicious record under the audit data model C is 3 minutes, the workload corresponding to the audit data model A, B, C is 100 minutes, and 105 minutes, respectively, and the total workload of the to-be-processed audit task is 305 minutes.
Further, the processing time required for the single suspicious record involved in step S202 may be obtained as follows: acquiring log data of a plurality of historical audit tasks; wherein the log data of the historical audit task comprises: the number of suspicious records under each audit data model in the historical audit task and the actual time consumption for processing all suspicious records in a single audit data model; determining the actual time consumption for processing the single suspicious record under the audit data model according to the number of the suspicious records in the single audit data model in a historical audit task and the actual time consumption for processing all the suspicious records in the audit data model; and calculating the average value of the actual time consumption of processing the single suspicious record under the audit data model in the plurality of historical audit tasks, and taking the average value as the processing time required by the single suspicious record under the audit data model.
For example, assume that log data for historical audit tasks 1, 2, and 3 are obtained, and that the log data for historical audit task 1 is shown in Table 1.
TABLE 1
Figure BDA0002409446780000101
Furthermore, by processing the data shown in table 1 in the above manner, the actual time consumed for processing a single suspicious record under each audit data model in each historical audit task can be obtained, as shown in table 2.
TABLE 2
Figure BDA0002409446780000102
Next, averaging the actual time consumed for processing a single suspicious record under the audit data model a in the historical audit tasks 1 and 3 shown in table 2, so that the processing time required for processing the single suspicious record under the audit data model a is 2.75 minutes; by averaging the actual time consumption for processing a single suspicious record under the audit data model B in the historical audit tasks 1, 2 and 3 shown in the table 2, the processing time required for processing the single suspicious record under the audit data model B can be 1.77 minutes; by averaging the actual time consumed for processing a single suspicious record under the audit data model C in the historical audit tasks 2 and 3 shown in table 2, the processing time required for processing the single suspicious record under the audit data model C is 2 minutes.
And step S203, the audit task scheduling device sends the total workload of the audit task to be processed to the user terminal.
In specific implementation, after the user terminal receives the information of the total workload sent by the audit task scheduling device, the initiator of the audit task can judge whether the workload of the audit task is controllable or not based on the information of the total workload. When the auditing task initiator confirms that the total workload of the auditing task is controllable, the step S204 can be executed; and when the auditing task initiator confirms that the total workload of the auditing task is uncontrollable, executing the step S207.
And step S204, under the condition that the total workload is confirmed to be controllable, the user terminal sends a personnel scheduling request to the audit operation scheduling device.
In specific implementation, when the auditing task initiator confirms that the total workload of the auditing task is controllable, a personnel scheduling request aiming at the auditing task can be initiated through an auditing portal website on a user terminal. Wherein the personnel scheduling request may include: and (4) auditing a target completion time limit set by a task initiator.
And step S205, after receiving the personnel scheduling request, the audit checking operation scheduling device generates a personnel scheduling list for executing the to-be-processed audit task.
In an optional example of step S205, the audit trail job scheduling apparatus may analyze target completion time limit information of the to-be-processed audit task from the staff scheduling request, and then perform staff scheduling planning according to the target completion time limit information and the to-be-allocated auditor information, so as to obtain a staff scheduling list for executing the to-be-processed audit task.
Specifically, in the above optional example, the performing, by the audit checking job scheduling apparatus, staff scheduling planning according to the target completion time limit information and the to-be-allocated auditor information may include: the audit data model in the audit task to be processed is traversed by the audit checking operation scheduling device; for each audit data model, inquiring the information of auditors to be distributed according to the audit data model identification to obtain the information of the auditors capable of processing the suspicious records under the audit data model; wherein, the auditor information capable of processing the suspicious records under the audit data model comprises: the audit personnel identification of the suspicious records under the audit data model can be processed, and the actual time consumption for processing the single suspicious records under the audit data model by the audit personnel is reduced; and determining the auditors distributed to the audit data model according to the auditor information capable of processing the suspicious records under the audit data model and the target completion time limit information. And further, according to the information of the auditors distributed to each audit data model, a personnel scheduling list for executing the audit task to be processed can be generated.
For example, assuming that the audit task to be processed relates to audit data models a and B, the auditor list to be allocated may be queried according to the identifier of the audit data model a to query the information of the auditor capable of processing the suspicious records under the audit data model a, assuming that the queried auditor information is: the work number 0001 and the work number 0003 and the work number A and the model A actually take 2 minutes to process a single suspicious record; inquiring a list of auditors to be distributed according to the identification of the audit data model B so as to inquire the information of the auditors capable of processing the suspicious records under the audit data model B, and assuming that the inquired information of the auditors is as follows: work number 0010, which actually takes 4 minutes to process a single suspicious record under model B, and work number 0015, which actually takes 5 minutes to process a single suspicious record under model B. Furthermore, according to the information of the auditors capable of processing the suspicious records under the audit data model A and the target completion time limit information, the auditors distributed to the audit data model A can be determined; and determining the auditors distributed to the audit data model B according to the auditor information capable of processing the suspicious records under the audit data model B and the target completion time limit information.
And step S206, the audit checking operation scheduling device sends the personnel scheduling list of the tasks to be processed to the user terminal.
And step S207, under the condition that the total workload is not controllable, the user terminal sends the modified audit task to the audit task scheduling device.
In specific implementation, if the initiator of the audit task considers that the total workload of the audit task is uncontrollable, the audit task can be modified through an audit portal website or an APP on the user terminal, for example, the number of audit data models related to the audit task is reduced, and then the modified audit task is submitted to an audit task scheduling device.
Step S208, after receiving the modified audit task submitted by the user terminal, the audit task scheduling device acquires the number of suspicious records under each audit data model in the modified audit task; and determining the total workload of the modified audit task according to the number of the suspicious records under each audit data model in the modified audit task and the processing time required by a single suspicious record.
In specific implementation, the audit task scheduling device can evaluate the total workload of the modified audit task in the same way of evaluating the total workload of the original audit task to be processed. After the total workload of the modified audit task is evaluated, the audit task scheduling device can send the information of the total workload of the modified audit task to the user terminal, so that an audit task initiator can judge whether the modified audit task is controllable according to the information, and personnel scheduling is carried out under the condition that the modified audit task is considered to be controllable.
In the embodiment of the invention, the time required by processing the single suspicious record in each audit data model is determined based on the log data of the historical audit task, so that the workload of the audit task to be processed can be accurately and quickly evaluated, and an audit task initiator can conveniently and accurately judge whether the workload of the audit task is controllable; through the steps of carrying out personnel scheduling planning after the work load of the audit task is confirmed to be controllable, generating a personnel scheduling list for executing the audit task to be processed and the like, personnel scheduling and distribution can be carried out automatically and reasonably aiming at the audit task to be processed, and the work efficiency of the whole audit operation is improved.
FIG. 3 is a schematic diagram of the main modules of an audit trail operation scheduling apparatus according to a third embodiment of the present invention. As shown in fig. 3, an audit task scheduling apparatus 300 according to an embodiment of the present invention includes: an acquisition module 301, a determination module 302 and a generation module 303.
The obtaining module 301 is configured to obtain the number of suspicious records under each audit data model in the to-be-processed audit task after receiving the to-be-processed audit task submitted by the user terminal.
Wherein the pending audit task may relate to one or more audit data models. The audit data model is used for analyzing the business data of the audited organization to find out or hit suspicious records in the business data. For example, a certain audit task to be processed relates to three audit data models, namely an audit data model a, an audit data model B and an audit data model C, wherein the number of suspicious records in the order of the audit data model a is 100, the number of suspicious records in the order of the audit data model B is 50, and the number of suspicious records in the order of the audit data model C is 35.
In an optional embodiment, the obtaining, by the obtaining module 301, the number of suspicious records under each audit data model in the audit task to be processed may include: the obtaining module 301 runs each audit data model in the to-be-processed audit task for the service data of the audited organization to obtain the number information of the suspicious records under each audit data model. In specific implementation, an audit task initiator can set an audit data model to be called by the audit work and information of an audited organization aiming at the audit work on an audit portal website or an APP on a user terminal, and then submit the information to an audit operation scheduling device in a mode of waiting for processing the audit task, and then an acquisition module 301 of the audit operation scheduling device can operate the data models aiming at service data of the audited organization to obtain the number information of suspicious records under each audit data model.
In another optional embodiment, the obtaining, by the obtaining module 301, the number of suspicious records under each audit data model in the audit task to be processed may include: the obtaining module 301 queries a database according to the identifier of the audit task to be processed, so as to obtain the number of suspicious records under each audit data model in the audit task to be processed. In specific implementation, one or more audit data models can be operated aiming at the service data of an audited organization in advance to obtain the number information of suspicious records under each audit data model, and the audit task identifiers and the number information of the suspicious records under the audit data models are correspondingly stored in the database. After receiving the to-be-processed audit task submitted by the audit task initiator, the obtaining module 301 may query the database according to the identifier of the to-be-processed audit task to obtain the number of suspicious records under each audit data model in the to-be-processed audit task.
A determining module 302, configured to determine a total workload of the audit data model to be processed according to the number of suspicious records in each audit data model in the audit data model to be processed and the processing time required for a single suspicious record, and return information of the total workload to the user terminal.
For example, the determining module 302 may specifically determine the total workload of the to-be-processed audit task by: the determining module 302 multiplies the number of suspicious records under an audit data model by the processing time required by a single suspicious record under the model to obtain the workload corresponding to the audit data model; the determining module 302 takes the sum of the workloads corresponding to the audit data models in the audit task to be processed as the total workload of the audit task to be processed.
For example, assuming that a certain to-be-processed audit task relates to the audit data model A, B, C, the number of suspicious records in the audit data model a is 100, the number of suspicious records in the audit data model B is 50, the number of suspicious records in the audit data model C is 35, the processing time required for a single suspicious record under the audit data model a is 1 minute, the processing time required for a single suspicious record under the audit data model B is 2 minutes, and the processing time required for a single suspicious record under the audit data model C is 3 minutes, the workload corresponding to the audit data model A, B, C is 100 minutes, and 105 minutes, respectively, and the total workload of the to-be-processed audit task is 305 minutes.
In the embodiment of the invention, the total workload of the audit task can be rapidly and accurately evaluated by the determining module 302 according to the type of the audit data model called by the audit task to be processed, the number of suspicious records under each audit data model and the processing time required by a single suspicious record under each type of audit data model. Furthermore, according to the calculated total workload of the audit task, the reasonability of subsequent personnel configuration management is improved.
A generating module 303, configured to generate a staff scheduling list for executing the to-be-processed audit task after receiving a staff scheduling request corresponding to the to-be-processed audit task and sent by the user terminal, and return the staff scheduling list to the user terminal.
In specific implementation, after the user terminal receives the information of the total workload sent by the audit task scheduling device, the initiator of the audit task can judge whether the workload of the audit task is controllable or not based on the information of the total workload. When the auditing task initiator confirms that the total workload of the auditing task is controllable, a personnel scheduling request aiming at the auditing task can be initiated through an auditing portal website on a user terminal.
After the audit job scheduling device receives the personnel scheduling request for the audit task, personnel scheduling planning can be performed through the iteration algorithm preset in the generating module 303, so as to obtain a personnel scheduling planning result. Illustratively, the personnel scheduling planning result may include: the number of persons required to be equipped, the specific person identification (such as job number, name and the like) of the equipment, the expected time length required for each person to complete the respective work and the like are checked against the suspicious records in each audit model. Then, the generating module 303 may generate a staff scheduling list for executing the to-be-processed audit task according to the staff scheduling planning result, and return the staff scheduling list to the user terminal.
In the device of the embodiment of the invention, after receiving the audit task to be processed submitted by a user terminal, the obtaining module 301 obtains the number of suspicious records under each audit data model in the audit task to be processed, and the determining module 302 determines the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, so that the workload of the audit task can be rapidly and accurately evaluated; further, the information of the total workload is returned to the user terminal through the determining module 302, so that an auditing task initiator can conveniently and accurately judge whether the workload of the auditing task is controllable or not; further, after receiving the personnel scheduling request corresponding to the to-be-processed audit task sent by the user terminal, the generating module 303 generates a personnel scheduling list for executing the to-be-processed audit task, and returns the personnel scheduling list to the user terminal, so that personnel scheduling and distribution can be automatically and reasonably performed on the to-be-processed audit task, and the working efficiency of the whole audit task is improved.
FIG. 4 is a schematic diagram of the main modules of an audit trail job scheduling apparatus according to a fourth embodiment of the present invention. As shown in fig. 4, an audit trail operation scheduling apparatus 400 according to an embodiment of the present invention includes: the device comprises a preprocessing module 401, an acquisition module 402, a determination module 403 and a generation module 404.
And the preprocessing module 401 is configured to determine processing time required by a single suspicious record in each audit data model. The audit data model is used for analyzing the business data of the audited organization to find out or hit suspicious records in the business data. For example, assuming that there are five audit data models, one or more audit data models can be selected from the five audit data models to audit the business data of the audited organization each time an audit task is performed.
Specifically, the preprocessing module 401 determines the processing time required for a single suspicious record in each audit data model, including: the preprocessing module 401 acquires log data of a plurality of historical audit tasks; wherein the log data of the historical audit task comprises: the number of suspicious records under each audit data model in the historical audit task and the actual time consumption for processing all suspicious records in a single audit data model; the preprocessing module 401 determines actual time consumption for processing a single suspicious record under a historical audit data model according to the number of suspicious records in a single audit data model in a historical audit task and the actual time consumption for processing all suspicious records in the audit data model; the preprocessing module 401 calculates an average value of actual time consumption for processing a single suspicious record under the audit data model in the plurality of historical audit tasks, and takes the average value as processing time required for processing the single suspicious record under the audit data model.
The obtaining module 402 is configured to obtain the number of suspicious records under each audit data model in the to-be-processed audit task after receiving the to-be-processed audit task submitted by the user terminal.
Wherein the pending audit task may relate to one or more audit data models. For example, assume that there are five audit data models A, B, C, D, E, three audit data models related to a certain to-be-processed audit task are respectively an audit data model a, an audit data model B and an audit data model C, the number of suspicious records in the order of the audit data model a is 100, the number of suspicious records in the order of the audit data model B is 50, and the number of suspicious records in the order of the audit data model C is 35.
In an optional embodiment, the obtaining, by the obtaining module 402, the number of suspicious records under each audit data model in the audit task to be processed may include: the obtaining module 402 runs each audit data model in the to-be-processed audit task for the service data of the audited organization to obtain the number information of the suspicious records under each audit data model. In specific implementation, an audit task initiator can set an audit data model to be called by the audit work and information of an audited organization aiming at the audit work on an audit portal website or an APP on a user terminal, and then submit the information to an audit operation scheduling device in a mode of waiting for processing the audit task, and then an acquisition module 402 of the audit operation scheduling device can operate the data models aiming at service data of the audited organization to obtain the number information of suspicious records under each audit data model.
In another optional embodiment, the obtaining module 402 may obtain the number of suspicious records under each audit data model in the audit task to be processed, where the number of suspicious records under each audit data model may include: the obtaining module 402 queries the database according to the identifier of the audit task to be processed, so as to obtain the number of suspicious records under each audit data model in the audit task to be processed. In specific implementation, one or more audit data models can be operated aiming at the service data of an audited organization in advance to obtain the number information of suspicious records under each audit data model, and the audit task identifiers and the number information of the suspicious records under the audit data models are correspondingly stored in the database. After receiving the to-be-processed audit task submitted by the audit task initiator, the obtaining module 402 may query the database according to the identifier of the to-be-processed audit task to obtain the number of suspicious records under each audit data model in the to-be-processed audit task.
A determining module 403, configured to determine a total workload of the audit data model to be processed according to the number of suspicious records in each audit data model in the audit data model to be processed and the processing time required for a single suspicious record, and return information of the total workload to the user terminal.
For example, the determining module 403 may specifically determine the total workload of the to-be-processed audit task by: the determining module 403 multiplies the number of suspicious records in an audit data model by the processing time required by a single suspicious record in the model to obtain the workload corresponding to the audit data model; the determining module 403 uses the sum of the workloads corresponding to the audit data models in the audit task to be processed as the total workload of the audit task to be processed.
For example, assuming that a certain to-be-processed audit task relates to the audit data model A, B, C, the number of suspicious records in the audit data model a is 100, the number of suspicious records in the audit data model B is 50, the number of suspicious records in the audit data model C is 35, the processing time required for a single suspicious record under the audit data model a is 1 minute, the processing time required for a single suspicious record under the audit data model B is 2 minutes, and the processing time required for a single suspicious record under the audit data model C is 3 minutes, the workload corresponding to the audit data model A, B, C is 100 minutes, and 105 minutes, respectively, and the total workload of the to-be-processed audit task is 305 minutes.
In the embodiment of the present invention, the determination module 403 can quickly and accurately evaluate the total workload of the current audit task according to the type of the audit data model called by the audit task to be processed, the number of suspicious records under each audit data model, and the processing time required by a single suspicious record under each type of audit data model. Furthermore, according to the calculated total workload of the audit task, the reasonability of subsequent personnel configuration management is improved.
A generating module 404, configured to generate a staff scheduling list for executing the to-be-processed audit task after receiving a staff scheduling request corresponding to the to-be-processed audit task and sent by the user terminal, and return the staff scheduling list to the user terminal.
In specific implementation, after the user terminal receives the information of the total workload sent by the audit task scheduling device, the initiator of the audit task can judge whether the workload of the audit task is controllable or not based on the information of the total workload. When the auditing task initiator confirms that the total workload of the auditing task is controllable, a personnel scheduling request aiming at the auditing task can be initiated through an auditing portal website on a user terminal. Wherein the personnel scheduling request may include: and (4) auditing a target completion time limit set by a task initiator.
After receiving a staff scheduling request corresponding to the to-be-processed audit task sent by the user terminal, the generating module 404 may parse target completion time limit information of the to-be-processed audit task from the staff scheduling request, and then perform staff scheduling planning according to the target completion time limit information and the to-be-allocated auditor information, so as to obtain a staff scheduling list for executing the to-be-processed audit task.
Specifically, the generating module 404 performs staff scheduling planning according to the target completion time limit information and the to-be-allocated auditor information, which may include: the generating module 404 traverses the audit data model in the audit task to be processed; for each audit data model, the generating module 404 queries the auditor information to be distributed according to the audit data model identifier to obtain the auditor information capable of processing the suspicious records under the audit data model; wherein, the auditor information capable of processing the suspicious records under the audit data model comprises: the audit personnel identification of the suspicious records under the audit data model can be processed, and the actual time consumption for processing the single suspicious records under the audit data model by the audit personnel is reduced; the generating module 404 determines the auditors assigned to the audit data model according to the auditor information capable of processing the suspicious records under the audit data model and the target completion time limit information. Further, the generating module 404 may generate a staff scheduling list for executing the to-be-processed audit task according to the information of the auditors allocated to each audit data model.
For example, assuming that the audit task to be processed relates to audit data models a and B, the auditor list to be allocated may be queried according to the identifier of the audit data model a to query the information of the auditor capable of processing the suspicious records under the audit data model a, assuming that the queried auditor information is: the work number 0001 and the work number 0003 and the work number A and the model A actually take 2 minutes to process a single suspicious record; inquiring a list of auditors to be distributed according to the identification of the audit data model B so as to inquire the information of the auditors capable of processing the suspicious records under the audit data model B, and assuming that the inquired information of the auditors is as follows: work number 0010, which actually takes 4 minutes to process a single suspicious record under model B, and work number 0015, which actually takes 5 minutes to process a single suspicious record under model B. Furthermore, according to the information of the auditors capable of processing the suspicious records under the audit data model A and the target completion time limit information, the auditors distributed to the audit data model A can be determined; and determining the auditors distributed to the audit data model B according to the auditor information capable of processing the suspicious records under the audit data model B and the target completion time limit information.
In the device provided by the embodiment of the invention, the time required by processing the single suspicious record in each audit data model is determined by the preprocessing module based on the log data of the historical audit task, so that the determining module can accurately and quickly evaluate the workload of the audit task to be processed, and an audit task initiator can conveniently and accurately judge whether the workload of the audit task is controllable; the generation module carries out personnel scheduling planning after confirming that the workload of the audit task is controllable, generates a personnel scheduling list for executing the audit task to be processed, can carry out personnel scheduling and distribution automatically and reasonably aiming at the audit task to be processed, and improves the working efficiency of the whole audit task.
FIG. 5 illustrates an exemplary system architecture 500 to which an audit trail job scheduling method or audit trail job scheduling apparatus of embodiments of the present invention may be applied.
As shown in fig. 5, the system architecture 500 may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 serves to provide a medium for communication links between the terminal devices 501, 502, 503 and the server 505. Network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 501, 502, 503 to interact with a server 505 over a network 504 to receive or send messages or the like. The terminal devices 501, 502, 503 may be installed with various communication client applications, such as an audit task scheduling application, a shopping application, a web browser application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 501, 502, 503 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 505 may be a server providing various services, such as a background management server providing support for audit trail scheduling type websites browsed by users using the terminal devices 501, 502, 503. The background management server can analyze and process the received data such as the audit task to be processed, and feed back the processing result (such as a personnel scheduling list) to the terminal equipment.
It should be noted that, the audit task scheduling method provided by the embodiment of the present invention is generally executed by the server 505, and accordingly, the audit task scheduling apparatus is generally disposed in the server 505.
It should be understood that the number of terminal devices, networks, and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use with the electronic device implementing an embodiment of the present invention. The computer system illustrated in FIG. 6 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the invention.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
To the I/O interface 605, AN input section 606 including a keyboard, a mouse, and the like, AN output section 607 including a network interface card such as a Cathode Ray Tube (CRT), a liquid crystal display (L CD), and the like, a speaker, and the like, a storage section 608 including a hard disk, and the like, and a communication section 609 including a network interface card such as a L AN card, a modem, and the like, the communication section 609 performs communication processing via a network such as the internet, a drive 610 is also connected to the I/O interface 605 as necessary, a removable medium 611 such as a magnetic disk, AN optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted into the storage section 608 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 601.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes an acquisition module, a determination module, and a generation module. The names of these modules do not in some cases constitute a limitation on the module itself, for example, the generation module may also be described as a "generation and transmission module".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to perform the following: after receiving an audit task to be processed submitted by a user terminal, acquiring the number of suspicious records under each audit data model in the audit task to be processed; determining the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal; and after receiving a personnel scheduling request corresponding to the audit task to be processed, which is sent by the user terminal, generating a personnel scheduling list for executing the audit task to be processed, and returning the personnel scheduling list to the user terminal.
According to the technical scheme of the embodiment of the invention, personnel scheduling and distribution can be automatically and reasonably carried out aiming at the audit task to be processed, and the working efficiency of the whole audit operation is improved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. An audit job scheduling method, comprising:
after receiving an audit task to be processed submitted by a user terminal, acquiring the number of suspicious records under each audit data model in the audit task to be processed;
determining the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal;
and after receiving a personnel scheduling request corresponding to the audit task to be processed, which is sent by the user terminal, generating a personnel scheduling list for executing the audit task to be processed, and returning the personnel scheduling list to the user terminal.
2. The method according to claim 1, wherein the determining the total workload of the audit task to be processed according to the number of suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record comprises:
multiplying the number of suspicious records under an audit data model by the processing time required by a single suspicious record under the model to obtain the workload corresponding to the audit data model; and taking the sum of the workload corresponding to each audit data model in the audit task to be processed as the total workload of the audit task to be processed.
3. The method of claim 1, wherein the processing time required for the single suspect record is derived from:
acquiring log data of a plurality of historical audit tasks; wherein the log data of the historical audit task comprises: the number of suspicious records under each audit data model in the historical audit task and the actual time consumption for processing all suspicious records in a single audit data model; determining the actual time consumption for processing the single suspicious record under the audit data model according to the number of the suspicious records in the single audit data model in a historical audit task and the actual time consumption for processing all the suspicious records in the audit data model; and calculating the average value of the actual time consumption of processing the single suspicious record under the audit data model in the plurality of historical audit tasks, and taking the average value as the processing time required by the single suspicious record under the audit data model.
4. The method of claim 1, wherein generating a personnel schedule for performing the pending audit task comprises:
target completion time limit information of the audit task to be processed is analyzed from the personnel scheduling request; and scheduling personnel according to the target completion time limit information and the information of the auditors to be distributed so as to obtain a personnel scheduling list for executing the audit tasks to be processed.
5. The method of claim 4, wherein performing staff scheduling planning according to the target completion time limit information and the to-be-allocated auditor information to obtain a staff scheduling list for executing the to-be-processed audit task comprises:
traversing an audit data model in the audit task to be processed; for each audit data model, inquiring the information of auditors to be distributed according to the audit data model identification to obtain the information of the auditors capable of processing the suspicious records under the audit data model; wherein, the auditor information capable of processing the suspicious records under the audit data model comprises: the audit personnel identification of the suspicious records under the audit data model can be processed, and the actual time consumption for processing the single suspicious records under the audit data model by the audit personnel is reduced; determining the auditors distributed to the audit data model according to the auditor information capable of processing the suspicious records under the audit data model and the target completion time limit information; and generating a personnel scheduling list for executing the audit task to be processed according to the information of the auditors distributed to each audit data model.
6. The method of claim 1, further comprising:
after the step of returning the information of the total workload to the user terminal, receiving a modified audit task submitted by the user terminal; acquiring the number of suspicious records under each audit data model in the modified audit task; and determining the total workload of the modified audit task according to the number of the suspicious records under each audit data model in the modified audit task and the processing time required by a single suspicious record, and returning the information of the total workload of the modified audit task to the user terminal.
7. The method according to claim 1, wherein the obtaining of the number of suspicious records under each audit data model in the audit task to be processed comprises:
and operating each audit data model in the audit task to be processed aiming at the service data of the audited organization to obtain the number information of the suspicious records under each audit data model.
8. An audit trail job scheduling apparatus, said apparatus comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring the number of suspicious records under each audit data model in an audit task to be processed after receiving the audit task to be processed submitted by a user terminal;
the determining module is used for determining the total workload of the audit task to be processed according to the number of the suspicious records under each audit data model in the audit task to be processed and the processing time required by a single suspicious record, and returning the information of the total workload to the user terminal;
and the generating module is used for generating a personnel scheduling list for executing the audit task to be processed after receiving a personnel scheduling request which is sent by the user terminal and corresponds to the audit task to be processed, and returning the personnel scheduling list to the user terminal.
9. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 7.
CN202010171871.5A 2020-03-12 2020-03-12 Audit audit job scheduling method and device Pending CN111428974A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010171871.5A CN111428974A (en) 2020-03-12 2020-03-12 Audit audit job scheduling method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010171871.5A CN111428974A (en) 2020-03-12 2020-03-12 Audit audit job scheduling method and device

Publications (1)

Publication Number Publication Date
CN111428974A true CN111428974A (en) 2020-07-17

Family

ID=71553741

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010171871.5A Pending CN111428974A (en) 2020-03-12 2020-03-12 Audit audit job scheduling method and device

Country Status (1)

Country Link
CN (1) CN111428974A (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009259214A (en) * 2008-03-19 2009-11-05 Nec Corp Audit system, external audit device, external audit method, and external audit program
US20140032280A1 (en) * 2012-07-26 2014-01-30 Uniloc Luxembourg, S.A. Employee performance evaluation
CN109324978A (en) * 2018-11-28 2019-02-12 北京精密机电控制设备研究所 A kind of software testing management system of multi-person synergy
CN109359798A (en) * 2018-08-21 2019-02-19 平安科技(深圳)有限公司 Method for allocating tasks, device and storage medium
CN109901920A (en) * 2019-01-18 2019-06-18 中国平安财产保险股份有限公司 Method for scheduling task and device, electric terminal
CN110070291A (en) * 2019-04-22 2019-07-30 北京冠群信息技术股份有限公司 Audit task distribution method and system
US20190236516A1 (en) * 2018-01-31 2019-08-01 Clari Inc. Method for determining amount of time spent on a task and estimating amount of time required to complete the task
CN110264036A (en) * 2019-05-10 2019-09-20 阿里巴巴集团控股有限公司 Method for scheduling task and device
US20190295015A1 (en) * 2018-03-22 2019-09-26 Canon Kabushiki Kaisha Task management system, server apparatus, method of controlling the same, and storage medium
CN110543483A (en) * 2019-08-30 2019-12-06 北京百分点信息科技有限公司 Data auditing method and device and electronic equipment

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009259214A (en) * 2008-03-19 2009-11-05 Nec Corp Audit system, external audit device, external audit method, and external audit program
US20140032280A1 (en) * 2012-07-26 2014-01-30 Uniloc Luxembourg, S.A. Employee performance evaluation
US20190236516A1 (en) * 2018-01-31 2019-08-01 Clari Inc. Method for determining amount of time spent on a task and estimating amount of time required to complete the task
US20190295015A1 (en) * 2018-03-22 2019-09-26 Canon Kabushiki Kaisha Task management system, server apparatus, method of controlling the same, and storage medium
CN109359798A (en) * 2018-08-21 2019-02-19 平安科技(深圳)有限公司 Method for allocating tasks, device and storage medium
CN109324978A (en) * 2018-11-28 2019-02-12 北京精密机电控制设备研究所 A kind of software testing management system of multi-person synergy
CN109901920A (en) * 2019-01-18 2019-06-18 中国平安财产保险股份有限公司 Method for scheduling task and device, electric terminal
CN110070291A (en) * 2019-04-22 2019-07-30 北京冠群信息技术股份有限公司 Audit task distribution method and system
CN110264036A (en) * 2019-05-10 2019-09-20 阿里巴巴集团控股有限公司 Method for scheduling task and device
CN110543483A (en) * 2019-08-30 2019-12-06 北京百分点信息科技有限公司 Data auditing method and device and electronic equipment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
胡俊俊等: "一种新型的计算机审计模型", 《计算机应用研究》 *
郭庆平主编: "《中国人民银行内审转型案例汇编》", 31 May 2017 *

Similar Documents

Publication Publication Date Title
CN109446274B (en) Method and device for managing BI metadata of big data platform
US9319343B2 (en) Modifying an assignment of nodes to roles in a computing environment
CN104536965B (en) A kind of data query display systems under the conditions of big data and method
CN109901987B (en) Method and device for generating test data
CN112184154A (en) Business approval method and device
CN111245642A (en) Method and device for acquiring dependency relationship between multiple systems and electronic equipment
CN111324786A (en) Method and device for processing consultation problem information
CN111126948A (en) Processing method and device for approval process
CN111127181A (en) Voucher bookkeeping method and device
CN111444077A (en) Method and device for generating flow node test data
CN111401684A (en) Task processing method and device
CN110928594A (en) Service development method and platform
CN117076280A (en) Policy generation method and device, electronic equipment and computer readable storage medium
US8751643B2 (en) Correlating event streams from independent processes in a complex business system using metadata associated with the transport interconnections
CN110930238A (en) Method, device, equipment and computer readable medium for improving audit task efficiency
CN111062572A (en) Task allocation method and device
CN107679096B (en) Method and device for sharing indexes among data marts
CN111428974A (en) Audit audit job scheduling method and device
CN112131257B (en) Data query method and device
CN111526184B (en) Business auditing method and device
Gürbüz et al. Software metrics for green parallel computing of big data systems
CN113282455A (en) Monitoring processing method and device
CN113011858A (en) Audit project configuration and execution method and device
CN112884427A (en) Process management method and device supporting multiple service sources
CN111158649A (en) Method and device for configuring multi-level parameters

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200717