Task adjustment method, device, server and computer-readable storage medium
By analyzing the historical task group and task matching rules and adjusting the planned tasks of the logistics transportation cycle, the problem of high temporary task costs caused by unreasonable planning of planned tasks is solved, and lower transportation costs and higher task execution efficiency are achieved.
Patent Information
- Application Number
- CN201910846956.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-09-09
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2039-09-09
AI Technical Summary
In the logistics field, the planned task planning in some regions cannot match business growth needs, resulting in frequent addition of temporary tasks and increasing transportation costs.
By obtaining the historical task group of the previous transportation cycle of the transit branch line, determine the target planned tasks and target temporary tasks according to the task matching rules, adjust the execution days and loading rate of the target temporary tasks. If the threshold exceeds the threshold, the current transportation cycle will be Plan tasks to adjust to reduce the number of temporary tasks and reduce transportation costs.
Reasonable planning of tasks is achieved, transportation costs are reduced, task execution and loading rates are improved, and business growth needs are met.
Smart Images

Figure CN112465280B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of logistics and transportation technology, and in particular to a task adjustment method, device, server and computer-readable storage medium. Background Art
[0002] In the field of logistics, branch lines connecting transit yards and outlets are important routes in express delivery. During express delivery, on the basis of formulating planned tasks to meet daily needs, temporary tasks will be temporarily added to meet the needs of business growth due to insufficient transportation volume of planned tasks. Temporary tasks are transportation tasks added outside the transportation plan.
[0003] The planned task planning in some areas cannot match the business growth needs, so temporary tasks need to be added in addition to the planned tasks. The need to add temporary tasks frequently indicates that the current task planning is unreasonable, and the transportation cost of temporary tasks is higher than that of planned tasks. Therefore, unreasonable task planning will lead to an increase in transportation costs. Summary of the invention
[0004] The embodiments of the present application provide a task adjustment method, device, server, and computer-readable storage medium, which can reasonably plan tasks.
[0005] In a first aspect, an embodiment of the present application provides a method for adjusting a task, including:
[0006] Acquire a historical task group of a previous transportation cycle of a transfer yard branch line, wherein the historical task group includes a planned task group and a temporary task group;
[0007] Determine a target planned task from the planned task group according to a task matching rule, and determine a target temporary task corresponding to the target planned task from the temporary task group;
[0008] When the target planned task is a qualified task, determining whether the execution days of the target temporary task are greater than an execution days threshold, and determining whether the loading rate of the target temporary task is greater than a temporary task loading rate threshold;
[0009] If the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, the planned tasks of the current transportation cycle are adjusted based on the target temporary task.
[0010] In some implementations, when the target planned task is a qualified task, before determining whether the execution days of the target temporary task are greater than an execution days threshold, the method further includes:
[0011] Determine whether the task execution rate of the target planned task is greater than the planned task execution rate threshold, and determine whether the loading rate of the target planned task is greater than the planned task loading rate threshold;
[0012] If the task execution rate of the target planned task is greater than the planned task execution rate threshold, and the loading rate of the target planned task is greater than the planned task loading rate threshold, then it is determined that the target planned task is passed.
[0013] In some implementations, after determining whether the task execution rate of the target planned task is greater than the planned task execution rate threshold, and determining whether the loading rate of the target planned task is greater than the planned task loading rate threshold, the method further includes:
[0014] If the task execution rate of the target planned task is not greater than the planned task execution rate threshold, or the loading rate of the target planned task is not greater than the planned task loading rate threshold, then reducing the number of the target planned tasks;
[0015] Adjust the planned tasks of the current transportation cycle based on the reduced number of target planned tasks.
[0016] In some implementations, determining the target planned task from the planned task group according to the task matching rule, and determining the target temporary task from the temporary task group, includes:
[0017] Classifying the tasks in the planned task group according to the destination, origin, planned departure shift, and shift type of the tasks in the planned task group to obtain a classified planned task group;
[0018] Selecting a preset task from the classified planned task group as the target planned task;
[0019] Classifying the tasks in the temporary task group according to the destination, origin, planned departure shift, and shift type of the tasks in the temporary task group to obtain a classified temporary task group;
[0020] A task corresponding to the target planned task category is selected from the classified temporary task group as the target temporary task.
[0021] In some implementations, when the target planned task is a qualified task, before determining whether the execution days of the target temporary task are greater than an execution days threshold, the method further includes:
[0022] Determine the target days corresponding to the target temporary task according to the shift type of the target temporary task and the historical days corresponding to the historical task group;
[0023] The execution days threshold is determined according to the target days and the temporary task execution rate threshold.
[0024] In some implementations, the historical task group of the previous transport cycle is the task group corresponding to the previous month of the transfer yard branch line, the shift type corresponding to the target planned task and the target temporary task is week n, and n includes one or more integers from 1 to 7, and the adjustment of the planned task of the current transport cycle based on the target temporary task includes:
[0025] Obtain the difference between the total number of tasks executed and the number of planned tasks in each week n in the previous month, and obtain the number of tasks of the target temporary task;
[0026] Obtain the average value of the difference in week n according to the number of tasks of the target temporary task;
[0027] Determine the average value of the difference as the number of curing tasks in week n;
[0028] Adjust the planned tasks of the current transportation cycle according to the number of solidified tasks.
[0029] In some embodiments, after adjusting the planned tasks of the current transportation cycle according to the number of solidified tasks, the method further includes:
[0030] Obtaining the adjusted execution cost of the planned tasks of the current transportation cycle and the execution cost of the tasks in the historical task group;
[0031] Determining whether the execution cost of the planned task of the current transportation cycle is lower than the execution cost of the tasks in the historical task group;
[0032] If it is lower than that, the adjusted planned task of the current transportation cycle is sent to the terminal;
[0033] If it is not lower than, sending the adjusted task number interval value of the planned task of the current transportation cycle to the terminal, the interval value is determined according to the standard deviation of the difference between the fixed task number and the task number of the target temporary task.
[0034] In a second aspect, the embodiment of the present application further provides a task adjustment device, including:
[0035] A first acquisition unit is used to acquire a historical task group of a previous transportation cycle of a transfer yard branch line, wherein the historical task group includes a planned task group and a temporary task group;
[0036] A first determining unit, configured to determine a target planned task from the planned task group according to a task matching rule, and to determine a target temporary task corresponding to the target planned task from the temporary task group;
[0037] a second determining unit, configured to determine, when the target planned task is a qualified task, whether the execution days of the target temporary task are greater than an execution days threshold, and determine whether the loading rate of the target temporary task is greater than a temporary task loading rate threshold;
[0038] The first adjustment unit is used to adjust the planned tasks of the current transportation cycle based on the target temporary task when the execution days of the target temporary task are greater than the execution days threshold and the loading rate of the target temporary task is greater than the temporary task loading rate threshold.
[0039] In some embodiments, the device further comprises:
[0040] A third determining unit is used to determine whether the task execution rate of the target planned task is greater than the planned task execution rate threshold, and determine whether the loading rate of the target planned task is greater than the planned task loading rate threshold;
[0041] The fourth determination unit is used to determine that the target planned task is passed when the task execution rate of the target planned task is greater than the planned task execution rate threshold and the loading rate of the target planned task is greater than the planned task loading rate threshold.
[0042] In some embodiments, the device further comprises:
[0043] A processing unit, configured to reduce the number of the target planned tasks when the task execution rate of the target planned tasks is not greater than the planned task execution rate threshold, or the loading rate of the target planned tasks is not greater than the planned task loading rate threshold;
[0044] The second adjustment unit is used to adjust the planned tasks of the current transportation cycle according to the reduced number of target planned tasks.
[0045] In some implementations, the first determining unit is specifically configured to:
[0046] Classifying the tasks in the planned task group according to the destination, origin, planned departure shift, and shift type of the tasks in the planned task group to obtain a classified planned task group;
[0047] Selecting a preset task from the classified planned task group as the target planned task;
[0048] Classifying the tasks in the temporary task group according to the destination, origin, planned departure shift, and shift type of the tasks in the temporary task group to obtain a classified temporary task group;
[0049] A task corresponding to the target planned task category is selected from the classified temporary task group as the target temporary task.
[0050] In some embodiments, the device further comprises:
[0051] a fifth determining unit, configured to determine a target number of days corresponding to the target temporary task according to the shift type of the target temporary task and the historical number of days corresponding to the historical task group;
[0052] The sixth determining unit is used to determine the execution days threshold according to the target days and the temporary task execution rate threshold.
[0053] In some implementations, the historical task group of the previous transport cycle is the task group corresponding to the previous month of the transfer yard branch line, the shift type corresponding to the target planned task and the target temporary task is week n, and n includes one or more integers from 1 to 7, and the first adjustment unit is specifically used to:
[0054] Obtain the difference between the total number of tasks executed and the number of planned tasks in each week n in the previous month, and obtain the number of tasks of the target temporary task;
[0055] Obtain the average value of the difference in week n according to the number of tasks of the target temporary task;
[0056] Determine the average value of the difference as the number of curing tasks in week n;
[0057] Adjust the planned tasks of the current transportation cycle according to the number of solidified tasks.
[0058] In some embodiments, the device further comprises:
[0059] A second acquisition unit is used to acquire the execution cost of the planned tasks of the current transportation cycle after adjustment, and the execution cost of the tasks in the historical task group;
[0060] a seventh determination unit, configured to determine whether the execution cost of the planned task of the current transportation cycle is lower than the execution cost of the tasks in the historical task group;
[0061] A first sending unit, configured to send the adjusted planned tasks of the current transportation cycle to the terminal when the execution cost of the planned tasks of the current transportation cycle is lower than the execution cost of the tasks in the historical task group;
[0062] The second sending unit is used to send the adjusted task number interval value of the planned tasks of the current transport cycle to the terminal when the execution cost of the planned tasks of the current transport cycle is not lower than the execution cost of the tasks in the historical task group, and the interval value is determined according to the standard deviation of the difference between the number of fixed tasks and the number of tasks of the target temporary tasks.
[0063] In a third aspect, an embodiment of the present application further provides a server, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, it executes the steps in the adjustment method of any task provided in the embodiment of the present application.
[0064] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a plurality of instructions, wherein the instructions are suitable for a processor to load to execute the steps in the adjustment method of any task provided in the embodiment of the present application.
[0065] In an embodiment of the present application, the task adjustment device obtains the historical task group of the previous transportation cycle of the transfer yard branch line, and the historical task group includes a planned task group and a temporary task group; then, according to the task matching rule, the target planned task is determined from the planned task group, and the target temporary task corresponding to the target planned task is determined from the temporary task group; when the target planned task is a qualified task, it is determined whether the execution days of the target temporary task are greater than the execution days threshold, and whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold; if the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then the planned tasks of the current transportation cycle are adjusted based on the target temporary task. In this scheme, when the execution days of the target temporary task in the previous transportation cycle are greater than the execution days threshold, and the loading rate is greater than the temporary task loading rate threshold, it means that the planned tasks of the current transportation cycle need to be adjusted for the target temporary task at this time, and the planned tasks can be planned more reasonably. BRIEF DESCRIPTION OF THE DRAWINGS
[0066] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0067] Figure 1 It is a flowchart of a method for adjusting a task provided in an embodiment of the present application;
[0068] Figure 2is another flowchart of the method for adjusting a task provided in an embodiment of the present application;
[0069] Figure 3 It is a structural schematic diagram of a task adjustment device provided in an embodiment of the present application;
[0070] Figure 4 is another structural schematic diagram of the task adjustment device provided in an embodiment of the present application;
[0071] Figure 5 It is a schematic diagram of the structure of the server provided in the embodiment of the present application. DETAILED DESCRIPTION
[0072] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0073] In the following description, the specific embodiments of the present application will be described with reference to the steps and symbols performed by one or more computers, unless otherwise stated. Therefore, these steps and operations will be mentioned several times as being performed by a computer, and the computer execution referred to herein includes the operation of a computer processing unit by an electronic signal representing data in a structured form. This operation converts the data or maintains it at a location in the memory system of the computer, which can be reconfigured or otherwise change the operation of the computer in a manner familiar to testers in the field. The data structure maintained by the data is a physical location in the memory, which has specific characteristics defined by the data format. However, the principles of the present application are described in the above text, which does not represent a limitation, and testers in the field will understand that the various steps and operations described below can also be implemented in hardware.
[0074] The principles of the present application may be operated using many other general or specific purpose computing, communication environments or configurations. Examples of well-known computing systems, environments and configurations suitable for use with the present application may include, but are not limited to, handheld phones, personal computers, servers, multiprocessor systems, microcomputer-based systems, mainframe computers, and distributed computing environments, including any of the above systems or devices.
[0075] The terms "first", "second", and "third" in this application are used to distinguish different objects rather than to describe a specific order. In addition, the terms "include", "have", and any variations thereof are intended to cover non-exclusive inclusions.
[0076] See also Figure 1 , Figure 1 : is a flowchart of a method for adjusting a task provided in an embodiment of the present application. The execution subject of the method for adjusting the task may be a device for adjusting the task provided in an embodiment of the present application, or a server integrating the device for adjusting the task, wherein the device for adjusting the task may be implemented in hardware or software. The method for adjusting the task may include:
[0077] 101. Obtain a historical task group of a previous transportation cycle of a transfer yard branch line, where the historical task group includes a planned task group and a temporary task group.
[0078] This embodiment can be processed on a natural month basis. In this case, the historical task group of the previous transportation cycle may be the task group corresponding to the transit point that required task adjustment in the previous month. The tasks in the historical task group are the tasks that have been executed in the previous transportation cycle. The historical task group includes a planned task group and a temporary task group. The tasks in the planned task group are the tasks in the transportation plan, and the tasks in the temporary task group are the tasks outside the transportation plan. For example, when the planned task planning of the transit point cannot match the business growth needs, that is, the planned tasks cannot meet the freight requirements, then it is necessary to add corresponding temporary tasks.
[0079] Among them, the task in this application is the branch line task of the transfer yard. When the task of the previous cycle is completed, it is necessary to obtain the historical task group of the previous cycle, and adjust the planned tasks of the current transportation cycle according to the tasks in the historical task group. The current transportation cycle is the transportation cycle that currently requires task planning.
[0080] 102. Determine a target planned task from the planned task group according to a task matching rule, and determine a target temporary task corresponding to the target planned task from the temporary task group.
[0081] Specifically, the tasks in the planned task group can be classified according to the task matching rules to obtain multiple categories of planned tasks, and then the tasks that currently need to be processed are determined as target planned tasks, wherein the tasks that currently need to be processed are tasks for determining whether to adjust the planned tasks for the current transportation cycle.
[0082] Among them, the task matching rules in the present application include: the destination, origin, planned departure shift and shift type of the task. At this time, the target planned task is determined from the plan task group according to the task matching rules, including: classifying the tasks in the plan task group according to the destination, origin, planned departure shift and shift type of the tasks in the plan task group to obtain the classified plan task group, and selecting a preset type task from the classified plan task group as the target planned task, wherein the preset type task is the task category that needs to be processed currently.
[0083] Among them, the planned departure shifts in this application include the departure time of the trucks that transfer goods (express mail). In some embodiments, a day can be divided into 7 shifts, that is, 7 departure times. The shift type is week n, where n includes one or more integers from 1 to 7. In some embodiments of this application, the shift type can be divided into multiple collection types and bulk types from Monday to Sunday according to the different properties of collection and bulk cargo based on historical experience. In some embodiments, the collection type (origin to transfer yard) includes: collection 1-5 (i.e., collection from Monday to Friday) and collection 6-7 (i.e., collection from Saturday to Sunday), and the bulk cargo type (transfer yard to destination) includes: bulk 2-6 (i.e., bulk cargo from Tuesday to Saturday) and bulk 7-1 (i.e., bulk cargo from Sunday to Monday).
[0084] Similarly, the present application also needs to determine the target temporary task from the temporary task group according to the task matching rule, wherein the task matching rule is the same as the task matching rule corresponding to the target task group, and the target temporary task is of the same category as the target planned task.
[0085] In some embodiments, when determining a target planned task, it is necessary to determine whether the target planned task is a qualified task, specifically, whether the task execution rate of the target planned task is greater than the planned task execution rate threshold (which can be preset, such as 90%), and whether the loading rate of the target planned task is greater than the planned task loading rate threshold (which can be preset, such as 60%); if the task execution rate of the target planned task is greater than the planned task execution rate threshold, and the loading rate of the target planned task is greater than the planned task loading rate threshold, then the target planned task is determined to be qualified. Among them, the loading rate of the target planned task can be the average loading rate of the tasks in the target planned task.
[0086] In some embodiments, when there is no target temporary task corresponding to the target planned task, there is no need to judge the target temporary task at this time. It is only necessary to judge whether the target planned task is a qualified task. When it is a qualified task, there is no need to adjust the target planned task of the current transportation cycle. When it is an unqualified task, it is necessary to adjust the target planned task of the current transportation cycle. For example, when there is a train trip in the target planned task whose historical execution rate has been very low or the loading rate has been very low, the train trip will be reduced.
[0087] 103. When the target planned task is a qualified task, determine whether the execution days of the target temporary task are greater than the execution days threshold, and determine whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold.
[0088] When it is determined that the target planned task is a qualified task and there is a target temporary task corresponding to the target planned task, it is determined whether the execution days of the target temporary task are greater than the execution days threshold, and whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold.
[0089] The loading rate of the target temporary task may be an average loading rate of tasks in the target temporary task.
[0090] Among them, in some embodiments, the execution order of determining whether the execution days of the target temporary task are greater than the execution days threshold is before determining whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold. In other embodiments, the execution order of these two judgment steps is not limited.
[0091] Among them, if it is determined that the execution days of the target temporary task are not greater than the execution day threshold, and it is determined that the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then it is determined that the increase of the target temporary task is reasonable, but since the execution days are not many, there is no solidification requirement.
[0092] If it is determined that the execution days of the target temporary task are not greater than the execution day threshold, and it is determined that the loading rate of the target temporary task is not greater than the temporary task loading rate threshold, then it is determined that although there is an unreasonable increase in the target temporary task, there is still no solidification requirement because the execution days are not many.
[0093] If it is determined that the execution days of the target temporary task are greater than the execution days threshold, and it is determined that the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then it is determined that the increase of the target temporary task is reasonable, and since the execution days of the target temporary task are greater than the execution days threshold, the increase of the target temporary task is reasonable at this time, and since the execution days are relatively large, the target temporary task has a certain periodicity and universality, so it is necessary to solidify the target temporary task (adjust the planned tasks of the current transportation cycle based on the target temporary task), and refer to step 104 for the specific solidification process.
[0094] When the natural month is used as the transportation cycle in this embodiment, the method for determining the execution day threshold of the present application is: determine the target days corresponding to the target temporary task according to the shift type of the target temporary task and the historical days corresponding to the historical task group; determine the execution day threshold according to the target days and the temporary task execution rate threshold.
[0095] Specifically, in some embodiments, because temporary tasks have a certain degree of uncertainty compared to planned tasks, the thresholds for temporary task execution rate and loading rate should be lower than the thresholds for planned task execution rate and loading rate. Referring to empirical data, the threshold for temporary task loading rate is D=30%, and the threshold for temporary task execution rate is C′=60%. Since the focus of temporary tasks is whether they are periodic and universal, it is more appropriate to judge the number of execution days here. Because there are differences in the number of natural days N per month, the execution days threshold C is a dynamic threshold, and the shift type corresponding to the target temporary task is shift type X. At this time, the calculation method for the execution days threshold is: Among them, x i is the shift type corresponding to the i-th day; I(x i =X) is an indicative function, when x i =X, the value is 1, otherwise it is 0; Round() is the rounding function.
[0096] 104. If the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, the planned tasks of the current transportation cycle are adjusted based on the target temporary task.
[0097] In this embodiment, if the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then the target temporary task needs to be solidified at this time to obtain the corresponding solidified task (that is, the planned task added in the current transportation cycle), that is, the planned tasks of the current transportation cycle are adjusted based on the target temporary task, and the number of planned tasks in the current transportation cycle is increased according to the target temporary task, so as to reduce the number of temporary tasks when executing the transportation tasks of the current transportation cycle, thereby reducing transportation costs.
[0098] In some embodiments, when the shift type corresponding to the target planned task and the target temporary task is week n, and n includes one or more integers from 1 to 7, the planned tasks of the current transportation cycle are adjusted based on the target temporary task, including: obtaining the difference between the total number of task executions and the number of planned tasks for each week n in the previous month, and obtaining the number of tasks of the target temporary task; obtaining the average value of the difference for week n according to the number of tasks of the target temporary task; determining the average value of the difference as the number of solidified tasks for week n; and adjusting the planned tasks of the current transportation cycle according to the number of solidified tasks.
[0099] Specifically, on the basis of the target planned task of the previous transportation cycle, the number of solidified tasks of the corresponding week is increased, that is, this embodiment needs to determine the day of the week that needs to be solidified and the number of solidified tasks corresponding to the day of the week. For example, when the target planned task is a shift type of 7-1, then the number of solidified tasks for Sunday to Monday needs to be calculated. The following is an example of calculating the number of solidified tasks on Monday: the total number of target task executions for each Monday in the historical task group (that is, the total number of tasks corresponding to the target task matching rule, where the target matching rule is the matching rule corresponding to the target planned task) and the difference y in the number of target planned tasks are counted ij , i represents the week number corresponding to the current shift type, i is equal to 1 on Monday, j represents the week number, this application determines the average difference on Monday based on the difference on each Monday in the historical task group and the standard deviation of the difference on Monday because It may be a non-integer. To avoid wasting resources as much as possible, the recommended number of curing tasks corresponding to curing week i is Floor() is a rounding function. This application uses the average difference Determine the number of curing tasks that correspond to Monday.
[0100] Among them, the recommendation results include not only the week that needs to be recommended and the number of fixed tasks for that week, but also the name of the corresponding transfer station and the content corresponding to the task matching rule corresponding to the target task, such as the destination, origin, planned departure flight and flight type of the task.
[0101] In some embodiments, in addition to recommending the week that needs curing and the number of curing tasks corresponding to the week, it is also necessary to recommend the curing carrier type, curing tonnage, and curing mileage of the tasks that need curing, wherein the method for determining the curing carrier type, curing tonnage, and curing mileage is as follows:
[0102] Fixed carrier type: In order to make the planned resources meet the actual situation, the fixed carrier type is recommended according to the proportion of self-operated and outsourced in the executed target temporary tasks. For example: Recommended fixed week i, the number of self-operated tasks in the executed temporary tasks in the month is a i1 , the number of outsourced tasks is a i2 , then the number of self-operated tasks in the corresponding solidified tasks is recommended to be The number of outsourced tasks is
[0103] Fixed tonnage: According to the mode of the tonnage of self-operated tasks in the executed target temporary tasks, the recommended fixed tonnage of self-operated tasks is set; when the mode is not unique, the smaller value is selected. Similarly, the recommended fixed tonnage of outsourced tasks can be obtained.
[0104] Fixed mileage: According to the mode of line mileages that have executed the target plan tasks, set the line mileage L corresponding to the fixed task.
[0105] In some embodiments, after the planned tasks of the current transport cycle are adjusted according to the fixed number of tasks, the method also includes: obtaining the execution cost of the adjusted planned tasks of the current transport cycle, and the execution cost of the tasks in the historical task group; determining whether the execution cost of the planned tasks of the current transport cycle is lower than the execution cost of the tasks in the historical task group; if lower, sending the adjusted planned tasks of the current transport cycle to the terminal; if not lower, sending the adjusted task number interval value of the planned tasks of the current transport cycle to the terminal, and the interval value is determined according to the standard deviation of the difference between the fixed number of tasks and the number of tasks of the target temporary task.
[0106] Specifically, whether the above curing scheme is reasonable can be judged based on whether the cost decreases after the task is cured. In some embodiments, the current task cost is recommended to be cured on the first week. Where M is the number of target temporary tasks that have been executed, cost 1it The cost of each executed temporary target task. Since there is a difference in the number of tasks between the recommended fixed tasks and the executed temporary target tasks, in order to eliminate the impact of the number of tasks on cost judgment, the current task cost is standardized by the total number of recommended fixed tasks and the executed temporary target tasks, that is, the current task cost used for comparison is:
[0107]
[0108] Because it is a common knowledge that the cost of planned tasks is lower than the cost of temporary tasks, the planned task cost is preferred for estimation of the solidified task cost. At the same time, in order to avoid the impact of line mileage on cost estimation, the concept of per-kilometer cost is selected here. The part of the corresponding per-kilometer cost of planned tasks that cannot be estimated in self-operated and outsourced tasks: For self-operated tasks, since the vehicle depreciation costs, labor costs, etc. are not the same in planned and temporary tasks, a reasonable assumption is made here that "there is no significant difference between the self-operated per-kilometer cost in planned tasks and the self-operated per-kilometer cost in temporary tasks", that is, the self-operated per-kilometer cost in planned tasks can be replaced by the self-operated per-kilometer cost in temporary tasks; for outsourced tasks, their temporary situation will have a greater impact on the cost. Therefore, when the outsourced per-kilometer cost in planned tasks cannot be obtained, the average per-kilometer cost of outsourced planned tasks in the current area should be selected. In summary, the recommended task cost after solidifying the solidified tasks of week i (that is, the planned tasks that need to be added on week i) is:
[0109]
[0110] Among them, cost 2itis the cost of each executed planned task (the task corresponding to the target task matching rule week i), L t is the mileage of each executed planned task, Ω1 is the set of self-operated tasks in the executed planned tasks, Ω2 is the set of outsourced tasks in the executed planned tasks, Ω3 is the set of self-operated tasks in the executed temporary tasks, Ω4 is the set of outsourced tasks in the executed planned tasks in the area to which the task belongs, and Nvl() is a filling function, that is, Nvl(A,B) means taking A first, and taking B when A is empty.
[0111] Compare old_fee i with new_fee i , if new_fee i ≤old_fee i , that is, the cost of the task is reduced after solidification, and the solidification solution is considered reasonable, then the recommended solidification related information is output to the terminal, and the process ends. i >old_fee i , that is, the cost does not decrease after the task is solidified, and only the recommended solidification task number interval is output to the terminal For reference. Ceil() is a round-up function. The embodiment of the present application needs to execute the task adjustment method in the present solution for each category (type) of task, and the task adjustment for each category can be executed in parallel or sequentially.
[0112] In an embodiment of the present application, the task adjustment device obtains the historical task group of the previous transportation cycle of the transfer yard branch line, and the historical task group includes a planned task group and a temporary task group; then, according to the task matching rule, the target planned task is determined from the planned task group, and the target temporary task corresponding to the target planned task is determined from the temporary task group; when the target planned task is a qualified task, it is determined whether the execution days of the target temporary task are greater than the execution days threshold, and whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold; if the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then the planned tasks of the current transportation cycle are adjusted based on the target temporary task. In this scheme, when the execution days of the target temporary task in the previous transportation cycle are greater than the execution days threshold, and the loading rate is greater than the temporary task loading rate threshold, it means that the planned tasks of the current transportation cycle need to be adjusted for the target temporary task at this time, and the planned tasks can be planned more reasonably.
[0113] Among them, this solution is applied to branch line task optimization, which can improve problems such as low task execution rate and low loading rate. The output planning tasks are more in line with actual business volume needs, which facilitates global resource integration and allocation. By solidifying temporary tasks, it can effectively reduce transportation costs.
[0114] In terms of operational use, the optimization plan can be completely calculated and judged through systematic program, providing managers with reasonable reference opinions.
[0115] The method for adjusting the tasks described in the above embodiment will be further described below.
[0116] Please refer to Figure 2 , Figure 2 Another flowchart of the task adjustment method provided in the embodiment of the present application is shown in FIG. The task adjustment method can be applied to a server, such as Figure 2 As shown, the process of the adjustment method of the task can be as follows:
[0117] 201. Obtain the historical task group of the previous transportation cycle of the transfer yard branch line, where the historical task group includes a planned task group and a temporary task group.
[0118] The transportation cycle mentioned in the present application can be based on natural months, wherein the historical task group of the previous transportation cycle can be the task group corresponding to the transit point that needs to adjust the task in the previous month. The tasks in the historical task group are the tasks that have been executed in the previous transportation cycle. The historical task group includes planned task groups and temporary task groups.
[0119] Among them, the task in this application is the branch line task of the transfer yard. When the task of the previous cycle is completed, it is necessary to obtain the historical task group of the previous cycle, and adjust the planned tasks of the current transportation cycle according to the tasks in the historical task group. The current transportation cycle is the transportation cycle that currently requires task planning.
[0120] 202. Determine a target planned task from the planned task group according to a task matching rule.
[0121] Among them, the task matching rules in the present application include: the destination, origin, planned departure shift and shift type of the task. At this time, the target planned task is determined from the plan task group according to the task matching rules, including: classifying the tasks in the plan task group according to the destination, origin, planned departure shift and shift type of the tasks in the plan task group to obtain the classified plan task group, and selecting a preset type task from the classified plan task group as the target planned task, wherein the preset type task is the task category that needs to be processed currently.
[0122] Among them, the shift type in the present application includes week n, where n includes one or more integers from 1 to 7. In some embodiments of the present application, the shift type can be divided into multiple collection types and bulk types from Monday to Sunday according to the different properties of collection and bulk cargo based on historical experience. In some embodiments, the collection types include: collection 1-5 and collection 6-7, and the bulk cargo types include: bulk 2-6 and bulk 7-1.
[0123] Among them, the present application can use multiple week types as a shift type, which can improve the efficiency of calculation.
[0124] 203. Determine whether the task execution rate of the target planned task is greater than the planned task execution rate threshold. If so, execute step 204; if not, execute step 205.
[0125] In some embodiments, when a target planned task is determined from a historical task group, it is necessary to determine whether the execution rate of the target planned task is greater than a planned task execution rate threshold, wherein the planned task execution rate threshold is a value pre-set based on historical experience, which may be 90%, and the specific value is not limited here.
[0126] 204. Determine whether the loading rate of the target planned task is greater than the planned task loading rate threshold. If so, execute step 206; if not, execute step 205.
[0127] In some embodiments, if the task execution rate of the target planned task is not greater than the planned task execution rate threshold, then it is necessary to determine whether the loading rate of the target planned task is greater than the planned task loading rate threshold, wherein the planned task loading rate threshold is a value pre-set based on historical experience, which can be 60%, and the specific value is not limited here.
[0128] In some other embodiments, the execution order of step 203 and step 204 is not limited.
[0129] 205. Reduce the number of target planning tasks in the current transportation cycle.
[0130] Among them, if it is determined that the task execution rate of the target planned task is not greater than the planned task execution rate threshold, or the loading rate of the target planned task is not greater than the planned task loading rate threshold, it means that the target planned task in the previous transportation cycle has not been fully utilized. At this time, the number of target planned tasks in the current transportation cycle should be reduced. Specifically, the tasks corresponding to the trains whose historical execution rates or loading rates have been very low in the target planned tasks can be reduced.
[0131] 206. Determine whether there is a target temporary task corresponding to the target planned task. If so, execute step 208; if not, execute step 207.
[0132] If it is determined that the loading rate of the target planned task is greater than the planned task loading rate threshold, then the target temporary task of the previous transportation cycle can be determined as a qualified task. At this time, it is necessary to determine whether there is a target temporary task corresponding to the target planned task in the historical task group, that is, to determine whether there is a temporary task of the same category as the target temporary task.
[0133] 207. Confirm that the target plan tasks are qualified and there are no temporary related issues.
[0134] In some embodiments, if there is no target temporary task corresponding to the target planned task, a judgment result can be outputted at this time that the target planned task is qualified and there are no temporary related issues, that is, there is no target temporary task that needs to be solidified at this time.
[0135] 208. Determine whether the execution days of the target temporary task are greater than the execution days threshold. If so, execute step 209; if not, execute step 211.
[0136] If there is a target temporary task corresponding to the target planned task, it is necessary to determine whether the execution days of the target temporary task are greater than the execution days threshold, that is, determine the execution days of the target temporary task within a month. In some embodiments, the method for determining the execution days threshold is as follows:
[0137] The temporary task loading rate threshold is D, and the temporary task execution rate threshold is C'. Since the focus of temporary tasks is whether they are periodic and universal, it is more appropriate to judge the execution days here. Since the number of natural days N in each month is different, the execution days threshold C is a dynamic threshold. The shift type corresponding to the target temporary task is shift type X. At this time, the calculation method of the execution days threshold is: Among them, x i is the shift type corresponding to the i-th day; I(x i =X) is an indicative function, when x i =X, the value is 1, otherwise it is 0; Round() is the rounding function.
[0138] 209. Determine whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold. If so, execute step 210; if not, execute step 211.
[0139] In some embodiments, when it is determined that the execution days of the target temporary task are greater than the execution days threshold, it means that the target temporary task has a certain long-term and universal nature. At this time, it can be further determined whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold.
[0140] The temporary task loading rate threshold is determined based on historical experience, and its value may be 30%. The specific value is not limited here.
[0141] 210. Solidify the target temporary task in the current transportation cycle and determine the solidification result.
[0142] In this embodiment, when the execution days of the target temporary task are greater than the execution days threshold and the loading rate is greater than the temporary task loading rate threshold, it can be determined that the target temporary task needs to be solidified and a solidification result is obtained.
[0143] Specifically, the target temporary task is solidified, that is, on the basis of the target planned task of the previous transportation cycle, the number of solidified tasks of the corresponding week is increased, that is, this embodiment needs to determine the day of the week that needs to be solidified, and the number of solidified tasks corresponding to the day of the week. For example, when the target planned task is a shift type of 7-1, then the number of solidified tasks for Sunday to Monday needs to be calculated. The following is an example of calculating the number of solidified tasks on Monday: the total number of target task executions on each Monday in the historical task group (that is, the total number of tasks corresponding to the target task matching rule, where the target matching rule is the matching rule corresponding to the target planned task) and the difference y in the number of target planned tasks are counted ij , i represents the week number corresponding to the current shift type, i is equal to 1 on Monday, j represents the week number, this application determines the average difference on Monday based on the difference on each Monday in the historical task group and the standard deviation of the difference on Monday because It may be a non-integer. To avoid wasting resources as much as possible, the recommended number of curing tasks corresponding to curing week i is Floor() is a rounding function. This application uses the average difference Determine the number of curing tasks that correspond to Monday.
[0144] Among them, the recommendation results include not only the week that needs to be recommended and the number of fixed tasks for that week, but also the name of the corresponding transfer station and the content corresponding to the task matching rule corresponding to the target task, such as the destination, origin, planned departure flight and flight type of the task.
[0145] In some embodiments, in addition to recommending the week that needs to be cured and the number of curing tasks corresponding to that week, it is also necessary to recommend the type of carrier that needs to be cured, the tonnage that needs to be cured, and the mileage that needs to be cured. The specific determination method is the same as Figure 1 The corresponding determination method is similar and will not be described in detail here.
[0146] 211. Confirm that there is no fixed demand for this temporary target task.
[0147] In some embodiments, when it is determined that the execution days of the target temporary task are not greater than the execution days threshold, or when it is determined that the loading rate of the target temporary task is not greater than the temporary task loading rate threshold, it can be determined that the target temporary task has no solidification requirement, that is, there is no need to solidify the target temporary task.
[0148] Among them, when it is determined that the execution days of the target temporary task are not greater than the execution days threshold, but the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then it is determined that the increase in the target temporary task in the previous transportation cycle is reasonable, but there is no long-term general need, and there is no need to solidify it.
[0149] When it is determined that the execution days of the target temporary task are not greater than the execution days threshold, and the loading rate of the target temporary task is not greater than the temporary task loading rate threshold, it is determined that the increase of the target temporary task in the previous transportation cycle is unreasonable.
[0150] 212. Determine whether the total cost of the task after curing is lower than the total cost of the task before curing. If so, execute step 213; if not, execute step 214.
[0151] In some embodiments, after the temporary tasks are solidified, it is also necessary to determine whether the execution cost of the planned tasks of the current transport cycle is lower than the execution cost of the tasks in the historical task group; or to determine whether the solidified tasks of the current transport cycle (the planned tasks added based on the temporary tasks) are lower than the execution cost of the temporary tasks of the previous transport cycle.
[0152] Specifically, when the task needs to be fixed to a specific number of weeks, the cost comparison should be carried out for each week that needs to be fixed. The specific comparison method is the same as Figure 1 The corresponding embodiments are similar and will not be described in detail here.
[0153] 213. Send the planned tasks adjusted for the current transportation cycle to the terminal.
[0154] When the total cost of the task after solidification is lower than the total cost of the task before solidification, it means that the solidification plan is reasonable. At this time, the planned tasks adjusted for the current transportation cycle can be directly output to the terminal (the number of solidification tasks to be solidified is increased based on the previous transportation cycle).
[0155] 214. Send the adjusted task number interval value of the planned tasks of the current transportation cycle to the terminal.
[0156] When the total cost of the task after solidification is not lower than the total cost of the task before solidification, it means that the solidification plan is unreasonable. At this time, it is only necessary to output the adjusted task number interval value of the planned task of the current transportation cycle, where the interval value is determined according to the standard deviation of the difference between the number of solidified tasks and the number of tasks of the target temporary tasks.
[0157] In an embodiment of the present application, the server obtains the historical task group of the previous transportation cycle of the transfer yard branch line, and the historical task group includes a planned task group and a temporary task group; then, according to the task matching rules, the target planned task is determined from the planned task group, and the target temporary task corresponding to the target planned task is determined from the temporary task group; when the target planned task is a qualified task, it is determined whether the execution days of the target temporary task are greater than the execution days threshold, and whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold; if the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then the planned tasks of the current transportation cycle are adjusted based on the target temporary task. In this scheme, when the execution days of the target temporary task in the previous transportation cycle are greater than the execution days threshold, and the loading rate is greater than the temporary task loading rate threshold, it means that the planned tasks of the current transportation cycle need to be adjusted for the target temporary task at this time, and the planned tasks can be planned more reasonably.
[0158] In order to facilitate better implementation of the task adjustment method provided in the embodiment of the present application, the embodiment of the present application also provides a device based on the task adjustment method. The meanings of the terms are the same as those in the task adjustment method, and the specific implementation details can refer to the description in the method embodiment.
[0159] See also Figure 3 , Figure 3 A schematic diagram of the structure of a task adjustment device provided in an embodiment of the present application, wherein the task adjustment device 300 may include a first acquisition unit 301, a first determination unit 302, a second determination unit 303, and a first adjustment unit 304, etc., wherein:
[0160] The first acquisition unit 301 is used to acquire a historical task group of a previous transportation cycle of a transfer yard branch line, wherein the historical task group includes a planned task group and a temporary task group;
[0161] A first determining unit 302 is used to determine a target planned task from the planned task group according to a task matching rule, and to determine a target temporary task corresponding to the target planned task from the temporary task group;
[0162] The second determining unit 303 is used to determine whether the execution days of the target temporary task are greater than the execution days threshold, and determine whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold when the target planned task is a qualified task;
[0163] The first adjustment unit 304 is used to adjust the planned tasks of the current transportation cycle based on the target temporary task when the execution days of the target temporary task are greater than the execution days threshold and the loading rate of the target temporary task is greater than the temporary task loading rate threshold.
[0164] See also Figure 4 In some embodiments, the device further comprises:
[0165] The third determining unit 305 is used to determine whether the task execution rate of the target planned task is greater than the planned task execution rate threshold, and determine whether the loading rate of the target planned task is greater than the planned task loading rate threshold;
[0166] The fourth determining unit 306 is used to determine that the target planned task is passed when the task execution rate of the target planned task is greater than the planned task execution rate threshold and the loading rate of the target planned task is greater than the planned task loading rate threshold.
[0167] In some embodiments, the device further comprises:
[0168] The processing unit 307 is used to reduce the number of the target planned tasks when the task execution rate of the target planned tasks is not greater than the planned task execution rate threshold, or the loading rate of the target planned tasks is not greater than the planned task loading rate threshold;
[0169] The second adjustment unit 308 is used to adjust the planned tasks of the current transportation cycle according to the reduced number of target planned tasks.
[0170] In some implementations, the first determining unit 302 is specifically configured to:
[0171] Classifying the tasks in the planned task group according to the destination, origin, planned departure shift, and shift type of the tasks in the planned task group to obtain a classified planned task group;
[0172] Selecting a preset task from the classified planned task group as the target planned task;
[0173] Classifying the tasks in the temporary task group according to the destination, origin, planned departure shift, and shift type of the tasks in the temporary task group to obtain a classified temporary task group;
[0174] A task corresponding to the target planned task category is selected from the classified temporary task group as the target temporary task.
[0175] In some embodiments, the device further comprises:
[0176] A fifth determining unit 309 is used to determine the target days corresponding to the target temporary task according to the shift type of the target temporary task and the historical days corresponding to the historical task group;
[0177] The sixth determining unit 310 is configured to determine the execution days threshold according to the target days and the temporary task execution rate threshold.
[0178] In some implementations, the historical task group of the previous transport cycle is the task group corresponding to the previous month of the transfer yard branch line, the shift type corresponding to the target planned task and the target temporary task is week n, and n includes one or more integers from 1 to 7, and the first adjustment unit 304 is specifically used to:
[0179] Obtain the difference between the total number of tasks executed and the number of planned tasks in each week n in the previous month, and obtain the number of tasks of the target temporary task;
[0180] Obtain the average value of the difference in week n according to the number of tasks of the target temporary task;
[0181] Determine the average value of the difference as the number of curing tasks in week n;
[0182] Adjust the planned tasks of the current transportation cycle according to the number of solidified tasks.
[0183] In some embodiments, the device further comprises:
[0184] The second acquisition unit 311 is used to acquire the execution cost of the planned tasks of the current transportation cycle after adjustment, and the execution cost of the tasks in the historical task group;
[0185] The seventh determining unit 312 is used to determine whether the execution cost of the planned task of the current transportation cycle is lower than the execution cost of the tasks in the historical task group;
[0186] The first sending unit 313 is used to send the adjusted planned tasks of the current transportation cycle to the terminal when the execution cost of the planned tasks of the current transportation cycle is lower than the execution cost of the tasks in the historical task group;
[0187] The second sending unit 314 is used to send the adjusted task number interval value of the planned tasks of the current transport cycle to the terminal when the execution cost of the planned tasks of the current transport cycle is not lower than the execution cost of the tasks in the historical task group, and the interval value is determined according to the standard deviation of the difference between the number of fixed tasks and the number of tasks of the target temporary tasks.
[0188] In the embodiment of the present application, the first acquisition unit 301 acquires the historical task group of the previous transportation cycle of the transfer yard branch line, and the historical task group includes a planned task group and a temporary task group; then the first determination unit 302 determines the target planned task from the planned task group according to the task matching rule, and determines the target temporary task corresponding to the target planned task from the temporary task group; when the target planned task is a qualified task, the second determination unit 303 determines whether the execution days of the target temporary task are greater than the execution days threshold, and determines whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold; if the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then the first adjustment unit 304 adjusts the planned tasks of the current transportation cycle based on the target temporary task. In this scheme, when the execution days of the target temporary task in the previous transportation cycle are greater than the execution days threshold, and the loading rate is greater than the temporary task loading rate threshold, it means that the planned tasks of the current transportation cycle need to be adjusted for the target temporary task at this time, and the planned tasks can be planned more reasonably.
[0189] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0190] refer to Figure 5 The embodiment of the present application provides a server 500, which may include one or more processing core processors 501, one or more computer-readable storage media memories 502, radio frequency (RF) circuits 503, power supplies 504, input units 505, and display units 506. Those skilled in the art will appreciate that Figure 5 The server structure shown in the figure does not constitute a limitation on the server, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:
[0191] The processor 501 is the control center of the server, and uses various interfaces and lines to connect various parts of the entire server. By running or executing software programs and / or modules stored in the memory 502, and calling data stored in the memory 502, the processor 501 performs various functions of the server and processes data, thereby monitoring the server as a whole. Optionally, the processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 501.
[0192] The memory 502 may be used to store software programs and modules. The processor 501 executes various functional applications and data processing by running the software programs and modules stored in the memory 502 .
[0193] The RF circuit 503 may be used for receiving and sending signals during the process of sending and receiving information.
[0194] The server also includes a power supply 504 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 501 through a power management system, so that the power management system can manage charging, discharging, power consumption and other functions.
[0195] The server may further include an input unit 505, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
[0196] The server may also include a display unit 506, which may be used to display information input by a user or information provided to a user and various graphical user interfaces of the server, which may be composed of graphics, text, icons, videos, and any combination thereof. Specifically in this embodiment, the processor 501 in the server will load the executable files corresponding to the processes of one or more applications into the memory 502 according to the following instructions, and the processor 501 will run the applications stored in the memory 502, thereby realizing various functions, as follows:
[0197] Acquire a historical task group of a previous transportation cycle of a transfer yard branch line, wherein the historical task group includes a planned task group and a temporary task group;
[0198] Determine a target planned task from the planned task group according to a task matching rule, and determine a target temporary task corresponding to the target planned task from the temporary task group;
[0199] When the target planned task is a qualified task, determining whether the execution days of the target temporary task are greater than an execution days threshold, and determining whether the loading rate of the target temporary task is greater than a temporary task loading rate threshold;
[0200] If the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, the planned tasks of the current transportation cycle are adjusted based on the target temporary task.
[0201] In the above embodiments, the description of each embodiment has its own focus. For the part that is not described in detail in a certain embodiment, please refer to the detailed description of the task adjustment method above, which will not be repeated here.
[0202] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0203] To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the steps in any of the task adjustment methods provided in the embodiments of the present application. For example, the instructions can execute the following steps:
[0204] Acquire a historical task group of a previous transportation cycle of a transfer yard branch line, wherein the historical task group includes a planned task group and a temporary task group;
[0205] Determine a target planned task from the planned task group according to a task matching rule, and determine a target temporary task corresponding to the target planned task from the temporary task group;
[0206] When the target planned task is a qualified task, determining whether the execution days of the target temporary task are greater than an execution days threshold, and determining whether the loading rate of the target temporary task is greater than a temporary task loading rate threshold;
[0207] If the execution days of the target temporary task are greater than the execution days threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, the planned tasks of the current transportation cycle are adjusted based on the target temporary task.
[0208] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0209] The storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0210] Since the instructions stored in the storage medium can execute the steps in the adjustment method of any task provided in the embodiments of the present application, the beneficial effects that can be achieved by the adjustment method of any task provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.
[0211] The above is a detailed introduction to a task adjustment method, device, server and computer-readable storage medium provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A task adjustment method, characterized in that: include: Acquire a historical task group of a previous transportation cycle of a transfer yard branch line, wherein the historical task group includes a planned task group and a temporary task group; Determine a target planned task from the planned task group according to a task matching rule, and determine a target temporary task corresponding to the target planned task from the temporary task group; When the target planned task is a qualified task, determining whether the execution days of the target temporary task are greater than an execution days threshold, and determining whether the loading rate of the target temporary task is greater than a temporary task loading rate threshold; The historical task group of the previous transport cycle is the task group corresponding to the previous month of the transfer yard branch line, and the shift type corresponding to the target planned task and the target temporary task is week n, where n includes one or more integers from 1 to 7; If the number of execution days of the target temporary task is greater than the execution day threshold, and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, then the difference between the total number of task executions and the number of planned tasks for each of the weeks n in the previous month is obtained to obtain the number of tasks of the target temporary task; Obtain the average value of the difference in week n according to the number of tasks of the target temporary task; Determine the average value of the difference as the number of curing tasks in week n; Adjust the planned tasks of the current transportation cycle according to the number of solidified tasks.
2. The method according to claim 1, characterized in that: When the target planned task is a qualified task, before determining whether the execution days of the target temporary task are greater than an execution days threshold, the method further includes: Determine whether the task execution rate of the target planned task is greater than the planned task execution rate threshold, and determine whether the loading rate of the target planned task is greater than the planned task loading rate threshold; If the task execution rate of the target planned task is greater than the planned task execution rate threshold, and the loading rate of the target planned task is greater than the planned task loading rate threshold, then it is determined that the target planned task is passed.
3. The method according to claim 2, characterized in that After determining whether the task execution rate of the target planned task is greater than the planned task execution rate threshold, and determining whether the loading rate of the target planned task is greater than the planned task loading rate threshold, the method further includes: If the task execution rate of the target planned task is not greater than the planned task execution rate threshold, or the loading rate of the target planned task is not greater than the planned task loading rate threshold, then reducing the number of the target planned tasks; Adjust the planned tasks of the current transportation cycle based on the reduced number of target planned tasks.
4. The method according to claim 1, characterized in that: The determining of the target planned task from the planned task group according to the task matching rule, and the determining of the target temporary task from the temporary task group, includes: Classifying the tasks in the planned task group according to the destination, origin, planned departure shift, and shift type of the tasks in the planned task group to obtain a classified planned task group; Selecting a preset task from the classified planned task group as the target planned task; Classifying the tasks in the temporary task group according to the destination, origin, planned departure shift, and shift type of the tasks in the temporary task group to obtain a classified temporary task group; A task corresponding to the target planned task category is selected from the classified temporary task group as the target temporary task.
5. The method according to claim 1, characterized in that: When the target planned task is a qualified task, before determining whether the execution days of the target temporary task are greater than an execution days threshold, the method further includes: Determine the target days corresponding to the target temporary task according to the shift type of the target temporary task and the historical days corresponding to the historical task group; The execution days threshold is determined according to the target days and the temporary task execution rate threshold.
6. The method according to claim 1, characterized in that After adjusting the planned tasks of the current transportation cycle according to the number of solidified tasks, the method further includes: Obtaining the adjusted execution cost of the planned tasks of the current transportation cycle and the execution cost of the tasks in the historical task group; Determining whether the execution cost of the planned task of the current transportation cycle is lower than the execution cost of the tasks in the historical task group; If it is lower than that, the adjusted planned task of the current transportation cycle is sent to the terminal; If it is not lower than, sending the adjusted task number interval value of the planned task of the current transportation cycle to the terminal, the interval value is determined according to the standard deviation of the difference between the fixed task number and the task number of the target temporary task.
7. A task adjustment device, characterized in that: include: A first acquisition unit is used to acquire a historical task group of a previous transportation cycle of a transfer yard branch line, wherein the historical task group includes a planned task group and a temporary task group; A first determining unit, configured to determine a target planned task from the planned task group according to a task matching rule, and to determine a target temporary task corresponding to the target planned task from the temporary task group; The second determination unit is used to determine whether the execution days of the target temporary task are greater than the execution days threshold, and whether the loading rate of the target temporary task is greater than the temporary task loading rate threshold when the target planned task is a qualified task; the historical task group of the previous transportation cycle is the task group corresponding to the previous month of the transfer yard branch line, and the shift type corresponding to the target planned task and the target temporary task is week n, where n includes one or more integers from 1 to 7; The first adjustment unit is used to obtain the difference between the total number of task executions and the planned number of tasks for each week n in the previous month when the execution days of the target temporary task are greater than the execution days threshold and the loading rate of the target temporary task is greater than the temporary task loading rate threshold, to obtain the number of tasks of the target temporary task; obtain the average value of the difference for week n according to the number of tasks of the target temporary task; determine the average value of the difference as the number of solidified tasks for week n; and adjust the planned tasks of the current transportation cycle according to the number of solidified tasks.
8. A server, characterized in that: The method comprises a processor and a memory, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the method for adjusting the task as claimed in any one of claims 1 to 6 is executed.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the method for adjusting the task according to any one of claims 1 to 6.
Citation Information
Patent Citations
Method and device for processing logistics information
CN102142107A
Cloud-based smart logistics calculation method
CN108346025A
