Data association sharing method in nuclear power project

Abstract

The embodiment of the invention relates to the technical field of data sharing, in particular to a data association sharing method in a nuclear power project, which comprises the following steps: defining the type and style of data of each stage of the nuclear power project; determining an association mode of the data in each stage according to the type and style of the data; in each stage, the defined data type and style are adopted to generate data applied to the nuclear power project in each stage; associating the generated data in each stage according to the determined association mode; the associated data is shared so that different departments use the data at various stages. According to the method provided by the embodiment of the invention, the association mode of the data in each stage of the nuclear power project is determined through the type and style of the data, and the associated data in each stage is shared, so that different departments can use the data in each stage, a collaborative working environment can be established, the accuracy, uniqueness and integrity of research and development data are ensured, and the research and development efficiency is improved. Therefore, the conversion period from research and development to production can be shortened.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of data sharing, and specifically to a data association sharing method in a nuclear power project. Background Art

[0002] The statements herein merely provide background information related to the present application and do not necessarily constitute prior art.

[0003] Nuclear power engineering is mainly used for the research and development of nuclear power plants. It has the characteristics of a long research and development cycle, many professionals involved, and a huge amount of data. From the perspective of the project cycle, each stage of the project, such as conceptual design, preliminary design, and detailed design, will generate a large amount of data such as results reports. These data are usually archived in the form of files, and this archiving method may result in the inability to effectively reuse and inherit these data; from a professional perspective, each profession, such as core design, radiation shielding, and civil engineering layout, uses its own professional software for research and development, but the data between these professional software cannot be shared, which brings many inconveniences to the implementation of nuclear power engineering. Summary of the invention

[0004] A brief overview of the present application is provided below in order to provide a basic understanding of certain aspects of the present application. It should be understood that this overview is not an exhaustive overview of the present application. It is not intended to identify the key or important parts of the present application, nor is it intended to limit the scope of the present application. Its purpose is merely to present certain concepts in a simplified form as a prelude to a more detailed description discussed later.

[0005] An embodiment of the present application provides a data association and sharing method in a nuclear power project, which includes the following steps: S10: defining the type and style of data in each stage of the nuclear power project; S20: determining the association method of the data in each stage based on the type and style of the data; S30: in each stage, using the type and style of the data defined in step S10 to generate data applied to the nuclear power project in each stage; S40: according to the association method of step S20, associating the data generated in step S30 in each stage; S50: sharing the data associated in step S40 so that different departments can use the data in each stage.

[0006] The method provided in the embodiment of the present application can generate data for actual application in various stages of nuclear power engineering by predetermining the types and styles of data in various stages of nuclear power engineering, and can also determine the association method of data in various stages based on the types and styles of data in various stages. Then, the data after association in various stages can be shared, so that different departments can use the data in various stages. This is conducive to establishing a collaborative working environment and ensuring the accuracy, uniqueness and integrity of R&D data, thereby shortening the transformation cycle from R&D to production, realizing the transition from result management to process control, and thus improving the level and effect of data management. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to further illustrate the above and other advantages and features of the present application, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. The accompanying drawings together with the following detailed description are included in this specification and form a part of this specification. Elements with the same function and structure are represented by the same reference numerals. It should be understood that these drawings only describe typical examples of the present application and should not be regarded as limiting the scope of the present application.

[0008] Figure 1 is a schematic flow chart of a data association sharing method in a nuclear power project according to an embodiment of the present application;

[0009] Figure 2 It is a schematic block diagram of the nuclear power engineering data architecture according to an embodiment of the present application.

[0010] It should be noted that the drawings are not necessarily drawn to scale, but are merely shown in a schematic manner that does not affect the reader's understanding. DETAILED DESCRIPTION

[0011] Exemplary embodiments of the present application will be described below in conjunction with the accompanying drawings. For the sake of clarity and conciseness, not all features of the actual implementation are described in the specification. However, it should be understood that many implementation-specific decisions must be made in the process of developing any such actual implementation in order to achieve the developer's specific goals, such as meeting those constraints related to the system and business, and these constraints may vary from implementation to implementation. In addition, it should be understood that although the development work may be very complex and time-consuming, it is only a routine task for those skilled in the art who benefit from the content of this application.

[0012] It is also necessary to explain here that, in order to avoid obscuring the present application due to unnecessary details, only the device structure and / or processing steps closely related to the scheme according to the present application are shown in the accompanying drawings, while other details that are not closely related to the present application are omitted.

[0013] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in this application should have the common meanings understood by persons with ordinary skills in the field to which this application belongs.

[0014] In the description of the embodiments of the present application, “plurality” means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0015] In the relevant technology, for the current nuclear power project, it can include multiple stages such as nuclear power research and development, design, procurement, construction and commissioning. In each stage of the nuclear power project, data type attributes and data results play a vital role. If the data attributes and data results are not systematically standardized, it will cause some downstream engineering stages to reference a certain version of the data, while other downstream engineering stages will reference other versions of data that are different from it. This will eventually lead to deviations in product specifications, simulation calculations and other results, which may cause major safety accidents and economic property losses in serious cases. Therefore, it is very important to associate and share data at each stage to achieve the management of data attributes, versions, permissions, changes, storage, and distribution at each stage.

[0016] In response to the above technical problems, an embodiment of the present application provides a data association sharing method in a nuclear power project. Figure 1 is a schematic flow chart of a data association sharing method in a nuclear power project according to an embodiment of the present application, such as Figure 1 As shown, the method includes the following steps S10 to S50.

[0017] S10: Define the type and style of data at each stage of nuclear power engineering.

[0018] S20: Determine the association method of the data at each stage according to the type and style of the data.

[0019] S30: In each stage, the data type and style defined in step S10 are used to generate data applied to the nuclear power project in each stage.

[0020] S40: According to the association method of step S20, the data generated in step S30 are associated in each stage.

[0021] S50: Share the data associated in step S40 so that different departments can use the data at different stages.

[0022] The method provided in the embodiment of the present application can generate data for actual application in various stages of nuclear power engineering by predetermining the types and styles of data in various stages of nuclear power engineering, and can also determine the association method of data in various stages based on the types and styles of data in various stages. Then, the data after association in various stages can be shared, so that different departments can use the data in various stages. This is conducive to establishing a collaborative working environment and ensuring the accuracy, uniqueness and integrity of R&D data, thereby shortening the transformation cycle from R&D to production, realizing the transition from result management to process control, and thus improving the level and effect of data management.

[0023] In some embodiments, a nuclear power project may include multiple stages, such as a design stage, a manufacturing stage, a construction stage, a commissioning stage, a delivery stage, an operation and maintenance stage, etc.

[0024] In some embodiments, the types of data corresponding to each stage of a nuclear power project may be different. The types of data may include the name, unit, type, specialty, version, status, document code, responsible person, etc. corresponding to the data.

[0025] In some embodiments, the data corresponding to each stage of a nuclear power project may have different formats. For example, for a reactor shell, the format of the data in the design stage is the size parameters of the reactor shell, and the format of the data in the manufacturing stage is the material selection and manufacturing method of the reactor shell.

[0026] In some embodiments, the data style may also include a version of the data. The same data should maintain an association relationship at each stage. For example, the old version of the data is retained, and the latest version is applied in accordance with the principle of application when the data is applied.

[0027] A version display text box may be provided in the interactive interface, and the version of the current data may be displayed in the version display text box. If the system defines the data versions as version A, version B, and version C, then version A is the default after successful creation. In some embodiments, if version A data is modified or upgraded to version A1, then the version of the current data displayed in the version display text box is version A1. In addition, if the data has been modified or upgraded, the historical version of the data can also be viewed.

[0028] In some embodiments, the nuclear power engineering data (SSC) architecture and its data and types are continuously enriched with the development of the product life cycle. In the design stage, the SSC source architecture, design attributes, and design results are defined; in the procurement and manufacturing stage, the SSC architecture is inherited and partially refined, and the corresponding procurement and manufacturing attributes and procurement and manufacturing results are formed; in the civil engineering and installation stage, the SSC architecture is further inherited and partially refined, and the civil engineering and installation attributes and civil engineering and installation results are formed; in the debugging stage, the SSC architecture is inherited and partially refined again, and the debugging attributes and debugging results are formed; in the operation and maintenance stage, the SSC architecture is finally inherited and partially refined, and the operation and maintenance attributes and operation and maintenance results are formed.

[0029] Figure 2 is a schematic block diagram of a nuclear power engineering data architecture according to an embodiment of the present application, such as Figure 2 As shown, if the current nuclear power project is to build a nuclear power plant, it may include the design of the nuclear steam supply system and other systems of the nuclear power plant. When designing the nuclear steam supply system, it can be divided into designing the reactor cooling system and designing the reactor body, wherein the reactor cooling system may include the design of the steam generator, the main pump and other structures, and the reactor body may include the design of the fuel assembly, the pressure vessel and other structures. The material structure (BOM structure) of the fuel assembly may include the upper tube seat, the lower tube seat, the grid, the leaf spring and the screw.

[0030] In some embodiments, step S10 also includes the following steps: S11: obtaining the type of nuclear power project; S12: determining the management method of the nuclear power project based on the type of the nuclear power project; S13: determining the specific stages of the nuclear power project based on the management method; S14: determining the type and style of data of each stage of the nuclear power project based on the specific stage.

[0031] The method provided in the embodiment of the present application determines the management method of the nuclear power project by the type of the nuclear power project, and then determines the specific stages of the nuclear power project based on the management method. This is conducive to improving the efficiency and accuracy of determining the specific stages included in the nuclear power project, thereby ensuring that the type and style of data at each stage of the nuclear power project are determined quickly and accurately.

[0032] In some embodiments, nuclear power projects may include different types of nuclear power projects such as scientific research and engineering.

[0033] In some embodiments, different management methods may be set for different types of nuclear power projects. For example, data management includes version control, approval control, change control, data storage, data distribution, etc. Different types of nuclear power projects may be set with different approval control processes or different data storage methods.

[0034] In some embodiments, step S14 also includes the following steps: S141: determine the specific technical tasks, participating departments and technical deliverables of the specific stage; S142: determine the format and style of the data of the specific stage based on the technical tasks, participating departments and technical deliverables determined in step S141; S143: determine the general principles of the data of each stage based on the format and style of the data of the specific stage; S144: determine the type and style of the data of each stage of the nuclear power project based on the general principles determined in step S143.

[0035] The embodiments of the present application can relatively accurately determine the format and style of the data of a specific stage through the specific technical tasks, participating departments and technical deliverables of the specific stage of the nuclear power project, and then based on the general principles of the data of each stage, the type and style of the data of each stage of the nuclear power project can be determined, thereby ensuring that the data of each stage can be associated and shared with relatively high reliability.

[0036] In some embodiments, for any specific stage of a nuclear power project, specific technical tasks, participating departments, and technical deliverables are set. For example, for the shell R&D stage of the reactor, the technical task of the department involved in the R&D is to determine the function of the shell, and then deliver the R&D results to the downstream design department, and the technical task of the department involved in the design is to design the shape, size, material, structure and other parameters of the shell to achieve the above-mentioned predetermined functions.

[0037] In some embodiments, step S20 may include the following steps: S21: construct a low-code development model based on the type and style of the data determined in step S10; S22: based on the low-code development model, convert the type and style of the data into a callable data format and operation template; S23: based on the data format and operation module, technicians can create data that complies with step S10 at each stage of the nuclear power project to complete the tasks of each stage, thereby associating the newly generated data at each stage to complete the tasks of each stage.

[0038] The method provided in the embodiment of the present application converts the type and style of data into callable data formats and operation templates through the constructed low-code development model, which can lightweight the data at each stage, thereby improving the efficiency of data processing. Then, technical personnel can create data that meets the requirements at each stage of the nuclear power project according to the data format and operation module to ensure the relevance of the data at each stage.

[0039] In some embodiments, in step S23, the following steps are also included: S231: based on the data format and the operation module, the data format and the operation module are published; S232: the technician can obtain the published data format and the operation module at his terminal; S233: after the technician obtains the published data format and the operation module, the technician can create data that complies with step S10 at each stage of the nuclear power project to complete the tasks of each stage, thereby associating the newly generated data at each stage to complete the tasks of each stage.

[0040] The method provided in the embodiment of the present application enables technicians to obtain the published data format and operation module on their terminals, so as to create data that meets the requirements at each stage of the nuclear power project, thereby further improving the relevance of data at each stage of the nuclear power project.

[0041] In some embodiments, in step S231, coding principles, confidentiality of permissions, and control processes for different data are constructed based on the published data format and operation module; and coding principles, confidentiality of permissions, and control processes are published.

[0042] The method provided in the embodiment of the present application can construct encoding principles, authority confidentiality, and control processes for different data based on the published data format and operation module, and publish them, which is conducive to ensuring that data can be associated and shared.

[0043] In some embodiments, the data control process may include an approval process, a change process, a storage process, a distribution process, etc.

[0044] In some embodiments, the data approval process may include: submitting data to the approval port and selecting an approver, and then the relevant approver opens the approval task after receiving the task, reviews and writes approval opinions, and performs quality scoring and other operations. Finally, after the approver completes the approval, the process can be signed and published simultaneously for relevant personnel to review.

[0045] In some embodiments, in the data change process, data changes can be made by filling out a change form. Data change forms can be divided into three levels according to the degree of change, namely major changes, major changes, and general changes. Each change form can be divided into two levels according to the degree of coreness, namely core level or non-core level.

[0046] In some embodiments, the data change form may include a design change request form and a design change notification form.

[0047] In some embodiments, the design change application (DCA) is a change application document submitted by the design department based on business needs, design improvement suggestions, etc., assuming that there are no design errors in the design plan and design documents. In this process, when the change application category is judged to be a large or major change, a design change application form needs to be filled out.

[0048] In some embodiments, a design change notification (DCN) is an application form issued by a design department to revise and improve an effective CFC version of the construction design document based on changes in upstream design input, design optimization, review or modification opinions proposed by the owner, manufacturer, purchaser or construction unit.

[0049] In some embodiments, after the data is changed, the user interface may display the data before and after the change, respectively. For example, the version corresponding to the data before the change may be displayed as A2, and the version corresponding to the data after the change may be displayed as B1.

[0050] In some embodiments, data may also correspond to multiple data states, including but not limited to: in preparation, in process, published, and invalid. After the approval process is completed, the data may be changed to published and stored in the system to ensure data persistence and reliability, while also meeting the needs of fast data access and retrieval.

[0051] In some embodiments, when data acceptance is required, the technician can click the "Acceptance" node in the process to perform the operation selected by the distributor. After the process annotation is completed, the electronic version of the data can be automatically sent to the designated recipient.

[0052] In some embodiments, in step S50, the flow, sharing, and scope of knowledge of the data generated at each stage are determined based on the published coding principles, confidentiality of authority, and control processes to ensure that the data can be accurately used by different departments at the corresponding stages.

[0053] In some embodiments, technical personnel can set different permissions for participants in each stage and department to control the flow, sharing, and scope of knowledge of the data generated at each stage.

[0054] In some embodiments, technicians can edit the user's enabled or disabled status by creating roles to add corresponding permissions, the user's confidentiality level, and the confidentiality level of technical deliverables based on the user's status.

[0055] In some embodiments, the confidentiality control of data rights can be set as follows: all task leaders of the nuclear power project have the authority to view the entire project data, and the viewing of specific task data is controlled by setting different confidentiality levels.

[0056] In some embodiments, the technician can edit the permissions and confidentiality levels of different roles by using the role authorization control displayed in the user interface. For example, the technician can perform the role authorization operation by clicking the control "Role Authorization", and then the function permission points corresponding to all roles in the application will be listed in the form of a tree table in the current user interface. The technician can authorize by checking the box, or close the authorization by unchecking the box.

[0057] In some embodiments, in step S233, different technicians at different stages or different technicians at the same stage can create different data in accordance with step S10 at each stage of the nuclear power project and associate the different data.

[0058] The method provided in the embodiment of the present application can facilitate the association of different data and has high reliability by having different technicians at different stages or different technicians at the same stage create the required data at each stage of a nuclear power project.

[0059] In some embodiments, step S233 may further include the following steps: S2331: define the logical relationship between data generated by different technicians at different stages or different technicians at the same stage; S2332: associate different data according to the logical relationship.

[0060] The embodiments of the present application determine the logical relationship between the data generated by different technicians, and then associate the different data based on the logical relationship. This helps avoid data confusion when the data is associated and shared, thereby ensuring the accuracy of the data used by different departments at each stage.

[0061] In some embodiments, the logical relationship may include data search, data management, or data call, etc.

[0062] In some embodiments, in step S2331, rules for inheritance or transfer of data at different stages are also defined, and different data are associated according to the rules and logical relationships. This is conducive to sharing data at each stage, so as to facilitate technical personnel from different departments at each stage to use data.

[0063] In some embodiments, if the shell of the reactor is designed as a high temperature resistant shell in the conceptual stage, then in the design stage, the high temperature resistant shell needs to be actually converted into a high temperature resistant material to obtain the physical entity of the shell of the reactor.

[0064] In some embodiments, the data of nuclear power projects are associated and shared through the method provided in the embodiments of the present application, so that technical personnel can more intuitively know the upstream and downstream relationships of data at each stage, and can automatically send notifications in the event of data changes, thereby ensuring that information on design changes is delivered to relevant departments in a timely manner. Through the centralized management of data, digital management of the R&D design process can be achieved; through the connection between the R&D design process and SSC, unified centralized management of R&D three-dimensional models, design parameters, design drawings, IED lists, and calculation notes, as well as the opening and sharing of data within the organization of the same nuclear power project, can be achieved. At the same time, the execution process of nuclear power projects can be standardized, and relevant work procedures and systems can be established to improve the operability of the procedures; a collaborative working environment can be established to ensure the accuracy, consistency and integrity of the data, which is conducive to shortening the transformation cycle from R&D to production, and then realizing the transformation from result management to process control, and improving management level and effect.

[0065] Regarding the embodiments of the present application, it should also be noted that, in the absence of conflict, the embodiments of the present application and the features therein can be combined with each other to obtain new embodiments.

[0066] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. The protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A data association sharing method in a nuclear power project, characterized in that: It includes the following steps: S10: defining the type and format of data at each stage of the nuclear power project; S20: Determine the association method of the data in each stage according to the type and style of the data; S30: In each of the stages, the data type and format defined in step S10 are used to generate data applied to the nuclear power project in each stage; S40: according to the association method of step S20, the data generated in step S30 are associated in each stage; S50: Sharing the data associated in step S40 so that different departments can use the data at various stages.

2. The method according to claim 1, characterized in that: In step S10, the following steps are also included: S11: Obtain the type of the nuclear power project; S12: Determine the management method of the nuclear power project according to the type of the nuclear power project; S13: Determine the specific phases of the nuclear power project according to the management measures; S14: Determine the type and format of data at each stage of the nuclear power project according to the specific stage.

3. The method according to claim 2, characterized in that In step S14, the following steps are also included: S141: Determine the specific technical tasks, participating departments and technical deliverables for the specific stage; S142: Determine the format and style of the data at the specific stage according to the technical tasks, participating departments and technical deliverables determined in step S141; S143: Determine the general principle of the data of each stage according to the format and style of the data of the specific stage; S144: According to the general principles determined in step S143, the type and style of data for each stage of the nuclear power project are determined.

4. The method according to claim 1, characterized in that: In step S20, the following steps are also included: S21: Building a low-code development model according to the type and style of the data determined in step S10; S22: According to the low-code development model, convert the type and style of the data into a callable data format and operation template; S23: According to the data format and operation module, the technicians can create data in accordance with step S10 at each stage of the nuclear power project to complete the tasks at each stage, and associate the data newly generated at each stage to complete the tasks at each stage.

5. The method according to claim 4, characterized in that In step S23, the following steps are also included: S231: publishing the data format and the operation module according to the data format and the operation module; S232: The technician can obtain the published data format and operation module on his terminal; S233: After the technician obtains the published data format and operation module, the technician can create data that complies with step S10 at each stage of the nuclear power project to complete the tasks of each stage, and associate the newly generated data at each stage to complete the tasks of each stage.

6. The method according to claim 5, characterized in that In step S231, according to the published data format and operation module, the coding principle, authority confidentiality and control process of different data are constructed; Publish the coding principles, confidentiality of authority, and control processes.

7. The method according to claim 5, characterized in that In step S50, the flow, sharing, and scope of knowledge of the data generated at each stage are determined based on the published coding principles, confidentiality of authority, and control procedures.

8. The method according to claim 5, characterized in that In step S233, different technicians at different stages or different technicians at the same stage can create different data in accordance with step S10 at each stage of the nuclear power project and associate the different data.

9. The method according to claim 8, characterized in that The following steps are also included: S2331: define the logical relationship between data generated by different technicians at different stages or different technicians at the same stage; S2332: Associating the different data according to the logical relationship.

10. The method according to claim 9, characterized in that In step S2331, the rules for inheritance or transfer of data at different stages are also defined, and the different data are associated according to the rules and the logical relationship.

Images