CODAC Requirements Specification Guidelines for PSOS SM management by COS SM

Transcription

1 IDM UID AC2P4J VERSION CREATED ON / VERSION / STATUS 24 Apr 2013 / 2.5/ Approved EXTERNAL REFERENCE CODAC Requirements Specification Guidelines for PSOS SM management by COS SM Guidelines for specifications of the Plant System Operating State (PSOS) machines and link to COS state machines Approval Process Name Action Affiliation Author Journeaux J.- Y. 24-Apr-2013:signed IO/DG/DIP/CHD/CSD/PCI Co-Authors Reviewers Wallander A. Yonekawa I. 06-May-2013:recommended 24-Apr-2013:recommended IO/DG/DIP/CHD/CSD IO/DG/DIP/CHD/CSD/PCI Approver Thomas P. 28-May-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, AD: Auditors, project administrator, RO, LG: CODAC team PDF generated on 29-May-2013 DISCLAIMER : UNCONTROLLED WHEN PRINTED PLEASE CHECK THE STATUS OF THE DOCUMENT IN IDM

2 Title (Uid) Guidelines for PSOS SM management by COS SM (AC2P4J_v2_5) Guidelines for PSOS SM management by COS SM (AC2P4J_v2_4) Guidelines for PSOS SM management by COS SM (AC2P4J_v2_3) Guidelines for PSOS SM management by COS SM (AC2P4J_v2_2) Guidelines for PSOS SM management by COS SM (AC2P4J_v2_1) Guidelines for PSOS SM management by COS SM (AC2P4J_v2_0) Guidelines for PSOS SM management by COS SM (AC2P4J_v1_1) Guidelines for PSOS SM management by COS SM (AC2P4J_v1_0) Change Log Latest Status Issue Date Description of Change Versio n v2.5 Approved 24 Apr 2013 v2.4 Signed 24 Apr 2013 v2.3 Approved 17 Jan 2013 v2.2 Signed 17 Jan 2013 v2.1 Signed 17 Jan 2013 v2.0 Signed 17 Jan 2013 v1.1 Signed 09 Nov 2012 v1.0 Signed 05 Jul 2012 Clarification added for rules to apply for COS/PSOS mapping: Each COS-OPSTATE shall be mapped to a PSOS-STATE. Mapping of COS-OPREQ and NA Clarification added for rules to apply for COS/PSOS mapping: Each COS-OPSTATE shall be mapped to a PSOS-STATE. Mapping of COS-OPREQ and NA New version reviewed for quality and issued in scope of PCDH v7 New version reviewed for quality and issued in scope of PCDH v7 Niew version reviewed for quality and issued in scope of PCDH v7 New version revieed sor quality and issued in scope iof PCDH v7 Includes Anders technical notes and cryo illustration for internal CSD review only PDF generated on 29-May-2013 DISCLAIMER : UNCONTROLLED WHEN PRINTED PLEASE CHECK THE STATUS OF THE DOCUMENT IN IDM

3 Document Revision History Version Status Date Changes 1.0 Draft 19/08/2010 Initial version 1.1 Draft 09/11/2012 Includes Anders note + cryo illustration for CSD internal review 2.0 Draft 14/11/2012 Modification of chapter 4 and 5 for cryo illustration 2.1 Draft 18/11/2012 Modification of chapter 3 and 4 for simplification, alignment of chapter 5 accordingly 2.2 Draft 29/11/2012 Anders and Lana comments introduced 2.3 Final 06/12/2012 Completion with ECH configuration 2.4 Final 17/01/2013 Reviewed for quality and issued in scope of PCDH v7 2.5 Final 24/04/2013 Clarification added for mapping of COS-OPREQ and PSOS- OPSTATE (after discussion with Lana)

4 Table of Contents 1 INTRODUCTION Document scope Acronyms Conventions Applicable documents Reference documents OPERATION REQUIREMENTS FOR COS SM Shutdown Not ready Ready Starting Running ARCHITECTURE REQUIREMENTS FOR GOS, COS AND PSOS SM State management architecture and flow of actions Process variables for state management IMPLEMENTATION REQUIREMENTS APPLICABLE TO PSOS SM ILLUSTRATION OF A CONTINUOUS PLANT SYSTEM: CRYOGENIC SYSTEM Introduction to the cryogenic system The cryogenic system functional I&C architecture The cryogenic system state machines COS/PSOS mapping for CRYO-CH plant system I&C COS/PSOS mapping for CRYO-CA plant system I&C COS/PSOS mapping for CRYO-CD plant system I&C COS/PSOS mapping for CRYO-MC plant system I&C ILLUSTRATION ON A PULSED PLANT SYSTEM: EC SYSTEM Introduction to the Electron Cyclotron (EC) system The EC system functional I&C architecture The EC system state machines COS/PSOS mapping for EC-GN plant system I&C COS/PSOS mapping for EC-TS plant system I&C COS/PSOS mapping for EC-MC plant system I&C...25 Page 2 of 26

5 1 Introduction 1.1 Document scope This document addresses the implementation of state management in CODAC and plant system I&Cs as specified in the Operations Handbook - 2 Operational States (2LGF8N v1.3). Only the global operational state (GOS) when it is to equal plasma operation state (POS) is considered in this version. In particular, this document addresses how to synchronize all plant systems for the execution of a pulse using a common operational state (COS) and plant system operational states (PSOS). 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 are explained in greater details in dedicated documents associated with PCDH as presented in Figure 1-1. This document is one of them, covering state management. The PCDH requirement related to state management is as follows: Plant system I&C shall implement COS and PSOS. 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: PCDH document package Page 3 of 26

6 1.2 Acronyms Following acronyms are used in this document: CBS CODAC COS CP CSD DA ECH&CD EPICS GOS I&C IO NA PA PCDH PLC PON POS PS PSH PS I&C RO PSOS PSP PV RO SDD SM TBC TBD Control Breakdown Structure COntrol Data Access and Communications Common Operating State Cryopump Control System Division of IO Domestic Agency Electron Cyclotron Heating and Current Drive Experimental Physics and Industrial Control System Global Operating State Instrumentation & Control ITER Organization Non Applicable Procurement Arrangement Plant Control Design Handbook Programmable Logic Controller Plant Operation Network Plasma Operating State Plant System Plant System Host Plant System I&C Responsible Officer Plant System Operating State Plant System Profile database Process Variable Responsible Officer Self Descripting Data State Machine To Be Confirmed To Be Defined Page 4 of 26

7 1.3 Conventions Throughout this document mandatory rules (or requirements) are enumerated and prefixed with R. Non mandatory guidelines (or recommendations) are enumerated and prefixed with G. The table below provides a list of paragraph identifiers used in this document. AD Applicable document D G RD SD Deliverable for a lifecycle phase Guideline / Recommendation Reference document Satellite document Rule referenced in core PCDH Paragraphs marked with TBD or TBC represent work in progress which will be confirmed and expanded further in the subsequent releases of this document. 1.4 Applicable documents The following applicable documents are referenced in this document: [AD1] Plant Control Design Handbook (27LH2V v7.1 or higher) [AD2] Operations Handbook 2 Operational States (2LGF8N v1.3 or higher). 1.5 Reference documents The following PCDH satellite documents are mentioned in this document: [SD1] [SD2] [SD3] [SD4] [SD5] [SD6] [SD7] Plant System I&C Architecture (32GEBH) I&C signal and variable naming convention (2UT8SH) Self description schema documentation (34QXCP) The CODAC - Plant System Interface (34V362) PLC software engineering handbook (3QPL4H) ITER CODAC glossary (34QECT) ITER CODAC Acronym list (2LT73V) Following plant system reference documents are used in this document: [RD1] ITER Control Breakdown Structure (CBS) (9TYFWC) [RD2] Main flow charts for the Cryogenic System (4AH6S4) [RD3] EC Control Breakdown Structure (35W8PZ) [RD4] Gyrotron Pair - Power Control Block EC.GN.PxC (A5U9DB) [RD5] TL Control Block (EC.TS.Tx) (BRAUCN) Page 5 of 26

8 2 Operation requirements for COS SM The state machines for GOS=POS and COS, as given in the Operations Handbook [AD2], are reproduced in Figure 2-2 and Figure 2-1 Figure 2-2: POS Figure 2-1: COS For convenience the generic description of each COS, as given in the Operations Handbook, is reproduced below. The handling of states Local and Safe still need to be clarified. 2.1 Shutdown These states represent conditions in which a plant system is declared as not operational. In these states the plant system cannot present any active hazard to machine operation or control Off Absent Safe The plant system is present, but it has informed the CODAC supervisory control system that it is being switched off or rebooted and will not be able to report its state. The plant system is not present. It is either not installed, has been removed or disconnected from the machine and CODAC networks and cannot report any state. The plant system is in a well-defined safe state. This may be trigged by the plant system safety system or at the instruction of the Central Safety System. (This state exists only where applicable). Page 6 of 26

9 2.2 Not ready These states indicate that the plant system is operational but is not currently ready to start initialising. Not Ready Local Fault The plant system is operational but currently not ready to receive configuration, e.g. it may be performing system start-up tasks. The plant system is undertaking some extended local preparation such as local control, conditioning or cleaning. The plant system has some internal fault, which must be corrected either manually or automatically. 2.3 Ready Ready The plant system is ready to receive configuration and start initialising. 2.4 Starting The plant system has received a configuration command and will initialise itself. It will configure and prepare itself under the control of the CODAC Supervisory Control System. Initialising Initialised Aborting The plant system has received the command to initialise and configure itself according to a pre-defined set of parameters. The plant system declares that it has initialised and configured itself according to the pre-defined set of parameters, and that it is ready to transfer to the executing state. The plant system has received a command to abort preparation and is executing any necessary actions under supervisory control. (This state exists only where applicable). 2.5 Running The plant system is executing. Pulsed systems are participating in a pulse sequence under fast timer control. Steady state systems remain under CODAC supervisory control. Executing Post-Checks Terminating The plant system is in its running state, that is: normal operation for steady state systems. Pulsed systems are under fast timing control. The plant system has completed its execution. Pulsed systems are executing any necessary actions under fast timing control. The plant system has received a command to terminate operations. Pulsed systems will execute any necessary actions under fast timing control. Page 7 of 26

10 3 Architecture requirements for GOS, COS and PSOS SM 3.1 State management architecture and flow of actions The architecture and deployment of the various state machines (SM) are illustrated in Figure 3-1. The flow of actions is described below. This flow introduces a set of process variables (PV) to implement operator/sm requests and reflect SM states, these PVs are listed in section 3.2. GOS SM CTRL:GOS-GOREQ 1 2 CTRL:GOS-GOSTATE CTRL:POS-OPREQ 3 POS SM 10 CTRL:POS-OPSTATE Central supervision (CODAC) CBS1:COS-OPREQ 4 Agregate COS SM 9 CBS1:COS-OPSTATE ITER control group (CODAC) CBS1-CBS2:COS-OPREQ 5 Agregate 8 CBS1-CBS2:COS-OPSTATE Plant System I&C COS-PSOS SM Plant System Host and CODAC Core System Provided by IO/CODAC CBS1-CBS2:PSOS-OPREQ 6 7 CBS1-CBS2:PSOS-OPSTATE Plant System Controllers And PSOS state machines Provided by plant system I&C supplier PSOS SM Figure 3-1: State management architecture The operator sets a global operating state by writing in CTRL:GOS-GOREQ (1). The GOS state machine (SM) detects the request and validates if the transition is allowed. If so, it updates CTRL:GOS-GOSTATE (2). Any process in the ITER control system can subscribe to this PV state. The GOS SM is only a management flag without any actions on the plant, and which can be used by any control logic in the control system to implement prohibitive logic. If GOS is POS, the operator can operate the POS SM by writing in CTRL:POS-OPREQ (3). The POS SM detects the request, performs internal work and writes CBS1:COS-OPREQ (4) in all of the ITER control groups involved. The COS SM at ITER control group level detects the request CBS1:COS-OPREQ (4). As a result of the execution of a COS request, the COS SM performs internal work and writes CBS1-CBS2:COS-OPREQ (5) in plant system I&Cs. Page 8 of 26

11 The plant system I&C associates the CBS1-CBS2:COS-OPREQ with the corresponding CBS1- CBS2:PSOS-OPREQ (6). The plant system specific state machine (PSOS SM) subscribes to CBS1-CBS2:PSOS-OPREQ and performs any corresponding actions that are required on the plant system. The plant system specific state machine (PSOS SM) publishes results in CBS1-CBS2:PSOS-OPSTATE (7). The plant system I&C associates the CBS1-CBS2:PSOS-OPSTATE with the corresponding CBS1- CBS2:COS-OPSTATE and publishes the CBS1-CBS2:COS-OPSTATE (8). In the COS SM at ITER control group level, a set of aggregation and guarding EPICS database records subscribes to all of the CBS1-CBS2:COS-OPSTATE involved. A change of any of those PV s triggers a recalculation and evaluation. The result is published in CBS1:COS-OPSTATE (9). In the POS SM a set of aggregation and guarding EPICS database records subscribes to all of the CBS1:COS-OPSTATE involved. A change of any of those PV s triggers a recalculation and evaluation of the POS SM. The result is written to CTRL:POS-OPSTATE (10). The POS SM may trigger an automatic transition by writing a new value in CTRL:POS-OPREQ. 3.2 Process variables for state management The standard process variables (PV) introduced in section 3.1 are all enumerations. CTRL:GOS-GOREQ 1 gotoltm 2 gotostm 3 gototcs 4 gotopos 5 gotosafe Table 3.1: Enumerations for requested and actual GOS CTRL:GOS-GOSTATE 1 LTM 2 STM 3 TCS 4 POS 5 SAFE CTRL:POS-OPREQ CTRL:POS-OPSTATE 1 gotonotready 1 NotReady 2 gotoready 2 Ready 3 Start 3 Start 4 gotowait 4 Wait 5 gotoprechecks 5 PreChecks 6 gotofinalprep 6 FinalPrep 7 Pulse 7 Pulse 8 PostCheck 8 PostChecks 9 Terminate 9 Terminate 10 Abort 10 Abort Error Local Table 3.2: Enumerations for requested and actual POS Page 9 of 26

12 *:COS-OPREQ *:COS-OPSTATE SwitchOff 1 Off 2 SwitchOn 2 NotReady 3 gotoready 3 Ready 4 Initialise 4 Initialising 5 gotoinitialised 5 Initialised 6 Execute 6 Executing 7 PostCheck 7 PostChecks 8 Terminate 8 Terminating 9 Abort 9 Aborting gotolocal? Absent Local gotosafe? Fault Safe Table 3.3: Enumerations for requested and actual CBS1 or CBS1-CBS2 COS. * is Page 10 of 26

13 4 Implementation requirements applicable to PSOS SM From chapter 3, GOS, COS and PSOS SM architecture is organized into 3 hierarchical layers: Central supervision, ITER control group and plant system I&C. See [RD1] for details on ITER control groups. ITER control groups match CBS level 1, while Plant System I&Cs match CBS level 2. Central supervision control and ITER control group control levels are implemented by CODAC systems. The associated implementation requirements are out of scope of this document. The following requirements are applicable to the plant system I&C in order to implement the COS concept as specified in section 3.1: REQ 1: PSOS SM must subscribe to PV CBS1-CBS2:PSOS-OPREQ. REQ 2: PSOS SM must publish on PV CBS1-CBS2:PSOS-OPSTATE. REQ 3: There must be one and only one PSOS SM per plant system I&C. REQ 4: Plant system I&C supplier must provide a PSOS - COS OPREQ and OPSTATE mapping table (Table 4-1). REQ 5: PSOS - COS OPREQ and OPSTATE must be deployed on the same IOC. PSOS SM must be deployed on one and only one controller. *:COS-OPREQ *:PSOS-OPREQ *:PSOS-OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 StateA 1 Off 2 SwitchOn 2 NA 2 StateB 2 NotReady 3 gotoready 3 gotostatec 3 StateC 3 Ready 4 Initialise 4 gotostated 4 StateD 4 Initialising 5 gotoinitialised 5 gotostatee 5 StateE 5 Initialised 6 Execute 6 gotostatef 6 StateF 6 Executing 7 PostCheck 7 gotostateg 7 StateG 7 PostChecks 8 Terminate 8 gotostateh 8 StateG 8 Terminating 9 Abort 9 gotostatei 9 StateH 9 Aborting 10 Absent 11 gotolocal? 11 gotostatelocal? 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 4.1: Example of PSOS / COS OPREQ and OPSTATE mapping table, * = CBS1-CBS2 The mapping table is defined in SDD and the SDD automatically generates a set of EPICS calculation records and the COS-PSOS SM. The following design requirements will be implemented in SDD: The *:COS-OPREQ 1-9 may or may not have a corresponding *:PSOS-OPREQ depending on how the plant system I&C is coupled to the COS SM. e.g. StateB in table 4.1 is not expected to be controlled by the COS SM; therefore there is no corresponding *:PSOS-OPREQ, this configuration is identified in the table by NA (Non Applicable) A *:PSOS-OPSTATE may correspond to multiple *:COS-OPSTATE (StateG in table 4.1). The COS SM at control group level will apply logic to determine which CBS1.COS-OPSTATE to set. A *:COS-OPSTATE must correspond to one and only one *:PSOS-OPSTATE. NA (Non applicable) are accepted in the PSOS/COS mapping tables in PSOS-OPREQ column for following configurations only: - For mapping with SwitchOn and SwitchOff in case corresponding states are kept under plant system control only (decoupled from COS state machines) Page 11 of 26

14 - All PSOS-OPREQ participating to the pulse loop (Ready, Initialise, execute, postcheck, terminate and abort) are assigned to NA, see illustration in Table 5-2. The table can have a maximum of 16 rows. The PSOS-OPREQ and PSOS-OPSTATE enumerations are identified by an alpha-numeric string of maximum 25 characters. Underscore is allowed. In addition, the plant system I&C developer is encouraged to align PSOS states to COS states as defined in section 2 as much as possible. Thus, the following steps are required by the plant system I&C developers: 1. Develop the plant system state machine (PSOS SM) accessing the hardware and taking the COS standard states into account as much as possible. 2. Connect the plant system state machine to COS state machine using the two PV s CBS1-CBS2:PSOS-OPREQ and CBS1-CBS2:PSOS-OPSTATE. These PVs are created by default on PSH. 3. Provide the COS PSOS mapping table and enter it in SDD 4. Use the SDD translator to complete the EPICS database required by COS SM. 5. Start the PSOS SM 6. Test the interface using the standard HMI provided on Mini-CODAC. Page 12 of 26

15 5 Illustration of a continuous plant system: Cryogenic system Since this is based on specifications which are not yet frozen, the examples of the implementation of the COS concept are given for illustration purposes only and must not be used as inputs for any other purpose. 5.1 Introduction to the cryogenic system The fundamental function of the cryogenic system is to cool down and maintain the required operating temperatures of the ITER components that operate at cryogenic temperatures. The cryogenic system provides the cooling of the ITER cryogenic components at four main nominal temperature levels, namely: 4 K, 50 K and 80 K, as well as a 300 K level. The 4 K temperature level is for the following components: Superconducting magnet system: central solenoid (CS) magnet, the toroidal field (TF) magnet, magnet structure (ST), poloidal field and correction coils (PF&CC) magnet system. Cryo-pump system: cryo-pumps for the vacuum vessel and cryostat, cryo-pumps for the neutral beam injectors. The cryogenic system will provide the cooling at 50 K for the high temperature superconducting (HTS) current leads of the magnet system. The cryogenic system will provide the cooling at 80 K for all the thermal shields, the 80 K chevron baffles and thermal shields of the cryo-pumps, cryogenic lines, cryogenic cold boxes, liquid helium and quench tanks of the cryogenic system. The cryogenic system will feed and recover warm helium gas at 300 K for conditioning, flushing, or any other maintenance/operation use (such as partial warm-up and cleaning). See details in: SRD-34 (Cryoplant and Cryodistribution) from DOORS (28B323) 5.2 The cryogenic system functional I&C architecture From the latest version of the Control Breakdown Structure (CBS) of the Cryogenic System, four plant system I&Cs are expected for controlling all of the cryogenic system. CRYO CH CA CD MC Figure 5-1: Cryogenic system CBS for level 1 and 2 The CRYO-CH plant system I&C is dedicated to the production of cryogenic cooling power though the CP liquid helium (LHe) and magnet LHe plants. The CRYO-CA plant system I&C is dedicated to the production of cryogenic cooling power though the liquid nitrogen (LN2) Plants 1&2, to the plant for production of the 80 K gaseous helium for loops 1&2 and to the gaseous helium (GHe) purification and drying plant. The CRYO-CD plant system I&C is dedicated to the distribution of cryogenic fluids to the cryogenic system clients at different temperature ranges. The CRYO-MC plant system I&C targets the integrated operation of the CH, CA and CD plant system I&C. CRYO-MC implements the controls required to get all cryogenic system equipment working together, in particular for coupling the cryo-plants to the cryo-distribution, for balancing the cryogenic power and for managing the helium mass inventory throughout the cryogenic system. These controls are cryogenic system specific and are implemented through dedicated functional links between plant system I&Cs. Page 13 of 26

16 5.3 The cryogenic system state machines The document [RD2] provides the specification of inputs suitable for the cryogenic system PSOS SM. The Figure 5-2 shows the functional links between CODAC and CRYO plant system I&Cs for PSOS management: The dark links between CODAC and COS SM are implemented by the CRYO- XX:COS-OPREQ and CRYO-XX:COS-OPSTATE process variables, where XX= LH, MC, CA, CD The blue links between COS SM and PSOS SM are implemented by the CRYO- XX:PSOS-OPREQ and CRYO-XX:PSOS-OPSTATE process variables, where XX= LH, MC, CA, CD The green links between PSOS SM are implemented by CRYO- MC:YY process variables for internal control business inside the Cryogenic System. The YY process variables are TBD by the I&C designer. These links are implemented using PVs over the CODAC infrastructure network, the link specifications are out of scope of this document. CODAC systems CRYO-CH:COS-OPREQ CRYO-CH:COS-OPSTATE CRYO-MC:COS-OPREQ CRYO-MC:COS-OPSTATE CRYO-CA:COS-OPREQ CRYO-CA:COS-OPSTATE CRYO-CD:COS-OPREQ CRYO-CD:COS-OPSTATE COS / PSOS mapping COS / PSOS mapping COS / PSOS mapping COS / PSOS mapping CRYO-CH:PSOS-OPREQ CRYO-CH:PSOS-OPSTATE CRYO-MC:PSOS-OPREQ CRYO-MC:PSOS-OPSTATE CRYO-CA:PSOS-OPREQ CRYO-CA:PSOS-OPSTATE CRYO-CD:PSOS-OPREQ CRYO-CD:PSOS-OPSTATE LHe state machine (PLC) Master control state machine (PLC) 80 K loop state machine (PLC) Cryodistribution (PLC) CH plant system I&C MC plant system I&C CA plant system I&C CD plant system I&C Figure 5-2: Functional links between CODAC and CRYO plant system I&Cs for PSOS management scope only 5.4 COS/PSOS mapping for CRYO-CH plant system I&C CP LHe cool-down CP LHe nominal CP LHe warm-up System stopped Figure 5-3: Simplified representation of state machines for controlling CP LHe and Magnet LHe plants. Magnet LHe cool-down Magnet LHe Ready Magnet LHe nominal Magnet Lhe Warm-up [RD2] provides the inputs for specifying the CRYO-CH PSOS SM. Figure 5-3 gives a simplified representation of what is specified in [RD2] for cryo-pump (CP) LHe plant and the magnet LHe plant states of operation. Relevant CRYO-CH states for PSOS management are: System stopped state reflects that cryopump and magnet LHe plants are in the stop state. Cryo-pump LHe nominal state reflects that the CP LHe ready is for plasma. The cryo-pump LHe plant is static and is not influenced by the plasma pulse sequence. Magnet LHe ready reflects that the magnet LHe plants are ready for plasma operation. Magnet LHe nominal reflects that the magnet LHe plants are in the right state for a plasma pulse. All grey states reflect that the cryo-pump and magnet LHe plants are not ready for plasma operation. Page 14 of 26

17 LHe stopped LHe Not Ready LHe Ready LHe nominal The PSOS SM suitable for CRYO-CH is determined from the description of CRYO-CH states of operation given above, see Figure 5-4. This state machine is implemented in one controller of the CRYO-CH plant system I&C. The corresponding COS states are: Off for LHe stopped, Not Ready, PostChecks, Terminating and Aborting for LHe not Ready. Ready for LHe Ready Initialising, Initialised and Executing for LHe nominal. The COS requests SwitchOn and SwitchOff are not implemented: corresponding state changes are managed manually by the CRYO-CH operator. The PSOS - COS OPREQ and OPSTATE mapping table is given in Table 5-1 Figure 5-4: The CRYO-CH PSOS SM *:COS-OPREQ *:PSOS-OPREQ *:PSOS-OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 LHestopped 1 Off 2 SwitchOn 2 NA 2 LHeNotReady 2 NotReady 3 gotoready 3 gotolheready 3 LHeReady 3 Ready 4 Initialise 4 gotolhenominal 4 LHeNominal 4 Initialising 5 gotoinitialised 5 gotolhenominal 5 LHeNominal 5 Initialised 6 Execute 6 gotolhenominal 6 LHeNominal 6 Executing 7 PostCheck 7 gotolhenotready 7 LHeNotReady 7 PostChecks 8 Terminate 8 gotolhenotready 8 LHeNotReady 8 Terminating 9 Abort 9 gotolhenotready 9 LHeNotReady 9 Aborting 10 Absent 11 gotolocal? 11 NA 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 5-1 PSOS - COS OPREQ and OPSTATE mapping table for CRYO-CH Page 15 of 26

18 5.5 COS/PSOS mapping for CRYO-CA plant system I&C CP 80 K loop cool-down System stopped Magnet 80 K loop cool-down TS 80 K loop cool-down [RD2] provides the inputs for specifying the CRYO-CA PSOS SM. Figure 5-6 provides a simplified representation of what is specified in [RD2] for CA 80 K loops operation. Relevant CRYO-CA states for PSOS management are: System stopped state indicates that all 80 K loops are stopped. 80 K loops nominal indicates that all 80 K loops at right state for plasma pulse. All grey states indicate that all 80 K loops at not ready for plasma operation. 80 K loops nominal Figure 5-6: Simplified representation of state machines for controlling 80 K loops. 80 K loops warm-up 80 K loops stopped 80 K loops Not Ready 80 K loops nominal The PSOS SM suitable for CRYO-CA is determined from the description of CRYO-CA states of operation as given above, see Figure 5-7. This state machine is implemented in one controller of the CRYO-CA plant system I&C. The corresponding COS states are: Off for 80 K loops stopped. Not Ready for 80 K loops not Ready. PostChecks, Terminating, Aborting, Ready, Initialising, Initialised and Executing for 80 K loops nominal. There is no applicable COS request, all PSOS state changes are managed manually by the CRYO-CA operator. Figure 5-7: The CRYO-CA PSOS SM The PSOS - COS OPREQ and OPSTATE mapping table is given in the table 5-2 Page 16 of 26

19 *:COS-OPREQ *:PSOS-OPREQ *:PSOS-OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 80Kloopsstopped 1 Off 2 SwitchOn 2 NA 2 80KloopsNotReady 2 NotReady 3 gotoready 3 NA 3 80KloopsNominal 3 Ready 4 Initialise 4 NA 4 80KloopsNominal 4 Initialising 5 gotoinitialised 5 NA 5 80KloopsNominal 5 Initialised 6 Execute 6 NA 6 80KloopsNominal 6 Executing 7 PostCheck 7 NA 7 80KloopsNominal 7 PostChecks 8 Terminate 8 NA 8 80KloopsNominal 8 Terminating 9 Abort 9 NA 9 80KloopsNominal 9 Aborting 10 Absent 11 gotolocal? 11 NA 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 5-2: PSOS - COS OPREQ and OPSTATE mapping table for CRYO-CA 5.6 COS/PSOS mapping for CRYO-CD plant system I&C [RD2] does not yet provide the inputs for specifying the CRYO-CD PSOS SM. However, Figure 5-8 provides an illustration of what might be proposed as PSOS SM for CRYO-CD. This state machine is implemented in one controller of the CRYO-CD plant system I&C. Cryodistribution stopped Cryodistribution Not Ready Cryodistribution Ready The corresponding COS states are: Off for Cryodistribution stopped, Not Ready, PostChecks, Terminating and Aborting for Cryodisribution not Ready. Ready for Cryodistribution Ready Initialising, Initialised and Executing for Cryodistribution nominal. The COS requests SwitchOn and SwitchOff are not implemented: the corresponding state changes are managed manually by the CRYO-CD operator. The PSOS - COS OPREQ and OPSTATE mapping table is given in Table 5-3 Cryodistribution nominal Figure 5-8: The CRYO-CD PSOS SM Page 17 of 26

20 *:COS-OPREQ *:PSOS-OPREQ *:PSOS- OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 CryodistriStopped 1 Off 2 SwitchOn 2 NA 2 CryodistriNotReady 2 NotReady 3 gotoready 3 gotodistriready 3 CryodistriReady 3 Ready 4 Initialise 4 gotodistrinominal 4 CrydistriNominal 4 Initialising 5 gotoinitialised 5 gotodistrinominal 5 CryodistriNominal 5 Initialised 6 Execute 6 gotodistrinominal 6 CryodistriNominal 6 Executing 7 PostCheck 7 gotodistrinotready 7 CryodistriNotReady 7 PostChecks 8 Terminate 8 gotodistrinotready 8 CryodistriNotReady 8 Terminating 9 Abort 9 gotodistrinotready 9 CryodistriNotReady 9 Aborting 10 Absent 11 gotolocal? 11 NA 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 5-3: PSOS - COS OPREQ and OPSTATE mapping table for CRYO-CD 5.7 COS/PSOS mapping for CRYO-MC plant system I&C [RD2] does not yet provide the inputs for specifying the CRYO-MC PSOS SM. However, Figure 5-9 provides an illustration of what might be proposed as PSOS SM for CRYO-MC. This state machine is implemented in the master controller of the Cryogenic System. Master control stopped Master control Not Ready Master control Ready The corresponding COS states are: Off for Master control stopped, Not Ready, PostChecks, Terminating and Aborting for Master control not Ready. Ready for Master control Ready Initialising, Initialised and Executing for Master control nominal. The COS requests SwitchOn and SwitchOff are not implemented: the corresponding state changes are managed manually by the CRYO-MC operator. The PSOS - COS OPREQ and OPSTATE mapping table is given in Table 5-4. Master control nominal Figure 5-9: The CRYO-MC PSOS SM Page 18 of 26

21 *:COS-OPREQ *:PSOS-OPREQ *:PSOS-OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 MasterCtrlStopped 1 Off 2 SwitchOn 2 NA 2 MasterCtrlNotReady 2 NotReady 3 gotoready 3 gotomasterctrlready 3 MasterCtrlReady 3 Ready 4 Initialise 4 gotomasterctrlnominal 4 MasterCtrlNominal 4 Initialising 5 gotoinitialised 5 gotomasterctrlnominal 5 MasterCtrlNominal 5 Initialised 6 Execute 6 gotomasterctrlnominal 6 MasterCtrlNominal 6 Executing 7 PostCheck 7 gotomasterctrlnotready 7 MasterCtrlNotReady 7 PostChecks 8 Terminate 8 gotomasterctrlnotready 8 MasterCtrlNotReady 8 Terminating 9 Abort 9 gotomasterctrlnotready 9 MasterCtrlNotReady 9 Aborting 10 Absent 11 gotolocal? 11 NA 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 5-4: PSOS - COS OPREQ and OPSTATE mapping table for CRYO-MC Page 19 of 26

22 6 Illustration on a pulsed plant system: EC system 6.1 Introduction to the Electron Cyclotron (EC) system The ECH&CD (EC) system provides localized heating and current drive using high power (between 1 and 2 MW)microwave beams with the location of energy deposition steerable across nearly the entire plasma cross section. The EC system will: Since this is based on specifications which are not yet frozen, the implementation examples for the COS concept are given for illustration purposes only and must not be used as inputs for any other purpose. Provide auxiliary heating to assist in accessing the H-mode, and achieving Q=10. The EC system will provide steady state on-axis and off-axis current drive. Control MHD instabilities by localized current drive Assist initial breakdown and heat during current ramp-up A dedicated feedback control system will be used to control the EC deposition relative to the desired deposition in the plasma for control of magneto-hydrodynamic (MHD) activity and current profile tailoring. There are up to twenty-four 170 GHz gyrotrons to be installed for generating the RF power for heating and current drive (H&CD) applications. All gyrotrons are powered by high voltage power supplies (HVPS) and transmitted via 24 main transmission lines (TL) to either one equatorial or four upper launchers. See details in: SRD-52 (ECH&CD) from DOORS (28B365 v4.0) 6.2 The EC system functional I&C architecture From the latest version of the Control Breakdown Structure (CBS) of the EC system, three plant system I&Cs are planned for the control of the complete EC system: EC-MC, EC-GN and EC-TS, see [RD3] for details. Figure 6-1: EC system CBS for level 1 and 2 The EC-MC management function will be responsible for integrating the operation of entire EC system so that it acts as a coherent unit. The tasks carried out by EC-MC are as follows: Page 20 of 26

23 a) Configuring EC Plant system: EC system units can co-exist in different modes for example some gyrotrons can be in test mode while others are configured to serve plasma. b) High Level State Management: ITER machine states like PSOS will be translated into the required EC system states by the master function and commands sent to the relevant sub functions. c) Pulse Power Profile Configuration: EC Power requirement will be received as a scheduled parameter from either the plasma control system or a dedicated scheduling system. d) Real Time Supervision & Monitoring: In either case, PCS will control the EC system in real time for power, polarization and steering mirror position. The EC master function will act as the interface for receiving such commands from the PCS and then converting them into control group level commands or to further individual (e.g. specific to particular gyrotron) levels if required. The EC-GN function for generation governs the part of EC system which will be responsible for generating the RF power. The principal physical components of the EC that are covered under this function are gyrotron tubes, HVPS and the TL which are coupled to the tubes. The primary role of the EC-GN is to carry out supervisory control of all the sources: the EC-GN determines when and which gyrotrons are to be made ready, switched on or how much power each one them should generate. The tasks carried out by the EC-GN are as follows: a) Configuration: The configuration parameters for individual units, like mode of operation, will be obtained from the EC-MC (management function) and passed on to individual source function blocks acting as gateway. b) Source System High Level Status: the EC-GN system will be responsible for generating a high level/overview type status for the source system. It will collect the key status of each gyrotron/source system from individual source blocks and present the information to the EC operator. c) Pulse Profile Configuration: the EC-GN function will receive the scheduled pulse power profile from the EC-MC on the basis of control group. The profile thus received will be re-computed to obtain a profile for each gyrotron/source. The EC-TS function governs systems closely associated with transmission and launching of the EC beam on to plasma in the vacuum vessel. The components that come under the scope of this function are the transmission lines and its components like RF switches, polarizers and loads. It also manages four upper launchers, the equatorial launcher and ex-vessel auxiliaries like isolation valves and vacuum windows. The tasks carried out by the EC-TS are as follows: a) Configuration Gateway: The state and any configuration commands generated by the EC management function will be received by the EC-TS and then conveyed to the relevant transmission lines and launchers. Similarly the scheduled pulse profile for any steering mirror will reach the relevant launcher function through EC-TS. b) Fast Steering Mirror Supervision: This is for real time applications of the EC system where the mirror position needs to be continuously varied (for example, to track instabilities). The supervisory function of the EC-TS will control the required set point in real time of the relevant launcher after obtaining it from the EC-MC management function. c) Polarizing Supervision: Similar to steering mirror supervision, the EC-TS will also control the polarization required in each beam in real time. d) Key Status Reporting: The EC-TS may collate key information from each launcher and transmission line and present it to the EC management function as well as to the EC CODAC. 6.3 The EC system state machines The documents [RD4] and [RD5] provide the input specifications for the EC system PSOS SM (EC-GN and EC-TS only). Figure 6-2 shows the functional links between CODAC and EC plant system I&Cs for PSOS management: The dark links between CODAC and COS SM are implemented by the EC- XX:COS-OPREQ and EC-XX:COS-OPSTATE process variables, where XX= MC, GN, TS The blue links between COS SM and PSOS SM are implemented by the EC- XX:PSOS-OPREQ and EC-XX:PSOS-OPSTATE process variables, where XX= MC, GN, TS Page 21 of 26

24 The green links between PSOS SM are implemented by the EC- MC:YY process variables for internal control business inside the EC system. The YY process variable are TBD by the I&C designer. These links are implemented using PVs over the CODAC infrastructure network, the link specifications are out of scope of this document. CODAC systems EC-GN:COS-OPREQ EC-GN:COS-OPSTATE EC-MC:COS-OPREQ EC-MC:COS-OPSTATE EC-TS:COS-OPREQ EC-TS:COS-OPSTATE COS / PSOS mapping COS / PSOS mapping COS / PSOS mapping EC-GN:PSOS-OPREQ EC-GN:PSOS-OPSTATE GN state machine EC-MC:PSOS-OPREQ EC-MC:PSOS-OPSTATE Master control state machine EC-TS:PSOS-OPREQ EC-TS:PSOS-OPSTATE TS state machine GN plant system I&C MC plant system I&C TS plant system I&C Figure 6-2: Functional links between CODAC and EC plant system I&Cs for PSOS management scope only 6.4 COS/PSOS mapping for EC-GN plant system I&C STOP Auxiliaries turn on Auxiliaries ready HVPS turn on HVPS ready Gyrotron check Gyrotron ready [RD4] provides the inputs for specifying the EC-GN PSOS SM. Figure 6-3 provides a simplified representation of what is specified in [RD4] for gyrotron control. The relevant EC-GN states for PSOS management are: Stop state indicates that the gyrotron auxiliaries and HVPS are stopped. Auxiliaries turn on, Auxiliaries ready, HVPS turn on, HVPS ready and Gyrotron check are steps which indicate the preparation stages of gyrotrons to be ready for RF. Gyrotron ready indicates that the gyrotron is ready for RF. Trigger HVPS indicates that the RF is initializing. RF ON indicates that the gyrotron RF is on. RFI indicates that there is an RF interrupt for failure (arc) recovery. The PSOS SM suitable for EC-GN is determined from the description of the state of operation above, see Figure 6-4. This state machine is implemented in one controller of the EC-GN plant system I&C. Trigger HVPS RF ON Figure 6-3: Simplified representation of state machines for controlling the gyrotrons RFI Page 22 of 26

25 STOP Gyrotron not ready Gyrotron ready Trigger HVPS RF ON The corresponding COS states are: Off for Stop. Not Ready for Auxiliaries turn on, Auxiliaries ready, HVPS turn on, HVPS ready and Gyrotron check. These gyrotron states are merged in scope of the PSOS state machine as Gyrotron not ready. Ready for Gyrotron ready. Initializing for Trigger HVPS. Executing for RF ON and RFI. Note that the case of interruption of the Executing COS is not introduced in the current version of the COS model. Therefore the RFI state is not introduced in the PSOS state machine. Figure 6-4: The EC-GN PSOS SM The COS requests SwitchOn and SwitchOff are not implemented: the corresponding state changes are managed manually by the EC operator. The PSOS - COS OPREQ and OPSTATE mapping table is given in Table 6-2 *:COS-OPREQ *:PSOS-OPREQ *:PSOS-OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 Stop 1 Off 2 SwitchOn 2 NA 2 GyrotronNotReady 2 NotReady 3 gotoready 3 GotoGyrotronReady 3 GyrotronReady 3 Ready 4 Initialise 4 GototrigHVPS 4 TriggerHVPS 4 Initialising 5 gotoinitialised 5 GototrigHVPS 5 TriggerHVPS 5 Initialised 6 Execute 6 GotoRFON 6 RFON 6 Executing 7 PostCheck 7 GotoGyrotronNotReady 7 GyrotronNotReady 7 PostChecks 8 Terminate 8 GotoGyrotronNotReady 8 GyrotronNotReady 8 Terminating 9 Abort 9 GotoGyrotronNotReady 9 GyrotronNotReady 9 Aborting 10 Absent 11 gotolocal? 11 NA 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 6-2: PSOS - COS OPREQ and OPSTATE mapping table for EC-GN Page 23 of 26

26 6.5 COS/PSOS mapping for EC-TS plant system I&C SUL STOP Auxiliaries stand by Auxiliaries ready SDL SUL [RD5] provides the inputs for specifying the EC-TS PSOS SM. Figure 6-5 provides a simplified representation of what is specified in [RD5] for transmission line control. THE relevant EC-TS states for PSOS management are: Stop state indicates that all the transmission line components and auxiliary services from other ITER plant systems are off. Auxiliaries stand by state indicates that the vacuum generation system is turned on. The switches are in the default position. Auxiliaries ready indicates that continuous cooling of the transmission line, dummy load and other components will be carried out in this state SDL indicates that the TL switches are configured in the correct position for an RF pulse. SEL indicates that the transmission line is configured for the equatorial launcher. SUL indicates that the transmission line is configured for the upper launcher. Figure 6-5: Simplified representation of state machines for controlling the gyrotrons The PSOS SM suitable for EC-TS is determined from the description of the state of operation above, see Figure 6-6. This state machine is implemented in one controller of the EC-TS plant system I&C. STOP TL not ready TL ready The corresponding COS states are: Off for Stop. Not Ready for Auxiliaries stand by, Auxiliaries ready and SDL, HVPS ready. These transmission line states are merged in scope of the PSOS state machine as TL not ready. Ready, Initialising, Initialised and Executing for TL ready. Figure 6-6: The EC-GN PSOS SM The COS requests SwitchOn and SwitchOff are not implemented: the corresponding state changes are managed manually by the EC operator. The PSOS - COS OPREQ and OPSTATE mapping table is given in Table 6-3 Page 24 of 26

27 *:COS-OPREQ *:PSOS-OPREQ *:PSOS-OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 Stop 1 Off 2 SwitchOn 2 NA 2 TLnotReady 2 NotReady 3 gotoready 3 GotoTLReady 3 TLReady 3 Ready 4 Initialise 4 GotoTLReady 4 TLReady 4 Initialising 5 gotoinitialised 5 GotoTLReady 5 TLReady 5 Initialised 6 Execute 6 GotoTLReady 6 TLReady 6 Executing 7 PostCheck 7 GotoTLnotReady 7 TLnotReady 7 PostChecks 8 Terminate 8 GotoTLnotReady 8 TLnotReady 8 Terminating 9 Abort 9 GotoTLnotReady 9 TLnotReady 9 Aborting 10 Absent 11 gotolocal? 11 NA 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 6-3: PSOS - COS OPREQ and OPSTATE mapping table for EC-TS 6.6 COS/PSOS mapping for EC-MC plant system I&C STOP EC not ready EC ready At the time of editing this version of the document, the specifications of the EC-MC state machine are not complete. Anyway, it is assumed the PSOS state machine applicable to the EC-MC reflects the standard COS state machine with the following mapping of COS and PSOS: Off indicates EC Stop. Not Ready indicates EC under preparation Ready for EC ready. Initializing for Trigger HVPS. Executing for RF ON and RFI. Trigger HVPS RF ON The COS requests SwitchOn and SwitchOff are not implemented: the corresponding state changes are managed manually by the EC operator. The PSOS - COS OPREQ and OPSTATE mapping table is given in Table 6-4 Page 25 of 26

28 *:COS-OPREQ *:PSOS-OPREQ *:PSOS-OPSTATE *:COS-OPSTATE 1 SwitchOff 1 NA 1 Stop 1 Off 2 SwitchOn 2 NA 2 ECnotready 2 NotReady 3 gotoready 3 GotoECReady 3 ECready 3 Ready 4 Initialise 4 GototrigHVPS 4 TriggerHVPS 4 Initialising 5 gotoinitialised 5 GototrigHVPS 5 TriggerHVPS 5 Initialised 6 Execute 6 GotoRFON 6 RFON 6 Executing 7 PostCheck 7 GotoECnotReady 7 ECnotReady 7 PostChecks 8 Terminate 8 GotoECnotReady 8 ECnotReady 8 Terminating 9 Abort 9 GotoECnotReady 9 ECnotReady 9 Aborting 10 Absent 11 gotolocal? 11 NA 11 StateLocal? 11 Local 12 StateFault 12 Fault 13 gotosafe? 13 gotostatesafe? 13 StateSafe? 13 Safe Table 6-4: PSOS - COS OPREQ and OPSTATE mapping table for EC-MC Page 26 of 26