I&C requirements and configuration management JSC RASU V. Rogov Moscow 06.2017

z z z z z z z Introduction. Terms z z configuration management the process of identifying and documenting the characteristics of a facility’s structures, systems and components (including computer systems and software), and of ensuring that changes to these characteristics are properly developed, assessed, approved, issued, implemented, verified, recorded and incorporated into the facility documentation [IAEA-TECDOC-1335]. requirements management activities that ensure requirements are identified, documented, maintained, communicated and traced throughout the life cycle of a system, product, or service [ISO/IEC 29148]. z z z z z z z z z z z z z

I&C lifecycle and roles of CM and RM management

CM and RM relations Configuration management Requirements management As configuration item Configuration Identification Requirements analysis Configuration Status Accounting Requirements identification Change Control Requirements development Requirements change management Assessments, Checks and Audits Requirements tracing Requirements V&V Requirements approval Change request

Documentation management CMS and RMS relations References Requirements management system Configuration management system Design process For approval After approval Documentation management system

Why do we need RM? IAEA-TECDOC-1335 – Configuration management in nuclear power plants (Jan. 2003) IEEE 828-2005 – IEEE Standard for Software Configuration Management Plans (2005) IEEE 1024-1987 Guide to Software Configuration Management TR-103586-R1 – EPRI – Guidelines for Optimizing the Engineering Change Process for Nuclear Power Plants (October 1998) ANSI/NIRMA CM 1.0 - Guidelines for Configuration Management for Nuclear Facilities (2007)

Configuration Identification Configuration Status Accounting CM process Configuration Identification Identification criteria and scope Elements Configuration baselines Change Control Change criteria Change control procedure Revisions control Assessments, Checks and Audits Assessments Qualification evaluation Phisical and functional audits Configuration Status Accounting Product records Inspection records Status modification records Status report

Physical configuration Facility configuration information Scope of CM for I&C Design requirements Contract requirements Requirements License requirements Environmental requirements Technical requirements CD Physical configuration Facility configuration information BD Schedule Change reports QA documentation DD DB actuators DB signals DB Cabinets V&V documentation Accompanying documentation License documentation Operational documentation

Identification of I&C configuration items Product properties Supporting properties I&C Systems/components Documents (including requirements) Functions (schemes, system software, video frames) Test equipment (eq. for tests, metrology and qualification) Interfaces (including cables) Application software (databases/files) Set of parameters

Configuration baselines A specification or product that has been formally reviewed and agreed upon, that there-after serves as the basis for further development, and that can be changed only through formal change control procedures. [IEEE Std 729]

Change request (workflow)

Why do we need RM? 1) Ensuring control over the implementation of the requirements of contracts concluded between the Customer and the designer, the applicable rules and regulations in the development of I&C design documents. 2) Ensuring conformity of the created product to the requirements of the Customer. 3) Distribution of responsibilities between project participants. 4) Estimation of resources, timing and cost in the early stages of the project. 5) Improving the quality of decisions. 6) Evaluation of project risks during the development and analysis of requirements.

RM process RM Requirements identification Requirements approval Requirements definition RM Requirements change management Requirements identification Requirements V&V

Requirements classification Classification approach is clarified for I&C (based on ISO 15288, ISO 9126-93, ISO 28195-89, ISO 25010, ISO 29148-2011, FURPS, BABOK, SWEBOK, )

RASU approach for requirements management

CM and RM in Design process Requirements Configuration items Inputs Design document Requirements Configuration items Current document Detailing Requirements Configuration items Relations Outputs V&V Requirements verification CI verification

CM and RM tools main purpose Managing the Product’s Configuration Control and deploy the product’s configuration throughout its lifecycle Working With Partners Work quickly and efficiently with partners while maintaining data security Structuring a Reliable, Flexible Process Create a reliable, flexible change management process for all users Coordinating Changes Across Engineering and Manufacturing Synchronize engineering and manufacturing to be faster, more cost-effective Managing Change Across Disciplines Manage and control change of my product data so it can be leveraged by the entire enterprise © 2010 PTC

SmartPlant Foundation RASU CM approaches SmartPlant Foundation DB SmartPlant Instrumentation CI management Systems (PBS) Systems Workflow SW and HW User alerts SW\HW Setting permissions Documents SmartPlant reports Reports(equipment lists, wiring diagrams, cable journals, specifications) Project documents External documents Users

RASU RMS approach for requirements development Main features Creating and changing requirements in MS Office Changing attributes in RMS DB Synchronizing of RMS DB and MS Office document by saving document. Requirements classification in RMS DB Convert (making relations between requirement into the document) by MS office Add-in Requirements development in original format of the document

RASU RMS. Main functions Requirements identification Requirements structuring Requirements development RMS Requirements classification Requirements tracing Requirements approval

CM and RM application for NPP projects 1. NPP «Kursk» unit 1,2 2. NPP «Hanhikivi-1» 3. NPP «PAKS-2», units 5,6 4. NPP «Ruppur», units1,2 5. NPP «Akkuyu», units1-4 6. NPP «El Dabaa»

Thank you for your attention! Victor Rogov www.rasu.ru

Just reflect Can't stop, too busy ! Too busy to improve?