Inspection task allocation method, device, equipment, and storage medium based on multi-tenancy

Abstract

The present invention proposes a multi-tenant based inspection task allocation method, device, equipment, and storage medium. The method includes: after a registered tenant constructs a preset inspection task, a target date is determined based on the current date and a preset number of redundant days; when the target date is associated with a target inspection line and determined as a target inspection account and a candidate inspection task, at least one target inspection task is allocated to each target inspection account; when at least one candidate inspection task is not allocated, a first exception notification is pushed to the corresponding registered tenant and the target date is locked; when each candidate inspection task is allocated, tasks are allocated based on the corresponding task inspection duration and the remaining duration of each target inspection account. The target date can be determined in advance. When the number of inspection accounts of the target inspection line is less than the inspection tasks, the target inspection tasks are allocated in advance through the SaaS system, thereby eliminating information isolation of registered tenants, avoiding task conflicts, and improving the efficiency of inspection task allocation.

Description

Technical Field

[0001] The present invention relates to the field of intelligent inspection technology, and in particular to a multi-tenant-based inspection task allocation method, device, equipment, and storage medium. Background Art

[0002] SaaS (Software as a Service) is a service model that delivers software applications over the internet. It can provide the same software application to multiple tenants, eliminating the need for local software installation and maintenance. Tenants in a SaaS system are software users. In the property management field, each residential complex or office building's property management team acts as a tenant of the SaaS system. Using the SaaS system to manage property online effectively improves property management efficiency.

[0003] Smart inspection is a commonly used function in property management. Each tenant can configure inspection points in the SaaS system according to their own needs and build an inspection plan based on the inspection points. The system will automatically assign inspection tasks to inspectors according to the time set in the inspection plan. After completing the inspection, the inspectors will upload the relevant inspection records to the SaaS system, allowing back-end personnel to conduct online summary management and control, thereby improving the efficiency of inspections.

[0004] However, in order to save labor costs, multiple properties under the same developer may share some highly professional inspection personnel. For example, multiple geographically close communities share an equipment maintenance team. In the SaaS system, the inspection tasks constructed by each tenant are isolated from each other. This makes it easy for different tenants to configure different inspection tasks for the same group of inspection personnel at the same time node, resulting in conflicts in the inspection tasks of different tenants, affecting the efficiency and reliability of smart inspections. Summary of the Invention

[0005] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the present invention proposes a multi-tenant inspection task allocation method, apparatus, device, and storage medium, which can realize the intelligent allocation of inspection personnel, reduce the risk of conflict between inspection tasks of different tenants, and improve the efficiency of intelligent inspection.

[0006] In a first aspect, an embodiment of the present invention provides a multi-tenant based inspection task allocation method, which is applied to a SaaS system, wherein the SaaS system includes multiple registered tenants, and the SaaS system is pre-set with multiple preset inspection lines, each of which is associated with at least one preset inspection account. The multi-tenant based inspection task allocation method includes:

[0007] Obtaining a preset inspection task constructed by any of the registered tenants, wherein the preset inspection task includes a preset inspection date, a task inspection point, and a task inspection line;

[0008] Determine a target date based on the current date and a preset number of redundant days; when the target date is associated with a target inspection line, determine the preset inspection account corresponding to the target inspection line as the target inspection account; and determine the plurality of preset inspection tasks associated with the target inspection line as candidate inspection tasks, wherein the target inspection line is the task inspection line for which the number of candidate inspection tasks is greater than the number of target inspection accounts;

[0009] Determine the task inspection duration of the candidate inspection tasks based on the task inspection points, and assign at least one target inspection task to each target inspection account, wherein the sum of the task inspection durations of the target inspection tasks is less than or equal to the preset working time;

[0010] When at least one of the candidate inspection tasks is not assigned, a first exception notification is pushed to the registered tenant corresponding to the unassigned candidate inspection task, and the target inspection line is locked as unassignable on the target date;

[0011] When each of the candidate inspection tasks is assigned, the remaining time of each of the target inspection accounts is determined based on the sum of the working time and the task inspection time. When any of the registered tenants constructs a new preset inspection task based on the target date, task assignment is performed based on the corresponding task inspection time and the remaining time of each of the target inspection accounts.

[0012] According to some embodiments of the present invention, allocating at least one target inspection task to each target inspection account includes:

[0013] Building a target task queue based on the construction order of the plurality of candidate inspection tasks;

[0014] Allocate a target inspection task to each target inspection account based on the target task queue, and determine the remaining time of the target inspection account based on the task inspection time of the allocated target inspection task;

[0015] Determine the next unassigned candidate inspection task in the target task queue as the inspection task to be assigned, determine the inspection duration of the inspection task to be assigned as the target duration, and assign the inspection task to be assigned to any target inspection account that meets a preset condition, wherein the preset condition is that the corresponding remaining duration is greater than or equal to the target duration;

[0016] Update the remaining time of the target inspection account assigned the inspection task to be assigned, determine the next inspection task to be assigned from the target task queue, and assign it to any target inspection account based on the corresponding target time and the preset conditions until the target task queue is cleared, or there is no target inspection account that meets the preset conditions.

[0017] According to some embodiments of the present invention, the preset inspection task further includes task location information. Before assigning the inspection task to be assigned to any target inspection account that meets the preset conditions, the method further includes:

[0018] Determine the task location information of the last target inspection task to which each target inspection account is assigned as the starting location information, and determine the task location information of the inspection task to be assigned as the end location information;

[0019] determining a commuting duration based on the starting point location information and the ending point location information;

[0020] The target duration is extended based on the commute duration.

[0021] According to some embodiments of the present invention, allocating the inspection task to be allocated to any target inspection account that meets preset conditions includes:

[0022] Determine the number of tasks for each target inspection account;

[0023] Determine the target inspection account that meets the preset conditions as a candidate inspection account;

[0024] Based on the candidate inspection account, a first weight is determined according to the number of tasks and a preset first weight, and a second weight is determined based on the target duration and a preset second weight, wherein the first weight is greater than the second weight;

[0025] Allocate the inspection task to be assigned to the candidate inspection account with the smallest sum of the first weight and the second weight.

[0026] According to some embodiments of the present invention, after pushing a first exception notification to the registered tenant corresponding to the unassigned candidate inspection task and locking the target inspection line as unassignable on the target date, the method further includes:

[0027] When the registered tenant re-edits the inspection date of the candidate inspection task in response to the first exception notification, removing the re-edited candidate inspection task from the target task queue;

[0028] Determine each of the candidate inspection tasks remaining in the target task queue as an unassigned inspection task;

[0029] Pushing each of the unassigned inspection tasks to each of the target inspection accounts, and allocating at least one additional inspection task selected from the unassigned inspection tasks to any of the target inspection accounts;

[0030] Alternatively, when a new target inspection account is detected to be added to the target inspection line, at least one unassigned inspection task is assigned to the new target inspection account, and the target date is unlocked if the new target inspection account meets the preset condition.

[0031] According to some embodiments of the present invention, obtaining a preset inspection task constructed by any registered tenant includes:

[0032] Constructing a task configuration interface, wherein the task configuration interface includes date options, point configuration items, line options, and a task description column;

[0033] Determine any of the registered tenants who initiates the task construction request as a target tenant, and push the task configuration interface to the target tenant;

[0034] Obtain the target inspection point selected by the target tenant based on the point configuration item, the task inspection line selected based on the line option, the inspection date input based on the date option, and the task description information input based on the task description field;

[0035] Determining the task location information based on a preset tenant location of the target tenant;

[0036] The preset inspection task is constructed based on the target inspection point, the task inspection line, the inspection date, the task description information and the task location information.

[0037] According to some embodiments of the present invention, when any of the registered tenants creates a new preset inspection task based on the target date, the task is allocated based on the corresponding inspection duration of the task and the remaining duration of each target inspection account, including:

[0038] When the target tenant selects any of the target inspection lines based on the line options, the target date in the locked state is masked in the date option;

[0039] When the selected inspection date is before the target date, the remaining time of each corresponding target inspection account is obtained; when the target inspection point is obtained based on the point configuration item, the task inspection time of the target inspection point is calculated;

[0040] When the inspection duration of the task is greater than each of the remaining durations, a second exception notification is pushed to the target tenant, wherein the second exception notification is used to indicate that the preset inspection task cannot be constructed;

[0041] When the inspection duration of the task is less than or equal to any of the remaining durations, the preset inspection task is constructed and allocated to any of the target inspection accounts that meet the preset conditions.

[0042] In the second aspect, an embodiment of the present invention provides a multi-tenant-based inspection task allocation device, comprising at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor so that the at least one control processor can execute the multi-tenant-based inspection task allocation method described in the first aspect above.

[0043] In a third aspect, an embodiment of the present invention provides an electronic device, comprising the multi-tenant-based inspection task allocation device as described in the second aspect above.

[0044] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the multi-tenant-based inspection task allocation method as described in the first aspect above.

[0045] The inspection task allocation method based on multiple tenants according to an embodiment of the present invention has at least the following beneficial effects: obtaining a preset inspection task constructed by any registered tenant, wherein the preset inspection task includes a preset inspection date, a task inspection point and a task inspection line; determining a target date based on the current date and a preset number of redundant days, and when the target date is associated with a target inspection line, determining the preset inspection account corresponding to the target inspection line as the target inspection account, and determining multiple preset inspection tasks associated with the target inspection line as candidate inspection tasks, wherein the target inspection line is a task inspection line whose number of candidate inspection tasks is greater than the number of target inspection accounts; determining candidate inspection lines based on task inspection points The task inspection duration of the task, at least one target inspection task is assigned to each target inspection account, wherein the sum of the task inspection durations of the target inspection tasks is less than or equal to the preset working hours; when at least one candidate inspection task is not assigned, a first exception notification is pushed to the registered tenant corresponding to the unassigned candidate inspection task, and the target inspection line is locked as unassignable on the target date; when each candidate inspection task is assigned, the remaining duration of each target inspection account is determined based on the sum of the working hours and the task inspection duration. When any registered tenant constructs a new preset inspection task based on the target date, the task is assigned based on the corresponding task inspection duration and the remaining duration of each target inspection account. According to the technical solution of the embodiment of the present invention, after the registered tenant constructs the preset inspection task, the target date can be determined in advance every day based on the number of redundant days. If there is a target inspection line with fewer inspection accounts than inspection tasks on the target date, the target inspection task is assigned to each target inspection account through the SaaS system, eliminating the information isolation when the registered tenant constructs the inspection task, avoiding task conflicts, and improving the efficiency of inspection task allocation. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 This is a flowchart of a multi-tenant based inspection task allocation method provided by one embodiment of the present invention;

[0047] Figure 2 This is a schematic diagram of a task list of a target inspection account provided by another embodiment of the present invention;

[0048] Figure 3 is a schematic diagram of a target inspection task provided by another embodiment of the present invention;

[0049] Figure 4 is a schematic diagram of a task configuration interface provided by another embodiment of the present invention;

[0050] Figure 5 This is a complete flow chart of a multi-tenant based inspection task allocation method provided by another embodiment of the present invention;

[0051] Figure 6It is a structural diagram of a multi-tenant based inspection task allocation device provided by another embodiment of the present invention. DETAILED DESCRIPTION

[0052] The following describes embodiments of the present invention in detail. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended only to explain the present invention and are not to be construed as limiting the present invention.

[0053] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, they cannot be understood as limitations on the present invention.

[0054] In the description of the present invention, "several" means one or more, "many" means more than two, "greater than," "less than," and "exceed" are understood to exclude the number itself, while "above," "below," and "within" are understood to include the number itself. The use of "first" and "second" in the description is solely for the purpose of distinguishing technical features and should not be construed as indicating or implying relative importance, implicitly specifying the number of the indicated technical features, or implicitly specifying the order of the indicated technical features.

[0055] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, and connecting should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention based on the specific content of the technical solution.

[0056] The embodiment of the present invention provides a method, apparatus, device and storage medium for allocating inspection tasks based on multiple tenants, wherein the method for allocating inspection tasks based on multiple tenants includes: obtaining a preset inspection task constructed by any registered tenant, wherein the preset inspection task includes a preset inspection date, a task inspection point and a task inspection line; determining a target date based on the current date and a preset number of redundant days, and when the target date is associated with a target inspection line, determining a preset inspection account corresponding to the target inspection line as the target inspection account, and determining multiple preset inspection tasks associated with the target inspection line as candidate inspection tasks, wherein the target inspection line is a task inspection line whose number of candidate inspection tasks is greater than the number of target inspection accounts; determining a target inspection line based on any The inspection point determines the inspection time of the candidate inspection task, and allocates at least one target inspection task to each target inspection account, wherein the sum of the inspection time of the target inspection tasks is less than or equal to the preset working time; when at least one candidate inspection task is not allocated, a first exception notification is pushed to the registered tenant corresponding to the unassigned candidate inspection task, and the target inspection line is locked as unassignable on the target date; when each candidate inspection task is allocated, the remaining time of each target inspection account is determined based on the sum of the working time and the inspection time of the task, and when any registered tenant builds a new preset inspection task based on the target date, the task is allocated based on the corresponding task inspection time and the remaining time of each target inspection account. According to the technical solution of the embodiment of the present invention, after the registered tenant builds the preset inspection task, the target date can be determined in advance every day according to the number of redundant days. If there is an inspection account on the target date that is less than the target inspection line of the inspection task, the target inspection task is allocated to each target inspection account through the SaaS system, eliminating the information isolation when the registered tenant builds the inspection task, avoiding task conflicts, and improving the allocation efficiency of the inspection task.

[0057] The technical solutions of the embodiments of the present invention are further described below based on the accompanying drawings.

[0058] Reference Figure 1 , Figure 1 A flowchart of a multi-tenant based inspection task allocation method provided in an embodiment of the present invention is provided. The multi-tenant based inspection task allocation method is applied to a SaaS system. The SaaS system includes multiple registered tenants. The SaaS system is pre-set with multiple preset inspection lines. Each preset inspection line is associated with at least one preset inspection account. The method includes but is not limited to the following steps:

[0059] S10, obtaining a preset inspection task created by any registered tenant, wherein the preset inspection task includes a preset inspection date, a task inspection point, and a task inspection line;

[0060] S20, determining a target date based on the current date and a preset number of redundant days; if the target date is associated with a target inspection line, determining a preset inspection account corresponding to the target inspection line as the target inspection account; and determining multiple preset inspection tasks associated with the target inspection line as candidate inspection tasks, wherein the target inspection line is a task inspection line for which the number of candidate inspection tasks is greater than the number of target inspection accounts;

[0061] S30, determining the task inspection duration of the candidate inspection tasks based on the task inspection points, and assigning at least one target inspection task to each target inspection account, wherein the sum of the task inspection durations of the target inspection tasks is less than or equal to the preset working hours;

[0062] S40: When at least one candidate inspection task is not assigned, a first exception notification is pushed to the registered tenant corresponding to the unassigned candidate inspection task, locking the target inspection line as unassignable on the target date;

[0063] S50, when each candidate inspection task is assigned, the remaining time of each target inspection account is determined based on the sum of the working time and the task inspection time. When any registered tenant builds a new preset inspection task based on the target date, the task is assigned based on the corresponding task inspection time and the remaining time of each target inspection account.

[0064] In actual applications, each registered tenant in the SaaS system can be a different property management team, such as the property management team of a different community or office building. Each registered tenant can log in to the SaaS system and enter the visual construction interface of the inspection task. In the visual construction interface, relevant information is input to build a preset inspection task, such as entering the inspection date, task inspection points, and specifying the task inspection line.

[0065] It should be noted that task inspection points can be locations customized by registered tenants, such as the lobby, elevators, and power equipment. Task inspection lines are job lines in property management, and each task inspection line includes multiple property management personnel. In this embodiment, preset inspection lines are pre-configured based on the structure of the property management team. Each property management personnel is assigned a preset inspection account, so each preset inspection line includes multiple preset inspection accounts.

[0066] It should be noted that in the field of property management, inspections typically include established operations such as equipment inspections and photo recording. Therefore, although task inspection points can be customized, the inspection duration for each inspection point can be pre-set. After the registered tenant enters the task inspection point in the visual construction interface, the corresponding inspection duration can be searched through a simple semantic matching method to determine the task inspection duration. For example, if the inspection duration for electrical equipment inspection is preset to 20 minutes and the inspection duration for elevators is preset to 2 hours, when the task inspection point entered is the resident elevator, the matched inspection duration is 30 minutes. When the task inspection point entered is the meter box, the inspection duration is determined to be 20 minutes for the electrical equipment inspection through simple semantic matching.

[0067] It should be noted that registered tenants can construct preset inspection tasks for future dates at any time, and the preset inspection tasks may be modified accordingly before execution. For example, the registered tenant modifies the inspection date or inspection point. Therefore, every time a preset inspection task is constructed, a task assignment is performed. It is very likely that unnecessary system operations will be caused by task withdrawal or task modification. Therefore, the SaaS system of this embodiment performs task matching once a day, and determines the target date for task matching based on the preset redundant days. This can reduce the probability of the preset inspection task being modified after allocation, and can also leave time for registered tenants to perform compensation operations when an inspection task conflict occurs. The redundant days can be 1 day or 2 days, and this embodiment does not impose any restrictions on this.

[0068] It should be noted that the preset inspection tasks are set with an inspection date. Therefore, after determining the target date, if there is no corresponding preset inspection task for the target date, the assignment will not be executed. If the task inspection account of the task line corresponding to the preset inspection task of the target date can meet the requirements, that is, the number of inspection personnel is greater than or equal to the number of inspection tasks, then there will be no task conflict. Therefore, this embodiment does not improve the above two scenarios. The subsequent default target date has at least one task inspection line with fewer preset inspection accounts than candidate inspection tasks. The target date can include multiple target inspection lines, and the technical solution of this embodiment can be implemented separately for each target inspection line.

[0069] It should be noted that after determining the target inspection line, the corresponding candidate inspection tasks are reverse matched through the target inspection line, and the task inspection duration of each candidate inspection task is calculated according to the method of the above embodiment. At least one target inspection task is assigned to each target inspection account based on the task inspection duration, and it is ensured that the sum of the task inspection durations is less than the working hours. The allocation strategy can be to evenly distribute the candidate inspection tasks according to the construction order, give priority to the tasks that were constructed first, or allocate them according to the remaining allocable time, to ensure that each inspection personnel has sufficient working hours to perform the relevant inspections.

[0070] For example, taking 8 hours as an example, the target inspection line is the elevator maintenance line, which is shared by multiple registered tenants. The overall elevator inspection time is 2 hours, the car inspection time is 30 minutes, and the machine room inspection time is 1 hour. All of the above target inspection tasks can be undertaken by the elevator maintenance line. Therefore, corresponding target inspection tasks can be assigned to each target inspection account to ensure that the sum of the inspection times of the target inspection tasks assigned to each target inspection account is less than 8.

[0071] It should be noted that, according to the description of the above embodiment, working hours are a restriction condition for task allocation. When the sum of the task inspection hours of the target inspection account reaches the working hours, the target inspection account can no longer be assigned a task. When at least one candidate inspection task has not been assigned, that is, the sum of the task inspection hours of each target inspection account is less than or equal to the working hours, but the sum of the task inspection hours of any candidate inspection task is greater than the working hours, then task allocation cannot continue. A first exception notification is pushed to the corresponding registered tenant, reminding the corresponding registered tenant to modify the inspection date of the candidate inspection task. The content of the first exception notification is not limited here.

[0072] It should be noted that the task allocation in this embodiment is done in advance, and the preset inspection task can be constructed at any time. For example, the current date is January 1, the redundant days are 3 days, and the target date is January 4. The registered tenant can still construct the preset inspection task to be executed on January 4 at any time before January 4. When the first abnormality notification is pushed according to the method of the above embodiment, it can be determined on the current date that the target inspection line can no longer undertake new tasks on the target date. Therefore, the target date is locked on the current date. For example, the task construction of the elevator inspection line on January 4 is locked on January 1, and the registered tenant cannot construct the preset inspection task of the elevator inspection line on January 4, thereby avoiding task conflicts from the task construction level.

[0073] It should be noted that when each candidate inspection task is assigned, the target inspection account may still be able to undertake more preset inspection tasks. This embodiment determines the remaining time of each target inspection account based on the sum of the working time and the task inspection time. For example, the above working time is 8 hours, and the target inspection account A is assigned an overall elevator inspection and a machine room inspection. The sum of the task inspection time is 3 hours, and the remaining time is 5 hours.

[0074] It should be noted that the task allocation in this embodiment has an advance amount. Therefore, when all the candidate inspection tasks for the current date have been allocated, when any registered tenant builds a new preset inspection task based on the target date again, the task can be allocated based on the remaining time on the next date. The already allocated target inspection task has locked part of the working time of the target inspection account, and it can be reallocated according to the method of the above embodiment within the limit of the remaining time.

[0075] For example, according to the description of the above embodiment, the current date is January 1. After completing the task allocation, the registered tenant newly constructs a preset inspection task for January 4. The preset inspection task can be allocated in real time based on the remaining time, and the scenario of early allocation of redundant days can still be met. Of course, the target date can also be determined to be after January 5 on January 2, and the preset inspection tasks that were not allocated before January 5 can be allocated on the corresponding inspection date, which improves the flexibility of task construction and meets the principle of first build first allocate at the same time. It can also ensure that the newly constructed task will not cause the sum of the inspection time of the target inspection account to exceed the working time.

[0076] In addition, in one embodiment, referring to Figure 5 In step S30, at least one target inspection task is assigned to each target inspection account, including but not limited to the following steps:

[0077] S31, building a target task queue based on the construction order of multiple candidate inspection tasks;

[0078] S32, assigning a target inspection task to each target inspection account based on the target task queue, and determining the remaining time of the target inspection account based on the task inspection time of the assigned target inspection task;

[0079] S33, determining the next unassigned candidate inspection task in the target task queue as the inspection task to be assigned, determining the inspection duration of the inspection task to be assigned as the target duration, and assigning the inspection task to any target inspection account that meets a preset condition, wherein the preset condition is that the corresponding remaining duration is greater than or equal to the target duration;

[0080] S34, updates the remaining duration of the target inspection account assigned the inspection task to be assigned, determines the next inspection task to be assigned from the target task queue, and assigns it to any target inspection account based on the corresponding target duration and preset conditions until the target task queue is cleared, or there is no target inspection account that meets the preset conditions.

[0081] It should be noted that after the candidate inspection tasks are determined, a target task queue is constructed according to the construction order, and the storage characteristics of the queue are used to ensure that the candidate inspection tasks are allocated according to the construction order.

[0082] It should be noted that when each target inspection account has not been assigned a task, it can at least undertake any target inspection task. This embodiment first assigns a target inspection task to each target inspection account, and after the assignment is completed, the real-time remaining time is determined based on the task inspection time.

[0083] For example, continuing to refer to the example of the above-mentioned elevator maintenance line, the overall elevator inspection time is 2 hours, the car inspection time is 30 minutes, the machine room inspection time is 1 hour, the number of target inspection accounts is 3, and the number of candidate inspection tasks is 5, which are elevator overall inspection, elevator overall inspection, car inspection, machine room inspection and elevator overall inspection respectively. The three target inspection accounts are respectively assigned elevator overall inspection, elevator overall inspection and car inspection in order, and the remaining time is 6 hours, 6 hours and 7.5 hours respectively.

[0084] It should be noted that after completing the first task allocation, the second task allocation may result in the sum of the task inspection time reaching the working time. Therefore, after the first task allocation, each candidate inspection task is determined as the inspection task to be assigned in turn, and is assigned one by one. The allocation operation is cyclical until the target task queue is cleared or the target inspection account is fully allocated.

[0085] It should be noted that in an allocation operation, the inspection duration of the inspection task to be assigned is first determined as the target duration. Based on the target duration, the remaining duration of the target inspection account is traversed, and the target inspection account that meets the preset conditions is determined as the assignable target inspection account, and the allocation can be performed arbitrarily.

[0086] For example, in the above example, the next inspection task to be assigned is a computer room inspection, with a target duration of 1 hour. All target inspection accounts meet the requirements, so any one can be assigned. If the remaining durations are 0.5 hours, 1 hour, and 1 hour, respectively, the target inspection account with the remaining duration of 0.5 hours will not be assigned. The above strategy is used to assign each candidate inspection task in the target task queue.

[0087] It should be noted that each target inspection account can view the assigned inspection tasks on the mobile terminal, such as Figure 2 As shown, the target inspection account B of inspection line A can view inspection tasks A, B and C after logging in. Inspection tasks A and B are executed on the same day, and the corresponding inspection points are different. Inspection tasks B and C are inspection tasks for the same inspection point on different dates, such as regular inspection tasks. Inspection personnel can click on each inspection task to enter the details page for viewing. This embodiment does not limit the description of task details.

[0088] In addition, in one embodiment, the preset inspection task also includes task location information, refer to Figure 5 In step S33, before allocating the inspection task to be assigned to any target inspection account that meets the preset conditions, the method further includes but is not limited to the following steps:

[0089] S331, determining the task location information of the last executed target inspection task assigned to each target inspection account as the starting location information, and determining the task location information of the inspection task to be assigned as the end location information;

[0090] S332, determining the commuting time based on the starting point location information and the ending point location information;

[0091] S333, extend the target duration based on the commuting duration.

[0092] It should be noted that the scenario of this embodiment is that multiple registered tenants share a preset inspection line, so the inspection personnel may be involved in performing inspections from one cell to another. The task location information can be entered when constructing the preset inspection task, or the default address of the registered tenant can be used. No further restrictions are made here.

[0093] It should be noted that after the target inspection account is assigned to the target inspection task for the first time, the starting location information is determined according to the corresponding task location, and the task location information of the next assigned inspection task to be assigned is determined as the end location information, thereby determining the commuting time between the two tasks, and extending the target time by the commuting time. The target time is then used to represent the time required from the completion of the previous task to the completion of the next task. The remaining time is traversed and matched based on the updated target time, which can ensure that the inspection personnel can complete all inspection tasks within the working hours.

[0094] It should be noted that different target inspection tasks can be assigned to the same location. For example, in the elevator maintenance line mentioned above, the same community can have both an elevator car inspection and a machine room inspection configured on the same day. Since they are in the same community, the starting and ending location information overlap, and the commute time is zero. Therefore, the inspection task can be prioritized to the target inspection account with a commute time of zero. After determining the commute time of each target inspection account for the inspection task, the target inspection account with the shortest commute time can also be assigned to improve work efficiency.

[0095] It should be noted that after updating the target duration based on the commuting duration and completing the task assignment, the target inspection account can display the commuting duration of the remaining inspection tasks after clicking on each inspection task, such as Figure 3 As shown, continue to refer to the inspection tasks A, B and C in the above example. Figure 2After clicking on inspection task A in the interface shown, it can be displayed on the terminal that it takes 20 minutes to commute from the location of inspection task A to inspection task B, and it takes 30 minutes to commute from the location of inspection task B to inspection task C, thereby improving visualization.

[0096] In addition, in one embodiment, referring to Figure 5 In step S33, the inspection task to be assigned is assigned to any target inspection account that meets the preset conditions, including but not limited to the following steps:

[0097] S334, determining the number of tasks for each target inspection account;

[0098] S335, determining the target inspection account that meets the preset conditions as a candidate inspection account;

[0099] S336, based on the candidate inspection account, determining a first weight according to the number of tasks and a preset first weight, and determining a second weight according to the target duration and a preset second weight, wherein the first weight is greater than the second weight;

[0100] S337 , allocating the inspection task to be assigned to the candidate inspection account with the smallest sum of the first weight and the second weight.

[0101] It should be noted that, when allocating inspection tasks to be allocated, this embodiment comprehensively considers the number of tasks and the inspection duration of the target inspection account to improve the rationality of task allocation.

[0102] It's important to note that the first weight is greater than the second weight. That is, the weight of the number of tasks is greater than the weight of the target duration. This ensures that each target inspection account has the same number of tasks as much as possible, preventing random assignment that could result in some target inspection accounts receiving significantly more tasks than others, thereby improving the utilization of inspection human resources. The values ​​of the first and second weights can be set based on actual needs, for example, a first weight of 3 and a second weight of 1.

[0103] It should be noted that after calculating the first weight based on the number of tasks and the first weight, and calculating the second weight based on the target duration and the second weight, the minimum sum of the first weight and the second weight can represent that the corresponding candidate inspection account has the strongest task acceptance capacity. Assigning the inspection tasks to be assigned to the corresponding candidate inspection tasks can improve the rationality of task allocation.

[0104] For example, taking three candidate inspection accounts as an example, the number of tasks are 3, 2 and 2 respectively. The target durations updated according to the commuting time are 3 hours, 2.5 hours and 2 hours respectively. Taking the first weight of 3 and the second weight of 1 as an example, the calculated first weights are 9, 6 and 6 respectively, and the second weights are 3, 2.5 and 2 respectively. The sum of the first weight and the second weight is 12, 8.5 and 8 respectively. The inspection task to be assigned is assigned to the third candidate inspection account.

[0105] In addition, in one embodiment, referring to Figure 5 In step S40, after pushing a first exception notification to the registered tenants corresponding to the unassigned candidate inspection tasks and locking the target inspection line as unassignable on the target date, the method further includes:

[0106] S41, when the registered tenant re-edits the inspection date of the candidate inspection task in response to the first exception notification, the re-edited candidate inspection task is removed from the target task queue;

[0107] S42, determining each remaining candidate inspection task in the target task queue as an unassigned inspection task;

[0108] S43, pushing each unassigned inspection task to each target inspection account, and assigning at least one additional inspection task selected from the unassigned inspection tasks to any target inspection account;

[0109] S44, when it is detected that a new target inspection account is added to the target inspection line, at least one unassigned inspection task is assigned to the new target inspection account, and the target date is unlocked if the new target inspection account meets the preset conditions.

[0110] It should be noted that according to the description of the above embodiment, when the first abnormal notification is obtained, the candidate inspection task cannot be assigned. The registered tenant can re-edit the inspection date and block the target date in the date options. Currently, if the date before the target date is locked according to the technical solution of this embodiment, it is also blocked, that is, only available dates are displayed in the date selection.

[0111] For example, according to the above example, the target date is January 4th. After being locked, January 4th cannot be selected. If January 3rd is also locked according to the same technical solution on the previous day, even if the current date is January 1st, January 3rd cannot be selected as the new inspection date, and so on.

[0112] It should be noted that the task inspection duration is determined according to the reference duration of the task inspection point set by the system. In actual application, it is likely to take shorter time than the task inspection duration. For example, the above-mentioned computer room inspection duration is 1 hour, and more experienced inspectors may complete it within half an hour. Therefore, this embodiment can also push each unassigned inspection task to each target inspection account of the target inspection line. The inspectors corresponding to the target inspection account can judge whether they can continue to undertake the task after the task assigned by the system based on experience. If the target inspection account selects any additional inspection task, the additional inspection task will be assigned to the corresponding target inspection account, thereby improving the flexibility of task allocation, allowing more candidate inspection tasks to be assigned, and improving the utilization rate of human resources.

[0113] It should be noted that during the peak time period of inspection tasks, it is also possible to add personnel to the target inspection line, that is, to add a new target inspection account. When the addition of a target inspection account is detected, according to the preset conditions of the above embodiment, at least one unassigned inspection task will be assigned to the new target inspection account according to the creation order. If the target task queue is cleared, the remaining time of the new target inspection account can still meet any preset inspection task, the target date will be unlocked in the SaaS system, and the registered tenant can further build a new preset inspection task.

[0114] In addition, in one embodiment, referring to Figure 5 Step S10 specifically includes but is not limited to the following steps:

[0115] S11, constructing a task configuration interface, wherein the task configuration interface includes date options, point configuration items, line options, and a task description column;

[0116] S12, determining any registered tenant that initiates the task construction request as the target tenant, and pushing the task configuration interface to the target tenant;

[0117] S13, obtaining the target inspection point selected by the target tenant based on the point configuration item, a task inspection line selected based on the line option, the inspection date input based on the date option, and the task description information input based on the task description field;

[0118] S14, determining task location information based on the preset tenant location of the target tenant;

[0119] S15, constructing a preset inspection task based on the target inspection point, task inspection line, inspection date, task description information and task location information.

[0120] It should be noted that a task configuration interface is pre-set in the SaaS system. After a registered tenant initiates a task construction request to the SaaS system through a mobile phone, computer or other terminal, the SaaS system will identify the registered tenant who initiated the request as the target tenant and push the task configuration interface to the target tenant, thereby enabling multiple registered tenants to share one task configuration interface and ensuring the universality of various types of information.

[0121] For example, the task configuration interface can refer to Figure 4 As shown, in the newly added point options, a point name is set as a point configuration item, an associated line is set as a line option, a start date is set as a date option, and a task description column is set for entering task description information.

[0122] It should be noted that the task configuration interface can also set the inspection frequency. The SaaS system can automatically determine the next trigger time of the preset inspection task based on the inspection frequency. For example Figure 4 As shown in the figure, the start date is January 1st and the inspection frequency is weekly. Then the first target date is January 1st. After completion, the next inspection date is automatically determined to be January 8th, and so on. In this way, cyclic inspection can be implemented after one configuration, without the need to repeatedly configure preset inspection tasks.

[0123] It should be noted that the location of the target tenant is pre-set, such as the address of a community or office building. Therefore, when constructing a preset inspection task, the preset tenant location can be directly obtained in the background as the task location information. I will not go into details here.

[0124] In addition, in one embodiment, referring to Figure 5 Step S50 specifically includes but is not limited to the following steps:

[0125] S51: When the target tenant selects any target inspection line based on the line option, the target date in the locked state is masked in the date option;

[0126] S52, when the selected inspection date is before the target date, obtaining the remaining time of each corresponding target inspection account, and when the target inspection point is obtained based on the point configuration item, calculating the task inspection time of the target inspection point;

[0127] S53: When the inspection duration of the task is greater than the remaining durations, a second exception notification is pushed to the target tenant, where the second exception notification is used to indicate that the preset inspection task cannot be constructed;

[0128] S54: When the inspection duration of the task is less than or equal to any remaining duration, a preset inspection task is constructed and assigned to any target inspection account that meets the preset conditions.

[0129] It should be noted that the target tenant can construct tasks at any time. The technical solution of the above embodiment assigns tasks to each target inspection line and locks the fully assigned target date. The same date is not necessarily locked for different preset inspection lines. Therefore, after selecting the target inspection line, this embodiment blocks the target date in the locked state in the date option.

[0130] It should be noted that after selecting the inspection date, if the inspection date is after the target date determined based on the current date, then the task allocation for the inspection date has not yet been performed. Simply construct a preset inspection task, wait for the target date to rotate to the inspection date, and then execute the allocation scheme of this embodiment. If the inspection date is before the target date, then the inspection date has already been assigned a task. Each target inspection account is assigned at least one inspection task, and the previously constructed task has already been assigned. In this case, each target tenant constructs a preset inspection task and performs a real-time allocation. This can avoid task conflicts and eliminate the need to re-assign tasks, wasting system resources. In this case, the remaining time of each target inspection account is obtained and allocated according to the preset conditions of the above embodiment.

[0131] It should be noted that the inspection date is not locked, which does not mean that the target inspection account can be assigned any inspection task. For example, in the example of the elevator maintenance line mentioned above, the inspection time of the whole machine is 2 hours, and the inspection time of the machine room is 1 hour. If the remaining time of each target inspection account is greater than 1 hour but less than 2 hours, since at least the machine room inspection task can be assigned, the corresponding date will not be locked. In this case, the task inspection time may be greater than the total remaining time. At this time, a second abnormal notification is pushed to the target tenant to indicate that the preset inspection task cannot be constructed and the inspection date needs to be further updated. After the inspection date is updated, the judgment process of this embodiment can be repeated. When the task inspection time is less than or equal to any remaining time, the preset inspection task can be constructed and the task can be directly assigned. It will not be repeated here.

[0132] like Figure 6 As shown, Figure 6 This is a structural diagram of a multi-tenant inspection task allocation device provided by an embodiment of the present invention. The present invention also provides a multi-tenant inspection task allocation device, including:

[0133] The processor 601 may be implemented as a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is configured to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0134] The memory 602 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 602 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program codes are stored in the memory 602 and are called by the processor 601 to execute the multi-tenant inspection task allocation method of the embodiments of this application.

[0135] Input / output interface 603, used to implement information input and output;

[0136] Communication interface 604, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, Wi-Fi, Bluetooth, etc.);

[0137] Bus 605 , which transmits information between various components of the device (e.g., processor 601 , memory 602 , input / output interface 603 , and communication interface 604 );

[0138] The processor 601 , the memory 602 , the input / output interface 603 and the communication interface 604 are connected to each other in communication within the device via a bus 605 .

[0139] An embodiment of the present application also provides an electronic device, including the multi-tenant-based inspection task allocation device as described above.

[0140] An embodiment of the present application also provides a storage medium, which is a computer-readable storage medium. The storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned multi-tenant-based inspection task allocation method is implemented.

[0141] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory optionally includes a memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of the above-mentioned networks include but are not limited to the Internet, an intranet, a local area network, a mobile communication network and a combination thereof. The device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and are located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0142] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0143] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above implementation. Those skilled in the art can also make various equivalent modifications or substitutions under the shared conditions that do not violate the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A multi-tenant inspection task allocation method, characterized in that: Applied to a SaaS system, the SaaS system includes multiple registered tenants, the SaaS system is pre-set with multiple preset inspection lines, each of the preset inspection lines is associated with at least one preset inspection account, and the multi-tenant-based inspection task allocation method includes: Obtaining a preset inspection task constructed by any of the registered tenants, wherein the preset inspection task includes a preset inspection date, a task inspection point, and a task inspection line; Determine a target date based on the current date and a preset number of redundant days; when the target date is associated with a target inspection line, determine the preset inspection account corresponding to the target inspection line as the target inspection account; and determine the plurality of preset inspection tasks associated with the target inspection line as candidate inspection tasks, wherein the target inspection line is the task inspection line for which the number of candidate inspection tasks is greater than the number of target inspection accounts; Determine the task inspection duration of the candidate inspection task based on the task inspection point, and assign at least one target inspection task to each target inspection account, wherein, based on any target inspection account, the sum of the task inspection durations of all the target inspection tasks is less than or equal to the preset working duration; When at least one of the candidate inspection tasks is not assigned, a first exception notification is pushed to the registered tenant corresponding to the unassigned candidate inspection task, and the target inspection line is locked as unassignable on the target date; When each of the candidate inspection tasks is assigned, the remaining time of each of the target inspection accounts is determined based on the sum of the working time and the task inspection time. When any of the registered tenants constructs a new preset inspection task based on the target date, task assignment is performed based on the corresponding task inspection time and the remaining time of each of the target inspection accounts.

2. The inspection task allocation method based on multi-tenancy according to claim 1 is characterized in that: Allocating at least one target inspection task to each target inspection account includes: Building a target task queue based on the construction order of the plurality of candidate inspection tasks; Allocate one target inspection task to each target inspection account based on the target task queue, and determine the remaining time of the target inspection account based on the task inspection time of the allocated target inspection task; Determine the next unassigned candidate inspection task in the target task queue as the inspection task to be assigned, determine the inspection duration of the inspection task to be assigned as the target duration, and assign the inspection task to be assigned to any target inspection account that meets a preset condition, wherein the preset condition is that the corresponding remaining duration is greater than or equal to the target duration; Update the remaining time of the target inspection account assigned the inspection task to be assigned, determine the next inspection task to be assigned from the target task queue, and assign it to any target inspection account based on the corresponding target time and the preset conditions until the target task queue is cleared, or there is no target inspection account that meets the preset conditions.

3. The inspection task allocation method based on multi-tenancy according to claim 2 is characterized in that: The preset inspection task also includes task location information. Before allocating the inspection task to be assigned to any target inspection account that meets the preset conditions, the method further includes: Determine the task location information of the last target inspection task to which each target inspection account is assigned as the starting location information, and determine the task location information of the inspection task to be assigned as the end location information; determining a commuting duration based on the starting point location information and the ending point location information; The target duration is extended based on the commute duration.

4. The inspection task allocation method based on multi-tenancy according to claim 3 is characterized in that: Allocating the inspection task to be assigned to any target inspection account that meets preset conditions includes: Determine the number of tasks for each target inspection account; Determine the target inspection account that meets the preset conditions as a candidate inspection account; Based on the candidate inspection account, a first weight is determined according to the number of tasks and a preset first weight, and a second weight is determined based on the target duration and a preset second weight, wherein the first weight is greater than the second weight; Allocate the inspection task to be assigned to the candidate inspection account with the smallest sum of the first weight and the second weight.

5. The inspection task allocation method based on multi-tenancy according to claim 2 is characterized in that: After pushing a first exception notification to the registered tenant corresponding to the unassigned candidate inspection task and locking the target inspection line as unassignable on the target date, the method further includes: When the registered tenant re-edits the inspection date of the candidate inspection task in response to the first exception notification, removing the re-edited candidate inspection task from the target task queue; Determine each of the candidate inspection tasks remaining in the target task queue as an unassigned inspection task; Pushing each of the unassigned inspection tasks to each of the target inspection accounts, and allocating at least one additional inspection task selected from the unassigned inspection tasks to any of the target inspection accounts; Alternatively, when a new target inspection account is detected to be added to the target inspection line, at least one unassigned inspection task is assigned to the new target inspection account, and the target date is unlocked if the new target inspection account meets the preset condition.

6. The inspection task allocation method based on multi-tenancy according to claim 3 is characterized in that: Get any preset inspection tasks created by the registered tenant, including: Constructing a task configuration interface, wherein the task configuration interface includes date options, point configuration items, line options, and a task description column; Determine any of the registered tenants who initiates the task construction request as a target tenant, and push the task configuration interface to the target tenant; Obtain the target inspection point selected by the target tenant based on the point configuration item, the task inspection line selected based on the line option, the inspection date input based on the date option, and the task description information input based on the task description field; Determining the task location information based on a preset tenant location of the target tenant; The preset inspection task is constructed based on the target inspection point, the task inspection line, the inspection date, the task description information and the task location information.

7. The inspection task allocation method based on multi-tenancy according to claim 6 is characterized in that: When any of the registered tenants creates a new preset inspection task based on the target date, the task is allocated based on the corresponding inspection duration of the task and the remaining duration of each target inspection account, including: When the target tenant selects any of the target inspection lines based on the line options, the target date in the locked state is masked in the date option; When the selected inspection date is before the target date, the remaining time of each corresponding target inspection account is obtained; when the target inspection point is obtained based on the point configuration item, the task inspection time of the target inspection point is calculated; When the inspection duration of the task is greater than each of the remaining durations, a second exception notification is pushed to the target tenant, wherein the second exception notification is used to indicate that the preset inspection task cannot be constructed; When the inspection duration of the task is less than or equal to any of the remaining durations, the preset inspection task is constructed and allocated to any of the target inspection accounts that meet the preset conditions.

8. A multi-tenant based inspection task allocation device, characterized in that: It includes at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the multi-tenant based inspection task allocation method as described in any one of claims 1 to 7.

9. An electronic device, characterized in that: Including the multi-tenant based inspection task allocation device as described in claim 8.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the multi-tenant-based inspection task allocation method according to any one of claims 1 to 7.

Images