Task allocation method and device, computer equipment and storage medium
By screening and allocating pending tasks in car accident claims, using task levels and status of audit objects to calculate allocation index, optimizing task allocation, the problem of low processing efficiency of complex tasks is solved, and the processing efficiency of loss and compensation tasks is improved and accuracy.
Patent Information
- Application Number
- CN202411098150.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-12
- Publication Date
- 2024-12-03
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
During the car accident claim settlement process, complex tasks are inefficient, resulting in low-level staff being unable to handle complex tasks, resulting in insufficient efficiency in handling damage and compensation tasks.
By obtaining pending tasks in the task public pool, filtering based on the task level, the status and level of the audit object, calculating the task allocation index, optimizing the task allocation order, and assigning tasks to matching target objects, ensuring that tasks are prioritized by importance Process and review through the relationship.
It improves task processing efficiency and accuracy, ensures timely processing of complex tasks, and improves the ability matching and processing efficiency of audit objects.
Smart Images

Figure CN119067369A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of task allocation, and in particular to a task allocation method, apparatus, computer equipment, storage medium and computer program product. Background Art
[0002] If a car encounters an accident while driving, it can be claimed through insurance. When claiming, it is necessary to determine the damage and compensation caused by the accident, and then conduct damage assessment and compensation after the damage assessment and compensation. The complexity of the loss items caused by different accident scenarios is different, and the amount of economic loss is different. Therefore, the difficulty of handling damage assessment and compensation tasks is also different. Complex tasks usually require high-level staff to handle.
[0003] When handling loss assessment and claims settlement tasks, staff at different levels usually choose to handle tasks corresponding to simple accident scenarios, and delay the processing of tasks with complex scenarios and serious economic losses, resulting in a large number of complex tasks remaining in the system. At this time, low-level staff are unable to handle complex tasks, resulting in insufficient processing efficiency of loss assessment and claims settlement tasks. Summary of the invention
[0004] Based on this, it is necessary to provide a task allocation method, device, computer equipment, computer-readable storage medium and computer program product that can improve task processing efficiency in response to the above technical problems.
[0005] In a first aspect, the present application provides a task allocation method. The method comprises:
[0006] Get the pending tasks contained in the task common pool;
[0007] Based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, a first target object that satisfies a preset matching condition with the pending task is screened, and the pending task is assigned to the first target object so that the first target object processes the pending task to obtain a first processing result;
[0008] A second target object that meets a preset association condition with the first target object is determined, and the task to be processed and the first processing result are sent to the second target object.
[0009] In one embodiment, the pending tasks include independent audit tasks and / or associated audit tasks; the independent audit tasks are audit tasks without audit records; after obtaining the pending tasks included in the task common pool, the method further includes:
[0010] If the task to be processed is the associated audit task, the associated audit task is assigned to the associated object of the associated audit task; the associated audit task includes the audit task returned to the fixed guarantee stage and the audit task returned to the task common pool.
[0011] In one embodiment, after assigning the associated audit task to an associated object of the associated audit task, the method further includes:
[0012] If the working state of the associated object is an abnormal working state, the associated audit task is converted into an independent audit task, and the independent audit task is added to the task common pool.
[0013] In one embodiment, the current state includes a work state and a task state; the screening based on the task level of the pending task, the current state of each audit object, and the object level of each audit object to determine the first target object that meets the preset matching condition with the pending task includes:
[0014] Acquire work record data of each audit object, and determine the work status of the audit object based on the record;
[0015] Obtaining the current number of processing tasks for each of the audit objects, and determining the task status corresponding to the current number of processing tasks;
[0016] Determine that the audit object whose working state is a normal working state and whose task state is a normal load state is a valid audit object;
[0017] Based on the task level of the task to be processed and the object level of the valid audit object, a first target object that meets a preset matching condition with the task to be processed is determined from the valid audit objects.
[0018] In one embodiment, the determining, based on the task level of the pending task and the object level of the valid audit object, a first target object that satisfies a preset matching condition with the pending task from the valid audit object includes:
[0019] Acquire the task processing scope of the object level of each of the valid audit objects, and if the task level of the task to be processed matches the task processing scope, determine that the valid audit object is the initial audit object;
[0020] From among the initial audit objects, the initial audit object with the least number of currently processed tasks is determined as the first target object.
[0021] In one embodiment, before obtaining the pending tasks contained in the task common pool, the method further includes:
[0022] Determine the allocation index of the task to be processed according to the duration coefficient of the task to be processed in the task common pool, the loss resource value of the task to be processed, the non-automatic underwriting degree value and the resource object loss data;
[0023] Determining the allocation order of each of the tasks to be processed based on the size of the allocation index of each of the tasks to be processed;
[0024] The tasks to be processed contained in the task common pool are obtained, including:
[0025] Based on the allocation sequence, multiple tasks to be processed included in the task common pool are traversed to obtain the tasks to be processed arranged in the allocation sequence.
[0026] In one embodiment, determining the allocation index of the pending task according to the duration coefficient of the pending task in the task common pool, the loss resource value of the pending task, the non-automatic underwriting degree value and the resource object loss data includes:
[0027] Obtaining the duration coefficient of the pending task in the task common pool, the loss resource value of the pending task, the non-automatic underwriting degree value and the resource object loss data;
[0028] Summing the duration coefficient and the resource object loss data to obtain a sum value; performing an exponential operation on the sum value to obtain a product value; an exponential parameter of the exponential operation is determined based on the loss resource value;
[0029] The product value and the non-automatic underwriting degree value are multiplied to obtain the allocation index of the task to be processed.
[0030] In a second aspect, the present application also provides a task allocation device. The device comprises:
[0031] The task acquisition module is used to obtain pending tasks contained in the task common pool;
[0032] A first allocation module is used to perform screening based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, determine a first target object that meets a preset matching condition with the pending task, and allocate the pending task to the first target object so that the first target object processes the pending task to obtain a first processing result;
[0033] The second allocation module is used to determine a second target object that meets a preset association condition with the first target object, and send the task to be processed and the first processing result to the second target object.
[0034] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following method steps when executing the computer program:
[0035] Get the pending tasks contained in the task common pool;
[0036] Based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, a first target object that satisfies a preset matching condition with the pending task is screened, and the pending task is assigned to the first target object so that the first target object processes the pending task to obtain a first processing result;
[0037] A second target object that meets a preset association condition with the first target object is determined, and the task to be processed and the first processing result are sent to the second target object.
[0038] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the following method are implemented:
[0039] Get the pending tasks contained in the task common pool;
[0040] Based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, a first target object that satisfies a preset matching condition with the pending task is screened, and the pending task is assigned to the first target object so that the first target object processes the pending task to obtain a first processing result;
[0041] A second target object that meets a preset association condition with the first target object is determined, and the task to be processed and the first processing result are sent to the second target object.
[0042] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the following method are implemented:
[0043] Get the pending tasks contained in the task common pool;
[0044] Based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, a first target object that satisfies a preset matching condition with the pending task is screened, and the pending task is assigned to the first target object so that the first target object processes the pending task to obtain a first processing result;
[0045] A second target object that meets a preset association condition with the first target object is determined, and the task to be processed and the first processing result are sent to the second target object.
[0046] The above-mentioned task allocation method, device, computer equipment, storage medium and computer program product disclose that the server determines the allocation index of each pending task through the duration coefficient, loss resource value, non-automatic underwriting degree value and resource object loss data of the pending task, and sorts multiple pending tasks according to the allocation index to obtain sorted pending tasks, and then the server allocates the pending tasks in sequence, and screens the first target object adapted to the pending task from each audit object according to the task level of the pending task, the current status of each audit object, and the object level, and allocates the pending task to the first target object to obtain the first processing result corresponding to the first target object. Based on this, the server determines that the next allocation object is the second target object based on the association relationship of the first target object, and sends the pending task and the first processing result to the second target object so that the second target object can process it.
[0047] Through the above method, the server can comprehensively determine the allocation index of the pending tasks through the duration coefficient of each pending task, the loss resource value of the pending task, the non-automatic underwriting degree value and the resource object loss data, and determine the sorted multiple pending tasks according to the allocation index, so that the important pending tasks can be allocated first according to the importance of each pending task, thereby optimizing the underlying logic of task allocation and improving the rationality and allocation efficiency of task allocation. In addition, by summing the duration coefficient and the resource object loss data, performing exponential calculations through the loss resource value, and multiplying through the non-automatic underwriting degree value, the intrinsic importance of the above four indicators and the external connections between the indicators can be fully utilized, thereby improving the accuracy of determining the allocation index. Based on this, the server then performs the initial screening of the target object according to the task level of each task to be assigned, the current status of the audit object, and the object level, so that the audit objects of each object level are assigned to the pending tasks that match the capabilities of the audit objects, ensuring the degree of adaptation between the audit objects and the pending tasks, thereby improving the processing efficiency of the audit objects. In addition, the server assigns the first processing result of the task to be processed and the task to be processed to the second target object, and further improves the accuracy of the first processing result through review by the second target object, so that the above method can improve the task processing efficiency on the basis of ensuring accuracy. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0049] FIG1 is an application environment diagram of a task allocation method in one embodiment;
[0050] FIG2 is a schematic diagram of a process flow of a task allocation method in one embodiment;
[0051] FIG3 is a schematic diagram of a flow chart of a step of determining a first target object in one embodiment;
[0052] FIG4 is a schematic diagram of the structure of a task allocation method in one embodiment;
[0053] FIG5 is a structural block diagram of a task allocation device in one embodiment;
[0054] FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0055] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0056] The task allocation method provided in the embodiment of the present application can be applied in the application environment shown in Figure 1. The terminal 102 can upload the insurance determination task to the server 104. The insurance determination task may include a damage determination task and a compensation determination task. The server 104 converts the insurance determination task into an audit task for the audit object to review. The audit task may include a loss verification task and a compensation verification task. For the same insurance case, four tasks, namely, damage determination task, loss verification task, compensation determination task, and compensation verification task, can be performed in chronological order. The damage determination task is generated by the damage determiner, and the damage determination result is reviewed by the audit object. After the damage determination result is reviewed and approved, the compensation determiner can generate a compensation result based on the damage determination result, and the audit object reviews the compensation result to obtain information such as the compensation amount of the insurance case.
[0057] In the business system of the server, multiple pending tasks are usually processed in parallel, and the tasks may be loss assessment tasks and / or claims assessment tasks. The server may assign multiple pending tasks to each audit object. The server may match the pending tasks according to the task level of the pending tasks, the current status of the audit objects, and the object level of the audit objects, determine that the audit objects that meet the preset matching conditions are the first target objects, and assign the pending tasks to the first target objects, thereby obtaining the first processing result of the pending tasks, and determining the second target objects that have an associated relationship with the first target objects, and sending the first processing result and the pending tasks to the second target objects for review.
[0058] Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 can be implemented with an independent server or a server cluster consisting of multiple servers.
[0059] In an exemplary embodiment, as shown in FIG2 , a task allocation method is provided, which is described by taking the method applied to the server in FIG1 as an example, and includes the following steps S202 to S206 . Among them:
[0060] Step S202, obtaining the pending tasks contained in the task common pool.
[0061] Among them, the task common pool is used to store pending tasks that currently need to be processed by the audit object. The pending tasks can be at least one of the damage assessment tasks and the claims assessment tasks. The pending tasks in the task common pool can be tasks returned from the audit object to the task common pool, and the pending tasks can be pending tasks sent to the task common pool after the insurance personnel have made the insurance. The damage assessment task is used to check the damage assessment information corresponding to the accident to determine whether the damage assessment information is valid. The claims assessment task is used to check the claims assessment information corresponding to the accident to determine whether the claims assessment information in the claims document is valid. The claims assessment information is usually determined based on the audited damage assessment information.
[0062] Specifically, the server traverses the task common pool according to a preset time period, obtains the pending tasks currently existing in the task common pool, and obtains the task information of each pending task, which may include task identification, task level, task type, task creation time, etc. In addition, each pending task may include the duration of the task in the task common pool. After each time period, the task common pool may be traversed again to obtain the latest pending tasks, and the task information of the pending tasks may be updated.
[0063] Step S204, screening is performed based on the task level of the task to be processed, the current status of each audit object, and the object level of each audit object, to determine the first target object that meets the preset matching conditions with the task to be processed, and to assign the task to be processed to the first target object so that the first target object processes the task to be processed and obtains a first processing result.
[0064] Among them, the task level is used to indicate the difficulty and importance of the pending tasks. There is a positive correlation between the difficulty and importance. The higher the difficulty or the higher the importance, the higher the task level of the pending tasks. The current status is used to indicate whether the audit object can currently undertake new pending tasks. The object level is used to indicate the difficulty of the pending tasks that the audit object can handle. The higher the object level, the stronger the business capabilities of the audit object, and the more difficult the pending tasks that can be handled.
[0065] Specifically, the server traverses each pending task, matches the currently traversed pending task with each audit object, and determines the matching audit object as the first target object. The server first determines whether the current state of each audit object meets the preset matching condition. If the current state meets the preset matching condition, a plurality of audit objects whose current state meets the preset matching condition are preliminarily screened. Among the preliminarily screened audit objects, the audit object whose object level of each audit object meets the preset matching condition with the task level of the pending task is determined as the first target object.
[0066] Based on this, the server sends the currently traversed pending tasks to the task personal pool of the first target object, thereby completing the initial allocation of pending tasks. After receiving the pending tasks, the object terminal of the first target object reviews the pending tasks, obtains the first processing result, and sends the first processing result to the server.
[0067] Step S206: determine a second target object that meets a preset association condition with the first target object, and send the task to be processed and the first processing result to the second target object.
[0068] The object level of the second target object is greater than the object level of the first target object. The preset association condition is used to indicate that the second target object and the first target object meet the condition information of multi-level review; the preset association condition can be the superior review object corresponding to the first target object, for example, if the object level of the second target object is greater than the object level of the first target object, then the second target object is the superior review object of the first target object.
[0069] Specifically, after receiving the first processing result of the pending task returned by the object terminal, the server determines the audit object that meets the preset association condition with the first target object, and sends the list of audit objects that meet the preset association condition to the object terminal of the first target object. The first target object can send an instruction to determine the second target object, and determine the second target object according to the instruction. The server sends the pending task and the first processing result to the second target object, so that the second target object can review the pending task and the first processing result, and determine any one of returning the pending task to the first target object, sending the pending task to the next level audit object, or completing the audit according to the review result.
[0070] In the above-mentioned task allocation method, a plurality of pending tasks contained in the task common pool are obtained, and the task level of the pending tasks is determined. Based on the task level of the pending tasks, the current status of each audit object, and the object level, the server selects the first target object adapted to the pending tasks from each audit object, and allocates the pending tasks to the first target object. The first target object can process the pending tasks to obtain the first processing result. Based on this, the server determines the second target object whose association relationship meets the preset association condition as the next allocation object based on the association relationship of the first target object, and sends the pending tasks and the first processing result to the second target object so that the second target object can process them. Through the above-mentioned method, the server can perform the initial screening of the target objects according to the task level, the current status of the audit object, and the object level of the task, and allocate the pending tasks that match the capabilities of the audit objects to the audit objects of each object level, so as to ensure the degree of adaptation between the audit object and the pending tasks, thereby improving the processing efficiency of the audit objects. In addition, the server allocates the first processing result of the pending tasks and the pending tasks to the second target object, and improves the accuracy of the first processing result through the review of the second target object, so that the above-mentioned method can improve the task processing efficiency on the basis of ensuring accuracy.
[0071] In an exemplary embodiment, the pending tasks include independent audit tasks and / or associated audit tasks; the independent audit tasks are audit tasks without audit records; after the step of "obtaining the pending tasks included in the task common pool", the method further includes:
[0072] If the task to be processed is an associated review task, the associated review task is assigned to the associated object of the associated review task.
[0073] Among them, an independent audit task is an audit task without an audit record, that is, the independent audit task has not been assigned to an audit object in the historical operation record; an associated audit task is an audit task with an audit record, that is, the associated audit task has undergone at least one audit by the audit object. Associated audit tasks include audit tasks returned to the fixed guarantee stage and / or audit tasks returned to the task common pool.
[0074] Specifically, an independent audit task in the task common pool can be assigned to an audit object for the first time. If the independent audit task fails the audit, the audit object returns the independent audit task to the security stage, deletes the independent audit task from the task common pool, and converts the independent audit task into an associated audit task. The security object in the security stage modifies the security data in the associated audit task, updates the associated audit task, and sends the associated audit task to the task common pool. The server identifies the associated object of the associated audit task, and assigns the associated audit task to the associated object's task private pool. In one example, the associated object may be the object that performed the most recent audit on the associated audit task.
[0075] In another example, after the independent audit task in the task common pool is assigned to the audit object for the first time, the audit object does not process the independent audit task and returns the independent audit task to the task common pool. At this time, the independent audit task and the audit object have an associated relationship, and the independent audit task is converted into an associated audit task. When the task is assigned in the next time period, the associated audit task can be directly assigned to the audit object assigned last time, that is, the associated object, so that the audit object can continue to perform the audit.
[0076] In this embodiment, by assigning the associated audit tasks to the associated objects, the matching process between the tasks to be processed and the audit objects can be reduced, thereby improving the efficiency of task assignment.
[0077] In an exemplary embodiment, after the step of “assigning the associated audit task to the associated object of the associated audit task”, the method further includes:
[0078] If the working status of the associated object is an abnormal working status, the associated audit task is converted into an independent audit task, and the independent audit task is added to the task common pool.
[0079] The working state may include a normal working state and an abnormal working state.
[0080] Specifically, when the working status of the associated object is an abnormal working status, the association relationship of the associated audit task is deleted, and the associated audit task is converted into an independent audit task, and the independent audit task is added to the task common pool, waiting for the server to reallocate the independent audit task.
[0081] Optionally, the associated audit task includes a task deadline. If the working status of the associated object is an abnormal working status and the task deadline is greater than the preset deadline value, the associated audit task will not be processed; if the working status of the associated object is an abnormal working status and the task deadline is less than the preset deadline value, the associated audit task will be converted into an independent audit task, and the independent audit task will be added to the task common pool.
[0082] In this embodiment, by determining the working status of the associated object, determining whether to reallocate the associated audit task, and in the case of an abnormal working status, converting the associated audit task into an independent audit task and adding it to the task common pool for reallocation, it can avoid the associated audit task from being unprocessed for a long time and improve the flexibility of allocating tasks to be processed.
[0083] In an exemplary embodiment, the current state includes the working state and the task state; as shown in FIG3 , the specific implementation process of the step “screening based on the task level of the task to be processed, the current state of each audit object, and the object level of each audit object, and determining the first target object that meets the preset matching condition with the task to be processed” includes steps S302 to S308. Among them:
[0084] Step S302: Acquire the work record data of each audit object, and determine the work status of the audit object based on the record.
[0085] The work record data may be determined based on the attendance data of the audit object, for example, the attendance data may be at least one of signed in and not signed out, signed in and signed out, or not signed in. The work status may be a normal working status and an abnormal working status.
[0086] Specifically, if the server determines that the attendance data indicates that the audit object is not currently working, the audit object's working state is determined to be an abnormal working state. For example, if the audit object's attendance data indicates that the audit object has not signed in, the audit object's working state is determined to be an abnormal working state. If the server determines that the attendance data indicates that the audit object is currently working, the audit object's working state is determined to be a normal working state. For example, if the attendance data indicates that the audit object has signed in and has not signed out, the audit object's working state is determined to be a normal working state.
[0087] Step S304, obtaining the current number of processing tasks for each audit object, and determining the task status corresponding to the current number of processing tasks.
[0088] The number of currently processed tasks may represent the number of tasks in the task personal pool of the audit object. The task status may include a normal load status and an abnormal load status.
[0089] Specifically, the server obtains the number of audit tasks contained in the task personal pool of each audit object, and uses it as the current number of processed tasks. If the current number of processed tasks is greater than or equal to the preset maximum number, the task state corresponding to the current number of processed tasks is determined to be an abnormal load state; if the current number of processed tasks is less than the preset maximum number, the task state corresponding to the current number of processed tasks is determined to be a normal load state. When the task state is a normal load state, new tasks to be processed can also be received in the task personal pool. When the task state is an abnormal load state, the task personal pool cannot receive new tasks to be processed. The current number of processed tasks in the task personal pool can change dynamically with the processing of the audit object.
[0090] Step S306, determining that the audit object whose working status is a normal working status and whose task status is a normal load status is a valid audit object.
[0091] Specifically, each audit object is traversed to obtain multiple audit objects with a normal working status, and each audit object with a normal working status is traversed twice to determine the audit object with a task status of a normal load status as a valid audit object.
[0092] Step S308, based on the task level of the task to be processed and the object level of the valid audit object, determine the first target object that meets the preset matching condition with the task to be processed from the valid audit objects.
[0093] Specifically, multiple valid audit objects are traversed, and when the task level of the task to be processed and the object level of the valid audit object meet the preset matching condition, the valid audit object is determined to be the first target object, and the number of the first target objects may not be limited, and may be one or more. In one example, the preset matching condition may be that when the object level of the valid audit object is greater than or equal to the task level of the task to be processed, the valid audit object matches the task to be processed.
[0094] In this embodiment, by determining the working status and task status of the audit object, determining the valid audit object from each audit object, and matching the valid audit object with the pending task according to the preset matching conditions, the first target object is determined, and the pending task can be accurately assigned to the audit object that can be processed, thereby improving the accuracy of task allocation.
[0095] In an exemplary embodiment, the specific implementation process of the step of "determining a first target object that meets a preset matching condition with the task to be processed from the valid audit objects based on the task level of the task to be processed and the object level of the valid audit object" includes:
[0096] The task processing scope of the object level of each valid audit object is obtained. If the task level of the task to be processed matches the task processing scope, the valid audit object is determined to be the initial audit object; from each initial audit object, the initial audit object with the least number of currently processed tasks is determined as the first target object.
[0097] The task processing range may represent the range of task levels of the tasks to be processed, for example, the task processing range may be level one to level five.
[0098] Specifically, the server determines the task processing scope of the effective audit object according to the preset scope rule and the object level of the effective audit object. In one example, if the object level of the effective audit object is the preset level, the range between the preset level of the effective audit object and the lowest task level can be determined as the task processing range. For example, if the preset level is level five, the task processing range is determined to be level one to level five. In one example, if the object level of the effective audit object is the preset level, the task processing range can be determined according to the preset range before and after the preset level. For example, if the preset level is level five and the preset service is level three, the task processing range is determined to be level two to level eight.
[0099] Based on this, if the task level of the pending task is within the task processing range of the valid audit object, the valid audit object is determined as the initial audit object. The server obtains the current number of processing tasks of each initial audit object, and determines the initial audit object with the least current number of processing tasks as the first target object.
[0100] In this embodiment, by determining the task processing scope corresponding to the object level of the effective audit object, it is possible to determine whether the task to be processed matches the effective audit object based on the task level of the task to be processed, thereby determining the matching effective audit object as the first target object, which can improve the accuracy of determining the first target object, thereby improving the audit efficiency of the assigned tasks to be processed.
[0101] In an exemplary embodiment, before the step of “obtaining the pending tasks contained in the task common pool”, the method further includes:
[0102] The allocation index of the pending tasks is determined based on the duration coefficient of the pending tasks in the task common pool, the loss resource value of the pending tasks, the non-automatic underwriting degree value and the resource object loss data; the allocation order of each pending task is determined based on the size of the allocation index of each pending task.
[0103] Among them, the duration coefficient is used to indicate the duration of the pending task being added to the task common pool. The loss resource value is used to indicate the size of resources corresponding to the loss involved in the pending task. The non-automatic underwriting degree value is used to indicate the quantitative value corresponding to the judgment basis that the pending task does not meet the automatic loss assessment and automatic compensation, that is, the non-automatic underwriting degree value can indicate the quantitative value of the pending task through manual processing of the pending task. The higher the quantitative value, the greater the probability that the pending task will be manually processed. The resource object loss data is used to indicate the number of loss items involved in the pending task, and the size of resources corresponding to each loss item; the loss allocation index is used to indicate the allocation priority of the pending task, and the higher the allocation index, the higher the allocation priority.
[0104] Specifically, the server obtains the duration data of the pending task in the task common pool, and calculates the duration coefficient corresponding to the duration data through a pre-configured preset calculation strategy. The server can obtain the loss resource value of the pending task, and optimize the loss resource value through a preset calculation strategy to obtain an updated loss resource value. In the case where the pending task is a damage assessment task, the server can determine one or more automatic damage assessment items triggered by the pending task according to the preset automatic damage assessment rule, and for each automatic damage assessment item, determine the corresponding single damage assessment degree value through a preset calculation strategy, and perform weighted summation on each single damage assessment degree value to obtain the non-automatic insurance degree value of the pending task. In the case where the pending task is a compensation task, the server can determine the automatic compensation item triggered by the pending task according to the preset automatic compensation assessment rule, and for each automatic compensation item, determine the single compensation degree value through a preset calculation strategy, and perform weighted summation on the single compensation degree value to obtain the non-automatic insurance degree value of the pending task. The server can obtain the information of each loss item corresponding to the pending task, and generate resource object loss data based on the loss item type and the resource value of the loss item.
[0105] According to the preset calculation formula, the above-mentioned duration coefficient, loss resource value, non-automatic underwriting degree value and resource object loss data are calculated to obtain the allocation index of each pending task. The server sorts each pending task according to the size of the allocation index to obtain the allocation order of each pending task.
[0106] The specific implementation process of the step "obtaining pending tasks contained in the task common pool" includes:
[0107] Based on the allocation order, multiple pending tasks contained in the task common pool are traversed to obtain the pending tasks arranged in the allocation order.
[0108] Specifically, based on the allocation order of the above-mentioned tasks to be processed, the multiple tasks to be processed included in the task common pool are traversed, so as to allocate each task to be processed according to the allocation order.
[0109] In this embodiment, the allocation index of the pending tasks is determined by the duration coefficient, loss resource value, non-automatic underwriting degree value and resource object loss data, and sorted according to the allocation index. This allows high-priority pending tasks to be allocated first, optimizes the processing order, and improves the rationality and accuracy of the allocation.
[0110] In an exemplary embodiment, the specific implementation process of the step of "determining the allocation index of the pending task according to the duration coefficient of the pending task in the task common pool, the loss resource value of the pending task, the non-automatic underwriting degree value and the resource object loss data" includes:
[0111] Obtain the duration coefficient of the pending task in the task common pool, the loss resource value of the pending task, the non-automatic underwriting degree value, and the resource object loss data. Sum the duration coefficient and the resource object loss data to obtain the sum value; perform an exponential operation on the sum value to obtain a product value; the exponential parameter of the exponential operation is determined based on the loss resource value. Perform the product of the product value and the non-automatic underwriting degree value to obtain the allocation index of the pending task.
[0112] Specifically, after obtaining the duration coefficient, the loss resource value of the task to be processed, the non-automatic underwriting degree value, and the resource object loss data, the server calculates the sum of the duration coefficient and the resource object loss data, and determines the sum of the resource loss value and the preset value as an exponential parameter. An exponential operation is performed based on the sum value and the exponential parameter to obtain a product value, and the product of the product value and the non-automatic underwriting degree value is calculated to obtain the allocation index of the task to be processed.
[0113] In this embodiment, the allocation index of the tasks to be processed is obtained by a calculation strategy that combines multiplication, exponentiation, addition and subtraction operations on the duration coefficient, loss resource value, non-automatic underwriting degree value and resource object loss data. This can determine the priority of each task to be processed and improve the accuracy of determining the allocation index.
[0114] As shown in Figure 4, the specific execution process of the above-mentioned task allocation method is described in detail below in combination with a specific embodiment. The following factors are included in determining the task allocation method: employee status, authority rules, number of tasks, and audit rules. The intelligent allocation process can be comprehensively determined based on four factors: employee status, authority rules, number of tasks, and audit rules. Employee status can assist in determining the effective audit object. The authority rules can assist in determining the first target object and the second target object that meet the authority rules, that is, determining the matching process of the audit object and the task to be processed. The number of tasks can be used together with the employee status to determine the effective audit object. The audit rules may include rules that do not allow automatic loss assessment, rules for automatic compensation at uneven speeds, etc. The non-automatic underwriting degree value can be determined through the audit rules.
[0115] Specifically, both the loss assessment task and the compensation task contain corresponding authority rules. For example, the authority level of the loss assessment task can be from level one to level nine. The authority level of the compensation task can be from level one to level nine. After the loss assessment task and the compensation task are assigned to the first target object, they can be submitted to the superior again. The server can determine the highest authority level of the first target object, and assign the loss assessment task and the compensation task to the second target object with a higher authority level after the highest authority level. For example, object 1 processes a level one loss assessment task, and the object level of object 1 is level four. When object 1 submits the loss assessment task to the second target object, the object level of the second target object can be greater than or equal to level five.
[0116] The allocation rules corresponding to intelligent allocation are as follows:
[0117] Screening audit objects: Audit objects include loss verification objects and claims verification objects. Audit objects can log in to the audit system to sign in and out, and check whether the audit object is in normal working state by signing in and out. For audit objects in normal working state, determine the current number of processing tasks of the audit object, and remove audit objects with saturated current processing tasks. The remaining audit objects are valid audit objects.
[0118] Reassignment method: The server queries the associated audit tasks contained in the task common pool, and determines whether the associated audit task is an audit task returned to the fixed-security stage or an audit task returned to the task common pool. If it is an audit task returned to the fixed-security stage, and the audit task is submitted to the task common pool again, it is determined whether the last audit object has resigned. If not, the audit task is assigned to the last audit object; if the last audit object has resigned, it is determined to be an independent audit task and is placed in the task common pool to reallocate the audit object. If it is an audit task returned to the task common pool, the audit task is reallocated to the last audit object.
[0119] Determine the order of pending tasks: determine the allocation index for each pending task. And determine the order of task allocation according to the size of the allocation index. Specifically, the task duration coefficient of the pending task added to the task common pool is: T. For example, the T value of 0 to 1 hour is 1, the T value of 1 hour to 2 hours is 2, the T value of 2 hours to 3 hours is 3, and so on. The loss resource value of the pending task: R. For example, if the loss resource value of the accident case corresponding to the task is between 0 and 5000, then R is 1, if the loss resource value is between 5000 and 10000, then R is 2, and if the loss resource value is between 10000 and 15000, then R is 3. Non-automatic underwriting degree value: H. The non-automatic underwriting degree value can be determined according to the rule of not allowing automatic loss in Table 1 or the rule of not allowing automatic compensation in Table 2. Resource object loss data: S. The resource object loss data can be determined according to the loss items of the accident case and the loss resource value of each loss item. The following formula is the formula for determining the allocation index: Y = H*(S+T) 1+R .
[0120] In addition, when assigning pending tasks to audit objects, priority is given to audit objects with the least number of currently processed tasks. If the number of currently processed tasks of an audit object reaches the maximum number after assignment, the audit object will not be considered as a valid audit object that can be assigned.
[0121] Table 1
[0122]
[0123] Table 2
[0124]
[0125] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0126] Based on the same inventive concept, the embodiment of the present application also provides a task allocation device for implementing the task allocation method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more task allocation device embodiments provided below can refer to the limitations on the task allocation method above, and will not be repeated here.
[0127] In an exemplary embodiment, as shown in FIG5 , a task allocation device 500 is provided, comprising: a task acquisition module 501 , a first allocation module 502 and a second allocation module 503 , wherein:
[0128] The task acquisition module 501 is used to acquire the pending tasks contained in the task common pool;
[0129] The first assignment module 502 is used to perform screening based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, determine the first target object that meets the preset matching condition with the pending task, and assign the pending task to the first target object so that the first target object processes the pending task to obtain a first processing result;
[0130] The second allocation module 503 is used to determine a second target object that meets a preset association condition with the first target object, and send the task to be processed and the first processing result to the second target object.
[0131] Furthermore, the tasks to be processed include independent audit tasks and / or associated audit tasks; the device also includes a third allocation module, which is specifically used to: if the task to be processed is an associated audit task, then allocate the associated audit task to the associated object of the associated audit task; the associated audit tasks include audit tasks returned to the fixed guarantee stage and audit tasks returned to the task common pool.
[0132] Furthermore, the third allocation module is specifically used to: if the working status of the associated object is an abnormal working status, convert the associated audit task into an independent audit task, and add the independent audit task to the task common pool.
[0133] Furthermore, the current status includes the working status and the task status. The first allocation module 502 is specifically used to: obtain the work record data of each audit object, and determine the working status of the audit object based on the record; obtain the current number of processed tasks of each audit object, and determine the task status corresponding to the current number of processed tasks; determine the audit object whose working status is a normal working status and whose task status is a normal load status as a valid audit object; based on the task level of the task to be processed and the object level of the valid audit object, determine the first target object that meets the preset matching conditions with the task to be processed from the valid audit objects.
[0134] Furthermore, the first allocation module 502 is specifically used to: obtain the task processing scope of the object level of each valid audit object, and if the task level of the task to be processed matches the task processing scope, determine the valid audit object as the initial audit object; from each initial audit object, determine the initial audit object with the least number of currently processed tasks as the first target object.
[0135] Furthermore, the device also includes a sequence determination module, which is specifically used to: determine the allocation index of the pending tasks based on the duration coefficient of the pending tasks in the task common pool, the loss resource value of the pending tasks, the non-automatic underwriting degree value and the resource object loss data; determine the allocation order of each pending task based on the size of the allocation index of each pending task; obtain the pending tasks contained in the task common pool, including: traversing multiple pending tasks contained in the task common pool based on the allocation order to obtain the pending tasks arranged in the allocation order.
[0136] Furthermore, the sequence determination module is specifically used to: obtain the duration coefficient of the task to be processed in the task common pool, the loss resource value of the task to be processed, the non-automatic underwriting degree value and the resource object loss data; sum the duration coefficient and the resource object loss data to obtain the sum value; perform exponential operation on the sum value to obtain the product value; the exponential parameter of the exponential operation is determined based on the loss resource value; perform the product of the product value and the non-automatic underwriting degree value to obtain the allocation index of the task to be processed.
[0137] Each module in the above task allocation device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
[0138] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store audit task data to be processed, task data contained in a task common pool, data of audit objects, etc. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a task allocation method is implemented.
[0139] Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.
[0140] In an exemplary embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.
[0141] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0142] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0143] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0144] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.
[0145] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0146] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A task allocation method, It is characterized in that The method comprises: Get the pending tasks contained in the task common pool; Based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, a first target object that satisfies a preset matching condition with the pending task is screened, and the pending task is assigned to the first target object so that the first target object processes the pending task to obtain a first processing result; A second target object that meets a preset association condition with the first target object is determined, and the task to be processed and the first processing result are sent to the second target object.
2. The method according to claim 1, It is characterized in that The pending tasks include independent audit tasks and / or associated audit tasks; the independent audit tasks are audit tasks without audit records; after obtaining the pending tasks included in the task common pool, the method further includes: If the task to be processed is the associated audit task, the associated audit task is assigned to the associated object of the associated audit task; the associated audit task includes the audit task returned to the fixed guarantee stage and the audit task returned to the task common pool.
3. The method according to claim 2, It is characterized in that After allocating the associated audit task to the associated object of the associated audit task, the method further includes: If the working state of the associated object is an abnormal working state, the associated audit task is converted into an independent audit task, and the independent audit task is added to the task common pool.
4. The method according to claim 1, It is characterized in that The current state includes a working state and a task state; the screening based on the task level of the pending task, the current state of each audit object, and the object level of each audit object to determine the first target object that meets the preset matching condition with the pending task includes: Acquire work record data of each audit object, and determine the work status of the audit object based on the record; Obtaining the current number of processing tasks for each of the audit objects, and determining the task status corresponding to the current number of processing tasks; Determine that the audit object whose working state is a normal working state and whose task state is a normal load state is a valid audit object; Based on the task level of the task to be processed and the object level of the valid audit object, a first target object that meets a preset matching condition with the task to be processed is determined from the valid audit objects.
5. The method according to claim 4, It is characterized in that The determining, based on the task level of the pending task and the object level of the valid audit object, a first target object that satisfies a preset matching condition with the pending task from the valid audit object comprises: Acquire the task processing scope of the object level of each of the valid audit objects, and if the task level of the task to be processed matches the task processing scope, determine that the valid audit object is the initial audit object; From among the initial audit objects, the initial audit object with the least number of currently processed tasks is determined as the first target object.
6. The method according to claim 1, It is characterized in that Before obtaining the pending tasks contained in the task common pool, the method further includes: Determine the allocation index of the task to be processed according to the duration coefficient of the task to be processed in the task common pool, the loss resource value of the task to be processed, the non-automatic underwriting degree value and the resource object loss data; Determining the allocation order of each of the tasks to be processed based on the size of the allocation index of each of the tasks to be processed; The tasks to be processed contained in the task common pool are obtained, including: Based on the allocation sequence, multiple tasks to be processed included in the task common pool are traversed to obtain the tasks to be processed arranged in the allocation sequence.
7. The method according to claim 6, It is characterized in that The step of determining the allocation index of the task to be processed according to the duration coefficient of the task to be processed in the task common pool, the loss resource value of the task to be processed, the non-automatic underwriting degree value and the resource object loss data includes: Obtaining the duration coefficient of the pending task in the task common pool, the loss resource value of the pending task, the non-automatic underwriting degree value and the resource object loss data; Summing the duration coefficient and the resource object loss data to obtain a sum value; performing an exponential operation on the sum value to obtain a product value; an exponential parameter of the exponential operation is determined based on the loss resource value; The product value and the non-automatic underwriting degree value are multiplied to obtain the allocation index of the task to be processed.
8. A task allocation device, It is characterized in that The device comprises: The task acquisition module is used to obtain pending tasks contained in the task common pool; A first allocation module is used to perform screening based on the task level of the pending task, the current status of each audit object, and the object level of each audit object, determine a first target object that meets a preset matching condition with the pending task, and allocate the pending task to the first target object so that the first target object processes the pending task to obtain a first processing result; The second allocation module is used to determine a second target object that meets a preset association condition with the first target object, and send the task to be processed and the first processing result to the second target object.
9. A computer device comprising a memory and a processor, wherein the memory stores a computer program. It is characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Task management method, device, computer equipment and storage medium
CN107784424A
Auditing task processing method and device, computer equipment and storage medium
CN109816331A
Dispatching system and dispatching method
CN112668819A
Medical task allocation method and device, computer equipment and medium
CN114283929A
Task processing method and device
CN115564303A
