A method, system, device and medium for supervising the generation of electronic form information

Abstract

The application provides a kind of supervision electronic form information generation method, system, equipment and medium, comprising the following steps: S1: establishing the database model of electronic form;S2: according to national standard specification, industry standard and internal specification, the basic data of the inspection subitem, subitem engineering inspection item and inspection point are warehoused in combination with the database model in S1;S3: according to the project applied, the engineering project and its corresponding engineering subpart item business data are warehoused in combination with the database model in S1;S4: configure inspection subitem information;S5: configure subitem engineering inspection item information;S6: configure inspection point information;S7: according to the inspection subitem electronic form generated in combination with engineering inspection information according to the inspection subitem information configured in S4;The application solves the problem that the description content of the inspection result is greatly different due to human factors, and the efficiency of on-site information collection is low.

Description

Technical Field

[0001] This invention belongs to the field of supervision information collection, specifically relating to a method, system, device, and medium for generating electronic supervision form information. Background Technology

[0002] The daily work of project supervision involves a large number and variety of forms. Relying on traditional paper forms to complete the work faces problems such as difficulty in information collection, poor timeliness of information collection, and low efficiency in data transmission. The content of traditional paper forms is largely arbitrary and easily affected by factors such as the professional ability of the person filling them out, their on-site experience, and their depth of understanding of the connotation of standard and specification clauses. There are significant differences in the description, judgment, and handling of the same problem. Information collection from traditional paper forms is scattered, and the data in forms of the same unit project lacks correlation, which easily leads to incomplete information collection and duplicate data entry. Fixed paper forms are updated and iterated quickly with changes in industry standards and specifications. Traditional paper forms have poor adaptability to change. Most of the information collection tools developed for project supervision work currently are simply digitized paper forms and built in, suitable for completion on PCs. However, the daily work of project supervision is mostly on the construction site, and direct entry and analysis of on-site data can significantly improve work efficiency. However, on-site data collection is limited by the screen size and resolution of mobile terminals, and there are still problems such as dense content display and difficulty in clicking. With the widespread application of electronic information technology in the engineering field, the electronic conversion of inspection forms for supervision is becoming increasingly important. It's crucial to refine inspection content and optimize operational procedures for ease of use by on-site personnel, while ensuring that key points and important processes are detailed, problems are clearly described, and responsibilities are fully covered to reflect the level of supervision and control effectiveness. In the past, during platform construction and application, supervision companies went through two stages: a purely manual version migrating from original Word tables to web pages, and a version combining fixed inspection content selection and manual input. Although both achieved the transformation from traditional paper-based document filling to internet-based electronic information entry, numerous problems remain when collecting information on-site. These include complex terminal operations, large data entry volumes, arbitrary content entry, partial repetitive entry, empty generated content, low data utilization, and strong reliance on form creation. If these problems are not effectively resolved, and on-site personnel do not actively collect data, the information management work will be stuck at the data source. Summary of the Invention

[0003] The purpose of this invention is to provide a method, system, device and medium for generating electronic supervision form information, which solves the defects of low efficiency and poor effect in the existing supervision form information collection.

[0004] To achieve the above objectives, the technical solution adopted by the present invention is as follows: The present invention provides a method for generating electronic supervision form information, comprising the following steps: S1: Establish a database model for electronic forms. The database model includes engineering projects, engineering projects are associated with engineering sub-items, engineering sub-items are associated with inspection sub-items, inspection sub-items are associated with sub-item engineering inspection items, and sub-item engineering inspection items are associated with inspection points. S2: Based on national standards, industry standards and internal standards, and combined with the database model in S1, the basic data of the inspection sub-items, sub-project inspection items and inspection points are entered into the database; S3: Based on the project being applied and combined with the database model in S1, the project and its corresponding engineering sub-item business data are entered into the database. S4: Configure inspection item information, which includes the inspection item name, sub-item inspection items, and inspection conclusions; S5: Configure sub-item project inspection item information, which includes the sub-item project inspection item name, at least one inspection point, and sub-item project inspection item prompts; S6: Configure checkpoint information, which includes checkpoint name, type, and standardized description; S7: Based on the inspection item information configured in S4 and combined with the project inspection information, generate an electronic form for the inspection item, and complete the collection and filling of the supervision inspection information based on the generated electronic form.

[0005] Preferably, the method for configuring and checking sub-item information in S4 includes: S401: Select the project and its corresponding sub-item nodes; S402: Select pre-configured inspection items from the basic data of the inspection items; S403: The basic data of the corresponding sub-item inspection items are associated with the inspection items selected in S402, and the sub-item inspection items included in the inspection items are selected from the basic data of the sub-item inspection items. S404: Configure the inspection conclusions corresponding to the inspection sub-items.

[0006] Preferably, the method for configuring sub-item project inspection item information in S5 includes: S501: Select the corresponding sub-item inspection item from the inspection items configured in S4; S502: Associate the basic data of the inspection points corresponding to the sub-item inspection items selected in S501, and select the inspection points pre-included in the sub-item inspection items from the basic data of the inspection points. S503: Configure the sub-item inspection item prompts corresponding to the sub-item inspection items.

[0007] Preferably, the method for configuring checkpoint information in S6 includes: S601: Select an inspection point from the list of inspection points included in the sub-item inspection items configured in S5; S602: Configure the type and standardized description of the checkpoint selected in S601.

[0008] Preferably, the checkpoint types include check, record, single selection, and multiple selection.

[0009] Preferably, the standardized narrative consists of a fixed description and inspection data; The fixed description is extracted from the inspection content of national standards, industry standards, and internal standards. The inspection data is automatically populated from the engineering inspection information.

[0010] Preferably, the electronic form in S7 includes a header, a stem, and a footer; The header consists of the engineering project described in S3 and its corresponding engineering sub-item information; The table stem is composed of a standardized description of the checkpoints described in S6; The table footer consists of the inspection conclusions of the inspection items described in S4.

[0011] A system for generating electronic forms for supervision includes: A database model building unit is used to build a database model for electronic forms. The database model includes engineering projects, engineering projects are associated with engineering sub-items, engineering sub-items are associated with inspection sub-items, inspection sub-items are associated with sub-item engineering inspection items, and sub-item engineering inspection items are associated with inspection points. The basic data entry unit is used to enter the basic data of the inspection items, sub-item inspection items and inspection points into the database according to national standards, industry standards and internal standards, combined with the database model; The business data entry unit is used to enter the business data of the project and its corresponding engineering sub-items into the database based on the project being applied and the database model in S1. The inspection item information configuration unit is used to configure inspection item information, which includes the inspection item name, inspection items of the sub-item project, and inspection conclusions. The sub-item project inspection item information configuration unit is used to configure sub-item project inspection item information, which includes the sub-item project inspection item name, at least one inspection point, and sub-item project inspection item prompts; A checkpoint information configuration unit is used to configure checkpoint information, which includes checkpoint name, type, and standardized description. The electronic form generation unit is used to generate electronic forms for the configured inspection items based on the engineering inspection information, and to complete the collection and filling of the supervision inspection information based on the generated electronic forms.

[0012] A processing apparatus comprising at least a processor and a memory, wherein a computer program is stored in the memory, and the processor executes steps to implement the method when running the computer program.

[0013] A computer storage medium having computer-readable instructions stored thereon, the computer-readable instructions being executable by a processor to perform the steps according to the method.

[0014] Compared with the prior art, the beneficial effects of the present invention are: This invention provides a method for generating electronic forms for supervision, which, compared with existing electronic forms, solves the problems of difficult operation on terminals in densely populated areas and limited form iteration updates. This application establishes a database model on the terminal, configuring inspection sub-item information, sub-project inspection item information, and inspection point information; it generates electronic forms for inspection sub-items based on the configured inspection sub-item information and project inspection information; in practical applications, operators associate the corresponding project electronic forms, and select the corresponding inspection results based on the actual inspection item judgment results in the electronic forms. This operation requires little or no editing of the inspection results. This application optimizes form association and generation rules, standardizes the language of inspection record descriptions, and significantly reduces manual input time and secondary editing work, truly solving the problems of large differences in description content due to human factors and low efficiency in on-site information collection. Attached Figure Description

[0015] Figure 1 This is a flowchart of the method for collecting supervision form information using a mobile terminal according to the present invention; Figure 2 This is a diagram illustrating the form filling format in the background technology; Figure 3 This is a schematic diagram illustrating an example of electronic form filling in an embodiment of the present invention. Detailed Implementation

[0016] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0017] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0018] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0019] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrases "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0020] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0021] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0022] Example 1 like Figure 1 , Figure 2 As shown in this embodiment, a method for generating electronic supervision form information includes: S1: Establish a database model for electronic forms. The database model includes engineering projects, engineering projects are associated with engineering sub-items, engineering sub-items are associated with inspection sub-items, inspection sub-items are associated with sub-item engineering inspection items, and sub-item engineering inspection items are associated with inspection points.

[0023] A database model for the electronic form is created using a database modeling tool, such as PowerDesigner. The electronic form database model includes a basic database model and a business database model.

[0024] The basic database model includes inspection sub-item entities, which are related to sub-project inspection item entities through foreign keys, and sub-project inspection item entities are related to checkpoint entities through foreign keys.

[0025] The business database model includes entities for engineering projects, engineering categories, and engineering sub-items. Engineering project entities are associated with engineering category entities via foreign keys, and engineering category entities are associated with engineering sub-item entities via foreign keys. Engineering sub-items include entities starting from the unit entity and sequentially associated with sub-units, sections, sub-sections, sub-items, and sub-sub-items via foreign keys.

[0026] The business database model also includes inspection sub-item entities, which are linked to sub-project inspection item entities via foreign keys. Sub-project inspection item entities are linked to checkpoint entities via foreign keys. The lowest-level entities of project sub-items are linked to inspection sub-item entities via foreign keys.

[0027] The business database model also includes a supervisor entity, which is associated with the supervisor through foreign keys. The project entity includes attributes such as project number, project name, and project address.

[0028] After the electronic form database model is established, a relational database, such as MySQL or Oracle, is selected. Based on this database model, corresponding database tables and foreign key mapping relationships are created in the database.

[0029] S2: Based on national standards, industry standards, and internal standards, and combined with the database model in S1, the basic data of the inspection sub-items, sub-project inspection items, and inspection points are entered into the database.

[0030] The basic data of inspection items, sub-item inspection items, and inspection points are entered into the database. Specifically, this includes the following steps: 1) Organize and standardize documents We compile the latest national standards, industry standards, and internal regulations related to the engineering industry into electronic documents, typically in PDF or Office format. When these documents change, such as with new standards or the release of new versions, we promptly compile them, parse them, and store the resulting inspection content in a database.

[0031] 2) Parsing the specification document For standardized electronic documents of different formats, corresponding parsing technologies are used to parse the electronic documents into structured data. For example, iText technology is used to parse PDF format files, and POI technology is used to parse Office format files.

[0032] Generally, national standards are the foundation for the same construction specifications, industry standards have higher requirements, and internal standards have the highest requirements. Therefore, for the same construction specifications, if there are internal standards, use the electronic document of the internal standard; if there are no internal standards, use the electronic document of the industry standard; and if there are no industry standards, use the electronic document of the national standard.

[0033] When parsing specification documents, the specification documents are parsed into relational structured data. For example, a certain inspection item that is parsed needs to be associated with the corresponding specification document, the inspection items of the sub-items included, and the inspection points associated with each inspection item of the sub-items.

[0034] During parsing, the inspection content is extracted from the electronic specification documents on a per-item basis. When multiple electronic specification documents contain the same type of inspection items, they need to be parsed into two inspection items because the applied project types are different or the included inspection items are inconsistent.

[0035] 3) Check the data entry into the database. After the standardized electronic document parsing is completed, the parsed data needs to be validated, such as for incomplete data, garbled characters, or data units that do not conform to national standards. After data validation, the validated parsed data is stored in the corresponding database table.

[0036] S3: Based on the project being applied and combined with the database model in S1, the project and its corresponding engineering sub-items business data are entered into the database.

[0037] For the project to be applied, the project information and its sub-items are extracted from electronic documents such as project tenders, designs, and surveys, and the project category is configured. Combined with the database tables established in S1 based on the database model, the corresponding project data and its sub-items are then stored in the database.

[0038] The extracted project information also needs to include the information of the supervisors, managers, and their corresponding management permissions, so that subsequent supervision, inspection, and approval work can be carried out.

[0039] S4: Configure inspection item information, which includes the inspection item name, inspection item of the sub-project, and inspection conclusion.

[0040] The methods for configuring the inspection of item information in S4 include: S401: Select the project and its corresponding sub-item node.

[0041] After logging into the system, the system administrator selects the pre-configured inspection and analysis project, then selects the sub-item node of the project to be inspected, typically selecting the lowest-level node of the sub-item. Based on the project information entered in S3, the system automatically associates the supervisor and the corresponding inspection and approval personnel for the selected sub-item node.

[0042] S402: Select a pre-configured inspection item from the basic data of the inspection items.

[0043] The system automatically retrieves the basic data list of inspection items entered in S2. The list consists of inspection item names. Fuzzy search technology allows for quick selection of pre-configured inspection items. Only one inspection item can be selected when configuring inspection item information.

[0044] Once an inspection item is selected, the information of the standard document on which the selected inspection item is based is automatically associated from the basic data of the inspection item entered in S2. This makes it easy to confirm whether the selected inspection item is a pre-configured inspection item. Therefore, there may be multiple standard documents containing inspection items with the same name.

[0045] At the same time, it automatically generates inspection item numbers, and the numbering rules are, for example, a combination of project number, specification document number, engineering sub-item number and date.

[0046] S403: Associate the basic data of the corresponding sub-item inspection items with the inspection sub-item selected in S402, and select the sub-item inspection items pre-included in the sub-item inspection items from the basic data of the sub-item inspection items.

[0047] Once an inspection item is selected, the basic data of the inspection item entered in S2 will automatically generate a list of sub-item inspection items included in the selected inspection item. The list of sub-item inspection items consists of the names of each sub-item inspection item. Select a sub-item inspection item from the list of sub-item inspection items.

[0048] For example, in oil extraction projects, the "Parallel Inspection Record of Gathering and Transmission Pipeline Welding" sub-item is selected for inspection. The standard document on which it is based is "SY / T 4204-2019 Oil and Gas Construction Engineering Construction Quality Acceptance Specification for Oil and Gas Field Gathering and Transmission Pipeline Engineering". The list of sub-item inspection items included is "process, materials and appearance, etc."

[0049] S404: Configure the inspection conclusions corresponding to the inspection sub-items.

[0050] The inspection conclusions for each inspection item include pass and fail conclusions. Pass conclusions consist of a fixed description, extracted from the specification document and entered into the database as attribute data for that inspection item in step S2. When configuring a pass conclusion, this fixed description is automatically associated, and its content can be edited and modified.

[0051] The configuration of non-conforming inspection conclusions is divided into multiple categories, each corresponding to a specific non-conforming item. Each non-conforming inspection conclusion consists of a fixed description and inspection data. The fixed description is extracted from the specification document and entered into the database as attribute data for that inspection item in step S2. When configuring a passing inspection conclusion, the fixed description is automatically retrieved. The inspection data is implemented using wildcard technology, with the corresponding wildcard configured at the corresponding position in the fixed description.

[0052] When in use, based on the non-conforming items in the inspection data, the system automatically associates them with the non-conforming conclusion configuration items and replaces the wildcards in the non-conforming conclusion configuration items with the corresponding non-conforming data to form a complete non-conforming conclusion.

[0053] S5: Configure sub-item project inspection item information, which includes the sub-item project inspection item name, at least one inspection point, and sub-item project inspection item prompts.

[0054] The methods for configuring sub-item project inspection item information in S5 include: S501: Select the corresponding sub-item inspection item from the inspection items configured in S4; From the list of inspection items configured in S4, which consists of the names of the inspection items, select an inspection item. The selected inspection item will automatically associate with the configured sub-item inspection items. Select the sub-item inspection item, which includes the sub-item inspection item name.

[0055] S502: Associate the basic data of the inspection points corresponding to the sub-item inspection items selected in S501, and select the inspection points pre-included in the sub-item inspection items from the basic data of the inspection points. Once a sub-item inspection item is selected, the list of inspection points included in the selected sub-item inspection item will be automatically generated from the basic data of the sub-item inspection item entered in S2. The list of inspection points consists of the inspection point name, type, and operation. A certain inspection point can be deleted or edited, but a new inspection point cannot be added.

[0056] S503: Configure the sub-item inspection item prompts corresponding to the sub-item inspection items.

[0057] The prompt for inspection items of sub - projects consists of fixed descriptions, which are extracted from the specification documents and entered into the database as attribute data of the inspection items of the sub - projects in step S2. When configuring the prompt for inspection items of sub - projects, the fixed description is automatically associated. The prompt for inspection items of sub - projects is used as the standard for determining whether the inspection result is qualified during inspection.

[0058] Configuring the information of inspection items of sub - projects also includes the configuration item of "allowing multiple records during inspection". By default, multiple records are not allowed during inspection, and it can be selected to allow multiple records during inspection. For example, for the inspection item of "weld appearance inspection" of a sub - project, which includes multiple inspection positions, at this time, it is necessary to allow multiple records during inspection to distinguish specific inspection positions.

[0059] Configuring the information of inspection items of sub - projects also includes two configuration items: "whether on - site pictures are required for each record" and "whether a conclusion is required for each record". By default, on - site pictures are not required for each record and a conclusion is not required for each record, and it can be configured to require on - site pictures for each record and a conclusion for each record.

[0060] When it is configured that on - site pictures are required for each record, during use, on - site pictures need to be uploaded for the inspection item of this sub - project. When it is configured that a conclusion is required for each record, during use, the standardized conclusion description is automatically associated for the inspection item of this sub - project.

[0061] S6: Configure inspection point information, where the inspection point information includes inspection point name, type, and standardized description.

[0062] The method for configuring inspection point information in S6 includes: S601: Select an inspection point from the list of inspection points included in the inspection items of sub - projects configured in S5; S602: Configure the type and standardized description of the inspection point selected in S601.

[0063] Inspection point types include inspection, record, single - selection, and multi - selection.

[0064] The inspection type represents that it is necessary to judge whether the result meets the requirements according to the inspection information; the record type represents that it is necessary to enter the measured result value according to the inspection information; the single - selection type represents that it is necessary to select a result item according to the inspection information; the multi - selection type represents that one or more result selection items are selected according to the inspection content.

[0065] When configuring inspection point information, the options of the type configuration item are set to four items: inspection, record, single - selection, and multi - selection. When configuring, first select the inspection point type. When the multi - selection type is selected, the option information of the multi - selection type is automatically associated.

[0066] Multiple-choice option information is extracted from the specification document and entered into the database as attribute data for that checkpoint in step S2. Multiple-choice options can be added and deleted.

[0067] The standardized description includes two configuration items: "Required" and "Description Content". The "Required" option is a radio button, with "Yes" selected by default. When configured as "Yes", it means that the checkpoint needs description content; when configured as "No", it means that the checkpoint does not need description content.

[0068] The "Description Content" configuration item is divided into qualified and unqualified configuration items. The "Description Content" configuration item consists of a fixed description and inspection data. The fixed description is extracted from the inspection content of national standards, industry standards, and internal standards, while the inspection data is automatically filled in by engineering inspection information.

[0069] The fixed description is extracted from the specification document and entered into the database as attribute data for that checkpoint in step S2. When configuring checkpoint standardization, this fixed description is automatically associated as the default information for the "narrative content" configuration item. The check data is implemented using wildcard technology; corresponding wildcards are configured at the corresponding positions in the fixed description dialogue, and multiple wildcards can be configured.

[0070] When in use, based on the inspection information, the checkpoint "narrative content" configuration item is automatically associated, and the wildcards in the "narrative content" configuration item are replaced with the corresponding inspection data to form a complete standardized narrative.

[0071] S7: Based on the inspection item information configured in S4 and combined with the project inspection information, generate an electronic form for the inspection item, and complete the collection and filling of the supervision inspection information based on the generated electronic form.

[0072] The electronic form described in S7 includes a header, a stem, and a footer. The header consists of the project items and their corresponding project sub-items as described in S3. The stem consists of the standardized description of the checkpoints as described in S6. The footer consists of the inspection conclusions of the inspection sub-items as described in S4.

[0073] Once the inspection items and associated sub-item inspection items, as well as the inspection points contained in the sub-item inspection items, are configured in S4, a supervision electronic form information entry template is generated in the system. The supervision electronic form information entry template includes a header section and an information entry section.

[0074] The header section contains project information and related sub-item information, such as project name, inspection location, and construction unit. The information entry section mainly consists of configured inspection sub-items, and sequentially associated sub-item inspection items and inspection point information.

[0075] When using the system, supervisors should follow the electronic form information entry template, conduct actual measurements, and enter the inspection information in the corresponding locations. For single-choice and multiple-choice inspection points, select the corresponding options. For inspection and record-type inspection points, enter the inspection information in the corresponding location of the standardized description section for that inspection point. After completion, submit the form for system verification and management approval.

[0076] After the supervisors enter the inspection information into the electronic supervision form information entry template and submit it, the system automatically generates the electronic supervision form.

[0077] The electronic form for supervision consists of three parts: header, stem, and footer.

[0078] The header section consists of the project information described in S3 and its corresponding project sub-items, including project name, number, inspection location, and construction unit.

[0079] The stem section consists of standardized descriptions of the checkpoints as described in S6. For checkpoints of the inspection and record types, the inspection data portion of the "Description Content" configuration item in the standardized description is filled with wildcards at the corresponding positions by the inspection information entered by the supervisor. For checkpoints of the multi-select type, the inspection data portion of the "Description Content" configuration item in the standardized description consists of the selected options.

[0080] The table footer consists of the inspection conclusions for the inspection items described in S4. When all inspection results are satisfactory, the inspection item is deemed satisfactory. If any inspection result at any checkpoint is unsatisfactory, the inspection item is deemed unsatisfactory. Wildcards in the configured unsatisfactory conclusions are filled in by the corresponding inspection data from the unsatisfactory checkpoints.

[0081] The end of the form also includes information on the inspector and the date. The inspector information is automatically linked from the project supervisor information entered in S3, and the date information is automatically generated by the system.

[0082] Example 2 This embodiment provides a system for generating electronic forms for supervision, including: A database model building unit is used to build a database model for electronic forms. The database model includes engineering projects, engineering projects are associated with engineering sub-items, engineering sub-items are associated with inspection sub-items, inspection sub-items are associated with sub-item engineering inspection items, and sub-item engineering inspection items are associated with inspection points. The basic data entry unit is used to enter the basic data of the inspection items, sub-item inspection items and inspection points into the database according to national standards, industry standards and internal standards, combined with the database model; The business data entry unit is used to enter the business data of the project and its corresponding engineering sub-items into the database based on the project being applied and the database model in S1. The inspection item information configuration unit is used to configure inspection item information, which includes the inspection item name, inspection items of the sub-item project, and inspection conclusions. The sub-item project inspection item information configuration unit is used to configure sub-item project inspection item information, which includes the sub-item project inspection item name, at least one inspection point, and sub-item project inspection item prompts; A checkpoint information configuration unit is used to configure checkpoint information, which includes checkpoint name, type, and standardized description. The electronic form generation unit is used to generate electronic forms for the inspection items based on the configured inspection item information and the engineering inspection information.

[0083] Example 3 This embodiment provides a processing device corresponding to the method for generating electronic form information for supervision provided in Embodiment 1. The processing device can be a processing device for a client, such as a mobile phone, laptop, tablet computer, desktop computer, etc., to execute the method of Embodiment 1.

[0084] The processing device includes a processor, a memory, a communication interface, and a bus. The processor, memory, and communication interface are connected via the bus to enable communication between them. The memory stores a computer program that can run on the processor. When the processor runs the computer program, it executes the method for generating electronic supervision form information provided in Embodiment 1.

[0085] In some embodiments, the memory may be high-speed random access memory (RAM). It may also include non-volatile memory, such as at least one disk storage device.

[0086] In other embodiments, the processor can be a general-purpose processor of various types, such as a central processing unit (CPU) or a digital signal processor (DSP), and is not limited thereto.

[0087] Example 4 The method for generating electronic form information for supervision described in Embodiment 1 can be specifically implemented as a computer program product. The computer program product may include a computer-readable storage medium on which computer-readable program instructions for executing the method for generating electronic form information for supervision described in Embodiment 1 are loaded.

[0088] A computer-readable storage medium can be a tangible device that holds and stores instructions used by an instruction execution device.

[0089] Computer-readable storage media may be, for example, but not limited to, electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any combination thereof.

[0090] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for generating electronic form information for supervision, characterized in that, Includes the following steps: S1: Establish a database model for electronic forms. The database model includes engineering projects, engineering projects are associated with engineering sub-items, engineering sub-items are associated with inspection sub-items, inspection sub-items are associated with sub-item engineering inspection items, and sub-item engineering inspection items are associated with inspection points. S2: Based on national standards, industry standards and internal standards, and combined with the database model in S1, the basic data of the inspection sub-items, sub-project inspection items and inspection points are entered into the database; S3: Based on the project being applied and combined with the database model in S1, the project and its corresponding engineering sub-item business data are entered into the database. S4: Configure inspection item information, which includes the inspection item name, sub-item inspection items, and inspection conclusions; S5: Configure sub-item project inspection item information, which includes the sub-item project inspection item name, at least one inspection point, and sub-item project inspection item prompts; S6: Configure checkpoint information, which includes checkpoint name, type, and standardized description; S7: Based on the inspection item information configured in S4 and combined with the project inspection information, generate an electronic form for the inspection item, and complete the collection and filling of the supervision inspection information based on the generated electronic form.

2. The method for generating electronic supervision form information according to claim 1, characterized in that, The method for configuring and checking itemized information as described in S4 includes: S401: Select the project and its corresponding sub-item nodes; S402: Select pre-configured inspection items from the basic data of the inspection items; S403: The basic data of the corresponding sub-item inspection items are associated with the inspection items selected in S402, and the sub-item inspection items included in the inspection items are selected from the basic data of the sub-item inspection items. S404: Configure the inspection conclusions corresponding to the inspection sub-items.

3. The method for generating electronic supervision form information according to claim 1, characterized in that, The method for configuring sub-item project inspection item information as described in S5 includes: S501: Select the corresponding sub-item inspection item from the inspection items configured in S4; S502: Associate the basic data of the inspection points corresponding to the sub-item inspection items selected in S501, and select the inspection points pre-included in the sub-item inspection items from the basic data of the inspection points. S503: Configure the sub-item inspection item prompts corresponding to the sub-item inspection items.

4. The method for generating electronic supervision form information according to claim 1, characterized in that, The method for configuring checkpoint information as described in S6 includes: S601: Select an inspection point from the list of inspection points included in the sub-item inspection items configured in S5; S602: Configure the type and standardized description of the checkpoint selected in S601.

5. The method for generating electronic supervision form information according to claim 4, characterized in that, The checkpoint types include check, record, single selection, and multiple selection.

6. The method for generating electronic supervision form information according to claim 4, characterized in that, The standardized narrative consists of fixed descriptions and inspection data; The fixed description is extracted from the inspection content of national standards, industry standards, and internal standards. The inspection data is automatically populated from the engineering inspection information.

7. The method for generating electronic supervision form information according to claim 1, characterized in that, The electronic form described in S7 includes a header, a stem, and a footer; The header consists of the engineering project described in S3 and its corresponding engineering sub-item information; The table stem is composed of a standardized description of the checkpoints described in S6; The table footer consists of the inspection conclusions of the inspection items described in S4.

8. A system for generating electronic forms for supervision, characterized in that, include: A database model building unit is used to establish a database model for electronic forms. The database model includes engineering projects, engineering projects are associated with engineering sub-items, engineering sub-items are associated with inspection sub-items, inspection sub-items are associated with sub-item engineering inspection items, and sub-item engineering inspection items are associated with inspection points. The basic data entry unit is used to enter the basic data of the inspection items, sub-item inspection items and inspection points into the database according to national standards, industry standards and internal standards, combined with the database model; The business data entry unit is used to enter the business data of the project and its corresponding engineering sub-items into the database based on the project being applied and the database model in S1. The inspection item information configuration unit is used to configure inspection item information, which includes the inspection item name, inspection items of the sub-item project, and inspection conclusions. The sub-item project inspection item information configuration unit is used to configure sub-item project inspection item information, which includes the sub-item project inspection item name, at least one inspection point, and sub-item project inspection item prompts; A checkpoint information configuration unit is used to configure checkpoint information, which includes checkpoint name, type, and standardized description. The electronic form generation unit is used to generate electronic forms for the configured inspection items based on the engineering inspection information, and to complete the collection and filling of the supervision inspection information based on the generated electronic forms.

9. A processing apparatus, the processing apparatus comprising at least a processor and a memory, the memory storing a computer program, characterized in that, When the processor runs the computer program, it performs steps to implement the method of any one of claims 1 to 7.

10. A computer storage medium, characterized in that, It stores computer-readable instructions that can be executed by a processor to perform the steps of the method according to any one of claims 1 to 7.

Images