<?xml version="1.0" encoding="utf-8"?>
<Spec id="279" path="\1\d\1d4f8146b57240b6453ca31cd71e0945.pdf"><Text id="36577" page="6">The purpose of this document is to describe the technical and functional requirements for the Automation system for the MFW . The content of this document describes the requirements for the</Text><Text id="36578" page="6">This document provides the overall design criteria for the Industrial Automation and Control System (IACS) and shall form the basis for the functional design specifications for IACS sub-systems, including Supervisory Control and Data Acquisition (SCADA) systems, with the required interfaces to all other related systems and external interfaces. Fiscal metering and TSO communication needs to be clarified and agreed with TSO</Text><Text id="36579" page="6">Reference is made to Design basis MFW – PM735-PMS-050-001</Text><Text id="36580" page="6">The design and operation of the entire Wind Power Plant (WPP) shall be demonstrated to be in accordance with all applicable laws, rules and regulations as required by the regulatory authorities, including but not limited to, Contract Appendix E document.</Text><Text id="36581" page="6">It is the Contractor’s responsibility to ensure that the design, material, and equipment provided meets all relevant requirements.</Text><Text id="36582" page="6">Contractor shall indicate in their proposal if any part of this specification deviates from Contractor’s usual design so that a significant increase in the cost is expected without providing a corresponding increase in quality; or if Contractor’s usual design will provide better quality than the design required by this specification.</Text><Text id="36583" page="6">Contractor shall ensure that the design incorporates HSE best practices and gained experiences so that construction, testing, installation, maintenance, and normal production activities can be carried out in an efficient manner, and without risk to people, environment, or the asset.</Text><Text id="36584" page="6">All engineering, design and construction covered by this specification shall be in line with relevant Polish Laws and Regulations and practices applicable for the offshore wind sector.</Text><Text id="36585" page="6">For roject specific design requirements towards Polish Transmission System Operator (TSO) is defined in the Grid Connection Agreements between TSO and , Technical Conditions for the Connection to the Telecommunication Network of PSE S.A., Grid Code and any other relevant TSO requirements for Telecommuncation systems.</Text><Text id="36586" page="7">Contractor shall be responsible to ensure and document that its products are designed in accordance with applicable laws, regulations, standards given in App E of the Contract.</Text><Text id="36587" page="7">If there are inconsistencies between the various requirements given within the regulations, requirements, and standards, reference is made to the contractual Order of Precedence.</Text><Text id="36588" page="7">The wind power plant shall be built for unmanned operation. This shall include the Onshore Substation (ONS), Offshore Substation (OSS) and Wind Turbine Generators (WTGs). It shall be possible to control and monitor the Wind Power Plant (WPP) from remote sites, including e.g. utility systems.</Text><Text id="36589" page="7">The WPP shall have an integrated automation system for supervision, control and monitoring of the Wind Farm including ONS, OSS, WTGs and cable monitoring. The automation system shall control utilities, or interface third party utility control systems supplied by package suppliers such as HVAC, UPS, etc. The overall automation system for is denoted Industrial Automation and Control System (IACS), see section 3 for further details.</Text><Text id="36590" page="7">The control system and electrical HV Control &amp; Protection system/ equipment, MV, LV equipment/systems and utility equipment/systems for ONS / OSS and the WTGs shall be remotely operated and controlled from the Multi wind farm Central Control Room (CCR), located at the O&amp;M base.</Text><Text id="36591" page="7">The IACS system in the wind farm shall be designed with three levels of control.</Text><Text id="36592" page="7">1. Remote Control from CCR at O&amp;M base</Text><Text id="36594" page="7">• The Control Room on the ONS shall serve as a backup for the CCR and the ONS Station control must therefore be designed with necessary facilities to accommodate this.</Text><Text id="36595" page="7">• Local control of substations equipment (CB (Circuit Breakers), Disconnector, earth switch etc)</Text><Text id="36596" page="7">The control philosophy with different control levels shall be described and detailed during the detail engineering phase.</Text><Text id="36597" page="7">The SCADA control and monitoring system for the wind farm including ONS, OSS and WTGs shall be designed for unmanned operation and remote maintenance. A Power System Philosophy will be developed by Contractor’s power consulting team, and shall be the base for the power control and protection system.</Text><Text id="36598" page="7">1. Remote control and monitoring of all systems from CCR at O&amp;M Base</Text><Text id="36599" page="8">2. All SCADA PCs and servers (both physical and VM (Virtual Machine)) are available via a remote access solution for remote operation</Text><Text id="36600" page="8">3. All equipment located in normally unmanned locations can be remotely reset from HMI</Text><Text id="36601" page="8">4. No SCADA HMI PC on wind turbines. Service technicians will require a mobile solution including dedicated port (RJ45-socket) on the SCADA network switch for local monitoring and control.</Text><Text id="36602" page="8">It shall be possible to perform remote troubleshooting, diagnostics, SW updating/modification/changes of all programmable monitoring and control devices/units, sub systems, database system/servers, Client workstation remotely via dedicated servers and Engineering workstations both locally and from the O&amp;M Base CCR via Company secure access solution. This also includes third-party control systems for utilities</Text><Text id="36603" page="8">It shall be possible to modify and change set-points, alarms and reset alarm, alarm inhibits/suppressions on any devices remotely from CCR either from Operator Station (OS) or from Engineering Workstations (EWS) Human Machine Interfaces</Text><Text id="36604" page="8">(HMIs). Different roles/accesses to operate the WF, to do HV switching, operation of ESI / WTG or both, change parameters/setpoints shall be defined.</Text><Text id="36605" page="8">The IACS, SCADA, Control and protection system, Instrumentation and local control systems shall be designed to provide safe, reliable, and efficient operation of the wind farm. This shall include the following:</Text><Text id="36606" page="8">• Redundant design of the component/system listed here: o Network o Individual equipment assemblies. Including electrical power supplies. o Connection to Local Control Units (LCUs)/Intelligent Electrical Devices (IED’s).</Text><Text id="36607" page="8">Network infrastructure must be setup for this purpose i.e., network to be available and WAN connection to be established.</Text><Text id="36608" page="8">The SCADA systems, control &amp; protection system/equipment including necessary network shall be fully redundant and a fail- safe philosophy shall be evaluated and defined for all related equipment, network, and critical signals.</Text><Text id="36609" page="8">The is designed with one OSS each, which has two separate “production trains”. The two trains shall be functionally segregated to the extent that one may be taken out of service for maintenance whilst the other is fully operational. This concept shall be reflected in the IACS design.</Text><Text id="36610" page="8">In case of equipment failure or communication failure, the system and equipment shall move to a predefined safest state with regards to the severity of the failure. The IACS shall have robust and fault tolerant protocols for the dual redundant communication network. The IACS shall have intuitive alarms and diagnostics tools for the communication network.</Text><Text id="36611" page="8">SCADA firewalls shall be included with required function and software for remote monitoring and management/control by Company.</Text><Text id="36612" page="8">The SCADA data system servers shall be capable of collecting real time, historical Open database Connectivity (ODBC) and analysed data from all systems. The data shall be available on trend displays and for forwarding of all data to Company Information Management System (IMS) via the office LAN for transmission to land organizations.</Text><Text id="36613" page="8">SCADA clients shall be available at the ONS (backup for CCR), OSS, and CCR.</Text><Text id="36614" page="8">Required engineering and service workstation shall also be installed at same locations and shall be accessible via Company secure access service.</Text><Text id="36615" page="8">Fiber optic connections embedded into the two export cables shall be provided for redundant communication between ONS and offshore substations.</Text><Text id="36616" page="8">External WAN data lines for communication to Company sites shall be based on redundant fiber optical network and preferably MPLS-TP.</Text><Text id="36617" page="9">All systems on shall have a uniform, consistent and standardized design. This applies to all aspects of system design, including both hardware (cabinet design, cabling etc), software (user interfaces etc), condition monitoring capabilities and so on.</Text><Text id="36618" page="9">All relevant real-time data shall be made available to the Company IMS/Wind Farm Management System. This shall include both raw and analysed data from all SCADA systems. Raw data shall be available without any filtering or compression, via agreed interface protocols. Definition of “all relevant real-time data” shall be detailed during the detail engineering phase and agreed with Company.</Text><Text id="36619" page="9">Both raw and analysed data shall include historical records, plus data from SCADA and Control and Protection systems, monitoring systems, database system, Conditioning Monitoring systems (CMS) Metering Systems, etc. Data shall flow from the source systems directly to the company IMS buffer servers on the company network without leaving and re-entering the Company network. Data transfers should, unless agreed with Company, occur continuously and with minimal delay.</Text><Text id="36620" page="9">The automation systems, including ESI SCADA, WTG SCADA and SUS SCADA (if not integrated part of ESI SCADA) shall have OPC UA interface to a future Top Level/Common SCADA in the CCR for operation of the windfarm. The WTG SCADA for could be combined, the ESI SCADA for could be combined and the SUS SCADA (if not integrated part of ESI SCADA) could be combined for . Top Level/Common SCADA will probably not be made until B is built. This to be clarified with Company during FEED.</Text><Text id="36623" page="10">The interface shall support OPC UA companion specification OPC 10040 - UA for IEC 61850 for monitoring and operation of the lED&apos;s exposing the information models to the above systems. In addition, the interface shall support other relevant OPC UA companion standards for non-IED equipment in the ESI systems exposing the information models to the above systems. The information model shall be inclusive of alarms and events.</Text><Text id="36624" page="10">The OPC UA interface should as a minimum support the following features:</Text><Text id="36625" page="10">A. OPC UA clients shall support the &quot;Standard UA Client 2017 Profile&quot; (http://opcfoundation.org/UA- Profile/Client/Standard2017).</Text><Text id="36626" page="10">B. OPC UA clients shall support the &quot;Documentation - Client&quot; profile (http://opcfoundation.org/UA-Profile/Client/Documentation).</Text><Text id="36627" page="10">C. OPC UA clients shall support the &quot;Base Client Behaviour Facet&quot; profile (http://opcfoundation.org/UA- Profile/Client/Behaviour)</Text><Text id="36628" page="10">D. OPC UA clients shall support the &quot;Reverse Connect Client Facet&quot; profile (http://opcfoundation.org/UA- Profile/CIient/ReverseConnect)</Text><Text id="36629" page="10">E. OPC UA servers shall support the &quot;Standard UA Server 2017&quot; profile&quot; (http://opcfoundation.org/UA- ProfiIe/Server/Sta ndardUA 2017).</Text><Text id="36630" page="10">F. OPC UA servers shall support the &quot;Data Access Server Facet” profile (http://opcfoundation.org/UA- Profile/Server/DataAccess)</Text><Text id="36631" page="10">G. OPC UA servers shall support the &quot;Documentation - Server&quot; profile (http://opcfoundation.org/UA- Profile/Server/Documentation).</Text><Text id="36632" page="10">H. OPC UA servers shall support the &quot;Base Server Behaviour Facet&quot; profile (http://opcfoundation.org/UA- Profile/Server/Behaviour).</Text><Text id="36635" page="10">Doc. No. C256-EQ-J-SP-OOOO2 Rev. no. 01 Valid from: 12.12.2022</Text><Text id="36636" page="10">Multi Wind Farm Central Control Room (CCR) Multi Wind Farm CCR SCADA System</Text><Text id="36638" page="10">Windfarm Automation System ESI Automation System Wind Turbine Automation System</Text><Text id="36641" page="10">Safety &amp; UtMtty System Sutotatlon Automaton Electrtcal System WTG System</Text><Text id="36642" page="10">I. OPC UA servers shall support the &quot;Reverse Connect Server Facet&quot; profile (http://opcfoundation.org/UA- Profile/Server/ReverseConnect) K</Text><Text id="36643" page="11">J. OPC UA client shall support the “Alarm &amp; Condition Server Facet” profile http://opcfoundation.org/UA-Profile/Client/ACBaseCondition</Text><Text id="36644" page="11">K. OPC UA server shall support the “Alarm &amp; Condition Server Facet” profile http://opcfoundation.org/UA-Profile/Server/ACBaseCondition2021</Text><Text id="36645" page="11">The OPC UA interface should support the following feature: OPC UA clients should support the “Pub/Sub facet” OPC UA servers should support the “Pub/Sub facet”</Text><Text id="36646" page="11">An overall Automation and Control System shall be installed for monitoring and control of the wind farm. For the IACS shall comprise one or more of the following components: Industrial control systems, including but not limited to distributed control systems (DCSs), programmable logic controllers (PLCs), remote terminal units (RTUs), Intelligent Electronic Devices (IEDs), Supervisory Control and Data Acquisition (SCADA) systems, network components, networked electronic sensing and control, and monitoring and diagnostic systems. All systems designated for operational use shall be compliant for real-time monitoring and control. The ESI SCADA shall therefore be designed with complete functionality for real-time monitoring, and for control of all electrical and utility equipment on the ONS/OSS. The control system shall be compliant with the IEC 61850 standard for substation automation and support other standard communication protocols as listed in chapter 6.1.6.</Text><Text id="36647" page="11">Figure 1 - IACS General Architecture gives a general overview of the IACS and does also indicate main interfaces towards systems and parties external to IACS. Please note that the outline of the IACS is only functional, hence not necessarily reflecting location or the Automation network topology correctly.</Text><Text id="36648" page="11">The objective of the IACS is to control and monitor the power generation, the electrical power distribution network, and auxiliary systems.</Text><Text id="36649" page="11">The IACS shall control and monitor the 400/220 kV switchboards, HV, MV and LV and all auxiliary equipment on the ONS, and controlling the 220/66 kV switchboards, HV, MV and LV and all auxiliary equipment on OSS including 66kV inter array cable incomers from the WTGs, with required signals and set point to/from the WTG SCADA Plant Control/Wind Farm Power Control (WFPC) system.</Text><Text id="36650" page="11">The ESI SCADA shall also control and monitor the WTG 66 kV switchgear in the WTGs via the IEC 61850 network.</Text><Text id="36651" page="11">The IACS shall in basis consist of the following systems:</Text><Text id="36652" page="11">• ESI SCADA performing Supervisory control and monitoring of the high voltage distribution, medium voltages and low voltage distribution system and transmission system from the high voltage connections in the WTGs.</Text><Text id="36653" page="11">• High Voltage Control &amp; Protection system including control equipment for:</Text><Text id="36654" page="12">Doc. No. C256-EQ-J-SP-00002 Rev.no. 01 Valid from: 12.12.2022</Text><Text id="36655" page="12">o Onshore 400/220 kV high voltage substation switchgear and other high voltage components, transformers, reactors etc. o Offshore 220 kV /66 kV high voltage substation switchgears and other high voltage components, transformers, reactors etc. o 66 kV inter array cable distribution system, including 66 kV WTG switchgear and the 66/0,690kV WTG transformer.</Text><Text id="36656" page="12">• ONS auxiliary system/equipment including but not limited to Low Voltage switchgears/distribution system, power supplies, battery systems, UPS, fire detection, HVAC systems as needed to obtain remote capabilities to the SCADA system</Text><Text id="36657" page="12">• OSS Safety and Utility automation system (SUS SCADA), including, but not limited to: o Shutdown System o Fire (and Gas) detection o Protection systems o Auxiliary and Utility systems o Low Voltage switchgears/distribution system and UPS&apos;s o HVAC control system o Intruder system</Text><Text id="36658" page="12">• WTG SCADA performing Supervisory control, monitoring of the WTGs, and controlling Active Power (MW) and Reactive Power (MVAr) from the WTGs.</Text><Text id="36659" page="12">• Interface between ESI SCADA and WTG SCADA/WFPC for power control of the WTGs in the Wind Farm.</Text><Text id="36660" page="12">• ESI SCADA HMI systems including operator and engineering workstation remote monitoring and control of the wind farm electrical system infrastructure, including remote monitoring and control of OSS SUS.</Text><Text id="36661" page="12">• WTG SCADA HMI systems including operator and engineering workstation for remote monitoring and control of the WTGs including remotely controlled medium voltage breaker at 690V side of WTG transformer, if poss. This to be further detailed in FEED.</Text><Text id="36662" page="12">• Interface to Information Management System (IMS) for data acquisition from the above systems.</Text><Text id="36663" page="12">• Interface to TSO for inter-tripping, monitoring and metering.</Text><Text id="36665" page="12">• Interface to Condition Monitoring System (CMS), including WTG Main Bearing CMS system.</Text><Text id="36666" page="12">• Interface to cable monitoring systems, such as Distributed Temperature Sensing (DTS) and similar.</Text><Text id="36667" page="12">• Interface to telecommunication systems (WTG WAN, Wifi, Telephony system, TMS, CCTV, Met-Ocean, GPS Clock system, Access Control, Intruder system, PVTS, radio and /radar systems).</Text><Text id="36669" page="12">• TCP/IP based interface to WTG Contractors Navigation and aviation aid system (Sabik)</Text><Text id="36670" page="12">• Interface to WTG Contractors Fleet leader systems (SiDAC in Baltyk) on two WTGs.</Text><Text id="36671" page="12">A dedicated and redundant PRP control and protection network utilizing the IEC 61850 protocol for the control &amp; protection shall be established. IEDs for control and monitoring function shall be implemented. Control &amp; Protection systems and related equipment&apos;s shall support PRP network, IEC61850 MMS and GOOSE communication.</Text><Text id="36672" page="12">400/220/66kV switchboard and LV transformer incomers shall be connected to the IEC61850 network for control and protection. The local control units (LCU) and protection relays/IE Os shall be integrated to the SCADA system via agreed interface/communication protocol. IEC 61850 GOOSE shall be used for intertrip and permissive signals, hardwired interlocks/intertrips shall be limited to what is strictly necessary.</Text><Text id="36673" page="12">Local Control Units (LCU) shall provide fully integrated monitoring functions of all 400/220/66 kV switchgear within the wind farm, e.g., circuit breaker, disconnector, earth switch, 3-pos-switch, etc. The LCU shall allow the operator to control switchgear locally at the relay or remotely from the SCADA.</Text><Text id="36674" page="13">Protection relays provide fully integrated protection functions of all 400/220/66 kV circuits within the wind farm. The protection relays also provide monitoring and control functionality for all the WTG 66 kV switchgear. These shall be controlled from the ESI SCADA system.</Text><Text id="36675" page="13">Required inter tripping signals shall be included for tripping of the circuit breakers for stop of the production and protection of equipment and export cable including soft stop and/or Hard stop of the WTG’s/400kV grid circuit breakers in compliance with TSO Operational Tripping Schemes (OTS).</Text><Text id="36676" page="13">Arming, disarming and reset functions shall be included from the ESI SCADA HMI, according to TSO.</Text><Text id="36677" page="13">All required HW, SW and functions shall be included for local and remote maintenance access, diagnostic, trouble shooting and SW updating via the Company secure access solution. The foregoing is applicable for all programmable and configurable equipment. Contractor to ensure all Sub Suppliers meet this requirement.</Text><Text id="36678" page="13">The three main parts of the “power supply chain” in are;</Text><Text id="36679" page="13">• The WTGs – the offshore wind turbines and the cables between the WTGs and the OSS.</Text><Text id="36680" page="13">• The transmission system - consisting of the OSS, ONS, HV cables between the two, and the interconnection to the grid</Text><Text id="36681" page="13">• The grid – TSO receiving the power from . This is owned by an external party; Company does therefore not have any control over the grid. The IACS shall comply with the TSO Manuals, such that grid-related control and status signals can be sent and received. Fiscal metering must also be incorporated.</Text><Text id="36682" page="13">For these three parties to work efficiently together, it is necessary to exchange some crucial information and act in a timely manner based on the information. The main objectives are to</Text><Text id="36684" page="13">2) Handle de-loading and inter-tripping efficiently and reliably, and finally,</Text><Text id="36685" page="13">3) Ensure the technical integrity of the wind farm is not compromised. The power control requirements will be described in the Power System Philosophy and shall be basis for the Power Control philosophy and design.</Text><Text id="36686" page="13">Power Control From the grid there is a requirement to not provide more active power (MW) at any given time than the grid can handle. Normally the grid can handle full production, but during maintenance of power lines onshore and high amount of wind a need to limit the active power produced may be informed by the TSO. To ensure grid compliance the reactive power control shall use voltage and reactive power reference at POI. The reactive power support requirement is specified in the grid code and the system shall be designed accordingly. TSO may, in special operation scenarios, specify how reactive power shall be controlled, by providing a reference value for voltage, reactive power or power factor at POI. The Power Control system shall be suited for different power control modes to enable input from TSO and manual input of set points. The concept for reactive power control shall be in line with the Projects Grid Connection Conditions and shall be agreed with the TSO.</Text><Text id="36687" page="13">De-load and inter-tripping; Under certain operational scenarios the grid owner may need to rapidly reduce the power production from the wind farm. In this situation the wind farm must be able to efficiently and reliably de-load as required by the grid owner. Should the required de-loading not be executed sufficiently fast, a trip shall be initiated according to a pre- defined inter-tripping scheme agreed with TSO.</Text><Text id="36688" page="13">1) Technical integrity; During operation of the wind farm there will be a limited number of pre-defined operational scenarios, sometimes referred to as Configurations and Topologies. Configuration means a clearly defined combination of open and closed HV breakers, and thereby a defined set of transformers, reactors, and WTGs in operation. Different Configurations may require different needs of support from the WFPC units. Topology is a term used by the WTG Contractor for identifying scenarios where a sub-set of WTGs may be controlled by another WFPC</Text><Text id="36690" page="14">Functions: Run each WTG as per received set point</Text><Text id="36691" page="14">Figure 2 Power Control, Interlocks and Grid Compliance. ESI Power control to be delivered by ESI contractor. WFPC and WTG controllers are WTG delivery.</Text><Text id="36692" page="14">The purpose of EPC is to receive external information from the TSO, in addition to information from within the Wind Farm. The information is typically MW, MVAr references, de-load/intertrip requests and so on from the TSO, as well as HV breaker status, transformer/reactor status, power production and export cable temperature from within the Wind Farm. Based on this information the EPC shall determine the optimized power production. The other main task for the EPC is to maintain an overview of the current topology based on the current status of all relevant equipment.</Text><Text id="36694" page="14">than then normal one. If for instance a transformer on the OSS is inoperable and a bus-tie breaker is closed to reroute power towards the grid on-shore, the power generated by a set of WTGs may now be routed in such a way that it is measured by another WFPC module than before. Such change of Topology required a Topology change sequency to be performed before resuming operation to inform the WFPC about the change in WTGs under its measurement and control.</Text><Text id="36695" page="14">For some pre-defined scenarios there can be limitations to permitted power production to prevent overloading components (e.g., cables &amp; transformers). Rerouting power by opening and closing of HV breakers in the system often means changing from one Topology or Configuration to another. A Topology Change procedure must be developed for the project since it involves informing the WFPC system about which WTGs are under which WFPC units&apos; control. The procedure shall define the necessary steps to be performed by operators in ESI Scada HMI, and for a given topology the system may be permitted only to change to a few other topologies, e.g., if the operator attempts to change to a topology for which there is insufficient capacity in transformers or export cables, they will be warned that this is an invalid topology.</Text><Text id="36696" page="14">These three functions are implemented in a common interface where the ESI Power Controller (EPC) and the Wind Farm Power Controllers (WFPC) are the main units at the side. The number and location of the EPCs and WFPCs necessary to implement reliable, maintainable, and safe solutions shall be assessed as part of the overall system design.</Text><Text id="36697" page="14">Figure 2 gives a high-level overview of the functional split between the different controllers, as well as the signals exchanged between them.</Text><Text id="36698" page="14">Assess topology and limitations based on all inputs</Text><Text id="36699" page="14">■ Decide Wind park set points (MW, Mvar)</Text><Text id="36701" page="14">Functions: Optimize WTG usage based on Wind Park set point Calculate set point for each WTG</Text><Text id="36702" page="15">The purpose of the WFPC is to adjust the Wind Farm power production according to the demand dictated by TSO, and within the limits dictated by the ESI Power Controller. Based on the set points received from the ESI Power Controller, the WFPC shall give set points to each WTG in operation to meet the overall requirement for MW and MVAr while still adhering to the limitations.</Text><Text id="36703" page="15">Further details of the different controllers and interfaces are described in the following sections.</Text><Text id="36704" page="15">A separate Power Control system philosophy describing the required topologies, tripping schemes and interfaces between the ESI SCADA, the WFPC and TSO for Grid Compliance shall be developed. Also, Power Control functional drawing and equipment scope drawing showing the entire windfarm shall be made, by collecting input from TSO, WTG and OSS.</Text><Text id="36705" page="15">The Wind Farm Power Controller (WFPC) shall be installed by the WTG supplier for control of the reactive and active power from the WTG’s. For SGRE WFPC is normally referred to as High Performance Park Pilot (HPPP).</Text><Text id="36706" page="15">The wind farm shall be designed to operate and be energized under different operation scenarios without overloading the plant.</Text><Text id="36707" page="15">The WFPC shall be able to receive various active power limiting “runback signals” from the Wind Farm Electrical System Infrastructure, e.g., bus tie circuit breaker position indication, external run back signals from grid operator, fault indications on transformer breakers etc. and take action by reducing total wind farm power output according to the new condition in the wind farm. The runback signal with the lowest power limiting shall have priority over runback signals with less reduction in allowable power production.</Text><Text id="36708" page="15">The intertrip/ run back signals from TSO control centre shall have duplicated communication routes between the POI and ONS. TSO intertrip shall have priority above all other intertrip signals, as long as the isolation of a fault is according to relevant electrical system studies, to ensure the safest intertrip scheme for every fault cause and location. This will be specified in the Power System Philosophy.</Text><Text id="36709" page="15">To perform required power control the interface signals per WFPC /Balancing mechanism units (BMU) must be included, such as: MW and MVAr references, MW measurements, MW and MVAr Set point, MW production, MW at Grid entry point, De- load request, Breaker configuration/constellation, and voltage measurements to be included and presented on the ESI SCADA HMI.</Text><Text id="36710" page="15">Required Trip and De-load signals shall be included as defined by TSO requirements.</Text><Text id="36711" page="15">It is the responsibility of the Contractor to coordinate the WFPC settings with the ESI system so that the overall integrity of the power system is not degraded. The WFPC shall have functionality supporting the different possible operating modes of the WTGs</Text><Text id="36712" page="15">A Function design document, equipment scope and cause and effect scheme shall be developed showing all exchanging signals with ESI SCADA.</Text><Text id="36713" page="15">Required functions, logic, interlocks, control of the different breaker positions/constellation, topologies and operation limits shall be included to maintain the active power and reactive power needed within defined limits to ensure the primary plant is not overloaded and the compliance to the grid code is met.</Text><Text id="36714" page="15">To fulfil this requirement a dedicated ESI Power Controller (EPC), for single point of contact with the WTG WFPC, shall be included for handling automatic verification of different topologies for the “Grid Code” Compliance towards TSO. Required</Text><Text id="36715" page="16">• The functionality to be implemented in the EPC for grid code compliance will be described in the Power System</Text><Text id="36716" page="16">topologies/logic, trip, and de-load signals (Soft stop), breakers status and control signals (MW, MVAr setpoints) shall be implemented between the EPC and the WFPC. Alternatives to a PLC-based implementation may be accepted by Company provided it can be documented that reliability, maintainability and uptime is comparable to the PLC.</Text><Text id="36717" page="16">The purpose of the EPC is to automate the response regarding power flow in each export cable dependent on a set of operational modes, scenarios (contingencies) and topologies/breaker constellations for the ONS and OSS.</Text><Text id="36718" page="16">Philosophy, and shall be followed. The main functionality shall be: o Power limitation dependent of operating scenario and a defined set of power limitation inputs (onshore/offshore) o Reactive power setpoint as a function of active power output and operational scenario.</Text><Text id="36719" page="16">The wind farm may be energized to operate under any of the above configurations by the operating personnel.</Text><Text id="36720" page="16">Depending on the configuration, the active power and reactive power needs to be maintained within defined limits to ensure the primary plant and component limits are not exceeded and the agreed compliance for the specific scenario to the grid code is met. To meet this functionality the required topologies and logic shall be implemented in dedicated controllers – the EPC and WFPC.</Text><Text id="36721" page="16">The ESI Power Controller shall include all relevant functionality to comply with the Power System Philosophy. It will include, but not limited to, the following:</Text><Text id="36722" page="16">• Receive WTG 66kV switchgear configuration information from the IEDs monitoring the WTG 66kV switchgears.</Text><Text id="36723" page="16">• Receive offshore 66 kV switchgear configuration information from the IEDs monitoring the switchgear.</Text><Text id="36724" page="16">• Receive onshore 220 kV switchgear status information, receive necessary measurements from WTG and ESI SCADA.</Text><Text id="36725" page="16">• Use reactive power controller at POI to give feedback to STATCOM to ensure the voltage and reactive power delivered is within the given limits in the Grid Code.</Text><Text id="36726" page="16">• Use active power controller at POI to give feedback to the WTG production to ensure the frequency and active power delivered is within the given limits in the Grid Code.</Text><Text id="36727" page="16">• Use the WTG and offshore 66 kV circuit breaker configuration and onshore 220 kV switchgear status information and measurements to provide the MW and MVAr set points to WFPC to ensure optimized compensation of the 220kV export cables.</Text><Text id="36728" page="16">• Utilise the CTS/DRS/DTS information to reduce the loading on the export cable when required.</Text><Text id="36729" page="16">• Detect and prevent invalid topologies and fault operation.</Text><Text id="36730" page="16">• Raise an alarm and/or initiate interlocks if the operator prepares to run the wind farm into a configuration which is not permitted.</Text><Text id="36731" page="16">Modes of operation and limitation scenarios shall be included. The below table indicate some examples, based on previous experience. It is the responsibility of the Contractor to develop the required modes for operation and limitations scenarios applicable to according to the project specific Power System Philosophy.</Text><Text id="36732" page="17">• Raise alarm and suggest a safe reconfiguration of the network in case an EAT (including 66kV earth reference point) at OSS is lost</Text><Text id="36733" page="17">• Either automatically and/or manually from the O&amp;M Base CCR execute de-loading of the wind farm, based on instruction from TSO.</Text><Text id="36734" page="17">• Either automatically and/or manually curtail the MW output of the wind farm if required.</Text><Text id="36735" page="17">• Raise an alarm, de-load and/or trip if the overall control interface fails.</Text><Text id="36736" page="17">• One push button energization sequence for the wind farm (ONS-OSS-WTG), including relevant time delay for the sequence to energizing the WTG transformers.</Text><Text id="36737" page="17">The wind farm MW and MVAr at the 66 kV or 220kV side offshore is handled via WFPCs which shall be interfaced to the EPC by means of a WFPC PLC to achieve the above aims of the overall control interface. The number and electrical placement of the WFPC controllers shall be evaluated during ESON FEED based on Grid code requirements, regulations related to need Balancing Mechanism Units (as in the United Kingdom or Polish equivalent) and subsidy CfD rules.</Text><Text id="36739" page="17">The need and method for de-load and tripping signals or requests shall be agreed with the TSO through workshops. The functionality must be in accordance with all grid code requirements for different operating modes and with the Power System Philosophy. TSO requirements to signal interfaces must be clarified through FEED.</Text><Text id="36740" page="17">Redundancy and Failure A fault function will need to be included to detect any problems caused by the program logic execution or interface/communication fault.</Text><Text id="36741" page="17">• Failure of EPC shall raise an alarm to the ESI SCADA.</Text><Text id="36742" page="17">• Failure of WFPC shall raise an alarm to the ESI SCADA.</Text><Text id="36743" page="17">• Communication error between the EPC and WFPC shall raise an alarm to the ESI SCADA</Text><Text id="36744" page="17">Redundancy of the interface between ESI Power Control and WFPC shall be included.</Text><Text id="37152" page="2">Technical. responsible (Organization unit / Name): Date/Signature: eApproved: 17.11.2022 Responsible (Organization unit / Name): Date/Signature: eApproved: 12.12.2022 Recommended (Organization unit / Name): Date/Signature: eApproved: 22.11.2022 Approved by (Organization unit / Name): Date/Signature: eApproved: 22.11.2022</Text><Text id="37153" page="2">Author(s)/Source(s): Subjects: Design premises necessary for the front-end engineering and design (FEED) and execution phase of the MFW offshore wind projects. Remarks: Updated: Valid from: 12/12/2022 Responsible publisher: Authority to approve deviations:</Text><Text id="37154" page="2">Distribution: Classification: Internal Expiry date: Status Final</Text><Text id="37155" page="2">Title: Automation Technical and Functional Requirements - Contract no.: Document no: C256-EQ-J-SP-00002 Project: MFW</Text><Text id="37156" page="16">Configuration Scenario A Normal operation B Loss of one 66kV WTG string/feeder C Loss of one 66 kV SWB D Loss of one OSS 220/66 kV transformer E Loss of one 220 kV export cable F Loss of one ONS 400/220 kV transformer G Loss of any reactive compensation or filter unit</Text></Spec>