DOCSLIB.ORG

Implementing PLM-Based Workflow for Configuration Management (CM) and Nuclear Knowledge Management (NKM) in the Nuclear Power Industry

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Implementing PLM-Based Workflow for Configuration Management (CM) and Nuclear Knowledge Management (NKM) in the Nuclear Power Industry Implementing PLM-based Workflow for Configuration Management (CM) and Nuclear Knowledge Management (NKM) in the Nuclear Power Industry Prof. Dr. Yanko Yanev Nuclear Knowledge Management Institute Kent Freeland, P.E. WorleyParsons Nuclear Services Implementing PLM-based Workflow for Configuration Management (CM) and Nuclear Knowledge Management (NKM) in the Nuclear Power Industry The theory and application of PLM methods to achieve better Configuration Management at Nuclear Power Plants (NPP’s), then integrating Knowledge Management into the PLM infrastructure to “fill in” the latent information and data so often lost. Nuclear Power has only started to embrace the concept of PLM to manage events, processes, workflow, design changes, requirements, and knowledge systems, as part of the implementation for a CM program. Implementing PLM-based Workflow for Configuration Management (CM) and Nuclear Knowledge Management (NKM) in the Nuclear Power Industry CM Information Systems (CMIS), Nuclear Knowledge Management (NKM), and other NPP work control and MRO/ERP systems are major sources of CM data, but currently are not always PLM-oriented, and anyway cannot enforce plant configuration alone. PLM can be utilized to reduce unsynchronized plant CM design and “slipstreaming” in installation events, as well as compliance and regulator requirements management. With the addition of the Nuclear Knowledge Engine, these processes may be enriched and enhanced, while laying the groundwork for systematic information turnover, process refinement and human resource accession betterment Implementing PLM-based Workflow for Configuration Management (CM) in the Nuclear Power Industry Overview of CM and Design Basis in Nuclear Power Plants (NPP’s) NPP configuration management and business/work control systems as a principal source of data for PLM. How PLM ensures NPP CM by the management of events, process, workflow, design changes, requirements. Applying PLM and SE across subcontractors, vendors and off-site fabrication during construction for CM. Selection of software to support implementation of PLM-based NPP Configuration Management. Overview of CM and Design Basis in Nuclear Power Plants (NPP’s) Configuration Management ensures that the design basis for any NPP plant system or component is satisfied and maintained over plant life, as installed in the plant, and as reflected in documents. Three basic management tools are used for this process. PLM controls for typical Design Basis Lifecycle The Nuclear Industry is just starting to understand the purpose of PLM, as an Integrated Management and Change Management tool for Configuration Management. Overall, nuclear power operators are becoming more aware of “lifecycle” in the design, building , operation and decommissioning of NPP’s. Baseline Plant and Engineering Design New Plant Baseline Basis Configuration Engineering Design Revise Drawings and Change Documents Procurement Install and Engineering and Implement through Component Work Management Evaluation NPP configuration management and business/work control systems as a principal source of data for PLM. Process example of no PLM Example While repairing a component in the plant, workers discover a part listed in the BOM for the equipment will not fit properly. Work cannot be completed until this problem is solved. Repository Data-Based Solution Contact Warehouse manually for part. Warehouse goes to Materials Manager and Procurement engineering by e-mail for non- conformance or variance. Procurement identifies new part, calls warehouse to issue replacement part. MRO must remember to update Material Request, and to update closed Work Order. Data Update forms must be filled out to update MRO Bill of Materials, Equipment List, Catalog Stock Code and QC. The Worker must create an ECR for Design Engineering to review design, update design drawings, documents and BOM. Fill out Data Update Requests (DUR) to put new data and link BOM to Equipment, Catalog and Approved Model List (AML) for the equipment. Data entry enters data by hand into MRO system. Process example using PLM Example While repairing a component in the plant, workers discover a part listed in the BOM for the equipment will not fit properly. Work cannot be completed until this problem is solved. PLM Solution The part misfit is entered in the MRO Client. Immediately the PLM process sends Lifecycle and RM messages to the warehouse, MRO Material Request, procurement engineering and design engineering for the part discrepancy. When approved, PLM automatically adds the Part Number to the Bill of Material. Procurement sees an RM notice from PLM for the BOM for equipment number, Purchase Order, Make/Model and Part Number. Design engineering and procurement can either issue a Non-Conformance or Variance. Procurement Engineering generates ROP to Purchasing to buy, or warehouse issues the new part on the MR and the work is completed. No need to note the part discrepancy on the Closed Work Order, PLM already knows. PLM record is updated and included in Documents. PLM documents the transaction and the data in the system. CAE data feeds back to CADD system. PLM-Based Knowledge System for Configuration Management How PLM ensures NPP CM by the management of events, process, workflow, design changes, requirements while capturing data sourced from Knowledge-based activities. PLM-Based Knowledge System for Configuration Management How PLM ensures NPP CM by the management of events, process, workflow, design changes, requirements while capturing data sourced from Knowledge-based activities. Selection of software to support implementation of PLM-based NPP Configuration Management. Most nuclear power facilities select software according to design engineering purposes, with CM functionality perceived as being more important for operation. CM, however, must be considered from the very first day an NPP is even considered. The concepts of process controls, integrated management and PLM for CM and SE comes in a too-distant third-place. This is mainly due to lack of understanding and experience with PLM and PLCS concepts and processes. Traditional 3rd/4th Generation RDBMS Architecture LEGACY DATA SOURCES FIXED RELATIONAL (RDBMS) DATA REPOSITORY FIXED RELATIONAL (RDBMS) DATA REPOSITORY Table Keys and RDBMS Cardinality Controls PROGRAMS AND LEGACY CODE PROGRAMS AND LEGACY CODE PROCESS Manual or e-mail-based Collaboration and CM processes Plant Lifecycle Management (PLM) Architecture XML DATA REPOSITORY XML DATA REPOSITORY XML Data Messaging and Linking Data PLM & CONFIGURATION INFRASTRUCTURE PLM & CONFIGURATION INFRASTRUCTURE PLM Functions Collaboration & Document Supplier Enterprise Lifecycle Visualization Configuration Management Relationship Knowledge Client Interaction and Business Rules IDE PROCESS MODELING IDE PROCESS MODELING Typical NPP Business Processes NPP ENGINEERING NPP EQUIPMENT & NPP ENGINEERING CATALOG & WORK NPP EQUIPMENT & DOCUMENT CHANGE CATALOG & WORK BUSINESS BOM CONTROLDOCUMENT CONTROLCHANGE MATERIALS MANAGEMENT BUSINESSRULES BOM CONTROL CONTROL MATERIALS MANAGEMENT RULES NPP Configuration Management Information Systems Selecting Software for PLM For those NPP’s purchasing software, these are the leading Commercial NPP CM Software packages (by NPP market share and market trend). The red arrow indicates the general trend of growth (or shrinkage) in the product’s market share. None of these Solutions are PLM enabled. IntergraphOthers SPO ABB Ventyx PASSPORT (65%) SAP MRO/MAXIMO V5.0 (20%) MPRO IFS (5%) MPAC MPAC (4%) IFS MPRO/CHAMPS (<2%) SAP (<2%) Maximo INTERGRAPH SPO (<2%) Passport Passport, MPRO and PIMS are specifically Nuclear products. Maximo and IFS have nuclear versions under development Information Technologies for PLM-enabled Nuclear CM, KM and SE Siemens Teamcenter Nuclear ARCHIMED NXT Archimed NXT Information Technologies for PLM-enabled Nuclear CM, KM and SE Applying PLM and System Engineering across subcontractors, vendors and off-site fabrication during construction for CM. Vendor Access to PLM System Vendor access to the PLM system may be permitted through Transaction (“XA”)-based or EDI (Electronic Data Interchange) methods. EDI offers many improvements over XA for realtime client-vendor interaction and maximizing the advantages of The IT-based CM solution. Subcontractor Subcontractor Vendor Regulator Vendor Regulator EDI File Control Transaction Files Review and Post Data Enterprise CM System Enterprise CM System XA Provides: EDI Provides: Staging of vendor data and Same-file bidirectional data procedures for reference exchange and posting Passive interaction with client data XA Realtime, Active interaciton with EDI client. Transaction Files mimic live data Authorized users access live data Data access limited to Transaction files Files Using PLM-based Workflow for Configuration Management (CM) in the Nuclear Power Industry Advantages – some work to do! NPP’s must adapt to using PLM-based solutions to support CM and to synchronize design changes to asset or product changes, and reduce “slipstreaming”. In the NPP world, this often appears as events that circumvent CM – for example, non-approved parts substitutions and “temporary” plant modifications that are never removed. PLM serves as the method for unifying the application of requirements to design changes, processes and workflow. In NPP’s, requirements are generally considered only relevant to designs – not process and workflow. PLM supports Configuration Management and Design Basis in Regulator Action Tracking for NPP’s, and application of PLM-based CM to regulator action and compliance systems. This is a poorly-understood application of CM in NPP’s, yet these elements control large parts of the NPP design basis. Suppliers, EPC’s and Technology Vendors must also understand the role of CM, SE and PLM in construction of new standards-driven NPP designs (like EPR and Westinghouse AP-1000 NPP designs), as well as understanding the role and handling of Knowledge Systems. .
Load more

Recommended publications
  • Managing the Configuration of Information Systems with a Focus on Security
    MANAGING THE CONFIGURATION OF INFORMATION SYSTEMS WITH A FOCUS ON SECURITY Shirley Radack, Editor Computer Security Division Information Technology Laboratory National Institute of Standards and Technology U.S. Department of Commerce Organizations have to make frequent changes to their information systems in order to implement new and updated hardware and software components, correct software flaws and other errors, address new security threats, and adapt to changing business objectives. These constant changes result in adjustments being made to the configuration of information systems; these activities could have an impact on the security of the systems and operations. In developing information systems, organizations employ many components that can be interconnected in different arrangements to meet the organization’s business, mission, and information security needs. To protect information systems and information, organizations need techniques for the secure configuration, operation, and management of system components, including mainframes, workstations, servers, networks, operating systems, middleware, and applications, and for the management and control of risks to systems and information. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) has issued a new guide to help organizations develop a well-defined process for managing and controlling secure system configurations, and for managing risks in information systems. NIST Special Publication 800-128, Guide to Security- Focused
    [Show full text]
  • Business Rule Based Configuration Management and Software System Implementation Using Decision Tables
    Business Rule Based Configuration Management and Software System Implementation Using Decision Tables Olegas Vasilecas, Aidas Smaizys Vilnius Gediminas Technical University, Sauletekio av. 11, LT-10223 Vilnius, Lithuania [email protected], [email protected] Abstract. Deployment and customization of the software in different information systems of separate organizations challenge large requirement conformity, project and specification management, design and architecture complexity, code integration, compatibility and interoperability issues, frequently causing the need of reengineering through the entire all the system development lifecycle. The paper proposes new business rule based method of information system configuration management and automated way of configuration implementation into the final software system code. 1 Introduction Business systems are functioning according to business rules in specific business domain. Due to dynamic of its nature, business environment is changing frequently according to internal and external influences such as changes in law, new competition etc. [1]. However Business rules (BR) of particular problem domain are similar in several organizations but they are never applied the same way even they depend on the same legal regulations. Production and implementation of such a software system into the large amount of slightly different information systems of separate organizations challenge large requirement conformity, project and specification management, design and architecture complexity,
    [Show full text]
  • ITIL Asset and Configuration Management in the Cloud
    ITIL Asset and Configuration Management in the Cloud January 2017 © 2017, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Contents Introduction 1 What Is ITIL? 1 AWS Cloud Adoption Framework 2 Asset and Configuration Management in the Cloud 3 Asset and Configuration Management and AWS CAF 5 Impact on Financial Management 5 Creating a Configuration Management Database 6 Managing the Configuration Lifecycle in the Cloud 8 Conclusion 9 Contributors 10 Abstract Cloud initiatives require more than just the right technology. They also must be supported by organizational changes, such as people and process changes. This paper is intended for IT service management (ITSM) professionals who are supporting a hybrid cloud environment that leverages AWS. It outlines best practices for asset and configuration management, a key area in the IT Infrastructure Library (ITIL), on the AWS cloud platform.
    [Show full text]
  • Software Project Monitoring and Control
    Module 12 Software Project Monitoring and Control Version 2 CSE IIT, Kharagpur Lesson 31 Risk Management and Software Configuration Management Version 2 CSE IIT, Kharagpur Specific Instructional Objectives At the end of this lesson the student would be able to: • Identify the main categories of risks which can affect a software project. • Explain how to assess a project risk. • Identify the main strategies to plan for risk containment. • Explain what risk leverage is. • Explain how to handle the risk of schedule slippage. • Explain what is meant by configuration of a software product. • Differentiate among release, version and revision of a software product. • Explain the necessity of software configuration management. • Identify the principal activities of software configuration management. • Identify the activities carried out during configuration identification. • Identify the activities carried out during configuration control. • Identify the popular configuration management tools. Risk management A software project can be affected by a large variety of risks. In order to be able to systematically identify the important risks which might affect a software project, it is necessary to categorize risks into different classes. The project manager can then examine which risks from each class are relevant to the project. There are three main categories of risks which can affect a software project: Project risks. Project risks concern varies forms of budgetary, schedule, personnel, resource, and customer-related problems. An important project risk is schedule slippage. Since, software is intangible, it is very difficult to monitor and control a software project. It is very difficult to control something which cannot be seen. For any manufacturing project, such as manufacturing of cars, the project manager can see the product taking shape.
    [Show full text]
  • Quality Assurance and Configuration Management
    Quality Assurance and Configuration Management Energy, Climate, & Sandia National Laboratories implements quality assurance and configuration Infrastructure Security systems essential to the control and traceability of modeling used to demonstrate regulatory compliance. Introduction agencies, including, most significantly, the U.S. Nuclear Regulatory Commission Sandia National Laboratories has a long and the U.S. Environmental Protection history of involvement in significant Agency, as well as various federal, state, national programs directed at solving and other organizations. Among more the national problem of managing the notable successes of this work has been disposal of various forms of nuclear the adaptation of quality assurance wastes. These involvements include to activities sponsored largely by the significant responsibility on the Waste U.S. Department of Energy involved Isolation Pilot Plant (WIPP), the Yucca in the characterization, selection, and Mountain Site Characterization Project performance analyses associated with (YMP), the Hanford Tank Waste programs involving nuclear waste Remediation System (TWRS), and management. Quality assurance the Greater Confinement Disposal requirements originated from a need to (GCD) programs. In addition, control and assure the quality of nuclear Sandia has also played major roles power plant design, construction, and in nuclear waste transportation, operations; modifying these concepts and in several environmental for application to scientific investigation remediation and restoration and characterization activities was a programs, including those at Fernald, necessary and beneficial effort that Ohio, and Hanford, Washington. has proven successful for nuclear waste A key to the success of our activities management. on these programs, particularly for Decades of experience under the WIPP, YMP, TWRS, and GCD, was the scrutiny of independent audits, development and application of quality identifying quality deficiencies, and assurance for program activities.
    [Show full text]
  • Service Asset and Configuration Management (SACM/CMDB) Process
    Service Transition SERVICE ASSET AND CONFIGURATION MANAGEMENT PROCESS VERSION: 4.3 REVISION DATE: February 23, 2017 Service Transition USER GUIDE Service Asset and Configuration Management Process 4.3 | 02/23/2017 Contents Section 1. Introduction ......................................................................................... 1 1.1 Purpose .............................................................................................. 1 1.2 Goal .................................................................................................... 1 1.3 Overview ............................................................................................ 1 1.4 Key Relationships with other processes ........................................ 2 1.5 Definitions .......................................................................................... 2 Section 2. Roles and Responsibilities .................................................................. 4 2.1 Process Owner/Configuration Manager ......................................... 4 2.2 Configuration Item Class Owner ..................................................... 4 2.3 Configuration Item Class Administrator ......................................... 4 2.4 Configuration Item Company Administrator .................................. 5 2.5 IT Service Continuity Management (ITSCM) Role......................... 5 2.6 IT Staff ................................................................................................ 5 2.7 ITSM Product Manager ....................................................................
    [Show full text]
  • 2. Configuration Management
    Computer Science and Software Engineering University of Wisconsin - Platteville 2. Configuration Management Yan Shi SE 3730 / CS 5730 Lecture Notes Outline . What is configuration management? — Identification — Change control — Status accounting — Audit and review . CM techniques and practices — lock-modify-unlock — copy-modify-merge — RCS — branching — deltas . CM tools Why is CM needed? . ``This worked yesterday and doesn't work now.” What happened? . ``The user manual says to do this, but when I do it, something different happens.'' Which is correct, the manual or the code? Why was one changed? . ``The code changes that I made last week are no longer in the code.” What happened to the fix? Who changed the code and Why? . ``The listing doesn't match what the program does!'' Which is correct? . ``Did the bug get fixed in this copy, too?'' Why is CM needed? . Control the changes — Versions of documents need to be combined to form a product, or configuration — With many people working on many files, inconsistencies can occur . Required for testing — We must know and control what source was used to produce a software system in order to know what is being tested — We need to be able to build and rebuild a software system reliably . Reduce the quality cost — https://www.youtube.com/watch?v=Ij1yDpfZI8Q CM CONCEPTS AND COMPONENTS What is Configuration Management? . Software CM is a discipline for managing the evolution of software systems throughout all stages of the software life cycle. SCM is a component of SQA system. — Infrastructure component — Organizational framework . SQA teams are often required to take the responsibility of managing the CM system.
    [Show full text]
  • A Guide to Configuration Management for Intelligent Transportation Systems
    A Guide to Configuration Management for Intelligent Transportation Systems April 2002 Prepared for Intelligent Transportation Systems Joint Program Office US Department of Transportation By Mitretek Systems, Inc. FHWA-OP-02-048 EDL #13622 Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. FHWA-OP-02-048 4. Title and Subtitle 5. Report Date April 2002 A Guide to Configuration Management for Intelligent Transportation 6. Performing Organization Code Systems 7. Author(s) 8. Performing Organization Report No. Paul J. Gonzalez 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) Mitretek Systems, Inc. 11. Contract or Grant No. 600 Maryland Avenue, SW, Suite 755 DTFH61-00-C-00001 Washington, DC 20024 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered Department of Transportation Intelligent Transportation Systems Joint Program Office 400 Seventh Street, SW – Room 3416 Washington, DC 20590 14. Sponsoring Agency Code HOIT 15. Supplementary Notes William S. Jones – Task Manager 16. Abstract This monograph is one of a series intended to introduce the topic of systems engineering to managers and staff working on transportation systems projects, with particular emphasis on Intelligent Transportation Systems (ITS) projects. Systems engineering is a discipline that has been used for over 50 years and has its roots in the building of large, complex systems for the Department of Defense. Systems engineering is an approach to building systems that enhances the quality of the end result and the expectation is that its application to transportation systems projects will make those projects more effective in developing and implementing the systems they are intended to build.
    [Show full text]
  • Configuration Management Process Map
    Configuration Management Process Asset Library Office of Information and Technology Table of Contents Configuration Management Process Map ............................................... 1 Configuration Management Description and Goals................................................ 2 Description................................................................................................................. 2 Goals........................................................................................................................... 2 Configuration Management RACI Information ........................................................ 3 Configuration Management Associated Artifacts Information .............................. 5 Configuration Management Tools and Web Sites Information ............................. 5 Configuration Management Standards Information ............................................... 5 Configuration Management Process ........................................................................ 6 Process Activity Name: CFG-01 Identify Configuration Items ........................... 6 Process Activity Name: CFG-02 Place Configuration Items Under Configuration Control .............................................................................................. 7 Process Activity Name: CFG-03 Adopt Change Management Procedures ...... 8 Process Activity Name: CFG-04 Verify and Audit Configuration Items ............ 9 Process Activity Name: CFG-05 Generate Reports ........................................... 11 Configuration
    [Show full text]
  • Configuration Management Basics
    Configuration Management Basics Enchantment Chapter of INCOSE October 12, 2011 Ann Hodges, CSEP [email protected] 505-844-6284 Topics • What is CM? • CMII Summary • Practical Suggestions for Applying CM Practices What is Configuration Management (CM)? A process that establishes and maintains consistency of a product's attributes with its requirements and product configuration information throughout the product's life cycle [EIA] Why CM? • CM ensures the effective management of the evolving configuration of a system, including all of its work products, during its life cycle [SE: pg 5.11] • Change is inevitable, and managing the impact of change is the focus of CM – It is important to maintain enough of and the right information to ensure that deliverables can be related and are controlled based on engineering and management trade-off decisions Systems engineering activities rely on product configurations being known and controlled When Does CM Occur? • CM activities occur throughout the life cycle of both the project and the product – CM begins at the initial determination of mission need and continues until project closeout or product retirement (from “lust to dust”) Industry Standard CM Activities* Quality Product Configuration Audit Identification Configuration Change Control Configuration Status Accounting Status Configuration CM Planning and Management * Adapted from [EIA] Figure 1 CM Planning and Management • Identify needs/requirements – Factors that might impact CM activities (e.g., team co- location, partners/subcontractors/suppliers,
    [Show full text]
  • Best Practices in Cyber Supply Chain Risk Management
    National Institute of Standards and Technology Best Practices in Cyber Supply Chain Risk Management Conference Materials Cyber Supply Chain Best Practices In a Nutshell: Cybersecurity in the supply chain cannot be viewed as an IT problem only. Cyber supply chain risks touch sourcing, vendor management, supply chain continuity and quality, transportation security and many other functions across the enterprise and require a coordinated effort to address. Cyber Supply Chain Security Principles: 1. Develop your defenses based on the principle that your systems will be breached. When one starts from the premise that a breach is inevitable, it changes the decision matrix on next steps. The question becomes not just how to prevent a breach, but how to mitigate an attacker’s ability to exploit the information they have accessed and how to recover from the breach. 2. Cybersecurity is never just a technology problem, it’s a people, processes and knowledge problem. Breaches tend to be less about a technology failure and more about human error. IT security systems won’t secure critical information and intellectual property unless employees throughout the supply chain use secure cybersecurity practices. 3. Security is Security. There should be no gap between physical and cybersecurity. Sometimes the bad guys exploit lapses in physical security in order to launch a cyber attack. By the same token, an attacker looking for ways into a physical location might exploit cyber vulnerabilities to get access. Key Cyber Supply Chain Risks: Cyber supply chain risks covers a lot of territory. Some of the concerns include risks from: • Third party service providers or vendors – from janitorial services to software engineering -- with physical or virtual access to information systems, software code, or IP.
    [Show full text]
  • Configuration Management Guidelines
    Configuration Management Guidelines Date: April 2014 www.iaqg.org/scmh Section 7.5 Forward . The guideline describes Configuration Management functions and principles and defines Configuration Management terminology for use with Aerospace and Defense AS&D product line. It is targeted at Small and Medium size companies acting as subcontractors/suppliers either in a Build to Print or a Build to Spec relationship. The intention of these guidelines is to assist organizations with understanding the concept and process of Configuration Management and is not intended to be a requirement, nor auditable. 2 Introduction . The Aerospace Standards (e.g. IAQG 9100) call for the implementation of Configuration Management and documents control throughout the entire life cycle of product realization. Configuration Management establishes a language of understanding between the customer and the supplier both in predefined relationship (such as Built to Print) and those in which the supplier is given some freedom (such as Built to Spec). 3 Introduction . When Configuration Management principles are applied using effective practices, return on investment is maximized, product life cycle costs are reduced and the small investment in resources necessary for effective Configuration Management is returned many fold in cost avoidance. These Guidelines provide the reader with the basic ideas of the industry needs, the benefits to the implementing organization and describes Configuration Management functions and principles. 4 List of Topics 1. What is “Configuration”? 2. Why it is important to manage and control configuration in AS&D 3. Applicable Terms and Definitions 4. The objectives of Configuration Management 5. Benefits for an enterprise gained through application of CM 6.
    [Show full text]