A technical document management system under a construction management system
By using tree-structured management and form configuration, the relationship between technical documents and other modules is established, which solves the problem of low efficiency in technical document retrieval in the construction management system, realizes multi-dimensional retrieval and statistics, improves the applicability of data utilization and management, and promotes the productization and data interconnection of the construction management system.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- POWERCHINA HUADONG ENG CORP LTD
- Filing Date
- 2022-04-05
- Publication Date
- 2026-07-21
AI Technical Summary
The existing construction management system suffers from low efficiency in retrieving technical documents, lacks associated management, makes data difficult to utilize, has many process nodes leading to management inconvenience, is difficult to adapt to project characteristics, and lacks multi-dimensional retrieval and statistical capabilities.
A tree-structured management system is adopted for technical document types. Combined with form configuration and process management, the system establishes the relationship between technical document types and other modules, enabling pre-management and upgraded retrieval of technical documents. Through the technical document type management module, association management module, retrieval module, and statistics module, multi-dimensional retrieval and statistics are achieved.
It has improved the productization of technical document management, realized multi-dimensional retrieval and statistical functions, enhanced the readability and applicability of data, supported project-specific configuration and flexible management, and promoted the interconnection and full digitization of data.
Smart Images
Figure CN116932472B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of digital intelligent construction of engineering projects, specifically to a technical document management system under a construction management system. It is mainly applicable to the digitalized, standardized, and normalized management of technical documents for complex and large-scale projects with long construction cycles, such as water conservancy and hydropower projects, as well as multi-dimensional technical document retrieval. It is a technical document management system based on BIM-based intelligent construction and information management system specifically designed for the construction phase of engineering projects, with the main functions of submitting and managing various types of documents such as on-site design documents and construction plans. Background Technology
[0002] The Intelligent Construction and Information Management System (hereinafter referred to as the Construction Management System) is an integrated application platform developed and constructed based on technologies such as databases, 3D GIS+BIM, automatic control, the Internet, mobile Internet, the Internet of Things, and digital handover, providing services for the construction period of engineering projects. This platform primarily meets the engineering management needs of construction units, supervision units, construction units, and design units during the construction period. It achieves intelligent management and control of all aspects of engineering construction, including progress, quality, investment, and safety, based on GIS+BIM models and digital and intelligent construction technologies such as compaction, temperature control, concrete mixing, and information technology. This promotes the improvement and optimization of engineering construction management and decision-making methods, enhances the level of engineering construction management, and achieves the organic integration and mutual promotion of scientific management, intelligent construction, and information technology. It realizes intelligent construction, standardized management, standardized processes, and information-based processes, transforming engineering construction management from fragmented to collaborative operation, and establishing a safe and efficient construction monitoring, information sharing, collaborative operation, business analysis, and decision support system.
[0003] The technical management module comprises three sub-modules: design management, construction management, and technical documents. It primarily handles the submission and management of various types of documents, including on-site design documents and construction plans. All relevant parties can track the process in real time and review approval records based on multiple parties' comments, improving the efficiency of document submission. It is evident that technical management is a crucial means of achieving paperless office operations. It also structures various submitted documents to a certain extent, thereby unifying data types and standards. Technical documents are entered into the system through a submission and approval process, ensuring that the technical management documents entering the system are valid and verified data. In practice, a large amount of data has been submitted and approved, achieving excellent application results.
[0004] However, current technical management, based on project management experience and standards, enumerates various approval types and implements structured forms. It also coordinates with node processes for uploading approvals. Uploading is inevitably based on the approval type, starting with the role, i.e., the participating party. This management approach is reasonable, but due to the large number of form types, retrieving technical documents is problematic. It requires locating specific fields for searching, which lacks uniformity. This results in many technical documents being issued and managed within the system, but with low efficiency in retrieval. Some technical documents may even be unsearchable. This is because of the lack of a good search design, leading to some data being difficult to utilize or even lost.
[0005] From an approval perspective, technical management links some technical documents to certain nodes in the WBS (Work Breakdown Structure) tree. This approach allows for the collection of approval data from a construction division perspective, such as documents issued by the design unit under a specific sub-project. However, for complex construction management systems and project management data extraction needs, this data is insufficient because it lacks effective linkage with spatial locations, progress sections, etc. Furthermore, from a technical implementation perspective, while various document types are enumerated and project-specific workflows are listed, document type and workflow management is poorly implemented, as both are custom-developed for each project. Logically, this management method is not easy for front-end managers to check and verify, as the numerous workflow nodes and custom development from the outset hinder productization; even with a different project, further customization is required. However, for the system itself, while project document types are customized for specific project characteristics, workflow and technical document types can be enumerated. Combining these two allows for the creation of project-specific technical document types for data structuring and workflow management. In addition, changes in process nodes also exist during the project. Often, after the process changes, the existing workflow files cannot be processed. However, in reality, as long as the process is different, it can run in the system. The process change is that the development team directly replaced the process. Because the process version management was not done well, it caused many problems in actual use.
[0006] These issues can actually be addressed by making management more explicit, thereby enabling customized content through management and separating development from application. Development would handle the creation of enumerated forms and the development of enumerated workflows, while application would configure the issuance of technical documents based on the project. However, due to a lack of relational management, the statistical capabilities for technical documents are relatively weak. Since different types of forms have different fields, associating WBS tree nodes is necessary to connect with other modules within the system, especially the BIM display module, to achieve some statistical analysis. However, this node-based management has been previously overlooked because relational management between modules within the construction management system is also lacking. For data statistics within the system, it is necessary to label data as nodes. Data entry for document management is through workflow forms. Adding relational management would be highly beneficial for the later development and utilization of data in the entire construction management system. However, currently, no engineering management or engineering digitization platforms on the market offer this kind of relational management. Summary of the Invention
[0007] To address the shortcomings of existing technologies, the present invention aims to provide a technical document management system within a construction management system. By managing technical documents according to their types in a tree structure, combining form configuration management and process management corresponding to each technical document type, and establishing relationships between technical types and other modules, the system achieves pre-management of technical documents and upgrades technical document retrieval, thereby enhancing the productization of the technical document management module within the construction management system.
[0008] Therefore, the above-mentioned objective of the present invention is achieved through the following technical solution:
[0009] A technical document management system under a construction management system, comprising:
[0010] The Technical Document Type Management module includes Technical Document Type Process Management, Technical Document Type Form Configuration Management, and Technical Document Type Management. It is used to customize the technical document types circulating within the system and configure the corresponding form configurations and process combinations. Technical Document Type Process Management manages various circulation processes in a tree structure, forming a basic process circulation library. Specifically, it categorizes and manages the processes that need to circulate using a tree-structured directory. The last node of the tree structure directory is the managed process name, and the managed content is a description of the process's circulation rules. After management, a basic process circulation library is formed, which can be extracted to compose the forms initiated by technical documents and the process parts within the workflow.
[0011] Technical document type form configuration management enumerates the structured forms that various types of technical documents may require, forming a basic library of technical document form configurations. This library is used to extract and compose the forms used in initiating technical documents and in workflows. The structured content within technical document forms consists of single-value tags. During management, form configurations are divided into general and specific parts. Creating a new form configuration involves adding specific fields to the general part. These specific fields refer to the tag names within the form, and the corresponding tag values are entered when initiating the process. Technical document type management maintains a specific technical document type directory tree for application in specific engineering projects. The root node is the corresponding project technical document type. For each project technical document type, the corresponding technical document type form configuration and workflow are configured from the workflow flow basic library and the technical document form configuration basic library, thus completing the form and workflow configuration for the project technical document type. The first level of the technical document type directory tree is defined by project participants. Workflow configuration is based on the participants and workflow requirements; it only defines the workflow rules and does not specify specific users. The specific personnel for each workflow node are selected when initiating the process in technical document management, based on the document's requirements. The information recorded during the workflow is also linked to the technical documents. The workflow information records the personnel involved, their opinions, and the time; these can be used as search terms. In this technical solution, a technical document refers to a technical document and its structured information initiated in the system, entering the system through workflow processes and recording workflow information. It does not refer to a single document; it can be a main document with several subsidiary documents and structured information. The structured information describes the technical document. It can also be a purely structured form without a document, which is still considered a technical document. In other words, a technical document here is a collection of technical documents and their digital content for a specific technical type within an engineering project.
[0012] The Technical Document Association Management module manages the association of technical documents with nodes in other directory trees within the system when a technical document is initiated. When initiating a document process, form content is filled out, and the initiated technical management document must be associated with nodes in other directory trees within the system. These other directory trees can be construction package partitioning directory trees, space partitioning directory trees, archive type directory trees, and other directory trees that may appear within the system. This association management module is used to link technical management with other modules. By initiating a technical document and associating it with other directory tree nodes, the process starts from the participating party, based on the actual system usage, to find the corresponding node in the technical document type tree, and then initiates the document process. The initiation process and form content are fixed based on the selected technical document type, and the initiated technical document itself is necessarily associated with the last node of the selected technical document type directory tree, i.e., the type of the initiated technical document.
[0013] The technical document retrieval module organizes the structured content of technical documents at the time of submission, along with associated tree nodes within the system and approval opinions generated during the workflow process, for retrieval. The workflow process involves forms representing workflow nodes for the submitted technical documents, recording workflow information and opinions, including the approvers at each node. This workflow information can also be used to retrieve specific technical documents. The technical document retrieval module consists of two parts that can be used in combination: a topic combination part and a form retrieval part. The topic combination part searches for relevant directory tree nodes within the system using keywords, then combines the corresponding directory tree nodes to obtain a collection of technical documents. Nodes in the technical document type directory tree are preferred and mandatory. Normal browsing and initiation of technical documents are done through the technical document type tree. Furthermore, technical documents are associated with the end node of the technical document type directory tree and share a common technical document type form configuration. Therefore, technical documents of the same type have consistent form types. Selecting the end node of the technical document type tree means selecting a technical document type and its corresponding structured form configuration. Meanwhile, each technical document type is associated with only one end node of the technical document type tree, but there is no limit to the number of other types of tree structure nodes that can be associated with within the system. When retrieving technical documents, through the topic combination section, at least one node of the technical document tree type must be selected. It can be combined with other tree structure types to obtain a set of technical documents commonly associated with the selected nodes. At this time, the files are the intersection of the files under the selected node combination. However, when multiple technical document type nodes are selected, it is the union of the technical documents associated with multiple technical document type nodes. The form retrieval section is for locating specific technical documents. It retrieves the structured content within the form and is filter-based. It requires a fixed structured form, which means a fixed technical document type node. The structured form of the technical documents of that type is searched and filtered to obtain the target set of technical documents. It can be combined with the topic combination section to complement each other. The topic combination section obtains the set of files, while the form retrieval section filters the set of files under the given conditions. In addition, the form retrieval section can also retrieve common parts of the data in the technical documents together, such as the initiation time, process nodes, and personnel. These are common and can be retrieved through unified retrieval. Similarly, this method can be used in combination with the topic combination section.
[0014] The technical document viewing module is integrated with the technical document retrieval module. It allows viewing of specific technical documents retrieved by the retrieval module. Viewing is divided into viewing structured information, such as the form entries submitted during reporting and the corresponding workflow, and viewing the main text. Typically, technical documents have a main text, which is then viewed, along with its structured content. For technical document types without a main text, a formatted document is created through style conversion, adhering to specifications or industry conventions. Style management utilizes existing system technology and can be freely replaced or added; this is not a core aspect of this technical solution.
[0015] The technical document statistics module is used to customize various statistics. The statistical dimensions are derived from technical document retrieval. The module retrieves a specific set of technical documents using search methods and performs statistics based on the status of this set and the values of its structured forms—the structured portion of the technical documents. The statistical dimensions are derived from the tree type associated with the technical documents, and the statistical content comes from the structured portion of the technical documents, including their own circulation status and the circulation information added to the documents during circulation. Based on the characteristics of technical documents entering and circulating within the system, standardized management of incoming technical documents is achieved, along with the association of different tree nodes within the system. The statistics module is relatively flexible and dynamic, and can be quickly customized to adapt to project needs.
[0016] By decoupling the structured forms and processes of technical document circulation in the above modules and establishing separate libraries for management, users can configure the circulation of technical document types themselves. By associating tree structures within multiple systems, multi-dimensional search and statistical functions can be achieved. This can help promote the productization of technical document management under the construction management system and is more applicable than existing technical management informatization solutions.
[0017] While adopting the above technical solutions, the present invention may also adopt or combine the following technical solutions:
[0018] As a preferred technical solution of the present invention, in the technical document type management module, the technical document type form configuration management forms a basic library of file form configurations that can be modified and added. Adding a file form configuration means adding a node to the form configuration management directory tree and naming it.
[0019] As a preferred technical solution of the present invention, in the technical document type management module, the technical document type form configuration management forms a basic library of form configurations that can be reused as a general library for similar projects. The basic library of form configurations is customized according to the project type, that is, the engineering type, and then reused for a specific project. When reused for a project, it forms a basic library of form configurations for the project. At this time, the basic library of form configurations for the project can be modified. The principle of the basic library of form configurations for engineering types is that new additions are allowed, but deletion and modification are strictly controlled.
[0020] As a preferred technical solution of the present invention, in the technical document type management module, the technical document type form configuration management will affect technical documents that are already in circulation or have been completed when the project form configuration base library is modified. The structured content in the technical document form is all single-value tags. The fields of the form in the form configuration base library can be modified, that is, the tag names of the single-value tags. Tags (form fields) cannot be added or deleted.
[0021] As a preferred technical solution of the present invention, in the technical document type management module, the technical document type form configuration management and the form configuration base library can be multiple according to the project. For a project, a project-specific form configuration base library is established. However, in order to ensure that the structured content of technical documents of the same type is consistent, some fields can be hidden according to the needs of the project during application. That is, the technical document can be initiated even if the structured content corresponding to the technical document is not fully displayed or not fully entered.
[0022] As a preferred technical solution of the present invention, in the technical document type management module, the technical document type form configuration management, the structured content in the technical document form is all single-value tags, during management, the form configuration is divided into a general part and a special part, the new form configuration is to add a special part field to the general part, the special part field refers to the tag name in the form, and the corresponding tag value is entered when the form is initiated.
[0023] As a preferred technical solution of the present invention, in the technical document type management module, the technical document type management is for the application of specific engineering projects, maintaining a specific technical document type directory tree, with the root node being the corresponding project technical document type, and configuring the corresponding technical document type form configuration and technical document type process respectively from the process flow base library and the technical document form configuration base library for the project technical document type, thereby completing the form and process configuration of the project technical document type.
[0024] As a preferred technical solution of the present invention, in the technical document type management module, the technical document management maintains a specific technical document type directory tree, and the first level of the technical document type directory tree is defined as being divided according to the project participants.
[0025] As a preferred technical solution of the present invention, in the technical document type management module, the process configuration is configured according to the participants and the needs of circulation. Only the circulation rules are set, without specifying specific users. The specific designation of each process node is when the technical document management is initiated, and the specific personnel of each node are selected according to the needs of the document itself.
[0026] As a preferred technical solution of the present invention, in the technical document type management module, the information recorded in the process flow is also linked to the technical document. The flow information records the node personnel, opinions, and time, which can be used as search items.
[0027] As a preferred technical solution of the present invention, in the technical document association management function module, the technical document association initialization is performed when the technical document process is initiated. During the process and after the process has been completed, the directory tree node associated with the technical document can be modified, but the association of the technical document type tree node cannot be modified.
[0028] As a preferred technical solution of the present invention, in the technical document association management function module, when a technical document is initiated, it starts from the participating party based on the actual usage of the system, finds the corresponding node in the technical document type tree, and then initiates the document process. The technical document initiation process and form content are fixed according to the selected technical document type. At the same time, the initiated technical document is also necessarily associated with the end node of the selected technical document type directory tree, that is, the type of the initiated technical document. The technical document type tree structure directory maintained in the technical document type management module is used to find the corresponding technical document type through the directory tree when initiating a technical document process. The first level directory is maintained and divided by the participating party, so users use it according to their own roles, which is in line with the usage logic.
[0029] As a preferred technical solution of the present invention, the technical document retrieval module organizes the structured content of the technical document when it is submitted, as well as the associated tree nodes in the system and the approval opinions formed during the circulation process, for the retrieval of technical documents. The circulation process is a form that forms process nodes for the initiated technical document, which is used to record circulation information and opinions, including the approver of the circulation node. The circulation information can also be used for the retrieval of specific technical documents.
[0030] As a preferred embodiment of the present invention, the technical document retrieval module is divided into two parts, which can be used in combination: a topic combination part and a form retrieval part.
[0031] As a preferred embodiment of the present invention, in the technical document retrieval module, the topic combination part is to search for tree nodes of relevant directory trees in the keyword search system, and then combine the corresponding directory tree nodes to obtain a collection of technical documents.
[0032] As a preferred technical solution of the present invention, in the technical document retrieval module, the nodes of the technical document type directory tree in the topic combination part are preferred and required. Normal browsing and initiation of technical documents are carried out through the technical document type tree. In addition, technical documents are associated with the end node of the technical document type directory tree and share a common technical document type form configuration. Therefore, the form type of technical document types of the same type is consistent. Selecting the end node of the technical document type tree means selecting a technical document type and its corresponding structured form configuration.
[0033] As a preferred technical solution of the present invention, in the technical document retrieval module, the topic combination part of the technical document type is only associated with the end node of a technical document type tree, but there is no limitation on the number of other types of tree structure nodes in the system that can be associated. When retrieving technical documents, at least one node of the technical document tree type must be selected through the topic combination part, and it can be combined with other tree structure types to obtain the set of technical documents under the common association of the selected node. At this time, the file is the intersection of the files under the combination of the selected nodes.
[0034] As a preferred technical solution of the present invention, in the technical document retrieval module, when multiple technical document type nodes are selected, it is the union of technical documents associated with multiple technical document type nodes. At this time, when combined with nodes of other types of tree structures, it is the union of files obtained after the intersection of files obtained by a single technical document type node and other tree structure nodes.
[0035] As a preferred technical solution of the present invention, the form retrieval module is used to locate specific technical documents. It retrieves the structured content within the form and is a filtering process. It requires a fixed structured form, which means it requires a fixed technical document type node. The structured form of the technical document of that type is searched and filtered to obtain a set of target technical documents. It can be combined with the topic combination part to complement each other. The topic combination part is for obtaining the set of documents, and the form retrieval part is for filtering the set of documents under the given conditions.
[0036] As a preferred technical solution of the present invention, the form retrieval module can also retrieve the common parts of the data in the technical documents together. The common parts of the technical document form configuration are the universally retrieval parts. In addition, the initiation time, process node personnel, etc. are common fields of technical documents and can be retrieved in a unified manner. Similarly, this method can be used in combination with the topic combination part.
[0037] As a preferred embodiment of the present invention, the technical document viewing module is combined with the technical document retrieval module, and the viewing is performed based on the specific technical documents retrieved by the retrieval module.
[0038] As a preferred technical solution of the present invention, the technical document viewing module is divided into viewing structured information, namely the form filling content and corresponding process flow when reporting, and viewing the main text. Usually, a technical document has a main text, so the main text can be viewed, and its structured content can also be viewed. For technical document types without a main text, a document is formed by style conversion and viewed. The document style is implemented according to the specification or industry convention.
[0039] As a preferred technical solution of the present invention, the technical document statistics module is used to customize various statistics. The statistical dimensions come from technical document retrieval. A certain set of documents about technical documents is obtained through the retrieval method in the technical document retrieval module, and statistics are performed based on the status of this set of documents and the value of the structured form, which is the structured part of the technical documents.
[0040] As a preferred technical solution of the present invention, in the technical document statistics module, the dimension of the technical document statistics comes from the tree type associated with the technical document, and the statistical content comes from the structured part of the technical document, including its own circulation status and the circulation information added to the technical document during the circulation process. The statistics can be used as an extension of the retrieval, and some customized quick retrieval and statistical data of the results can be viewed as needed.
[0041] As a preferred technical solution of the present invention, the technical document statistics module is characterized by the ability to perform comprehensive statistics based on the associated data types. The statistical dimensions are richer and more flexible than the previous mode, and the display of technical document statistical data can be customized according to the specific needs of the project.
[0042] As a preferred technical solution of the present invention, the technical document statistics module performs customized target retrieval based on the technical document retrieval module. It performs statistics based on the retrieval results. Furthermore, it can also calculate specific values in the structured form of technical documents with specific retrieval topics, or extract tag values in the structured form with one click, thereby realizing data processing and rapid data extraction. This kind of processing is difficult to handle and implement in other existing systems.
[0043] As a preferred technical solution of the present invention, based on the characteristics of the initiation and circulation of technical documents entering the system, the technical documents entering the system are managed in a standardized manner, and the association of tree nodes of different dimensions in the system is also realized. The statistics module is relatively flexible and dynamic, and can be quickly customized to adapt to project needs.
[0044] As a preferred technical solution of the present invention, the management of file viewing styles can be arbitrarily replaced or added using existing technologies within the system, and is not considered the core content of this technical solution. This technical solution is suitable for flexibly incorporating other superior technologies to adapt to the needs of specific projects.
[0045] In this technical solution, a technical document refers to a technical document and its structured information that is initiated in the system, enters the system through process flow and records flow information, and is not simply a single document. It can be a main document with several subsidiary documents and structured information. The structured information is a description of the technical document. It can also be a purely structured form without a document, which is also a technical document. In other words, a technical document here is a collection of technical documents and their digital content for a specific technical type in an engineering project.
[0046] As a preferred technical solution of the present invention, it is applicable to the technical document management system under the digital intelligent construction system for engineering, mainly applicable to complex and large-scale projects with long construction cycles such as water conservancy and hydropower, and also applicable to intelligent construction systems in other industries.
[0047] Compared with the prior art, the present invention has the following advantages and beneficial effects:
[0048] 1) Decouple the structured forms and processes of technical document circulation and establish separate libraries for management. This allows users to configure the circulation of technical document types themselves and associate tree structures within multiple systems to achieve multi-dimensional retrieval and statistical functions. This can help promote the productization of technical document management under the construction management system and is more applicable and productized than existing technical management informatization solutions.
[0049] 2) Technical documents, structured forms, and processes are stored in a separate library, which can be reused in different projects within the same industry. Combined with standards and specifications, they can form a basic library and a knowledge base, facilitating the formation of unified application standards within the industry during practical applications, achieving data interconnection and interoperability, and helping to realize big data applications. The basic library has strong reusability, which is more conducive to the promotion and application of the construction management system. It can be used simply by configuring the project's technical document type tree, without the need for special customized development for the project.
[0050] 3) Make the tree structure of various dimensions of technical document association explicit and realize association management, thereby enabling multi-dimensional technical document retrieval and statistics. Multi-dimensional technical document retrieval and statistics is a problem that existing construction management systems cannot solve. By combining the characteristics of technical document reporting with the tree structure established by multiple modules and dimensions within the system, association is realized, thereby enabling technical document data to be interconnected with other modules. The addition of association management has a fundamental improvement on the customizability, flexibility and data readability of the construction management system.
[0051] 4) Unify the management of relevant technical documents and their structured information. Some structured information can also be converted into documents to form a unified technical document with a consistent description. Unify the structured form structure and process flow information into forms for management. Combined with search paths and statistical methods, the structured data of technical documents that were previously unusable can be utilized. This non-routine management of technical documents makes the technical document data more valuable.
[0052] 5) Considering the characteristics of technical documents, namely that they require process flow, their structured information is guaranteed, and the information is rich, the process can ensure the accuracy and reliability of the data entering the system. This technical solution meets the requirements of all parties for approval. At the same time, this action realizes the collection of technical document data, thereby achieving the comprehensive digitization of technical documents within the project. Attached Figure Description
[0053] Figure 1 This is a schematic diagram of the processing flow of the technical document management system under the construction management system provided by the present invention.
[0054] Figure 2 This is a diagram illustrating the management process flow using a tree structure.
[0055] Figure 3 This is a diagram illustrating how form configurations are managed using a tree structure.
[0056] Figure 4 This is an example of a directory tree for project technical document types.
[0057] Figure 5 This diagram illustrates how to initiate a technical document submission process based on the directory tree for project technical document types.
[0058] Figure 6 This is a diagram illustrating the directory tree nodes within the technical document association system.
[0059] Figure 7 This is a schematic diagram of the process flow information recording style.
[0060] Figure 8 This is a diagram illustrating how forms without attachments can be automatically converted into standard format files. Detailed Implementation
[0061] To enable those skilled in the art to better understand the technical solutions of the present invention, the preferred embodiments of the present invention are described below in conjunction with specific examples. However, it should be understood that the accompanying drawings are for illustrative purposes only and should not be construed as limiting the present patent.
[0062] Referring to the accompanying drawings, the technical document management system under the construction management system of the present invention includes a technical document type management module, a technical document association management module, a technical document retrieval module, a technical document viewing module, and a technical document statistics module.
[0063] First, let's explain the technical document type management module. This module includes technical document type process management, technical document type form configuration management, and technical document type management. It is used to customize the technical document types circulating within the system and configure the form configurations and process combinations corresponding to the technical document types.
[0064] Technical document type workflow management uses a tree-structured directory to manage the flow of information. The workflow is described using a diagram, such as... Figure 2 As shown, the final node in the tree structure is named the process form name. The process flow description is mainly displayed graphically, depicting the flow relationships between participating parties. The specific nodes in the flow, and the personnel selected for each node, are chosen at the time of initiation. The process flow establishes the flow rules, while the appropriate time to select personnel for each node is determined based on the specific project situation. The process flow information is recorded in a separate form and finally attached to this technical document. Development then uses a process engine to customize the flow rules for the flow diagram.
[0065] Technical document type form configuration management enumerates the structured forms that various types of technical documents may require, forming a basic library of technical document form configurations. The structured content within technical document forms consists of single-value tags. During management, form configurations are divided into general and specific sections. Creating a new form configuration adds specific fields to the general section. These specific fields refer to the tag names within the form; the corresponding tag values are entered when the form is initiated. For example... Figure 3The image shows a configured form format. The filename and process number are common elements. Creating a new form configuration involves adding tags, which are single-value tags. For example, adding a "Meeting Name" tag would display "Meeting Name: Tag Value" in the form. The tag value is the corresponding content, which is filled in when the form is initiated. This maintained form configuration is saved using a tree structure, with the form configuration name being the name of the last node in the tree structure. For example, after maintaining a form configuration, it is saved as "General Contractor Mode - Owner's Document - Third-Party Consultation - General Contractor" and saved to the form configuration management directory tree; the node name is this. Upper-level nodes in the tree structure can be project types, etc. The tree structure directory is mainly used to categorize and manage form configuration types.
[0066] It's important to note that once a form configuration is established, it should be modified as much as possible. This is because some technical documents will reference this configuration, and modification will affect existing and completed technical documents. The general approach is to create a new, renamed form configuration and then create a new technical document type to use it. In other words, the initialization of the form configuration library should be based on existing industry experience, ensuring its authority and preventing later modifications. The resulting form configuration library should be universally applicable within the industry.
[0067] Technical document type management is implemented for specific engineering projects, maintaining a directory tree of technical document types. The root node represents the corresponding project's technical document type. It also configures the corresponding technical document type form configurations and processes from the workflow flow base library and the technical document form configuration base library for each project's technical document type, thereby completing the form and process configuration for the project's technical document type. Figure 4 As shown, the first level of the technical document type directory tree is divided by project participants. This allows users to find the corresponding technical document type based on the type of application they need to submit for review, and then initiate the review process. Figure 5 As shown.
[0068] When initiating an approval process, first fill out the corresponding form, specify the personnel responsible for the next step of the process, and also associate nodes with other directory trees within the system. The associated node content is separate from the form and process and does not interfere with each other. The required directory trees are uniformly set by the system according to project needs. Taking the construction package breakdown and space partitioning tree as an example, at least one node from these two trees must be associated during upload, such as... Figure 6 As shown.
[0069] After a technical document is initiated, it is retrieved. The conventional method is to browse and search within the original directory that manages technical documents, i.e., the technical document type directory tree, based on its own characteristics, such as the initiating organization and the technical document type. If the document number is known, it can be searched using the number as a keyword, or by file name. Of course, it is also possible to search using the structured information of the technical document. However, the structured forms of technical documents vary, and searches can only be performed by searching the full text of the form using keywords. This results in relatively disorganized and less precise results, and it is impossible to pinpoint fields with specific requirements. For example, it is difficult to obtain technical documents of the technical contact form type related to a specific spatial location within a certain sub-project, because the existing technical solutions only associate with the sub-project and lack corresponding fields for spatial distribution. The description of the technical document in the structured form is also relatively loose, and it is difficult to accurately locate the document from the tag values in the form.
[0070] The core of retrieval and statistics lies in obtaining a collection of documents under specific keywords, or rather, a combination of elements. Within this collection, a structured form allows for quick viewing of relevant technical documents, locating specific files efficiently. Furthermore, the structured form is consistent for technical documents of the same type. The document collection is obtained by combining nodes in a tree-like structure associated with the technical documents, thus creating a collection of documents under a specific topic. This organizes documents that were previously difficult to access quickly, providing a foundation for multi-dimensional statistics. Statistical analysis is then performed on the collection of documents based on topic combinations and their progress status (completeness). In other words, statistics and retrieval are essentially the same; if something can be retrieved, it can be statistically analyzed. Additionally, this technical solution includes a universal form component that can be used for system-wide retrieval. This universal component includes a universal form and workflow information. The workflow information is recorded in a form, and the recorded content is as follows... Figure 7 As shown, the main categories are opinions, personnel, and time, so this part can also be searched universally.
[0071] After obtaining the file collection by combining topics, technical files can be further filtered using a form. If only one technical file type is selected within a topic, the form configuration for that specific technical file type is fixed, allowing filtering by tags and their values, similar to advanced search in a literature retrieval system. It's important to note that if multiple technical file type nodes are selected—that is, two nodes within the same tree—both technical file types should be listed if no other tree structure directories are selected. Combining with other tree structure nodes in this case yields the union of the files obtained from the intersection of a single technical file type node with each other tree structure node. This logic aligns with current practical application needs. Of course, the intersection and union logic here can be adjusted based on the application's requirements, but this is predicated on association management. Without association management, such rapid file collection retrieval is impossible. Furthermore, these logical and combined changes form the basis for customized statistics for projects. Various statistical methods can be customized according to the actual needs of the project. In fact, it is an operation of using topic combinations and structured form field filtering. Only a fixed retrieval method is defined. As the data grows, the statistical data changes accordingly, which greatly improves usability and can quickly meet the needs. This is something that the previous system could not do because it did not have such a design in the initial system design. It only used some structured content to customize statistics later, which was inefficient and the functions may not meet the actual needs.
[0072] Technical document viewing involves locating and reviewing the technical documents, similar to viewing ordinary documents. Further, it allows viewing the document's structured content and workflow information. For technical documents without a main file, the system provides a method to extract a portion of the structural content and create a display file, such as... Figure 8 As shown, this is a technical document that was initiated without a main file, and can eventually be exported as a single file.
[0073] In other words, through the technical document management in this system, the process of entering the system is used as the basis for the reliability of technical documents, thus realizing structured management. At the same time, a form configuration library for technical document types has been established. Technical documents have broken away from the scope of traditional single documents, with richer content, and the structured content has been utilized to a certain extent, namely retrieval and statistics. In the future, as data continues to accumulate, more advanced applications can be used. This is the foundation of the initial design of the technical document management system and the corresponding data sorting and content support.
[0074] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Any simple modifications or equivalent changes made to the above embodiments based on the technical essence of the present invention shall fall within the protection scope of the present invention.
Claims
1. A technical document management system under a construction management system, characterized in that: The system includes: The technical document type management module is used to customize the types of technical documents circulating within the system and configure the form configurations and process combinations corresponding to the technical document types. The technical document type management module includes technical document type process management, technical document type form configuration management, and technical document type management. - Technical document type process management is used to manage various flow processes in a tree structure to form a basic process flow library; the content managed by technical document type process management is the description of the flow rules of the process. After management, a basic process flow library is formed, which can be extracted to form the forms initiated by technical documents and the process parts in the process. - Technical document type form configuration management is used to enumerate the structured forms required for various types of technical documents, forming a basic library of technical document form configurations, which can be extracted to form the forms initiated by technical documents and the form parts in the process; - Technical document type management is used for specific engineering projects. It maintains a directory tree of specific technical document types, with the root node being the corresponding project technical document type. It also configures the corresponding technical document type form configuration and technical document type process from the process flow base library and the technical document form configuration base library for the project technical document type, thereby completing the form and process configuration of the project technical document type. The technical document association management module is used to manage the nodes of other directory trees in the system associated with the technical document when it is initiated. When initiating a document process, form content is filled in, and other directory tree nodes in the system need to be associated with the initiated technical management document. When a technical document is initiated, it starts from the participating party based on the actual system usage, finds the corresponding technical document type tree node, and then initiates the document process. The process and form content of the technical document initiation are fixed according to the selected technical document type. The technical document retrieval module organizes the structured content of the technical document at the time of submission, along with the associated tree nodes within the system and the approval opinions generated during the workflow process, for the purpose of retrieving the technical document. The workflow process involves forms that form process nodes for the initiated technical document, recording workflow information and opinions, including the approvers of the workflow nodes. This workflow information is used for retrieving specific technical documents. The technical document retrieval module is divided into two parts: a topic combination part and a form retrieval part. - The topic combination section searches for relevant directory tree nodes within the system using keywords, then combines these nodes to obtain a collection of technical documents. The technical document type directory tree nodes in the topic combination section are preferred and mandatory. Normal browsing and initiation of technical documents are done through the technical document type tree. Furthermore, technical documents are associated with the last node of the technical document type directory tree and share a common technical document type form configuration. Therefore, technical document types of the same type have consistent form types. Selecting the last node of the technical document type tree selects a specific technical document type and its corresponding structured form configuration. Each technical document type in the topic combination section is associated with only one technical document type. The technical document type tree is the last node, but there is no limit to the number of other types of tree structure nodes that can be associated with within a system. When retrieving technical documents, through the topic combination part, at least one node of the technical document tree type must be selected and combined with other tree structure types to obtain the set of technical documents that are commonly associated with the selected nodes. At this time, the files are the intersection of the files under the selected node combination. In the technical document retrieval module, when multiple technical document type nodes are selected, it is the union of the technical documents associated with multiple technical document type nodes. At this time, the combination with nodes of other types of tree structure nodes is the union of the files obtained after the intersection of the files obtained by a single technical document type node with other tree structure nodes. - The form retrieval section is for locating specific technical documents. It retrieves the structured content within the form and is filter-based. It requires a fixed structured form and a fixed technical document type node. It searches and filters the structured form of that type of technical document to obtain the target technical document set. This is combined with the topic combination section, which complements each other. The topic combination section obtains the document set, while the form retrieval section filters the document set under certain conditions. The technical document viewing module is integrated with the technical document retrieval module. The technical document viewing module views specific technical documents retrieved by the technical document retrieval module. The technical document statistics module is used to customize various statistics. The statistical dimensions come from technical document retrieval. A certain set of technical documents is obtained through the retrieval methods in the technical document retrieval module, and the structured part of the technical documents is statistically analyzed based on the status of the file set and the values of the structured forms.
2. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document type form configuration management, the structured content within the technical document form consists of single-value tags. During management, the form configuration is divided into a general part and a special part. Creating a new form configuration involves adding special part fields to the general part. The special part fields refer to the tag names within the form, and the corresponding tag values are entered when the form is initiated.
3. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document type management module, the technical document management maintains a specific technical document type directory tree. The first level of the technical document type directory tree is defined as being divided by the project participants.
4. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document type management module, the process configuration is based on the participants and the needs of the workflow. Only the workflow rules are set, without specifying specific users. The specific personnel for each process node are selected when the technical document management is initiated, based on the needs of the document itself.
5. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document type management module, the information recorded during the workflow is linked to the technical document. The workflow information records the personnel involved, their opinions, and the time, which are used as search terms.
6. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document association management module, technical document association initialization is performed when the technical document process is initiated. During the process and for technical documents that have already completed the circulation, the directory tree node associated with the technical document can be modified, but the association of the technical document type tree node cannot be modified.
7. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document viewing module, viewing is divided into viewing structured information, the form content filled in during reporting and the corresponding process flow, and viewing the main text. Technical documents have a main text, so you can view the main text and its structured content. For technical document types without a main text, the document is converted into a document through style conversion for viewing.
8. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document statistics module, comprehensive statistics are performed based on the associated data types, and the display of technical document statistical data is customized according to the specific needs of the project.
9. The technical document management system under the construction management system according to claim 1, characterized in that: In the technical document statistics module, technical document statistics are a customized target retrieval of the technical document retrieval module. Based on the retrieval results, statistics are performed. As needed, specific values in the structured form of technical documents on a specific retrieval topic are calculated, or tag values in the structured form are extracted with one click.