Task management method, device, system and medium based on property system

By automatically decomposing and allocating tasks in the property management system, the problem of low task allocation efficiency in the existing technology is solved, and more efficient property management is achieved.

CN118469259BActive Publication Date: 2024-11-26LINJIU WISDOM (GUANGDONG) TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410925574.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-07-11
Publication Date
2024-11-26
Estimated Expiration
2044-07-11

AI Technical Summary

Technical Problem

The existing property management system is relatively inefficient in task allocation and requires manual determination of task division, resulting in low management efficiency.

Method used

By setting up an account pool and optional task types in the property system, the subscription information of the management account is automatically obtained, the tasks are decomposed into subtasks, and tasks are automatically assigned according to the account pool and task types to ensure that the tasks meet the needs of the management account.

Benefits of technology

The automatic allocation and decomposition of tasks is realized, the flexibility and rationality of task allocation are improved, and the efficiency of property management is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118469259B_ABST
    Figure CN118469259B_ABST
Patent Text Reader

Abstract

The present invention proposes a task management method, device, system, and medium based on a property system, which belongs to the field of property management. The method includes: obtaining first subscription information sent by a first management account; constructing a target task based on a target task type and task description information; decomposing the target task into multiple target subtasks, and determining the first requirement information of each target subtask based on the task description information; determining multiple first candidate accounts based on the first subscription information and the target task type and constructing multiple subtask account pools; determining the first target account of the target subtask from the subtask account pool based on the first requirement information. According to the technical solution of the embodiment of the present invention, the target task can be automatically decomposed into multiple target subtasks, and tasks can be automatically assigned according to the subscription information of the management account. The decomposed tasks can meet the subscription requirements of the management account, improve the flexibility and rationality of task assignment, and improve the efficiency of property management.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of task management, and in particular to a task management method, device, system and medium based on a property system. Background Art

[0002] With the development of software technology, property management has shifted from offline to online, and property management personnel can follow up on property management related matters online through the property management system. In the field of property management, task allocation is often required, such as holiday duty, community service events, organizing community activities, etc. Supervisors use the property system to assign tasks to property management personnel in corresponding positions. Property management personnel feedback the progress of related tasks in the property system, and supervisors manage and control the progress of tasks based on the feedback from property management personnel. Although online task management has been achieved, the division of tasks still needs to be determined manually after the tasks are formulated, and the efficiency of task management is low. Summary of the invention

[0003] 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 task management method, device, system, and medium based on a property system, which can automatically allocate tasks and improve the flexibility of task management.

[0004] In a first aspect, an embodiment of the present invention provides a task management method based on a property system, which is applied to a property system, wherein the property system is pre-set with a first account pool and a plurality of optional task types, wherein the first account pool includes a plurality of first management accounts, and the task management method based on the property system includes:

[0005] Acquire first subscription information sent by each first management account, wherein the first subscription information records at least one exception task and at least one subscription task type, and the subscription task type is selected from the plurality of optional task types;

[0006] Acquire task description information, determine a target task type from a plurality of optional task types, and construct a target task based on the target task type and the task description information;

[0007] Decomposing the target task into a plurality of target subtasks, and determining first requirement information of each of the target subtasks based on the task description information, wherein the first requirement information is used to indicate the management function and number of accounts of the first target account;

[0008] Based on the subscription task type and the target task type, determining a plurality of first candidate accounts from the first account pool, building a task account pool based on the plurality of first candidate accounts, and determining a subtask account pool for each of the target subtasks based on the task account pool, wherein the exception task of each of the first candidate accounts in the subtask account pool does not include the corresponding target subtask;

[0009] For each of the target subtasks, at least one first target account is determined from the subtask account pool based on the first requirement information, and the target subtask is associated with the corresponding first target account.

[0010] According to some embodiments of the present invention, after associating the target subtask with the corresponding first target account, the method further includes:

[0011] Constructing a task tree based on the target task and the target subtasks, wherein the target task is the root node of the task tree, and each of the target subtasks is a leaf node of the task tree;

[0012] Determine a first control account from the task account pool, determine a second control account from each of the subtask account pools, associate the task tree with the first control account, and associate the target subtask with the corresponding second control account, wherein the management level of the second control account is greater than or equal to the first target account of the same target subtask, and the management level of the first control account is greater than or equal to the second control account;

[0013] When task update information fed back by the first target account is obtained, the leaf node progress of the corresponding target subtask is updated based on the task update information, and the root node progress of the target task is updated based on the progress of each leaf node;

[0014] The leaf node progress is associated with the corresponding second management and control account, and the root node progress is associated with the first management and control account.

[0015] According to some embodiments of the present invention, after associating the target subtask with the corresponding second management and control account, the method further includes:

[0016] Sending a task assignment notification to the first target account;

[0017] Determine the first target account of the allocation confirmation information that has not been fed back within a preset time as an abnormal account, and determine a first replacement account from the first candidate accounts remaining in the subtask account pool;

[0018] replacing the abnormal account by using the first replacement account, and sending the task assignment notification to the first replacement account;

[0019] When the allocation confirmation information fed back by the first replacement account is not obtained within the preset time period, and the number of times the abnormal account is replaced reaches a preset replacement threshold, the target subtask corresponding to the abnormal account is terminated, and an abnormal prompt information is sent to the corresponding second management and control account.

[0020] According to some embodiments of the present invention, after associating the target subtask with the corresponding second management and control account, the method further includes:

[0021] When a replacement instruction initiated by the first target account for the target subtask is obtained, a second replacement account is determined from the first candidate accounts remaining in the subtask account pool;

[0022] Alternatively, when the replacement instruction initiated by the second control account for the first target account is obtained, the first candidate account selected by the second control account from the subtask account pool is determined as the second replacement account;

[0023] The first target account that initiates the replacement instruction is replaced based on the second replacement account.

[0024] According to some embodiments of the present invention, after determining at least one first target account from the subtask account pool based on the first requirement information, the method further includes:

[0025] When at least one of the management functions recorded in the first requirement information of the target subtask is not satisfied by any of the first target accounts, the corresponding target subtask is determined as a subtask to be decomposed, the unsatisfied management function is determined as an exceptional function, and the number of accounts corresponding to the exceptional function is determined as an exceptional number;

[0026] Decompose the subtask to be decomposed into a first subtask and a second subtask, wherein the first subtask corresponds to the first requirement information, the second subtask corresponds to the second requirement information, and the second requirement information includes the exception function and the exception quantity;

[0027] determining at least one second target account from the first management account that has not subscribed to the target task type based on the second demand information;

[0028] The first subtask is associated with the corresponding first target account, and the second subtask is associated with the second target account.

[0029] According to some embodiments of the present invention, the property system is further provided with at least a second account pool, the first account pool and the second account pool belong to different property entities, the second account pool includes a plurality of second management accounts, each of the second management accounts is pre-associated with the second subscription information, the second subscription information records at least one of the exception tasks and at least one of the subscription task types,

[0030] After determining at least one first target account from the subtask account pool based on the first requirement information, the method further includes:

[0031] Determine the target subtask for which the subtask account pool does not satisfy the first requirement information as a collaborative subtask, and determine third requirement information based on the first requirement information and the first target account, wherein the third requirement information is used to indicate the management function and number of accounts of the target collaborative account;

[0032] Determining a plurality of candidate collaboration accounts from the second account pool based on the target task type and the second subscription information;

[0033] At least one target collaboration account is determined from the collaboration candidate accounts according to the third requirement information, and the target subtask is associated with the target collaboration account.

[0034] According to some embodiments of the present invention, the acquiring of task description information and determining a target task type from a plurality of optional task types includes:

[0035] Based on the current date, determining a target event from a plurality of preset events recorded in the schedule, wherein the event date of the target event is after the current date, and the date difference between the event date of the target event and the current date is less than or equal to a preset date threshold;

[0036] Acquire a target template corresponding to the target event from a preset template pool, wherein the template pool includes a plurality of preset event templates, and the event template records event description information and event type of the target event;

[0037] The task description information is generated based on the event description information of the target event, and a target task type is determined from a plurality of selectable task types based on the event type of the target event.

[0038] In a second aspect, an embodiment of the present invention provides a task management device based on a property system, comprising at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions executable 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 task management method based on the property system as described in the first aspect above.

[0039] In a third aspect, an embodiment of the present invention provides a property system, including a task management device based on the property system as described in the second aspect above.

[0040] 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 task management method based on the property system as described in the first aspect above.

[0041] The task management method based on the property system according to the embodiment of the present invention has at least the following beneficial effects: obtaining first subscription information sent by each first management account, wherein the first subscription information records at least one exception task and at least one subscription task type, and the subscription task type is selected from a plurality of optional task types; obtaining task description information, determining a target task type from a plurality of optional task types, and constructing a target task based on the target task type and the task description information; decomposing the target task into a plurality of target subtasks, and determining first requirement information for each target subtask based on the task description information, wherein the first requirement information is used to indicate the management function and the number of accounts of the first target account; determining a plurality of first candidate accounts from the first account pool based on the subscription task type and the target task type, constructing a task account pool based on the plurality of first candidate accounts, and determining a subtask account pool for each target subtask based on the task account pool, wherein the exception task of each of the first candidate accounts in the subtask account pool does not include the corresponding target subtask; for each target subtask, determining at least one first target account from the subtask account pool based on the first requirement information, and associating the target subtask with the corresponding first target account. According to the technical solution of the embodiment of the present invention, the target task can be automatically decomposed into multiple target subtasks, and the tasks can be automatically assigned according to the subscription information of the management account. The decomposed tasks can meet the subscription requirements of the management account, improve the flexibility and rationality of task allocation, and improve property management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 is a schematic diagram of a property system provided by an embodiment of the present invention;

[0043] Figure 2 is a flow chart of a task management method based on a property system provided by another embodiment of the present invention;

[0044] Figure 3 is a schematic diagram of a subscription task type provided by another embodiment of the present invention;

[0045] Figure 4 It is a complete step diagram of a task management method based on a property system provided by another embodiment of the present invention;

[0046] Figure 5 It is a structural diagram of a task management device based on a property system provided by another embodiment of the present invention. DETAILED DESCRIPTION

[0047] Embodiments of the present invention are described in detail below, examples of which 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 only used to explain the present invention, and cannot be understood as limiting the present invention.

[0048] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., and orientations or positional relationships indicated are based on the orientations or positional relationships shown in the accompanying drawings, and 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, and therefore should not be understood as a limitation on the present invention.

[0049] In the description of the present invention, "several" means one or more, "more" means more than two, "greater than", "less than", "exceed" etc. are understood as not including the number itself, and "above", "below", "within" etc. are understood as including the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing the technical features, and cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0050] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. 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.

[0051] The embodiment of the present invention provides a task management method, device, system, and medium based on a property system, wherein the task management method based on the property system includes: obtaining first subscription information sent by each first management account, wherein the first subscription information records at least one exception task and at least one subscription task type, and the subscription task type is selected from multiple optional task types; obtaining task description information, determining a target task type from multiple optional task types, and constructing a target task based on the target task type and the task description information; decomposing the target task into multiple target subtasks, and determining first requirement information of each target subtask based on the task description information, wherein the first requirement information is used to indicate the management function and account number of the first target account; determining multiple first candidate accounts from a first account pool based on the subscription task type and the target task type, constructing a task account pool based on the multiple first candidate accounts, and determining a subtask account pool of each target subtask based on the task account pool, wherein the exception task of each first candidate account in the subtask account pool does not include the corresponding target subtask; for each target subtask, determining at least one first target account from the subtask account pool based on the first requirement information, and associating the target subtask with the corresponding first target account. According to the technical solution of the embodiment of the present invention, the target task can be automatically decomposed into multiple target subtasks, and the tasks can be automatically assigned according to the subscription information of the management account. The decomposed tasks can meet the subscription requirements of the management account, improve the flexibility and rationality of task allocation, and improve property management efficiency.

[0052] First, refer to Figure 1 , Figure 1 The schematic diagram of the property management system provided in the embodiment of the present invention is as follows: the property management system 10 may be a property management server, and the property management system 10 may be connected to a device cluster of multiple property management entities, and the property management entities may be common property management entities such as residential areas or shopping malls, and each property management entity may include a management device 21 and multiple management terminals, such as Figure 1 As shown, the first property entity includes a management device 21, a first terminal 22, and a second terminal 23, and the second property entity includes a third terminal 31 and a fourth terminal 32. The property management personnel log in to the management account through the management terminal and send task subscription information by operating the management terminal, thereby realizing the subscription of the task type. The management device 21 is used to log in to the property system 10 to construct the target task. After the property system 10 obtains the target task, it matches the candidate account that can execute the target task according to the task type subscribed by each management account, and then obtains multiple target subtasks through task decomposition. Exclusive selection is made according to the exception task identified by each management account when subscribing, so as to avoid the target subtask being assigned to the management account that cannot be executed, thereby realizing automatic and accurate task allocation.

[0053] The following is based on the Figure 1The property system shown further illustrates the technical solution of the embodiment of the present invention.

[0054] Reference Figure 2 , Figure 2 A flowchart of a task management method based on a property system provided by an embodiment of the present invention, the task management method based on a property system includes but is not limited to the following steps:

[0055] S11, obtaining first subscription information sent by each first management account, wherein the first subscription information records at least one exception task and at least one subscription task type, and the subscription task type is selected from a plurality of optional task types;

[0056] S12, obtaining task description information, determining a target task type from a plurality of optional task types, and constructing a target task based on the target task type and the task description information;

[0057] S13, decomposing the target task into multiple target subtasks, and determining first requirement information of each target subtask based on the task description information, wherein the first requirement information is used to indicate the management function and number of accounts of the first target account;

[0058] S14, based on the subscription task type and the target task type, determining multiple first candidate accounts from the first account pool, building a task account pool based on the multiple first candidate accounts, and determining a subtask account pool for each target subtask based on the task account pool, wherein the exception task of each first candidate account in the subtask account pool does not include the corresponding target subtask;

[0059] S15 , for each target subtask, determine at least one first target account from the subtask account pool based on the first requirement information, and associate the target subtask with the corresponding first target account.

[0060] It should be noted that each management account corresponds to a manager. The first management account in this embodiment can be the management accounts of multiple managers of the same property entity, for example Figure 1 As shown, the first property entity is community A, the first account pool is a collection of management accounts of all managers in community A, each first management account corresponds to a manager of community A, and the subsequent second management accounts are the same, which will not be repeated later.

[0061] It should be noted that, in this embodiment, each first management account can submit first subscription information to the property system in advance. The first subscription information of each first management account can be set according to actual needs. The first subscription information represents the types of tasks that can be undertaken and the exceptional tasks that need to be excluded. This embodiment uses the first subscription information as a screening condition when assigning tasks to ensure that the assigned tasks can meet the needs of the management account and realize flexible subscription of management personnel.

[0062] It should be noted that the optional task types can be set in advance in the property management system. For the property management field, the task types that need to be assigned are known in advance. Managers can subscribe to the task types according to their own functions and skills. After completing the subscription, the property system can distribute the subscribed optional task types to the manager, improve the rationality of task assignment, and ensure that the manager has the corresponding skills to improve the efficiency and reliability of task completion. In addition, the range of optional task types is usually large. There may be multiple optional tasks under each optional task type. The manager can specify an exception task when sending the first subscription information. The exception task can be selected in the preset task list. All optional tasks corresponding to the corresponding optional task type are displayed in the task list. The first management account can not be selected, or any number of optional tasks can be selected as exception tasks. After the first candidate account is screened out based on the target task type, the relevant first candidate account can be excluded through the exception task. When the task is encountered, it will not be assigned to the corresponding manager, avoiding the task being assigned to a manager who does not have the execution conditions.

[0063] For example, Figure 3 As shown in Figure 1, common task types may include holiday duty, organizing community activities, community cleanup, resident care, and sales assistance, etc. Figure 1 As shown, the first terminal 22 is installed with a property management APP, and the property management APP is used to log in to the property system 10. The manager A logs in to the first management account through the first terminal 22 and logs in to the first management account. Figure 3The subscription interface shown selects "holiday duty", "holding activities in the community" and "community rectification" as the subscription task types. When encountering the task assignment of holiday duty, manager A belongs to the assignable range, that is, belongs to the first candidate account. When encountering the task assignment of resident care, manager A will not be assigned the relevant task because he has not subscribed to this task type. At the same time, after selecting "holiday duty", a selection list of exception tasks can be further popped up. After selecting "Spring Festival duty", "weekend duty" and "continuous duty", the above tasks are used as exception tasks. When the target task is "duty arrangement during the Spring Festival", manager A is determined as the first candidate account through the task type of "holiday duty", but manager A is excluded through "Spring Festival duty", so manager A will not be assigned to the relevant target subtasks; similarly, when the target task is "duty arrangement during the National Day", manager A is determined as the first candidate account through the task type of "holiday duty". Since the first subscription information does not exclude the National Day duty, the relevant target subtasks can be assigned to manager A. When assigning tasks, the property system 10 not only performs task decomposition and personnel matching, but also improves the rationality of task assignment based on the subscription information submitted by the management personnel, thereby improving the efficiency of property management.

[0064] It should be noted that in the field of property management, the construction and allocation of tasks are usually initiated by the heads of relevant departments, e.g. Figure 1 When constructing a target task, you can enter simple text description information as the task description information, and select any optional task type from the pre-set type list as the target task type, for example Figure 3 As shown, when constructing tasks related to Spring Festival duty, the task description information input through the management device 21 is "Spring Festival duty", and the optional task type selected is "holiday duty", thereby constructing the target task.

[0065] It should be noted that after completing the construction of the target task, the task can be decomposed through a pre-set decomposition strategy, such as setting a corresponding subtask template for each optional task type, and recording the relevant functions of each department in the subtask template, so as to achieve automatic decomposition after obtaining the target task, and then construct the first demand information based on the target subtask decomposed based on the subtask template. This embodiment does not limit the specific principle of task decomposition, and can be decomposed based on the management functions of managers, so that the decomposed target subtasks can correspond to the management functions in the property field, and the first demand information is determined according to the determined management functions and number of accounts. For example, taking the above-mentioned "Spring Festival Duty" as an example of the target task, the subtask template is the number of personnel and rank arrangement of each department when on duty during holidays. For example, each rank needs to have at least one manager. When decomposing the subtasks, it can be decomposed into "Department A, rank A, one person on duty during the Spring Festival", "Department A, rank B, two people on duty during the Spring Festival", "Department B, rank A, two people on duty during the Spring Festival", "Department B, rank B, one person on duty during the Spring Festival", etc. The first demand information is {one person in department A, rank A, two people in department A, one person in department B, rank A, two people in department B}.

[0066] It should be noted that after determining the target task, the first account pool is screened according to the target task type, and the first management account that has subscribed to the target task type is determined as the first candidate account. The management function of the first management account is not considered during this screening. If no one has subscribed to the target task type for a certain management function, the corresponding first candidate account cannot be matched even if more dimensions are introduced. Therefore, only the target task type condition is introduced during the initial screening, which not only improves the efficiency of data screening, but also can accurately identify the lack of management functions, thereby triggering subsequent compensation mechanisms, such as selecting the first target account from the first management account that has not subscribed to the target task type, or making a collaboration request to the second account pool.

[0067] It should be noted that the task account pool obtains all first candidate accounts that have subscribed to the target task type. This embodiment further decomposes the task to improve the rationality of task allocation. An exception task is specified when subscribing, and then an exclusion is performed through the exception task, so that the first candidate account in the subtask account pool has subscribed to the target task type and has not specified the target subtask as an exception task, ensuring that the first candidate account in the subtask account pool can be allocated the target subtask.

[0068] It should be noted that after determining the subtask account pool, multiple first target accounts are screened out according to the first requirement information. Since the first requirement information records the management function and the number of accounts, and the management function of each first management account can be determined in advance, the screening of the first target account can be completed through simple information matching. When the number of optional first candidate accounts is greater than the number of accounts in the first requirement information, it can be determined by random selection, or a priority can be set for each first candidate account, and screening is performed according to the priority. No further restrictions are made here.

[0069] It should be noted that after determining the first target account, the corresponding target subtask can be sent to the first target account, such as Figure 1 As shown, the first terminal 22 is logged in with the target account A, and the second terminal 23 is logged in with the target account B. After determining that the target account A is the first target account of the target subtask A, the target subtask A is pushed to the first terminal 22. Similarly, the target subtask B is pushed to the second terminal 23 to ensure that each first target account can obtain the corresponding task information.

[0070] Through the technical solution of this embodiment, the first management account sends the first subscription information to the property system in advance, subscribes to the optional task type through the first subscription information, and records the exceptional tasks that need to be excluded. The first subscription information represents the task acceptance requirements of the first management account. After the target task is constructed, the first candidate account that can undertake the target task is screened out by matching the target task type and the subscribed task type. After the target task is further decomposed to obtain the target subtasks, the exceptional tasks recorded by the first candidate account are excluded. The exceptional tasks of each first candidate account in the subtask account pool do not include any target subtask, and then the first target account of each target subtask is determined, thereby realizing automatic allocation of the target subtask and ensuring that the first candidate account in the subtask account pool has the corresponding management skills and can execute the target subtask, thereby improving the efficiency of task execution and thus improving the efficiency of property management.

[0071] In addition, in one embodiment, referring to Figure 4 After executing step S15, the following steps are also included but not limited to:

[0072] S21, constructing a task tree based on the target task and the target subtasks, wherein the target task is the root node of the task tree, and each target subtask is a leaf node of the task tree;

[0073] S22, determining a first control account from the task account pool, determining a second control account from each subtask account pool, associating the task tree to the first control account, associating the target subtask to the corresponding second control account, wherein the management level of the second control account is greater than or equal to the first target account of the same target subtask, and the management level of the first control account is greater than or equal to the second control account;

[0074] S23, when task update information fed back by the first target account is obtained, the leaf node progress of the corresponding target subtask is updated based on the task update information, and the root node progress of the target task is updated based on the progress of each leaf node;

[0075] S24, associating the leaf node progress with the corresponding second management and control account, and associating the root node progress with the first management and control account.

[0076] It should be noted that the target subtask is obtained by decomposing the target task, so the target task can be used as the root node and the target subtask as the leaf node to construct a task tree, and the specific form of the task tree is not limited here.

[0077] For example, Figure 3 As shown in the figure, the target task is "Children's Day activities in the community", the target task type is "holding activities in the community", and the decomposed target subtasks can be "gift procurement", "venue arrangement" and "owner publicity", etc. The constructed task tree has "Children's Day activities in the community" as the root node, and "gift procurement", "venue arrangement" and "owner publicity" as leaf nodes.

[0078] It should be noted that the first control account and the second control account can be specified when constructing the target task. The execution progress of the target task can be monitored through the first control account, and the execution progress of the target subtask can be monitored through the second control account. Of course, the first control account and the second control account can also be determined from the subtask account pool, which will not be elaborated here. It is worth noting that the first control account and the second control account can be selected from the first target account, ensuring that their management levels meet the requirements. In addition, the first control account can also be the second control account at the same time, and each second control account can be associated with multiple target subtasks to improve management flexibility.

[0079] For example, continuing to refer to the above-mentioned target task of "Community Children's Day Activities", Community A includes Property Department A and Property Department B. Manager A of Property Department A has a higher management level, and Manager B of Property Department B has the same level as Manager A. One of Manager A and Manager B can be determined as the first management and control account; taking the example of Property Department A being assigned "gift procurement" and "venue arrangement", Manager A can be used as the second management and control account for the two target subtasks, or Manager C can be selected from Property Department A as the second management and control account for "venue arrangement".

[0080] It should be noted that after constructing the task tree, each first target account is assigned a corresponding target subtask. The first target account can upload task update information through the management terminal to realize the progress update of the target subtask, so as to determine the corresponding leaf node progress. The weight of each leaf node can be set in the task tree, so as to convert the leaf node progress into the root node progress for statistics, associate the leaf node progress with the second management and control account, associate the root node progress with the first management and control account, and make relevant notifications to realize the progress monitoring of the target task and target subtask. This embodiment does not impose many restrictions on the task progress update method, and can perform relevant calculations according to actual needs.

[0081] For example, taking the target subtask as the above-mentioned "gift procurement" as an example, the first target account needs to complete the procurement of 100 gifts. After completing the procurement of 50 pieces, the task update information uploaded through the management terminal is "50 pieces", thereby determining that the leaf node progress is 50%. The weight of the target subtask is 0.3, and the calculated root node progress is 15%.

[0082] In addition, in one embodiment, referring to Figure 4 After executing step S22, the following steps are also included but not limited to:

[0083] S31, sending a task assignment notification to the first target account;

[0084] S32, determining the first target account of the allocation confirmation information that has not been fed back within a preset time as an abnormal account, and determining a first replacement account from the remaining first candidate accounts in the subtask account pool;

[0085] S33, replacing the abnormal account with the first replacement account, and sending a task assignment notification to the first replacement account;

[0086] S34, when the allocation confirmation information fed back by the first replacement account is not obtained within the preset time, and the number of times the abnormal account is replaced reaches the preset replacement threshold, the target subtask corresponding to the abnormal account is terminated, and an abnormal prompt information is sent to the corresponding second management and control account.

[0087] It should be noted that since task allocation and decomposition are automatically completed by the property system, the first target account may not be able to respond in time. For example, the corresponding manager is on vacation or has gone out to perform other tasks. Therefore, this embodiment also proposes a compensation mechanism after completing the task allocation. After the first target account is determined, a task allocation notification is issued. The manager can confirm after logging into the first target account on the management terminal to trigger the allocation confirmation information. If the allocation confirmation information is not obtained within the preset time, the corresponding first target account is determined as an abnormal account, and the first replacement account is determined from the remaining first candidate accounts. The abnormal account is replaced by the first replacement account to achieve personnel compensation for the abnormal account.

[0088] It should be noted that the first replacement account may also be determined as an abnormal account. Therefore, the above compensation mechanism can be repeated. If the number of replacements reaches the replacement threshold, for example, if the allocation confirmation information cannot be obtained after 5 replacements, it can be considered that the target subtask does not have an executor, and a prompt is sent to the second management and control account to request human access. The allocation of the target subtask can be completed through offline allocation to ensure that the target subtask can be executed smoothly.

[0089] In addition, in one embodiment, referring to Figure 4 After executing step S22, the following steps are also included but not limited to:

[0090] S41, when a replacement instruction initiated by the first target account for the target subtask is obtained, a second replacement account is determined from the remaining first candidate accounts in the subtask account pool;

[0091] S42, when a replacement instruction initiated by the second control account for the first target account is obtained, a first candidate account selected by the second control account from the subtask account pool is determined as a second replacement account;

[0092] S43, replacing the first target account that initiates the replacement instruction based on the second replacement account.

[0093] It should be noted that the first target account is determined by the property system based on the first subscription information. When there are multiple optional first candidate accounts, the property system can randomly select the first target account, which results in some first target accounts being assigned more tasks. In order to avoid uneven task distribution, this embodiment can initiate a replacement instruction through the first target account and the second control account. The replacement instruction of the first target account is for the target subtask, and the replacement instruction of the second control account is for the first target account, thereby triggering the property system to determine a new second replacement account from the subtask account pool, realize task transfer and secondary distribution, and improve the flexibility of task management.

[0094] In addition, in one embodiment, referring to Figure 4 In step S15, after determining at least one first target account from the subtask account pool based on the first requirement information, the following steps are also included but not limited to:

[0095] S51, when at least one management function recorded in the first requirement information of the target subtask is not satisfied by any first target account, the corresponding target subtask is determined as a subtask to be decomposed, the unsatisfied management function is determined as an exception function, and the number of accounts corresponding to the exception function is determined as an exception number;

[0096] S52, decomposing the subtask to be decomposed into a first subtask and a second subtask, wherein the first subtask corresponds to the first requirement information, the second subtask corresponds to the second requirement information, and the second requirement information includes an exception function and an exception quantity;

[0097] S53, determining at least one second target account from the first management account that has not subscribed to the target task type based on the second demand information;

[0098] S54: Associating the first subtask with the corresponding first target account, and associating the second subtask with the second target account.

[0099] It should be noted that when at least one management function recorded in the first demand information of the target subtask is not satisfied by any first target account, it can be determined that the first management account subscribed to the target task type is insufficient. For example, in the above-mentioned example of "Community Children's Day Activities", the target subtask corresponding to "Gift Purchasing" requires purchasing personnel and logistics personnel. Therefore, the management functions of the first demand information may include "purchasing function" and "logistics function". If no purchasing personnel subscribes to the target task type, when determining the first target account, the subtask account pool does not have the first candidate account with "purchasing function", and it is impossible to assign the corresponding first target account to the target subtask of "Gift Purchasing". In this case, this embodiment further decomposes the target subtask twice, constructs the first subtask based on the part that can be completed at present, and constructs the second subtask for the part that cannot be completed. For example, the transportation task corresponding to the "logistics function" is determined as the first subtask, and the procurement task is determined as the second subtask. Through the technical solution of this embodiment, it is possible to perform multi-layer decomposition of subtasks and improve the rationality of task allocation.

[0100] It should be noted that after determining the second subtask, since the first target account is selected from the subtask candidate pool, it can be determined that no first management account with this management function has subscribed to the relevant target task type. In order to ensure the completion of the task, the second target account can be determined from the first management account that has not subscribed to the target task type, thereby realizing temporary calling of personnel and associating the second subtask to the second target account. For example, continuing with the above example, the first management account with "procurement function" is screened out from the first management personnel who have not subscribed to "holding activities in the community" as the second target account, and the corresponding management personnel are temporarily called to ensure that the task can be completed smoothly and to improve the flexibility of task allocation.

[0101] In addition, in one embodiment, referring to Figure 4 The property system is further provided with at least a second account pool, the first account pool and the second account pool belong to different property entities, the second account pool includes a plurality of second management accounts, each second management account is pre-associated with second subscription information, the second subscription information records at least one exception task and at least one subscription task type, in step S15, after determining at least one first target account from the subtask account pool based on the first demand information, the following steps are also included but not limited to:

[0102] S61, determining a target subtask whose subtask account pool does not meet the first requirement information as a collaborative subtask, and determining third requirement information based on the first requirement information and the first target account, wherein the third requirement information is used to indicate the management function and number of accounts of the target collaborative account;

[0103] S62, determining a plurality of candidate collaboration accounts from a second account pool based on the target task type and the second subscription information;

[0104] S63: Determine at least one target collaboration account from the collaboration candidate accounts according to the third requirement information, and associate the target subtask with the target collaboration account.

[0105] It should be noted that the property system implemented in this embodiment can be used to manage multiple property entities. For example, multiple communities and shopping malls can be managed through the property system. Each community or shopping mall corresponds to a property entity, and the property management personnel of each property entity are usually independent. Therefore, an account pool is constructed for each property entity. The first account pool of this embodiment can be a collection of property management personnel of community A, and the second account pool can be a collection of property management personnel of community B.

[0106] It should be noted that, according to the description of the above embodiment, after screening the subscription task types and exception tasks, it is very likely that the subtask account pool cannot meet the first demand information, such as insufficient management functions and personnel. In this case, assistance can be requested from other property entities, and the corresponding target subtask can be determined as a collaborative subtask, and then the third demand information can be determined. The third demand information of this embodiment is a true subset of the first demand information, that is, the third demand information is constructed according to the unmet part of the first demand information, providing a basis for collaborative requests when the number of first target accounts is insufficient.

[0107] It should be noted that after determining the third demand information, personnel matching can be performed from the second account pool to achieve cross-cell collaboration. Referring to the same principle as the first account pool, multiple collaboration candidate accounts are matched in the second account pool according to the subscription task type and exception tasks to build a collaboration account pool, and then multiple target collaboration accounts are determined based on the third demand information. The specific matching process can refer to the description of the above embodiment, and will not be repeated here.

[0108] For example, Figure 1 As shown, the target subtask A is "community cleaning before the Spring Festival", and the first demand information is that the management function of demand A is "cleaning staff", and the number of accounts is 10, but there are only 6 corresponding first candidate accounts in the subtask account pool. Based on this, the third demand information is constructed as a collaborative demand, and the corresponding management function is "cleaning task", and the number of accounts is 4. 4 corresponding target collaborative accounts are selected from the second account pool and the task allocation is completed. For example, the management personnel corresponding to the fourth terminal 32 is the cleaning staff, and the corresponding target subtask A is sent to the fourth terminal 32.

[0109] In addition, in one embodiment, referring to Figure 4 Step S12 specifically includes but is not limited to the following steps:

[0110] S121, based on the current date, determining a target event from a plurality of preset events recorded in the calendar, wherein the event date of the target event is after the current date, and the date difference between the event date of the target event and the current date is less than or equal to a preset date threshold;

[0111] S122, acquiring a target template corresponding to a target event from a preset template pool, wherein the template pool includes a plurality of preset event templates, and the event template records event description information and event type of the target event;

[0112] S123, generating task description information based on the event description information of the target event, and determining a target task type from a plurality of optional task types based on the event type of the target event.

[0113] It should be noted that the target task can be constructed through the management device. This embodiment further pre-sets a template pool for periodic events, and automatically triggers the target task through the event template, thereby improving the intelligence of task allocation. For example, for the task type of holiday duty, the time of the holiday is fixed, so multiple preset events related to holiday duty can be constructed in the schedule, and the construction of the target task is automatically triggered when the current date is close to the event date. This embodiment can determine whether the date is close by setting a date threshold. The specific threshold can be set according to actual needs, for example, the date threshold is 1 month.

[0114] What is needed is that after the target event is triggered, the corresponding target template is obtained to construct the task. The target template can be pre-configured with the corresponding event description information and event type. For example, if the target event is the Spring Festival, the event description information is Spring Festival duty, and the event type is holiday duty. The specific content can be set according to the actual situation of the event.

[0115] It should be noted that after determining the target event, the event description information is directly determined as the task description information, or the task description information is generated according to the set requirements. For example, the event description information is "on duty during the Spring Festival", and the pre-set requirement is that one person is on duty in each department, then the task description information is "one person is arranged to be on duty in each department during the Spring Festival", thereby triggering the task allocation process of the above embodiment and realizing automatic task triggering.

[0116] like Figure 5 As shown, Figure 5 The present invention also provides a task management device based on a property system, including:

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

[0118] The memory 502 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 502 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 502, and the processor 501 calls and executes the task management method based on the property system in the embodiment of this application;

[0119] Input / output interface 503, used to implement information input and output;

[0120] Communication interface 504, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0121] A bus 505 that transmits information between various components of the device (e.g., the processor 501, the memory 502, the input / output interface 503, and the communication interface 505);

[0122] The processor 501 , the memory 502 , the input / output interface 503 and the communication interface 504 are connected to each other in communication within the device via a bus 505 .

[0123] An embodiment of the present application also provides a property system, including the task management device based on the property system as described above.

[0124] 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 task management method based on the property system is implemented.

[0125] As a non-transient computer-readable storage medium, the memory 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 devices. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may 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 implemented to be located in one place, or may also 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.

[0126] It will be appreciated by those skilled in the art that all or some of the steps and systems in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or transient medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (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, it is well known to those skilled in the art that communication media generally include 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.

[0127] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions under the shared conditions without violating the spirit of the present invention. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A task management method based on property system, It is characterized in that Applied to a property management system, the property management system is pre-set with a first account pool and a plurality of optional task types, the optional task types include a plurality of optional tasks, the first account pool includes a plurality of first management accounts, and the task management method based on the property management system includes: Acquire first subscription information sent by each first management account, wherein the first subscription information records at least one exception task and at least one subscription task type, the subscription task type is selected from a plurality of optional task types, the exception task is selected from the optional tasks of the subscription task type, and the exception task is used to indicate the optional task that the first management account needs to exclude from the subscription task type; Acquire task description information, determine a target task type from a plurality of optional task types, and construct a target task based on the target task type and the task description information; Decomposing the target task into a plurality of target subtasks, and determining first requirement information of each of the target subtasks based on the task description information, wherein the first requirement information is used to indicate the management function and number of accounts of the first target account; Based on the subscription task type and the target task type, determining a plurality of first candidate accounts from the first account pool, building a task account pool based on the plurality of first candidate accounts, and determining a subtask account pool for each of the target subtasks based on the task account pool, wherein the exception task of each of the first candidate accounts in the subtask account pool does not include the corresponding target subtask; For each of the target subtasks, determining at least one of the first target accounts from the subtask account pool based on the first requirement information, and associating the target subtask with the corresponding first target account; After determining at least one first target account from the subtask account pool based on the first requirement information, the method further includes: When at least one of the management functions recorded in the first requirement information of the target subtask is not satisfied by any of the first target accounts, the corresponding target subtask is determined as a subtask to be decomposed, the unsatisfied management function is determined as an exceptional function, and the number of accounts corresponding to the exceptional function is determined as an exceptional number; Decompose the subtask to be decomposed into a first subtask and a second subtask, wherein the first subtask corresponds to the first requirement information, the second subtask corresponds to the second requirement information, and the second requirement information includes the exception function and the exception quantity; determining at least one second target account from the first management account that has not subscribed to the target task type based on the second demand information; Associating the first subtask with the corresponding first target account, and associating the second subtask with the second target account; The property system is further provided with at least a second account pool, wherein the first account pool and the second account pool belong to different property entities, the second account pool includes a plurality of second management accounts, each of the second management accounts is pre-associated with second subscription information, and the second subscription information records at least one of the exception tasks and at least one of the subscription task types, After determining at least one first target account from the subtask account pool based on the first requirement information, the method further includes: Determine the target subtask for which the subtask account pool does not satisfy the first requirement information as a collaborative subtask, and determine third requirement information based on the first requirement information and the first target account, wherein the third requirement information is used to indicate the management function and number of accounts of the target collaborative account; Determining a plurality of candidate collaboration accounts from the second account pool based on the target task type and the second subscription information; At least one target collaboration account is determined from the collaboration candidate accounts according to the third requirement information, and the target subtask is associated with the target collaboration account.

2. The task management method based on the property system according to claim 1, It is characterized in that After associating the target subtask with the corresponding first target account, the method further includes: Constructing a task tree based on the target task and the target subtasks, wherein the target task is the root node of the task tree, and each of the target subtasks is a leaf node of the task tree; Determine a first control account from the task account pool, determine a second control account from each of the subtask account pools, associate the task tree with the first control account, and associate the target subtask with the corresponding second control account, wherein the management level of the second control account is greater than or equal to the first target account of the same target subtask, and the management level of the first control account is greater than or equal to the second control account; When task update information fed back by the first target account is obtained, the leaf node progress of the corresponding target subtask is updated based on the task update information, and the root node progress of the target task is updated based on the progress of each leaf node; The leaf node progress is associated with the corresponding second management and control account, and the root node progress is associated with the first management and control account.

3. The task management method based on the property system according to claim 2, It is characterized in that After associating the target subtask with the corresponding second management and control account, the method further includes: Sending a task assignment notification to the first target account; Determine the first target account of the allocation confirmation information that has not been fed back within a preset time as an abnormal account, and determine a first replacement account from the first candidate accounts remaining in the subtask account pool; replacing the abnormal account by using the first replacement account, and sending the task assignment notification to the first replacement account; When the allocation confirmation information fed back by the first replacement account is not obtained within the preset time period, and the number of times the abnormal account is replaced reaches a preset replacement threshold, the target subtask corresponding to the abnormal account is terminated, and an abnormal prompt information is sent to the corresponding second management and control account.

4. The task management method based on the property system according to claim 2, It is characterized in that After associating the target subtask with the corresponding second management and control account, the method further includes: When a replacement instruction initiated by the first target account for the target subtask is obtained, a second replacement account is determined from the first candidate accounts remaining in the subtask account pool; Alternatively, when the replacement instruction initiated by the second control account for the first target account is obtained, the first candidate account selected by the second control account from the subtask account pool is determined as the second replacement account; The first target account that initiates the replacement instruction is replaced based on the second replacement account.

5. The task management method based on the property system according to claim 1, It is characterized in that The acquiring of task description information and determining a target task type from a plurality of optional task types includes: Based on the current date, determining a target event from a plurality of preset events recorded in the schedule, wherein the event date of the target event is after the current date, and the date difference between the event date of the target event and the current date is less than or equal to a preset date threshold; Acquire a target template corresponding to the target event from a preset template pool, wherein the template pool includes a plurality of preset event templates, and the event template records event description information and event type of the target event; The task description information is generated based on the event description information of the target event, and a target task type is determined from a plurality of selectable task types based on the event type of the target event.

6. A task management device based on a property system, It is 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 property system-based task management method as described in any one of claims 1 to 5.

7. A property system, It is characterized in that Including the task management device based on the property system as described in claim 6.

8. A computer-readable storage medium, It is 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 task management method based on the property system as described in any one of claims 1 to 5.