Engineering document management method, electronic equipment and computer readable medium

Abstract

The invention provides an engineering document management method. The engineering document management method comprises the steps of receiving and storing an engineering document; each engineering document corresponds to a preset engineering project, and the total number of the preset engineering projects is one or more; determining a standard document type label of the engineering document; the standard document type label represents the type of the engineering document. The invention further provides electronic equipment and a computer readable medium.

Description

Technical Field

[0001] The present disclosure relates to the technical field of engineering project management, and particularly to a method for engineering document management, an electronic device, and a computer-readable medium. Background Art

[0002] In an engineering project, many engineering documents will be generated, and these engineering documents need to be uniformly managed.

[0003] In some related technologies, it is difficult to efficiently locate, file, count, access, etc. engineering documents, that is, efficient document management cannot be achieved, and unified management of multiple engineering projects (project groups) cannot be achieved either. Summary of the Invention

[0004] The present disclosure provides a method for engineering document management, an electronic device, and a computer-readable medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for engineering document management, which includes:

[0006] Receiving and storing engineering documents; each of the engineering documents corresponds to a preset engineering project, and the total number of the preset engineering projects is one or more;

[0007] Determining a standard document type tag of the engineering document; the standard document type tag represents the type of the engineering document.

[0008] In a second aspect, an embodiment of the present disclosure provides an electronic device, which includes a memory and a processor; the memory stores a computer program executable by the processor, and when the computer program is executed by the processor, it implements any one of the methods for engineering document management in the embodiments of the present disclosure.

[0009] In a third aspect, an embodiment of the present disclosure provides a computer-readable medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements any one of the methods for engineering document management in the embodiments of the present disclosure.

[0010] In the embodiments of the present disclosure, the engineering documents stored in each different engineering project have standard document type tags. The standard document type tags can indicate the specific types of engineering documents (such as survey reports or design drawings). Therefore, in the embodiments of the present disclosure, different engineering documents are accurately distinguished not by names but according to the standard document type tags. Thus, for the enterprise headquarters, the engineering documents in different subordinate engineering projects can be unified and aligned, achieving efficient and unified document management (such as various functions like positioning, archiving, statistics, access, real-time monitoring, big data analysis, etc., thereby ensuring the timeliness and integrity of the storage of engineering documents), and unified management of multiple preset engineering projects can be realized, that is, it can be used for the management of "project groups", facilitating business statistics, development planning, etc. according to the situation of the project groups. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In the drawings of the embodiments of the present disclosure:

[0012] Figure 1 is a flowchart of a method for engineering document management provided by an embodiment of the present disclosure;

[0013] Figure 2 is a block diagram of the composition of an electronic device provided by an embodiment of the present disclosure;

[0014] Figure 3 is a block diagram of the composition of a computer-readable medium provided by an embodiment of the present disclosure;

[0015] Figure 4 is a process schematic diagram of another method for engineering document management provided by an embodiment of the present disclosure;

[0016] Figure 5 is a process schematic diagram of the generation of a project document type template in another method for engineering document management provided by an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0017] To enable those skilled in the art to better understand the technical solutions of the present disclosure, the method for engineering document management, electronic device, and computer-readable medium provided by the embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0018] In the following, the present disclosure will be described more fully with reference to the accompanying drawings. However, the disclosed embodiments can be embodied in different forms and the present disclosure should not be construed as limited to the embodiments set forth below. On the contrary, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art.

[0019] The accompanying drawings of the embodiments of the present disclosure are used to provide a further understanding of the embodiments of the present disclosure, and constitute a part of the specification. Together with the detailed embodiments, they are used to explain the present disclosure and do not constitute a limitation to the present disclosure. By describing the detailed embodiments with reference to the accompanying drawings, the above and other features and advantages will become more obvious to those skilled in the art.

[0020] The present disclosure can be described with reference to the plan view and / or cross-sectional view by means of the ideal schematic diagrams of the present disclosure. Therefore, the example illustrations can be modified according to the manufacturing technology and / or tolerances.

[0021] In the case of no conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other.

[0022] The terms used in the present disclosure are only used to describe specific embodiments and are not intended to limit the present disclosure. As used in the present disclosure, the term "and / or" includes any and all combinations of one or more related listed items. As used in the present disclosure, the singular forms "a" and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. As used in the present disclosure, the terms "comprising", "made of...", specify the presence of the described features, wholes, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or their groups.

[0023] Unless otherwise defined, the meanings of all terms (including technical and scientific terms) used in the present disclosure are the same as those commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in common dictionaries should be interpreted as having a meaning consistent with their meaning in the relevant art and the context of the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless the present disclosure clearly defines so.

[0024] The present disclosure is not limited to the embodiments shown in the accompanying drawings, but includes modifications to the configurations formed based on the manufacturing process. Therefore, the regions illustrated in the accompanying drawings have schematic properties, and the shapes of the regions shown in the figures illustrate the specific shapes of the regions of the elements, but are not intended to be restrictive.

[0025] As the project management technology for engineering projects (such as those in the communication engineering field) becomes more and more mature, enterprises (especially large group enterprises) will establish standard construction processes (such as network planning, surveying, design, distribution, civil engineering, installation, commissioning, acceptance, etc.) and key project management actions (such as project establishment, scope management, schedule planning, cost budgeting, quality management, outsourcing management, procurement management, communication management, issue management, etc.) for various engineering projects, and require engineering projects to be carried out in accordance with the above standards to standardize the construction activities and project management behaviors of engineering projects, improve the delivery efficiency of engineering projects, control the delivery risks of engineering projects, and ensure the compliance of the business activities of engineering projects.

[0026] In many construction activities, corresponding project documents (such as exploration reports, design drawings, construction records, etc.) will be generated. Therefore, the project documents can be stored, and based on them, it can be judged whether the construction project is constructed according to the standard construction process and whether the key actions of project management are executed, etc.

[0027] However, since different construction projects involve different countries, regions, customers, etc., there are differences in languages, terms, habits, etc. of different construction projects, and there are also different preferences and requirements for the naming of the same type of project documents (such as exploration reports). Therefore, it is very difficult to keep the names of the same type of project documents consistent in different construction projects.

[0028] In some related technologies, project documents are directly stored in the project document library so that the project documents in the project document library can be used when needed. However, this method has at least the following problems:

[0029] (1) When relevant personnel need to use a certain project document (such as a project administrator auditing project documents), due to the inconsistent names, it is very difficult to locate the storage path of the required project document in the project document library, and thus the work cannot be carried out smoothly.

[0030] (2) The project document library cannot automatically analyze the categories and quantities of project documents of each construction project based on the names of the project documents in it, and thus cannot conduct statistics on the completion progress of the construction activities of the construction project, the record retention rate, etc.

[0031] (3) Some project documents need to be archived into the electronic file system, but the project documents that need to be archived cannot be found according to the names in the project document library.

[0032] (4) Based on security considerations, the authorization of project documents needs to comply with the principle of "minimizing permissions". Therefore, each project document is authorized by the creator to specific users according to its content and confidentiality level. However, when other personnel (such as personnel in the business domain's competent department) need to use some project documents (such as auditing the project documents in their field), they need to contact the creator of the project document to authorize them, and the process is complex, the communication cost is high, and the efficiency is low.

[0033] (5) The names of the same type of project documents in different construction projects are different, so they can only be managed separately according to the specific situation of each construction project, and it is impossible to achieve unified management of multiple construction projects (project groups).

[0034] In a first aspect, embodiments of the present disclosure provide a method for project document management.

[0035] Embodiments of the present disclosure are used to manage various engineering documents (such as survey reports, design drawings, construction records, etc.) generated during the process of an engineering project (such as a communication engineering project), and then it can be determined whether the engineering project is constructed according to the standard construction process and whether key project management actions are executed, etc.

[0036] Embodiments of the present disclosure can be executed by an electronic device with data processing and transmission capabilities, such as a server loaded with an engineering document management system.

[0037] Referring to Figure 1 , the method for engineering document management in embodiments of the present disclosure includes:

[0038] S101. Receive and store engineering documents.

[0039] Among them, each engineering document corresponds to a preset engineering project, and the total number of preset engineering projects is one or more.

[0040] In embodiments of the present disclosure, records of each engineering project to be carried out are established in the engineering document management system in advance, that is, one or more engineering projects are preset. Thus, when an engineering document is generated during the process of a certain engineering project, it can be stored in the engineering document management system, and the engineering project corresponding to the engineering document can be determined (such as "entering" the interface or subsystem of the corresponding engineering project before uploading the engineering document, or selecting the corresponding engineering project during uploading).

[0041] S102. Determine the standard document type label of the engineering document.

[0042] Among them, the standard document type label represents the type of the engineering document.

[0043] For each stored engineering document, a standard document type label also needs to be configured for it (such as selected by the uploader during upload, or directly configured according to the upload location). The standard document type label is used to indicate which pre-specified "standard type" this engineering document is, such as indicating that this engineering document is of the survey report type or the design drawing type, etc.

[0044] It should be understood that each engineering document may have only one standard document type label, or may have multiple standard document type labels at the same time, that is, according to different classification methods, this engineering document may be of different types.

[0045] Thus, when the engineering document is uploaded to the engineering document management system, its name can be set according to specific circumstances; but through the standard document type label of each engineering document, regardless of its name, it can be determined what specific type of engineering document this is.

[0046] It should be understood that for specific engineering projects in different countries, regions, and for different customers, to meet the specific needs of each engineering project, "custom document type tags" can also be set for at least some of the engineering documents in the engineering project to indicate what type the corresponding engineering document belongs to in the specific engineering project.

[0047] In the embodiments of the present disclosure, the engineering documents stored in each different engineering project have standard document type tags, and the standard document type tags can indicate the specific types of the engineering documents (such as survey reports or design drawings). Therefore, in the embodiments of the present disclosure, instead of using names, different engineering documents are accurately distinguished according to the standard document type tags. Thus, for the enterprise headquarters, the engineering documents in different subordinate engineering projects can be pulled through and aligned to achieve efficient and unified document management (such as various functions such as positioning, archiving, statistics, access, real-time monitoring, big data analysis, etc., so as to ensure the timeliness and integrity of the storage of engineering documents), and unified management of multiple preset engineering projects can be achieved, that is, it can be used for the management of "project groups", thereby facilitating business statistics, development planning, etc. according to the situation of the project group.

[0048] In some embodiments, before receiving and storing the engineering document (S101), it further includes:

[0049] S100. Determine the project document type template of the preset engineering project.

[0050] Among them, the project document type template includes multiple candidate standard document type tags.

[0051] Determining the standard document type tag of the engineering document (S102) includes:

[0052] S1021. Select the standard document type tag of the engineering document from the candidate standard document type tags in the project document type template.

[0053] The types of engineering documents that may appear in different engineering projects are different (for example, some engineering projects may require an environmental assessment report, while some engineering projects do not). Therefore, as a way of the embodiments of the present disclosure, for each engineering project (preset engineering project) in the engineering document management system, a dedicated "project document type template" can be determined in advance. The project document type template records the types of engineering documents specifically required in this engineering project, that is, the "candidate" standard document type labels. Therefore, when determining the standard document type label of each engineering document, it must be selected from the standard document type labels in its project document type template, and it is neither necessary nor allowed to use the standard document type labels that do not exist in the project document type template, so as to simplify the selection process of the standard document type label (only need to select from a small number of standard document type labels in this project document type template), and avoid the occurrence of incorrect standard document type labels (the standard document type labels not applicable to this engineering project have been excluded when setting the "project document type template").

[0054] In some embodiments, determining the project document type template (S100) of the preset engineering project includes:

[0055] S100A. Refer to the preset standard document type template as the project document type template.

[0056] Or,

[0057] S100B. Select some standard document type labels in the preset standard document type template to form the project document type template.

[0058] Wherein, the standard document type template includes a plurality of preset standard document type labels.

[0059] As a way of the embodiments of the present disclosure, one or more standard document type templates as "benchmarks" can be pre-released. Each standard document type template records the types of engineering documents specifically required in a "category" of engineering projects (standard document type templates). Therefore, each engineering project can directly refer to the appropriate standard document type template, that is, directly use the standard document type template as its own project document type template.

[0060] Or, as another way of the embodiments of the present disclosure, it is not necessary to completely refer to the standard document type template, but to select some contents (partial standard document type templates) in the standard document type template to form a specific project document type template, that is, the standard document type template can be "tailored" according to the specific situation of the engineering project.

[0061] It should be understood that the above standard document type template can be issued by the enterprise headquarters according to the situation, and operations such as content modification, unified update, and version traceability can also be carried out, which will not be described in detail here.

[0062] In some embodiments, at least some of the standard document type tags have corresponding document attributes.

[0063] As a way of the embodiments of the present disclosure, corresponding attributes (i.e., document attributes, such as those that can be stored in the standard document type template or the project document type template) can be set for the standard document type tags in advance, which represent the attributes that the engineering documents with the standard document type tags should conform to, that is, the nature of the corresponding types of engineering documents. For example, assuming that the standard document type tag of the exploration report corresponds to the attribute of "needing to be archived", it means that all engineering documents of the exploration report type should be archived to the electronic file system.

[0064] Among them, the specific content of the document attributes is diverse, including the correspondence between engineering documents and the standard construction process and key project management actions, whether to be archived to the electronic file system, the mapping relationship with downstream systems (such as the financial collection system), etc.

[0065] Thus, for the stored engineering documents, corresponding operations can be performed according to the document attributes of their types (standard document type tags). For example, downstream systems such as the electronic file system, the financial collection system, and the customer system can be automatically allowed to access specific types of engineering documents (such as automatically archiving all engineering documents with the standard document type tag corresponding to the attribute of "needing to be archived" to the electronic file system), realizing automatic docking and automatic transfer of engineering documents between the engineering document management system and downstream systems.

[0066] In some embodiments, the document attributes include access permission attributes; the method for engineering document management in the embodiments of the present disclosure further includes:

[0067] S1031. Receive an access request for an engineering document.

[0068] S1032. Process the access request according to the access permission attribute of the standard document type tag of the engineering document.

[0069] As a way of the embodiments of the present disclosure, the document attributes include access permission attributes, and the access permission attributes describe what operation permissions various roles have for this type of engineering document. For example, the setting of one type of access permission attribute can be as shown in Table 1 below.

[0070] Table 1. Access Permission Attribute Table

[0071]

[0072] It should be understood that Table 1 is exemplary, and the specific situations of types, roles, and permissions are not limited thereto. For example, permissions may also be related to factors such as access time and access frequency.

[0073] Furthermore, when the engineering document management system receives a request to access one of the already stored engineering documents (access request), it can determine how to handle the access request (allow, deny, partially allow, etc.) according to the access request (from which role) and the document access permission attributes corresponding to the standard document type label of the engineering document to be accessed (what role is allowed what access).

[0074] Thus, the embodiments of the present disclosure can preset the access permissions for each type of engineering document (each standard document type label), and accordingly determine whether to allow access to it (for example, when personnel in the business area competent department want to audit the engineering documents in their field, it is allowed, and when they want to access the engineering documents in other fields, it is denied), without the need to contact the creator for authorization, thereby significantly improving work efficiency (such as audit efficiency) while fully ensuring information security.

[0075] In some embodiments, at least part of the preset engineering projects include preset construction activities, at least part of the construction activities are provided with corresponding standard activity type labels, and at least part of the standard activity type labels correspond to one or more standard document type labels.

[0076] As a way of the embodiments of the present disclosure, the construction activities included in each engineering project can also be preset according to the specific situation of each engineering project, that is, to set which construction work needs to be carried out in the engineering project, such as the construction of the power system, the construction of the engineering site (such as a communication base station), etc.

[0077] It should be understood that the specific classification methods (dimensions) of construction activities are diverse.

[0078] For example, a construction activity can represent all the construction work of a certain engineering site (such as a communication base station), or can also represent a more specific construction work (such as the construction work of the power system in an engineering site), etc.

[0079] It should be understood that the construction activities can also be "customized", that is, according to the habits of the corresponding country, region, and customer, as well as the specific situation of each engineering project, the construction activities to be included can be set; or the construction activities can also be "standard", that is, some of the standard construction activities pre-released by the headquarters can also be selected as the construction activities of the specific engineering project (which of course also have corresponding standard activity type labels).

[0080] Thus, construction activities are equivalent to "nodes" in the engineering document management system. Therefore, based on the status of the nodes of construction activities (under processing, unprocessed, completed), it can be determined which construction work is currently in progress, which construction work is pending, and which construction work has been completed in the engineering project, etc.

[0081] Among them, at least some construction activities have corresponding "standard activity type labels", which indicate what pre-defined "standard types" the construction activities are (such as construction work on the power supply system); and the standard activity type labels also correspond to standard document type labels, which indicate what types of engineering documents should be generated in the construction activities.

[0082] It should be understood that the corresponding relationship between the standard activity type labels and the standard document type labels can be diverse.

[0083] For example, only one engineering document may be generated in a construction activity, that is, one standard activity type label may only correspond to one standard document type label.

[0084] Again, multiple types of engineering documents may also be generated in a construction activity, that is, one standard activity type label may correspond to multiple standard document type labels.

[0085] Or, some construction activities may not require the generation of engineering documents, so the standard activity type labels may not correspond to standard document type labels either.

[0086] Relatively speaking, one standard document type label may only correspond to one standard activity type label (that is, this type of engineering document can only be generated in one type of construction activity), may also correspond to multiple standard activity type labels (that is, this type of engineering document may be generated in multiple types of construction activities), or may not correspond to a standard activity type label either (that is, this type of engineering document is not generated by construction activities).

[0087] Thus, through the correspondence between the standard activity type labels and the standard document type labels, the embodiments of the present disclosure link engineering documents with construction activities, that is, link engineering documents with the construction progress. Therefore, the standard construction process of the engineering project can be managed through engineering documents, and the generation of engineering documents in each construction activity can also be counted.

[0088] In some embodiments, the method for engineering document management in the embodiments of the present disclosure further includes:

[0089] S1041. Receive a construction document statistics instruction.

[0090] S1042. Select a construction activity that matches the construction document statistics instruction from the preset construction activities, determine the standard document type label corresponding to the standard activity type label of the selected construction activity, and obtain the construction document statistics result according to the determined standard document type label.

[0091] As a way of an embodiment of the present disclosure, when the project document management system receives a construction document statistics instruction (including a user input instruction or automatically statistics according to a preset instruction), it can select a construction activity that meets the requirements of the construction document statistics instruction from the construction activities, such as a certain type of construction activity (such as a construction activity with a specific standard activity type label), and / or a construction activity in a specific state (such as a completed or uncompleted construction activity), etc.

[0092] The above-selected construction activities have standard activity type labels, the standard activity type labels have corresponding standard document type labels, and the standard document type labels have corresponding project documents, and these project documents are also the project documents corresponding to the construction activities within a specific range. Therefore, these project documents can be analyzed to obtain the construction document statistics result (such as a statistical report).

[0093] It should be understood that the specific form of the above construction document statistics result (statistical report) is diverse and can be flexibly selected according to the requirements of the construction document statistics instruction.

[0094] For example, the construction document statistics result can also count the upload (completion) situation of the project documents corresponding to specific construction activities, such as counting the upload rate, upload time, etc. of the project documents of specific construction activities (such as the construction activities of some sites).

[0095] For another example, the construction document statistics result can indirectly count the situation of construction activities. For example, in specific construction activities (such as the construction activities of some sites), it can be counted which construction activities have been completed (all the project documents of the corresponding sites exist) and which have not been completed (the project documents of the corresponding sites are missing).

[0096] Furthermore, it can also count the completion rate, completion time (such as determined by the upload time of the last project document), the consumed duration, etc. (such as determined by the interval between the completion time of the previous construction activity and the completion time of this construction activity) of the construction activities according to the completion situation of the construction activities.

[0097] It should be understood that the completion situation of the construction activities can also be directly counted by the status of the nodes of the construction activities. Specifically, for example, it can be counted which of the nodes with the same certain type of construction activities (such as construction activities with a specific standard activity type label) are in the completed state, so as to obtain the completion situation of the corresponding construction activities, etc.

[0098] It should be understood that the specific statistical scope of the above construction document statistics results (statistical reports) can be flexibly selected according to the requirements of the construction document statistics instruction.

[0099] For example, the construction document statistics results can be "organization-level" or "multi-project (multiple engineering projects)", that is, the construction document statistics results can be the statistics of the sum of the construction activities in multiple preset engineering projects.

[0100] Again, the statistical report can also be "single-project (a single engineering project)", that is, the statistical report can only count the construction activities in a preset engineering project.

[0101] In some embodiments, the method for engineering document management according to the embodiments of the present disclosure further includes:

[0102] S1051. Receive an engineering document presentation instruction.

[0103] S1052. Select engineering documents that match the engineering document presentation instruction from the stored engineering documents according to the standard document type tags, and present the selected engineering documents according to the engineering document presentation instruction.

[0104] As a way of the embodiments of the present disclosure, it is also possible to find (screen out) the engineering documents that meet the requirements from the stored engineering documents according to the engineering document presentation instruction, and present (such as display) these engineering documents in a specific way, so that various users can view the corresponding engineering documents according to their own required dimensions (such as enterprise auditors finding the engineering documents related to the required business for auditing), improving the positioning speed of engineering documents.

[0105] It should be understood that the specific presentation methods of engineering documents are diverse. For example, engineering documents can be presented in different "views", and the forms of views can include standard document type views (displaying the corresponding engineering documents under the standard document type tags of the standard document type template), project document type views (displaying the engineering documents in the engineering project under the standard document types of the project document type template), site document classification views (displaying the engineering documents corresponding to the construction activities of each engineering site), etc.

[0106] It should be understood that the scope of the above-presented engineering documents is also flexibly selected according to the requirements of the engineering document presentation instruction, such as it can be "organization-level" or "multi-project", or it can be "single-project".

[0107] Example 1:

[0108] The following is an exemplary introduction to the specific process of a method for engineering document management according to the embodiments of the present disclosure.

[0109] Refer to Figure 4, the method for engineering document management in the embodiments of the present disclosure is executed by an engineering document management system, and enterprise standard maintainers, project management personnel for engineering projects, project members of engineering projects, and enterprise auditors can all operate on the engineering document management system.

[0110] Among them, enterprise standard maintainers are the managers of the entire engineering document management system, such as the staff at the enterprise headquarters.

[0111] Refer to Figure 5 , enterprise standard maintainers can edit the standard document types (standard document type tags) applicable to all subordinate units of the enterprise and the corresponding attribute information (document attributes, such as access permission attributes, archiving attributes, etc.) on the standard release platform of the engineering document management system at the headquarters, and then publish and maintain them in the form of a standard document type template.

[0112] Among them, enterprise standard maintainers can also modify and update the published standard document type template on the standard release platform, publish the modified content, and record the historical versions of various standard document type templates.

[0113] Among them, enterprise standard maintainers can also publish standard construction activities and the corresponding standard activity types (standard activity type tags) on the standard release platform, as well as the corresponding relationships between each standard activity type and the standard document type, that is, pre-determine the corresponding relationships between standard construction activities and engineering documents.

[0114] Among them, project management personnel for engineering projects are the administrators of specific engineering projects in the subordinate units of the enterprise. When there are engineering projects, they can set up corresponding engineering projects in the engineering document management, obtain the latest standard document types and attribute information from the above-published standard document type templates, and form a project document type template for each engineering project. The project document type template includes multiple standard activity types applicable to this engineering project.

[0115] For example, project management personnel for engineering projects can quickly reference the standard document type template in the engineering document management system, so as to realize generating the engineering document type template required for this engineering project with one click.

[0116] Or, project management personnel for engineering projects can select some standard activity types from the standard document type template according to the specific situation of this engineering project as the engineering document type template required for this engineering project.

[0117] In addition, refer to Figure 4 , project management personnel for engineering projects can also customize construction activities for the engineering project, determine at least some of the standard activity types corresponding to the customized construction activities (that is, determine their corresponding standard activity type tags), and obtain the corresponding relationships between the standard activity type tags and the standard document type tags.

[0118] In addition, referring to Figure 4 , project management personnel can also set "custom document types (custom document type labels)" for engineering projects as more detailed features applicable to specific engineering projects, which will not be described in detail herein.

[0119] Among them, project members are the personnel who specifically execute the work of engineering projects. During the progress of engineering projects, project members can obtain corresponding engineering documents and upload them to the engineering document management system (such as a single-project engineering document management system).

[0120] When project members upload engineering documents of a certain engineering project, the engineering document management system will display each standard document type in the engineering document type template of the engineering project (the custom document type can also be displayed). Project members must select a standard document type (the custom document type can also be selected), that is, add the standard document type label to the engineering document.

[0121] Alternatively, it can also be that when project members upload engineering documents to a specific node, the engineering document management system directly selects the corresponding standard document type (the custom document type can also be available) for the engineering document according to the node.

[0122] Among them, enterprise auditors are the personnel who audit engineering projects, so they need to view the engineering documents generated by engineering projects.

[0123] If enterprise auditors need to enter an engineering project to carry out audit work, they need to first initiate an organizational role permission application, clarify the name of the organizational role to be applied for and the scope of the engineering project to be accessed. After the approval (the headquarters configures the access permission attribute of the corresponding standard document type to allow the enterprise auditor to access), the user will automatically have the access permission to the engineering documents of the applied engineering project and the corresponding organizational role.

[0124] Exemplarily, referring to Figure 4 , the method for engineering document management in the embodiments of the present disclosure may include the following steps:

[0125] Step 1

[0126] Enterprise standard maintenance personnel maintain enterprise standard document types and publish them to each engineering project.

[0127] Exemplarily, this Step 1 may include the following content:

[0128] (1) Maintain standard document types

[0129] The enterprise standard maintainers maintain (add, delete, modify) the list, display order, etc. of standard document types on the standard release platform at the headquarters. Each standard document type can be represented by a unique number.

[0130] Among them, the standard document types and the project documents under them can form a tree-like hierarchical structure. When deleting a certain standard document type, it is also necessary to clarify the project document transfer rule, that is, clarify to which other standard document type the uploaded project documents under this standard document type should be transferred after deleting this standard document type.

[0131] (2) Maintain the attribute information of standard document types

[0132] The enterprise standard maintainers set the attribute information for each standard document type, such as whether the project documents of this type need to be archived in the electronic file system, the mapping relationship between this project document and the downstream system (such as the electronic file system), the organizational-level roles and access permission types that can access the standard document type, etc.

[0133] In addition, the enterprise standard maintainers also need to set the corresponding relationship between the standard document type and the standard construction activities (or key actions of project management).

[0134] (3) Release the standard document type

[0135] The enterprise standard maintainers release the above-mentioned maintained standard document types to the standard release platform of the project group for any project team to select.

[0136] (4) Based on the released standard document types, one or more standard document type templates can be customized for any project team to select.

[0137] Step 2

[0138] The project management personnel reference the standard document type template for the project, or cut the standard document type template (select the part of the standard document types involved in the business scope of this project from the standard document types) for the project, and obtain the project document type template applicable to the specific project.

[0139] Thus, in each project, only the standard document types in its project document type template can be displayed (standard document type view), and the unselected standard document types will not be displayed to the relevant users of the project, and these standard document types cannot be selected when users upload project documents, thus avoiding the trouble caused to users by seeing too much content irrelevant to this project.

[0140] Step 3

[0141] The project management personnel customize the construction activities (or project management actions) for the project.

[0142] Step 4

[0143] The project management personnel bind the standard construction activities released by the enterprise to the self-defined construction activities of the project (or bind the key project management actions to the project management actions of the project).

[0144] Specifically, this Step 4 may include the following content:

[0145] (1) Based on the self-defined construction activities of the project, the project management personnel select specific project sites to generate project site construction activity instances, and then the project team members upload project documents for each project site and select standard document types (and there may also be self-defined document types) for the project documents.

[0146] (2) Based on the project management actions of the project, the project management personnel generate one or more sets of project management action instances, and then the project team members upload the project documents of the project management actions and set standard document types for the project documents.

[0147] (3) For project documents that are not for construction at project sites (i.e., project documents that have no necessary relationship with construction activities), the project team members upload the project documents and select standard document types (and there may also be self-defined document types) for the project documents.

[0148] Step 5

[0149] The project team members upload project documents of project sites, project documents of project management actions or other project documents, and select standard document types (and there may also be self-defined document types) for the project documents.

[0150] Step 6

[0151] The project document management system automatically (equivalent to automatically generating construction document statistics instructions) generates single-project and organizational-level project document submission rates and submission cycle dashboards (construction document statistics results).

[0152] Since the corresponding relationship of what project documents should be output after the standard construction activities are completed has been pre-established (one construction activity corresponds to one type of project document, or one construction activity corresponds to multiple types of project documents), and the project documents can be uploaded to specific project sites, and it is clear which project site each project document belongs to, the project document management system can automatically judge whether the project documents under the standard document types corresponding to the standard construction activities of this project have been submitted, the submission cycle (calculated using the interval from the actual completion time of the construction activity to the project document submission time), etc.

[0153] Among them, if there are many engineering sites that need to be constructed for a certain engineering project, the engineering document management system can also calculate the submission rate of various types of engineering documents (among the completed engineering sites, the number of engineering sites that have submitted engineering documents / the number of completed engineering sites).

[0154] Specifically, this step 6 may include the following:

[0155] (1) The engineering document management system will automatically generate an organizational-level engineering document report in real time, including but not limited to:

[0156] (1-1) Organizational-level standard construction activity record engineering document upload progress report: Calculate the number and ratio of the construction activities of engineering sites that have completed the upload of record engineering documents in all completed standard engineering site construction activities of each engineering project, and support viewing the engineering sites that have not completed the upload of engineering documents and the names of missing engineering documents.

[0157] In particular, when a construction activity of an engineering site requires multiple engineering documents to be output, only when all engineering documents are uploaded is it considered that the upload of the construction of the engineering site is completed.

[0158] (1-2) Organizational-level standard construction activity record engineering document upload cycle report: Calculate the average time period required for each engineering project from the completion of the construction activity of the engineering site to the completion of the upload of the engineering document.

[0159] (1-3) Organizational-level engineering project management key action record engineering document upload integrity report: Calculate the action ratio of the record engineering documents that have been uploaded for all completed key actions of engineering project management of each engineering project.

[0160] (1-4) Organizational-level standard document type view report: Calculate the number of engineering documents uploaded under each standard document type of each engineering project.

[0161] Based on the above organizational-level reports, enterprise auditors can initially analyze which engineering projects and which standard document types have missing or risky engineering documents according to the requirements of business specifications, screen out the scope of engineering projects to be audited or spot-checked, control risks more precisely, and ensure compliance.

[0162] (2) In addition to the organizational-level engineering document report, the single-project engineering document management system can also automatically generate a single-project document report in real time for project team members to easily view and manage the progress of various engineering documents of this engineering project and use it as reference data during enterprise audits, including but not limited to:

[0163] (2-1) Report on the Upload Rate of Record Engineering Documents for Single-Project Standard Construction Activities: Statistic on the ratio of construction activities of engineering sites for which record engineering documents have been uploaded among all completed construction activities of engineering sites in this engineering project.

[0164] Among them, for the custom engineering site construction activities corresponding to the standard construction activities in this engineering project, if the actual completion time has been filled in, it is regarded that the construction activities of this engineering site should upload record engineering documents; if there is a consistent engineering site number in the engineering document management system with the construction activities of this engineering site, and the standard document type label of the engineering document corresponds to the standard construction activities bound to this construction activity, then it is regarded that the construction activities of this engineering site have uploaded record engineering documents.

[0165] (2-2) Report on the Upload Cycle of Record Engineering Documents for Single-Project Standard Construction Activities: Statistic on the time cycle from the completion of construction activities of engineering sites to the completion of uploading of engineering documents in this engineering project.

[0166] (2-3) Report on the View of Standard Document Types in the Single-Project Document Library: Statistic on the number of engineering documents, the number of automatically archived documents, the dynamics of engineering documents in a certain period (such as the recent 4 weeks), etc. under each standard document type in this engineering project.

[0167] Step 7

[0168] Enterprise auditors access the engineering project, view, download and audit the content of engineering documents.

[0169] Specifically, this Step 7 may include the following content:

[0170] (1) The enterprise pre-defines the organizational-level roles according to the needs of different business areas in advance, as well as the scope of engineering documents of standard document types that each organizational-level role can default to access, and embeds this permission control mechanism into the single-project engineering document management system as an additional permission control mechanism independent of single-project document authorization.

[0171] (2) Enterprise auditors need to first apply for the scope of engineering projects that can be accessed and the permissions of specific organizational-level roles. After approval, different organizational-level roles will be able to access and download the engineering documents related to their own business in the applied engineering projects.

[0172] Through the above organizational-level role permission mechanism, enterprise auditors can avoid applying for engineering document access and download permissions from the creators of engineering documents for each engineering project, significantly improving the authorization efficiency.

[0173] Step 8

[0174] The single-project engineering document management system automatically synchronizes the engineering documents of the corresponding standard document types to the downstream business system according to a specific mechanism.

[0175] Specifically, this step 8 may include the following:

[0176] (1) The enterprise first clarifies the list of the scope of engineering documents that the downstream system needs to obtain from the engineering document library and the synchronization rules.

[0177] (2) Based on the standard document types and synchronization rules, the engineering document library automatically synchronizes the engineering documents to the downstream systems, such as the electronic file system, the financial collection system, etc.

[0178] In a second aspect, referring to Figure 2 , an embodiment of the present disclosure provides an electronic device, which includes a memory and a processor; the memory stores a computer program executable by the processor, and when the computer program is executed by the processor, it implements any one of the engineering document management methods of the embodiments of the present disclosure.

[0179] In a third aspect, referring to Figure 3 , an embodiment of the present disclosure provides a computer-readable medium, on which a computer program is stored, and when the computer program is executed by the processor, it implements any one of the engineering document management methods of the embodiments of the present disclosure.

[0180] Among them, the processor is a device with data processing capabilities, which includes but is not limited to a central processing unit (CPU), etc.; the memory is a device with data storage capabilities, which includes but is not limited to a random access memory (RAM, more specifically such as SDRAM, DDR, etc.), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory (FLASH); the I / O interface (read / write interface) is connected between the processor and the memory and can realize the information interaction between the memory and the processor, which includes but is not limited to a data bus (Bus), etc.

[0181] Those of ordinary skill in the art can understand that all or some of the steps, systems, and functional modules / units in the devices disclosed above can be implemented as software, firmware, hardware, and their appropriate combinations.

[0182] In the hardware implementation manner, the division between the functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be executed by several physical components in cooperation.

[0183] Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit (CPU), a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-temporary medium) and a communication medium (or temporary medium). As known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH) or other disk storage; read-only compact disk (CD-ROM), digital versatile disk (DVD) or other optical disk storage; magnetic cassettes, magnetic tapes, disk storage or other magnetic storage; any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0184] The present disclosure has disclosed example embodiments, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for limiting purposes. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly stated, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, those skilled in the art will appreciate that various changes in form and detail may be made without departing from the scope of the present disclosure as set forth in the appended claims.

Claims

1. A method for engineering document management, wherein, Including: Receiving and storing engineering documents; each of the engineering documents corresponds to a preset engineering project, and the total number of the preset engineering projects is one or more; Determining a standard document type tag of the engineering document; the standard document type tag characterizes the type of the engineering document.

2. The method according to claim 1, wherein, Before receiving and storing the engineering document, it further includes: determining a project document type template of a preset engineering project; the project document type template includes a plurality of candidate standard document type tags; The determining the standard document type tag of the engineering document includes: selecting the standard document type tag of the engineering document from the candidate standard document type tags in the project document type template.

3. The method according to claim 2, wherein, The determining the project document type template of a preset engineering project includes: Referring to a preset standard document type template as the project document type template; Or, Selecting a part of the standard document type tags in the preset standard document type template to form the project document type template; Wherein, the standard document type template includes a plurality of preset standard document type tags.

4. The method according to claim 1, wherein, At least some of the standard document type tags have corresponding document attributes.

5. The method according to claim 4, wherein The document attributes include access permission attributes; the method further includes: Receiving an access request for the engineering document; Processing the access request according to the access permission attribute of the standard document type tag of the engineering document.

6. The method according to claim 1, wherein, At least some of the preset engineering projects include preset construction activities, at least some of the construction activities are provided with corresponding standard activity type tags, and at least some of the standard activity type tags correspond to one or more of the standard document type tags.

7. The method according to claim 6, wherein The method further includes: Receiving a construction document statistics instruction; Selecting the construction activities matching the construction document statistics instruction from the preset construction activities, determining the standard document type tags corresponding to the standard activity type tags of the selected construction activities, and obtaining a construction document statistics result according to the determined standard document type tags.

8. The method according to claim 1, wherein, The method further includes: Receiving an engineering document presentation instruction; Selecting the engineering documents matching the engineering document presentation instruction from the stored engineering documents according to the standard document type tag, and presenting the selected engineering documents according to the engineering document presentation instruction.

9. An electronic device, which includes a memory and a processor; the memory stores a computer program that can be executed by the processor, and when the computer program is executed by the processor, it implements the method for engineering document management according to any one of claims 1 to 8.

10. A computer-readable medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the method for engineering document management according to any one of claims 1 to 8.

Images