{"component": "clause", "props": {"groups": [{"samples": [{"hash": "fM8eiN9n26a", "uri": "/contracts/fM8eiN9n26a#technical-coordination", "label": "Solicitation, Offer and Award", "score": 29.1573562622, "published": true}, {"hash": "lVCDYfyINnd", "uri": "/contracts/lVCDYfyINnd#technical-coordination", "label": "Contract", "score": 29.0752334595, "published": true}], "snippet": "i. Performance of work under this Contract shall be in compliance with the requirements documents (i.e. Performance Work Statement (PWS)) and terms and conditions of the Contract.\nii. All technical coordination shall remain within the scope of this Contract. No oral statements of any person whosoever shall in any manner or degree modify or otherwise affect the terms of this Contract. Technical coordination shall not result in any action that:\n(a) Constitutes an assignment of additional work outside the requirements documents.\n(b) Constitutes a change as defined in the Contract clauses 52.243-1, Changes Fixed-Price and 52.243-2, Changes - Cost-Reimbursement, as applicable.\n(c) Causes an increase in the total Contract ceiling amount, Contract price, or the time required for Contract performance.\n(d) Changes any of the expressed terms, conditions or specifications of this Contract.\n(e) Interferes with the Contractor\u2019s right to perform the terms and conditions of the Contract.", "snippet_links": [{"key": "performance-of-work", "type": "clause", "offset": [3, 22]}, {"key": "under-this-contract", "type": "clause", "offset": [23, 42]}, {"key": "requirements-documents", "type": "definition", "offset": [75, 97]}, {"key": "performance-work-statement", "type": "definition", "offset": [104, 130]}, {"key": "terms-and-conditions-of-the-contract", "type": "clause", "offset": [142, 178]}, {"key": "scope-of-this-contract", "type": "clause", "offset": [235, 257]}, {"key": "oral-statements", "type": "clause", "offset": [262, 277]}, {"key": "any-person", "type": "definition", "offset": [281, 291]}, {"key": "terms-of-this-contract", "type": "clause", "offset": [363, 385]}, {"key": "in-any-action", "type": "clause", "offset": [427, 440]}, {"key": "assignment-of-additional-work", "type": "clause", "offset": [466, 495]}, {"key": "contract-clauses", "type": "clause", "offset": [575, 591]}, {"key": "the-total", "type": "clause", "offset": [707, 716]}, {"key": "ceiling-amount", "type": "clause", "offset": [726, 740]}, {"key": "contract-price", "type": "definition", "offset": [742, 756]}, {"key": "time-required", "type": "clause", "offset": [765, 778]}, {"key": "contract-performance", "type": "clause", "offset": [783, 803]}, {"key": "the-contractor", "type": "clause", "offset": [912, 926]}, {"key": "right-to-perform", "type": "clause", "offset": [929, 945]}, {"key": "the-terms-and-conditions", "type": "definition", "offset": [946, 970]}], "size": 2, "hash": "a1a8174fe54e5db2a4bab52fc17cef4b", "id": 1}, {"samples": [{"hash": "aqTHgWJp62z", "uri": "/contracts/aqTHgWJp62z#technical-coordination", "label": "Shared Cost RTD Contract", "score": 17.0, "published": true}], "snippet": "The Project Coordinator, \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh), is in overall charge of the technical work in the project. He is responsible for overseeing progress on the various workpackages and for initiating remedial action in case technical difficulties in some area necessitates a rethink of the overall project structure. He will convene, and be advised by, a steering committee consisting of all the workpackage coordinators and supplemented by additional members as needs demand. This committee will convene quarterly, either in person or by video/tele- conferencing. The main means of access to the deliverables of the project and to internal technical documents will be via WWW, and the Project Coordinator is responsible for setting up and maintaining the project\u2019s Web site. The Project Coordinator is also responsible for organising the project\u2019s annual workshop. Each workpackage is managed by a Workpackage Coordinator. These are as follows: Workpackage 1 : \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 2 : \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 3 : \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 4 : \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 5 : \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 6 : \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 7 : \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Munich) Workpackage 8 : \u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 9 : \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Munich) Workpackage 10 : \u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh) Workpackage 11 : \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Edinburgh) Each Workpackage Coordinator is responsible for monitoring the technical work within that workpackage and ensuring that it proceeds according to plan, convening meetings, main- taining an electronic mailing list for discussion on matters relevant to the technical work, reviewing internal technical documents and deliverables and maintaining a section of the project\u2019s website. Decisions concerning the overall technical direction of the project will be made by the Project Coordinator in close consultation with the Workpackage Coordinators and other col- leagues. A formal technical management meeting will be convened by the Project Coordi- nator at each of the project workshops and will be open to all project personnel. Project workshops will consist partly of presentations of technical developments and partly of a review of the progress of the project, and decisions concerning the future direction of the project will be informed by these reviews.", "snippet_links": [{"key": "project-coordinator", "type": "clause", "offset": [4, 23]}, {"key": "technical-work", "type": "definition", "offset": [79, 93]}, {"key": "responsible-for", "type": "clause", "offset": [116, 131]}, {"key": "remedial-action", "type": "clause", "offset": [199, 214]}, {"key": "in-case", "type": "clause", "offset": [215, 222]}, {"key": "technical-difficulties", "type": "clause", "offset": [223, 245]}, {"key": "project-structure", "type": "clause", "offset": [297, 314]}, {"key": "be-advised", "type": "definition", "offset": [337, 347]}, {"key": "steering-committee", "type": "definition", "offset": [354, 372]}, {"key": "additional-members", "type": "definition", "offset": [440, 458]}, {"key": "in-person", "type": "clause", "offset": [522, 531]}, {"key": "the-deliverables", "type": "clause", "offset": [592, 608]}, {"key": "technical-documents", "type": "definition", "offset": [640, 659]}, {"key": "setting-up", "type": "definition", "offset": [724, 734]}, {"key": "web-site", "type": "definition", "offset": [765, 773]}, {"key": "according-to", "type": "definition", "offset": [1532, 1544]}, {"key": "convening-meetings", "type": "clause", "offset": [1551, 1569]}, {"key": "mailing-list", "type": "clause", "offset": [1599, 1611]}, {"key": "documents-and-deliverables", "type": "clause", "offset": [1699, 1725]}, {"key": "decisions-concerning-the", "type": "clause", "offset": [1778, 1802]}, {"key": "technical-direction", "type": "definition", "offset": [1811, 1830]}, {"key": "a-formal", "type": "clause", "offset": [1966, 1974]}, {"key": "management-meeting", "type": "clause", "offset": [1985, 2003]}, {"key": "project-personnel", "type": "clause", "offset": [2107, 2124]}, {"key": "technical-developments", "type": "clause", "offset": [2184, 2206]}, {"key": "review-of-the", "type": "clause", "offset": [2223, 2236]}, {"key": "progress-of-the-project", "type": "clause", "offset": [2237, 2260]}, {"key": "future-direction", "type": "clause", "offset": [2291, 2307]}], "size": 2, "hash": "3c4eb265cf4e077a8d3711ad0901f649", "id": 2}, {"samples": [{"hash": "jOEu5VjaLTt", "uri": "/contracts/jOEu5VjaLTt#technical-coordination", "label": "Framework Collaboration Agreement", "score": 34.3404701458, "published": true}], "snippet": "\u200c The Parties shall each nominate a technical coordinator, who together shall coordinate the technical execution of the Project, as well as a designated safety coordinator. Their names and contact details are set out in Annex 1.", "snippet_links": [{"key": "the-parties-shall", "type": "clause", "offset": [2, 19]}, {"key": "technical-coordinator", "type": "clause", "offset": [36, 57]}, {"key": "the-technical", "type": "clause", "offset": [89, 102]}, {"key": "execution-of-the-project", "type": "clause", "offset": [103, 127]}, {"key": "a-designated", "type": "clause", "offset": [140, 152]}, {"key": "safety-coordinator", "type": "definition", "offset": [153, 171]}, {"key": "contact-details", "type": "clause", "offset": [189, 204]}, {"key": "set-out", "type": "definition", "offset": [209, 216]}, {"key": "annex-1", "type": "definition", "offset": [220, 227]}], "size": 1, "hash": "38204e74454d2e7126f7f03ea85fb383", "id": 3}, {"samples": [{"hash": "dQR06fU6BoS", "uri": "/contracts/dQR06fU6BoS#technical-coordination", "label": "Framework Collaboration Agreement", "score": 24.0882949829, "published": true}], "snippet": "For the purpose of the technical co-ordination of this Project, CERN\u2019s representative shall be: - \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2013 HL-LHC DF Project leader - \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2013 HL-LHC DF Project Engineer (?) And University\u2019s representative shall be: - \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587 \u2013 Southampton DF construction leader or such successors as each Party may designate and communicate to the other Party. All documentation shall be sent to \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (WP6a Leader) and \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (Deputy WP6a Leader). The Technical Coordinators shall liaise with each other at regular intervals in order to define the detailed work packages and time schedules, to monitor the execution of the Project and to ensure corrective actions in case any difficulty arises in the execution of a Party\u2019s contribution.", "snippet_links": [{"key": "the-technical", "type": "clause", "offset": [19, 32]}, {"key": "project-leader", "type": "definition", "offset": [126, 140]}, {"key": "project-engineer", "type": "clause", "offset": [169, 185]}, {"key": "each-party", "type": "definition", "offset": [305, 315]}, {"key": "other-party", "type": "definition", "offset": [353, 364]}, {"key": "technical-coordinators", "type": "definition", "offset": [478, 500]}, {"key": "regular-intervals", "type": "definition", "offset": [533, 550]}, {"key": "in-order-to", "type": "clause", "offset": [551, 562]}, {"key": "work-packages", "type": "clause", "offset": [583, 596]}, {"key": "time-schedules", "type": "clause", "offset": [601, 615]}, {"key": "execution-of-the-project", "type": "clause", "offset": [632, 656]}, {"key": "to-ensure", "type": "clause", "offset": [661, 670]}, {"key": "corrective-actions", "type": "definition", "offset": [671, 689]}, {"key": "in-case", "type": "clause", "offset": [690, 697]}, {"key": "a-party", "type": "clause", "offset": [740, 747]}], "size": 1, "hash": "4ceaee9b9da9d1009fc77a4b1acadcce", "id": 4}, {"samples": [{"hash": "5OWdxoCLMwO", "uri": "/contracts/5OWdxoCLMwO#technical-coordination", "label": "Solicitation, Offer and Award", "score": 29.5624866486, "published": true}], "snippet": "(1) Performance of work under this contract shall be in compliance with the PWS and terms and conditions of the contract.\n(2) All technical coordination shall remain within the scope of this contract. No oral statements by any person shall in any manner or degree modify or otherwise affect the terms of this contract. Technical coordination shall not result in any action that:\n(i) Constitutes an assignment of additional work outside the PWS.\n(ii) Constitutes a change as defined in the contract clauses 52.243-1, Changes - Fixed-Price and 52.243-2, Changes - Cost-Reimbursement, as applicable.\n(iii) Causes an increase in the total contract ceiling amount or the time required for contract performance.\n(iv) Changes in any of the expressed terms, conditions or specifications of this contract.\n(v) Interfere with the Contractor\u2019s right to perform the terms and conditions of the contract.", "snippet_links": [{"key": "performance-of-work", "type": "clause", "offset": [4, 23]}, {"key": "under-this-contract", "type": "clause", "offset": [24, 43]}, {"key": "compliance-with-the", "type": "clause", "offset": [56, 75]}, {"key": "terms-and-conditions-of-the-contract", "type": "clause", "offset": [84, 120]}, {"key": "scope-of-this-contract", "type": "clause", "offset": [177, 199]}, {"key": "oral-statements", "type": "clause", "offset": [204, 219]}, {"key": "any-person", "type": "definition", "offset": [223, 233]}, {"key": "terms-of-this-contract", "type": "clause", "offset": [295, 317]}, {"key": "in-any-action", "type": "clause", "offset": [359, 372]}, {"key": "assignment-of-additional-work", "type": "clause", "offset": [398, 427]}, {"key": "contract-clauses", "type": "clause", "offset": [489, 505]}, {"key": "the-total", "type": "clause", "offset": [625, 634]}, {"key": "ceiling-amount", "type": "clause", "offset": [644, 658]}, {"key": "time-required", "type": "clause", "offset": [666, 679]}, {"key": "contract-performance", "type": "clause", "offset": [684, 704]}, {"key": "changes-in", "type": "clause", "offset": [711, 721]}, {"key": "the-contractor", "type": "clause", "offset": [816, 830]}, {"key": "right-to-perform", "type": "clause", "offset": [833, 849]}, {"key": "the-terms-and-conditions", "type": "definition", "offset": [850, 874]}], "size": 1, "hash": "bf7b43a5ecba65d0a51f005480060166", "id": 5}, {"samples": [{"hash": "bv0LEMhJ3JC", "uri": "/contracts/bv0LEMhJ3JC#technical-coordination", "label": "Terrestrial Broadcasting Agreement", "score": 19.0, "published": true}], "snippet": "Technical coordinations concerning allotments and assignments shall normally consist of an exchange of letters between the Department of Communications of Canada and the Federal Communications Commission of the United States of America. In the event that the matter cannot be resolved by correspondence, a meeting shall be arranged. 2 .................. 54 - 60 36 .................. 602 - 608 3 .................. 60 - 66 37 .................. 608 - 614* 4 .................. 66 - 72 38 .................. 614 - 620 5 .................. 76 - 82 39 .................. 620 - 626 6 .................. 82 - 88 40 .................. 626 - 632 7 ................. 174 - 180 41 .................. 632 - 638 8 ................. 180 - 186 42 .................. 638 - 644 9 ................. 186 - 192 43 .................. 644 - 650 10 ................. 192 - 198 44 .................. 650 - 656 11 ................. 198 - 204 45 .................. 656 - 662 12 ................. 204 - 210 46 .................. 662 - 668 13 ................. 210 - 216 47 .................. 668 - 674 48 .................. 674 - 680 UHF 49 . .6. 8. 0... .-.. . 6. .8.6.... 50 .................. 686 - 692 14 ................. 470 - 476 51 .................. 692 - 698 15 ................. 476 - 482 52 .................. 698 - 704 16 ................. 482 - 488 53 .................. 704 - 710 17 ................. 488 - 494 54 .................. 710 - 716 18 ................. 494 - 500 55 .................. 716 - 722 19 ................. 500 - 506 56 .................. 722 - 728 20 ................. 506 - 512 57 .................. 728 - 734 21 ................. 512 - 518 58 .................. 734 - 740 22 ................. 518 - 524 59 .................. 740 - 746 23 ................. 524 - 530 60 .................. 746 - 752 24 ................. 530 - 536 61 .................. 752 - 758 25 ................. 536 - 542 62 .................. 758 - 764 26 ................. 542 - 548 63 .................. 764 - 770 27 ................. 548 - 554 64 .................. 770 - 776 28 ................. 554 - 560 65 .................. 776 - 782 29 ................. 560 - 566 66 .................. 782 - 788 30 ................. 566 - 572 67 .................. 788 - 794 31 ................. 572 - 578 68 .................. 794 - 800 32 ................. 578 - 584 69 .................. 800 - 806 33 ................. 584 - 590 34 ................. 590 - 596 35 ................. 596 - 602 * Channel 37 is allocated to the Radio Astronomy Service and is not available for broadcast use. Zone I: consists of that area between Windsor and Quebec which is located within the confines of the USA-Canada border and the following lines: beginning from the west at the intersection of the common border and the North Latitude 44E10'; thence in a straight line northeast to the point of intersection of 77E West Longitude and 46E North Latitude; thence following the 46E North Latitude until the 75E West Longitude; thence in a straight line northeast to the point of intersection of 72E West Longitude, and 47E North Latitude; thence following the 47E North Latitude to the point of intersection with 71E West Longitude; thence following the 71E West Longitude southwards to the common border. Zone II: consists of that portion of Canada within 400 km of the USA-Canada border which is not in Zone I. Zone I: consists of that portion of the United States located within the confines of the following lines drawn on the United States \u2587\u2587\u2587\u2587\u2587\u2587 Equal Area Projection Map (based on standard parallels 29.5E and 45.5E; North American Datum); beginning at the most easterly point of the State boundary line between North Carolina and Virginia; thence in a straight line to a point on the Virginia, West Virginia boundary line located at North Latitude 37E 49' and West Longitude 80E 12' 30\"; thence westerly along the southern boundary lines of the States of West Virginia, Ohio, Indiana and Illinois to a point at the junction of the Illinois, Kentucky and Missouri State boundary lines; thence northerly along the western boundary line of the State of Illinois to a point at the junction of the Illinois, Iowa and Wisconsin State boundary lines; thence easterly along the northern State boundary line of Illinois to the 90th meridian; thence north along this meridian to the 43.5E parallel; thence east along this parallel to the USA- Canada border; thence southerly and following the international border until it again intersects the 43.5E parallel; thence east along this parallel to the 71st meridian; thence in a straight line to the intersection of the 69th meridian and the 45th parallel; thence east along the 45th parallel to the Atlantic Ocean. When any of the above lines pass through a city, the city shall be considered to be located in Zone 1.", "snippet_links": [{"key": "consist-of", "type": "clause", "offset": [77, 87]}, {"key": "exchange-of-letters", "type": "clause", "offset": [91, 110]}, {"key": "department-of", "type": "clause", "offset": [123, 136]}, {"key": "commission-of", "type": "clause", "offset": [193, 206]}, {"key": "the-united-states-of-america", "type": "clause", "offset": [207, 235]}, {"key": "in-the-event", "type": "clause", "offset": [237, 249]}, {"key": "allocated-to", "type": "definition", "offset": [2487, 2499]}, {"key": "radio-astronomy-service", "type": "definition", "offset": [2504, 2527]}, {"key": "not-available", "type": "clause", "offset": [2535, 2548]}, {"key": "point-of-intersection", "type": "definition", "offset": [2851, 2872]}, {"key": "following-the", "type": "definition", "offset": [2926, 2939]}, {"key": "zone-ii", "type": "definition", "offset": [3268, 3275]}, {"key": "united-states-\u2587", "type": "clause", "offset": [3493, 3508]}, {"key": "based-on", "type": "definition", "offset": [3541, 3549]}, {"key": "north-american", "type": "clause", "offset": [3586, 3600]}, {"key": "the-state", "type": "clause", "offset": [3649, 3658]}, {"key": "north-carolina", "type": "clause", "offset": [3681, 3695]}, {"key": "west-virginia", "type": "definition", "offset": [3764, 3777]}, {"key": "boundary-lines", "type": "definition", "offset": [3893, 3907]}, {"key": "missouri-state", "type": "definition", "offset": [4024, 4038]}, {"key": "western-boundary", "type": "clause", "offset": [4082, 4098]}, {"key": "line-of", "type": "definition", "offset": [4099, 4106]}, {"key": "state-of-illinois", "type": "clause", "offset": [4111, 4128]}, {"key": "pass-through", "type": "definition", "offset": [4751, 4763]}, {"key": "the-city-shall", "type": "clause", "offset": [4772, 4786]}, {"key": "located-in", "type": "definition", "offset": [4807, 4817]}, {"key": "zone-1", "type": "definition", "offset": [4818, 4824]}], "size": 1, "hash": "93288428c811889b02ae6b39183549c7", "id": 6}, {"samples": [{"hash": "jMDZ9SbchdS", "uri": "/contracts/jMDZ9SbchdS#technical-coordination", "label": "Office Building Lease (Quest Software Inc)", "score": 21.0, "published": true}], "snippet": "Day to day coordination of functional and technical activities as described in Part I and elsewhere in this Contract shall be coordinated with Company\u2019s Building Manager listed below. Fluor Enterprises, Inc. \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587 Aliso Viejo, CA 92698 Telephone: (\u2587\u2587\u2587) \u2587\u2587\u2587-\u2587\u2587\u2587\u2587 FAX: (\u2587\u2587\u2587) \u2587\u2587\u2587-\u2587\u2587\u2587\u2587 Attn.: \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587/B1O", "snippet_links": [{"key": "technical-activities", "type": "clause", "offset": [42, 62]}, {"key": "in-this-contract", "type": "clause", "offset": [100, 116]}, {"key": "with-company", "type": "clause", "offset": [138, 150]}, {"key": "building-manager", "type": "clause", "offset": [153, 169]}, {"key": "listed-below", "type": "clause", "offset": [170, 182]}], "size": 1, "hash": "c692c4892dadf3c426d6bfc98925892a", "id": 7}, {"samples": [{"hash": "9xuOfjPVh88", "uri": "/contracts/9xuOfjPVh88#technical-coordination", "label": "Amendment No Amd 101079600 3", "score": 33.7406463623, "published": true}], "snippet": "Steering the project results to comply with TTR program Demarcation to other CEF projects: \u00bb The risk of overlaps with other ongoing EU projects is minimal because all staff costs are closely monitored through periodic reports. Work Package Number WP2 Lead Beneficiary 1 - RNE Work Package Name TTR Capacity strategy/model Start Month 1 End Month 48 Involved beneficiaries \u00bb RNE \u00bb DB InfraGO \u00bb RFI \u00bb SNCF-Reseau \u00bb SZCZ \u00bb Infrabel \u00bb RFC NSM Objectives The following objectives shall be achieved: \u00bb Facilitate the collection of information and general principles to be used further in the capacity planning and capacity allocation process on a European scale (RNE) \u00bb Support the harmonisation of the cross-border capacity planning (RNE) \u00bb Provide an overview on the available capacities on a European scale (RNE) \u00bb Enable and facilitate Capacity Partitioning (RNE) \u00bb Provide an overview concerning the infrastructure sections where future capacity bottlenecks might occur (RNE) \u00bb Create different visualisation possibilities of the capacities in order to satisfy the needs of various stakeholders (e.g. Regulatory Bodies, Applicants, Infrastructure Managers, Allocation Bodies etc.) (RNE) \u00bb Create different Capacity Model variants for the same period to facilitate the pre-planning of capacities (RNE) \u00bb Ensure that the potential Applicants can indicate their future capacity needs (via Capacity Needs Announcements), which can be directly transferred to the Capacity Model, which leads to smoother cooperation between the stakeholders (RNE) \u00bb Enable the unified clustering of TCRs (RNE) \u00bb Enable the unified impact calculation of TCRs (RNE) \u00bb Facilitate the TCR Consultation process through providing a standardised, transparent platform for every involved stakeholder. \u00bb Study on capacity bands, rolling planning requests on dedicated multi-annual offer (SNCF R\u00e9seau) \u00bb TTR-compliant Capacity Model (\u2587\u2587 \u2587\u2587\u2587\u2587) \u00bb Long-term planning Capacity Model (RFI) \u00bb Capacity Intelligence \u2013 homogeneous KPIs on capacity issues and visualisation (RFC NSM) \u00bb National capacity strategy and model tool (Infrabel) Anticipated effects: \u00bb Harmonised visualisation of capacity \u00bb Harmonised principles for infrastructure development and planning \u00bb Exchange of data in all phases (planning, operation, \u2026) \u00bb Transparent communication of capacity and specific capacity restrictions Links to other WPs \u00bb WP 3 and 4 (TCRs and allocation procedures are heavily affected by capacity model and strategy and vice versa) Overall WP description The IMs start the advance planning with the creation of Capacity Strategies. The focus of the strategy is on the future infrastructure development and the planning principles, already at this stage international coordination is needed, as various planning approaches exist between IMs. The Capacity Strategy is also the main connection between political and social requirements of citizens and the capacity planning process, since the competent authorities have a prominent role in this phase. The validated final strategies set the rules for the Capacity Models and next planning steps. A Capacity Model is a visualisation of: \u00bb volumes of capacity for commercial traffic \u00bb volumes of capacity to be used for TCRs The model is used to transparently communicate and discuss, in more detail, the expected volumes (not path or TCR details) and detect pressure points. In case of lines with international relevance, harmonisation with involved IMs is obligatory. The final model at X-18 (X as point of timetable change; i.e. 18 months prior the timetable change) is subject to the Capacity Partitioning. The capacity of a railway line section is set aside in the Capacity Model for dedicated purposes: \u00bb volumes for passenger traffic, \u00bb volumes for freight traffic, \u00bb Temporary Capacity Restrictions It should be ensured that high-quality capacity products will be set aside for both market segments (passenger and freight). In order to facilitate the TCR consultation, Capacity Model variants are created for major and high impact TCR periods. The number of Capacity Model variants depends on modifications made for this specific line. This can vary from 0 variants (no changes apply) to hundreds of variants (hundreds of changes apply). The Capacity Models is valid for a period from 24 months to 18 before timetable change and will be altered based on input from construction planning of the respective Infrastructure Manager which is becoming increasingly detailed. Note: It is not possible to indicate a specific number Tasks:\n2.1 Joint capacity model RNE To enable Applicants submitting their future capacity needs, the European Capacity Management Tool (ECMT) shall be extended with a new form, including dedicated parameters to the Applicant's needs. A new user role shall be prepared as Applicant user and workflow shall be implemented to track the statuses of the created Capacity Needs Announcements (CNA). Based on the Capacity Model Handbook, the existing objects in ECMT shall be extended with additional parameters, so that the IMs can publish all the necessary information for their Capacity Model (including paths, capacity bands and TCRs). That helps the interpretation of the models, the presentation options and also the capacity partitioning. The tool shall support variants of Capacity Models. That means, that an IM can prepare different Capacity Models for a particular day of the calendar. The objects can be then assigned to one or more variants. After the creation or import of the Capacity Model objects and Capacity Needs Announcements, those shall be presented on several different kind of views. There are four new potential views foreseen. A line overview showing the planned train runs on an hourly basis for the selected route; a block diagram showing the departing trains for a selected section of the network; a network overview showing the estimated free or booked capacity with different colours on a map; and a TCR duration overview showing the planned TCRs on a selected section clustered by the TCRs' impact. Once the object model of the tool is adjusted, and CNA objects, CM objects can be created in the tool, it is also essential to provide an import feature. An import template shall be available for the users (most likely in an XLSX format) where they can set up their CNA and CM inputs in a single source. Apart from importing the objects to the tool, there is an artifact on the capacity model views that presents an estimated limit of the capacity. It is called intended capacity and it is represented on the views with a line. The information behind this line is much less than for any CNA or CM object, that is why a dedicated import function shall be prepared. Compared to the Capacity Models, where an IM can prepare an object on its network alone, it works different for the Applicants with the CNAs. That is why, a harmonisation process shall be added to the tool so that Applicants will be able to coordinate their status among themselves, before submitting the CNA to the IMs. As the tool will serve as a platform for CNA and for Capacity Model objects, it's almost trivial that there should be a connection among those. In the Capacity Model handbook there is a dedicated process about how to deal with the CNAs and how the IMs can fit those to their Capacity Models. The workflow shall be specified in more details, then implemented in the tool, so that those two areas (CNA and CM) can interact with each other. After adjusting the object model in the tool and preparing Excel import, it's also necessary to provide more advanced integration options, meaning API options. There are two kinds of API options foreseen. First, a synchronization inside the RNE IT Tools, and synchronize the TCR objects from RNE's TCR Tool to the ECMT. Then, IMs would create, read, update and delete TCRs only in the TCR tool. Apart from the RNE internal integration, it's also relevant to integrate to the national tool of the IMs, so that the Capacity Model objects can be imported directly from their national tool to ECMT. Or vice versa, any IM could download the published Capacity Model to their national tool from ECMT. The documentation is essential before the implementation, but even during the implementation. We expect to have frequent deploys for the internal tests, so that the RNE team can check the implementation status and adjust the requirements immediately. During the implementation the change requests shall be tracked and included in the development, just like as the results of the UATs. At the end, this booking shall be a machine-to-machine process between RNE and the IMs. Therefore, the performance of the application is essential. The acceptance and effectiveness of the ECMT Tool shall be measured in data entries. When this tool is being set up, a total of more than 5000 data objects (Capacity Supply, Capacity Model, Capacity Needs Announcements, TCRs) per timetable year will be considered as successful in the first timetable year of deployment. It shall be monitored, but also the frequency of usage. Sub-tasks:\n2.1.1 Preparation for the implementation Preparing the functional requirements for developments\n2.1.2 Implementation of the necessary objects Creation of capacity model objects, CNAs, TCR part\n2.1.3 Implementation of the necessary views Section view, line view, network view, TCR duration overview\n2.1.4 Adjusting the import function of ECMT Intended capacity line, CNAs, Capacity Model objects and TCRs can be imported\n2.1.5 Implementing the workflows Harmonization function for the Applicants for their CNAs, connection between CNA and the Capacity Model", "snippet_links": [{"key": "project-results", "type": "clause", "offset": [13, 28]}, {"key": "comply-with", "type": "definition", "offset": [32, 43]}, {"key": "the-risk", "type": "definition", "offset": [93, 101]}, {"key": "staff-costs", "type": "clause", "offset": [168, 179]}, {"key": "periodic-reports", "type": "definition", "offset": [210, 226]}, {"key": "work-package-number", "type": "clause", "offset": [228, 247]}, {"key": "lead-beneficiary", "type": "definition", "offset": [252, 268]}, {"key": "month-1", "type": "definition", "offset": [329, 336]}, {"key": "collection-of-information", "type": "clause", "offset": [512, 537]}, {"key": "general-principles", "type": "clause", "offset": [542, 560]}, {"key": "capacity-planning", "type": "clause", "offset": [587, 604]}, {"key": "capacity-allocation-process", "type": "definition", "offset": [609, 636]}, {"key": "an-overview", "type": "clause", "offset": [745, 756]}, {"key": "concerning-the", "type": "clause", "offset": [885, 899]}, {"key": "future-capacity", "type": "definition", "offset": [930, 945]}, {"key": "in-order-to", "type": "clause", "offset": [1041, 1052]}, {"key": "regulatory-bodies", "type": "definition", "offset": [1101, 1118]}, {"key": "different-capacity", "type": "definition", "offset": [1196, 1214]}, {"key": "the-pre", "type": "clause", "offset": [1264, 1271]}, {"key": "calculation-of", "type": "clause", "offset": [1615, 1629]}, {"key": "consultation-process", "type": "clause", "offset": [1662, 1682]}, {"key": "sncf-r\u00e9seau", "type": "definition", "offset": [1856, 1867]}, {"key": "anticipated-effects", "type": "clause", "offset": [2097, 2116]}, {"key": "development-and-planning", "type": "clause", "offset": [2200, 2224]}, {"key": "exchange-of-data", "type": "clause", "offset": [2227, 2243]}, {"key": "all-phases", "type": "clause", "offset": [2247, 2257]}, {"key": "communication-of", "type": "clause", "offset": [2297, 2313]}, {"key": "specific-capacity", "type": "definition", "offset": [2327, 2344]}, {"key": "allocation-procedures", "type": "clause", "offset": [2400, 2421]}, {"key": "affected-by", "type": "definition", "offset": [2434, 2445]}, {"key": "advance-planning", "type": "clause", "offset": [2531, 2547]}, {"key": "the-future", "type": "clause", "offset": [2622, 2632]}, {"key": "planning-principles", "type": "clause", "offset": [2668, 2687]}, {"key": "planning-process", "type": "clause", "offset": [2920, 2936]}, {"key": "competent-authorities", "type": "clause", "offset": [2948, 2969]}, {"key": "the-rules", "type": "clause", "offset": [3042, 3051]}, {"key": "the-model", "type": "clause", "offset": [3228, 3237]}, {"key": "in-case-of", "type": "clause", "offset": [3379, 3389]}, {"key": "final-model", "type": "clause", "offset": [3477, 3488]}, {"key": "the-timetable", "type": "clause", "offset": [3551, 3564]}, {"key": "subject-to-the", "type": "clause", "offset": [3576, 3590]}, {"key": "line-section", "type": "definition", "offset": [3640, 3652]}, {"key": "set-aside", "type": "clause", "offset": [3656, 3665]}, {"key": "passenger-traffic", "type": "definition", "offset": [3726, 3743]}, {"key": "capacity-products", "type": "definition", "offset": [3849, 3866]}, {"key": "market-segments", "type": "definition", "offset": [3894, 3909]}, {"key": "number-of", "type": "definition", "offset": [4059, 4068]}, {"key": "no-changes", "type": "clause", "offset": [4178, 4188]}, {"key": "of-changes", "type": "clause", "offset": [4230, 4240]}, {"key": "period-from", "type": "definition", "offset": [4284, 4295]}, {"key": "based-on", "type": "definition", "offset": [4356, 4364]}, {"key": "construction-planning", "type": "clause", "offset": [4376, 4397]}, {"key": "specific-number", "type": "definition", "offset": [4519, 4534]}, {"key": "management-tool", "type": "clause", "offset": [4654, 4669]}, {"key": "new-form", "type": "definition", "offset": [4702, 4710]}, {"key": "user-role", "type": "definition", "offset": [4775, 4784]}, {"key": "be-prepared", "type": "clause", "offset": [4791, 4802]}, {"key": "additional-parameters", "type": "clause", "offset": [5018, 5039]}, {"key": "necessary-information", "type": "clause", "offset": [5077, 5098]}, {"key": "interpretation-of-the", "type": "clause", "offset": [5183, 5204]}, {"key": "day-of", "type": "clause", "offset": [5404, 5410]}, {"key": "the-planned", "type": "clause", "offset": [5706, 5717]}, {"key": "an-hourly-basis", "type": "clause", "offset": [5732, 5747]}, {"key": "the-selected", "type": "clause", "offset": [5752, 5764]}, {"key": "block-diagram", "type": "clause", "offset": [5774, 5787]}, {"key": "the-network", "type": "definition", "offset": [5843, 5854]}, {"key": "network-overview", "type": "clause", "offset": [5858, 5874]}, {"key": "booked-capacity", "type": "definition", "offset": [5905, 5920]}, {"key": "the-object", "type": "clause", "offset": [6065, 6075]}, {"key": "to-provide", "type": "clause", "offset": [6184, 6194]}, {"key": "single-source", "type": "clause", "offset": [6349, 6362]}, {"key": "the-information", "type": "clause", "offset": [6588, 6603]}, {"key": "an-object", "type": "definition", "offset": [6781, 6790]}, {"key": "the-applicants", "type": "clause", "offset": [6836, 6850]}, {"key": "will-serve", "type": "definition", "offset": [7057, 7067]}, {"key": "more-details", "type": "clause", "offset": [7372, 7384]}, {"key": "the-national", "type": "clause", "offset": [7954, 7966]}, {"key": "the-requirements", "type": "clause", "offset": [8399, 8415]}, {"key": "change-requests", "type": "clause", "offset": [8459, 8474]}, {"key": "the-development", "type": "clause", "offset": [8508, 8523]}, {"key": "results-of-the", "type": "clause", "offset": [8542, 8556]}, {"key": "the-performance", "type": "clause", "offset": [8662, 8677]}, {"key": "the-application", "type": "clause", "offset": [8681, 8696]}, {"key": "effectiveness-of-the", "type": "clause", "offset": [8730, 8750]}, {"key": "shall-be-measured", "type": "clause", "offset": [8761, 8778]}, {"key": "timetable-year", "type": "definition", "offset": [8941, 8955]}, {"key": "frequency-of", "type": "clause", "offset": [9068, 9080]}, {"key": "preparation-for", "type": "clause", "offset": [9105, 9120]}, {"key": "requirements-for", "type": "clause", "offset": [9165, 9181]}, {"key": "applicants-for", "type": "definition", "offset": [9583, 9597]}], "size": 1, "hash": "a486d5f2bf2c42d29e57610e69a522ea", "id": 8}, {"samples": [{"hash": "8r5fxrZ3Tp", "uri": "/contracts/8r5fxrZ3Tp#technical-coordination", "label": "Contract", "score": 31.3445129395, "published": true}], "snippet": "C.1.25.1. Performance of work under this contract shall be in compliance with the contract and any approved documents associated with thiscontract.\nC.1.25.2. All technical coordination shall be within the general scope of this contract. Technical coordination shall not result in any action that:\nC.1.25.2.1. Constitutes an assignment of additional work outside contract.\nC.1.25.2.2. Causes an increase in the total estimated cost, the resource limits approved by the KO in the approved Implementation Plan, or the time required for contract performance.\nC.1.25.2.3. Changes in any of the expressed terms, conditions, or specifications of this contract.\nC.1.25.2.4. Interferes with the contractor's right to perform the terms and conditions of this contract.", "snippet_links": [{"key": "performance-of-work", "type": "clause", "offset": [10, 29]}, {"key": "under-this-contract", "type": "clause", "offset": [30, 49]}, {"key": "compliance-with-the-contract", "type": "clause", "offset": [62, 90]}, {"key": "approved-documents", "type": "clause", "offset": [99, 117]}, {"key": "associated-with", "type": "definition", "offset": [118, 133]}, {"key": "scope-of-this-contract", "type": "clause", "offset": [213, 235]}, {"key": "in-any-action", "type": "clause", "offset": [277, 290]}, {"key": "assignment-of-additional-work", "type": "clause", "offset": [324, 353]}, {"key": "total-estimated-cost", "type": "clause", "offset": [410, 430]}, {"key": "resource-limits", "type": "clause", "offset": [436, 451]}, {"key": "approved-by", "type": "definition", "offset": [452, 463]}, {"key": "implementation-plan", "type": "clause", "offset": [487, 506]}, {"key": "time-required", "type": "clause", "offset": [515, 528]}, {"key": "contract-performance", "type": "clause", "offset": [533, 553]}, {"key": "changes-in", "type": "clause", "offset": [567, 577]}, {"key": "the-contractor", "type": "clause", "offset": [682, 696]}, {"key": "right-to-perform", "type": "clause", "offset": [699, 715]}, {"key": "terms-and-conditions-of-this-contract", "type": "clause", "offset": [720, 757]}], "size": 1, "hash": "291e72a8bccdc6bd38386294708fecad", "id": 9}, {"samples": [{"hash": "gmkS3EokZKt", "uri": "/contracts/gmkS3EokZKt#technical-coordination", "label": "Contract", "score": 29.9019203186, "published": true}], "snippet": "1) Performance of work under this contract shall be in compliance with the PWS, terms, and conditions of any approved Task Orders. The contractor shall use the PWS together with other applicable portions of the basic award as a basis for the description of its capabilities and ability to propose appropriate services when solicited in future Task Orders.\n2) All technical coordination shall remain within the scope of this contract and that of individual Task Orders. No oral statements of any person whosoever shall in any manner or degree modify or otherwise affect the terms of this contract or of the Task Orders. Technical coordination shall not result in any action that:\ni. Constitutes an assignment of additional work outside the SOW, PWS or Task Order.\nii. Constitutes a change as defined in the contract clauses 52.243-1, Changes - Fixed-Price, as applicable.\niii. Causes an increase in the total contract ceiling amount, TO price, or the time required for contract or Task Order performance.\niv. Changes in any of the expressed terms, conditions or specifications of this contract or any approved Task Orders.\nv. Interfere with the contractor\u2019s right to perform the terms and conditions of the contract. CLAUSES INCORPORATED BY REFERENCE 52.232-19 Availability Of Funds For The Next Fiscal Year APR 1984 252.204-7006 Billing Instructions OCT 2005 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports JUN 2012 252.232-7006 Wide Area WorkFlow Payment Instructions MAY 2013 252.232-7007 Limitation Of Government's Obligation APR 2014 CLAUSES INCORPORATED BY FULL TEXT 97X4930.5F20 000 C1013 0 068142 2F Contracting Officer Name: \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 (\u2587\u2587\u2587\u2587) \u2587\u2587\u2587\u2587\u2587\u2587\u2587 Organization/Office Symbol: DISA/DITCO/PL8414 Phone No.: \u2587\u2587\u2587-\u2587\u2587\u2587-\u2587\u2587\u2587\u2587 E-Mail Address: \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587.\u2587\u2587\u2587\u2587\u2587\u2587.civ@\u2587\u2587\u2587\u2587.\u2587\u2587\u2587 Contract Specialist Name: \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587 Organization/Office Symbol: DISA/DITCO/PL8414 Phone No.: \u2587\u2587\u2587-\u2587\u2587\u2587-\u2587\u2587\u2587\u2587 E-Mail Address: \u2587\u2587\u2587\u2587\u2587\u2587.\u2587.\u2587\u2587\u2587\u2587.civ@\u2587\u2587\u2587\u2587.\u2587\u2587\u2587 COR/Mission Partner Point of Contact (Note: To be filled in upon contract award) Name: Organization/Office Symbol: Phone No.: E-Mail Address: Contractor Point of Contact Contractor Legal Business Name: DUNS: CAGE CODE: Contractor POC: Phone Number: E-Mail Address: (End of text) Timely contract closeout is a priority under this contract/order. The Contractor shall submit a final invoice within ninety (90) calendar days after the expiration of this contract/order, unless the Contractor requests and is granted an extension by the Contracting Officer, in writing. In addition, and concurrent with the submission of the final invoice, the Contractor shall notify the Contracting Officer of the amount of excess funds that can be deobligated from this contract/order so the closeout process can begin as soon as possible upon expiration of this contract/order. A bilateral contract/order closeout modification will be forwarded to the Contractor by the Contracting Officer and must be signed by the Contractor and returned to the Contracting Officer within thirty (30) calendar days of issuance of the modification. A Contractor\u2019s failure to respond and/or sign the bilateral closeout modification within thirty", "snippet_links": [{"key": "performance-of-work", "type": "clause", "offset": [3, 22]}, {"key": "under-this-contract", "type": "clause", "offset": [23, 42]}, {"key": "compliance-with-the", "type": "clause", "offset": [55, 74]}, {"key": "task-orders", "type": "definition", "offset": [118, 129]}, {"key": "the-contractor-shall", "type": "clause", "offset": [131, 151]}, {"key": "other-applicable", "type": "clause", "offset": [178, 194]}, {"key": "basic-award", "type": "definition", "offset": [211, 222]}, {"key": "description-of", "type": "definition", "offset": [242, 256]}, {"key": "ability-to", "type": "clause", "offset": [278, 288]}, {"key": "scope-of-this-contract", "type": "clause", "offset": [410, 432]}, {"key": "oral-statements", "type": "clause", "offset": [472, 487]}, {"key": "any-person", "type": "definition", "offset": [491, 501]}, {"key": "terms-of-this-contract", "type": "clause", "offset": [573, 595]}, {"key": "in-any-action", "type": "clause", "offset": [659, 672]}, {"key": "assignment-of-additional-work", "type": "clause", "offset": [697, 726]}, {"key": "contract-clauses", "type": "clause", "offset": [806, 822]}, {"key": "the-total", "type": "clause", "offset": [898, 907]}, {"key": "ceiling-amount", "type": "clause", "offset": [917, 931]}, {"key": "time-required", "type": "clause", "offset": [950, 963]}, {"key": "task-order-performance", "type": "clause", "offset": [980, 1002]}, {"key": "changes-in", "type": "clause", "offset": [1008, 1018]}, {"key": "right-to-perform", "type": "clause", "offset": [1157, 1173]}, {"key": "terms-and-conditions-of-the-contract", "type": "clause", "offset": [1178, 1214]}, {"key": "clauses-incorporated-by-reference", "type": "clause", "offset": [1216, 1249]}, {"key": "availability-of-funds-for-the-next-fiscal-year", "type": "clause", "offset": [1260, 1306]}, {"key": "billing-instructions", "type": "definition", "offset": [1329, 1349]}, {"key": "submission-of-payment-requests", "type": "clause", "offset": [1383, 1413]}, {"key": "wide-area", "type": "definition", "offset": [1458, 1467]}, {"key": "payment-instructions", "type": "definition", "offset": [1477, 1497]}, {"key": "limitation-of", "type": "clause", "offset": [1520, 1533]}, {"key": "clauses-incorporated-by-full-text", "type": "clause", "offset": [1567, 1600]}, {"key": "contracting-officer-name", "type": "clause", "offset": [1636, 1660]}, {"key": "phone-no", "type": "clause", "offset": [1733, 1741]}, {"key": "mail-address", "type": "definition", "offset": [1759, 1771]}, {"key": "contract-specialist", "type": "clause", "offset": [1804, 1823]}, {"key": "contract-award", "type": "definition", "offset": [2020, 2034]}, {"key": "contractor-point-of-contact", "type": "clause", "offset": [2097, 2124]}, {"key": "legal-business-name", "type": "definition", "offset": [2136, 2155]}, {"key": "phone-number", "type": "definition", "offset": [2190, 2202]}, {"key": "contract-closeout", "type": "definition", "offset": [2241, 2258]}, {"key": "final-invoice", "type": "definition", "offset": [2330, 2343]}, {"key": "days-after", "type": "definition", "offset": [2372, 2382]}, {"key": "expiration-of", "type": "clause", "offset": [2387, 2400]}, {"key": "the-contracting", "type": "clause", "offset": [2484, 2499]}, {"key": "in-writing", "type": "clause", "offset": [2509, 2519]}, {"key": "in-addition", "type": "clause", "offset": [2521, 2532]}, {"key": "the-final", "type": "clause", "offset": [2572, 2581]}, {"key": "notify-the", "type": "clause", "offset": [2612, 2622]}, {"key": "excess-funds", "type": "clause", "offset": [2660, 2672]}, {"key": "closeout-process", "type": "clause", "offset": [2729, 2745]}, {"key": "as-soon-as-possible", "type": "definition", "offset": [2756, 2775]}, {"key": "upon-expiration", "type": "clause", "offset": [2776, 2791]}, {"key": "bilateral-contract", "type": "definition", "offset": [2818, 2836]}, {"key": "contractor-by", "type": "definition", "offset": [2890, 2903]}, {"key": "by-the-contractor", "type": "clause", "offset": [2947, 2964]}, {"key": "within-thirty", "type": "clause", "offset": [3005, 3018]}, {"key": "the-modification", "type": "clause", "offset": [3053, 3069]}, {"key": "a-contractor", "type": "clause", "offset": [3071, 3083]}, {"key": "failure-to-respond", "type": "clause", "offset": [3086, 3104]}], "size": 1, "hash": "f2870a397e5244df39aeda5d82ccf22a", "id": 10}], "next_curs": "Cl8SWWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjsLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ih90ZWNobmljYWwtY29vcmRpbmF0aW9uIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"parents": [["procedures-for-notification", "Procedures for Notification"], ["deliverables", "DELIVERABLES"], ["roles-and-responsibilities", "ROLES AND RESPONSIBILITIES"], ["amendments", "Amendments"], ["deliverables-list", "Deliverables list"]], "children": [["calculation-of-azimuth", "Calculation of Azimuth"], ["computation-of-distance", "Computation of Distance"]], "size": 13, "title": "Technical coordination", "id": "technical-coordination", "related": [["project-coordination", "Project Coordination", "Project Coordination"], ["technical-cooperation", "Technical Cooperation", "Technical Cooperation"], ["project-management-and-coordination", "Project Management and Coordination", "Project Management and Coordination"], ["utility-coordination", "Utility Coordination", "Utility Coordination"], ["cooperation-and-coordination", "Cooperation and Coordination", "Cooperation and Coordination"]], "related_snippets": [], "updated": "2025-07-10T05:58:13+00:00"}, "json": true, "cursor": ""}}