Outline Guide to ITER PON Archiving

Transcription

1 IDM UID B7N2B7 VERSION CREATED ON / VERSION / STATUS 06 Mar 2013 / 1.1/ Approved EXTERNAL REFERENCE Report Outline Guide to ITER PON Archiving Design, development, procurement, operation and maintenance of ITERPON Archiving AbstractThis guide provides simple and practical guidance to plant system Instrumentation and Control (I&C) responsible officers and designers on how to design, develop, procure, operate and maintain an effective plant system archiving system on PON. Approval Process Name Action Affiliation Author Utzel N. 06-Mar-2013:signed IO/DG/DIP/CHD/CSD/CDC CoAuthor Reviewers Wallander A. IO/DG/DIP/CHD/CSD Approver Thomas P. 06-Mar-2013:approved IO/DG/DIP/CHD Document Security: level 1 (IO unclassified) RO: Journeaux Jean-Yves Read Access AD: ITER, AD: External Collaborators, AD: Division - Control System Division - EXT, AD: Section - CODAC - EXT, AD: Section - CODAC, project administrator, RO, LG: CODAC team PDF generated on 06-Mar-2013 DISCLAIMER : UNCONTROLLED WHEN PRINTED PLEASE CHECK THE STATUS OF THE DOCUMENT IN IDM

2 Title (Uid) Versio n Change Log Latest Status Issue Date Description of Change Outline Guide to ITER PON Archiving (B7N2B7_v1_1) Outline Guide to ITER PON Archiving (B7N2B7_v1_0) Outline Guide to ITER PON Archiving (B7N2B7_v0_0) v1.1 Approved 06 Mar 2013 v1.0 Approved 18 Jan 2013 v0.0 In Work 23 Oct 2012 Title change Version for final approval PDF generated on 06-Mar-2013 DISCLAIMER : UNCONTROLLED WHEN PRINTED PLEASE CHECK THE STATUS OF THE DOCUMENT IN IDM

3 Table of Contents 1 Introduction PCDH Context Document Scope Related documents PON Archiving Context What is a sample? When is an EPICS PV value notified to the Archive Engine? Difference between Log and Archive Difference between Backup and Archive CODAC PON Archiving Architecture PON Archiving Physical Architecture PON Archiving Software Architecture PON Archiving Architecture Before Integration PON Archiving Modes Event Driven Archiving Archiving Monitor Mode Archiving Monitor with Threshold Mode Archiving Scan Mode PON Archiving Management Lifecycle Identification of PON Archiving Requirements PON Archiving Rationalisation PON Archiving Detailed Design PON Archiving Implementation PON Archiving Operation PON Archiving Maintenance PON Archiving Monitoring and Assessment PON Archiving Management of Change PON Archiving Audit PON Historic Data Retrieval PON Archiving Trending PON Archiving Post-Analyser PON Archiving Export Outline Guide to ITER PON Archiving Page 1 of 11

4 1 Introduction 1.1 PCDH Context The Plant Control Design Handbook (PCDH) [RD1] defines methodology, standards, specifications and interfaces applicable to the whole life cycle of ITER plant Instrumentation & Control (I&C) systems. I&C standards are essential for ITER to: Integrate all plant systems into one integrated control system. Maintain all plant systems after delivery acceptance. Contain cost by economy of scale. The PCDH comprises a core document which presents the plant system I&C life cycle and recaps the main rules to be applied to the plant system I&Cs for conventional controls, interlocks and safety controls. Some I&C topics will be explained in greater detail in dedicated documents associated with PCDH as presented in Figure 1.1. This document is one of them. PCDH core and satellite documents: v7 PS CONTROL DESIGN INTERLOCK CONTROLS Guidelines for PIS design (3PZ2D2) Guidelines for PIS integration & config. (7LELG4) Management of local interlock functions (75ZVTY) PIS Operation and Maintenance (7L9QXR) Plant system I&C architecture (32GEBH) Methodology for PS I&C specifications (353AZY) CODAC Core System Overview (34SDZ5) I&C CONVENTIONS I&C Signal and variable naming (2UT8SH) ITER CODAC Glossary (34QECT) ITER CODAC Acronym list (2LT73V) OCCUPATIONAL SAFETY CONTROLS Guidelines for PSS design (C99J7G) NUCLEAR PCDH (2YNEFU) CATALOGUES for PS CONTROL Slow controllers products (333J63) Fast controller products (345X28) Cubicle products (35LXVZ) Integration kit for PS I&C (C8X9AE) Core PCDH (27LH2V) Plant system control philosophy Plant system control Life Cycle Plant system control specifications CODAC interface specifications Interlock I&C specification Safety I&C specification PS CONTROL DEVELOPMENT I&C signal interface (3299VT) PLC software engineering handbook (3QPL4H) Guidelines for fast controllers (333K4C) Software engineering and QA for CODAC (2NRS2K) Guidelines for I&C cubicle configurations (4H5DW6) CWS case study specifications (35W299) PS SELF DESCRIPTION DATA Self description schema documentation (34QXCP) PS CONTROL INTEGRATION The CODAC -PS Interface (34V362) PS I&C integration plan (3VVU9W) ITER alarm system management (3WCD7T) ITER operator user interface (3XLESZ) Guidelines for PON archiving (B7N2B7) PS Operating State management (AC2P4J) Guidelines for Diagnostic data structure (354SJ3) Legend This document Available and approved (XXXXXX) IDM ref. Figure 1.1 Schema of PCDH documents 1.2 Document Scope This guide provides simple and practical guidance to responsible officers and designers of plant system Instrumentation and Control (I&C) on how to design, develop, procure, operate and maintain an effective plant system archiving system on the PON (Plant Operation Network). 1.3 Related documents [RD1] Plant Control Design Handbook (PCDH). (ITER_D_27LH2V) Outline Guide to ITER PON Archiving Page 2 of 11

5 2 PON Archiving Context The PON scalable and central Archiving System can monitor any value that is available via Channel Access (CA) - the EPICS communication protocol (~10Hz) - such as tank levels, pump status or system pressures, store them and make them available to the operator for trend analysis. As shown on Figure 2-I PON Archiving Overview, the Archive Engines collect data from a given list of Process Variables (PV) controlled by an EPICS IOC (Input/Output Controller). The settings of the archive monitoring can be configured: one may store every change, store changes that exceed a dead band or use periodic scanning. The configuration and operation of the Archive Engines will require some planning, as only data that was sampled and stored will be available for future retrieval and analysis. Some sensible compromise will have to be made between the urge to store all miniscule changes of all the available PV on one hand, and data storage constraints on the other hand. Configuration of each PV to archive. Archive monitoring parameters Archive Engines Archive Storage PON / Channel Access Data Retrieval CAS CAC Slow Controllers IOC CAS CAC Fast Controllers IOC Figure 2-I PON Archiving Overview 2.1 What is a sample? The PON Archiving System monitors Process Variables that are served by an IOC EPICS Channel Access server. It stores all the information available via CA according to the archive monitoring parameters: Original Time Stamp (nanosecond precision) Value (integer, float, array or string) Alarm Status/Severity (major, minor, no_alarm) Meta information: like engineering units and display ranges. The PON Archiving System stores the original time stamps as it receives them from Channel Access. It cannot check if these time stamps are valid, except that it refuses to go back in time because it can only append new values/time stamps in the data storage. It is therefore imperative to properly configure the data sources, i.e. the clocks on the CA servers and the slow/fast controllers. NOTE: If the CA server provides bad time stamps, i.e. stamps that are older than values which are already in the storage, the Archive Engine will log a warning message and refuse to store the samples affected. This is a common reason for Why is there no data in my archive?. Outline Guide to ITER PON Archiving Page 3 of 11

6 2.2 When is an EPICS PV value notified to the Archive Engine? Before even considering the archive monitoring options available, it is important to understand how the Channel Access servers which control the Process Variables will notify the Archive Engine of a status change. In the following example - Figure 2-II Monitoring screen of an analogue input (AI) a simulated signal gives the temperature within [-10º C; +10º C], with Alarm Limits and Severity defined. Figure 2-II Monitoring screen of an analogue input (AI) What happens if the temperature is to be archived? The PV is scanned at 10 Hz, so a maximum of 10 values per second could be expected. Practically: the archive dead band (ADEL) limits the values that will be received by the Archive Engine via CA to changes beyond 0.10º C in order to reduce the amount of processing and network traffic by filtering out negligible value changes. So the temperature signal whose EPICS definition is shown on Figure 2-III EPICS analogue input record, will be archived on value change by more than the ADEL threshold, at most 10 values per second. record (ai,"cws-tcph-fxxx:temp") { field(desc, "Temperature") field(egu, "C") field(hhsv, "MAJOR") field(high, "8") field(hihi, "9") field(hopr, "10") field(hsv, "MINOR") field(llsv, "MAJOR") field(lolo, "-9") field(lopr, "-10") field(low, "-8") field(lsv, "MINOR") field(prec, "2") field(scan, ".1 second") field(adel, "0.1") } Figure 2-III EPICS analogue input record NOTE: The Archive Engine has no knowledge of the scan rate or the dead band configuration of the EPICS IOC! It is just a CA client that subscribes to PV and monitors them. The Archive Engine stores the time stamp with each value as well as the alarm status and severity. So when the temperature is higher than the HIGH level of 8º C, the status/severity of HIGH/MINOR will be archived in addition to the value (VAL field). One illustration is given in Figure 2-IV Archived Samples Export View which provides a tabular view of the samples with their time stamp, value and alarm severity/status. Outline Guide to ITER PON Archiving Page 4 of 11

7 2.3 Difference between Log and Archive Figure 2-IV Archived Samples Export View Messages are logged on the Log System to keep track of some events like an operator action - alarm acknowledgment, a configuration change, an alarm state change or some severe system exceptions. The operator can access to the message history as shown on Figure 2-V Message History View. Figure 2-V Message History View 2.4 Difference between Backup and Archive A classic backup application takes periodic images of active data in order to provide a method of recovering information that have been deleted or destroyed. Essentially, a backup is designed as a shortterm insurance policy to facilitate disaster recovery, while archive is designed to provide ongoing rapid access to historical data in order to analyse trends or a sequence of events. Outline Guide to ITER PON Archiving Page 5 of 11

8 3 CODAC PON Archiving Architecture 3.1 PON Archiving Physical Architecture The PON Archiving architecture supports many archive engines, typically one archive engine per control group (CBS 1) such as Magnets, Cryogenics or Water Cooling as shown (2) on Figure 3-I CODAC Physical Architecture. Operator Interface 3 PON Archive Engine 2 Data Producers 1 Figure 3-I CODAC Physical Architecture 3.2 PON Archiving Software Architecture As a CODAC service, the PON Archiving System resides on top of the software architecture as shown on Figure 3-II CODAC Software Architecture. Figure 3-II CODAC Software Architecture Outline Guide to ITER PON Archiving Page 6 of 11

9 3.3 PON Archiving Architecture Before Integration The PON Archiving System is present in the mini-codac environment before integration (including the Factory Acceptance Test (FAT)), as shown on Figure 3-III Mini-CODAC Architecture. High Performance Networks (HPN) Time Communication Network (TCN) Synchronous Data Network (SDN) Mini-CODAC CODAC Terminal Central Interlock System Audio/video Network (AVN) Plant Operation Network (PON) Plant System I&C Plant Operation Network (PON) Central Interlock Network (CIN) Plant System Host Fast Controller Fast Controller COTS Intelligent Device Slow Controller Slow Controller Interlock Controller Signal Interface Remote I/O Remote I/O Signal Interface Signal Interface 4 PON Archiving Modes 4.1 Event Driven Archiving Figure 3-III Mini-CODAC Architecture Archiving can be enabled according to a specific variable defined as the enabling variable: Whenever the value of this variable is above zero, sampling and archiving of a whole group will be enabled until the variable returns to zero or below. A typical use case is the configuration of a group with all power supply process variables and the power supply state ON/OFF as the enabling variable of the group. The benefit of this configuration is to suppress archiving of noise while the power supply is OFF. 4.2 Archiving Monitor Mode Actuators and Sensors Using the Archiving Monitor mode, each value received is stored: In this mode, the Archive Engine requests a Channel Access Monitor, i.e. it subscribes to changes and stores all the values sent out, The Channel Access server determines when values are sent to the Archive Engine client, With a perfectly configured data source with adequate EPICS thresholds that only pass significant changes to the archive engine, this mode is ideal and is the recommended one. Important changes in value are written to the archive, whilst noise in the signal is suppressed to minimise waste of resources. Outline Guide to ITER PON Archiving Page 7 of 11

10 4.3 Archiving Monitor with Threshold Mode Using the Archive Monitor with Threshold mode, each value received is compared by the Archive Engine to the previous one and stored only if the change is greater than the dead band: The Archive Engine performs the dead band checks in place of the Channel Access server. But to minimise network traffic and Archive Engine CPU load, this should happen on the EPICS PV level with the configuration of the PV ADEL threshold. 4.4 Archiving Scan Mode Using the Archiving Scan mode, the Archive Engine receives each update from the data source but only writes the most recent ones at specific intervals, for example once every 5 minutes: This mode was created for PVs which do not have a good dead band configuration and where using monitored mode would add too many data to the archive, But should the archive engine fill disk space every 5 minutes if the PV has no significant change for hours? If an important event happened producing a brief blip, it will probably be missed when storing a value every 5 minutes. Periodic sampling is clearly imperfect, but sometimes a workable compromise. 5 PON Archiving Management Lifecycle The PON archiving management lifecycle covers the design and maintenance activities from philosophy and guidelines to management of change, thus from initial conception through decommissioning as shown on Figure 5-I PON Archiving Management Lifecycle. Figure 5-I PON Archiving Management Lifecycle Outline Guide to ITER PON Archiving Page 8 of 11

11 5.1 Identification of PON Archiving Requirements Some sensible compromise will have to be made between the urge to store all the available PV on one hand, and data storage and network traffic constraints on the other. When this has been accomplished, the need for an archived PV has been identified and it is ready to be rationalised. 5.2 PON Archiving Rationalisation Rationalisation is the process of examining one PV to be archived at a time against the principles defined in this document. The product of rationalisation is a set of consistent, well-documented archived PVs. The documentation supports both the design process and operator training. Example of report: Group Name Group Description RF-ICH1-RS1 Archiving of RF Source 1 PVs PV Name RF-ICH1-RS1: OPSTATE RF-ICH1-RS1: AHF11-JZ-CRC RF-ICH1-RS1: BDC113-JT-CRC RF-ICH1-RS1-CMB-1: JT-CRC 5.3 PON Archiving Detailed Design PV Description RS1 Common Operational State RF Power Level Actuator DC Screen Grid Voltage Transmit HVA1 Combined Voltage Enabling variable? Archiving Mode? YES Scan 1 minute NO Monitor 1 second NO Monitor 1 second NO Monitor with Threshold of 0.1 MW Estimated Archive Period 1 second The design stage includes the basic configuration of archived PV attributes including the definition of the thresholds and smoothing filter to reduce noise on the input signal. The objective is to define these necessary parameters on the EPICS IOC level to reduce the amount of processing negligible value changes. Then, the Archive Engine should be configured using an Archive Configuration Tool to monitor all PV value changes and rely on EPICS IOC to determine when values are sent. 5.4 PON Archiving Implementation Implementation is the stage where the design is put into service. This process includes training for the operator and initial testing. 5.5 PON Archiving Operation Operation is the stage in the life cycle when the PV is archived and used for trend analysis. The output of this stage is the operational list of archived PVs with their sampling rate and archived volume on different periods: daily, weekly and according to operational conditions: test & conditioning, maintenance or pulse mode. 5.6 PON Archiving Maintenance In the maintenance stage, the archived PV is not available or the PON Archiving System is not operational because it is being tested or repaired. Outline Guide to ITER PON Archiving Page 9 of 11

12 5.7 PON Archiving Monitoring and Assessment Performance monitoring is the periodic collection and analysis of data from archived PVs in the operation stage of the life cycle. Without monitoring, it is almost impossible to maintain an effective PON Archiving System. It is the primary method to detect problems such as unexpected archived PV floods. The assessment using the archive engine monitoring interface and the web reports may trigger maintenance work or identify the need of changes based on the archive monitoring report. 5.8 PON Archiving Management of Change Management of Change is the structured process of approval and authorisation to make additions, modifications, and deletions of archived PV from the system. Changes may be identified by many means, including operator suggestions and monitoring. The change process should feed back to the identification stage to ensure that each change is consistent. The outputs of this phase are the authorised archived PV changes. 5.9 PON Archiving Audit Periodic reviews are conducted to maintain the integrity of PON Archiving System and its associated processes. Outline Guide to ITER PON Archiving could be adapted as a result of an audit in order to improve the system. The outputs of this stage are recommendations for improvement. Outline Guide to ITER PON Archiving Page 10 of 11

13 6 PON Historic Data Retrieval 6.1 PON Archiving Trending The operator can: Have both historical and live data trending, Define online or use predefined plot configuration, Plot many trended EPICS PVs at once, Use formulas (min, max, Java Math routines ), Zoom, individually scale the time axis and the value range and start/stop scrolling, Make annotations, Save a snapshot to PNG file. For improved display and analysis capabilities, the line thickness, color and style of trends can be configured. Figure 6-I Data Plot View gives the trend of 3 archived PVs over 1 day of operation. 6.2 PON Archiving Post-Analyser Figure 6-I Data Plot View In addition the PON Archiving Analyser tool gives the capability to display integrated statistical functions FFT, correlation, Gaussian fit, exponential fit or line fit. 6.3 PON Archiving Export The process values and statistical data displayed in the plot can be exported to a CSV/Matlab file at the push of a button and analysed using standard tools. Outline Guide to ITER PON Archiving Page 11 of 11