A method and system for managing nuclear power project files

Abstract

The application provides a nuclear power project file management method and system. The nuclear power project file includes at least a license application file and a design file. The nuclear power project file management method includes the following steps: constructing an association list of each sub-structure unit in the design file and the license application file, the association list including at least one design file associated with the license application file; in response to detecting a change event, determining a target sub-structure unit in the license application file affected by the change event according to the association list; determining and executing a modification strategy of the target sub-structure unit, so that the license application file is consistent with the changed design file. The application establishes an association list between chapters of the design file and the license application file. When a change in the design file is detected, the application can automatically locate the specific position affected in the license application file and execute the modification strategy, thereby ensuring the consistency of the content of the license application file and the design file, and improving the accuracy and efficiency of the nuclear power project document management.

Description

Technical Field

[0001] This application relates to the field of nuclear power technology, specifically to a method and system for managing nuclear power project documents. Background Technology

[0002] Nuclear power plant license application documents are the primary documents submitted to the National Nuclear Safety Administration for obtaining construction and fuel loading permits, playing a crucial role in the design and construction of nuclear power projects. On one hand, the license application documents present the overall preliminary design and safety analysis to regulators; on the other hand, after the construction permit for the nuclear power project is issued, the license application documents, as a legally binding nuclear safety commitment, serve as guiding documents that must be followed in subsequent construction drawing design.

[0003] However, due to the large size of the license application documents, the involvement of numerous professional fields, the complexity of the compilation interfaces, and the tight compilation cycle, current technologies primarily rely on manual verification of the consistency between the design documents and the license application documents. In some cases, the manual verification process is even lacking altogether. This results in low efficiency in the compilation of license application documents, numerous errors, and impacts on project progress and the fulfillment of nuclear safety commitments. Summary of the Invention

[0004] The main objective of this application is to propose a method and system for managing nuclear power project documents, aiming to improve the accuracy and efficiency of nuclear power project document management.

[0005] This application provides a method for managing nuclear power project documents, which include at least license application documents and design documents. The method includes the following steps: constructing an association list between the design documents and each substructural unit in the license application documents, the association list including at least one design document associated with the license application documents; in response to detecting a change event, determining the target substructural unit in the license application documents affected by the change event based on the association list; and determining and implementing a modification strategy for the target substructural unit to ensure that the license application documents are consistent with the modified design documents.

[0006] In one embodiment, constructing the association list between the design document and each sub-structural unit in the license application document includes: constructing the association list between the design document and each sub-structural unit in the license application document based on the document structure identifier in the license application document.

[0007] In one embodiment, constructing an association list between the design document and each sub-structural unit in the license application document based on the document structure identifier in the license application document includes: parsing the document structure of the license application document to determine the document structure identifier corresponding to each sub-structural unit in the license application document; binding the file attributes of the design document to one or more of the document structure identifiers, or binding the document structure identifiers to one or more file attributes of the design document to construct an association list between the design document and each sub-structural unit in the license application document; wherein the file attributes are used to uniquely identify the design document.

[0008] In one embodiment, constructing the association list between the design document and each sub-structural unit in the license application document further includes: constructing a first association list between a first sub-structural unit of the license application document and the design document, wherein the first sub-structural unit includes common features of the nuclear power project and the first association list includes design documents related to the first sub-structural unit; constructing a second association list between a second sub-structural unit of the license application document and the design document, wherein the second sub-structural unit includes unique features of the nuclear power project and the second association list includes design documents related to the second sub-structural unit; and obtaining the association list between the design document and each sub-structural unit in the license application document based on the first association list and the second association list.

[0009] In one embodiment, before determining the target substructural unit in the license application document affected by the change event based on the association list, the method further includes: updating the association list based on the change event.

[0010] In one embodiment, updating the association list based on the change event includes: if the change event involves the common characteristics of the nuclear power project, then updating the design documents in the first association list; if the change event involves the unique characteristics of the nuclear power project, then updating the design documents in the second association list.

[0011] In one embodiment, determining the target substructure unit in the license application document affected by the change event based on the association list includes: querying the association list based on the design document in which the change event occurred, obtaining one or more document structure identifiers bound to the design document; and determining the substructure unit corresponding to the obtained document structure identifier as the target substructure unit.

[0012] In one embodiment, the method further includes: generating a processing task based on a determined target substructure unit; and distributing the processing task to the responsible party for the target substructure unit.

[0013] In one embodiment, determining and executing the modification strategy for the target substructural unit to ensure consistency between the license application document and the revised design document includes: determining the modification strategy for the target substructural unit based on the processing status of the license application document and / or the change event; and executing the modification strategy to ensure consistency between the license application document and the revised design document.

[0014] In one embodiment, determining the modification strategy for the target substructure unit based on the processing status of the license application document and / or the change event includes: when the license application document is in the preparation stage, modifying the content of the target substructure unit according to the change event; when the license application document is in the filed stage and the change event affects the commitments and review requirements of the license application document, initiating the nuclear safety design change process; when the license application document is in the filed stage and the change event does not affect the commitments and review requirements of the license application document, recording the inconsistencies caused by the change event as pending items and associating them with the next stage of the license application document; when the license application document is in the filed stage, the change event affects the commitments and review requirements of the license application document, and it is determined based on regulatory review opinions or internal assessments that the change event needs to be withdrawn, initiating the withdrawal process for the change event.

[0015] This application embodiment also provides a management system for nuclear power project documents, the nuclear power project documents including at least license application documents and design documents, the system comprising: a construction module, configured to construct an association list of each sub-structural unit in the design documents and the license application documents, the association list including at least one design document associated with the license application document; a detection module, configured to, in response to the detection of a change event, determine the target sub-structural unit in the license application document affected by the change event according to the association list; and a modification module, configured to determine and execute a modification strategy for the target sub-structural unit to ensure that the license application document is consistent with the modified design document.

[0016] This application provides a method and system for managing nuclear power project documents. The nuclear power project documents include at least license application documents and design documents. The method includes the following steps: constructing an association list between the design documents and each sub-structural unit in the license application documents, the association list including at least one design document associated with the license application document; in response to the detection of a change event, determining the target sub-structural unit in the license application document affected by the change event based on the association list; and determining and implementing a modification strategy for the target sub-structural unit to ensure consistency between the license application document and the revised design document. By establishing an association list between the design documents and the chapters of the license application documents, this application can automatically locate the affected specific location in the license application document and execute a modification strategy when a change in the design document is detected, thereby ensuring the consistency of the content of the license application document and the design document, and improving the accuracy and efficiency of nuclear power project document management. Attached Figure Description

[0017] Figure 1 This is a diagram illustrating the relationship between design activities and license application activities in a nuclear power project.

[0018] Figure 2 This is a diagram illustrating the relationship between design documents and license application documents in a nuclear power project.

[0019] Figure 3 This is a flowchart illustrating the nuclear power project document management method provided in the embodiments of this application.

[0020] Figure 4 This is a schematic diagram illustrating the construction of the association list provided in the embodiments of this application.

[0021] Figure 5 This is a flowchart illustrating the process of determining the modification strategy provided in an embodiment of this application.

[0022] Figure 6 This is a schematic diagram of the structure of the nuclear power project document management system provided in the embodiments of this application.

[0023] Figure 7 This is a schematic diagram of the structure of an embodiment of the electronic device provided in this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0025] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0026] Design activities refer to the technical implementation process in nuclear power plant projects where various professional teams develop, analyze, and verify specific technical solutions for systems, equipment, and layouts, resulting in a series of design documents. These design documents may include preliminary design documents and construction drawings. License application activities refer to the compliance management process of transforming design results into a series of license application documents submitted to the National Nuclear Safety Administration (NNEA) to ensure nuclear power plant safety and compliance. This process involves review, filing, and other regulatory procedures to make these documents legally binding nuclear safety commitments. License application documents are the compliance documents submitted by the nuclear power plant project to the NNEA for construction and fuel loading permits, and may include a Preliminary Safety Analysis Report (PSAR) and a Final Safety Analysis Report (FSAR).

[0027] Figure 1 A diagram illustrating the relationship between design activities and license application activities in a nuclear power project. For example... Figure 1 As shown, nuclear power plant design activities and licensing application documents are illustrated using PSAR as an example. Based on the deliverables of the design activities, they can be divided into the preliminary design phase and the construction drawing design phase. Preliminary design documents are delivered during the preliminary design phase, and construction drawing design documents are delivered during the construction drawing design phase. Based on the execution progress of the design activities, they can be divided into functional baseline, allocation baseline, and release baseline. Specifically, in the preliminary design phase, based on the functional baseline and allocation baseline, the overall / general design of the nuclear power project is subdivided into system design, equipment design, and layout design. Then, the system design, equipment design, and layout design are further subdivided into various disciplines (e.g., discipline A, discipline B, discipline C, discipline D), resulting in different design documents (e.g., document a, document b, document c, document d, document e, etc.) based on the discipline.

[0028] The licensing application process (i.e., licensing activities) proceeds concurrently with the design activities. Specifically, the preliminary design documents generated during the preliminary design phase serve as input data for preparing the licensing application document (such as the Preliminary Design SAR). After the PSAR is completed, the preliminary design documents are used as the basis for a centralized conformity check. Next, the PSAR undergoes review and formalization. Review refers to the official process of submitting the completed PSAR to the National Nuclear Safety Administration for technical review and safety assessment. During the review process, the regulatory agency organizes experts to conduct a comprehensive technical review of the PSAR, covering aspects such as design safety, technical rationality, and compliance. Simultaneously, the design unit needs to answer review questions raised by the regulatory agency and revise and improve the PSAR based on the review comments to obtain regulatory approval. After the PSAR passes review, the final approved version is formally submitted to the National Nuclear Safety Administration for filing and archiving, completing the formalization of the PSAR and forming a binding safety commitment.

[0029] Once the construction drawing design phase begins, if the resulting construction drawing design documents contain design changes compared to the preliminary design documents or PSAR, a design change process needs to be initiated to determine whether the design change involves nuclear safety. If the design change involves nuclear safety, the formal reporting or approval process for the design change should be followed in accordance with regulatory requirements; if it is not related to nuclear safety, it should be processed according to the normal design process.

[0030] Figure 2 This is a diagram illustrating the relationship between design documents and license application documents in a nuclear power project. For example... Figure 2 As shown, the Preliminary Design SAR (PSAR) is used to bridge the gap between preliminary design documents and construction drawings. In the early stages of a project, the preliminary design documents serve as the foundational input for the PSAR, which presents the preliminary design deliverables. The two must be consistent to ensure that the license application submitted to regulatory authorities accurately reflects the preliminary design. Once the PSAR is completed, it undergoes review and filing to solidify its status. When the project enters the construction drawing design phase, the construction drawings must implement the nuclear safety commitments made in the solidified PSAR and incorporate all approved nuclear safety-related design changes. In other words, the PSAR serves two purposes: firstly, it presents the overall preliminary design and safety analysis to regulators as part of the license application; secondly, after the construction permit is issued, it becomes the basis for guiding the construction drawing design and strictly adhering to nuclear safety commitments. Finally, the Final Design SAR (FSAR) is prepared based on the construction drawings, ensuring consistency between the FSAR and the construction drawings.

[0031] In existing technologies, the control of consistency between license application documents and design documents mainly relies on manual compilation of correlation lists, manual identification of the impact of design changes, and manual review. However, due to the wide range of technologies involved in license application documents, their large size, complex compilation interfaces, and the highly tight compilation cycle, traditional manual management methods are insufficient to achieve comprehensive, timely, and accurate consistency control. This results in widespread inconsistencies between design documents and license application documents in projects, seriously affecting the accurate presentation of technical solutions to regulators and the effectiveness of nuclear safety commitment implementation, thereby hindering project approval and construction progress. Therefore, how to meet the needs of mass project construction while ensuring the effective implementation of nuclear safety commitments and PSAR consistency quality control has become an urgent technical challenge to be solved in this field.

[0032] Based on this, embodiments of this application provide a method and system for managing nuclear power project documents, which can improve the accuracy and efficiency of nuclear power project document management.

[0033] The nuclear power project document management method provided in this application can be applied to a terminal, a server, or software running on either a terminal or a server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, etc.; the server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the nuclear power project document management method, but is not limited to the above forms.

[0034] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers (PCs), minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0035] It should be noted that in various specific embodiments of this application, when the documents involved require processing based on data related to the object's identity or characteristics, such as object information, object attribute information, and object rank, the object's permission or consent will be obtained first. Furthermore, the collection, use, and processing of this data will comply with relevant laws, regulations, and standards. In addition, when embodiments of this application require obtaining sensitive personal information of an object, separate permission or consent from the object will be obtained through pop-ups or redirects to confirmation pages. Only after obtaining the object's separate permission or consent will the necessary object-related data for the normal operation of the embodiments of this application be obtained.

[0036] The method for managing nuclear power project documents provided in this application will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0037] To address the aforementioned challenges, this application provides a method for managing nuclear power project documents. Please refer to [link to relevant documentation]. Figure 3 Control methods may include: Step S101: Construct a list of associations between the design documents and the sub-structural units in the license application documents. The list of associations includes at least one design document associated with the license application documents.

[0038] Step S102: In response to the detection of a change event, determine the target substructural unit in the license application document affected by the change event based on the associated list.

[0039] Step S103: Determine and implement the modification strategy for the target substructure unit to ensure that the license application documents are consistent with the revised design documents.

[0040] In step S101 of some embodiments, firstly, the document structure of the license application document is parsed, and each sub-structural unit of the license application document is identified and extracted. A sub-structural unit is an independent part that constitutes the logical structure of the license application document, such as a chapter, clause, or module. Then, in the project document management system, the design documents are associated with each sub-structural unit to form an association list. The association list includes one or more design documents related to the license application document, and the mapping relationship between the design documents and their associated sub-structural units.

[0041] In step S102 of some embodiments, when a change event is detected, such as adjustments to the technical solutions related to the nuclear power project unit model, or design improvement requirements for the nuclear power unit model proposed by a regulatory agency, or a version update or content revision of the design documents, the consistency control process between the design documents and the license application documents is automatically triggered. First, the target design documents that have been changed or are to be changed are determined based on the change event. Next, one or more sub-structural units of the license application documents associated with the target design documents are located in the association list. In this way, the target sub-structural units in the license application documents affected by the change event can be quickly and accurately identified through the association list.

[0042] In step S103 of some embodiments, after identifying the target substructural unit affected by the change event, a modification strategy for the target substructural unit is further determined. A set of modification strategies can be pre-set, including strategies such as modifying the content of the target substructural unit, modifying the content of the license application document in the next stage, and withdrawing the change event. It should be noted that the application document may include a Preliminary Security Analysis Report (PSAR) and a Final Security Analysis Report (FSAR). The PSAR and FSAR are prepared at different stages, with the PSAR being prepared earlier than the FSAR. Next, based on the processing status of the change event and / or the license application document, a corresponding modification strategy is determined from the set of modification strategies. Finally, the determined modification strategy is executed.

[0043] This application constructs an association list of sub-structural units of design documents and license application documents through steps S101 to S103. It can automatically respond to design document change events, locate the affected target sub-structural units based on the association list, and determine and execute the corresponding modification strategies. This realizes automated consistency management of nuclear power project documents, solves the document inconsistency problem caused by the lag and omission of manual management, and improves the accuracy and efficiency of nuclear power project document management.

[0044] In one embodiment, constructing an association list of each sub-structural unit in the design document and the license application document includes: constructing an association list of each sub-structural unit in the design document and the license application document based on the document structure identifier in the license application document.

[0045] Here, the association list includes the document structure identifiers and design documents of the sub-structural units. First, a unique document structure identifier is assigned or recorded for each sub-structural unit in the license application document. The document structure identifier refers to a coding or marking system that uniquely identifies each logical component within the license application document, such as using a hierarchical coding method of "chapter number-subchapter number" (e.g., "3.5.2" represents Chapter 3, Section 5, Item 2) or a unique ID based on the standard document structure. Next, based on the document structure identifiers in the license application document, a mapping relationship is established between the design documents and each sub-structural unit in the license application document, resulting in the association list.

[0046] In practice, the target license application documents (such as the PSAR report) are first structurally parsed to extract their complete document skeleton, identify all sub-structural units with independent technical meaning, and record the corresponding document structure identifier for each unit. Subsequently, in the project document management system, a mapping is established between the file attributes of the design documents (such as file number and version number) and the corresponding document structure identifiers to form an association list. For example, when it is necessary to establish an association between design document X and the PSAR report, the specific chapter of design document X in the PSAR is first identified, and then the design document X is bound to the identifier of that specific chapter in the PSAR (such as "Chapter 6.3.1"). In this way, a fine-grained association between design documents and license application documents is established. The structured identifiers ensure the consistency and maintainability of the association, effectively solving the problems of unclear associations and difficult maintenance under traditional manual management methods.

[0047] In one embodiment, based on the document structure identifier in the license application document, an association list between the design document and each sub-structural unit in the license application document is constructed, including: parsing the document structure of the license application document to determine the document structure identifier corresponding to each sub-structural unit in the license application document; binding the file attributes of the design document to one or more document structure identifiers, or binding the document structure identifiers to the file attributes of one or more design documents, to construct an association list between the design document and each sub-structural unit in the license application document; wherein, the file attributes are used to uniquely identify the design document.

[0048] Here, the document structure of the license application document is parsed to determine the document structure identifier corresponding to each sub-structural unit in the license application document. Then, the file attributes of the design document are bound to one or more document structure identifiers, or the document structure identifiers are bound to the file attributes of one or more design documents, to establish a mapping relationship between the design document and each sub-structural unit in the license application document. The file attributes here are used to uniquely identify the design document and can be information such as the design document number, name, version number, or a combination thereof.

[0049] In practice, the hierarchical structure of the license application documents is first identified, and all sub-structural units are extracted. Simultaneously, the structured identifier corresponding to each sub-structural unit is obtained, such as the identifier "4.3.2" formed using a three-level coding system of "chapter number-sub-chapter number-clause number". Next, the association between design documents and document structure identifiers is established in the document management platform. This is achieved through two optional methods: one is forward association, binding the attribute set of the design document (including unique identifiers such as file code, version number, and file name) to one or more document structure identifiers; the other is reverse indexing, using the document structure identifier as the index key to associate the attribute sets of multiple related design documents. For example, a bidirectional association is established between the file code of design document Y and the "7.2.3" chapter identifier in the PSAR report, and this chapter identifier can also be associated with multiple design documents such as design document Z. In this way, a many-to-many mapping relationship between design documents and license application documents is achieved, ensuring the complete traceability of technical evidence and providing a complete topological data foundation for subsequent change impact analysis.

[0050] In one embodiment, constructing the association list of each sub-structural unit in the design documents and the license application documents further includes: constructing a first association list between a first sub-structural unit in the license application documents and the design documents, wherein the first sub-structural unit includes common features of the nuclear power project and the first association list includes design documents related to the first sub-structural unit; constructing a second association list between a second sub-structural unit in the license application documents and the design documents, wherein the second sub-structural unit includes unique features of the nuclear power project and the second association list includes design documents related to the second sub-structural unit; and obtaining the association list of each sub-structural unit in the design documents and the license application documents based on the first and second association lists.

[0051] Here, the consistency association list between PSAR and design documents can be managed using a "standardized association list (first association list) + differentiated association list (second association list)" approach. The standardized association list mainly includes design documents related to the nuclear power project model that are less affected by site differences, procurement, and construction. The differentiated association list mainly includes design documents outside the standardized association list that are more significantly affected by site differences and owner requirements. Both the standardized and differentiated association lists need to be dynamically maintained as the project progresses. For example, the standardized association list refers to common design content across multiple projects that affects the model's technical characteristics, such as unit main parameters and system configuration, including overall schemes, overall requirements, main parameters, general design principles, major design differences, abbreviations, safety system functional requirements and operating modes, system and equipment parameters, etc. The differentiated association list refers to design content significantly affected by site differences and owner requirements, such as site location, population distribution, nearby industrial / transportation / military facilities, site information such as earthquake, meteorological / hydrological / tsunami information, design optimization items that do not affect the model's technical characteristics, and owner-specific requirements, etc. Figure 4 As shown, the PSAR (Personal Reference Registry) association list for nuclear power projects adopts a hierarchical architecture, consisting of a standardized PSAR association document list (first association list) and a project-specific PSAR association document list (second association list). First, a standardized association list (first association list) is established based on the general design documents for nuclear power models. Then, a differentiated association list (second association list) is established based on the project's differentiated design documents. In actual project applications, the standardized list (first association list) is used as a base template, and the project-specific differentiated list (first association list) is overlaid as supplementary content to generate and continuously and dynamically maintain a project-specific association list. This ensures both the standardization of model design and the completeness of the project's specific requirements.

[0052] In one embodiment, the method for managing nuclear power project documents before determining the target substructure unit affected by the change event in the license application document based on the association list further includes: updating the association list based on the change event.

[0053] Here, the related list is updated according to the change event, including: if the change event involves the common characteristics of the nuclear power project, the design documents in the first related list are updated; if the change event involves the unique characteristics of the nuclear power project, the design documents in the second related list are updated.

[0054] Here, when a design document change event is detected, the content attributes of the change event are first automatically identified. If the change involves common characteristics of the nuclear power project, the corresponding design document version or content in the first association list is updated. If the change involves unique characteristics of the nuclear power project, the relevant design document records in the second association list are updated. For example, when design document Q is revised due to a model upgrade, the version information of design document Q in the first association list is automatically updated. However, when design document W needs to be adjusted due to changes in local hydrological conditions, only design document W in the second association list is updated. In this way, dynamic maintenance of the association list is achieved, effectively maintaining its timeliness and accuracy.

[0055] In one embodiment, determining the target substructure unit affected by the change event in the license application document based on the association list includes: querying the association list based on the design document where the change event occurred, obtaining one or more document structure identifiers bound to the design document; and determining the substructure unit corresponding to the obtained document structure identifier as the target substructure unit.

[0056] Here, when a design document change event is detected, the constructed association list is used as the query basis, and the unique identifier of the changed design document is used as the search condition. All document structure identifiers that have a mapping relationship with the design document are automatically retrieved from the association list. Each obtained document structure identifier represents a sub-structural unit in the license application document that has a technical relationship with the design document. Subsequently, the obtained document structure identifiers are mapped to the corresponding sub-structural units and identified as target sub-structural units. For example, when design document G is updated, the association list is queried to obtain the two document structure identifiers "Chapter 5.3.1" and "Chapter 5.3.2" bound to it, and then the corresponding Chapters 5.3.1 and 5.3.2 in PSAR are identified as target sub-structural units. In this way, by establishing a hierarchical mapping relationship of "design document - document structure identifier - sub-structural unit" in the association list, the efficiency and accuracy of nuclear power project document consistency management are improved.

[0057] In one embodiment, the method for managing nuclear power project documents further includes: generating processing tasks based on identified target substructure units; and distributing the processing tasks to the responsible parties for the target substructure units.

[0058] Here, after identifying the target substructural unit affected by the change event, a processing task is automatically generated. This task may include the changed design document version, the associated target substructural unit identifier, a summary of the change, and a preset processing timeframe. Subsequently, the processing task can be assigned to the technical party responsible for the corresponding target substructural unit through the document management system. This achieves automated integration of problem identification and task assignment, while establishing an individual-level work responsibility traceability mechanism, improving the response speed and processing quality of consistency control for nuclear power project documents.

[0059] In one embodiment, determining and implementing a modification strategy for the target substructural unit to ensure consistency between the license application document and the revised design document includes: determining the modification strategy for the target substructural unit based on the processing status and / or change events of the license application document; and implementing the modification strategy to ensure consistency between the license application document and the revised design document.

[0060] Here, on the one hand, the specific content of the change event can be analyzed to determine the modification strategy. For example, different modification strategies can be formulated for different release versions of design documents (initial version and upgraded version). It should be noted that the difference between the initial version and the upgraded version is that the initial version is created from scratch, and it is only necessary to ensure the consistency of the design document with the PSAR. The upgraded version involves changes in the content of the design document, and it is necessary to first assess whether the changed parts affect the PSAR, not all design changes will affect the PSAR. Only if the PSAR is affected, a consistency judgment and processing are carried out. On the other hand, the modification strategy can also be determined based on the processing status of the license application documents, such as in preparation, under review, or already filed. Furthermore, the modification strategy can also be determined jointly based on the change event and the processing status of the license application documents. Modification strategies include, but are not limited to, modifying the content of the target substructural unit, modifying the content of the license application documents in the next stage, and withdrawing the change event. After the modification strategy is determined, by implementing the modification strategy, the efficiency of consistency management of nuclear power project documents can be improved while ensuring nuclear safety commitments.

[0061] In one implementation, the modification strategy for the target substructural unit is determined based on the processing status of the license application document and / or change events. This includes: when the license application document is in the preparation stage, modifying the content of the target substructural unit according to the change events; when the license application document is in the filed stage and the change events affect the commitments and review requirements of the license application document, initiating the nuclear safety design change process to the regulatory authority; when the license application document is in the filed stage and the change events do not affect the commitments and review requirements of the license application document, recording the inconsistencies caused by the change events as pending items and linking them to the next stage of the license application document; when the license application document is in the filed stage, the change events affect the commitments and review requirements of the license application document, and it is determined based on regulatory review opinions or internal assessments that the change events need to be withdrawn. For example, if the regulatory authority does not agree to the implementation, or the designer believes, after its own assessment, that the change plan is problematic and not recommended for implementation, and the change process needs to be withdrawn, then the withdrawal process for the change events is initiated.

[0062] like Figure 5 As shown, this embodiment provides a complete process for constructing and controlling the consistency of the PSAR associated document list. First, the PSAR management document list is constructed and dynamically managed, using a combination of a standardized associated list and a differentiated list. Both the standardized and differentiated associated lists are directly related to PSAR chapters. The standardized associated list includes standardized PSAR associated design documents based on common characteristics such as model standard design, while the differentiated associated list includes newly added PSAR-related design documents based on design optimizations for this project or owner requirements.

[0063] When the associated list is published for the first time, a pending task is automatically pushed to the PSAR writer. First, it checks whether the PSAR has been filed and whether it is consistent with the revised design documents. If the PSAR has not been filed and the two are inconsistent, the PSAR content can be modified to ensure consistency with the revised design documents. After modification, the writer must confirm it again.

[0064] If the PSAR has been reported but the two are inconsistent, they can be handled separately in three scenarios. First, if the modification requires changing the nuclear safety commitment of the PSAR, the nuclear safety-related design change processing flow is triggered, and the PSAR writer fills in the change order number. If the designer fails to effectively identify the nuclear safety-related design change, the PSAR writer can use this as a fallback to identify it and remind the design document manager to initiate a change report or review. Second, if the modification does not require changing the nuclear safety commitment of the PSAR but requires modifying the PSAR description, the modification content is summarized, and then modified during the FSAR development phase, with the PSAR writer filling in the modification content. Because FSAR development starts late, to avoid the pending task remaining unclosed for an extended period, select "FSAR Phase Processing," summarize the modification content, and then close the pending task. Simultaneously, the SAR compilation platform will record the required modifications according to the sub-processes, automatically loading them when FSAR development begins, reminding the FSAR writer to implement them. In the third scenario, if the modifications fail internal evaluation or are disagreed with by the regulatory body (e.g., the evaluation maintains the original description, or the regulatory body has explicitly disagreed during other project review processes), the modifications to the design documents shall be withdrawn. The person responsible for the design documents shall complete the document processing, and the PSAR writer shall confirm. After the person responsible for the design documents completes the withdrawal process or the document is upgraded and confirmed by the SAR writer, the "Submit" task shall be closed. The document management system shall check whether the withdrawal operation has been performed or whether new document version information has been added to prove that the "Withdrawal of Design Document Modifications" has been executed.

[0065] If the PSAR has been reported and both are consistent, or if the PSAR has not been reported but both are consistent, then there is no need to modify the PSAR; simply close the pending task.

[0066] When the associated list is upgraded, the pending tasks are automatically pushed to the PSAR writer. If the modified content affects the PSAR, the processing logic is the same as in the first version. If the modified content does not affect the PSAR, the pending tasks are closed directly.

[0067] Thus, this application's embodiments take measures from the design source, formulating corresponding modification strategies to address the consistency management issues of documents for different nuclear power projects. This ensures the consistency between the PSAR and the design documents, guaranteeing that the PSAR accurately reflects the preliminary design results while ensuring that the construction drawing design documents effectively implement nuclear safety commitments. Furthermore, the modification strategies are traceable and verifiable, forming a complete control loop.

[0068] This application provides a method for managing nuclear power project documents, which include at least license application documents and design documents. The method comprises the following steps: constructing an association list between the design documents and each sub-structural unit in the license application documents, the association list including at least one design document associated with the license application document; in response to a detected change event, determining the target sub-structural unit in the license application document affected by the change event based on the association list; and determining and executing a modification strategy for the target sub-structural unit to ensure consistency between the license application document and the revised design document. This application, by establishing an association list between the design documents and the chapters of the license application documents, can automatically locate the affected specific position in the license application document and execute a modification strategy when a change in the design document is detected, thereby ensuring consistency between the content of the license application document and the design document and improving the accuracy and efficiency of nuclear power project document management.

[0069] Please see Figure 6 This application also provides a nuclear power project document management system 30, including a construction module 301, a detection module 302, and a modification module 303.

[0070] Among them, the construction module 301 is used to construct an association list of each sub-structural unit in the design documents and the license application documents, and the association list includes at least one design document associated with the license application documents; Detection module 302 is used to determine the target substructure unit affected by the change event in the license application document based on the associated list in response to the detection of a change event; Modification module 303 is used to determine and execute the modification strategy for the target substructure unit to ensure that the license application documents are consistent with the revised design documents.

[0071] In one embodiment, constructing an association list of each sub-structural unit in the design document and the license application document includes: constructing an association list of each sub-structural unit in the design document and the license application document based on the document structure identifier in the license application document.

[0072] In one embodiment, based on the document structure identifier in the license application document, an association list between the design document and each sub-structural unit in the license application document is constructed, including: parsing the document structure of the license application document to determine the document structure identifier corresponding to each sub-structural unit in the license application document; binding the file attributes of the design document to one or more document structure identifiers, or binding the document structure identifiers to the file attributes of one or more design documents, to construct an association list between the design document and each sub-structural unit in the license application document; wherein, the file attributes are used to uniquely identify the design document.

[0073] In one embodiment, constructing the association list of each sub-structural unit in the design documents and the license application documents further includes: constructing a first association list between a first sub-structural unit in the license application documents and the design documents, wherein the first sub-structural unit includes common features of the nuclear power project and the first association list includes design documents related to the first sub-structural unit; constructing a second association list between a second sub-structural unit in the license application documents and the design documents, wherein the second sub-structural unit includes unique features of the nuclear power project and the second association list includes design documents related to the second sub-structural unit; and obtaining the association list of each sub-structural unit in the design documents and the license application documents based on the first and second association lists.

[0074] In one embodiment, before determining the target substructure unit affected by the change event in the license application document based on the association list, the detection module 302 is further configured to: update the association list based on the change event.

[0075] In one embodiment, updating the association list based on the change event includes: if the change event involves the common characteristics of the nuclear power project, then updating the design documents in the first association list; if the change event involves the unique characteristics of the nuclear power project, then updating the design documents in the second association list.

[0076] In one embodiment, determining the target substructure unit affected by the change event in the license application document based on the association list includes: querying the association list based on the design document where the change event occurred, obtaining one or more document structure identifiers bound to the design document; and determining the substructure unit corresponding to the obtained document structure identifier as the target substructure unit.

[0077] In one embodiment, the modification module 303 is further configured to: generate processing tasks based on the determined target substructure unit; and distribute the processing tasks to the responsible party for the target substructure unit.

[0078] In one embodiment, determining and implementing a modification strategy for the target substructural unit to ensure consistency between the license application document and the revised design document includes: determining the modification strategy for the target substructural unit based on the processing status and / or change events of the license application document; and implementing the modification strategy to ensure consistency between the license application document and the revised design document.

[0079] In one embodiment, determining the modification strategy for the target substructure unit based on the processing status of the license application document and / or change events includes: when the license application document is in the preparation stage, modifying the content of the target substructure unit according to the change event; when the license application document is in the filed stage and the change event affects the commitments and review requirements of the license application document, initiating the nuclear safety design change process; when the license application document is in the filed stage and the change event does not affect the commitments and review requirements of the license application document, recording the inconsistencies caused by the change event as pending items and associating them with the next stage of the license application document; when the license application document is in the filed stage, the change event affects the commitments and review requirements of the license application document, and it is determined that the change event needs to be withdrawn based on regulatory review opinions or internal assessments, initiating the withdrawal process for the change event.

[0080] The nuclear power project document management system provided in this application embodiment can implement all the steps of the above-described nuclear power project document management method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0081] Optionally, embodiments of this application also provide an electronic device, including a processor and a memory. The memory stores a program or instructions that can run on the processor. When the program or instructions are executed by the processor, they implement the various steps of the above-described nuclear power project document management method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here. It should be noted that the electronic device in the embodiments of this application includes the above-described mobile electronic device and non-mobile electronic device.

[0082] Figure 7 To illustrate the hardware structure of the electronic device according to the embodiments of this application, the electronic device includes: The processor 601 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. The memory 602 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 602 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 602 and is called and executed by the processor 601 using the nuclear power project file management method of the embodiments of this application. The input / output interface 603 is used to implement information input and output; The communication interface 604 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 605 transmits information between various components of the device (e.g., processor 601, memory 602, input / output interface 603, and communication interface 604); The processor 601, memory 602, input / output interface 603, and communication interface 604 are connected to each other within the device via bus 605.

[0083] The electronic device provided in this application embodiment can implement all the steps of the above-described nuclear power project document management method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0084] This application also provides a computer-readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various steps of the above-described nuclear power project document management method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0085] The processor is the processor in the electronic device described in the above embodiments. The computer-readable storage medium includes computer-readable storage media such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0086] This application also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various steps of the above-described nuclear power project document management method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0087] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0088] This application provides a computer program product stored in a storage medium. The program product is executed by at least one processor to implement the various steps of the above-described nuclear power project document management method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0089] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0090] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0091] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for managing nuclear power project documents, characterized in that, The nuclear power project documents include at least license application documents and design documents, and the method includes the following steps: Construct an association list between the design documents and each sub-structural unit in the license application documents, the association list including at least one of the design documents associated with the license application documents; In response to the detection of a change event, the target substructural unit in the license application document affected by the change event is determined according to the associated list; Determine and implement the modification strategy for the target substructure unit to ensure that the license application documents are consistent with the revised design documents.

2. The method for managing nuclear power project documents according to claim 1, characterized in that, The process of constructing the association list of each sub-structural unit in the design document and the license application document includes: Based on the document structure identifiers in the license application document, construct a list of associations between the design document and each sub-structural unit in the license application document.

3. The method for managing nuclear power project documents according to claim 2, characterized in that, The step of constructing an association list between the design document and each sub-structural unit in the license application document based on the document structure identifier in the license application document includes: Parse the document structure of the license application document to determine the document structure identifier corresponding to each sub-structural unit in the license application document; The file attributes of the design file are bound to one or more document structure identifiers, or the document structure identifiers are bound to one or more file attributes of the design file to construct an association list between the design file and each sub-structural unit in the license application file; wherein the file attributes are used to uniquely identify the design file.

4. The method for managing nuclear power project documents according to claim 1, characterized in that, The process of constructing the association list of each sub-structural unit in the design document and the license application document also includes: Construct a first association list between the first sub-structural unit of the license application document and the design document, wherein the first sub-structural unit includes the common feature part of the nuclear power project, and the first association list includes the design documents related to the first sub-structural unit; Construct a second association list between the second sub-structural unit of the license application document and the design document, wherein the second sub-structural unit includes the unique features of the nuclear power project, and the second association list includes the design documents related to the second sub-structural unit; Based on the first association list and the second association list, an association list is obtained between the design document and each sub-structural unit in the license application document.

5. The method for managing nuclear power project documents according to claim 4, characterized in that, Before determining the target substructural unit in the license application document affected by the change event based on the association list, the method further includes: Update the associated list based on the change event.

6. The method for managing nuclear power project documents according to claim 5, characterized in that, The step of updating the associated list based on the change event includes: If the change event involves a common feature of the nuclear power project, then update the design documents in the first associated list; If the change event involves a unique characteristic of the nuclear power project, then the design documents in the second associated list are updated.

7. The method for managing nuclear power project documents according to claim 4, characterized in that, The step of determining the target sub-structural unit in the license application document affected by the change event based on the association list includes: Based on the design document where the change event occurred, query the associated list to obtain one or more document structure identifiers bound to the design document; The substructure unit corresponding to the obtained document structure identifier is determined as the target substructure unit.

8. The method for managing nuclear power project documents according to claim 7, characterized in that, The method further includes: Based on the defined target substructure units, processing tasks are generated; The processing task is distributed to the responsible party for the target substructure unit.

9. The method for managing nuclear power project documents according to claim 4, characterized in that, The method for determining and implementing the modification strategy for the target substructure unit to ensure consistency between the license application document and the revised design document includes: The modification strategy for the target substructure unit is determined based on the processing status of the license application documents and / or the change events. Implement the modification strategy to ensure that the license application documents are consistent with the revised design documents.

10. The method for managing nuclear power project documents according to claim 9, characterized in that, The method for determining the modification strategy of the target substructure unit based on the processing status of the license application document and / or the change event includes: When the license application document is in the preparation stage, the content of the target substructure unit is modified according to the change event; When the license application documents are in the filed status and the change event affects the commitments and review requirements of the license application documents, the nuclear safety design change process is initiated. When the license application document is in the filed status and the change event does not affect the commitment and review requirements of the license application document, the inconsistency caused by the change event is recorded as a pending item and associated with the license application document in the next stage; When the license application document is in the filed status, the change event affects the commitment and review requirements of the license application document, and it is determined based on regulatory review opinions or internal assessment that the change event needs to be withdrawn, the withdrawal process for the change event is initiated.

11. A management system for nuclear power project documents, characterized in that, The nuclear power project documents include at least license application documents and design documents, and the system includes: A construction module is used to construct an association list between the design documents and each sub-structural unit in the license application documents, the association list including at least one of the design documents associated with the license application documents; The detection module is used to determine the target substructure unit in the license application document affected by the change event based on the associated list in response to the detection of a change event; The modification module is used to determine and execute the modification strategy of the target substructure unit to ensure that the license application document is consistent with the modified design document.

Images