{"component": "clause", "props": {"groups": [{"snippet_links": [{"key": "security-analysis", "type": "clause", "offset": [80, 97]}, {"key": "in-accordance-with", "type": "definition", "offset": [98, 116]}, {"key": "commission-regulation", "type": "definition", "offset": [131, 152]}, {"key": "august-2017", "type": "clause", "offset": [176, 187]}, {"key": "transmission-system-operation", "type": "clause", "offset": [228, 257]}, {"key": "approved-by", "type": "definition", "offset": [268, 279]}, {"key": "according-to-article", "type": "clause", "offset": [285, 305]}], "snippet": "The document \u201cAll TSOs\u2019 proposal for a methodology for coordinating operational security analysis in accordance with article 75 of Commission Regulation (EU) 51 2017/1485 of 2 August 2017 establishing a guideline on electricity transmission system operation\u201d has been approved by ACER according to Article 6(2)(c) of SOGL. SOGL 75", "size": 7, "samples": [{"hash": "hOVriGhlfG8", "uri": "/contracts/hOVriGhlfG8#rules-methodologies", "label": "Nordic System Operation Agreement (Soa)", "score": 32.4272384644, "published": true}, {"hash": "9ca64nUtyDd", "uri": "/contracts/9ca64nUtyDd#rules-methodologies", "label": "Nordic System Operation Agreement (Soa)", "score": 32.3376350403, "published": true}], "hash": "a1f4e9b52552206234a7c381c3f175d4", "id": 1}, {"snippet_links": [{"key": "common-rules", "type": "clause", "offset": [6, 18]}, {"key": "the-operation", "type": "clause", "offset": [23, 36]}, {"key": "normal-state", "type": "clause", "offset": [40, 52]}, {"key": "section-532", "type": "clause", "offset": [370, 383]}], "snippet": "5.4.1 Common rules for the operation in normal state and alert state\n1. During the operational hour the TSOs\u2019 operators follow the trend of the operational situation and continuously estimate upcoming need of readjusting the balancing. In normal and alert state conditions TSOs use market based FRR activation as long as possible. These include:\na. mFRR activation (see section 5.3.2);\nb. aFRR activation (see section 5.3.2", "size": 6, "samples": [{"hash": "g9g7ROnmKh2", "uri": "/contracts/g9g7ROnmKh2#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 33.2261009216, "published": true}, {"hash": "hikg9T5KtNe", "uri": "/contracts/hikg9T5KtNe#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 33.1494522095, "published": true}, {"hash": "677CPscJwTB", "uri": "/contracts/677CPscJwTB#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 32.1455497742, "published": true}], "hash": "cbd0f909cfe57f41dea78fcccd555f0c", "id": 2}, {"snippet_links": [{"key": "the-rules", "type": "clause", "offset": [95, 104]}, {"key": "article-3", "type": "definition", "offset": [153, 162]}], "snippet": "6.4.1 Dimensioning of FCR-N FCR-N shall be at least 600 MW.\n6.4.2 Dimensioning rules for FCR-D The rules for dimensioning of Nordic FCR-D are defined in article 3 of the methodology below:", "size": 6, "samples": [{"hash": "g9g7ROnmKh2", "uri": "/contracts/g9g7ROnmKh2#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 33.2261009216, "published": true}, {"hash": "677CPscJwTB", "uri": "/contracts/677CPscJwTB#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 32.1455497742, "published": true}, {"hash": "a43ChoBQuBL", "uri": "/contracts/a43ChoBQuBL#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 32.0543365479, "published": true}], "hash": "e53ede824f0dd5263cf54fd1fbd348bd", "id": 3}, {"snippet_links": [{"key": "the-danish", "type": "clause", "offset": [34, 44]}, {"key": "capacity-calculation", "type": "clause", "offset": [87, 107]}, {"key": "in-accordance-with", "type": "definition", "offset": [172, 190]}, {"key": "article-16", "type": "definition", "offset": [191, 201]}, {"key": "commission-regulation", "type": "definition", "offset": [205, 226]}, {"key": "september-2016", "type": "clause", "offset": [248, 262]}, {"key": "capacity-allocation", "type": "clause", "offset": [299, 318]}, {"key": "subject-to-approval", "type": "clause", "offset": [389, 408]}, {"key": "according-to-article", "type": "clause", "offset": [409, 429]}, {"key": "acknowledged-by", "type": "definition", "offset": [449, 464]}], "snippet": "The TSOs agree that the document \u201cThe Danish TSO, Energinet\u2019s, proposal for the Nordic Capacity Calculation Region methodology for splitting long-term cross-zonal capacity in accordance with Article 16 of Commission Regulation (EU) 2016/1719 of 26 September 2016 establishing a guideline on forward capacity allocation\u201d that has been submitted to Danish NRA on 16 January 2019 and that is subject to approval according to Article 4(7)(b) of FCA, is acknowledged by the other TSOs. FCA 16", "size": 5, "samples": [{"hash": "kHSXiBHX9LI", "uri": "/contracts/kHSXiBHX9LI#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Forward Capacity Allocation (Fca)", "score": 27.4895935059, "published": true}, {"hash": "146bvHLz9Kt", "uri": "/contracts/146bvHLz9Kt#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Forward Capacity Allocation (Fca)", "score": 27.374622345, "published": true}, {"hash": "jLFT1LTz6kL", "uri": "/contracts/jLFT1LTz6kL#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Forward Capacity Allocation (Fca)", "score": 27.0543518066, "published": true}], "hash": "5e55f981eefe1934aa2e6d58c47d23ba", "id": 4}, {"snippet_links": [{"key": "capacity-calculation", "type": "clause", "offset": [58, 78]}, {"key": "coordinated-redispatching-and-countertrading", "type": "clause", "offset": [92, 136]}, {"key": "in-accordance-with", "type": "definition", "offset": [149, 167]}, {"key": "commission-regulation", "type": "definition", "offset": [182, 203]}, {"key": "july-2015", "type": "clause", "offset": [225, 234]}, {"key": "capacity-allocation", "type": "clause", "offset": [263, 282]}, {"key": "congestion-management", "type": "clause", "offset": [287, 308]}, {"key": "approved-by", "type": "definition", "offset": [342, 353]}, {"key": "nordic-ccr", "type": "definition", "offset": [354, 364]}, {"key": "according-to-article", "type": "clause", "offset": [370, 390]}, {"key": "accepted-by", "type": "clause", "offset": [430, 441]}], "snippet": "The TSOs agree that the document \u201cAll TSOs\u2019 of the Nordic Capacity Calculation Region for a coordinated redispatching and countertrading methodology in accordance with Article 35 of Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a guideline on capacity allocation and congestion management (CRC Methodology)\u201d that has been approved by Nordic CCR NRAs according to Article 9(7)(c) of CACM on 10 January 2019, is accepted by all TSOs. CACM 35", "size": 5, "samples": [{"hash": "rOHNFPuC87", "uri": "/contracts/rOHNFPuC87#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Capacity Allocation & Capacity Management (Cacm)", "score": 29.4895935059, "published": true}, {"hash": "bn25I7NO88b", "uri": "/contracts/bn25I7NO88b#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Capacity Allocation & Capacity Management (Cacm)", "score": 24.245721817, "published": true}], "hash": "a1998edd52e4d2830a2f48832f2874e9", "id": 5}, {"snippet_links": [{"key": "resulting-from", "type": "definition", "offset": [87, 101]}, {"key": "single-day", "type": "clause", "offset": [102, 112]}, {"key": "in-accordance-with", "type": "definition", "offset": [128, 146]}, {"key": "commission-regulation", "type": "definition", "offset": [165, 186]}, {"key": "july-2015", "type": "clause", "offset": [208, 217]}, {"key": "capacity-allocation", "type": "clause", "offset": [246, 265]}, {"key": "congestion-management", "type": "clause", "offset": [270, 291]}, {"key": "approved-by", "type": "definition", "offset": [297, 308]}, {"key": "according-to-article", "type": "clause", "offset": [318, 338]}], "snippet": "The document \u201cAll TSOs\u2019 proposal for a Methodology for Calculating Scheduled Exchanges resulting from single day-ahead coupling in accordance with Article 43 of the Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a guideline on capacity allocation and congestion management\u201d was approved by all NRAs according to Article 9(7)(d) of CACM.", "size": 4, "samples": [{"hash": "eGlKOPiQ8WQ", "uri": "/contracts/eGlKOPiQ8WQ#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Capacity Allocation & Capacity Management (Cacm)", "score": 34.2615470886, "published": true}, {"hash": "8KCTEumWIgk", "uri": "/contracts/8KCTEumWIgk#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Capacity Allocation & Capacity Management (Cacm)", "score": 33.5114097595, "published": true}], "hash": "02267004343100b162a59f0240b5807e", "id": 6}, {"snippet_links": [{"key": "concerning-the", "type": "clause", "offset": [19, 33]}, {"key": "technical-infrastructure", "type": "clause", "offset": [82, 106]}, {"key": "in-the-process", "type": "definition", "offset": [179, 193]}, {"key": "section-421", "type": "clause", "offset": [220, 233]}, {"key": "control-systems", "type": "clause", "offset": [254, 269]}, {"key": "information-systems", "type": "definition", "offset": [301, 320]}, {"key": "operation-information", "type": "clause", "offset": [337, 358]}, {"key": "messaging-systems", "type": "clause", "offset": [390, 407]}, {"key": "communication-links", "type": "clause", "offset": [411, 430]}, {"key": "nordic-tsos", "type": "definition", "offset": [474, 485]}, {"key": "restoration-process", "type": "clause", "offset": [708, 727]}, {"key": "a-week", "type": "definition", "offset": [895, 901]}, {"key": "hours-per-day", "type": "clause", "offset": [923, 936]}, {"key": "the-functions", "type": "definition", "offset": [987, 1000]}, {"key": "related-to", "type": "clause", "offset": [1027, 1037]}, {"key": "the-year", "type": "definition", "offset": [1181, 1189]}, {"key": "software-architecture", "type": "clause", "offset": [1208, 1229]}, {"key": "and-application", "type": "clause", "offset": [1230, 1245]}, {"key": "monthly-maintenance", "type": "clause", "offset": [1397, 1416]}, {"key": "system-shutdowns", "type": "clause", "offset": [1434, 1450]}, {"key": "planned-maintenance", "type": "clause", "offset": [1507, 1526]}, {"key": "for-example", "type": "definition", "offset": [1528, 1539]}, {"key": "software-upgrades", "type": "clause", "offset": [1561, 1578]}, {"key": "per-month", "type": "clause", "offset": [1663, 1672]}, {"key": "availability-of", "type": "clause", "offset": [1693, 1708]}, {"key": "calendar-year", "type": "definition", "offset": [1876, 1889]}, {"key": "once-a-month", "type": "clause", "offset": [2036, 2048]}, {"key": "shall-be-informed", "type": "definition", "offset": [2059, 2076]}, {"key": "hours-in-advance", "type": "clause", "offset": [2133, 2149]}, {"key": "on-request", "type": "definition", "offset": [2200, 2210]}, {"key": "communication-lines", "type": "clause", "offset": [2454, 2473]}, {"key": "european-level", "type": "clause", "offset": [2662, 2676]}, {"key": "communication-protocols", "type": "clause", "offset": [2701, 2724]}], "snippet": "4.4.1 Requirements concerning the availability, reliability and redundancy of the technical infrastructure Technical infrastructure that is required for the processes referred to in the process activation structure (see section 4.2.1) include: \u2022 Digital control systems such as o SCADA/LFC systems; o Information systems like the Nordic Operation Information System (NOIS); and o Telephone/messaging systems. \u2022 Communication links between the Digital control systems of the Nordic TSOs. SOGL 143(4) SOGL 145(6) SOGL 119(1)(e) SOGL 151(2)-(3) SOGL 118(1)(p) SOGL 119(1)(f) SOGL 151(1)\n4.4.1.1 Availability, reliability and redundancy of Digital control systems for frequency containment process and frequency restoration process SOGL 118(1)(p) SOGL 119(1)(f) Digital control systems required for frequency containment process and frequency restoration process have to be available seven (7) days a week and twenty-four (24) hours per day during the whole year. The TSOs shall ensure that the functions in these systems that are related to the frequency containment process and frequency restoration process run with a minimum of interruptions twenty-four (24) hours per day through the year. The hardware and software architecture and application design of the Digital control systems required for frequency containment process and frequency restoration process shall be such that normal daily and monthly maintenance does not require system shutdowns and system can be used uninterruptedly. However, during planned maintenance, for example in major hardware or software upgrades, downtime less than 1\u22122 hours can still be considered acceptable not more than once per month. SOGL 151(2)(b) The availability of the functions in these systems that are related to the frequency containment process and frequency restoration process shall be at least 99,5 % as an average over the calendar year, excluding planned maintenance. Short occasional interruptions (10\u221220 minutes) are allowed once a week. Planned maintenance pauses are acceptable once a month. All TSOs shall be informed of planned maintenance breaks at least twenty-four (24) hours in advance. Planned maintenance can be cancelled at all time on request from one of the TSOs. SOGL 151(2)(b)\n4.4.1.2 Availability, reliability and redundancy of Communication links between Digital control systems for frequency containment process and frequency restoration process SOGL 118(1)(p) SOGL 119(1)(f) The communication lines between the Nordic TSOs and between the Nordic TSOs and other European TSOs are part of the so-called Electronic Highway (EH). The availability and redundancy of the EH are described on a European level. SOGL 151(2)(c)\n4.4.1.3 Communication protocols SOGL 151(2)(d) Communication protocols that are used between the Nordic TSOs are Elcom and Tase 2.", "size": 4, "samples": [{"hash": "71z2MbsxDC9", "uri": "/contracts/71z2MbsxDC9#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 29.9001979828, "published": true}, {"hash": "7iXpz31tOMM", "uri": "/contracts/7iXpz31tOMM#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex LFCR", "score": 26.5944728851, "published": true}], "hash": "d061c9a4db08b5dc6328e8802b24e251", "id": 7}, {"snippet_links": [{"key": "resulting-from", "type": "definition", "offset": [93, 107]}, {"key": "intraday-coupling", "type": "definition", "offset": [115, 132]}, {"key": "in-accordance-with", "type": "definition", "offset": [133, 151]}, {"key": "commission-regulation", "type": "definition", "offset": [173, 194]}, {"key": "july-2015", "type": "clause", "offset": [216, 225]}, {"key": "capacity-allocation", "type": "clause", "offset": [254, 273]}, {"key": "congestion-management", "type": "clause", "offset": [278, 299]}, {"key": "approved-by", "type": "definition", "offset": [315, 326]}, {"key": "according-to-article", "type": "clause", "offset": [336, 356]}, {"key": "accepted-by", "type": "clause", "offset": [396, 407]}, {"key": "gate-closure", "type": "clause", "offset": [513, 525]}, {"key": "april-2018", "type": "clause", "offset": [771, 781]}], "snippet": "The TSOs agree that the document \u201cThe all TSOs\u2019 proposal for calculating scheduled exchanges resulting from single intraday coupling in accordance with Article 56(1) of the Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a guideline on capacity allocation and congestion management\u201d that has been approved by all NRAs according to Article 9(7)(d) of CACM on 30 October 2019, is accepted by all TSOs. The TSOs agree that the document \u201cAll TSOs\u2019 proposal for intraday cross-zonal gate opening and gate closure times in accordance with Article 59 of Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a guideline on capacity allocation and congestion management\u201d that has been approved by all NRAs according to Article 9(6)(k) of CACM on 24 April 2018, is accepted by all TSOs. CACM 56(1) CACM 59(1)", "size": 4, "samples": [{"hash": "bn25I7NO88b", "uri": "/contracts/bn25I7NO88b#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Capacity Allocation & Capacity Management (Cacm)", "score": 24.245721817, "published": true}], "hash": "3d64ba84a3ae86c74a9b4ca4139352cf", "id": 8}, {"snippet_links": [{"key": "resulting-from", "type": "definition", "offset": [73, 87]}, {"key": "intraday-coupling", "type": "definition", "offset": [95, 112]}, {"key": "in-accordance-with", "type": "definition", "offset": [113, 131]}, {"key": "commission-regulation", "type": "definition", "offset": [153, 174]}, {"key": "july-2015", "type": "clause", "offset": [196, 205]}, {"key": "capacity-allocation", "type": "clause", "offset": [234, 253]}, {"key": "congestion-management", "type": "clause", "offset": [258, 279]}, {"key": "approved-by", "type": "definition", "offset": [285, 296]}, {"key": "according-to-article", "type": "clause", "offset": [306, 326]}, {"key": "gate-closure", "type": "clause", "offset": [419, 431]}, {"key": "svenska-kraftn\u00e4t", "type": "definition", "offset": [657, 673]}, {"key": "april-2017", "type": "clause", "offset": [973, 983]}, {"key": "the-arrangements", "type": "clause", "offset": [1271, 1287]}, {"key": "december-2018", "type": "clause", "offset": [1421, 1434]}, {"key": "agency-for-the-cooperation-of-energy-regulators", "type": "definition", "offset": [1476, 1523]}], "snippet": "The document \u201cThe all TSOs\u2019 proposal for calculating scheduled exchanges resulting from single intraday coupling in accordance with Article 56(1) of the Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a guideline on capacity allocation and congestion management\u201d was approved by all NRAs according to Article 9(7)(d) of CACM. The document \u201cAll TSOs\u2019 proposal for intraday cross-zonal gate opening and gate closure times in accordance with Article 59 of Commission Regulation (EU) CACM 56(1) CACM 59(1) Arrangements concerning more NEMOs (Multi NEMO arrangement \u201cMNA\u201d)5 \u2022 The four individual documents (respectively Energinet\u2019s, Fingrid\u2019s, Svenska kraftn\u00e4t\u2019s and Statnett\u2019s) \u201cArrangements concerning more than one NEMO in one bidding zone in accordance with Article 45 and 57 of the Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a Guideline on Capacity Allocation and Congestion Management\u201d approved by each individual Nordic NRA on 10 April 2017. \u2022 The four individual documents (respectively Energinet\u2019s, Fingrid\u2019s, Svenska kraftn\u00e4t\u2019s and \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2019s) \u201camendment in accordance with Article 9(13) of the Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a Guideline on Capacity Allocation and Congestion Management on the Arrangements concerning more than one NEMO in one bidding zone in accordance with Article 45 and 57\u201d approved by each individual Nordic NRA on 18 December 2018 The document \u201cDecision No 01/2019 of the Agency for the Cooperation of Energy Regulators of 24 January 2019 establishing a single methodology for pricing intraday cross-zonal capacity\u201d was approved by ACER on 24 January 2019 according to Article 9(11) of CACM.", "size": 4, "samples": [{"hash": "eGlKOPiQ8WQ", "uri": "/contracts/eGlKOPiQ8WQ#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Capacity Allocation & Capacity Management (Cacm)", "score": 34.2615470886, "published": true}], "hash": "b8b173b78008a050c7a516596ca81c06", "id": 9}, {"snippet_links": [{"key": "concerning-the", "type": "clause", "offset": [19, 33]}, {"key": "technical-infrastructure", "type": "clause", "offset": [82, 106]}, {"key": "in-the-process", "type": "definition", "offset": [179, 193]}, {"key": "section-421", "type": "clause", "offset": [220, 233]}, {"key": "control-systems", "type": "clause", "offset": [254, 269]}, {"key": "information-systems", "type": "definition", "offset": [300, 319]}, {"key": "operation-information", "type": "clause", "offset": [336, 357]}, {"key": "messaging-systems", "type": "clause", "offset": [388, 405]}, {"key": "communication-links", "type": "clause", "offset": [408, 427]}, {"key": "nordic-tsos", "type": "definition", "offset": [471, 482]}, {"key": "restoration-process", "type": "clause", "offset": [608, 627]}, {"key": "a-week", "type": "definition", "offset": [765, 771]}, {"key": "hours-per-day", "type": "clause", "offset": [793, 806]}, {"key": "the-functions", "type": "definition", "offset": [857, 870]}, {"key": "related-to", "type": "clause", "offset": [897, 907]}, {"key": "the-year", "type": "definition", "offset": [1051, 1059]}, {"key": "software-architecture", "type": "clause", "offset": [1078, 1099]}, {"key": "and-application", "type": "clause", "offset": [1100, 1115]}, {"key": "monthly-maintenance", "type": "clause", "offset": [1334, 1353]}, {"key": "system-shutdowns", "type": "clause", "offset": [1371, 1387]}, {"key": "planned-maintenance", "type": "clause", "offset": [1444, 1463]}, {"key": "for-example", "type": "definition", "offset": [1465, 1476]}, {"key": "software-upgrades", "type": "clause", "offset": [1498, 1515]}, {"key": "per-month", "type": "clause", "offset": [1600, 1609]}, {"key": "communication-lines", "type": "clause", "offset": [1802, 1821]}, {"key": "european-level", "type": "clause", "offset": [2010, 2024]}, {"key": "communication-protocols", "type": "clause", "offset": [2049, 2072]}], "snippet": "4.4.1 Requirements concerning the availability, reliability and redundancy of the technical infrastructure Technical infrastructure that is required for the processes referred to in the process activation structure (see section 4.2.1) include: \u2022 Digital control systems such as o SCADA/LFC systems o Information systems like the Nordic Operation Information System (NOIS) and o Telephone/messaging systems \u2022 Communication links between the Digital control systems of the Nordic TSOs.\n4.4.1.1 Availability, reliability and redundancy of Digital control systems for frequency containment process and frequency restoration process Digital control systems required for frequency containment process and frequency restoration process have to be available seven (7) days a week and twenty-four (24) hours per day during the whole year. The TSOs shall ensure that the functions in these systems that are related to the frequency containment process and frequency restoration process run with a minimum of interruptions twenty-four (24) hours per day through the year. The hardware and software architecture and application design of the Digital control systems required for frequency containment process and frequency SOGL 143(4) SOGL 145(6) SOGL 151(2)-(3) SOGL 151(1) SOGL 151(2)(b) restoration process shall be such that normal daily and monthly maintenance does not require system shutdowns and system can be used uninterruptedly. However, during planned maintenance, for example in major hardware or software upgrades, downtime less than 1\u22122 hours can still be considered acceptable not more than once per month.\n4.4.1.2 Availability, reliability and redundancy of Communication links between SOGL 151(2)(b) Digital control systems for frequency containment process and frequency restoration process The communication lines between the Nordic TSOs and between the Nordic TSOs and other European TSOs are part of the so-called Electronic Highway (EH). The availability and redundancy of the EH are described on a European level. SOGL 151(2)(c) 4.4.1.3 Communication protocols SOGL 151(2)(d) Communication protocols that are used between the Nordic TSOs are ICCP, Elcom and Tase 2.", "size": 3, "samples": [{"hash": "g9g7ROnmKh2", "uri": "/contracts/g9g7ROnmKh2#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 33.2261009216, "published": true}, {"hash": "a43ChoBQuBL", "uri": "/contracts/a43ChoBQuBL#rules-methodologies", "label": "Nordic System Operation Agreement (Soa) \u2013 Annex Load Frequency Control & Reserves (Lfcr)", "score": 32.0543365479, "published": true}], "hash": "bc6d31d96cd9c20103416f7146180329", "id": 10}], "next_curs": "ClwSVmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjgLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhxydWxlcy1tZXRob2RvbG9naWVzIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"children": [["objective", "Objective"], ["rules-methodologies", "Rules & Methodologies"], ["operational-procedures", "Operational Procedures"], ["roles-responsibilities", "Roles & Responsibilities"], ["", ""]], "title": "Rules & Methodologies", "size": 32, "parents": [["operational-procedures", "Operational Procedures"], ["definitions", "Definitions"], ["general-requirements", "General requirements"], ["exchange-agreement", "Exchange agreement"], ["power-flow-management", "Power Flow Management"]], "id": "rules-methodologies", "related": [["methodology", "Methodology", "Methodology"], ["service-providing-methodology", "Service Providing Methodology", "Service Providing Methodology"], ["payment-methodology", "Payment Methodology", "Payment Methodology"], ["application-procedures", "Application Procedures", "Application Procedures"], ["selection-procedures", "Selection Procedures", "Selection Procedures"]], "related_snippets": [], "updated": "2025-07-10T05:58:13+00:00"}, "json": true, "cursor": ""}}