Task order processing system

Abstract

To provide a task order processing system for improving convenience of operation of a user, allowing the user to directly start task order allocation when browsing construction drawings, schedules, and price management tables without leaving a present interface, and thereby improving accuracy and efficiency in task order creation.SOLUTION: A system, in response to a user initiating a task order creation operation for a construction project, determines task order assignment entry information, acquires related information on the basis of the task order assignment entry information, generates a target task order on the basis of the related information, and automatically adapts acquisition of the related information and a task order generation logic on the basis of a specific task order assignment entry selected by the user, thereby ensuring high consistency between the task order and an actual situation of the project.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This invention claims priority from a Chinese application filed on August 19, 2024, bearing application number 202411134930.6, a Chinese application filed on June 4, 2024, bearing application number 202410713323.9, a Chinese application filed on May 22, 2024, bearing application number 202410639396.8, and a Chinese application filed on March 8, 2024, bearing application number 202410263671.0, the entire contents of which are incorporated herein by reference.

[0002] The present specification relates to the technical field of information processing, and more particularly to a task order processing system. [Background technology]

[0003] In architectural and construction project management, task order creation and allocation are crucial processes for ensuring the smooth progress of a project. When assigning task orders, the prime contractor typically assigns tasks to subcontractors, who then assign task areas and task items to different work groups, which then assign them to workers. Currently, task order creation relies on manual entry and manual assignment. However, due to the large number of task items and the complexity of the areas, workers face the greatest challenge of finding the appropriate task item from the large number of task items and selecting the appropriate area, time, and price to assign a task order. This manual method is not only inefficient but also prone to errors, especially in large, complex projects that involve multiple areas, different types of construction tasks, and frequent cost management and progress tracking. As projects grow in scale and complexity, there is a growing need for intelligent and automated task order management systems.

[0004] Therefore, it is expected to provide a task order processing system that can realize intelligent filling of task orders, improve the efficiency and accuracy of task order creation, reduce labor costs, and improve user experience. Summary of the Invention

[0005] The present invention includes a task order processing system including a processor configured to, in response to a user initiating a task order creation operation for a construction project, identify task order assignment entry information, obtain related information based on the task order assignment entry information, and generate a target task order based on the related information.

[0006] In some embodiments, the processor is further configured, in response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, to obtain target construction area information including a parent area and a child area, identify a target past task order assigned by the user based on the parent area, identify a reference task order based on the target past task order and the child area, and generate the target task order based on the reference task order and the target construction area information.

[0007] In some embodiments, the processor is further configured to obtain all past source task orders of the user within a predetermined period in the parent area and sort them chronologically to obtain a first sorted result, and identify the target past task order from the first sorted result.

[0008] In some embodiments, the processor is further configured to obtain all split task orders of the user that have been accepted by a contract fulfiller in the parent area within a predetermined period of time, and sort them chronologically to obtain a second sorted result, and identify the target past task order from the second sorted result.

[0009] In some embodiments, the processor is further configured, in response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, to obtain user information of the user and project information of the task order to be created, identify a target task order template from a task order template library based on the user information and the project information, identify a reference task order based on the target task order template, and identify the target task order based on the target task order template and the reference task order.

[0010] In some embodiments, the processor is further configured to: acquire past task orders including past user information and past project information; divide the past task orders into a plurality of primary groups based on the past user information and the past project information; for each of the primary groups, divide the past task orders corresponding to the primary group into a plurality of secondary groups based on construction areas, task items, and contract performers in the past task orders; for each of the plurality of secondary groups, identify a task order template and a corresponding number of times the template has been used based on the past task orders corresponding to the secondary group; and identify the task order template library based on the task order templates corresponding to the plurality of secondary groups and the number of times the template has been used.

[0011] In some embodiments, the processor is further configured to, for each of the plurality of secondary groups, identify a most recent past task order in the secondary group as a related task order of a task order template corresponding to the secondary group; identify the task order template library based on the task order templates corresponding to the plurality of secondary groups, a number of template uses, and the related task orders; query the related task orders based on the target task order template; and identify the related task orders as reference task orders.

[0012] In some examples, the task order template library includes a first type task order template library and a second type task order template library, the first type task order template library being a source task order template library and the second type task order template library being a split task order template library, and the processor is further configured to: in response to the user initiating a create source task order operation, perform matching within the first type task order template library based on the user information and the project information to identify the target task order template; in response to the user initiating a create split task order operation, identify contract performer information based on the task order to be split, perform matching within the second type task order template library based on the user information, the project information, and the contract performer information to identify a recommended parent-level task order; and in response to the recommended parent-level task order satisfying a predetermined condition, identify the target task order template based on the recommended parent-level task order.

[0013] In some examples, the processor is further configured to obtain a current state of a contract fulfiller associated with task order templates in a task order template library, including a source task order template and a split task order template; and adjust the availability of the task order template in response to the current state of the contract fulfiller being unavailable, wherein adjusting the availability of the task order template includes: updating the task order template as unavailable in response to the task order template being the source task order template; determining whether the unavailable contract fulfiller is a worker in response to the task order template being the split task order template; updating the task order template as unavailable in response to the unavailable contract fulfiller being a worker; determining whether the worker is the only contract fulfiller for the corresponding task order template in response to the worker being the only contract fulfiller for the corresponding task order template; updating the corresponding task order template as unavailable in response to the worker being the only contract fulfiller for the corresponding task order template; and excluding the worker from the contract fulfillers of the corresponding task order template in response to the worker not being the only contract fulfiller for the corresponding task order template.

[0014] In some embodiments, the processor is further configured, in response to the task order assignment entry information indicating that the task order assignment entry is a drawing entry, to obtain drawing area information, identify a reference task order based on the drawing area information, and identify the target task order based on the reference task order.

[0015] In some embodiments, the processor is further configured to analyze a construction drawing, extract numeric information and alphabetic information in the construction drawing, identify an axis grid node set for the construction drawing based on the numeric information and the alphabetic information, obtain a combination of target nodes in the axis grid node set, enclose a closed polygon with the combination of target nodes, and identify drawing area information based on the combination of target nodes.

[0016] In some embodiments, the processor is further configured to obtain an initial node combination input by the user, each node being a node within the axis grid node set, validate the initial node combination based on predetermined conditions including at least whether it encloses a unique closed polygon, identify a valid node combination, obtain input information input by the user based on the valid node combination, and identify the target node combination.

[0017] In some embodiments, the processor is further configured to obtain part information and initial coordinates of the nodes of the combination of the target nodes, identify standard coordinates of the nodes based on the initial coordinates, and identify the reference task order based on the part information and the standard coordinates.

[0018] In some embodiments, the processor is further configured, in response to the task order assignment entry information indicating that the task order assignment entry is a progress entry, to obtain progress unit information entered by the user, identify a reference task order based on the progress unit information, and identify a target task order based on the reference task order.

[0019] In some embodiments, the processor is further configured, in response to the task order allocation entry information indicating that the task order allocation entry is a price management table entry, to obtain listing information in a price management table cell entered by the user, identify a reference task order based on the listing information, and identify a target task order based on the reference task order. [Effects of the Invention]

[0020] The embodiments of the present specification have at least the following beneficial effects: By identifying a target task order based on task order assignment entry information, the user's operation convenience is improved, allowing the user to directly initiate task order assignment when viewing construction drawings, schedules, and price management tables without leaving the current interface, thereby improving the accuracy and efficiency of task order creation; The processor automatically adapts related information acquisition and task order generation logic based on the specific task order assignment entry selected by the user, ensuring high consistency between the task order and the actual situation of the project. [Brief explanation of the drawings]

[0021] The present invention is further illustrated by exemplary embodiments, which are described in detail in the drawings, and are not intended to be limiting, and in which like reference numerals refer to like structures.

[0022] [Figure 1] FIG. 1 is a schematic diagram of an application scenario of a task order processing system according to some embodiments of the present disclosure.

[0023] [Figure 2] FIG. 1 is an example block diagram of a task order processing system according to some embodiments of the present disclosure.

[0024] [Figure 3]1 is an exemplary flowchart of a task order processing method according to some embodiments of the present disclosure.

[0025] [Figure 4] 1 is a first exemplary flowchart for generating a target task order according to some embodiments herein.

[0026] [Figure 5A] FIG. 10 is an exemplary diagram illustrating identifying a reference task order according to some embodiments herein.

[0027] [Figure 5B] FIG. 2 is an exemplary sequence diagram of a task order processing method according to some embodiments of the present disclosure.

[0028] [Figure 6] 10 is a second exemplary flowchart for generating a target task order according to some embodiments herein.

[0029] [Figure 7] 10 is an exemplary third flowchart for generating a target task order according to some embodiments herein.

[0030] [Figure 8] 10 is an exemplary fourth flowchart for generating a target task order according to some embodiments herein.

[0031] [Figure 9] 10 is an exemplary fifth flowchart for generating a target task order according to some embodiments herein.

[0032] [Figure 10] 10 illustrates an example flowchart for adjusting the availability of a task order template in accordance with some embodiments herein.

[0033] [Figure 11]FIG. 1 is an exemplary schematic diagram illustrating allocation of target task orders for different construction sites according to some embodiments of the present disclosure.

[0034] [Figure 12A] FIG. 10 is an exemplary diagram of a first axis number according to some embodiments herein.

[0035] [Figure 12B] FIG. 10 is an exemplary diagram of a second axis number according to some embodiments herein.

[0036] [Figure 12C] FIG. 10 is an exemplary schematic diagram of an axis grid in accordance with some embodiments of the present disclosure.

[0037] [Figure 12D] FIG. 2 is an exemplary schematic diagram of a graphical construction site database according to some embodiments herein. DETAILED DESCRIPTION OF THE INVENTION

[0038] In order to more clearly explain the technical solutions of the embodiments of the present specification, the drawings necessary for the description of the embodiments will be briefly described below. Obviously, the accompanying drawings in the following description are merely some examples or embodiments of the present specification, and those skilled in the art can apply the present specification to other similar scenarios based on these drawings without any creative effort. Unless otherwise clear from the context or indicated otherwise, the same symbols in the figures represent the same structures or operations.

[0039] It should be understood that the terms "system," "device," "unit," and / or "module" used herein are ways of distinguishing between different components, elements, parts, portions, or assemblies at different levels. However, other terms may be substituted if they achieve the same purpose.

[0040] Unless the context clearly indicates otherwise, terms such as "a," "one," "an," "one," and / or "the" do not specifically refer to the singular but can also include the plural. In general, the terms "comprise" and "comprising" only indicate the inclusion of explicitly identified steps and elements, and do not constitute an exclusive list, and the method or apparatus may include other steps or elements.

[0041] Flowcharts are used herein to describe operations performed by systems according to embodiments of the present invention. It should be understood that the operations are not necessarily performed in exact order. Instead, steps may be performed in reverse order or simultaneously. Other operations may be added to these processes, or particular steps or steps may be removed from these processes.

[0042] Existing task order management systems typically provide a single task order assignment entry, requiring users to manually enter all relevant information in a dedicated interface to create a task order. This method requires users to frequently switch between different interfaces, for example, from viewing construction drawings, schedules, and price management tables to returning to the dedicated task order assignment interface. This not only increases operational complexity but also increases the risk of information omissions and inconsistencies. Furthermore, traditional systems lack the ability to automatically associate information or automatically create task orders, and they are unable to fully utilize historical data and reference information, making the task order creation process complicated and inaccurate.

[0043] The embodiments of the present specification provide a task order processing system that can intelligently identify and process multiple types of task order allocation entry information (e.g., dedicated entries, drawing entries, visual progress entries, and price management table entries) according to a construction project creation operation initiated by a user, and obtain related relevant information based on these entries, such as the target construction area, user information, the area corresponding to the drawing, etc. By integrating this information, the system can automatically generate accurate target task orders, more efficiently fill out and assign task orders, reduce human costs and time costs, greatly improve the efficiency and accuracy of task order creation, reduce human errors, and enhance the intelligence level of the system, thereby optimizing the construction project management process.

[0044] FIG. 1 is a schematic diagram of an application scenario of a task order processing system according to some embodiments of the present disclosure.

[0045] In some embodiments, as shown in FIG. 1, a task order processing system application scenario 100 includes a processor 110, a storage device 120, a user terminal 130, and a user 140, etc.

[0046] The processor 110 is used to manage resources and process data and / or information from at least one component or external data source in the application scenario 100 of the task order processing system. For example, the processor 110 may obtain input information from a user 140 from a user terminal 130. For a description of the input information, please refer to the related description of FIG. 3.

[0047] In some embodiments, processor 110 may include one or more sub-processors. By way of example, processor 110 may be a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), or the like, or any combination thereof.

[0048] The storage device 120 can be used to store data and / or instructions. The storage device 120 can include one or more storage components, each of which can be a separate device or part of another device, such as part of the processor 110.

[0049] The user terminal 130 is one or more terminals used by a corresponding user 140. The user 140 refers to any individual or group that needs to process a task order. For example, the user 140 may be a prime contractor, a subcontractor, a functional department manager, a team leader, and a contract performer of a construction project. For a related description of the contract performer, please refer to the corresponding description in FIG. 3.

[0050] In some embodiments, user terminal 130 may be one or any combination of a mobile device, a tablet computer, a laptop computer, a desktop computer, or other device having input and / or output capabilities.

[0051] In some embodiments, one user terminal may correspond to one user or may correspond to multiple users.

[0052] In some embodiments, a user 140 may create or assign a task order via a user terminal 130. In some embodiments, a contract performer may receive a task order assigned by their superior (e.g., a team leader) via a user terminal 130. For a related description of task orders, see the corresponding description in FIG. 3.

[0053] In some embodiments, the components of task order processing system application scenario 100 may be connected via a network (not shown). In some embodiments, the network may be one or more of a wired network or a wireless network. For example, the network may include a cable network, a fiber optic network cable connection, or the like, or a combination thereof. The network connections between the components may employ one or more of the above methods.

[0054] It should be noted that the above description of the application scenario 100 of the task order processing system is for illustrative purposes only and is not intended to limit the scope of the present specification. Those skilled in the art can make various changes and modifications based on the description of the present specification. However, these changes and modifications do not depart from the scope of the present specification.

[0055] FIG. 2 is an example block diagram of a task order processing system according to some embodiments of the present disclosure.

[0056] In some embodiments, as shown in FIG. 2, task order processing system 200 may include an identification module 210, an acquisition module 220, and a generation module 230.

[0057] In some embodiments, the identification module 210 is used to identify task order assignment entry information in response to a user initiating a task order creation operation for a construction project.

[0058] In some embodiments, the retrieval module 220 is used to retrieve relevant information based on the task order assignment entry information.

[0059] In some embodiments, the generation module 230 is used to generate a target task order based on the relevant information.

[0060] In some embodiments, the generation module 230 is further used to, in response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, obtain target construction area information including a parent area and a child area, identify a target past task order assigned by the user based on the parent area, identify a reference task order based on the target past task order and the child area, and generate a target task order based on the reference task order and the target construction area information.

[0061] In some embodiments, the generation module 230 is further used to obtain all past source task orders of the user within a predetermined period in the parent area, sort them chronologically, obtain a first sorted result, and identify a target past task order from the first sorted result.

[0062] In some embodiments, the generation module 230 is further used to obtain all split task orders of the user that have been accepted by the contract fulfiller in the parent area within a predetermined period, sort them chronologically, obtain a second sorted result, and identify a target past task order from the second sorted result.

[0063] In some embodiments, the generation module 230 is further used to, in response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, obtain user information of the user and project information of the task order to be created, identify a target task order template from a task order template library based on the user information and the project information, identify a reference task order based on the target task order template, and identify a target task order based on the target task order template and the reference task order.

[0064] In some embodiments, the generation module 230 is further used to obtain past task orders including past user information and past project information, divide the past task orders into a plurality of primary groups based on the past user information and the past project information, divide the past task orders of the primary group into a plurality of secondary groups based on the construction area, task items, and contract performers in the past task orders, identify task order templates and the corresponding number of times the templates are used for each of the plurality of secondary groups based on the past task orders corresponding to the secondary group, and identify a task order template library based on the task order templates and the number of times the templates are used for each of the plurality of secondary groups.

[0065] In some embodiments, the generation module 230 further identifies, for each of the plurality of secondary groups, the most recent past task order in the secondary group as a related task order of the task order template corresponding to the secondary group, and identifies a task order template library based on the task order templates corresponding to the plurality of secondary groups, the number of times the templates are used, and the related task orders, which is further used to query the related task orders based on the target task order template and identify the related task orders as reference task orders.

[0066] In some examples, the task order template library includes a first type of task order template library and a second type of task order template library, the first type of task order template library is an order template library, and the second type of task order template library is a split task order template library; and the generation module 230 is further used to: in response to a user initiating a create source task order operation, perform matching within the first type of task order template library based on user information and project information to identify a target task order template; in response to a user initiating a create split task order operation, perform matching within the second type of task order template library based on the user information, project information, and contract performer information to identify a recommended parent-level task order; and in response to the recommended parent-level task order satisfying a predetermined condition, identify a target task order template based on the recommended parent-level task order.

[0067] In some embodiments, the task order processing system 200 further includes an update module that is used to obtain a current state of a contract fulfiller associated with task order templates, including a source task order template and a split task order template, in the task order template library, and adjust the availability of the task order template in response to the current state of the contract fulfiller being unavailable, where adjusting the availability of the task order template includes updating the task order template as unavailable in response to the task order template being the source task order template, determining whether the unavailable contract fulfiller is a worker in response to the task order template being a split task order template, updating the task order template as unavailable in response to the unavailable contract fulfiller being a worker, determining whether the worker is the only contract fulfiller for the corresponding task order template in response to the unavailable contract fulfiller being a worker, updating the corresponding task order template as unavailable in response to the worker being the only contract fulfiller for the corresponding task order template, and excluding the worker from the contract fulfillers of the corresponding task order template in response to the worker not being the only contract fulfiller for the corresponding task order template.

[0068] In some embodiments, the generation module 230 is further used to obtain drawing area information in response to the task order assignment entry information indicating that the task order assignment entry is a drawing entry, identify a reference task order based on the drawing area information, and identify a target task order based on the reference task order.

[0069] In some embodiments, the generation module 230 is further used to analyze the construction drawing, extract numeric information and alphabetic information in the construction drawing, identify an axis grid node set of the construction drawing based on the numeric information and alphabetic information, obtain a combination of target nodes in the axis grid node set, enclose a closed polygon by the combination of target nodes, and identify drawing area information based on the combination of target nodes.

[0070] In some embodiments, the generation module 230 further obtains an initial node combination input by a user, each node being a node within an axis grid node set, validates the initial node combination based on predetermined conditions including at least whether it encloses a unique closed polygon, identifies a valid node combination, obtains input information input by the user based on the valid node combination, and is used to identify a target node combination.

[0071] In some embodiments, the generation module 230 is further used to obtain the location information and initial coordinates of the node of the combination of the target node, determine the standard coordinates of the node based on the initial coordinates, and determine the reference task order based on the location information and the standard coordinates.

[0072] In some embodiments, the generation module 230 is further used to obtain user-entered progress unit information in response to the task order assignment entry information indicating that the task order assignment entry is a progress entry, identify a reference task order based on the progress unit information, and identify a target task order based on the reference task order.

[0073] In some embodiments, the generation module 230 is further used to, in response to the task order allocation entry information indicating that the task order allocation entry is a price management table entry, obtain list item information in the price management table cell entered by the user, identify a reference task order based on the list item information, and identify a target task order based on the reference task order.

[0074] For a detailed description of the above content, please refer to the corresponding descriptions of FIGS.

[0075] The above description of the task order processing system 200 and its modules is provided for convenience of explanation only, and the present specification is not intended to limit the scope of the illustrated embodiments. Those skilled in the art will understand that, after understanding the principles of the system, they can arbitrarily combine modules or connect them to other modules to form subsystems without departing from these principles. In some embodiments, the acquisition module 210, first identification module 220, second identification module 230, and third identification module 240 shown in FIG. 2 may be different modules in a single system, or a single module may fulfill the functions of two or more of the above modules. For example, each module may share a single storage module or each have its own storage module. All such variations are within the scope of protection of the present specification.

[0076] 3 is an exemplary flowchart of a task order processing method according to some embodiments of the present disclosure. As shown in FIG. 3, flow 300 includes the following steps. In some embodiments, one or more operations of flow 300 shown in FIG. 3 can be implemented in an application scenario 100 of a task order processing system. For example, flow 300 shown in FIG. 3 can be stored in a storage device in the form of instructions and invoked and / or executed by a processor. In some embodiments, flow 300 can also be executed by a processor.

[0077] Step 310: In response to a user initiating a task order creation operation for a construction project, identify task order assignment entry information.

[0078] The create task order operation refers to the operational instructions required for a user to create a task order. In some embodiments, a user can initiate the create task order operation via a user terminal. For more information about task orders, see step 330 and its associated description.

[0079] A task order assignment entry refers to a specific means by which a user initiates a task order. In some embodiments, task order assignment entries include dedicated entries, drawing entries, visual progress entries, and price management table entries. Dedicated entries are entries in the system interface designed specifically for task order assignment. Drawing entries are task order assignment entries provided when a user views construction drawings. Visual progress entries are task order assignment entries provided when a user views the visual progress (i.e., project progress status) of a construction project. Price management table entries are task order assignment entries provided when a user views a price management table (a table for managing costs and prices).

[0080] In some examples, the task order assignment entry may further include an input entry, which is an entry in a system interface specifically designed for a user to input information. A user may manually input relevant information, such as a task order assignment, through the input entry. For example, a user may input construction task and construction area information corresponding to a construction project through the input entry.

[0081] Task order assignment entry information refers to information related to a task order assignment entry, such as the type of task order assignment entry.

[0082] In some examples, in response to a user initiating a create source task order operation, the processor may identify the task order assignment entry information based on the interface the user is currently viewing and / or the interface through which the user is allocating the task order. For example, different interfaces may have corresponding identifiers, and the processor may identify the interface the user is currently viewing based on the identifier, thereby identifying the task order assignment entry information. As yet another example, task order allocation buttons in different interfaces may have corresponding identifiers, and the processor may identify the interface through which the user is allocating the task order based on the identifier, thereby identifying the task order assignment entry information. The identifiers are used to distinguish between different interface types and may be pre-populated by the system or pre-populated manually.

[0083] Step 320: Obtain related information based on the task order allocation entry information.

[0084] Related information refers to information about a task order assignment entry. Different task order assignment entries may correspond to the same or different types of related information. Related information may be obtained from the task order assignment entry. As an example, related information may be information included in an interface where the task order assignment entry is located. Related information may be information entered by a user into the task order assignment entry.

[0085] In some embodiments, when a user selects a specific task order assignment entry, the processor can determine the type of entry and automatically retrieve corresponding related information to more accurately generate the task order.

[0086] In some examples, if the type of the task order assignment entry is a dedicated entry, the corresponding associated information may consist of project information and user information.

[0087] User information refers to the identity document (ID) of any individual or group initiating the task order creation operation. For example, user information may be the name of the project's prime contractor, a subcontractor's unique code, the name of the team leader, etc.

[0088] Project information refers to information about construction projects. Construction projects refer to related projects based on engineering construction.

[0089] In some embodiments, the project information includes an identification of the associated project based on the engineering construction, such as the name of the project, a unique code for the project, etc.

[0090] In some embodiments, when a user 140 (e.g., a functional department manager) creates a construction project via a user terminal 130, project information for the construction project can be entered and stored in the storage device 120. For related descriptions of the user 140, the user terminal 130, and the storage device 120, reference can be made to the corresponding descriptions in FIG. 1 .

[0091] The construction area information refers to information related to a construction area included in a construction project. In some embodiments, the construction area information may indicate a construction area of ​​a construction project.

[0092] In some embodiments, the construction area may be a pre-divided area. In some embodiments, the construction area may be pre-divided into multiple levels, such as a primary construction area, a secondary construction area, and a tertiary construction area. The multiple levels may include a higher level and a lower level. For a certain construction area, the higher-level construction area may include at least one lower-level construction area. For example, if the primary construction area is Building 10096, the secondary construction area corresponding to the primary construction area may include Building 1, Floor 1, ..., Building 12, Floor 1. Correspondingly, a past primary construction area refers to a primary area corresponding to a past task order.

[0093] In some embodiments, the construction area may be pre-divided into multiple levels, etc. The multiple levels may include upper and lower levels, and for a given construction area, the construction area at the upper level may include at least one construction area at the lower level.

[0094] In some embodiments, a construction area may include a parent area and a child area. A parent area refers to an area corresponding to a higher level within the construction area. For example, a parent area is one building (e.g., Building 1, Building 2, etc.). A child area is an area corresponding to a lower level corresponding to a parent area. For example, if the parent area is Building 1, the child area corresponding to the parent area may include the first floor of Building 1, ..., the 12th floor of Building 1, etc. If the parent area is the 12th floor of Building 1, the child area corresponding to the parent area may include one unit on the 12th floor of Building 1, two units on the 12th floor of Building 1, etc. The parent area and the child areas corresponding to each parent area may be pre-divided areas.

[0095] In some examples, the acquisition module 210 may acquire project information for a construction project in various manners. For example, the acquisition module 210 may acquire pre-stored project information for a construction project via the storage device 120.

[0096] In some embodiments, when the type of the task order assignment entry is a drawing entry, the corresponding related information may be configured from an area corresponding to the drawing. For example, the corresponding related information may include drawing area information, task item range, etc. For details, see FIG. 7 and its related description.

[0097] In some embodiments, when the type of the task order assignment entry is a visual progress entry, the corresponding related information may consist of an area corresponding to a progress unit. For example, the corresponding related information may include progress unit information, task item range, etc. For details, see FIG. 8 and its related description.

[0098] In some examples, if the type of task order allocation entry is a price management table entry, the corresponding related information may be comprised of a list item in a price management list. For example, the corresponding related information may include list item information. For more information, see FIG. 9 and its related discussion.

[0099] Step 330: Generate a target task order based on the relevant information.

[0100] The target task order refers to the task order that is ultimately created after the user initiates the task order creation operation.

[0101] A task order refers to a document that records a list of tasks to be assigned to a contractor (e.g., a worker) to perform construction work. A task order may take various forms, such as a form or a list. In some examples, a task order may be a task list consisting of multiple construction tasks. In some examples, a task order may include specific content and general content for the construction tasks. The specific content may include sub-items such as task item, construction area, building shape, and interior layout. The general content may include sub-items such as contractor, construction period, construction volume, unit price, payment method, payment period, technical explanation, safety explanation, and precautions. For a description of the construction area, see the corresponding description in step 320. For a description of the planned construction period and contractor, see the corresponding description in FIG. 4.

[0102] A contract performer refers to a worker who performs a task item in a task order. In some examples, each contract performer may correspond to one or more trades, such as a rebar worker or a concrete worker. The trades can be used to match task information. Specifically, a trade includes at least one construction skill within that trade, and a worker belongs to the trade corresponding to the construction skill only if the worker possesses any of the construction skills. For example, if the trade is a rebar worker, the construction skills within that trade may include rebar rust removal, rebar straightening, rebar connection, etc. Since rebar rust removal, rebar straightening, and rebar connection cannot be further subdivided into lower-level construction skills, rebar rust removal, rebar straightening, and rebar connection each correspond to a lowest-level task item. In addition, some construction skills may have multiple levels, and the construction skill corresponding to the lowest level task item (the lowest level subtask item within a task item; the lowest level subtask item cannot be further subdivided) is the lowest level construction skill.

[0103] A task item refers to a specific construction task, such as pouring concrete. A technical description refers to the description of the technology required to complete a task item. A safety description refers to related description such as safety precautions that need to be taken into account in order to complete a task item. A pricing method refers to the method for specifying the relevant price of a construction project. A unit price refers to the price per unit amount (e.g., 1 ton, 1 square meter). A construction volume refers to the estimated total construction volume, such as several tons, several square meters, or several meters. A total amount refers to the total amount corresponding to an estimated task order. A payment period refers to the estimated time for which labor costs are paid to the contract performer.

[0104] Each sub-item in the task order includes corresponding specific content. For example, content corresponding to a task item in a sub-item may include rebar work, etc., and content corresponding to a contract performer in a sub-item may include the names of one or more contract performers.

[0105] In some embodiments, a task order may be divided into a source task order, a split task order, etc. A source task order refers to a task order without a higher-level task order, i.e., a task order with a parent-level task order of zero. A split task order refers to a task order split from a source task order, i.e., a task order with a non-zero parent-level task order. A parent level refers to a higher level, and a parent-level task order refers to a task order at a higher level. A parent-level task order of zero refers to a task order without a higher level. A task order with a non-zero parent-level task order refers to a task order with a higher level.

[0106] In some embodiments, a source task order may be assigned by a prime contractor to a subcontractor. A user may receive a source task order, split it into subtask orders, and further assign it to subordinates. For example, a source task order assigned by a prime contractor to a work group includes data for a total of 100,000 RMB for rebar work on the first floor of Building 1. A team leader may then assign the source task order to multiple subtask orders. For example, the first floor of Building 1 in the construction area may be divided into two units, and the task item rebar work may be divided into two parts: rebar fabrication and rebar installation. Group A completes the rebar fabrication for units 1 and 2, Group B completes the rebar installation for unit 1, and Group C completes the rebar installation for unit 2. The 100,000 RMB is then allocated to the team leader and three groups, A, B, and C, at an agreed price.

[0107] In some embodiments, after the processor obtains the relevant information, it can automatically generate a specific target task order based on the relevant information.

[0108] In some examples, if the task order assignment entry information indicates that the user selects to assign the task order via a "dedicated entry," the processor may identify a reference task order based on the target construction area information, and further generate a target task order based on the reference task order and the target construction area information. For details of such examples, see FIG. 4 and its associated description.

[0109] In some examples, if the task order assignment entry information indicates that the user selects to assign the task order via a "dedicated entry," the processor may identify a target task order template and a reference task order based on the user information of the user and project information of the task order to be created, and further generate the target task order based on the target task order template and the reference task order. For details of such examples, see FIG. 6 and its associated description.

[0110] In some embodiments, if the task order assignment entry information indicates that the user selects to assign the order via a "drawing entry," the processor may generate a target task order based on the drawing area information. For details of such embodiments, see FIG. 8 and its associated discussion.

[0111] In some embodiments, if the task order assignment entry information indicates that the user selects to assign the order via a "progress entry," the processor may generate a target task order based on the progress unit information. For details of such embodiments, see FIG. 9 and its associated discussion.

[0112] In some embodiments, if the task order allocation entry information indicates that the user selects to allocate the order via a "price management table entry," the processor may generate a target task order based on the listing information in the price management table cell. For details of such embodiments, see FIG. 10 and its associated discussion.

[0113] In some embodiments of the present specification, identifying a target task order as described above improves user convenience and allows users to directly initiate task order assignment when viewing construction drawings, schedules, and price management tables without leaving the current interface, thereby improving the accuracy and efficiency of task order creation. The processor automatically adapts related information acquisition and task order generation logic based on the specific task order assignment entry selected by the user, ensuring high consistency between the task order and the actual situation of the project.

[0114] In some other embodiments, the processor may identify the target task order by the following steps S11 to S14.

[0115] Step S11: Identify the reference task order.

[0116] For the method of identifying the reference task order, please refer to the related descriptions of Figures 4, 6, and 8.

[0117] Step S12: Generate an initial task based on the reference task order.

[0118] An initial task order refers to a task order that is generated by the processor after a user initiates a task order creation operation and has not yet been confirmed by the user. In some embodiments, the processor may directly copy a reference task order as the initial task order. In some embodiments, the processor may obtain the initial task order after adjusting the construction area in the reference task order as the target construction area.

[0119] Step S13: Obtain user input information for the initial task order.

[0120] The input information refers to information such as confirmation and correction of the initial task order entered by the user according to actual needs. Correction refers to modifying the content of the initial task order. For example, the user can delete the sub-item "Payment Information" by clicking the delete symbol in the sub-item "Payment Information." As another example, the user may manually modify the data information corresponding to the sub-item.

[0121] In some embodiments, the processor may control the display of the initial task order on a user terminal, and the user may review and modify content within the initial task order on the user terminal, thereby allowing the processor to obtain user input information for the initial task order via the user terminal.

[0122] Step S14: Identify a target task order based on the initial task order and the input information.

[0123] In some examples, in response to the input information being a confirmation of the initial task order, the processor may identify the initial task order as the target task order.

[0124] In some embodiments, in response to the input information being modification information for an initial task order, the processor may identify a target task order based on the modification information and the initial task order. For example, the processor may use the initial task order as a basis and modify the initial task order based on the modification information, thereby identifying the target task order. For example, if the modification information is to delete a subitem called "Payment Information," the processor may identify the target task order by deleting the subitem called "Payment Information" and its corresponding data in the initial task order. As yet another example, if the modification information is to modify "Unit Price" from a to b, the processor may identify the target task order by modifying the data corresponding to the subitem called "Unit Price" in the initial task order from a to b.

[0125] In some embodiments herein, the user may fine-tune the initial task order to make the resulting target task order more suited to the actual situation and better meet the user's needs.

[0126] It should be noted that the above description of the process for identifying a target task order is for illustrative and explanatory purposes only and is not intended to limit the scope of the present disclosure. Those skilled in the art may, under the guidance of this disclosure, make various modifications and variations to the process for identifying a target task order. These modifications and variations are still within the scope of this disclosure.

[0127] In some examples, if the initial task order is a source task order, in response to the input information satisfying a first condition, the processor may identify a new task order template based on the modification information and update the task order template library, where the input information is modification information and the modification information relates to a construction area, a task item, and / or a contract performer.

[0128] For example, if the initial task order is a source task order, in response to the input information satisfying a first condition, the processor can identify the target task order modified by the user as a new task order template in the task order template library, and the template use count corresponding to the task order template is 1.

[0129] In some examples, if the initial task order is a source task order, in response to the input information satisfying a second condition, the processor may update the number of uses of the task order template and the associated task order based on the modification information. The second condition refers to the input information being modification information and the modification information not relating to the construction area, task item, and contract performer.

[0130] For example, if the initial task order is a source task order, in response to the input information satisfying the second condition, the processor may increase the number of uses of the template corresponding to the target task order template by one and identify the target task order modified by the user as an associated task order of the target task order template.

[0131] In some examples, if the initial task order is a split task order, in response to the input information satisfying a third condition, the processor may identify a new task order template based on the modification information and update the task order template library, where the input information is modification information and the modification information relates to the number of subtasks, the construction task items of the subtasks, and / or the contract performers of the subtasks.

[0132] For example, if the initial task order is a split task order, in response to the input information satisfying the third condition, the processor can identify the target task order modified by the user as one new task order template in the task order template library, and the template use count corresponding to the task order template is 1.

[0133] In some examples, if the initial task order is a split task order, in response to the input information satisfying a fourth condition, the processor may update the number of uses of the task order template and the associated task order based on the modification information. The fourth condition refers to the input information being modification information, and the modification information not relating to the number of subtasks, the construction task items of the subtasks, and the contract performers of the subtasks.

[0134] For example, if the initial task order is a split task order, in response to the input information satisfying the fourth condition, the processor may increase the number of uses of the template corresponding to the target task order template by one and identify the target task order modified by the user as the associated task order of the target task order template.

[0135] In some embodiments, for a target task order identified by step 340 or a target task order identified by steps S11 to S14, and the input information is confirmation of the initial task order, the processor may increase the number of uses of the template corresponding to the target task order template by one, and identify the identified target task order as an associated task order of the target task order template.

[0136] In some embodiments herein, after each target task order is identified, the task order template library is updated. In response to the user initiating the next task order creation operation, the target task order can be identified based on the updated task order template library, thereby making the identified target task order more rational.

[0137] In some examples, after task order processing system 200 transmits the generated target task order to a user, task order processing system 200 may monitor the target task order to identify a task status of the target task order. For example, the task status of the target task order may include unassigned, completed, under construction, overdue, in adjustment work, etc.

[0138] In some embodiments, the task order processing system 200 may identify task states for a target task order by obtaining user input.

[0139] In some examples, the task order processing system 200 may represent different task states of a target task order with different colors on a construction drawing. In some examples, the task order processing system 200 may represent different task states of a target task order for different construction sites with different text descriptions on a construction drawing. As an example, FIG. 11 is an exemplary schematic diagram illustrating the allocation status of target task orders for different construction sites according to some examples herein. As shown in FIG. 11 , white areas 2 and 4 on a construction drawing indicate unassigned, dark area 1 indicates completed construction, and light areas 3 and 5 indicate ongoing construction.

[0140] 4 is an exemplary first flowchart for generating a target task order according to some embodiments of the present disclosure. As shown in FIG. 4, flow 400 includes the following steps. In some embodiments, one or more operations of flow 400 shown in FIG. 4 can be implemented in application scenario 100 of the task order processing system. For example, flow 400 shown in FIG. 4 can be stored in a storage device in the form of instructions and invoked and / or executed by a processor. In some embodiments, flow 400 can also be executed by a processor.

[0141] Step 410: In response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, obtain target construction area information including a target parent area and a target child area.

[0142] The target construction area information includes information related to the target construction area, such as the building number, floor number, and other spatial location of the target construction area.

[0143] The target construction area refers to the construction area associated with a task item in a task order. In some embodiments, the target construction area includes a target parent area and a target child area.

[0144] There is a correspondence between the target parent area and the target child area. For example, the target parent area refers to an area corresponding to a higher level within the target construction area, and the target child area refers to a construction area corresponding to at least one lower level of the target parent area. Different target parent areas correspond to at least one different target child area.

[0145] In some examples, in response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, the processor may identify the target construction area of ​​the construction project in various manners. For example, the processor may identify the target construction area in a predetermined manner based on past construction areas recorded in storage device 120. As yet another example, the processor may identify the target construction area by obtaining user input.

[0146] The predetermined method is a method for identifying a target construction area. As an example, the predetermined method includes the following steps: The processor may identify a target parent area according to the numerical order of the parent areas identified by the previous task order assignment based on the construction area of ​​the construction project identified by the previous task order assignment recorded in the storage device, and identify all corresponding lower-level areas as target child areas. For example, if the parent area identified by the previous task order assignment is Building 1, the child areas include each floor of Building 1, and the target parent area can be identified as Building 2, the target child areas may be identified as each floor of Building 2.

[0147] In some examples, the task order is a split task order. The processor may identify a target construction area of ​​the construction project based on the split task order and the source task order of the split task order. For example, the processor may identify an area at the same level as the target construction area based on the construction area identified by the split task order and the source task order of the split task order. That is, the processor may identify one or more parent areas related to the construction project corresponding to the split task order in the parent area identified by the source task order as target parent areas of the construction project, and further identify one or more child areas related to the construction project within the child area identified by the source task order of the split task order in the target parent area as target child areas.

[0148] For split task orders, the relevant content of the source task order can refer to FIG. 3 and its related description.

[0149] In some examples herein, since the construction area of ​​a split task order depends on the construction area of ​​the source task order, the target construction area can be identified based on the source task order of the split task order, thereby quickly identifying the construction area in the split task order and avoiding unnecessary manual repetitive entry.

[0150] In some examples, in response to the task order being a source task order, the processor may obtain user input information and obtain target construction area information from the input information.

[0151] User input information refers to related information about a construction project entered by a user. For example, user input information may include, but is not limited to, the project name, construction location, specific areas (parent and child areas), task type, scheduled start time, and scheduled end time. As another example, user input information may include related text content of a task order entered by a user on a user terminal, such as "The steel reinforcement work area is all floors of Building 1," or related options selected by a user on a user terminal, such as task items selected by the user.

[0152] In some examples, the processor may identify the target construction area of ​​the construction project based on the user's input information in various ways. For example, the processor may identify the target construction area by using a keyword extraction algorithm to extract keywords related to the construction area of ​​the task order based on the user's input information and matching them with the construction area information of the construction project.

[0153] For example, assuming that the construction area information indicates that Building 1 includes floors 1 to 10, and the relevant text content entered by the user is "The construction area for rebar work is all floors of Building 1," the processor may extract keywords such as "rebar work," "construction area," "Building 1," and "all floors," match them with the construction area information, and identify the target parent area corresponding to the rebar work of the task order as Building 1, and identify the target child area as all floors of Building 1, i.e., floors 1 to 10 of Building 1.

[0154] In some examples herein, the target construction area of ​​a construction project may be identified based on user input information, thereby identifying the target construction area according to the actual needs of the user when creating a source task order.

[0155] In some examples, in response to the task order being a source task order, the processor may obtain user information of the user and identify target construction area information based on the user information and project information of the construction project. For more information about the user information and project information, see step 320 and its associated description.

[0156] In some embodiments, in response to a user initiating a source task order creation operation, the processor may acquire user information and acquire project information based on the user's input. For example, if the user who initiated the source task order creation operation logs in to the system, the processor may acquire a user ID as user information. After the user accesses a functional module through input on a user terminal, the processor may acquire a project ID in which the functional module is located as project information.

[0157] In some embodiments, in response to a user initiating a split task order creation operation, the processor may acquire user information and identify project information based on the task order to be split. For example, if the user who initiated the split task order creation operation logs in to the system, the processor may acquire a user ID as user information. The processor may acquire a project ID corresponding to the parent-level task order as project information based on the task order to be split (i.e., the parent-level task order). It can be understood that the parent-level contract fulfiller corresponding to the parent-level task order and the user who initiated the split task order creation operation are the same.

[0158] In some examples, the processor may combine user information with project information to identify an optimal construction area as the target construction area for the task order.

[0159] In some embodiments, in response to the task order being a source task order, the processor may retrieve past task orders assigned by a user. Based on the past task orders, the processor may determine the task order assignment period, child area, and last task order assignment time for each task item in each parent area. Based on the last task order assignment time and the task order assignment period, the processor may identify a task order assignment pool that includes tasks to be assigned in each parent area within a predetermined time range (first time range). The processor may sort the task orders to be assigned in the task order assignment pool according to time and execution area, and identify a target execution area based on the sorting result and the child area.

[0160] A past task order refers to a task order that a user has created and assigned in the past. In some embodiments, a past task order may be a task order that a user has created and assigned within a predetermined past period. The length of the predetermined past period may be preset according to actual needs.

[0161] In some examples, the processor may obtain past task orders assigned by the user in various ways, for example, the processor may obtain, via a storage device, past task orders assigned by the user within a predetermined past period and previously stored.

[0162] The task order assignment cycle is data that indicates the task order assignment rules for different types of task items in each parent area. For example, the task order assignment cycle may include the assignment of one rebar work task item every seven days and one brickwork task item every six days in each building.

[0163] The target task order allocation time refers to the task order allocation time that corresponds to the task order closest to the current time point, corresponding to each different type of task item in the past task orders in each parent area. For example, if the current time point is March 30th and the recent allocation times for task orders in parent area A whose task item is rebar work are March 11th, March 18th, and March 25th, the target task order allocation time will be March 25th, which is the date closest to the current date.

[0164] In some embodiments, the processor may use various methods to determine the task order allocation period, child area, and target task order allocation time for task items in task orders in each parent area based on past task orders. For example, the processor may collect statistics on the number of days between task order allocations for task orders corresponding to different task items in different parent areas based on the task order allocation times for past task orders in each parent area, and determine the task order allocation period for task items in the parent area based on the statistical results. As an example, the average or most frequent number of days between order allocations for task orders corresponding to task item A in parent area B in past task orders may be used as the task order allocation period for task item A in parent area B.

[0165] In some embodiments, the processor may identify each child area associated with a past task order of each parent area based on the past task order of each parent area in the past task order. For example, the processor may extract content corresponding to an area field in the past task order of each parent area to identify the child area associated with each parent area.

[0166] In some examples, the processor may identify, for the past task orders, the task order assignment time of one past task order that is closest to the current time point and that corresponds to a different type of task item in each parent area based on the task order assignment times of the past task orders in each parent area, and identify the task order assignment time as the target task order assignment time. For example, if the past task orders include task orders A1 and A2 for rebar work in parent area A, the current time point is March 19, the task order assignment time corresponding to A1 is March 10, and the task order assignment time corresponding to A2 is March 16, the first identification module 220 may identify the target task order assignment time corresponding to the task item in parent area A being rebar work as March 16.

[0167] The task order allocation pool refers to the collection of task orders that may or may not be allocated around the current time.

[0168] In some examples, the task order allocation pool may include task orders to be assigned in each parent area within a first time range. The predetermined time range (i.e., the first time range) is a predetermined range of task order allocation times corresponding to the task order allocation pool, and may be, for example, within three days (yesterday, today, and tomorrow). The first time range may be predetermined. The task orders to be assigned refer to task orders that are assigned or not assigned within the first time range.

[0169] In some examples, the processor may identify the task order allocation pool in various ways based on the target task order allocation time and the task order allocation period. For example, the processor may identify the next task order and task order allocation time of the task item based on the target task order allocation time and the task order allocation period of the corresponding type of task order, and add task orders in the parent area whose task order allocation time is within a first time range to the task order allocation pool as task orders to be assigned.

[0170] The sorting result refers to the result of sorting the task orders to be assigned.

[0171] In some examples, the processor may determine the sorted results of the assigned task orders in various manners. For example, the processor may sort the assigned task orders based on time and construction area, e.g., first sorting based on task order assignment time and then sorting based on construction area, and then determining the sorted results.

[0172] As an example, assuming that the construction areas of the task orders to be assigned include rebar work in Building 2 that was scheduled to be assigned yesterday, rebar work in Building 1 that was scheduled to be assigned yesterday, and brick work in Building 1 that is scheduled to be assigned today, after sorting the task orders to be assigned in chronological order by yesterday, today, and tomorrow, and in order of the construction areas of Buildings 1 and 2, the sorting results will be rebar work in Building 1 that was scheduled to be assigned yesterday, rebar work in Building 2 that was scheduled to be assigned yesterday, and brick work in Building 1 that is scheduled to be assigned today.

[0173] In some examples, the processor may identify the target construction area of ​​the construction project based on the sorted result and the child areas in various ways. For example, the processor may identify the target construction area based on the correspondence between the type of task item of the top-level task order to be assigned and the number of child areas in the sorted result.

[0174] As an example, the top-ranked task order to be assigned in the sorted results is a rebar work scheduled to be assigned yesterday, and the processor may identify the parent area corresponding to the task order to be assigned as the target parent area. If the child area assigned by the task order to be assigned is the 22nd floor, the target child area for the corresponding future (i.e., next) task order assignment for the rebar work may be the 23rd floor. If the child areas assigned by the task order to be assigned are the 10th and 11th floors, the target child areas for the corresponding future (i.e., next) task order assignment for the rebar work may be the 12th and 13th floors.

[0175] In some embodiments of the present specification, a task order allocation pool is identified, and task orders to be assigned in the task order allocation pool are sorted to identify a target construction area of ​​a construction project. If there is no higher-level document in the source task order, the priority of the construction project is identified based on the sorting result of the task orders to be assigned, and the target construction area to which task orders will be assigned in the future (i.e., next) is more intelligently and accurately predicted based on past data, which can subsequently make it easier to identify a more reasonable reference task order, improve work efficiency, and enhance the user experience.

[0176] In some embodiments, after identifying the target construction area, the processor may acquire the target construction area information in various ways. For example, the processor may acquire pre-stored information related to the target construction area via a storage device.

[0177] Step 420: Identify the target past task order assigned by the user based on the target origin area.

[0178] A target past task order refers to a past task order that is used as a reference when identifying a task order. In some examples, there may be multiple target past task orders, and different task items may correspond to different target past task orders.

[0179] In some embodiments, the processor may identify the target past task order in various ways based on the target parent area. For example, the processor may identify the target past task order corresponding to a different task item assigned by the user based on the content of a field corresponding to the task item in the past task order based on the past task orders in the target parent area whose creation time falls within a predetermined period. The predetermined period refers to a period close to the current time, such as within two days or within one week, and may be set according to actual needs.

[0180] In some embodiments, if the task order is a source task order, the processor may obtain at least one past source task order of the user in a second time range in the target parent area, identify a second sorted result of the at least one past source task order, and identify the target past task order based on the second sorted result.

[0181] A past source task order refers to a source task order that was previously created and assigned by a user.

[0182] The predetermined period (hereinafter also referred to as the second time range) is a predetermined time range for obtaining past source task orders, and may be set according to actual needs. For example, the second time range may be within the past three months or within six months from the current time point.

[0183] In some embodiments, the processor may retrieve at least one past source task order of the user within the second time range in the destination origin area in various manners. For example, the processor may retrieve, via a storage device, all past source task orders assigned by the user and pre-stored in the processor at the time of creation in one or more destination origin areas.

[0184] The first sorting result refers to the result of sorting past source task orders.

[0185] In some embodiments, the processor may identify the first sorted result of at least one past-source task order in various manners. For example, the processor may sort the past-source task orders in the target parent area in the second time range in reverse order of creation time to identify the first sorted result of all past-source task orders.

[0186] As an example, if the creation times of past source task orders in the second time range in the target parent area are March 10, March 11, and March 13, the processor can sort the corresponding past source task orders in the order of creation times March 13, March 11, and March 10 as the first sorting result.

[0187] In some embodiments, the processor may identify the target past task order based on the first sorting result in various ways.

[0188] In some embodiments, the processor may identify the target past task order based on the past sub-items included in the past source task order by the following steps S21 to S24.

[0189] Step S21: The past source task order ranked first in the first sorting result is set as the first candidate task order.

[0190] Step S22: Compare the past sub-items included in the second-ranked past source task order with the past sub-items included in the first candidate task order.

[0191] If the past sub-items of both do not match perfectly, the processor selects the past source task order with the second highest priority as the second candidate task order.

[0192] If the past sub-items of both are a perfect match, the processor excludes the past source task order with the second highest priority, then compares the past sub-items included in the past source task order with the past sub-items included in the first candidate task order, and if the past sub-items of both are not a perfect match, the processor sets the past source task order with the third highest priority as the second candidate task order, and continues processing in this manner.

[0193] Step S23: If the past source task order that is the second candidate task order is a past source task order with the pth rank, then the past sub-items included in the past source task order with the p+1th rank are compared with the past sub-items included in the first candidate task order and the second candidate task order, respectively.

[0194] If the past sub-items of both do not match completely, the processor selects the past source task order in the p+1th place as the third candidate task order.

[0195] If there is an exact match with the past sub-item of any of the candidate task orders, the processor excludes the past source task order in the p+1th order, then compares the past sub-item contained in the past source task order in the p+2th order with the past sub-items contained in the first candidate task order and the second candidate task order, respectively, and if there is no exact match with the past sub-items of either of the two, the processor selects the past source task order in the p+2th order as the third candidate task order and continues processing in this order.

[0196] Step 24: If the past source task order that is the third candidate task order is the qth past source task order, the past sub-items included in the q+1th past source task order, the q+2nd past source task order, ..., and the last past source task order are compared in order with the past sub-items included in at least one of the identified candidate task orders (e.g., the first candidate task order, the second candidate task order, the third candidate task order, etc.) according to the rules in steps S22 to S23 above, until n candidate task orders are identified. Note that n may be set according to actual needs, and as an example, the value of n may be 3 to 5.

[0197] A past sub-item refers to a sub-item included in a past source task order, which is similar to a sub-item included in a task order, and reference can be made to step 320 for a description of a task order and its sub-items.

[0198] A complete match between past sub-items means that the fields and corresponding contents of the past sub-items of two task orders are exactly the same. For example, if the past sub-items to be compared are task items, and the task item in the past source task order is rebar work and the task item in the first candidate task order is also rebar work, then the past sub-items included in the past source task order and the first candidate task order will be a complete match.

[0199] In some embodiments, the processor may identify the above n candidate task orders as the target past task orders.

[0200] In some embodiments, if the number of identified candidate task orders is less than n after the processor completes the comparison of all past source task orders within a predetermined time period in the target parent area through the above steps, the comparison range may be changed from all past source task orders within a second time range in the target parent area to all past source task orders in the construction project within a predetermined time period.

[0201] In some embodiments of the present specification, since source task orders assigned by the same user within a short period of time are usually similar, when creating a new source task order, different recent past source task orders can be referenced; by sorting the past source task orders assigned by the user and identifying a target past task order based on the sorting result, if the task order is a source task order, a past source task order with different sub-items can be identified as the target past task order, which then provides a more appropriate alternative means for identifying the reference task order, improves the efficiency with which users create source task orders, and enhances the user experience.

[0202] In some embodiments, if the task order is a split task order, the processor may obtain all split task orders of the user that have been accepted by the contract fulfiller in the target parent area within a predetermined period (hereinafter also referred to as a third time range), sort them by time, obtain a second sorted result, and identify the target past task order from the second sorted result.

[0203] The third time range is a predetermined time range in which the contract fulfiller accepts the split task order and may be set according to actual needs. For example, the third time range may be within six months from the current time. For related descriptions of the contract fulfiller, please refer to the corresponding descriptions in Figure 3.

[0204] In some embodiments, the processor may retrieve the user's split task orders in the target parent area in various manners. For example, the processor may retrieve, via the storage device, all of the user's split task orders that have been accepted by the contract fulfiller in the target parent area during a third time range and that have been pre-stored.

[0205] The second sorting result refers to the result of sorting multiple split task orders.

[0206] In some embodiments, the processor may identify the second sorted result of all split task orders accepted by the contract fulfiller within the third time range in various ways. For example, the processor may sort all split task orders accepted by the contract fulfiller within the third time range in reverse order of the time at which the contract fulfiller accepted the split task orders, thereby identifying the second sorted result of all past split task orders. The specific sorting method is similar to the method for identifying the first sorted result, and reference may be made to the related description above.

[0207] In some embodiments, the processor may identify the target past task order based on the second sorting result in various ways. For example, the processor may identify the target past task order corresponding to the split task order based on the second sorting result by the following steps S31 to S32.

[0208] Step S31: The processor compares the past sub-items included in the past divided task order with the sub-items included in the divided task order in question.

[0209] If there is a perfect match, the processor may determine that the past divided task order with the first priority is the first similar task order.

[0210] If there is no perfect match, the processor may exclude the past divided task order with the first priority, then compare the past sub-items included in the past divided task order with the sub-items of the divided task order, and if there is a perfect match, the processor may set the past divided task order with the second priority as the second similar task order.If there is no perfect match, the processor may exclude the past divided task order with the second priority, and continue processing in this manner.

[0211] Step S32: Repeat according to the above rule until m similar task orders are identified, where m may be set according to actual needs, and for example, the value of m may be 3 to 5.

[0212] In some embodiments, the processor may identify the identified m similar task orders as target past task orders.

[0213] In some embodiments, if the number of similar task orders identified above is less than m, the processor may select past split task orders as candidates whose past sub-items include sub-items that correspond to the split task order and have more past sub-items than the split task order by up to a predetermined number, and may randomly select past split task orders as similar task orders from the candidate past split task orders until m similar task orders are identified.

[0214] That is, past split task orders with fewer sub-items than the split task order and past split task orders with a predetermined number of past sub-items more than the sub-items included in the split task order are both excluded from the scope of the split task order. The predetermined number may be set according to actual needs, and as an example, the predetermined number may be 2.

[0215] In some embodiments of the present specification, split task orders assigned by the same user within a short period of time are usually similar, and therefore split task orders with similar sub-items often do not require significant changes when they are created. By sorting multiple past split task orders and identifying multiple target past task orders with the same number as the sub-items of the split task order, and / or identifying a number of target past task orders that is within a predetermined number of the number of sub-item contents of the split task order, if the task order is a split task order, a more appropriate alternative can be provided for subsequently identifying a reference task order, improving the efficiency with which users create split task orders and improving the user experience.

[0216] Step 430: Identify a reference task order based on the target past task order and the target child area.

[0217] A reference task order refers to a task order used as a reference by a user.

[0218] 5 is an exemplary schematic diagram illustrating the identification of a reference task order according to some embodiments of the present specification. As shown in FIG. 5, the reference task order includes data corresponding to fields such as a reference area, a reference task item, a reference planned construction period, a reference contract performer, a reference technical description, a reference safety description, a reference pricing method, a reference unit price, a reference construction quantity, a reference total amount, and a reference payment period. The format and included field contents of the reference task order are similar to those of a task order, and references to the corresponding descriptions of the task order in step 330 above can be referred to. For details about the reference task order, reference can be made to the related descriptions below.

[0219] In some embodiments, the processor may identify one or more reference task orders based on the target past task order and the target child area in various ways.

[0220] For example, the processor may directly identify target past task orders as reference task orders, where the number of reference task orders matches the number of target past task orders.

[0221] As yet another example, the processor may, based on the target past task order, the target child area, and the reference planned construction period, replace the child area in the target past task order with the target child area (i.e., generate a reference area for the reference task order) using the target child area and the reference planned construction period, replace the past planned construction period with the reference planned construction period, and the remaining information (e.g., task item, technical description, safety description, pricing method, contract performer, etc.) is the same as the corresponding information in the target past task order without any changes, and the contract performer is personnel excluding retired personnel, and the replaced target past task order may become the reference task order. For details about the reference planned construction period, please refer to the related description below.

[0222] In some embodiments, as shown in the central frame of FIG. 5A , when the number of reference past task orders is relatively large, the task order processing system 200 may recommend similar target past task orders according to the user's task order allocation rules and past task order entry rules, and automatically enter or update data for each sub-item in the reference task order. For example, the automatically filled-in range of the reference task order in the central frame includes data corresponding to fields such as the reference task item, reference planned construction period, reference contract performer, reference technical description, reference safety description, reference pricing method, reference unit price, reference construction quantity, reference total amount, and reference payment period (i.e., the check mark portion in the central frame of FIG. 5A ), thereby identifying the reference task order. Other information in the reference task order (e.g., the reference area) (i.e., the cross mark portion in the central frame of FIG. 5A ) can be entered by the user via a user terminal according to actual needs, thereby generating and initiating a task order.

[0223] In some embodiments of the present specification, by identifying a target past task order based on a past task order and identifying a reference task order, the content of the task order can be reasonably predicted, the efficiency of task order generation can be improved, and work efficiency can be thereby improved.

[0224] In some examples, if the target past task order is sufficiently large (e.g., the number of task orders exceeds a set quantity threshold), the processor may set the target construction area as the reference area for the reference task order. The processor may automatically fill in or update data for each sub-item in the reference task order according to the user's task order allocation rules and past task order entry rules. For example, the automatically filled ranges for the reference task order in the right frame may include corresponding contents such as the reference area, reference task item, reference planned construction period, reference contract performer, reference technical description, reference safety description, reference pricing method, reference unit price, reference construction quantity, reference total amount, and reference payment period (i.e., the check mark portions in the right frame in FIG. 5A ).

[0225] When there are a sufficient number of target past task orders, the task order processing system 200 can more intelligently and accurately predict the content of future task orders, realize one-click input of reference task orders, improve the efficiency of task order generation, and thereby improve work efficiency.

[0226] In some examples, the reference task order may include a reference planned construction duration, and if the task order is a source task order, the processor may identify the reference planned construction duration based on the past planned construction duration of the target past task order.

[0227] The reference planned construction duration refers to the scheduled construction time of the task items in the reference task order. In some examples, the reference planned construction duration may include the planned start time and planned finish time of the task items in the task order.

[0228] The past planned construction duration refers to the actual construction time of the task items in the target past task order. In some examples, the past planned construction duration may include the planned start time and the planned end time of the task items in the target past task order. In some examples, the processor may obtain the past planned construction duration of the target past task order via a storage device.

[0229] In some examples, the processor may determine the reference planned construction duration based on the past planned construction duration of the target past task order in various ways. For example, the processor may determine the reference planned construction duration based on the past planned construction duration and creation time of the target past task order and the creation time of the reference task order, by the relationship between the past planned construction duration and creation time of the target past task order.

[0230] As an example, the processor may determine the reference planned construction period based on the difference between the past planned construction period and the creation time and the creation time of the reference task order, and determine the planned start time S1 and planned end time E1 of the reference task order using the following equations (1) and (2): S1=C1-(C2-S2) (1) E1=C1-(C2-E2) (2)

[0231] Here, C1 denotes the creation time of the reference task order, C2 denotes the creation time of the target past task order, S2 denotes the planned start time of the target past task order, and E2 denotes the planned end time of the target past task order. The above formula is based on the fact that the difference between the planned start / end time and creation time of the reference task order is the same as the difference between the planned start / end time and creation time of the target past task order, i.e., C1-S1 is the same as C2-S2, and C1-E1 is the same as C2-E2.

[0232] In some embodiments, the processor may obtain the creation time of the target past task order and the creation time of the reference task order via a storage device.

[0233] In some embodiments of the present specification, the reference planned construction period of the reference task order can be determined based on the past planned construction period of the target past task order, and the reference planned construction period of the reference task order can be determined according to the rules for determining the past planned construction period, so that the determined planned construction period can be more adapted to the actual situation and further improve the user experience.

[0234] In some examples, the reference task order includes a reference area and a reference planned construction period, and if the task order is a split task order, the processor may identify the reference area based on the target child area and identify the reference planned construction period based on the past planned construction period of the target past task order.

[0235] In some embodiments, the processor may identify the reference area based on the target child area in various ways. For example, the reference area of ​​the reference task order includes a reference parent area being the second floor and a reference child area being one unit on the second floor and two units on the second floor. Assuming that the target parent area corresponding to the split task order is the third floor and the target child area is one unit on the third floor and two units on the third floor, the reference parent area of ​​the reference area is replaced with the third floor of the target parent area, and the reference child area of ​​the reference area is replaced with one unit on the third floor and two units on the third floor of the target child area.

[0236] In some examples, when the task order is a split task order, the processor may determine the reference planned construction duration based on the past planned construction duration of the target past task order in various ways. For example, the processor may determine the reference planned construction duration based on the relationship between the past planned construction duration of the target past task order and the creation time using a method similar to Equation (1) or Equation (2).

[0237] In some embodiments of the present specification, by determining the reference planned construction period based on the past planned construction period of the target past task order, the reference planned construction period can be reasonably estimated based on the relationship between the past planned construction period of the divided task order and the creation time, thereby improving the accuracy and generation efficiency of the reference task order and reducing labor costs.

[0238] In some embodiments, the processor may generate a list of reference task orders and a reference sort based on the target past task order and the target child area, obtain a user-selected reference task order based on the list of reference task orders and the reference sort, and obtain a user-modified task order based on the user-selected reference task order.

[0239] A list of reference task orders refers to a list containing multiple reference task orders. Reference sorting refers to the sorting of reference task orders within a list of reference task orders.

[0240] In some embodiments, the processor may generate the list of reference task orders and the reference sort based on the target past task order and the target child area in various ways. For example, the processor may generate multiple reference task orders based on the target past task order and the target child area in the above manner and display the multiple reference task orders in the form of a list of reference task orders, thereby facilitating user selection. As another example, there may be a correspondence between the multiple target past task orders and the second or third sorted results, and there may be a correspondence between the target past task orders and the identified reference task orders, and the third identification module 240 may identify the second or third sorted result corresponding to the target past task order as the reference sort of the multiple reference task orders based on the correspondence.

[0241] In some embodiments, the processor may obtain a second past task order of the user within a fourth time range in the target parent area, identify past reference task orders and past modified task orders of the user based on the second past task order, and identify a list of reference task orders and a reference sort based on the past reference task orders and the past modified task orders.

[0242] The fourth time range refers to the time range of creation times of the past task orders to be obtained, and may be set according to actual needs. For example, the fourth time range may be within six months from the current time.

[0243] The second past task order refers to all past task orders of the user in the target parent area.

[0244] In some embodiments, the processor may obtain the second past task order of the user in the target parent area within the fourth time range in various manners, for example, the processor may obtain the second past task order of the user in the target parent area within the fourth time range, which is pre-stored, via a storage device.

[0245] The past reference task order refers to a reference task order that the user previously selected within the second past task order.

[0246] A past correction task order refers to a task order that is generated by a user by correcting a past reference task order in the second past task order.

[0247] In some examples, the processor may identify the user's reference task order and the modified task order based on the second past task order. For example, the processor may identify a task order that includes a modification record in the second past task order as the user's modified task order based on the modification record in the second past task order. As another example, the third identification module 240 may identify a reference task order selected by the user in the second past task order as the user's reference task order based on the selection record in the second past task order.

[0248] In some examples, the processor may identify the list of reference task orders based on the past reference task orders and the past modified task orders in various ways. For example, the processor may generate the list of reference task orders based on the past reference task orders and the past modified task orders that meet a predetermined condition, such as based on a record in which the past reference task order is selected by a user and a modification record of the past modified task order.

[0249] The predetermined condition refers to a condition for identifying a list of reference task orders. For example, the previously referenced task orders and previously modified task orders that satisfy the predetermined condition may include at least one of the following: previously referenced task orders whose number of modifications is greater than a first threshold; previously modified task orders whose number of modifications with the same modification content is greater than a second threshold; and previously referenced task orders whose number of selections by a user and no modifications is greater than a third threshold. The first, second, and third thresholds may be manually set in advance.

[0250] In some examples, when the list of reference task orders is identified based on past reference task orders and past modified task orders, the processor may generate the reference sort in various ways. For example, the processor may sort the reference task orders in the list of reference task orders based on the number of times they are modified and / or selected based on the selection records and modification records of the past reference task orders and past modified task orders in the list of reference task orders, for example, by performing a weighted sum on the number of times the reference task orders are selected and modified (where the weight of the number of times selected may be greater than the weight of the number of times modified), sorting the reference task orders in the list of reference task orders from high to low based on the result of the weighted sum, and identifying the sorted result as the reference sort.

[0251] In some embodiments of the present specification, by identifying a list of reference task orders and reference sorting based on past reference task orders and past modified task orders, a reference task order that the user wants to select or possible modifications to the reference task order are predicted based on the user's past selection habits and modification habits, and second past task orders that may be referenced are further screened, reducing task orders that may be abandoned, thereby generating a more reasonable list of reference task orders for the user to select, increasing the reference rate of task orders in the list of reference task orders, and further improving the user experience.

[0252] In some embodiments, the user may select, edit, modify, or discard a reference task order according to actual needs. For example, when a user creates a task order, the processor may cause a reference pop-up window including a list of reference task orders to be displayed on the user terminal, and the user may select, edit, modify, or discard a reference task order in the list of reference task orders in the pop-up window.

[0253] Editing refers to editing a sub-item included in the reference task order (e.g., deleting the sub-item "Reference Pricing Method"), and modifying refers to modifying the content corresponding to the sub-item. The user may close the reference pop-up window and manually enter the task order, etc. After the user performs the above related operations, the processor may obtain related content such as the selections and changes made by the user via the user terminal.

[0254] In some examples, the processor may retrieve a reference task order selected by a user based on a user's associated operation on the list of reference task orders. For example, the processor may retrieve a reference task order in the list of reference task orders selected by a user in a user pop-up window via a user terminal.

[0255] In some examples, after a user selects a reference task order, the user may manually modify the reference task order. For example, the user may change the reference child area in the reference task order from "1st Floor, 1 Unit" to "1st Floor, 2 Units" via a user terminal. The processor may obtain the user-modified task order based on the user-selected reference task order and the user's manual modifications.

[0256] In some embodiments of the present specification, by generating a list of reference task orders and a reference sort, various reference task orders can be provided for the user to select based on the target past task orders, thereby significantly reducing human and time costs.

[0257] In some embodiments of the present specification, by identifying a target construction area and a target past task order and identifying a reference task order, it is possible to obtain a reference task order that is relatively reasonable and more likely to be used by the user based on the rules used to create or assign task orders in the past, thereby reducing unnecessary analysis, reducing human and time costs, improving user work efficiency, and improving the user experience.

[0258] In some embodiments, the reference task order includes a reference contract performer, and in response to not obtaining a task order assigned by the user in the target parent area, the processor may obtain user input information including a range of contract performers for the construction project and task information, and match the reference contract performer based on the task information. For a related description of the contract performer, please refer to the corresponding description in FIG. 4.

[0259] The referenced contract performer refers to the data corresponding to the contract performer in the referenced task order.

[0260] For relevant descriptions of the target parent area, task order, and user input information, please refer to the corresponding descriptions in step 420 above, and for relevant descriptions of the construction project, please refer to the corresponding descriptions in step 410 above.

[0261] The range of contract performers refers to the range of contract performers that can be selected for the current reference task order. In some examples, different contract performers correspond to different trades, and the trades may correspond to task item types. For example, a user may pre-associate the trades of contract performers with task item types, such as associating a rebar worker in the trade type with a rebar worker in the task item type, and store the correspondence in a storage device.

[0262] Task information refers to information about a task item. In some embodiments, the task information may include a task item and a type of the task item. For a related description of the type of task item, see the corresponding description of step 420 above.

[0263] In some embodiments, the processor may acquire the range of contract performers for a construction project and the user's input information in various ways. For example, the processor may acquire the range of contract performers corresponding to a construction project from a storage device based on a correspondence between job titles and task item types via task items included in the construction project. For example, contract performers of job titles corresponding to task items included in at least one construction project are added to the range of contract performers. As another example, the processor may acquire the user's input information via a user terminal.

[0264] In some examples, the processor may match the reference contract performer based on the task information in various ways. For example, the processor may identify, based on the type of task item in the task information, a contract performer whose job title and task item type satisfy a matching condition within a range of contract performers as the reference contract performer for the reference task order.

[0265] The matching condition is a condition for matching a reference contract performer. For example, the matching condition may be that the job type of the contract performer includes a job type that corresponds to the type of task item of the task order.

[0266] In some examples, the processor may identify a contract performer from a past task order in the same construction area with a task item type that is the same as the task item type in the reference task order as the referenced contract performer in the reference task order.

[0267] In some embodiments, as shown in the left frame of FIG. 5A, if there are no previous task orders available for reference in the early stages of a project, the task order processing system 200 may match a reference contractor based on the contractor's job type and task information using the above method. The automatically filled-in scope of the reference task order in the left frame is the reference contractor (i.e., the check mark in the left frame of FIG. 5A). Other information in the reference task order (e.g., reference area, reference task item, reference planned construction period, reference technical description, reference safety description, reference pricing method, reference unit price, reference construction quantity, reference total amount, reference payment period, etc.) (i.e., the cross mark in the left frame of FIG. 5A) can be entered by the user through a user terminal according to actual needs, thereby generating and initiating a task order.

[0268] In some embodiments of the present specification, when a construction project is in the early stage of the project and has not obtained a task order assigned by a user in the target parent area, by matching a reference contract performer based on the information input by the user, it is possible to intelligently match a suitable contract performer for a task order containing different task items based on the job type of the contract performer, thereby improving the efficiency of task order generation and reducing time costs.

[0269] Step 440: Generate a target task order based on the reference task order and the target construction area information.

[0270] In some embodiments, the processor may generate a target task order based on the reference task order and the target construction area information in various ways. For example, the processor may construct a blank task order according to the format of the reference task order and fill in the target construction area information in the blank task order to obtain the target task order.

[0271] Some embodiments herein utilize reference task orders and target construction area information to generate accurate target task orders, and this design significantly improves the efficiency and accuracy of task order generation.

[0272] FIG. 5B is an example sequence diagram of a task order processing method according to some embodiments of the present disclosure.

[0273] In some embodiments, as shown in FIG. 5B , when a user needs to create or assign a task order, the user may first access a task order creation / task order division page via the user terminal 130 and enter work area information. For related user instructions, please refer to the corresponding description in FIG. 1. For related content of task orders and work area information, please refer to the corresponding description in FIG. 3.

[0274] In some embodiments, the task order processing system 200 may identify a target construction area based on construction area information. For example, the task order processing system 200 may identify a target past task order from past task orders through query and selection based on the target construction area, and return it to a pop-up window containing a list of reference task orders for selection by the user. For related descriptions of the target construction area, the target past task order, and the list of reference task orders, please refer to the corresponding descriptions in Figures 3 and 4.

[0275] In some embodiments, after the user selects a reference task order via the user terminal 130, the task order processing system 200 returns the reference task order to the Create Task Order / Split Task Order page, where the user can modify / edit the reference task order and thereby specify the final task order. For a related description of the reference task order, please refer to the corresponding description above. For more specific details, please refer to the related descriptions of Figures 3 and 4.

[0276] 6 is an exemplary second flowchart for generating a target task order according to some embodiments of the present disclosure. As shown in FIG. 6, flow 600 includes the following steps. In some embodiments, one or more operations of flow 600 shown in FIG. 6 can be implemented in application scenario 100 of the task order processing system. For example, flow 600 shown in FIG. 6 can be stored in a storage device in the form of instructions and can be invoked and / or executed by a processor. In some embodiments, flow 600 can also be executed by a processor.

[0277] Step 610: In response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, obtain user information of the user and project information of the task order to be created.

[0278] For details about user information and project information, please refer to Figures 3 and 4 and their associated descriptions.

[0279] Step 620: Identify a target task order template from a task order template library based on the user information and project information.

[0280] A task order template library refers to a set of task order templates and their characteristics. For example, a task order template library consists of task order templates and template usage counts. As another example, a task order template library consists of task order templates, template usage counts, and associated task orders. For descriptions of task order templates, template usage counts, and associated task orders, please refer to the corresponding descriptions below.

[0281] In some examples, before performing the method for processing construction task orders, it is necessary to first identify a task order template library, which may be identified in various ways. In some examples, the processor may identify the task order template library based on steps S41 to S42.

[0282] Step S41: Obtain past task orders.

[0283] A past task order refers to a task order created and assigned by a user in the past. In some examples, a past task order may be a task order created and assigned by a user within a predetermined past period. The length of the predetermined past period may be preset according to actual needs. In some examples, the past task orders may be stored in a storage device.

[0284] In some examples, the past task orders may include a first past task order and a second past task order. The first past task order may be a source task order. The second past task order may be a split task order. For a description of task orders, source task orders, and split task orders, see Figures 3 and 4 and their associated discussion.

[0285] In some embodiments, the past task order may include past user information and past project information.

[0286] Past user information refers to the ID of the person or group who initiated the past task order creation operation. If the past task order is a first past task order, the past user information is the task order creator of the source task order. If the past task order is a second past task order, the past user information is the contract fulfiller of the parent-level task order.

[0287] Past project information refers to the ID of the project corresponding to the past task order.

[0288] In some examples, the processor may acquire past task orders in various ways. For example, the processor may acquire all past task orders assigned by a user during a predetermined past period and stored in advance via a storage device. In some examples, if the past task order is a first past task order, the past task order may include past task orders whose parent-level task orders are zero. In some examples, if the past task order is a second past task order, the past task order may include past task orders whose parent-level task orders are not zero. For descriptions of when the parent-level task order is zero and when the parent-level task order is not zero, please refer to the corresponding descriptions above.

[0289] In some examples, the processor may verify the validity of the initial past task orders, filter out invalid task orders from the initial past task orders, and identify past task orders.

[0290] The initial past task orders refer to past task orders that have not been screened for validity. For example, the initial past task orders may be all past task orders assigned by a user in a predetermined past period that are pre-stored in a storage device.

[0291] A valid task order is a task order that can be used to identify a task order template library.

[0292] In some examples, if the past task order is the first past task order, the valid task orders may include past task orders with zero parent-level task orders and non-zero child-level task orders. The child level refers to a lower level, and the child-level task order refers to a task order at the lower level. The parent-level task order being zero and the child-level task order being non-zero indicates that there is no task order at the higher level, but there is a task order at the lower level.

[0293] In some examples, if the past task order is a second past task order, the valid task orders may include past task orders with a non-zero parent-level task order and a non-zero child-level task order. A non-zero parent-level task order and a non-zero child-level task order indicates that there is a higher-level task order and a lower-level task order.

[0294] In some examples, a valid task order may include a task order where the parent and child levels are verified and the fields are complete. In some examples, a valid task order may include a case where, after assigning or splitting a task order, a child level task order includes at least one attendance record, work record, or inspection record.

[0295] An invalid task order refers to a task order that cannot be used to identify a task order template library. In some examples, if the past task order is a first past task order, an invalid task order may include a past task order with a parent-level task order that is not zero. In some examples, if the past task order is a second past task order, an invalid task order may include a past task order with a parent-level task order that is zero or a child-level task order that is zero. A parent-level task order that is zero or a child-level task order that is zero refers to the absence of a higher-level task order or the absence of a lower-level task order.

[0296] In some examples, invalid task orders may include task orders where the upper and lower levels are not confirmed and / or the fields are complete. For example, invalid task orders may include task orders that are not assigned after being assigned or split, task orders that are assigned or split and assigned but then canceled, and task orders that are assigned or split and assigned but then have no recipient for a long time or are rejected.

[0297] In some examples, an invalid task order may include a child-level task order that does not have any attendance records, work records, or inspection records after the task order is assigned or split. For example, if a child-level task order does not have anyone at work for a long time after it is accepted at a lower level, i.e., it is only accepted but not performed, the task order is considered to have no reference value and should be deleted. Similarly, a task order with no long work records or inspection records is also considered an abnormal task order, has no reference value, and should be deleted.

[0298] In some examples, the processor may identify past task orders by verifying the validity of the initial past task orders and filtering out invalid task orders from the initial past task orders based on predetermined rules, which may be preset based on the characteristics of valid and invalid task orders described above.

[0299] Step S42: Identify a task order template library based on past task orders.

[0300] In some embodiments, the processor may identify a plurality of task order templates and corresponding usage counts of the templates based on past task orders, thereby identifying a task order template library.

[0301] In some embodiments, identifying the task order template library may include the following steps S51 to S55.

[0302] Step S51: Obtain past task orders. For details, please refer to step S41 and its related explanation.

[0303] Step S52: Divide the past task orders into a plurality of primary groups based on the past user information and the past project information.

[0304] The primary groups refer to multiple groups obtained by first classifying past task orders. For example, the primary groups may be multiple groups obtained by dividing past task orders based on past user information and past project information.

[0305] In some embodiments, in response to identifying the first task order template library, the processor may divide the first past task order into a plurality of primary groups based on the task order creator and past project information of the source task order. For example, the processor may divide the first past task order into a primary group in Zhang San's D project, a primary group in Zhang San's E project, and a primary group in Li Si's D project.

[0306] In some examples, in response to identifying the second task order template library, the processor may divide the second past task orders into a plurality of primary groups based on the contract performer and past project information of the parent-level task orders. For example, the processor may divide the second past task orders into a primary group where the contract performer of the parent-level task orders of the F project is Zhang San, a primary group where the contract performer of the parent-level task orders of the G project is Zhang San, and a primary group where the contract performer of the parent-level task orders of the F project is Li Si.

[0307] Step S53: For each of the plurality of primary groups, divide the past task orders corresponding to the primary group into a plurality of secondary groups based on the construction area, task items, and contract performers in the past task orders. For details of the construction area, task items, and contract performers, please refer to FIG. 3 and its related description.

[0308] The secondary groups refer to multiple groups obtained by further classifying the past task orders in each primary group.

[0309] In some examples, in response to identifying the first task order template library, for each of the plurality of primary groups, the processor may consolidate based on past primary construction area, past task item, and past contract performer, and consolidate into the same task order template if the above three fields in the first past task orders exactly match, thereby dividing the first past task orders in the primary group into a plurality of secondary groups.

[0310] For example, if the first past task orders in a primary group consist of four task orders: "Assign the rebar tying task to worker A for the first floor of building 1," "Assign the rebar tying task to worker A for the second floor of building 1," "Assign the rebar tying task to worker A for the third floor of building 1," and "Assign the concrete pouring task to worker A for the third floor of building 1," the processor may divide them into two secondary groups: "Assign the rebar tying task to worker A for building 1" and "Assign the concrete pouring task to worker A for building 1."

[0311] A past task item refers to a task item corresponding to a past task order. A past contract performer refers to a contract performer corresponding to a past task order.

[0312] In some embodiments, in response to identifying the second task order template library, for each of the plurality of primary groups, the processor may merge based on past parent level task items, past child level task items, and past child level contract performers, and merge into the same task order template if the above three fields in the second past task orders exactly match, thereby dividing the second past task orders in the primary group into a plurality of secondary groups.

[0313] For example, if the second past task orders in a primary group are three task orders: "parent-level task item rebar work, child-level task item rebar manufacturing, child-level contract performer Zhang San," "parent-level task item rebar work, child-level task item rebar manufacturing, child-level contract performer Li Si," and "parent-level task item rebar work, child-level task item rebar manufacturing, child-level contract performer Li Si," the processor may divide them into two secondary groups: "parent-level task item rebar work, child-level task item rebar manufacturing, child-level contract performer Zhang San" and "parent-level task item rebar work, child-level task item rebar manufacturing, child-level contract performer Li Si."

[0314] Step S54: For each of the plurality of secondary groups, a task order template and the number of times the corresponding template has been used are identified based on the past task orders corresponding to the secondary group.

[0315] In some embodiments, for each of the plurality of secondary groups, the processor may identify a past task order corresponding to the secondary group as a task order template, and identify the number of past task orders corresponding to the secondary group as the number of template uses of the task order template.

[0316] For example, if the first past task orders in a primary group consist of four task orders: "Assign the rebar tying task to worker A for the first floor of building 1," "Assign the rebar tying task to worker A for the second floor of building 1," "Assign the rebar tying task to worker A for the third floor of building 1," and "Assign the concrete pouring task to worker A for the third floor of building 1," the processor may identify the past task orders corresponding to "Assign the rebar tying task to worker A for building 1" and "Assign the concrete pouring task to worker A for building 1" as two task order templates, respectively, and the template usage counts of the two task order templates are three and one, respectively.

[0317] As another example, if the second past task orders in a certain primary group are three task orders: “parent-level task item Rebar Work, child-level task item Rebar Fabrication, child-level contract performer Zhang San,” “parent-level task item Rebar Work, child-level task item Rebar Fabrication, child-level contract performer Li Si,” and “parent-level task item Rebar Work, child-level task item Rebar Fabrication, child-level contract performer Li Si,” the processor may identify the past task orders corresponding to “parent-level task item Rebar Work, child-level task item Rebar Fabrication, child-level contract performer Zhang San” and “parent-level task item Rebar Work, child-level task item Rebar Fabrication, child-level contract performer Li Si” as two task order templates, respectively, and the template usage counts of the two task order templates are two and one, respectively.

[0318] In some embodiments, in response to identifying the first task order template library, for each of the multiple primary groups, the processor sorts the first past task orders in the primary group from front to back according to the task order creation time, and then compares the first past task order in the nth place with all previous task order templates in order, and if none of the ``past primary construction area, past task items, and past contract performers'' exactly match, the first past task order in the nth place becomes the next task order template, and if it exactly matches one of the ``past primary construction area, past task items, and past contract performers'' in all previous task order templates, the number of times the corresponding task order template has been used is increased by one, thereby integrating k independent task order templates.

[0319] For example, the processor sorts the first past task orders in the primary group from front to back according to the time the task orders were created, then designates the first past task order in the first order as the first task order template, compares the first past task order in the second order with the first task order template's "past primary construction area, past task items, and past contract performers," and if none of them match, designates the first past task order in the second order as the second task order template, then compares the first past task order in the third order with the first task order template and the second task order template in turn, and identifies the first past task order in the third order as the third task order template unless one of them matches completely in the "past primary construction area, past task items, and past contract performers." In this way, when identifying the first task order template library, the process of identifying task order templates and the number of times the corresponding templates have been used is the same as the process described above, and therefore will not be described again here.

[0320] Task items and contract fulfillers assigned by the same user within a short period of time are very similar, and the planned construction period and time difference between task order creation for the same task item are fairly stable. Furthermore, although task items may change, the relationship between task items and contract fulfillers is fairly stable, and the number of types of task items within a short period of time is not large. Therefore, it can be seen that the past task orders within the task order template identified by steps S41 to S43 have a certain degree of similarity.

[0321] Step S55: Identify a task order template library based on task order templates corresponding to multiple secondary groups and the number of times the templates are used.

[0322] In some embodiments, the processor may identify task order templates corresponding to multiple secondary groups and the number of times the templates are used as a task order template library.

[0323] In some embodiments, for each of the plurality of secondary groups, the processor may identify the most recent past task order in the secondary group as an associated task order of the task order template corresponding to the secondary group, and may identify a task order template library based on the task order templates corresponding to the plurality of secondary groups, the number of times the templates are used, and the associated task orders.

[0324] The related task order refers to the past task order with the highest reference accuracy among the past task orders corresponding to the secondary group. For example, the related task order may be the latest past task order among the past task orders corresponding to the secondary group. Since construction sites change significantly, the newer the task order is and the more it meets the recent conditions, the higher the reference accuracy.

[0325] In some examples, after identifying the task order template and the corresponding number of times the template has been used, the template is associated with the ID of the most recent task order (i.e., the ID of the related task order), and other data for the related task order can be queried based on the ID of the related task order.

[0326] In some embodiments, the processor may identify task order templates corresponding to multiple secondary groups, the number of times the templates are used, and the associated task orders as a task order template library.

[0327] In some embodiments of the present specification, by identifying a task order template library based on past task orders, when a user initiates a task order creation operation, the processor can identify a reasonable target task order based on the task order template library, thereby improving the efficiency of generating the target task order and improving work efficiency. In addition, because the task order template library is identified when it is not operational, problems such as being unable to generate a target task order due to insufficient computing power during actual use can be avoided.

[0328] In some examples, the processor may identify a target task order template from the task order template library in various ways based on user information and project information. For example, if the user is a project manager and the project is undergoing interior construction, the processor may select one task order template related to interior construction as the target task order template.

[0329] In some examples, the task order template library may include a first task order template library and a second task order template library.

[0330] The first task order template library is the source task order template library. For a description of source task orders, see FIG. 3 and its associated discussion. In some embodiments, in response to a user initiating a create source task order operation, the processor may identify a target task order template from the first task order template library, thereby identifying the target task order. Note that the source task order template library may also be referred to as a task order assignment template library, and the corresponding source task order template may also be referred to as a task order assignment template.

[0331] The second task order template library is a split task order template library. For a description of split task orders, see FIG. 3 and its associated description. In some embodiments, in response to a user initiating a split task order creation operation, the processor may identify a target task order template from the second task order template library, thereby identifying the target task order. Note that the split task order template library may also be referred to as a task order split template library, and the corresponding split task order template may also be referred to as a task order split template. For details on identifying task order templates, see the corresponding description above.

[0332] The target task order template refers to the task order template that is most similar to the task order to be created.

[0333] In some embodiments, in response to a user initiating a source task order creation operation, the processor may perform a match within a first task order template library based on user information and project information to identify a corresponding recommended template. The processor may then recommend to the user a plurality of task order templates corresponding to the recommended template in order of the most frequently used template among the plurality of task order templates or the most recently updated time of the plurality of task order templates. The processor may identify a target task order template based on the user's selection. The update time of a task order template refers to the time at which the template use count of each task order template changes. The recommended templates refer to a plurality of task order templates having the same task information and project information as the task order to be created.

[0334] In some examples, in response to a user initiating a source task order creation operation, the processor may perform matching within a first task order template library based on user information and project information to identify a corresponding recommended template.The processor may then sort the multiple task order templates corresponding to the recommended templates in descending order of the number of times the multiple task order templates have been used or in descending order of the most recent update time of the multiple task order templates.The processor may identify the task order template with the most frequent template use or the most recent update time of the multiple task order templates corresponding to the recommended templates as the target task order template.

[0335] In some examples, in response to a user initiating a split task order creation operation, the processor may match within a second task order template library based on the user information and the project information to identify a corresponding recommended template. The processor may then identify a parent-level task order of the task orders corresponding to the plurality of task order templates corresponding to the recommended template as a recommended parent-level task order.

[0336] For one recommended parent-level task order, the processor may determine whether the recommended parent-level task order satisfies a predetermined condition. In response to the recommended parent-level task order satisfying the predetermined condition, the processor may retain the task order corresponding to the recommended parent-level task order; if not, the processor may remove the task order corresponding to the recommended parent-level task order, thereby updating and obtaining multiple recommended templates corresponding to the group. Next, the processor may recommend the multiple task order templates to the user in descending order of the number of times the templates have been used or in descending order of the most recent update time of the multiple task order templates. The processor may identify a target task order template based on the user's selection.

[0337] In some examples, after obtaining a plurality of recommended templates corresponding to the group using the above method in response to a user initiating a source task order creation operation, the processor may sort the plurality of task order templates corresponding to the recommended templates in descending order of the number of times the template has been used or in descending order of the most recent update time of the plurality of task order templates.The processor may then identify, as a target task order template, the task order template with the most frequent template use or the most recent update time of the plurality of task order templates corresponding to the recommended templates.

[0338] The predetermined condition refers to a predetermined condition for determining whether the recommended parent-level task order and the parent-level task order of the task order to be created are similar. For example, the predetermined condition may be that the difference between the task items of the recommended parent-level task order and the parent-level task order of the task order to be created is less than a predetermined number. The predetermined number may be two, three, five, etc. The difference between the task items of the recommended parent-level task order and the parent-level task order of the task order to be created refers to the sum of the number of task items that are present in the task items of the recommended parent-level task order but not in the task items of the parent-level task order of the task order to be created, and the number of task items that are not present in the task items of the recommended parent-level task order but are present in the task items of the parent-level task order of the task order to be created.

[0339] In some examples, the processor may obtain the available state of the target task order template and adjust the available state of the target task order template. For more details, see FIG. 6 and its related discussion.

[0340] Step 630: Identify a reference task order based on the target task order template.

[0341] In some embodiments, as shown in Table 1 in step 640, in response to a user initiating a create source task order operation, the reference content of the reference task order may include the project, task order creator, primary construction area, construction tasks, contract performer, unit price, estimated quantity, and payment information.

[0342] In some embodiments, as shown in Table 2 in step 640, in response to a user initiating a create split task order operation, the referenced task order reference content may include the project, task order splitter, construction area, construction tasks, contract performer, unit price, estimated quantity, and payment information.

[0343] In some examples, if the task order template library includes a task order template, a number of uses of the template, and an associated task order, the processor may query the associated task order based on the target task order template and identify the associated task order as the reference task order.

[0344] In some embodiments, when the task order template library includes task order templates and the number of times the templates are used, the processor may obtain the most recent task order among the task orders corresponding to the target task order template based on a change in the number of times the target task order template is used in the task order template library, and identify the most recent task order as the reference task order. The change in the number of times the target task order template is used in the task order template library refers to a change in the number of times the template corresponding to the target task order template is used in the process of identifying the task order template library. The most recent task order refers to the task order corresponding to the time when the number of times the template is used was last changed.

[0345] Step 640: Identify a target task order based on the target task order template and the reference task order.

[0346] In some examples, in response to a user initiating a create source task order operation, the processor may retrieve all data from the task order fields of the reference task order. The processor may then retain data corresponding to the project, task order creator, primary construction area, construction tasks, contract performer, unit price, estimated quantity, and payment information in the reference task order, automatically import it into secondary areas according to a user selection, calculate the planned construction period, fill in the reference task order, and identify the updated reference task order as the target task order shown in Table 1.

[0347] In some examples, the duration of a construction task performed by a task order to be created may refer to the duration of the construction task performed based on the reference task order. That is, the difference between the planned start time and planned end time of the task order to be created is the same as the difference between the planned start time and planned end time of the reference task order. The processor may determine the planned construction duration of the task order to be created based on the task order creation time of the task order to be created, the task order creation time of the reference task order, the planned start time of the reference task order, and the planned end time of the reference task order.

[0348] For example, the processor may determine the planned start time S1 of the task order to be created and the planned end time E1 of the task order to be created according to equations (1) and (2). For equations (1) and (2), reference may be made to step 430 and the related description.

[0349] In some examples, in response to a user initiating a source task order creation operation, a processor may retrieve a blank template (i.e., including only task order fields and no tables of related data corresponding to the task order fields) corresponding to the target task order template and retrieve all data along with the task order fields of the reference task order. The processor may then fill in the blank template with data corresponding to the project, task order creator, primary construction area, construction tasks, contract performer, unit price, estimated quantity, and payment information in the reference task order. The processor may then automatically populate the secondary areas and calculate the planned construction duration according to the user's selection, and subsequently fill in the blank template, thereby identifying the target task order shown in Table 1.

[0350] When retaining or entering construction tasks, task items that are included in the reference task order but not included in the task order being created will not be retained. When retaining or entering contract performers, if a worker has left the site or if their job title does not match the task item, the worker will not be retained. [Table 1]

[0351] In some embodiments, the process for identifying a target task order when a user initiates a create source task order operation is similar to the process for identifying a target task order when a user initiates a create source task order operation and will not be repeated here.

[0352] It should be noted that the process for identifying the work area of ​​the target task order when a user initiates a create source task order operation is different from the process for identifying the work area of ​​the target task order when a user initiates a create source task order operation.

[0353] In response to a user initiating a create split task order operation, for a child-level task order, the processor may replace the construction area of ​​the reference task order at the same level with the construction area of ​​the task order to be created. For example, the reference task order may split the second floor into two child-level task orders: one unit on the second floor and two units on the second floor. The task order to be created may split the third floor into two subunits: one unit on the third floor and two units on the third floor. [Table 2]

[0354] In some embodiments, the processor may generate an initial task order based on the reference task order, obtain user input information for the initial task order, and identify a target task order based on the initial task order and the input information. For related descriptions of identifying the target task order, please refer to the corresponding descriptions in Figures 3 and 4.

[0355] In some embodiments of the present specification, the task order template library can more intelligently and accurately identify target task orders, realize one-click input of target task orders, improve the efficiency of generating target task orders, and improve work efficiency.

[0356] 7 is an exemplary third flowchart for generating a target task order according to some embodiments of the present disclosure. As shown in FIG. 7, flow 700 includes the following steps. In some embodiments, one or more operations of flow 700 shown in FIG. 7 can be implemented in application scenario 100 of the task order processing system. For example, flow 700 shown in FIG. 7 can be stored in a storage device in the form of instructions and can be invoked and / or executed by a processor. In some embodiments, flow 700 can also be executed by a processor.

[0357] Step 710: In response to the task order assignment entry information indicating that the task order assignment entry is a drawing entry, obtain drawing area information.

[0358] Drawing area information refers to information about the construction area included in the construction drawing. For example, the drawing area information may include building information, floor information, the area range selected for the construction drawing, and drawing size (e.g., length, width, area, etc.) of the construction project.

[0359] A construction drawing is a drawing used to guide the construction of a construction project. A construction drawing may include a graphical representation of the details required for construction, such as size, orientation, and technical parameters, as well as a graphical representation of the actual project object to be constructed.

[0360] In some examples, construction drawings may include architectural construction drawings, structural construction drawings, mechanical construction drawings, and the like.

[0361] In some examples, the construction drawing may include an axis grid. The axis grid is a planar grid that is made up of axis lines, axis numbers, and size marks. The axis grid information may include information about the axis lines, axis numbers, size marks, etc. The axis grid may be pre-drawn on the construction drawing by the designer involved.

[0362] In some embodiments, the axes in the construction drawing include horizontal and vertical axes, which form an axis grid, and the intersections of the horizontal and vertical axes are axis grid nodes. The horizontal axes are axes parallel to the horizontal axis of the reference coordinate system, and the vertical axes are axes parallel to the vertical axis of the reference coordinate system. The horizontal direction (i.e., the horizontal axis direction) of the reference coordinate system refers to the width direction of the building, and the vertical direction (i.e., the vertical axis direction) refers to the length direction of the building. For example, as shown in Figures 12A to 12C, the horizontal direction of the reference coordinate system may be the east-west direction on the construction drawing, and the vertical direction of the reference coordinate system may be the north-south direction on the construction drawing.

[0363] In some embodiments, the axes in the construction drawing further include corresponding axis numbers. For example, vertical axes are numbered, and different vertical axes correspond to different axis numbers (e.g., numbers 1, 2, 3, etc.). The axis numbers of the vertical axes are sequentially incremented by a predetermined number along a certain direction of the horizontal axis (e.g., due east on the construction drawing). The predetermined number may be a default value, an experience value, a user-entered value, etc. For example, the predetermined number may be 1. As another example, horizontal axes are numbered alphabetically, and different horizontal axes correspond to different axis numbers (e.g., letters a, b, c, etc.). The axis numbers of the horizontal axes increase alphabetically along a certain direction of the vertical axis (e.g., due north on the construction drawing).

[0364] If a user selects to initiate a task order via a "drawing entry," the processor identifies the type of this task order assignment entry and obtains the corresponding drawing area information. In some embodiments, the processor may analyze the construction drawing currently being viewed by the user to extract specific drawing area information therefrom. The processor may analyze the construction drawing in various ways.

[0365] In some examples, the processor may perform image recognition on the construction drawings to identify drawing information within the construction drawings using an image recognition algorithm or any other suitable algorithm, including, but not limited to, Tesseract OCR, Google Cloud Vision API, or Microsoft Azure Cognitive Services.

[0366] In some examples, the processor may identify drawing information for the construction drawings by processing the construction drawings through a machine learning model (e.g., a Convolutional Neural Networks (CNN) model).

[0367] In some embodiments, the drawing information may include both numeric and alphabetic information.

[0368] Numerical information refers to information about numbers on construction drawings. For example, the numerical information may include the axis number of a horizontal axis.

[0369] The alphabet information refers to information about the alphabet of the construction drawing. For example, the alphabet information may include the axis number of the vertical axis.

[0370] In some embodiments, the processor may identify the drawing area information through steps 711 to 714.

[0371] Step 711: Analyze the construction drawing and extract the numeric information and alphabet information in the construction drawing. For details of the analysis method, please refer to the above.

[0372] Step 712: Identify a set of axis grid nodes of the construction drawing based on the numeric information and alphabet information.

[0373] An axis grid node set is a set of axis grid nodes of a construction drawing. An axis grid node is an intersection between axis lines. In some embodiments, an axis grid node set includes at least one axis grid node.

[0374] In some embodiments, the drawing information analyzed by the processor may include line information, and the processor may, based on the line information in the drawing information, identify lines among the line information that are parallel to the horizontal axis direction of the reference coordinate system as horizontal axes, and identify lines among the line information that are parallel to the vertical axis direction of the reference coordinate system as vertical axes, and may identify at least one axis grid node based on the at least one horizontal axis and the at least one vertical axis, thereby obtaining an axis grid node set.

[0375] In some examples, the processor may identify a set of axis grid nodes for a construction drawing based on numeric and alphabetic information.

[0376] In some examples, the numerical information may include a numerical text and a numerical position corresponding to the numerical text, the numerical text indicating the axis number of the vertical axis, and the numerical position indicating the coordinate position of the vertical axis on the construction drawing.

[0377] In some examples, the alphabet information may include alphabet text and an alphabet position corresponding to the alphabet text, the alphabet text indicating the alphabet of the axis number of the horizontal axis, and the alphabet position indicating the coordinate position of the horizontal axis on the construction drawing.

[0378] In some embodiments, identifying an axis grid node set for the construction drawing based on the numeric information and alphabetic information includes identifying a first axis number in a first direction based on numeric text and numeric position, identifying a second axis number in a second direction perpendicular to the first direction based on alphabetic text and alphabetic position, and identifying an axis grid node set based on the first axis number and the second axis number.

[0379] The first direction refers to the direction of the horizontal axis of the reference coordinate system. As shown in Figures 12A to 12C, the first direction is due east on the construction drawings.

[0380] The first axis number refers to the axis number that constitutes the first axis line of the target axis grid. The first axis number may include axis numbers of multiple first axes identified along the first direction. For a description of the target axis grid and the first axis line, please refer to the description of step 720 below.

[0381] In some embodiments, the processor may arbitrarily select a starting number as the starting axis number, search for all numeric texts along the first direction of the construction drawing, starting from the numeric position corresponding to the starting number, and identify all the searched numeric texts together with the starting number as the first axis number. The starting number refers to the numeric text that is the starting axis number among all the numeric texts. For example, the starting number may be 1.

[0382] In some embodiments, the processor may obtain a first set of numbers along a first direction based on the numeric text, identify a target numeric set based on the number of numbers included in the first numeric set, and identify a first axis number based on the numeric text included in the target numeric set.

[0383] The first number set refers to a set consisting of multiple number texts searched along a first direction.

[0384] In some embodiments, the processor arbitrarily selects a starting number in the construction drawing as a starting axis number, and searches for numeric text along a first direction starting from a numeric position corresponding to the starting number. If there is no gap between the currently searched numeric text and the previous numeric text, the processor classifies the currently searched numeric text into a first numeric set corresponding to the starting number, and continues searching for the next numeric text, until there is a gap between the currently searched numeric text and the previous numeric text, at which point the search is stopped and the first numeric set corresponding to the starting number is obtained.

[0385] For example, if the numbering method for the vertical axis line is a method of sequentially adding a preset number, the existence of a gap between two number texts means that the two number texts are not consecutive, that is, the pitch between the two number texts is not equal to the preset number. For example, if the two number texts are 4 and 6 respectively, there will be a gap between the two number texts.

[0386] The processor may identify the first set of other starting numbers in the first direction in the above manner.

[0387] The target number set refers to the first number set that will ultimately be selected.

[0388] In some embodiments, the processor may sort the first number sets in descending order based on the number of numbers included in the first number sets, and identify the first number set with the first predetermined number sorted at the top as the target number set. The first predetermined number may be a system default value, an experience value, a manually preset value, or any other combination, and may be set according to actual needs.

[0389] For example, the processor may set the first predetermined number to 1, 2, etc. For example, if the first predetermined number is 2, the processor may specify the two first number sets sorted at the top as the target number sets. The first predetermined number may be other values, and is not limited thereto in this specification.

[0390] In some embodiments, for each target number set, the processor may identify all numeric texts included in the target number set as first axis numbers. As an example, FIG. 12A is an exemplary schematic diagram of a first axis number according to some embodiments of the present specification. As shown in FIG. 12A, dotted frame A and dotted frame B are searched target number sets, and all numeric texts included in each of the two target number sets are one first axis number.

[0391] The second direction refers to the direction of the vertical axis of the reference coordinate system. As shown in Figures 12A and 12B, the second direction is due north on the construction drawing.

[0392] The second axis number refers to the axis number that constitutes the second axis line of the target axis grid. The second axis number may include axis numbers of multiple second axes identified along the second direction. For a description of the target axis grid and the second axis line, please refer to the description of step 720 below.

[0393] In some embodiments, the processor may arbitrarily select a starting alphabet in the construction drawing as a starting axis number, and start from the alphabet position corresponding to the starting alphabet, search for all alphabet texts along the second direction of the construction drawing, and identify all searched alphabet texts together with the starting alphabet as a second axis number. The starting alphabet refers to the alphabet text that is the starting axis number in all alphabet texts. For example, the starting alphabet may be "a."

[0394] In some embodiments, the processor may obtain a first alphabet set along a second direction based on the alphabet text, identify a target alphabet set based on the number of alphabets in the first alphabet set, and identify a second axis number based on the alphabet text included in the target alphabet set.

[0395] The first alphabet set refers to a set consisting of multiple alphabetic texts searched along the second direction.

[0396] In some embodiments, the processor arbitrarily selects a starting alphabet in the construction drawing as a starting axis number, and searches for alphabet text along the second direction starting from the alphabet position corresponding to the selected alphabet. If there is no gap between the currently searched alphabet text and the previous alphabet text, the processor classifies the currently searched alphabet text into a first alphabet set corresponding to the starting alphabet, and continues searching for the next alphabet text, until there is a gap between the currently searched alphabet text and the previous alphabet text, at which point the search is stopped and the first alphabet set corresponding to the starting alphabet is obtained.

[0397] For example, if the numbering system of the axis numbers on the horizontal axis line changes alphabetically, the existence of a gap between two alphabetic texts means that the two alphabetic texts are not continuous, that is, the change between the two alphabetic texts does not follow the alphabetic change rules. For example, if the two alphabetic texts are a and c, respectively, there will be a gap between the two alphabetic texts.

[0398] The processor may identify the first alphabet set of other starting alphabets in the second direction in the above manner.

[0399] The target alphabet set refers to the first alphabet set that is ultimately selected.

[0400] In some embodiments, the processor may sort the first alphabet sets in descending order based on the number of alphabets included in the first alphabet sets, and identify a second predetermined number of the first alphabet sets sorted at the top as the target alphabet sets. The second predetermined number may be a system default value, an experience value, a manually preset value, or any other combination, and may be set according to actual needs. For example, the second predetermined number may be 1, 2, etc. For example, if the second predetermined number is 2, the processor may identify the two first alphabet sets sorted at the top as the target alphabet sets. The second predetermined number may be another value, and the present specification does not limit such a value.

[0401] In some embodiments, for each pair of target alphabet sets, the processor may identify all alphabet texts included in the target alphabet sets as second axis numbers. As an example, FIG. 12B is an exemplary schematic diagram of second axis numbers according to some embodiments of the present specification. As shown in FIG. 12B, dotted box C and dotted box D are searched target alphabet sets, and all alphabet texts included in each of the two target alphabet sets are one second axis number.

[0402] In some embodiments, the processor may identify at least one first axis line and at least one second axis line based on the first axis number and the second axis number, and may identify at least one axis grid node based on the at least one first axis line and the at least one second axis line to obtain an axis grid node set.

[0403] The first axis refers to an axis identified based on the first axis number. In some embodiments, for various first axis numbers, the processor may identify a straight line that passes through the numeric position of the numeric text corresponding to the first axis number and is perpendicular to the horizontal axis of the reference coordinate system, and identify the straight line as the first axis. For example, one first axis may be identified for each of the first axis numbers "1," "2," "3," etc.

[0404] The second axis refers to an axis identified based on the second axis number. In some embodiments, for various second axis numbers, the processor may identify a line that passes through the alphabet position where the alphabet text corresponding to the second axis number is located and is perpendicular to the vertical axis of the reference coordinate system, and identify the line as the second axis. For example, one second axis may be identified for each of the second axis numbers "a," "b," "c," etc.

[0405] The axis grid nodes may be identified in various ways. In some embodiments, for each of at least one first axis, the processor may identify an intersection of the first axis with at least one second axis and identify the intersection as an axis grid intersection. In some embodiments, for each of at least one second axis, the processor may identify an intersection of the second axis with at least one first axis and identify the intersection as an axis grid node.

[0406] In some embodiments, the processor may combine at least one axis grid node to identify an axis grid node set. For example, for each of at least one first axis line, the processor may place at least one axis grid node corresponding to the first axis line in the same column and arrange the second axis lines in ascending order of axis numbers to obtain at least one column of axis grid nodes. Furthermore, the processor may arrange the at least one column of axis grid nodes in ascending order of axis numbers of the first axis line to obtain a matrix-form axis grid node set.

[0407] In some embodiments, the axis grid node set may include at least one axis grid node and intersection information corresponding to the axis grid node.

[0408] The intersection information refers to information about the axis grid node. For example, the intersection information may include the coordinate position of the axis grid node on the construction drawing.

[0409] In some embodiments, the processor may identify at least one target axis line and intersection information of the at least one target axis line based on the first axis number and the second axis number, and identify an axis grid node set based on the at least one target axis line and the intersection information.

[0410] The target axis lines refer to the axis lines that make up the target axis grid. The target axis grid is an axis grid identified from the construction drawings. The target axis lines include a first axis line and a second axis line, where the first axis line is the vertical axis line of the target axis grid and the second axis line is the horizontal axis line of the target axis grid.

[0411] In some embodiments, the processor may connect two or more numeric texts with the same first axis number to axis lines to obtain at least one first axis line, connect two or more alphabetic texts with the same second axis number to axis lines to obtain at least one second axis line, and identify an intersection of the first axis line and the second axis line as an axis grid node. The processor may identify a coordinate position of the axis grid node on the construction drawing based on the numeric position of the axis grid node corresponding to the first axis number of the axis grid node and the alphabetic position corresponding to the second axis number, and identify it as intersection information. For example, the coordinate position of the axis grid intersection may be (numeric position, alphabetic position).

[0412] 12C is an exemplary schematic diagram of an axis grid according to some embodiments of the present disclosure. As shown in FIG. 12C, the processor may connect two numbers 1 to obtain one first axis line, connect two numbers 2 to obtain one first axis line, connect two numbers 3 to obtain one first axis line, ..., connect two numbers 6 to obtain one first axis line. Furthermore, the processor may connect two letters a to obtain one second axis line, connect two letters b to obtain one second axis line, connect two letters c to obtain one second axis line, and obtain an axis grid based on the first axis lines and the second axis lines, and identify intersections of the axis grid as axis grid nodes.

[0413] As shown in FIG. 12C , for axis grid node P, the processor may identify the coordinate position of axis grid node P on the construction drawing based on the numeric position of number 1 and the alphabetical position of alphabet c corresponding to axis grid node P, and identify it as the intersection information of axis grid node P.

[0414] In some embodiments, the processor may identify at least one axis grid node and the intersection information corresponding to each axis grid node as an axis grid node set.

[0415] In some embodiments, the axis grid node set may further include an axis number coordinate of a first axis number and an axis coordinate of a second axis number. The axis number coordinate of the first axis number refers to the coordinate of the first axis number corresponding to the first axis line on the horizontal axis of the construction drawing. For example, the axis number coordinate of the first axis number may be the horizontal axis coordinate of the first axis number corresponding to all numeric text on the first axis line, and the horizontal axis coordinate of the first axis number corresponding to all numeric text on the first axis line is the same. The axis number coordinate of the second axis number refers to the coordinate of the second axis number corresponding to the second axis line on the vertical axis of the construction drawing. For example, the axis number coordinate of the second axis number may be the vertical axis coordinate of the second axis number corresponding to all alphabetic text on the second axis line, and the vertical axis coordinate of the second axis number corresponding to all alphabetic text on the second axis line is the same.

[0416] In some embodiments, the processor may identify numeric positions of the first axis number corresponding to all numeric text on the first axis and identify horizontal axis coordinates within the numeric positions as axis number coordinates of the first axis number. In some embodiments, the processor may identify alphabet positions of the second axis number corresponding to all alphabet text on the second axis and identify vertical axis coordinates within the alphabet positions as axis number coordinates of the second axis number.

[0417] Step 713: Obtain a combination of goal nodes in the axis grid node set, and the combination of goal nodes encloses a closed polygon.

[0418] A combination of target nodes refers to a combination of multiple axis grid nodes that constructs a construction area. In some embodiments, the combination of target nodes can enclose a closed polygon, which constitutes a contoured construction area or contoured construction site. That is, multiple axis grid nodes of a combination of target nodes can enclose a closed polygon. For example, a closed polygon such as a square or a rectangle can be enclosed. The enclosing refers to a shape enclosed by grid lines corresponding to multiple axis grid nodes. A grid line is a partial axis line between two axis grid nodes.

[0419] In some embodiments, the processor may identify a closed polygon enclosed by a combination of goal nodes as a construction site corresponding to the combination of goal nodes. In some embodiments, the processor may identify a plurality of combinations of goal nodes, and a union of the construction sites corresponding to the plurality of combinations of goal nodes may completely cover or partially cover all construction areas of the construction drawing.

[0420] In some embodiments, the processor may display the axis grid node set to a user via a display device, obtain at least one axis grid node selected by the user from the axis grid node set, and identify a combination of axis grid nodes selected by the user that can enclose a closed polygon as a target node combination.

[0421] In some embodiments, the processor may identify the combination of target nodes by the following steps S61 to S63.

[0422] Step S61: The combination of initial nodes input by the user is obtained.

[0423] The initial node combination refers to the combination of nodes initially selected by the user. Each node in the initial node combination is an axis grid node in the axis grid node set.

[0424] In some embodiments, the processor may display the axis grid node set to the user via a display device, and the user may select at least one axis grid node from the axis grid node set to configure the initial node combination. In some embodiments, the processor may obtain a coordinate position of the at least one axis grid node input by the user, and identify the axis grid node corresponding to the coordinate position as a node in the initial node combination. It can be understood that, in order for the nodes in the initial node combination to enclose a closed polygon, the number of at least one axis grid node selected or input by the user must be three or more, and they must not be located on the same straight line.

[0425] Step S62: Verify the initial node combination based on a predetermined condition to identify an eligible node combination.

[0426] An eligible node combination refers to a combination of initial nodes that meets a predetermined condition.

[0427] In some embodiments, the predetermined condition may include whether the combination of the initial nodes can enclose a closed polygon. For details about enclosing a closed polygon, please refer to the related description above.

[0428] In some embodiments, the processor may identify combinations of initial nodes that can enclose a closed polygon as eligible node combinations.

[0429] In some examples, the predetermined condition includes a ratio of the area of ​​the closed polygon to the area of ​​the construction drawing being greater than a first percentage threshold and less than a second percentage threshold, the first percentage threshold being less than the second percentage threshold. For example, the first percentage threshold may be 5% and the second percentage threshold may be 80%.

[0430] The first and second percentage thresholds are threshold conditions related to area percentages, and may be default values, predetermined values, user-entered values, etc.

[0431] In some embodiments, the processor may identify as eligible node combinations initial node combinations that can enclose a closed polygon and whose proportion of the area of ​​the closed polygon to the area of ​​the construction drawing is greater than a first proportion threshold and less than a second proportion threshold.

[0432] In some examples, the processor may identify a closed polygon enclosed by a combination of eligible nodes as the construction site corresponding to the combination of eligible nodes.

[0433] Step S63: Identify a target node combination based on the input information of the eligible node combination.

[0434] The input information for the eligible node combination refers to information about the eligible node combination entered by the user. For example, the input information for the eligible node combination may include the axis grid nodes that the user selected in the eligible node combination.

[0435] In some embodiments, the processor may obtain input information of the combination of eligible nodes by accessing a user terminal.

[0436] In some embodiments, the processor may identify at least one axis grid node from the eligible node combination based on the input information of the eligible node combination, and identify the at least one axis grid node as a target node combination. In some embodiments, the processor may identify a construction site corresponding to the eligible node combination as a construction site corresponding to the target node combination.

[0437] As an example, FIG. 12D is an exemplary schematic diagram of a graphically represented construction site database according to some embodiments of the present disclosure. As shown in FIG. 12D , a combination of axis grid nodes f1, f2, f3, w1, w2, w3, and w4 is a qualifying node combination, and the qualifying node combination can enclose a closed polygon. If the user inputs axis grid nodes w1, w2, w3, and w4 to form a target node combination, the combination of w1, w2, w3, and w4 may be identified as the target node combination. In this case, the closed polygon enclosed by axis grid node w1, axis grid node w2, axis grid node w3, and axis grid node w4 is the construction site corresponding to the target node combination, i.e., "site 3."

[0438] In some embodiments of the present specification, a combination of target nodes is identified from a combination of initial nodes that satisfies a predetermined condition, and the construction site corresponding to the combination of target nodes is guaranteed to be a closed area, while preventing the area of ​​the construction site from being too large or too small.

[0439] In some embodiments, the initial node combination entered by the user may include multiple combinations. For example, the user may first select at least one axis grid node from the axis grid node set to configure the initial node combination, and after confirming the selection, the user may again select at least one axis grid node from the axis grid node set to configure a new initial node combination. The nodes included in the initial node combinations selected by the user multiple times differ in at least one node. When multiple initial node combinations are included, multiple eligible node combinations are included. In some embodiments, the multiple eligible node combinations can cover all areas of the construction drawing.

[0440] In some embodiments, when there are a plurality of combinations of initial nodes, the processor may identify a combination of goal nodes for each of the plurality of combinations of initial nodes by the following steps S631 to S634.

[0441] Step S631: Based on a combination of a plurality of initial nodes, identify a first subset consisting of a combination of a plurality of eligible nodes.

[0442] The first subset refers to a set that includes at least one eligible node combination.

[0443] In some embodiments, for each initial node combination, the processor performs step S62 above based on the initial node combination, and classifies the initial node combinations that satisfy the predetermined condition into a first subset of eligible node combinations.

[0444] Step S632: In response to the first subset not covering the construction area of ​​the construction drawing, identify a second subset of eligible node combinations.

[0445] In some examples, the processor may determine whether the union of the construction sites corresponding to the first subset of eligible node combinations covers the construction area of ​​the entire construction drawing in various ways. For example, the processor may calculate the area of ​​all construction sites corresponding to the first subset of eligible node combinations, and determine that the first subset does not cover the construction area of ​​the construction drawing in response to the calculated area being smaller than the total area of ​​the construction area of ​​the construction drawing.

[0446] The second subset refers to a set that includes at least one eligible node combination identified by multiple axis grid nodes that are not selected by the user.

[0447] In some embodiments, the processor may select axis grid nodes that are not selected as initial node combinations in the axis grid node set, divide the remaining axis grid nodes, and obtain a second subset of axis grid node combinations that satisfy a predetermined condition. For axis grid nodes that are not selected as initial node combinations in the axis grid node set, the processor may select a third predetermined number of axis grid nodes to form axis grid node combinations, perform step S62 above, and classify axis grid node combinations that satisfy the predetermined condition into the second subset of eligible node combinations. The third predetermined number may be a default value, a predetermined value, a user-entered value, etc. For details about the predetermined condition, please refer to the related description above.

[0448] Step S633: Identify the union of the first subset and the second subset as an eligible node combination.

[0449] Step S634: Obtain user input information based on the eligible node combinations to identify the target node combination. For a specific description of step S634, please refer to step S63 and its related description.

[0450] In some embodiments of the present specification, if the construction site corresponding to the combination of initial nodes entered by the user does not cover the entire construction area, the acquisition module can automatically divide the uncovered construction site, and finally identify the target node combination, ensuring that all construction areas of the construction drawing are divided into different construction sites, thereby avoiding the user forgetting some construction areas and not generating the corresponding task order.

[0451] Step 714: Identify drawing area information based on the combination of the target nodes.

[0452] In some embodiments, the processor may combine the combination of target nodes with numeric information, alphabetic information to generate drawing area information.

[0453] In some embodiments, the processor may store the extracted drawing information in a storage device.

[0454] Step 720: Identify a reference task order based on the drawing area information.

[0455] For details of the reference task order, please refer to Figures 4, 6 and their associated descriptions.

[0456] In some embodiments, the processor may generate an information request command based on the combination of target nodes corresponding to the drawing area information, send it to the user terminal, obtain the content input by the user through the user terminal, and identify it as the dedicated content of the reference task order.Furthermore, based on the construction project of the construction site corresponding to the combination of target nodes corresponding to the drawing area information, access the storage device to obtain the general content of the target task order, and generate the reference task order based on the dedicated content and the general content.

[0457] In some embodiments, the processor may identify the reference task order through steps S71 to S73.

[0458] Step S71: The part information and initial coordinates of the combination of the target nodes are obtained.

[0459] The part information of a combination of target nodes refers to information about a construction part corresponding to the combination of target nodes. For example, the part information of a combination of target nodes may include a construction project to which the construction part belongs (e.g., information about the building and floor to which it belongs). The construction part may be an object or structure produced / constructed in the construction project. Examples include walls, handrails, and stairs. Taking a construction project for building construction as an example, the part information may include wall information (e.g., wall position, thickness, area, material, structure, etc.), column information (e.g., column position, quantity, configuration, size, material, etc.), door and window information (e.g., door and window position, quantity, configuration, size, etc.), and fence information (e.g., fence type, position, quantity, configuration, size, etc.).

[0460] In some embodiments, the storage device may pre-store location information corresponding to various types of construction locations. After identifying a combination of target nodes, the type of construction location corresponding to the combination of target nodes may be identified. The location information of the construction location corresponding to the combination of target nodes may be read from the storage device. The storage device may be a storage device included in the task order processing system 200, or may be an external storage device not belonging to the task order processing system 200, such as a hard disk or an optical disk.

[0461] In some embodiments, the processor may read the location information of the target node combination through an interface, including, but not limited to, a program interface, a data interface, a transmission interface, etc. In some embodiments, when task order processing system 200 is operating, the location information of the target node combination may be automatically obtained from the interface. In some embodiments, task order processing system 200 may be invoked by another external device or system, and when invoked, the data is transmitted to task order processing system 200. In some embodiments, the location information of the target node combination may be obtained by any method known to one skilled in the art, and this specification is not intended to be limited thereto.

[0462] The initial coordinates may be relative coordinates of the combination of target nodes in the construction drawing, for example, coordinates of the combination of target nodes on the reference coordinate system in the construction drawing.

[0463] In some embodiments, the initial coordinates of the combination of target nodes may include coordinates of each axis grid node in the combination of target nodes corresponding to the construction drawing. In some embodiments, the initial coordinates of the combination of target nodes may include a coordinate range of the construction site corresponding to the combination of target nodes on the construction drawing.

[0464] In some embodiments, the processor may determine the initial coordinates of the combination of target nodes in various ways based on the coordinates of each axis grid node in the combination of target nodes in the construction drawing. For example, the processor may determine a set of coordinates of each axis grid node in the combination of target nodes in the construction drawing as the initial coordinates of the combination of target nodes. As another example, the processor may determine a coordinate range consisting of the coordinates of each axis grid node in the combination of target nodes in the construction drawing as the initial coordinates of the combination of target nodes.

[0465] Step S72: Based on the initial coordinates, the standard coordinates are identified.

[0466] The initial coordinates specified above are relative coordinates of the combination of target nodes relative to the construction drawing. The standard coordinates refer to the absolute coordinates of the combination of target nodes. For example, the standard coordinates may be coordinates relative to the standard coordinate system in the standard drawing.

[0467] Standard drawings refer to construction drawings that conform to standard sizes, such as A0, A1, A2, A3, and A4.

[0468] The standard coordinate system refers to a coordinate system established in a standard drawing. In some embodiments, the horizontal axis direction of the standard coordinate system may be the same as the horizontal axis direction of the reference coordinate system (both are first directions), and the vertical axis direction of the standard coordinate system may be the same as the vertical axis direction of the reference coordinate system (both are second directions). The standard coordinate system may be preset in the standard drawing by the designer or system involved.

[0469] In some embodiments, the processor may convert the initial coordinates of the combination of target nodes from the reference coordinate system to the standard coordinate system through coordinate system conversion, thereby obtaining the standard coordinates of the combination of target nodes relative to the standard drawing. The embodiments of this specification do not particularly limit the coordinate system conversion method, and operations well known to those skilled in the art may be used.

[0470] In some examples, the processor may obtain the drawing size of the construction drawing, determine a conversion factor based on the drawing size of the construction drawing and a standard size, and determine the standard coordinates based on the initial coordinates and the conversion factor.

[0471] In some examples, the processor may obtain the drawing size of the construction drawing by accessing a storage device. In some examples, the processor may identify the drawing size of the construction drawing by obtaining user input. The drawing size of the construction drawing may also be obtained in any other feasible manner, and this specification is not intended to be limiting.

[0472] The standard size refers to the drawing size of the standard drawing. In some examples, the processor may obtain the standard size of the standard drawing by accessing a storage device. In some examples, the processor may identify the standard size of the standard drawing by obtaining user input. The standard size of the standard drawing may also be obtained by any other feasible manner, and this specification is not intended to be limiting thereto.

[0473] Conversion coefficient refers to the coefficient used for coordinate conversion between construction drawings and standard drawings.

[0474] In some embodiments, when the initial coordinates are coordinates of an axis grid node, the processor may determine a first conversion factor in the first direction based on the drawing sizes of the construction drawings and the standard drawings in the first direction, and determine a second conversion factor in the second direction based on the drawing sizes of the construction drawings and the standard drawings in the second direction, where the first conversion factor is a conversion factor used for abscissa transformation and the second conversion factor is a conversion factor used for ordinate transformation.

[0475] For example, if the size in the first direction of the construction drawing is q1 and the size in the first direction of the standard drawing is q2, the first conversion coefficient in the first direction can be calculated by the formula Q=q1 / q2. As another example, if the size in the second direction of the construction drawing is p1 and the size in the second direction of the standard drawing is p2, the second conversion coefficient in the second direction can be calculated by the formula Q=p1 / p2.

[0476] In some embodiments, when the initial coordinates are the coordinate range of the construction site, the processor may determine a conversion factor based on the drawing areas of the construction drawings and the standard drawings. For example, when the drawing area of ​​the construction drawings is m1 and the drawing area of ​​the standard drawings is m2, the conversion factor is calculated by the formula M=m1 / m2.

[0477] In some embodiments, the processor may determine the normal coordinate as the product of the initial coordinate and the normal coordinate determined by the transformation coefficient. For example, for the normal coordinate in a first direction of an axis grid node in the combination of target nodes, the processor may calculate it using the formula q0 = q3 / Q, where q0 is the normal coordinate in the first direction of the axis grid node, q3 is the initial coordinate in the first direction of the axis grid node, and Q is a first transformation coefficient in the first direction. For the normal coordinate in a second direction of an axis grid node in the combination of target nodes, the processor may calculate it using the formula p0 = p3 / p, where p0 is the normal coordinate in the second direction of the axis grid node, p3 is the initial coordinate in the second direction of the axis grid node, and P is a second transformation coefficient in the second direction.

[0478] As another example, for the standard coordinates (range values) of the construction site, the processor may calculate them using the formula m0=m3 / M, where m0 is the standard coordinate of the construction site, m3 is the initial coordinate of the construction site, and M is a conversion coefficient.

[0479] Step S73: Identify the reference task order based on the part information and standard coordinates.

[0480] In some embodiments, the processor may identify a previous construction site that matches the construction site corresponding to the combination of target nodes based on the site information and the standard coordinates, where the previous construction site is a construction site to which a task has been assigned. The processor may identify at least one reference task order corresponding to the combination of target nodes based on a previous task order of the previous construction site.

[0481] In some examples, the processor may perform matching in the task order database using a first rule based on the location information and the standard coordinates to identify a first reference construction location and generate a first task order subset; perform matching in the task order database using a second rule based on the location information and the standard coordinates to identify a second reference construction location and generate a second task order subset; perform matching in the task order database using a third rule based on the location information and the standard coordinates to identify a third reference construction location and generate a third task order subset; and identify at least one reference task order based on the first task order subset, the second task order subset, and the third task order subset.

[0482] The task order database includes multiple assigned past task orders. Each past task order may correspond to one or more past construction sites. That is, each past task order includes multiple tasks to perform construction work on one or more past construction sites. A past construction site is a construction site to which a task is assigned.

[0483] In some embodiments, the task order database may be automatically generated by the system. For example, the task order processing system 200 may associate assigned past task orders with one or more past construction sites and store the assigned past task orders and their corresponding one or more past construction sites together in the task order database. The task order database may be updated in real time.

[0484] In some embodiments, the first rule is that the standard coordinates are the same as the coordinate range corresponding to the construction site in the task order database, and the construction project corresponding to the site information is the same as the construction project corresponding to the construction site in the task order database (hereinafter referred to as the reference construction site). The construction project corresponding to the site information being the same as the construction project corresponding to the construction site in the task order database may include one or more of the following situations:

[0485] 1. The building corresponding to the part information is the same as the building corresponding to the reference construction part, but the floor corresponding to the part information is different from the floor corresponding to the reference construction part. 2. The building corresponding to the part information is different from the building corresponding to the reference construction part, but the floor corresponding to the part information is the same as the floor corresponding to the reference construction part. 3. The building corresponding to the part information is different from the building corresponding to the reference construction part, and the floor corresponding to the part information is different from the floor corresponding to the reference construction part.

[0486] That is, when one matching rule in the following first rule is satisfied, the reference construction portion obtained by matching in the task order database may be identified as the first reference construction portion.

[0487] In some embodiments, matching rule 1 is that the standard coordinates are the same as the coordinate range corresponding to the reference construction site, the building corresponding to the site information is the same as the building corresponding to the reference construction site, but the floor corresponding to the site information is different from the floor corresponding to the reference construction site.

[0488] In some embodiments, matching rule 2 is that the standard coordinates are the same as the coordinate range corresponding to the reference construction site, the building corresponding to the site information is different from the building corresponding to the reference construction site, but the floor corresponding to the site information is the same as the floor corresponding to the reference construction site.

[0489] In some embodiments, matching rule 3 is that the standard coordinates are the same as the coordinate range corresponding to the reference construction site, the building corresponding to the site information is different from the building corresponding to the reference construction site, and the floor corresponding to the site information is different from the floor corresponding to the reference construction site.

[0490] In some examples, the processor may identify at least one reference construction site that satisfies the first rule as at least one first reference construction site. In some examples, the processor may identify at least one reference construction site that satisfies any one or more matching rules from Matching Rule 1, Matching Rule 2, and Matching Rule 3 as at least one first reference construction site.

[0491] In some examples, the processor may generate the first task order subset based on past task orders corresponding to at least one first reference construction site.

[0492] In some embodiments, the second rule is that the standard coordinates are within the coordinate range of the construction site in the task order database, and the construction project corresponding to the site information is the same as the construction project corresponding to the construction site in the task order database. The construction project corresponding to the site information being the same as the construction project corresponding to the construction site in the task order database may also include one or more of the following situations:

[0493] 1. The building corresponding to the part information is the same as the building corresponding to the construction part in the task order database, but the floor corresponding to the part information is different from the floor corresponding to the construction part. 2. The building corresponding to the part information is different from the building corresponding to the construction part, but the floor corresponding to the part information is the same as the floor corresponding to the construction part. 3. The building corresponding to the part information is different from the building corresponding to the construction part, and the floor corresponding to the part information is different from the floor corresponding to the construction part.

[0494] That is, if one matching rule in the following second rule is satisfied, the reference construction portion obtained by matching in the task order database may be identified as the second reference construction portion.

[0495] In some embodiments, matching rule 4 is that the standard coordinates are within the coordinate range of the construction site in the task order database, the building corresponding to the site information is the same as the building corresponding to the construction site in the task order database, but the floor corresponding to the site information is different from the floor corresponding to the construction site.

[0496] In some embodiments, matching rule 5 is that the standard coordinates are within the coordinate range of the construction site in the task order database, and the building corresponding to the site information is different from the building corresponding to the construction site, but the floor corresponding to the site information is the same as the floor corresponding to the construction site.

[0497] In some embodiments, matching rule 6 is that the standard coordinates are within the coordinate range of the construction site in the task order database, the building corresponding to the site information is different from the building corresponding to the construction site, and the floor corresponding to the site information is different from the floor corresponding to the construction site.

[0498] In some examples, the processor may identify at least one reference construction site that satisfies the second rule as at least one second reference construction site. In some examples, the processor may identify at least one reference construction site that satisfies any one or more matching rules of Matching Rule 4, Matching Rule 5, and Matching Rule 6 as at least one second reference construction site.

[0499] In some examples, the processor may generate the second task order subset based on past task orders corresponding to the second reference construction site.

[0500] In some embodiments, the third rule is that the standard coordinates are the same as the coordinate range of the construction site in the task order database, or the standard coordinates are included in the coordinate range of the construction site in the task order database, and the construction project corresponding to the site information is different from the construction project corresponding to the construction site in the task order database. The construction project corresponding to the site information being different from the construction project corresponding to the construction site in the task order database may include one or more of the following situations:

[0501] 1. The building corresponding to the part information is different from the building corresponding to the construction part, but the floor corresponding to the part information is the same as the floor corresponding to the construction part. 2. The building corresponding to the part information is different from the building corresponding to the construction part, and the floor corresponding to the part information is different from the floor corresponding to the construction part.

[0502] That is, if one matching rule in the following third rule is satisfied, the reference construction portion obtained by matching in the task order database may be identified as the third reference construction portion.

[0503] In some embodiments, matching rule 7 is that the standard coordinates are the same as the coordinate range of the construction site in the task order database, the building corresponding to the site information is different from the building corresponding to the construction site, but the floor corresponding to the site information is the same as the floor corresponding to the construction site.

[0504] In some embodiments, matching rule 8 is that the standard coordinates are the same as the coordinate range of the construction site in the task order database, the building corresponding to the site information is different from the building corresponding to the construction site, and the floor corresponding to the site information is different from the floor corresponding to the construction site.

[0505] In some embodiments, matching rule 9 is that the standard coordinates are within the coordinate range of the construction site in the task order database, and the building corresponding to the site information is different from the building corresponding to the construction site, but the floor corresponding to the site information is the same as the floor corresponding to the construction site.

[0506] In some embodiments, the matching rule 10 is such that the standard coordinates are within the coordinate range of the construction site in the task order database, the building corresponding to the site information is different from the building corresponding to the construction site, and the floor corresponding to the site information is different from the floor corresponding to the construction site.

[0507] In some examples, the processor may identify at least one reference construction site that satisfies the third rule as at least one third reference construction site.

[0508] In some embodiments, the processor may identify at least one reference construction site that satisfies any one or more of matching rules: matching rule 7, matching rule 8, matching rule 9, and matching rule 10, as at least one third reference construction site.

[0509] In some examples, the processor may generate a third task order subset based on past task orders corresponding to a third reference construction site.

[0510] In some embodiments, the processor may identify the union of the first task order subset, the second task order subset, and the third task order subset as the reference task order.

[0511] In some examples, the processor may sort the first task order subset, the second task order subset, and the third task order subset in a predetermined order and identify at least one reference task order based on the sorting result.

[0512] In some embodiments, the predetermined order is relative to the rule type when matching. For example, the predetermined order may be: first task order subset specified by first rule > second task order subset specified by second rule > third task order subset specified by third rule.

[0513] In some examples, the processor may identify N task orders sorted to the top as reference task orders based on the sorting results, where N may be a default value, a predetermined value, a user-entered value, or the like. For example, if the number of task orders included in the first task order subset is less than N (e.g., the number of task orders is R), all task orders in the first task order subset may be identified as reference task orders, and N R task orders from the second task order subset may be selected as reference task orders. As another example, if the number of task orders included in the first task order subset is greater than N, N task orders from the first task order subset may be selected as reference task orders. Selection methods include, but are not limited to, random selection, user selection, etc.

[0514] In some embodiments of the present specification, the first task order subset, the second task order subset, and the third task order subset are sorted based on the type of rule, and the coordinate range corresponding to the task orders sorted higher is the same as the standard coordinate, and the construction project corresponding to the task orders sorted later is different from the construction project corresponding to the site information, so that the identified reference task order has a higher reference value.

[0515] In some examples, the processor may sort the task orders in each task order subset based on the body part information, the standard coordinates, and the matching relationships in the task order database, and identify at least one reference task order based on the sorted first task order subset, the sorted second task order subset, and the sorted third task order subset.

[0516] In some embodiments, the matching relationships of the part information, standard coordinates, and task order database may include matching relationships that perform matching based on matching rules 1 to 10, respectively. Thus, the sort order of the task orders in the first task order subset may be specified such that the sort order of the task orders corresponding to the first reference construction parts identified based on matching rules 1 to 3, respectively, is in descending order. The sort order of the task orders in the second task order subset is specified such that the sort order of the task orders corresponding to the second reference construction parts identified based on matching rules 4 to 6, respectively, is in descending order. The sort order of the task orders in the third task order subset is specified such that the sort order of the task orders corresponding to the third reference construction parts identified based on matching rules 7 to 10, respectively, is in descending order.

[0517] In some examples, the processor may identify N task orders sorted to the top as reference task orders based on the first sorted task order subset, the second sorted task order subset, and the third sorted task order subset. N may be a default value, a predetermined value, a user-entered value, etc. For example, if the number of task orders included in the first task order subset is less than N (e.g., the number of task orders is R), all task orders in the first task order subset may be identified as reference task orders, and N R task orders sorted to the top from the second task order subset may be identified as reference task orders. As another example, if the number of task orders included in the first task order subset is greater than N, the N task orders sorted to the top from the first task order subset may be identified as reference task orders. Selection methods include, but are not limited to, random selection, user selection, etc.

[0518] In some embodiments of the present specification, by converting the initial coordinates of the combination of target nodes into standard coordinates, the construction drawings can be standardized, which not only facilitates subsequent processing and management of the construction drawings, but also improves the accuracy of the reference construction site obtained by matching within the task order database.

[0519] Step 730: Identify a target task order based on the reference task order.

[0520] In some embodiments, for each construction site on each floor of each building in the construction project, the processor may generate a corresponding target task order. For example, if each floor of each building corresponds to one construction drawing, the processor may identify a combination of multiple target nodes from the axis grid node set, and each combination of target nodes may correspond to one construction site. Therefore, a target task order for the construction site is generated based on the combination of target nodes corresponding to the construction site. For details about the combination of multiple target nodes, see step 710 and its related description.

[0521] In some embodiments, the processor may generate a target task order based on at least one reference task order in various ways. For example, the processor may randomly select one reference task order from the at least one reference task order as the target task order. As another example, the processor may transmit the at least one reference task order to a user terminal, and the processor may select a reference task order from the at least one reference task order as the target task order.

[0522] In some embodiments, the processor may obtain a target reference task order selected by a user from at least one reference task order, identify a first task order content based on the target reference task order, identify a second task order content based on the site information, and generate a target task order based on the first task order content and the second task order content. The target reference task order refers to the reference task order selected by the user.

[0523] The first task order content refers to the general content in the target task order. For example, the first task order content may include the contractor, construction period, construction volume, unit price, payment method, technical explanation, safety explanation, precautions, etc. For details about the general content, please refer to step 330 and its related description.

[0524] In some embodiments, the processor may identify general content within the target reference task order as the first task order content.

[0525] In some embodiments, the processor may modify general content in the target-reference task order based on the actual situation of the construction site corresponding to the combination of target nodes, and identify the modified general content as the first task order content. For example, the processor may modify information such as the contractor, construction period, construction volume, and unit price in the general task.

[0526] The second task order content refers to content related to the construction area (i.e., dedicated content) in the target task order. For example, the second task order content may include the construction area, building shape, interior layout, etc. For details about the dedicated content, see step 330 and its related description. In some embodiments, the processor may modify the dedicated content in the target reference task order and identify the modified dedicated content as the second task order content. In some embodiments, the processor may display the generated second task order content to the user via a display device. The user may modify or confirm the generated second task order content.

[0527] In some embodiments, the storage device may include a correspondence between various body part information and second task order content, and the processor may access the storage device based on the identified body part information and generate the second task order content according to the correspondence.

[0528] In some embodiments, the processor may combine the first task order content and the second task order content to generate the target task order.

[0529] In some embodiments herein, generating a target task order using a target reference task order and site information selected by a user improves the efficiency of generating a target task order and facilitates time savings.

[0530] In some embodiments, the processor may, in response to a reference construction site not being matched in the task order database based on the site information and the standard coordinates, push an information input request to the user, identify a first task order content based on the information input request, identify a second task order content based on the site information, and generate a target task order based on the first task order content and the second task order content.

[0531] The information prompt may be a prompt that prompts the user to manually enter information. In some examples, the information prompt may prompt the user to manually enter the first task order details.

[0532] In some embodiments, the processor may identify the first task order content based on information input by the user in response to the information input request.

[0533] The method of identifying the second task order content based on the part information and generating the target task order based on the first task order content and the second task order content is the same as the method described above, so it will not be described here again.

[0534] For details on identifying a target task order based on a reference task order, see Figures 4, 6 and their associated discussions.

[0535] The task assignment process requires the entry of a large amount of information into the task order, which consumes time and effort. In some embodiments of this specification, the numerical information and alphabetical information in the construction drawing are analyzed to obtain, and the axis grid information in the construction drawing is automatically identified. A graphical construction part database is created based on the axis start points and axis intersection points in the axis grid information. During the construction task order assignment process, a construction part corresponding to the combination of target nodes is selected, and a task order template is recommended and imported based on the relative coordinate relationship between the selected construction part and the assigned construction part, thereby realizing efficient and intelligent task order assignment, avoiding the need to manually enter a large amount of data information, improving the generation efficiency of target task orders, and helping to shorten the task order assignment time.

[0536] 8 is an exemplary fourth flowchart for generating a target task order according to some embodiments of the present disclosure. As shown in FIG. 8, flow 800 includes the following steps. In some embodiments, one or more operations of flow 800 shown in FIG. 8 can be implemented in application scenario 100 of the task order processing system. For example, flow 800 shown in FIG. 8 can be stored in a storage device in the form of instructions and can be invoked and / or executed by a processor. In some embodiments, flow 800 can be executed by a processor.

[0537] Step 810: In response to the task order allocation entry information indicating that the task order allocation entry is a progress entry, obtain progress unit information input by the user.

[0538] Progress unit information refers to information about the construction progress of a specific area or specific component of a construction project. Construction progress is an indicator for measuring the completion status of a specific area or component of a construction project. Construction progress may be displayed in various ways. For example, construction progress may be visually displayed in various ways, such as a Gantt chart or a schedule. For example, the inspection information of different progress units may be reflected in the form of no mark, a dark mark, a light mark, or the like. A dark mark indicates that the minimum production unit has not been inspected after reaching the planned end time, a light mark indicates that the minimum production unit has been inspected before reaching the planned end time, and no mark indicates that the current time has not reached the planned end time of the minimum production unit.

[0539] The Gantt chart and / or schedule may visually display the relationship between the construction plan (e.g., planned start time, planned finish time, etc.) and actual progress (e.g., actual start time, actual finish time, etc.) for each task item, as well as the completion percentage for each task item.

[0540] In some examples, the progress unit information may include the specific construction task of the progress unit, associated time information (e.g., start time of a task), task description and status (e.g., completed, in progress, not started, percentage complete), etc. A progress unit is a unit that visually represents and manages the progress of a construction project, and can be used to indicate the completion status of a specific area or component in the progress of the project.

[0541] The progress units can be used to check the progress of each task, assess the rationality of the interlocking progress of each task, assess cost and progress risks, and assess collaboration risks between functional departments. In some embodiments, the processor can visually display the construction progress of a construction project by constructing a visual progress display table. For example, taking the construction progress of a building construction project as an example, the visual progress display table can display the correspondence between each floor of the building body and the task processes included in each floor. The task processes included in each floor may include multiple cells such as "framework work," "exterior wall puttying," "aluminum window installation," "handrail installation," "bricklaying," "public area plastering," "insulation work," "floor finishing," "interior plastering," and "public area interior design." Each cell corresponds to one progress unit, and the information corresponding to that progress unit is progress unit information. For example, the time information included in the visual progress display table includes the planned completion time of each progress unit. In practical applications, different color marks can be used to represent the inspection information of each progress unit. For example, a first color mark indicates that the current time has not reached the planned end time of the progress unit, a second color mark indicates that the progress unit has been inspected before reaching the planned end time, and a third color mark indicates that the progress unit has not been inspected after reaching the planned end time. Progress units may be divided and identified in advance manually or by a system.

[0542] In some embodiments of this specification, a visual progress display table can be constructed to intuitively and visually display the alternate progress of each area and each task step, and time-dimensional information of each progress unit can be added to the visual progress display table, and the inspection status of each visual progress unit can be distinguished using color marks, thereby obtaining dynamic visualized results such as dynamic simulation of construction, dynamic comparison of plan and actual results, and review of construction process.

[0543] In some embodiments, if a user selects to initiate a task order via a “progress entry,” the processor may identify the type of this task order assignment entry and obtain the corresponding progress unit information.

[0544] Step 820: Identify a reference task order based on the progress unit information.

[0545] In some examples, the processor may query a historical database based on the progress unit information to identify task orders related to the current progress unit. These task orders may be from the same or similar projects and have similar task types and progress stages. The processor may match the historical task order that best meets the current needs as a reference task order based on the progress unit information.

[0546] In some examples, the processor may identify assigned task items and unassigned task items for the progress unit based on the progress unit information, identify reference assignment information for the reference progress unit, identify items to be assigned from the unassigned task items based on the reference assignment information, and identify a reference task order based on the items to be assigned and the reference assignment information.

[0547] An assigned task item is a task item for which a task order has been generated. An unassigned task item is a task item for which a task order has not yet been generated.

[0548] In some embodiments, the processor may check the status of all tasks in the current unit of progress and distinguish which tasks are assigned (i.e., task orders have been generated and are in progress or completed) and which tasks are not yet assigned.

[0549] A reference progress unit refers to a progress unit that is used as a reference. In some embodiments, a processor may use a fully completed progress unit as a reference progress unit.

[0550] The reference assignment information refers to task order assignment information obtained by extracting all completed task items from the reference progress unit. In some examples, the task order assignment information may include at least one of a task order assignment period (e.g., once a week), a task order assignment frequency (e.g., the number of tasks assigned per day), and a task order assignment interval (e.g., the interval time between tasks), etc.

[0551] An item to be assigned refers to a task item that is to be assigned. In some examples, the processor may identify assigned task items from unassigned task items in combination with assigned task items in the current progress unit based on the task order assignment cycle, task order assignment frequency, and task order assignment interval in the reference assignment information. For example, if the structural work on the fifth floor is completely completed but a task order has not been assigned for part of the structural work on the sixth floor, the processor may identify which task item to assign next for the structural work on the sixth floor based on the task order assignment mode for the structural work on the fifth floor.

[0552] In some examples, for each identified item to be assigned, the processor may find a corresponding task order from the reference unit of progress as a reference task order. For example, the processor may find similar or related task items by comparing unassigned task items in the current unit of progress with task items in the reference unit of progress. As an example, if it is determined that electrical installation work needs to be performed for the structural work on the sixth floor, the processor may find and reference a task order to perform electrical installation work before the structural work on the fifth floor.

[0553] Step 830: Identify a target task order based on the reference task order.

[0554] In some embodiments, the processor may combine the specific task content in the reference task order with current progress unit information to generate a target task order, such that the content of the target task order accurately reflects the specific circumstances and requirements of the current project.

[0555] In some embodiments, the processor may identify, based on the reference task order, reference data that is data described in the reference task order but does not include the construction area described in the reference task order, identify a target construction area based on progress unit information, and enter the reference data and the target construction area into the target task order.

[0556] In some examples, the reference data may include, but is not limited to, a task description, materials required, estimated completion time, responsible parties, etc. The processor may copy this data into the target task order.

[0557] In some embodiments, the processor may identify the target construction area based on the progress unit information in various ways. For example, the processor may extract specific construction area information, such as an associated floor or room number, from the progress unit selected by the user. The processor may identify the target construction area for the target task order by combining the construction area information in the progress unit.

[0558] In some examples, the processor may complete the creation of the target task order by filling in the identified target construction area information into the target task order, where the target task order includes all necessary information such as a task description, required materials, estimated completion time, responsible party, and exact target construction area.

[0559] For a description of identifying a target task order based on a reference task order, reference may be made to Figures 4, 6 and their associated discussions.

[0560] In some embodiments of the present specification, by allocating task orders through visual progress entries, when a user checks the visual progress, task orders can be appropriately allocated based on the acquired progress status, and progress issues such as progress delays can be improved. Reference task orders can effectively improve the information reference rate, realize automatic reference or automatic entry of related information, and improve the efficiency of building target task orders.

[0561] 9 is an exemplary fifth flowchart for generating a target task order according to some embodiments of the present disclosure. As shown in FIG. 8, flow 900 includes the following steps. In some embodiments, one or more operations of flow 900 shown in FIG. 9 can be implemented in application scenario 100 of the task order processing system. For example, flow 900 shown in FIG. 9 can be stored in a storage device in the form of instructions and can be invoked and / or executed by a processor. In some embodiments, flow 900 can be executed by a processor.

[0562] Step 910: In response to the task order allocation entry information indicating that the task order allocation entry is a price management table entry, obtain the list item information in the cell of the price management table entered by the user.

[0563] List item information refers to information about project costs in a price management table. In some examples, list item information may include a specific cell location (e.g., a cost item for a task), a task description and status (e.g., completed, in progress, not started), associated cost information (e.g., material costs, labor costs, etc.), estimated completion time, and other associated details.

[0564] In some embodiments, the list item information may be data information in a table format including row information and column information. For example, the row information may include a building number, a floor number, a list item, a task item, a construction amount, a total cost, a completion time, a contract performer, etc. The column information may include numerical or text content corresponding to each row information.

[0565] In some examples, a user may select specific cells from the price management table, which represent specific items or tasks in project cost control, and the processor may then retrieve the user-selected cells and corresponding list item information.

[0566] Step 920: Identify a reference task order based on the list item information.

[0567] In some examples, the processor may query past task orders to identify past task orders related to the current progress unit. For example, past task orders originating from the same or similar projects and having similar task types and cost control requirements may be identified as relevant past task orders. The processor may further match and identify the past task order that best meets the current needs as the reference task order based on the list item information from the relevant past task orders. For example, if a user selects a pouring task represented by a cell, the processor may query past task orders that were previously poured and performed detailed cost control in the same project or other similar projects.

[0568] In some embodiments, the processor may identify a reference cell based on row information and column information in the list item information, and identify a reference task order based on the reference cell.

[0569] In some examples, the processor may instruct the user to select a cell from the list item information. The processor may then identify a parent area and a child area based on row information corresponding to the cell selected by the user, and identify a task item based on the row information corresponding to the cell selected by the user. For example, if the cell selected by the user is "Building 7, 2nd Floor, Task Item 2," the row information indicates that the parent area is Building 7 and the child area is 2nd Floor, and the column information indicates that the task item is Task Item 2. Furthermore, the processor may search for a construction area where task order assignments for all task items have been completed from past task orders as a reference area based on the row information and column information, and search for a corresponding cell in the price management table as a reference cell based on the coordinates (e.g., row number and column number) of the cell corresponding to the reference area.

[0570] In some examples, the processor may extract information from the reference cell and identify list item information of the reference cell. Based on the list item information of the reference cell, the processor may identify a past task order in past task orders that has similar list item information as the reference task order. For example, if the reference cell indicates task item 2 on the first floor of Building 7, the processor may use this information to search the past task orders for past task orders that previously performed the same task in the same project or other similar projects and that underwent detailed cost control as the reference task order.

[0571] Step 930: Identify a target task order based on the reference task order.

[0572] In some embodiments, the processor may combine the specific task content in the reference task order with the current listing information to generate the target task order.

[0573] In some embodiments, after identifying the reference task order, the processor may identify reference data based on the reference task order, which is data described in the reference task order but does not include the construction area described in the reference task order, identify a target construction area based on cell information, and enter the reference data and the target construction area into the target task order.

[0574] For details on identifying a target task order based on a reference task order, see Figures 4, 6 and their associated discussions.

[0575] In some examples herein, allocating task orders via price management table entries allows users to understand the cost situation, allocate task orders appropriately, and avoid potential cost issues when reviewing the price management table.

[0576] 10 is an example flowchart for adjusting the availability of a task order template according to some embodiments herein. As shown in FIG. 10, flow 1000 includes the following steps. In some embodiments, one or more operations of flow 1000 shown in FIG. 10 can be implemented in an application scenario 100 of a task order processing system. For example, flow 1000 shown in FIG. 10 can be stored in a storage device in the form of instructions and can be invoked and / or executed by a processor. In some embodiments, flow 1000 can be executed by a processor.

[0577] Step 1010: Obtain the current status of the contract performer for the task order template in the task order template library.

[0578] The current state refers to the current state of the contract performer. In some examples, the current state may include an unavailable state (e.g., exited) and an available state.

[0579] In some embodiments, the processor may obtain information related to the contract performer and identify the current status of the contract performer. For example, the processor may determine whether the contract performer has left the venue via location information of the contract performer's user terminal.

[0580] Step 1020: Adjust the availability of the task order template in response to the current status of the contract performer being unavailable.

[0581] The availability of a task order template refers to a property that reflects whether the task order template can be used. For example, the availability of a task order template may include available and unavailable. In some embodiments, adjusting the task order template by the processor may include the following steps 1021 through 1026.

[0582] Step 1021: In response to the task order template being the source task order template, update the task order template as unavailable.

[0583] If the task order template is a source task order template, the task order to be created is not divided, the unavailable contract performer is more important, and if the current status of the contract performer is unavailable, the task order template will no longer have reference value, so the task order template will be updated as unavailable.

[0584] In some embodiments, steps 1022 through 1026 may be performed in response to the task order template being a split task order template.

[0585] Step 1022: In response to the task order template being a split task order template, determine whether the unavailable contract performer is a worker.

[0586] In some embodiments, in response to the unavailable contract fulfiller not being a worker, step 1023 may be performed. In some embodiments, in response to the unavailable contract fulfiller being a worker, steps 1024 through 1026 may be performed.

[0587] Step 1023: Update the task order template as unavailable.

[0588] If the unavailable contract performer is not a worker, the unavailable contract performer is relatively important, and if the current status of the contract performer is unavailable, the task order template will no longer have any reference value, so the task order template will be updated as unavailable.

[0589] Step 1024: Determine whether the worker is the only contract performer in the task order template.

[0590] If the unavailable contract performer is a worker, the unavailable contract performer is relatively unimportant, and if the current status of the unavailable contract performer is unavailable, further determine whether the worker is the only contract performer in the task order template.

[0591] In some examples, step 1025 may be performed in response to the worker being the only contract fulfiller in the task order template. In some examples, step 1026 may be performed in response to the worker not being the only contract fulfiller in the task order template.

[0592] Step 1025: Update the task order template as unavailable.

[0593] In response to the worker being the only contract fulfiller in the task order template, if the current state of the contract fulfiller is unavailable, the task order template is updated as unavailable because the task order template cannot be executed.

[0594] Step 1026: Exclude the worker from the contract performers of the task order template.

[0595] In response to the worker not being the only contract performer in the task order template, if the current status of the contract performer is unavailable, the worker may be removed from the contract performers of the task order template, and the remaining workers may execute the task order template.

[0596] In some examples herein, the availability of task order templates is adjusted in response to the current status of the contract fulfiller being unavailable, thereby making the updated task order template library more compliant with the actual situation and avoiding situations where an identified target task order cannot be executed due to the current status of the contract fulfiller being unavailable.

[0597] The above description of the flow for adjusting the availability of a task order template is for illustrative purposes only and does not limit the scope of the present specification. Those skilled in the art may make various modifications and changes to the flow for adjusting the availability of a task order template under the guidance of this specification. However, these modifications and changes are still within the scope of this specification.

[0598] Some embodiments herein also provide a computer-readable storage medium storing computer instructions, which, when read by a computer, cause the computer to execute the task order processing method.

[0599] It should be noted that the above description of each flow is for illustrative and explanatory purposes only and does not limit the scope of the present specification. Those skilled in the art may make various modifications and changes to each flow under the guidance of this specification. However, these modifications and changes still fall within the scope of this specification.

[0600] While the basic concepts have been described above, it will be apparent to those skilled in the art that the above detailed disclosure is merely illustrative and is not intended to limit the present disclosure. Although not expressly stated herein, those skilled in the art may make various changes, improvements, and modifications to the present disclosure. Such changes, improvements, and modifications are proposed herein and therefore fall within the spirit and scope of the illustrative embodiments herein.

[0601] Furthermore, the present specification uses specific terms to describe the embodiments of the present specification. For example, "one embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic of at least one embodiment of the present specification. Therefore, it should be noted that "one embodiment," "one embodiment," or "one alternative embodiment" mentioned two or more times in different places in the present specification do not necessarily refer to the same embodiment. Furthermore, specific features, structures, or characteristics of one or more embodiments of the present specification may be combined as appropriate.

[0602] Additionally, unless expressly recited in the claims, the order of processing elements and sequences, the use of numerical, alphabetical, or other designations described herein are not intended to limit the order of flows and methods herein. While the above disclosure has described, through various examples, some of the presently believed useful embodiments of the present invention, it is understood that such details are for illustrative purposes only, and the appended claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover modifications and equivalent combinations consistent with the substance and scope of the embodiments herein. For example, the system components described above can be implemented using hardware devices, but can also be implemented using software-only solutions, such as installing the described system on an existing server or mobile device.

[0603] It should be noted that the foregoing description of the embodiments herein may group together multiple features in a single embodiment, drawing, or description thereof to simplify the presentation of the disclosure herein and thereby facilitate understanding of one or more embodiments. However, this method of disclosure does not imply that the subject matter of this disclosure requires more features than are recited in the claims. In fact, an embodiment may have fewer features than all of the features of each individual embodiment disclosed above.

[0604] In some examples, numbers are used to describe the quantities of components and attributes. It is understood that such numbers used to describe the examples are, in some instances, modified by modifiers such as "about," "about," or "and." Unless otherwise specified, "about," "about," or "approximately" indicate that the numbers described above allow for a variation of ±20%. Thus, in some examples, the numerical parameters used in the specification and claims are approximations that may vary depending on the desired properties of the particular example. In some examples, the numerical parameters should take into account the number of significant digits specified and employ conventional methods to conserve digits. In some examples herein, the numerical ranges and parameters used to identify the breadth of ranges are approximations; however, in specific embodiments, such numerical values ​​are set as precisely as possible within the ranges feasible.

[0605] The entire contents of each patent, patent application, patent application publication, and other material (e.g., articles, books, specifications, publications, documents, etc.) cited herein are incorporated herein by reference. Any prior application documents that contradict or conflict with the contents of this specification are excluded, as are any documents (now or hereafter added to this specification) that limit the full scope of the claims herein. In the event that a statement, definition, and / or terminology in the accompanying materials contradicts or conflicts with the contents of this specification, the statement, definition, and / or terminology in this specification shall control.

[0606] Finally, it is understood that the examples described herein are used only to illustrate the principles of the examples herein. Other variations may fall within the scope of the present specification. Thus, by way of example, and not of limitation, alternative configurations of the examples herein are contemplated as being consistent with the teachings herein. Thus, the examples herein are not limited to the embodiments explicitly introduced and described herein.

Claims

1. 1. A task order processing system including a processor, The processor: identifying task order assignment entry information in response to a user initiating a task order creation operation for the construction project; Obtaining related information based on the task order assignment entry information; A task order processing system configured to generate a target task order based on the related information.

2. The processor further comprises: In response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, acquiring target construction area information including a parent area and a child area; Identifying a target past task order assigned by the user based on the parent area; Identifying a reference task order based on the target past task order and the child area; The system of claim 1 , configured to generate the target task order based on the reference task order and the target construction area information.

3. The processor further comprises: Obtain all past source task orders of the user within a predetermined period in the parent area, and sort them by time to obtain a first sorting result; The system of claim 2 , further configured to identify the target past task order from the first sorted result.

4. The processor further comprises: Obtain all the divided task orders of the user that are accepted by the contract fulfiller in the parent area within a predetermined period, and sort them by time to obtain a second sorting result; The system of claim 2 , further configured to identify the target past task order from the second sorted result.

5. The processor further comprises: In response to the task order assignment entry information indicating that the task order assignment entry is a dedicated entry, acquiring user information of the user and project information of the task order to be created; Identifying a target task order template from a task order template library based on the user information and the project information; Identifying a reference task order based on the target task order template; The system of claim 1 , configured to identify the target task order based on the target task order template and the reference task order.

6. The processor further comprises: Obtain past task orders including past user information and past project information, Dividing the past task orders into a plurality of primary groups based on the past user information and the past project information; For each of the primary groups, divide the past task orders corresponding to the primary group into a plurality of secondary groups based on the construction area, task items, and contract performers in the past task orders; for each of the plurality of secondary groups, identifying a task order template and a corresponding number of times the template has been used based on past task orders corresponding to the secondary group; 6. The system of claim 5, further configured to identify the task order template library based on task order templates corresponding to the plurality of secondary groups and a number of times the templates are used.

7. The processor further comprises: For each of the plurality of secondary groups, identifying the most recent past task order in the secondary group as a related task order of a task order template corresponding to the secondary group; identifying the task order template library based on task order templates corresponding to the plurality of secondary groups, a number of times the templates are used, and the associated task orders; The system of claim 6 , further configured to query the related task order based on the target task order template and identify the related task order as a reference task order.

8. The task order template library includes a first type task order template library and a second type task order template library, the first type task order template library is a source task order template library, and the second type task order template library is a split task order template library; The processor further comprises: In response to the user initiating a source task order creation operation, matching within the first type task order template library based on the user information and the project information to identify the target task order template; In response to the user initiating a split task order creation operation, Identifying contract performer information based on the task order to be split; performing a match within the second type task order template library based on the user information, the project information, and the contract performer information to identify a recommended parent-level task order; 7. The system of claim 6, further configured to identify the target task order template based on the recommended parent-level task order in response to the recommended parent-level task order satisfying a predetermined condition.

9. The processor further comprises: Obtaining the current status of the contract performer for the task order templates in the task order template library, including the source task order template and the split task order template; configured to adjust the availability of the task order template in response to the current status of the contract fulfiller being unavailable; adjusting the availability of the task order template updating the task order template as unavailable in response to the task order template being the source task order template; In response to the task order template being the split task order template, determining whether the unavailable contract performer is a worker; updating the task order template as unavailable in response to the unavailable contract performer not being a worker; In response to the unavailable contract performer being a worker, determining whether the worker is the only contract performer in the corresponding task order template; updating the corresponding task order template as unavailable in response to the worker being the only contract fulfiller for the corresponding task order template; 2. The system of claim 1, further comprising: responsive to the worker not being the only contract fulfiller in the corresponding task order template, excluding the worker from being a contract fulfiller in the corresponding task order template.

10. The processor further comprises: In response to the task order assignment entry information indicating that the task order assignment entry is a drawing entry, obtaining drawing area information; Identifying a reference task order based on the drawing area information; The system of claim 1 , configured to identify the target task order based on the reference task order.

11. The processor further comprises: Analyzing the construction drawings and extracting numerical information and alphabetical information from the construction drawings; Identifying an axis grid node set for the construction drawing based on the numeric information and the alphabetical information; Obtaining a combination of target nodes in the axis grid node set, and enclosing a closed polygon with the combination of target nodes; The system of claim 10 , further configured to identify drawing area information based on the combination of the target nodes.

12. The processor further comprises: Obtain a combination of initial nodes input by the user, each node being a node in the axis grid node set; verifying the initial node combinations based on predetermined conditions including at least whether they enclose a unique closed polygon, and identifying valid node combinations; The system of claim 10, configured to acquire input information input by the user based on the combination of legitimate nodes and identify the combination of target nodes.

13. The processor further comprises: Obtaining the part information of the combination of the target nodes and the initial coordinates of the nodes; determining standard coordinates of the node based on the initial coordinates; The system of claim 11 , further configured to identify the reference task order based on the body part information and the standard coordinates.

14. The processor further comprises: In response to the task order assignment entry information indicating that the task order assignment entry is a progress entry, acquiring progress unit information input by the user; Identifying a reference task order based on the progress unit information; The system of claim 1 , further configured to identify a target task order based on the reference task order.

15. The processor further comprises: In response to the task order allocation entry information indicating that the task order allocation entry is a price management table entry, obtaining list item information in a cell of the price management table entered by the user; Identifying a reference task order based on the list item information; The system of claim 1 , further configured to identify a target task order based on the reference task order.

Images