A method, system, and storage medium for storing project documents

Abstract

The present invention provides a method, a system and a storage medium for storing project documents. The method includes generating a construction progress matrix corresponding to a target project; generating a first document directory of the target project according to the eigenvalue of the project characteristics of the target project; for a target matrix unit in the construction progress matrix, determining a second project document corresponding to the target matrix unit from a plurality of first project documents based on the construction area label and the progress node label of the plurality of first project documents, and generating a second document directory corresponding to the target matrix unit; monitoring the database corresponding to the second project document based on the database label of the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory. This method can realize a document management method based on matrix units by generating a construction progress matrix, and improve the centralization and management efficiency of project documents.

Description

Technical Field

[0001] This specification relates to the field of document management, and particularly to a method, a system, and a storage medium for storing project documents. Background Art

[0002] In the management of modern engineering projects, project documents, as an important part of project management, are numerous in variety and involve multiple business processes. Project documents cover records of various aspects such as project design, construction, and supervision, and are closely related to project progress, quality, safety, etc. Traditional project document management relies on a folder structure to store and manage documents, making it cumbersome and inefficient to search for project documents. Moreover, different business systems store different project documents, and the scattered storage of project documents makes it difficult to achieve global unified management. On the other hand, there is almost no correlation between document storage and project progress, and project documents can only serve as information records and cannot play more functions.

[0003] Therefore, it is necessary to provide a method, a system, and a storage medium for storing project documents to improve the management efficiency of project documents and enable project documents to play more roles by establishing the correlation between project documents and actual project progress. Summary of the Invention

[0004] One or more embodiments of this specification provide a method for storing project documents. The method includes: generating a construction progress matrix corresponding to a target project, where the construction progress matrix includes a plurality of matrix units, and each matrix unit corresponds to a progress node of a construction area of the target project; generating a first document directory of the target project according to the eigenvalue of the project characteristics of the target project, where the first document directory is configured to store the document tags of a plurality of first project documents corresponding to the target project, and the document tags include construction area tags, progress node tags, and database tags; for a target matrix unit in the construction progress matrix, based on the construction area tags and progress node tags of the plurality of first project documents, determining a second project document corresponding to the target matrix unit from the plurality of first project documents, and generating a second document directory corresponding to the target matrix unit, where the second document directory is configured to store the index information of the second project document; monitoring the database corresponding to the second project document based on the database tag of the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory.

[0005] One embodiment of this specification provides a system for storing project documents. The system includes a first generation module configured to generate a construction progress matrix corresponding to a target project. The construction progress matrix includes a plurality of matrix units, and each matrix unit corresponds to a progress node of a construction area of the target project. A second generation module is configured to generate a first document directory of the target project according to the eigenvalue of the project characteristics of the target project. The first document directory is configured to store the document tags of a plurality of first project documents corresponding to the target project. The document tags include construction area tags, progress node tags, and database tags. A third generation module is configured to, for a target matrix unit in the construction progress matrix, determine a second project document corresponding to the target matrix unit from the plurality of first project documents based on the construction area tags and progress node tags of the plurality of first project documents, and generate a second document directory corresponding to the target matrix unit. The second document directory is configured to store the index information of the second project document. A monitoring module is configured to monitor the database corresponding to the second project document based on the database tag of the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory.

[0006] One or more embodiments of this specification provide a computer-readable storage medium. The storage medium stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes a method for storing project documents.

[0007] The beneficial effects brought by the above-mentioned invention content include but are not limited to: (1) Since the construction business is the hub for the cooperation of various functional units, when the association between project documents and the construction business is closer, the association between project documents and functional departments can also be closer, and thus project documents can play a greater role (such as compliance discrimination, early warning handling, etc.). By establishing a logical mapping between project documents, construction areas, and progress nodes, the association between project documents and the construction business is made closer; (2) By generating a construction progress matrix, it is possible to manage project documents based on matrix units, centrally store the relevant information of the project documents corresponding to the matrix units in the document directory, and improve the centralization and management efficiency of project documents. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] This specification will be further described by way of exemplary embodiments, which will be described in detail through the drawings. These embodiments are not restrictive. In these embodiments, the same numbers represent the same structures, where:

[0009] Figure 1 is a schematic diagram of an application scenario of a system for storing project documents according to some embodiments of this specification;

[0010] Figure 2 is an exemplary schematic diagram of a system for storing project documents as shown in some embodiments of this specification;

[0011] Figure 3 is an exemplary flowchart of a method for storing project documents as shown in some embodiments of this specification;

[0012] Figure 4 is an exemplary schematic diagram of determining a first project document and generating a first document directory as shown in some embodiments of this specification;

[0013] Figure 5 is an exemplary schematic diagram of a second document directory as shown in some embodiments of this specification;

[0014] Figure 6 is an exemplary flowchart of construction progress management based on an updated second project document as shown in some embodiments of this specification;

[0015] Figure 7 is an exemplary schematic diagram of a progress display table as shown in some embodiments of this specification. Detailed implementation manners

[0016] To more clearly illustrate the technical solutions of the embodiments of this specification, the following briefly introduces the drawings required for the description of the embodiments. Obviously, the following drawings are only some examples or embodiments of this specification. For those of ordinary skill in the art, without creative efforts, this specification can also be applied to other similar scenarios based on these drawings. Unless obvious from the language context or otherwise stated, the same reference numerals in the drawings represent the same structure or operation.

[0017] It should be understood that the "system", "device", "unit" and / or "module" used herein is a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the said words can be replaced by other expressions.

[0018] As shown in this specification and the claims, unless the context clearly indicates an exception, words such as "a", "an", "one" and / or "the" are not specifically singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of the clearly identified steps and elements, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0019] Flowcharts are used in this specification to illustrate the operations performed by the systems according to the embodiments of this specification. It should be understood that the preceding or subsequent operations are not necessarily executed precisely in order. On the contrary, the steps can be processed in reverse order or simultaneously. Also, other operations can be added to these processes, or one or more steps can be removed from these processes.

[0020] Figure 1 FIG. 1 is a schematic diagram of an application scenario of a system for storing project documents shown according to some embodiments of this specification. As Figure 1 shown, the application scenario 100 of the system for storing project documents (hereinafter simply referred to as the application scenario 100) may include a processing device 110, a network 120, a terminal 130, and a database 140. In some embodiments, the system for storing project documents can be used to implement the methods and / or processes disclosed in this specification.

[0021] The processing device 110 can be used to process data and / or information from various components of the application scenario 100 and / or external data sources. The processing device 110 can execute program instructions based on this data, information, and / or processing results, so as to perform one or more functions described in this specification. For example, the processing device 110 can generate a construction progress matrix corresponding to the target project; generate a first document directory of the target project according to the eigenvalue of the project characteristics of the target project; for the target matrix unit in the construction progress matrix, based on the construction area label and progress node label of multiple first project documents, determine the second project document corresponding to the target matrix unit from multiple first project documents, and generate a second document directory corresponding to the target matrix unit; based on the database label of the second project document, monitor the database corresponding to the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory.

[0022] In some embodiments, the processing device 110 can be a single server or a server group. In some embodiments, the server can include a processor, and the server group can be centralized or distributed. In some embodiments, the processing device 110 can be local or remote. In some embodiments, the processing device 110 can be implemented on a cloud platform. Merely by way of example, the cloud platform can include a private cloud, a public cloud, a hybrid cloud, etc., or any combination thereof.

[0023] The network 120 can include any suitable network that provides the ability to facilitate information and / or data exchange. In some embodiments, information and / or data can be exchanged between one or more components of the application scenario 100 through the network 120. For example, the processing device 110 can obtain the index information of the second project document through the network 120. The network 120 can include a local area network (LAN), a wide area network (WAN), a wired network, a wireless network, etc., or any combination thereof.

[0024] The terminal 130 refers to one or more terminal devices used by the user. In some embodiments, the user includes project managers, construction workers, acceptance personnel, etc. In some embodiments, the terminal 130 may include a mobile phone 130-1, a tablet 130-2, a computer 130-3, etc.

[0025] The database 140 can store data or information generated by other devices. In some embodiments, the database 140 can store project documents, for example, the first project document, the second project document, the third project document, the fourth project document, etc. In some embodiments, the database 140 can store the data and / or information processed by the processing device 110, such as monitoring information, etc. The database 140 can include one or more database components, and each database component can be an independent device or a part of other devices. The database 140 can be local or implemented through the cloud. In some embodiments, the database 140 can be implemented on a cloud platform.

[0026] In some embodiments, the database 140 includes a general database 141 and a business domain database 142.

[0027] The general database 141 is configured to store project documents that have no direct association with the construction business. For example, general project documents, general standard project documents, regulations and specifications, etc. Among them, the construction business includes but is not limited to construction task execution, construction task acceptance, and construction task supervision.

[0028] The business domain database 142 is configured to store project documents related to the construction business. For example, the business domain database 142 can store project documents related to construction business such as construction task acceptance, construction task execution, and construction task supervision (such as acceptance documents, task execution logs, etc.).

[0029] In some embodiments, the business domain database 142 can set up one or more sub-databases for storing project documents corresponding to different construction businesses. For example, the business domain database 142 can set up an acceptance business domain database to store documents related to construction task acceptance, such as acceptance reports, acceptance records, etc.; it can also set up a supervision business domain database to store documents related to construction task supervision, such as supervision logs, safety inspection records, etc.

[0030] It should be noted that the application scenario 100 is provided only for the purpose of illustration and is not intended to limit the scope of this specification. For those of ordinary skill in the art, various modifications or changes can be made according to the description of this specification. For example, the application scenario 100 can implement similar or different functions on other devices. However, the changes and modifications will not deviate from the scope of this specification.

[0031] Figure 2 It is an exemplary schematic diagram of a system for storing project documents shown in some embodiments of this specification. The system 200 for storing project documents includes a first generation module 210, a second generation module 220, a third generation module 230, and a monitoring module 240. The first generation module 210, the second generation module 220, the third generation module 230, and the monitoring module 240 are implemented by one or more processing devices.

[0032] The first generation module 210 is configured to generate a construction progress matrix corresponding to a target project. The construction progress matrix includes a plurality of matrix units, and each matrix unit corresponds to a progress node of a construction area of the target project. For more information about the construction progress matrix, refer to step 310.

[0033] The second generation module 220 is configured to generate a first document directory of the target project according to the eigenvalue of the project characteristics of the target project. The first document directory is configured to store the document labels of a plurality of first project documents corresponding to the target project. The document labels include construction area labels, progress node labels, and database labels. For more information about the first document directory, refer to step 320.

[0034] The third generation module 230 is configured to, for a target matrix unit in the construction progress matrix, based on the construction area label and the progress node label of a plurality of first project documents, determine a second project document corresponding to the target matrix unit from the plurality of first project documents, and generate a second document directory corresponding to the target matrix unit. The second document directory is configured to store the index information of the second project document. For more information about the second document directory, refer to step 330.

[0035] The monitoring module 240 is configured to monitor the database corresponding to the second project document based on the database label of the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory. For more information about monitoring the database, refer to step 340.

[0036] It should be noted that the above description of the system 200 for storing project documents and its module units is only for convenience of description, and does not limit this specification within the scope of the examples given. It can be understood that for those skilled in the art, after understanding the principle of the system, they may, without departing from this principle, make any combination of the various module units, or form a subsystem and connect it with other module units. In some embodiments, Figure 2The first generation module 210, the second generation module 220, the third generation module 230, and the monitoring module 240 disclosed in

[0037] Figure 3 is an exemplary flowchart of a method for storing project documents according to some embodiments of the present specification. As Figure 3 shown, process 300 includes the following steps. In some embodiments, process 300 may be executed by a processing device.

[0038] Step 310, generate a construction progress matrix corresponding to the target project.

[0039] The target project refers to a construction project for which project document management is to be carried out. The construction project may include various engineering categories. For example, the construction project may include construction projects of types such as building engineering, decoration engineering, installation engineering, municipal engineering, and landscaping engineering.

[0040] The target project involves multiple construction areas, and each construction area involves multiple progress nodes. Among them, the construction area refers to the area that needs to be constructed in the target project; the progress node refers to the construction stage that the construction area has to go through during the construction process. For example, taking the target project as a construction project of the building engineering category, the construction areas include each floor area, such as the 1st floor, the 2nd floor, etc.; for each construction area, its progress nodes include main construction, mechanical and electrical pre-embedding, and mechanical and electrical installation.

[0041] The construction progress matrix refers to a two-dimensional matrix corresponding to the target project. One dimension of this matrix corresponds to the construction area, and the other dimension corresponds to the progress node. The construction progress matrix may include multiple matrix units. The matrix unit refers to the constituent unit in the construction progress matrix. Each matrix unit corresponds to a construction area and a progress node in the target project. Taking the two-dimensional construction progress matrix as an example, the construction progress matrix is composed of multiple matrix units and can be represented by the following formula (1):

[0042] (1)

[0043] Wherein, represents the construction progress matrix, represents the th construction area, represents the th progress node, represents the matrix unit, are the number of rows and columns of the matrix, representing the number of construction areas and progress nodes respectively.

[0044] For example, for a target project with 2 floors and 2 progress nodes, the construction progress matrix can be expressed as .

[0045] In some embodiments, the processing device can construct a construction progress matrix according to the construction areas and progress nodes of the target project. For example, the processing device can obtain multiple construction areas and multiple progress nodes in the target project, and combine the multiple construction areas with the multiple progress nodes to form multiple matrix units, thereby generating a construction progress matrix. Among them, the construction areas and progress nodes of the target project can be extracted from the paper or electronic construction plan of the target project, or input by the user (such as project management personnel) through the terminal device. For example, the processing device can use Optical Character Recognition (OCR) technology to scan the paper construction plan of the target project and extract information related to the construction areas and progress nodes.

[0046] It should be understood that the progress nodes corresponding to different construction areas can be the same or different. When the progress nodes corresponding to different construction areas are the same, each matrix unit in the construction progress matrix is a valid matrix unit and will be used for project document management in subsequent steps. When the progress nodes corresponding to different construction areas are different, only some matrix units in the construction progress matrix are valid matrix units, and the remaining invalid matrix units will not be used for project document management in subsequent steps. For example, when construction area A has progress nodes 1 and 2, and construction area B only has progress node 1, the matrix unit corresponding to construction area B and progress node 2 is an invalid matrix unit and will not be used in subsequent steps.

[0047] Step 320, generate the first document directory of the target project according to the eigenvalue of the project characteristics of the target project.

[0048] Project characteristics refer to the characteristics of construction projects, including but not limited to project category, region, construction unit, construction company, etc. The eigenvalue refers to the specific value of the project characteristics. Each construction project has and only has a set of eigenvalues. For example, the eigenvalues of the project characteristics of the target project can be: the project category is building construction project, the construction region is Sichuan, etc.

[0049] The first document directory is a directory used to store information related to the first project documents corresponding to the target project (such as document name, document type, etc.). The first project documents refer to the project documents that may be generated and need to be stored during the entire progress of the target project. For example, the first project documents include the construction log, construction inspection documents, etc. of the target project.

[0050] In some embodiments, the first document directory is configured to store document tags of multiple first project documents corresponding to a target project. A document tag refers to a tag that identifies the attributes of a project document. The document tags include one or more of a construction area tag, a progress node tag, a database tag, an early warning rule tag, a handling rule tag, an associated unit tag, a construction task tag, etc. The document tags may also include basic information tags, such as tags corresponding to the document name and tags corresponding to the document type.

[0051] The construction area tag can identify the construction area corresponding to the project document. The progress node tag can identify the progress node corresponding to the project document. The database tag can identify the database in which the project document is stored. The early warning rule tag can identify the early warning rule associated with the project document. The handling rule tag can identify the handling rule associated with the project document. The associated unit tag can identify the construction unit associated with the project document. The construction task tag can identify the construction task associated with the project document. For more information about the early warning rule and the handling rule, see step 350 and step 360. For more information about the associated unit and the construction task, see step 360.

[0052] In some embodiments, the processing device can generate the first document directory in various ways. For example, default document directories corresponding to the characteristic values of the project characteristics are pre-stored in the database, and the corresponding default document directory can be obtained according to the characteristic value of the project characteristics of the target project as the first document directory. Alternatively, the user (such as a project manager) can input the first document directory according to the characteristic value of the project characteristics of the target project. For another example, the first document directory can be generated through the Figure 4 schematic process 400 shown in, and the specific description can be found later.

[0053] Step 330: Based on the construction area tag and the progress node tag of multiple first project documents, determine the second project document corresponding to the target matrix unit from the multiple first project documents, and generate the second document directory corresponding to the target matrix unit.

[0054] The target matrix unit refers to the matrix unit to be managed for project documents. In some embodiments, the target matrix unit can be any matrix unit in the construction progress matrix. In some embodiments, the target matrix unit can be any valid matrix unit in the construction progress matrix. For specific details, see the description of step 310. For convenience of description, the construction area and the progress node corresponding to the target matrix unit are referred to as the target construction area and the target progress node.

[0055] The second project document refers to the project document corresponding to the target matrix unit, that is, the project document that may be generated and needs to be stored when the target construction area is at the target progress node.

[0056] The second document directory is a directory for storing relevant information of the second project document corresponding to the target matrix unit. For example, the second document directory is configured to store index information of the second project document, etc. For another example, the second document directory is also configured to store document tags of the second project document.

[0057] In some embodiments, the form of the second project document may include an electronic document or a paper document. For example, an electronic document can be uploaded by a user to the corresponding business domain database through a terminal device; a paper document such as an original signature needs to be scanned and uploaded to the corresponding database by the user through optical character recognition technology.

[0058] In some embodiments, in response to detecting the generation of the second project document, the processing device may generate a virtual document object associated with the document in the target matrix unit. For example, for an electronic document, the processing device can automatically call the blockchain interface to complete the deposit operation when it is generated, and write content such as the digest information (such as hash value) and generation time of the electronic document to the blockchain; for a paper document, after the scanning and uploading are completed, the digest information can also be calculated and stored in the blockchain to achieve unified traceability and anti-tampering protection. Regarding how to detect the generation of the second project document, refer to step 340.

[0059] Among them, the virtual document object includes operation log information of the second project document. For example, the log information includes multiple data information such as the creation, upload, approval, receipt and dispatch, borrowing, and modification of the second project document. The data information in the log information can be hashed and compared with the timestamps and digest information recorded in the blockchain deposit or metadata mapped to verify the authenticity and integrity of the second project document.

[0060] The index information is used to locate the project document and realize the query and retrieval of the project document. In some embodiments, the entity of the second project document is stored in the database corresponding to the second project document, and the index information can point to the database where the second project document is actually stored. For example, the index information includes the path, storage address, or jump link of the database of the project document, etc. A user (such as a project manager) can locate to the database corresponding to the second project document through the index information. The index information can be updated as the status of the second project document changes. For example, when the second project document is generated and stored in its corresponding database, the index information will be updated, and the updated index information can point to the second project document itself, and the second project document itself can be located through the updated index information. For more detailed content about the index information, refer to step 340.

[0061] Figure 5 It is an exemplary schematic diagram of the second document directory shown in some embodiments of this specification.

[0062] The second document directory can list various project documents corresponding to each target matrix unit. For example, Figure 5 As shown, the directory hierarchy structure on the left side of the second document directory shows the project documents corresponding to each target matrix unit (i.e., each target construction area and its target progress node). In the directory hierarchy structure, the first-level directory is the construction area of the target matrix unit, such as the first floor, etc.; the second-level directory is the progress node of the target matrix unit, such as the main body, etc.; the third-level directory is the second project document corresponding to the target matrix unit, such as the acceptance document, rectification form, project log, meeting log, etc. The first-level directory and the second-level directory correspond to a matrix unit in the construction progress matrix.

[0063] By selecting a certain project document in the second document directory, relevant information of the project document can be obtained. For example, Figure 5 As shown, on the right side of the second document directory, the project name, storage address (i.e., index information), upload time, uploader, document preview, etc. of the second project document can be displayed.

[0064] In some embodiments, each second project document corresponds to a construction task in the progress node of the target matrix unit, and the second project documents in the second document directory can be sorted according to the time of the construction tasks.

[0065] In some embodiments of this specification, through the directory hierarchy structure of the second document directory, the hierarchical relationship in the construction progress matrix can be mapped, so that the management of project documents can be carried out layer by layer according to the construction area - progress node - construction document, improving the query efficiency of project documents.

[0066] In some embodiments, the processing device can determine the second project document corresponding to the target matrix unit based on the construction area label and progress node label of the first project document, and then generate a second document directory storing the relevant information of the second project document. Specifically, the processing device can screen out the first project documents with the construction label being the target construction area and the progress node label being the target progress node from the first project documents in the first document directory, and use these screened-out first project documents as the second project documents. The second project documents can inherit the document labels of the first project documents. For example, the document labels that the second project documents can inherit include basic information labels, construction area labels, progress node labels, database labels, warning rule labels, handling rule labels, associated unit labels, construction task labels, etc. Then, the processing device can generate a second document directory based on the document labels of the second project documents. The basic information such as the document name and type in the second document directory can be determined based on the basic information label, and the index information can be determined based on the database label. For example, based on the database label, it can be determined which database the second project document will be stored in, and the address or link of this database can be used as the index information of the second project document.

[0067] In some embodiments, a user (such as a project manager) may manually modify the second document directory generated by the processing device according to requirements through a terminal.

[0068] Step 340: Monitor the database corresponding to the second project document based on the database label of the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory.

[0069] The status changes of the second project document include generation, modification, deletion, etc. As described in step 330, when the second document directory is generated, the index information of the second project document points to the database where it is located. When it is monitored that the second project document is generated, the index information can be updated to point to the second project document itself. For example, the index information can be updated to the jump link corresponding to the second project document, and the second project document can be opened through this link. When it is monitored that the second project document is deleted, the index information can be updated back to point to its corresponding database. When the storage address of the second project document is modified, the index information can be updated to point to its new storage address.

[0070] In some embodiments, the processing device may set a listener in the database corresponding to the second project document based on the database label of the second project document to monitor the status change of the second project document.

[0071] In some embodiments, the document label further includes an early warning rule label and a handling rule label. The process 300 further includes step 350 and step 360.

[0072] Step 350: In response to monitoring the generation of the second project document, monitor whether the associated data of the second project document conforms to the early warning rule according to the early warning rule label of the second project document.

[0073] The early warning rule defines the rules that the second project document and / or its associated data need to meet, otherwise an early warning will be triggered (such as sending an early warning prompt to the user). For example, the early warning rule is configured to constrain the generation time of the associated data of the second project document. If the generation time of the associated data of the second project document conforms to the early warning rule, no early warning will be triggered; otherwise, an early warning will be triggered.

[0074] Associated data refers to data associated with a second project document. The manifestation form of the associated data can be a project document or other forms (such as user input data, instructions, etc.). Generally speaking, the conduct of construction operations (such as construction task execution, construction task acceptance, construction task supervision) needs to comply with specific project specifications. There may be specific associations between different construction operations, which also makes there be specific associations between the data corresponding to different construction operations. The associations between data can be determined according to project specifications or specified by users.

[0075] In some embodiments, the associated data may include pre-data and post-data. Pre-data refers to the data that needs to exist before the generation of the second project document. That is to say, the generation of the second project document can only be carried out after the pre-data exists. For example, the construction of the secondary structure can only be carried out after the acceptance of the main body of the first floor. Therefore, the acceptance form corresponding to the main body of the first floor is the pre-data of the construction log corresponding to the construction of the main body of the second floor. Post-data refers to the data that needs to be generated after the generation of the second project document. That is, before the generation of the post-data, the second document must exist. For example, after the acceptance of the concealed reinforcement, concrete pouring needs to be carried out. Then, the construction log corresponding to the concrete pouring is the post-data of the acceptance form corresponding to the concealed reinforcement.

[0076] In some embodiments, the associated data includes the third project documents related to the second project document among multiple first project documents. That is to say, the associated data is also a project document related to the target project. The third project document can be a pre-project document or a post-project document of the second project document. The construction area corresponding to the third project document can be the target construction area (that is, the second project document and the third project document correspond to the same construction area), or it can be other construction areas (that is, the second project document and the third project document correspond to different construction areas). The progress node corresponding to the third project document can be the target progress node (that is, the second project document and the third project document correspond to the same progress node), or it can be other progress nodes (that is, the second project document and the third project document correspond to different progress nodes).

[0077] The generation time of the associated data refers to the generation point of the pre-data or post-data relative to the generation of the second project document. For example, the second project document can be a construction log. The warning rule stipulates that after the construction log is generated, a supervision approval document should be generated within 24 hours. Then, the supervision approval document, as the post-data of the construction log, the 24 hours is the generation time requirement for this post-data.

[0078] The processing device can determine its corresponding warning rule based on the warning rule label of the second project document. The warning rule label is a label that identifies the warning rule associated with the project document. For example, project managers can preset the warning rule labels for various types of project documents in the general document directory library. When the first project document is determined from the general document directory library, its warning rule label is inherited from the general document directory library; when the second project document is determined, its warning rule label is inherited from the first project document; the processing device can determine its warning rule based on the warning rule label of the second project document. In some embodiments, project managers can also modify the warning rule of the second project document through the terminal according to requirements to meet the actual needs of different projects.

[0079] Furthermore, the processing device can obtain monitoring information related to the associated data. The monitoring information refers to the relevant information obtained by monitoring the state changes of the associated data. For example, the monitoring information includes the generation, modification, deletion, generation timestamp, modification timestamp, etc. of the associated data. In some embodiments, the processing device can obtain the monitoring information through various methods. For example, the processing device can obtain the monitoring information based on the log record of the associated data, and the log record can include the historical record of the user operating on the associated data, the upload record of the associated data, the state changes of the associated data, etc.

[0080] In some embodiments, when the associated data includes the third project document, the monitoring information related to the third project document can be obtained according to the database label of the third project document. For example, the processing device can determine the storage database of the third project document based on the database label of the third project document, and use a listener to monitor the third project document in this storage database to obtain the monitoring information related to the third project document.

[0081] The processing device can determine whether the associated data complies with the warning rule based on the monitoring information. For example, the warning rule is that after the second project document is generated, the post-data should be generated within 24 hours. If the monitoring information of the post-data indicates that its generation time exceeds 24 hours, then the post-data does not comply with the warning rule.

[0082] When the associated data does not comply with the warning rule, step 360 can be executed.

[0083] Step 360, implement the corresponding handling operation based on the handling rule label corresponding to the second project document.

[0084] The handling operation refers to the measures to be taken when the associated data does not comply with the warning rules. For example, the handling operations include pushing messages, intercepting data, intercepting processes, revoking permissions, etc. Pushing a message means sending a warning notice to the relevant users of the associated data. Pushing a message means sending a warning prompt or operation notice to the corresponding responsible unit according to the associated unit label carried by the associated data. Intercepting a document means prohibiting operations such as creating, uploading, or approving associated data that does not meet the warning rules to ensure the maintenance of the sequential dependency relationship of the process. Intercepting the process suspends or stops operations such as creating, uploading, or approving associated data until it complies with the warning rules. Revoking permissions means temporarily restricting or revoking specific operation permissions of the relevant responsible unit according to the associated unit label of the associated data to prevent continued non-compliant operations.

[0085] The handling rule label is a label that identifies the handling rules associated with the project document. The determination method of the handling rule label is similar to the warning rule label described in step 350 and will not be elaborated here.

[0086] In some embodiments, the document label further includes an associated unit label. When the associated data includes a third project document, the implementation of the corresponding handling operation based on the handling rule label further includes: sending a notice to the associated unit corresponding to the third project document according to the associated unit label of the third project document.

[0087] The associated unit refers to a unit that has a direct or indirect relationship with the construction area and progress nodes of the project during the project construction process. For example, the associated units can include construction units, design units, supervision units, etc. In some embodiments, different associated units assume different project document management responsibilities. For example, the construction unit is responsible for submitting project documents such as construction logs and quality acceptance forms; the supervision unit is responsible for submitting project documents such as acceptance forms and supervision logs; the design unit is responsible for submitting project documents such as technical disclosures and construction change documents.

[0088] The associated unit label is used to identify the construction unit associated with the project document. The determination method of the associated unit label is similar to the warning rule label described in step 350 and will not be elaborated here.

[0089] In some embodiments, the processing device can determine the associated unit of the third project document by identifying the associated unit label of the third project document. When the handling rule label indicates that the handling operation corresponding to the third project document includes pushing a message, the processing device can send a notice to the determined associated unit.

[0090] In some embodiments of this specification, based on the warning rule tags of the second project document, the monitoring and compliance evaluation of associated data can be realized to ensure that the associated data is submitted within the specified time, avoiding the lag of the construction task progress caused by the delay of the associated data. In this way, project supervision and progress promotion can be realized based on document management, giving play to other functions of the document in addition to information recording.

[0091] In addition, since construction projects often involve multiple responsible units, the uploading and rectification of documents require collaborative work among multiple units. When the associated data is the third project document, the associated units can be quickly identified and notifications can be sent based on its associated unit tags. This can reduce the manual communication cost among multiple units, improve the automation level of project document management, and ensure the efficient circulation of documents among multiple responsible units.

[0092] In some embodiments of this specification, by generating a construction progress matrix corresponding to the target project, document management can be realized based on the target matrix unit. The relevant information of the second project document corresponding to the target matrix unit is centrally stored in the second document directory, enabling the second project document to be managed in a structured manner. The second project document itself is stored in the corresponding database, and its storage path may change due to database migration, file renaming, version update, etc. Through the database tag for the database listener corresponding to the second project document, the status change of the second project document can be automatically detected and the index information can be updated in real time, ensuring that the status of the project document is always synchronized with the construction progress, avoiding lags or errors caused by manual maintenance of the index, ensuring that users can access the latest version of the project document, and improving the intelligent level of construction management.

[0093] On the other hand, compared with the traditional file management method, the document management method in this specification can establish a logical mapping between project documents and construction areas and progress nodes, making the association between project documents and construction operations closer. Since construction operations are the hub for the cooperation of various functional units, when the association between project documents and construction operations is closer, the association between project documents and functional departments can also be closer, and project documents can thus play a greater role (such as compliance judgment, warning handling, etc.).

[0094] It should be noted that the above description of process 300 is only for illustration and example, and does not limit the scope of application of this specification. For those skilled in the art, various modifications and changes can be made to the process under the guidance of this specification. However, these modifications and changes are still within the scope of this specification.

[0095] Figure 4 It is an exemplary schematic diagram of determining the first project document and generating the first document directory shown in some embodiments of this specification.

[0096] As Figure 4 shown, the processing device can match the corresponding alternative project document 430 from the general document directory library 420 according to the feature value 410 of the project features of the target project; based on the alternative project document 430, determine the first project document 440 corresponding to the target project and generate the first document directory 450.

[0097] The general document directory library refers to a document directory library that is common to multiple categories of projects and is used to store information about project documents corresponding to various projects. In some embodiments, the general document directory library is configured to store the correspondence between the reference values of project features and various types of project documents, as well as the document tags of each type of project document. The document tags of project documents can be set by users.

[0098] The reference value refers to the typical feature value of project features. The general document directory library can store the correspondence between the reference values of project features and various types of project documents, that is, the reference values of project features corresponding to various types of project documents. For a certain type of project document, if the reference value of the project features corresponding to it is A, it means that projects with a feature value of A usually have this type of project document. For example, for the concealed acceptance form of steel bars, the reference values of the project category and region are "building construction project" and "Guangdong Province and Zhejiang Province" respectively, indicating that building construction projects in Guangdong Province and Zhejiang Province usually require the concealed acceptance form of steel bars.

[0099] In some embodiments, the general document directory library can be constructed by users. In some embodiments, the general directory library can be obtained by statistically analyzing the historical data of projects. For example, as Figure 4 shown, the general document directory library can be constructed in the following manner: obtain the sample document directory 421 of multiple sample projects and the feature values 422 of the project features of each sample project; based on the sample document directory, determine the distribution of the feature values of the project features corresponding to various types of project documents 423; based on the distribution of the feature values corresponding to various types of project documents, determine the reference values 424 of the project features corresponding to each type of project document.

[0100] The sample projects can be determined based on historical data. For example, multiple sample projects can be determined from multiple historical construction projects and are used to generate the general document directory library.

[0101] The sample document directory refers to the document directory corresponding to the sample project, which stores information about the sample documents involved in the sample project. In some embodiments, the processing device can obtain all the historical documents of the sample project as the sample documents and generate the sample document directory based on the information about the sample documents (such as document name, document generation time, document uploader, document type).

[0102] In some embodiments, the sample document directory includes a record-filing project document directory and a project management document directory. Among them, the sample documents involved in the record-filing project document directory (which can also be referred to as record-filing project documents) are project documents that need to be archived according to government or construction project industry regulations. For example, process acceptance documents, sub-project acceptance documents, supervision logs, pouring orders, etc. In some embodiments, the record-filing project document directory records the hierarchical division of the record-filing project documents. For example, the first-level directory is the project category, and the second-level directory is the document category, etc.

[0103] The sample documents involved in the project management document directory (which can also be referred to as project management documents) are documents used for internal management of the participants in the sample project. For example, it includes meeting records, construction daily reports, etc. of the sample project.

[0104] In some embodiments, the storage format of the record-filing project documents in the record-filing project document directory is [document type, region, project category, record-filing requirements], and the storage format of the project management documents in the project management document directory is [document type, region, project category, construction unit, construction company].

[0105] In some embodiments, the processing device can obtain record-filing document entries and filing requirements for different regions and different project categories based on local government regulations, industry standards, industry databases, etc.; construct a record-filing project document directory based on the record-filing document entries and filing requirements; obtain the historical document data of the sample project, and accordingly construct a project management document directory; merge and deduplicate the record-filing project document directory and the project management document directory to determine the sample document directory. Among them, the user (such as a project manager) can manually adjust the sample document directory according to actual needs.

[0106] In some embodiments, the processing device can identify the storage format of the project management documents to obtain the eigenvalue of the project characteristics of the sample project. For example, if the storage format of the project management documents used in the sample project is [document type, region, project category, construction unit, construction company], the processing device can parse this storage format and extract the eigenvalues corresponding to the region, project category, construction unit, and construction company of the sample project (that is, the eigenvalues of each project characteristic).

[0107] For each type of project document, based on the sample document directory, the eigenvalue distribution of the project characteristics corresponding to this type of project document can be determined, and this eigenvalue distribution can reflect the occurrence frequency of each eigenvalue of the sample project storing this type of project document.

[0108] Specifically, the processing device can, based on the sample document directory, count the occurrence frequencies of each document category under different eigenvalue conditions, so as to determine the eigenvalue distribution of the project characteristics corresponding to various project documents. For example, for acceptance documents, the processing device can count the occurrence frequencies in sample projects in different regions, in sample projects of different project categories, in sample projects of different construction units, in sample projects of different construction contractors, etc., so as to statistically determine the eigenvalue distribution of the project characteristics corresponding to the acceptance documents. Taking regions as an example, if the occurrence frequencies of acceptance documents in sample projects in Sichuan, Guangdong, and Hangzhou are A, B, and C respectively, then the eigenvalue distribution of the project characteristic of region corresponding to them is A, B, and C.

[0109] In some embodiments, for various project documents, the processing device can, based on the first frequency threshold and its eigenvalue distribution, screen out one or more eigenvalues with occurrence frequencies higher than the first frequency threshold as reference values. Among them, the first frequency threshold can be preset by the user according to needs, or can be determined based on the total occurrence times of various project documents (for example, the occurrence frequency threshold can be 20% of the total occurrence times). Continuing the above example, assuming that the occurrence frequencies A and B exceed the first frequency threshold, and C is less than the first frequency threshold, then Sichuan and Guangzhou will be used as reference values, and Hangzhou will be excluded.

[0110] In some embodiments, if the project document is a filing document required to be archived by the government or the construction industry, then even if the occurrence frequency of the project characteristics corresponding to the project document is lower than the first frequency threshold, it will not be excluded.

[0111] In some embodiments of this specification, by establishing a general document directory library, it can provide a data basis for the document management of various construction projects, enabling all construction projects to follow a unified document management standard and ensuring the consistency of project document management. During the construction process of the general document directory library, by statistically determining the eigenvalue distribution and determining the high-frequency eigenvalues as reference values, the most common eigenvalues can be retained for generating the first project document directory, avoiding the influence of occasionally occurring eigenvalues. At the same time, mandatory filing documents will not be accidentally excluded due to low frequency, ensuring the compliance of project document management, preventing the omission of filing documents required by the government or the industry, and making the construction of the general document directory library more in line with the general situation of the actual construction industry.

[0112] The alternative project document refers to the project document in the general document directory library that matches the target project. In some embodiments, the processing device may screen the project documents with the same feature values as the target project based on the reference values of the project features corresponding to each type of project document in the general document directory library. For example, if the reference value of a certain document is the same as the feature value of the project features of the target project, then this document can be an alternative project document. Continuing with the above example, if the region to which the target project belongs is Sichuan, and the reference value of the region corresponding to the acceptance document in the general document directory library includes Sichuan, then the acceptance document will be selected as an alternative project document; if the region to which the target project belongs is Nanjing, and the reference value of the region corresponding to the acceptance document in the general document directory library does not include Nanjing, then the acceptance document will not be selected as an alternative project document.

[0113] In some embodiments, the processing device may directly use the alternative project document as the first project document corresponding to the target project and generate a first document directory. In some embodiments, the processing device may screen the alternative project documents to determine the first project document and generate a first document directory. For example, the occurrence frequency of the alternative project documents in the sample project can be determined, and the alternative project documents with an occurrence frequency less than the second frequency threshold are excluded. The second frequency threshold can be preset according to requirements. The user can manually adjust the first project document according to actual needs. After determining the first project document, the relevant information (such as document tags) of the first project document in the general document directory library will be inherited and stored in the first document directory.

[0114] In some embodiments of this specification, there are various types of construction projects, and different engineering categories (such as building construction, municipal engineering) require different documents. By matching the backup project documents from the general document directory library based on the feature values of the target project, and then screening the alternative project documents, and finally generating the first document directory, the first project document can be made complete and meet the requirements of the target project, and the influence of low-frequency project documents can be avoided. At the same time, the user can manually adjust the first project document to meet personalized needs without affecting project document management.

[0115] Figure 6 It is an exemplary flowchart of construction progress management based on the updated second project document shown in some embodiments of this specification. In some embodiments, process 600 can be executed by the processing device. In some embodiments, process 600 can be executed after step 340.

[0116] As various construction operations in the target project are carried out, corresponding second project documents will be generated or updated, and these status changes will cause the update of the index information in the second document directory. Due to the association between the construction operations and the second project documents, the updated second document directory can reflect the construction progress changes of the target project. Therefore, construction progress management can be carried out based on the updated second document directory.

[0117] Step 610: Determine whether the target progress node corresponding to the target matrix unit meets the progress node update condition according to the updated second document directory.

[0118] The target progress node refers to the progress node corresponding to the target matrix unit.

[0119] The update condition of the progress node refers to the prerequisite conditions that need to be met for the target progress node to advance to the next progress node in the target project.

[0120] In some embodiments, the progress node update condition includes that a specific number (such as all) of second project documents corresponding to the target progress node or one or more specific second project documents (such as acceptance documents) have been successfully uploaded. For example, when the target progress node is the main body of the first floor, the progress node update condition includes that the acceptance document of the main body has been successfully uploaded.

[0121] As described in step 340, when the status of the second project document changes, the index information in the updated second document directory can be generated. The processing device can determine whether the target progress node meets the progress node update condition based on the index information in the updated second document directory.

[0122] Step 620: In response to determining that the target progress node meets the progress node update condition, determine the associated matrix unit associated with the target matrix unit based on the association relationship information related to the construction progress matrix.

[0123] The associated matrix unit refers to other matrix units that have an association relationship with the target matrix unit. In some embodiments, the associated matrix unit can be one or more. Other matrix units may correspond to the same or different construction areas as the target matrix unit. That is to say, the mutually associated matrix units can be located in the same row (or column) of the construction progress matrix, or in different rows (or columns) of the construction progress matrix.

[0124] The association relationship information is used to reflect the association relationships between different matrix units in the construction progress matrix. There are sequential dependencies between the progress nodes and construction areas of different matrix units in the construction progress matrix, including but not limited to progress node dependencies and construction area influence relationships. Exemplarily, the progress node dependency can be that certain progress nodes must be completed before other related progress nodes can be executed. For example, the construction task in the main structure must be completed before the construction task of electrical and mechanical pre-embedding can be carried out. The construction area influence relationship can be that a certain construction area may affect the progress of other construction areas, such as the upper layer construction needs to wait for the lower layer to be completed.

[0125] The association relationship information can be determined in various ways. For example, the association relationship information can be determined based on handover documents such as the construction plan of the target project. Another example is that the association relationship information can be manually input by the user through a terminal device.

[0126] The processing device can determine the associated matrix units associated with the target matrix unit based on the association relationship information of the target matrix unit. For example, in response to determining that the target progress node meets the progress node update condition, the processing device can retrieve the construction progress matrix based on the association relationship information to determine the associated matrix units affected by the target matrix unit.

[0127] Step 630, send a construction notice to the target associated unit of the associated matrix unit.

[0128] The target associated unit refers to the associated unit corresponding to the associated matrix unit. The target associated unit can be determined based on the corresponding relationship between each matrix unit in the construction progress matrix and the participating units of the target project. The processing device can send a construction notice to the terminal of the person in charge of the target associated unit. The construction notice is used to inform that a certain construction task of the target progress node has been completed and the construction task of the associated matrix unit needs to be started.

[0129] In some embodiments, the document tags further include associated unit tags and construction task tags. Sending a construction notice to the target associated unit of the associated matrix unit includes: determining the fourth project document corresponding to the associated matrix unit based on the construction area tags and progress node tags of multiple first project documents; determining the target fourth project document based on the construction task tag of the fourth project document, and the construction time corresponding to the target fourth project document meets the preset conditions; determining the target associated unit based on the associated unit tag of the target fourth project document and sending a notice to the target associated unit.

[0130] The fourth project document refers to the document corresponding to the associated matrix unit. The processing device can screen out the project documents in the first project documents that have the same construction area and progress node as the associated matrix unit based on the construction area tags and progress node tags of the first project documents, and use them as the fourth project document.

[0131] The target fourth project document refers to the project document that meets the preset conditions in the fourth project document. In some embodiments, the processing device may determine the target fourth project document according to the construction task label of the fourth project document. The construction task label is a label that identifies the construction task associated with the project document. The determination method of the construction task label is similar to the warning rule label described in step 350 and will not be elaborated here.

[0132] For example, for each fourth project document, the processing device may determine whether the construction time of the construction task corresponding to the fourth project document meets the preset conditions according to the construction task label of the fourth project document; if the preset conditions are met, it is determined that the fourth project document is the target fourth project document. For example, the preset conditions may be that the construction time is within 7 days, and the construction time is the first N of the construction tasks corresponding to all fourth project documents. That is, when starting the construction work related to the association matrix unit, the construction task corresponding to the target fourth project document will be carried out first (such as within 7 days).

[0133] Furthermore, the processing device may determine the target associated unit based on the associated unit label of the target fourth project document and send a notice to the target associated unit.

[0134] In some embodiments of this specification, by using the construction task label to screen the target fourth project documents that meet the construction time requirements, it is possible to preferentially send notices to the target associated units with earlier construction times to ensure the progress of the construction tasks as planned, reduce construction lags caused by project document delays, and improve the execution efficiency of the construction tasks. In addition, based on the associated unit label, the target associated unit can be quickly and accurately determined, and a construction notice can be sent to the target associated unit to ensure that the submission and approval of construction documents are all executed on time by the relevant units, reduce management loopholes caused by untimely manual notifications, and improve the intelligent level of project document management.

[0135] In some embodiments of this specification, through the updated second document directory, it is possible to determine whether the target progress node corresponding to the target matrix unit meets the progress node update conditions, ensure the progress of the construction as planned, and improve the construction efficiency; by using the association relationship information related to the construction progress matrix, determine the associated matrix unit associated with the target matrix unit, and send a construction notice to the target associated unit, which can ensure the orderly connection between different construction tasks, avoid breaks in construction tasks and resource waste, improve the overall construction coordination efficiency, and ensure that changes in the construction progress can be promptly transmitted to the relevant responsible units. Through the above methods, construction progress management based on project documents is realized, and the automation and efficiency of construction progress management are improved.

[0136] It should be noted that the above description of process 600 is only for illustration and example, and does not limit the scope of application of this specification. For those skilled in the art, various modifications and changes can be made to the process under the guidance of this specification. However, these modifications and changes are still within the scope of this specification.

[0137] Figure 7 It is an exemplary schematic diagram of a progress display table shown in some embodiments of this specification.

[0138] In some embodiments, the processing device can generate a progress display table corresponding to the construction progress matrix and mark the display cell corresponding to the target matrix cell in the progress display table. Specifically, the processing device can determine the progress information of the target matrix cell based on the updated second document directory; and mark the display cell corresponding to the target matrix cell in the progress display table based on the progress information.

[0139] The progress display table is used to visually represent the construction progress of each construction area and progress node. As Figure 7 shown, the progress display table 710 is a two-dimensional table, and the vertical axis and the horizontal axis respectively represent the construction areas and progress nodes in the construction progress matrix. In some embodiments, the processing device can generate a progress display table based on the construction areas and progress nodes in the construction progress matrix. For example, the processing device takes the construction areas as the rows of the progress display table and the progress nodes as the columns according to the construction progress matrix, so as to generate the table structure of the progress display table.

[0140] A display cell refers to the basic unit of the progress display table. Each matrix cell in the construction progress matrix can correspond to a display cell in the progress display table. The processing device can determine its corresponding display cell based on the construction area and progress node of the target matrix cell.

[0141] The progress information reflects the completion status of the relevant construction tasks of the target matrix cell. For example, the progress information includes the status of each construction task (not started, in progress, completed), the completion percentage of all construction tasks, etc. The progress information can be determined based on the updated second document directory. For example, for each construction task, the processing device can determine whether the acceptance form of the construction task has been uploaded based on the updated second document directory; if the acceptance form has been uploaded, further obtain the acceptance form to confirm whether the construction task has passed the acceptance; if it has passed the acceptance, confirm that the construction task has been completed. In some embodiments, the progress information can be in the form of a percentage, representing the completion percentage of all construction tasks of the target matrix cell.

[0142] In some embodiments, the processing device may label the display cell corresponding to the target matrix cell in the progress display table based on the progress information. For example, the processing device may label the display cell corresponding to the target matrix cell by using methods such as color labeling, percentage labeling, text labeling, etc.

[0143] Exemplarily, as Figure 7 shown, the third color mark indicates that all construction tasks have been completed, the second color mark indicates that some construction tasks have been completed, and the first color mark indicates that all construction tasks have not started; the percentage represents the completion ratio of all construction tasks, 100% means that all construction tasks have been completed, 50% means that half of the construction tasks have been completed, 0% means that all construction tasks have not started, etc.

[0144] In some embodiments of this specification, by generating a progress display table of the construction progress matrix and labeling the display cell corresponding to the target matrix cell in the progress display table, the user can intuitively view the construction progress status of the target project, improving the visual display effect of the construction progress; through the labeling of the display cell, the construction progress can be monitored in real time to prevent the lag of the construction progress.

[0145] Some embodiments of this specification also provide a computer-readable storage medium, and the storage medium stores computer instructions. When the computer reads the computer instructions in the storage medium, the computer executes the method described in any one of the above embodiments.

[0146] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only an example and does not constitute a limitation to this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements, and corrections to this specification. Such modifications, improvements, and corrections are proposed in this specification, so such modifications, improvements, and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0147] Meanwhile, this specification uses specific words to describe the embodiments of this specification. Such as "one embodiment", "an embodiment", and / or "some embodiments" mean a certain feature, structure, or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "an embodiment" or "one embodiment" or "an alternative embodiment" mentioned twice or more at different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this specification can be appropriately combined.

[0148] In addition, unless clearly stated in the claims, the order of the processing elements and sequences, the use of numerical and alphabetical characters, or the use of other names described in this specification are not used to limit the order of the processes and methods of this specification. Although some currently useful embodiments of the invention are discussed through various examples in the above disclosure, it should be understood that such details are for illustrative purposes only. The appended claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that conform to the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only through software solutions, such as installing the described system on existing servers or mobile devices.

[0149] Similarly, it should be noted that, in order to simplify the presentation of the disclosure in this specification and thus help the understanding of one or more embodiments of the invention, in the foregoing description of the embodiments of this specification, sometimes multiple features are merged into one embodiment, drawing, or description thereof. However, this method of disclosure does not mean that the features required by the subject matter of this specification are more than those mentioned in the claims. In fact, the features of the embodiments are fewer than all the features of the individual embodiments disclosed above.

[0150] In some embodiments, numbers are used to describe components and the quantity of attributes. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximate" or "substantially" in some examples. Unless otherwise stated, "about", "approximate" or "substantially" indicate that the stated number allows a variation of ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, and such approximate values may vary according to the characteristics required by individual embodiments. In some embodiments, the numerical parameters should consider the specified significant digits and adopt the method of retaining the general number of digits. Although the numerical ranges and parameters used in some embodiments of this specification to confirm the breadth of their scope are approximate values, in specific embodiments, such numerical settings are as precise as possible within the feasible range.

[0151] For each patent, patent application, patent application publication, and other materials cited in this specification, such as articles, books, specifications, publications, documents, etc., their entire contents are hereby incorporated into this specification by reference. This excludes the application history documents that are inconsistent with or conflict with the content of this specification, as well as the documents that limit the broadest scope of the claims of this specification (currently or subsequently appended to this specification). It should be noted that if there are any inconsistencies or conflicts between the descriptions, definitions, and / or uses of terms in the attached materials of this specification and the content described in this specification, the descriptions, definitions, and / or uses of terms in this specification shall prevail.

[0152] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of this specification. Therefore, by way of example and not limitation, alternative configurations of the embodiments of this specification may be regarded as consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly presented and described in this specification.

Claims

1. A method for storing project documents, characterized in that, The method includes: Generating a construction progress matrix corresponding to a target project, where the construction progress matrix includes a plurality of matrix units, and each matrix unit corresponds to a progress node of a construction area of the target project; Generating a first document directory for the target project according to the eigenvalue of the project characteristics of the target project, where the first document directory is configured to store document tags of a plurality of first project documents corresponding to the target project, and the document tags include construction area tags, progress node tags, and database tags; For a target matrix unit in the construction progress matrix, based on the construction area tags and progress node tags of the plurality of first project documents, determining a second project document corresponding to the target matrix unit from the plurality of first project documents, and generating a second document directory corresponding to the target matrix unit, where the second document directory is configured to store index information of the second project document; Monitoring the database corresponding to the second project document based on the database tag of the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory.

2. The method according to claim 1, wherein The generating the first document directory for the target project includes: Matching corresponding alternative project documents from a general document directory library according to the eigenvalue of the project characteristics of the target project, where the general document directory library is configured to store the reference values of project characteristics and the corresponding relationships between various types of project documents, as well as the document tags of each type of project document; Based on the alternative project documents, determining the first project documents corresponding to the target project and generating the first document directory.

3. The method according to claim 2, wherein The general document directory library is constructed by the following method: Obtaining the sample document directories of a plurality of sample projects and the eigenvalue of the project characteristics of each sample project; Based on the sample document directories, determining the eigenvalue distribution of the project characteristics corresponding to various types of project documents; Based on the eigenvalue distribution corresponding to various types of project documents, determining the reference value of the project characteristics corresponding to each type of project document.

4. The method according to claim 1, wherein The document tags further include warning rule tags and handling rule tags, and the method further includes: In response to monitoring the generation of the second project document, determining the warning rule of the second project document according to the warning rule tag of the second project document, where the warning rule is configured to restrict the generation time of the associated data of the second project document; Obtaining monitoring information related to the associated data, and determining whether the associated data conforms to the warning rule based on the monitoring information; In response to determining that the associated data does not conform to the warning rule, implementing a corresponding handling operation based on the handling rule tag.

5. The method according to claim 4, wherein The document tags further include associated unit tags, and the associated data includes third project documents related to the second project document in the plurality of first project documents: Obtaining the monitoring information related to the associated data includes: obtaining the monitoring information related to the third project document according to the database tag of the third project document; Performing a corresponding handling operation based on the handling rule tag includes: sending a notice to the associated unit corresponding to the third project document according to the associated unit tag of the third project document.

6. The method according to claim 1, characterized in that The method further includes: Determining whether the target progress node corresponding to the target matrix unit meets the progress node update condition according to the updated second document directory; In response to determining that the target progress node meets the progress node update condition, determining an associated matrix unit associated with the target matrix unit based on the association relationship information related to the construction progress matrix; Sending a construction notice to the target associated unit of the associated matrix unit.

7. The method according to claim 6, characterized in that, The document tag further includes an associated unit tag and a construction task tag. Sending a construction notice to the target associated unit of the associated matrix unit includes: Determining a fourth project document corresponding to the associated matrix unit based on the construction area tag and the progress node tag of the plurality of first project documents; Determining a target fourth project document based on the construction task tag of the fourth project document, where the construction time corresponding to the target fourth project document meets a preset condition; Determining the target associated unit based on the associated unit tag of the target fourth project document and sending a notice to the target associated unit.

8. The method according to claim 1, wherein The method further includes: Generating a progress display table corresponding to the construction progress matrix, where the progress display table includes display cells corresponding to the plurality of matrix units; Determining the progress information of the target matrix unit according to the updated second document directory; Based on the progress information, marking the display cell corresponding to the target matrix unit in the progress display table.

9. A system for storing project documents, characterized in that, The system includes: A first generation module configured to generate a construction progress matrix for a target project, where the construction progress matrix includes a plurality of matrix units, and each matrix unit corresponds to a progress node of a construction area of the target project; A second generation module configured to generate a first document directory for the target project according to the eigenvalue of the project characteristics of the target project, where the first document directory is configured to store document tags of a plurality of first project documents corresponding to the target project, and the document tags include a construction area tag, a progress node tag, and a database tag; A third generation module configured to determine a second project document corresponding to the target matrix unit from the plurality of first project documents based on the construction area tag and the progress node tag of the plurality of first project documents for the target matrix unit in the construction progress matrix, and generate a second document directory corresponding to the target matrix unit, where the second document directory is configured to store index information of the second project document; A monitoring module configured to monitor the database corresponding to the second project document based on the database tag of the second project document, so as to monitor the status change of the second project document and update the corresponding index information in the second document directory.

10. A computer-readable storage medium, characterized in that, The storage medium stores computer instructions, and when a computer reads the computer instructions in the storage medium, the computer executes the method according to any one of claims 1 to 8.

Images