{"component": "clause", "props": {"groups": [{"snippet_links": [{"key": "to-employ", "type": "clause", "offset": [23, 32]}, {"key": "common-equipment", "type": "definition", "offset": [33, 49]}, {"key": "in-place", "type": "definition", "offset": [58, 66]}, {"key": "the-internet", "type": "clause", "offset": [82, 94]}, {"key": "world-wide-web", "type": "definition", "offset": [96, 110]}, {"key": "communications-network", "type": "clause", "offset": [132, 154]}, {"key": "for-example", "type": "definition", "offset": [174, 185]}, {"key": "integrated-service", "type": "definition", "offset": [190, 208]}, {"key": "digital-network", "type": "definition", "offset": [209, 224]}, {"key": "technological-equipment", "type": "definition", "offset": [263, 286]}, {"key": "video-teleconferencing", "type": "clause", "offset": [309, 331]}, {"key": "attention-of", "type": "clause", "offset": [384, 396]}, {"key": "mutual-agreement-of-the-parties", "type": "clause", "offset": [439, 470]}, {"key": "information-exchange", "type": "definition", "offset": [481, 501]}, {"key": "information-of", "type": "clause", "offset": [591, 605]}, {"key": "the-source", "type": "clause", "offset": [606, 616]}, {"key": "other-discussions", "type": "clause", "offset": [671, 688]}, {"key": "interest-on-the", "type": "clause", "offset": [699, 714]}, {"key": "emergency-event", "type": "clause", "offset": [779, 794]}, {"key": "in-the-event-of", "type": "definition", "offset": [808, 823]}, {"key": "evaluation-period", "type": "definition", "offset": [910, 927]}, {"key": "representatives-of", "type": "clause", "offset": [929, 947]}, {"key": "available-means", "type": "clause", "offset": [986, 1001]}, {"key": "electronic-mail", "type": "definition", "offset": [1030, 1045]}, {"key": "to-discuss", "type": "definition", "offset": [1047, 1057]}, {"key": "for-information", "type": "clause", "offset": [1092, 1107]}, {"key": "development-and-implementation", "type": "clause", "offset": [1132, 1162]}, {"key": "communications-link", "type": "clause", "offset": [1180, 1199]}, {"key": "the-parties-shall", "type": "clause", "offset": [1201, 1218]}, {"key": "emergency-information", "type": "clause", "offset": [1287, 1308]}, {"key": "exchange-programs", "type": "clause", "offset": [1309, 1326]}, {"key": "the-global", "type": "definition", "offset": [1338, 1348]}, {"key": "information-network", "type": "clause", "offset": [1370, 1389]}, {"key": "activities-of-the", "type": "clause", "offset": [1441, 1458]}, {"key": "international-atomic-energy-agency", "type": "definition", "offset": [1459, 1493]}], "snippet": "(i) The Parties expect to employ common equipment already in place and to utilize the Internet, World Wide Web or other appropriate communications network or infrastructure (for example, or Integrated Service Digital Network). Problems regarding compatibility of technological equipment (e.g., band width for video teleconferencing and alphanumeric transfers) shall be brought to the attention of the Parties and expeditiously resolved by mutual agreement of the Parties.\n(ii) The information exchange will be limited to atmospheric dispersion modeling products, graphical displays, textual information of the source term and predictive results, and teleconferencing and other discussions of mutual interest on the information exchange, during hypothetical, non-military nuclear emergency event simulations. In the event of an actual non- military, nuclear emergency event during the prototype development and evaluation period, representatives of JAERI and DOE will confer by the best available means (e.g., phone, facsimile, or electronic mail) to discuss utilization of the prototype link for information exchange.\nB. During the development and implementation of the prototype communications link, the Parties shall explore relationships of this information exchange program to other emergency information exchange programs, including the Global Emergency Management Information Network Initiative project as well as related programs and activities of the International Atomic Energy Agency.", "samples": [{"hash": "7j4JojwpZnD", "uri": "/contracts/7j4JojwpZnD#technical-scope", "label": "Memorandum of Agreement", "score": 24.6673511294, "published": true}, {"hash": "8UupGPCXm5x", "uri": "/contracts/8UupGPCXm5x#technical-scope", "label": "Memorandum of Agreement", "score": 24.1704312115, "published": true}], "size": 2, "hash": "952e71e8eebaa79fa8c16d65b610fbe4", "id": 1}, {"snippet_links": [{"key": "other-components", "type": "clause", "offset": [146, 162]}, {"key": "the-value", "type": "clause", "offset": [166, 175]}, {"key": "the-supplier", "type": "clause", "offset": [206, 218]}, {"key": "proposed-solution", "type": "clause", "offset": [221, 238]}, {"key": "user-requirements", "type": "clause", "offset": [357, 374]}, {"key": "separate-system", "type": "definition", "offset": [378, 393]}, {"key": "existing-systems", "type": "definition", "offset": [493, 509]}, {"key": "the-business", "type": "clause", "offset": [516, 528]}, {"key": "the-system", "type": "definition", "offset": [654, 664]}, {"key": "appendix-1", "type": "clause", "offset": [682, 692]}, {"key": "section-33", "type": "clause", "offset": [694, 705]}, {"key": "for-more-information", "type": "clause", "offset": [714, 734]}, {"key": "section-32", "type": "definition", "offset": [759, 770]}, {"key": "further-description-of-the", "type": "clause", "offset": [810, 836]}, {"key": "the-scope", "type": "clause", "offset": [861, 870]}], "snippet": "\u200c The high-level scope for this procurement is illustrated in the figure below coloured in red. The figure includes the origin solution, but also other components in the value-chain to give a full picture. The Supplier\u2019s proposed solution could differ from the illustration, however in areas where NRK has very bespoke needs or expects changing business or user requirements, a separate system or integration is preferred to an \u201call-in-one\u201d solution. Likewise, the integration between new and existing systems where the business logic or domain is important and may change due to changing business flows or requirements, NRK wants to own or be a part of the system-integration, see Appendix 1, section 3.3 and 6.5 for more information. Please see Appendix 1, section 3.2 (green itmes) and 3.3 (blue items) for further description of the figure. Requirements to the scope is further detailed in Appendix 1, chapter 6.", "samples": [{"hash": "k9RPeqLt9my", "uri": "/contracts/k9RPeqLt9my#technical-scope", "label": "Contract for Live/Live to Vod Origin", "score": 30.3747779966, "published": true}], "size": 2, "hash": "ca484c05cde9bfe528996dc742307086", "id": 2}, {"snippet_links": [{"key": "the-requirements", "type": "clause", "offset": [20, 36]}, {"key": "associated-with", "type": "definition", "offset": [37, 52]}, {"key": "the-installation", "type": "clause", "offset": [53, 69]}, {"key": "control-systems", "type": "clause", "offset": [114, 129]}, {"key": "county-jail", "type": "definition", "offset": [142, 153]}, {"key": "public-safety", "type": "clause", "offset": [175, 188]}, {"key": "county-building", "type": "definition", "offset": [204, 219]}, {"key": "the-vendor", "type": "clause", "offset": [249, 259]}, {"key": "all-equipment", "type": "clause", "offset": [296, 309]}, {"key": "to-provide", "type": "definition", "offset": [357, 367]}, {"key": "working-order", "type": "clause", "offset": [425, 438]}, {"key": "power-supplies", "type": "clause", "offset": [552, 566]}, {"key": "proposed-system", "type": "definition", "offset": [717, 732]}, {"key": "turnkey-solution", "type": "definition", "offset": [782, 798]}, {"key": "software-operation", "type": "clause", "offset": [882, 900]}, {"key": "technical-support", "type": "clause", "offset": [933, 950]}, {"key": "software-upgrades", "type": "clause", "offset": [980, 997]}, {"key": "the-work", "type": "definition", "offset": [1050, 1058]}, {"key": "to-the-county", "type": "definition", "offset": [1072, 1085]}, {"key": "fully-operational", "type": "definition", "offset": [1108, 1125]}, {"key": "telephone-support", "type": "definition", "offset": [1154, 1171]}, {"key": "same-day", "type": "definition", "offset": [1176, 1184]}, {"key": "serious-incidents", "type": "definition", "offset": [1222, 1239]}, {"key": "equipment-failure", "type": "clause", "offset": [1243, 1260]}, {"key": "site-support", "type": "clause", "offset": [1280, 1292]}, {"key": "hours-of", "type": "clause", "offset": [1320, 1328]}, {"key": "notification-of", "type": "definition", "offset": [1329, 1344]}, {"key": "not-limited", "type": "clause", "offset": [1388, 1399]}, {"key": "substantially-affect", "type": "definition", "offset": [1441, 1461]}, {"key": "county-sheriff", "type": "definition", "offset": [1516, 1530]}, {"key": "vendor-will", "type": "clause", "offset": [1545, 1556]}, {"key": "office-staff", "type": "clause", "offset": [1609, 1621]}, {"key": "to-ensure", "type": "clause", "offset": [1664, 1673]}, {"key": "completion-of-the-project", "type": "definition", "offset": [1685, 1710]}], "snippet": "This section covers the requirements associated with the installation, additions and replacements of the Security Control systems in the Dane County Jail. Specifically in the Public Safety Building, City-County Building, and Dane County Courthouse. The vendor is to furnish a price that includes all equipment, materials, labor, engineering and programming to provide complete and professionally installed systems in optimum working order. Vendor is to furnish a price that includes any and all connectors, cable strain relief, hardware, transformers, power supplies, rack panels, interfaces, fasteners, wire harnessing material, bushings and any other incidentals required for complete and proper functioning of the proposed system. The Security Control systems proposed must be a turnkey solution. Vendor is to provide Dane County, in-person training on the installed systems and software operation. Vendor is to provide 1 year of technical support on the entire system and any software upgrades that become available and will commence on the date the work is completed to the County\u2019s satisfaction and is fully operational. This support shall include telephone support the same day as reported problem or question. For serious incidents of equipment failure or malfunction, on-site support shall be provided within 2 hours of notification of problem. Serious incidents include but are not limited to any failure or malfunction which will substantially affect jail security or operations as determined by the Dane County Sheriff\u2019s Office. The vendor will consult and work closely with Dane County Sheriff\u2019s Office staff before, during and after the installation to ensure successful completion of the project.", "samples": [{"hash": "5MoWxRIy4NH", "uri": "/contracts/5MoWxRIy4NH#technical-scope", "label": "Service Maintenance Agreement", "score": 22.083504449, "published": true}], "size": 1, "hash": "d16254cf0a5e79ab2516a2c793fd3a77", "id": 3}, {"snippet_links": [{"key": "scope-of", "type": "definition", "offset": [15, 23]}, {"key": "agr-eement", "type": "definition", "offset": [41, 51]}, {"key": "i-s", "type": "clause", "offset": [52, 55]}], "snippet": "The Techni cal Scope of t hi s Pr oj ect Agr eement i s pr ovi ded as Appendi x A.", "samples": [{"hash": "5n6xgYXuAl6", "uri": "/contracts/5n6xgYXuAl6#technical-scope", "label": "Project Agreement", "score": 24.6714579055, "published": true}], "size": 1, "hash": "b6f4b8dd5a0157f4b5149ebf9dc495af", "id": 4}, {"snippet_links": [{"key": "internet-browser", "type": "definition", "offset": [104, 120]}, {"key": "login-credentials", "type": "definition", "offset": [149, 166]}, {"key": "smart-phone", "type": "clause", "offset": [305, 316]}, {"key": "provide-the", "type": "clause", "offset": [503, 514]}, {"key": "cell-phone-number", "type": "definition", "offset": [515, 532]}, {"key": "access-to", "type": "definition", "offset": [658, 667]}, {"key": "provide-a", "type": "definition", "offset": [763, 772]}, {"key": "email-address", "type": "definition", "offset": [780, 793]}, {"key": "the-organization", "type": "definition", "offset": [887, 903]}, {"key": "user-training", "type": "definition", "offset": [947, 960]}, {"key": "go-live", "type": "clause", "offset": [1050, 1057]}], "snippet": "Both CDS and PASS are cloud-based applications accessible via the web using either MS Chrome or MS Edge internet browser. Each User will have secure login credentials required to access the application(s). The CDS application requires multi-factor authentication (\u201cMFA\u201d). Therefore, each Users must use a smart phone and download an approved MFA application to access the CDS application. Approved MFA applications are: Okta Verify, Google Authenticator, and Microsoft Authenticator. Users will need to provide the cell phone number for the smart phone they will use for the MFA to IHIE.MFA verification is required every 24hours. Therefore, Users will need access to their work/personal cell phone to perform the authentication to access CDS. Users will need to provide a secure email address to IHIE to enroll in the MFA process. The email address should be a secure email supplied by the organization (not Gmail/Hotmail/Yahoo, AOL, etc.) Group User Training (live, recorded, webcast, and/or printed) will be provided during the implementation and Go Live period.", "samples": [{"hash": "6afAS1HmARP", "uri": "/contracts/6afAS1HmARP#technical-scope", "label": "Subscription Agreement", "score": 23.0923645323, "published": true}], "size": 1, "hash": "9fae3404c37af78e49cc5f81d45282ee", "id": 5}, {"snippet_links": [{"key": "the-contractor-must", "type": "clause", "offset": [3, 22]}, {"key": "time-employee", "type": "clause", "offset": [37, 50]}, {"key": "to-maintain", "type": "clause", "offset": [51, 62]}, {"key": "power-station", "type": "definition", "offset": [82, 95]}, {"key": "allocated-to", "type": "definition", "offset": [181, 193]}, {"key": "this-contract", "type": "clause", "offset": [194, 207]}, {"key": "the-contractor-will", "type": "clause", "offset": [252, 271]}, {"key": "work-orders", "type": "clause", "offset": [334, 345]}, {"key": "maintenance-strategy", "type": "clause", "offset": [407, 427]}, {"key": "the-systems", "type": "clause", "offset": [432, 443]}, {"key": "according-to", "type": "definition", "offset": [448, 460]}, {"key": "termination-of", "type": "definition", "offset": [528, 542]}, {"key": "certification-of", "type": "clause", "offset": [701, 717]}, {"key": "contract-commencement", "type": "clause", "offset": [811, 832]}, {"key": "will-work", "type": "clause", "offset": [848, 857]}, {"key": "provide-own", "type": "clause", "offset": [990, 1001]}, {"key": "all-contractors", "type": "clause", "offset": [1056, 1071]}, {"key": "medically-fit", "type": "definition", "offset": [1078, 1091]}, {"key": "work-and", "type": "clause", "offset": [1103, 1111]}, {"key": "medical-certificates", "type": "clause", "offset": [1136, 1156]}, {"key": "continuous-improvement", "type": "clause", "offset": [1199, 1221]}, {"key": "monthly-report", "type": "clause", "offset": [1310, 1324]}, {"key": "the-plant", "type": "clause", "offset": [1328, 1337]}, {"key": "compliance-report", "type": "clause", "offset": [1349, 1366]}, {"key": "when-required", "type": "definition", "offset": [1453, 1466]}, {"key": "current-system", "type": "clause", "offset": [1518, 1532]}, {"key": "the-contractor-shall", "type": "clause", "offset": [1545, 1565]}, {"key": "new-system", "type": "definition", "offset": [1603, 1613]}], "snippet": "1. The contractor must supply a full-time employee to maintain the BMS at Matimba Power Station on a 24/7 basis including callouts during emergencies.\n2. The contractors\u2019 employees allocated to this contract need to be security cleared by the SAPS.\n3. The contractor will execute all BMS related Corrective (CM) and Preventative (PM) work orders generated on the SAP Maintenance system and in line with the Maintenance Strategy for the systems and according to the RWM process.\n4. Maintenance includes repairs, replacement, and termination of all BMS cables and fibre optic cables, networks and network cables and relevant servers for each system.\n5. Maintenance includes annual calibration and SANAS certification of the Trek Weigh Bridge.\n6. The contractor will be ORHVS module1 authorised within 6 months of contract commencement.\n7. Contractor will work without assistance from Eskom Employees.\n8. The contractor must report and recommend solutions of repeat failures.\n9. Contractor to provide own PPE, equipment and all the tools to execute work.\n10. All contractors to be medically fit to execute work and shall supply Eskom with medical certificates.\n11. Contractor may propose and implement continuous improvement including modifications once granted permission to do so.\n12. Contractor shall submit a monthly report on the plant health and compliance report.\n13. The contractor must be able to expand and do installations on the systems if and when required.\n14. If ever a modification is implemented and the current system is changed, the contractor shall continue with the maintenance on the new system.", "samples": [{"hash": "h6w158RgIYr", "uri": "/contracts/h6w158RgIYr#technical-scope", "label": "Nec3 Term Service Contract (Tsc3)", "score": 34.0810562808, "published": true}], "size": 1, "hash": "c05b17ec794678e1c31813a56abf3712", "id": 6}, {"snippet_links": [{"key": "the-project", "type": "clause", "offset": [0, 11]}, {"key": "a-tender", "type": "definition", "offset": [23, 31]}, {"key": "processing-equipment", "type": "definition", "offset": [68, 88]}], "snippet": "The project will issue a tender to procure the beekeeping and honey processing equipment as follows:\n1. Bee venom collector\n2. Electric wax extractor\n3. Heat induction machine\n4. Honey warmer tank\n5. Frame grip\n6. Uncapping tray\n7. Manual honey extractor\n8. Bee queen rearing kit\n9. Beekeeping moving grafting tools Enabel \u2022 Belgian development agency \u2022 Public-law company with social purposes Rue Haute 147 \u2022 1000 Brussels \u2022 T +\u2587\u2587 (\u2587)\u2587 \u2587\u2587\u2587 \u2587\u2587 \u2587\u2587 \u2022 \u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\n10. Queen marking tube and pen 11. Queen catcher", "samples": [{"hash": "iO13Bu39dKc", "uri": "/contracts/iO13Bu39dKc#technical-scope", "label": "Public Contract for the Supply and Installation of Equipment", "score": 34.3242243984, "published": true}], "size": 1, "hash": "ddea6923ebd5cd3a441d6686d3a66c90", "id": 7}, {"snippet_links": [{"key": "professional-association", "type": "clause", "offset": [107, 131]}, {"key": "insurance-agents", "type": "clause", "offset": [135, 151]}, {"key": "and-insurance", "type": "clause", "offset": [152, 165]}, {"key": "the-book", "type": "clause", "offset": [213, 221]}, {"key": "subject-to-the", "type": "definition", "offset": [287, 301]}, {"key": "agreement-for", "type": "clause", "offset": [324, 337]}, {"key": "with-respect-to", "type": "clause", "offset": [461, 476]}, {"key": "prior-to", "type": "definition", "offset": [497, 505]}], "snippet": "For all companies belonging to the Sectoral Section Commerce of the Austrian Federal Economic Chamber, the Professional Association of Insurance Agents and Insurance Consultants or the Professional Association of the Book and Media Industry with the following exceptions:\n2.1. companies subject to the Collective Bargaining Agreement for White-collar Workers in Pharmaceutical Wholesale Companies.\n2.2. OMV-Aktiengesellschaft\n2.3. VOEST-ALPINE STAHLHANDEL GmbH with respect to employees recruited prior to 1 March 2000; VOEST-ALPINE Rohstoffhandel Gesellschaft m.b.H., Vienna (VAR) and Verkaufsstelle \u00f6sterreichischer Kalt- walzwerke Ges.m.b.H., Vienna (V\u00d6K).\n2.4. General-Motors-Austria Ges.m.b.H.", "samples": [{"hash": "5uTTgAEmM1L", "uri": "/contracts/5uTTgAEmM1L#technical-scope", "label": "Collective Bargaining Agreement", "score": 21.0711841205, "published": true}], "size": 1, "hash": "721682e54ecf04fd66e500b6702a137b", "id": 8}, {"snippet_links": [{"key": "services-and", "type": "clause", "offset": [62, 74]}, {"key": "analytical-services", "type": "definition", "offset": [93, 112]}, {"key": "national-security", "type": "clause", "offset": [190, 207]}, {"key": "dual-use", "type": "clause", "offset": [221, 229]}, {"key": "development-of", "type": "clause", "offset": [295, 309]}, {"key": "the-mission", "type": "clause", "offset": [344, 355]}, {"key": "work-for", "type": "definition", "offset": [492, 500]}, {"key": "outside-the-united-states", "type": "definition", "offset": [600, 625]}, {"key": "secret-facility-clearance", "type": "clause", "offset": [644, 669]}, {"key": "staff-augmentation", "type": "clause", "offset": [780, 798]}, {"key": "support-services", "type": "definition", "offset": [799, 815]}, {"key": "research-and-analysis", "type": "clause", "offset": [830, 851]}], "snippet": "The broad technical scope described herein includes all RDT&E services and other R&D-related analytical services. These services may support all aspects of identified or potential military, national security-related, and dual use applications of related technologies and methods, as well as the development of tools and techniques that enhance the mission of the DoD Research and Engineering community. TOs can be multi-million dollar efforts, may involve multi-year performance, may involve work for other than DoD customers, may be performed at multiple worldwide locations (to include performance outside the United States), may require Top Secret facility clearance, and may require personnel clearances up to Top Secret (compartmented and collateral). TOs are not Government-staff augmentation support services. The level of research and analysis are above and beyond that provided by the BCOs.", "samples": [{"hash": "aU9NmSdy05A", "uri": "/contracts/aU9NmSdy05A#technical-scope", "label": "Contract", "score": 29.7349399482, "published": true}], "size": 1, "hash": "b715953a5e5a0cfb40d7ca9ff9cb5d29", "id": 9}, {"snippet_links": [{"key": "the-objective", "type": "clause", "offset": [0, 13]}, {"key": "this-action", "type": "definition", "offset": [17, 28]}, {"key": "the-cooperation", "type": "clause", "offset": [45, 60]}, {"key": "located-in", "type": "definition", "offset": [92, 102]}, {"key": "research-activities", "type": "clause", "offset": [220, 239]}, {"key": "thematic-priorities", "type": "clause", "offset": [297, 316]}, {"key": "work-programme", "type": "clause", "offset": [326, 340]}, {"key": "part-7", "type": "definition", "offset": [358, 364]}, {"key": "international-cooperation", "type": "clause", "offset": [380, 405]}, {"key": "development-of", "type": "clause", "offset": [424, 438]}, {"key": "regional-coverage", "type": "clause", "offset": [727, 744]}, {"key": "social-environment", "type": "clause", "offset": [824, 842]}, {"key": "job-opportunities", "type": "clause", "offset": [944, 961]}, {"key": "the-country", "type": "definition", "offset": [965, 976]}, {"key": "measures-to", "type": "clause", "offset": [999, 1010]}, {"key": "career-opportunities", "type": "clause", "offset": [1049, 1069]}, {"key": "work-conditions", "type": "clause", "offset": [1078, 1093]}, {"key": "access-to", "type": "definition", "offset": [1095, 1104]}], "snippet": "The objective of this action is to reinforce the cooperation capacities of research centres located in the ENP countries, which are not associated to FP7.The call will give these countries the possibility to improve the research activities of their highest quality and/or promising centres in the thematic priorities of FP7. (Work Programme 2011, Capacities Part 7, Activities of international cooperation, pg. 7) The joint development of training modules to build competency and facilitate participation of the research centres in FP7 should build on already existing expertise or successful collaboration experience.\u201d (Work Programme 2011, Capacities Part 7, Activities of international cooperation, pg. 9) \u201cIncreased scope (regional coverage, subjects, activities) of the centres with increased linkage with economic and social environment\u201d (Work Programme 2011, Capacities Part 7, Activities of international cooperation, pg. 9) \u201cIncreased job opportunities in the country for young scientists (measures to avoid \u201ebrain drain\u201f phenomena: better career opportunities, better work conditions, access to research)\u201d (Work Programme 2011, Capacities Part 7, Activities of international cooperation, pg. 9)", "samples": [{"hash": "hjBfmwjMRJY", "uri": "/contracts/hjBfmwjMRJY#technical-scope", "label": "Grant Agreement", "score": 19.9048596851, "published": true}], "size": 1, "hash": "be745ed6e1accdf5f89d0edebedc69ed", "id": 10}], "next_curs": "ClgSUmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjQLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ihh0ZWNobmljYWwtc2NvcGUjMDAwMDAwMGEMogECZW4YACAA", "clause": {"title": "Technical Scope", "parents": [["scope-of-procurement", "SCOPE OF PROCUREMENT"], ["demonstrations", "Demonstrations"], ["notification-of-intent-to-award", "Notification of Intent to Award"], ["mandatory-requirements", "Mandatory Requirements"], ["general-provisions", "General provisions"]], "children": [["plant-design-study-technical-support", "Plant Design Study - Technical Support"], ["plant-design-study-fees", "Plant Design Study - Fees"], ["\u00f6sterreichische-salinen-ag", "\u00d6sterreichische Salinen AG"], ["", ""], ["cyber-security-and-information-systems-domain-technical-focus-areas", "Cyber Security and Information Systems Domain Technical Focus Areas"]], "size": 15, "id": "technical-scope", "related": [["technical-specifications", "Technical Specifications", "Technical Specifications"], ["project-scope", "Project Scope", "Project Scope"], ["general-scope-of-work", "General Scope of Work", "General Scope of Work"], ["technical-specifications-and-drawings", "Technical Specifications and Drawings", "Technical Specifications and Drawings"], ["technical-evaluation", "TECHNICAL EVALUATION", "TECHNICAL EVALUATION"]], "related_snippets": [], "updated": "2025-07-07T12:37:48+00:00", "also_ask": [], "drafting_tip": "", "explanation": "The Technical Scope clause defines the specific technical requirements, deliverables, and boundaries of work to be performed under an agreement. It typically outlines the technologies, standards, and performance criteria that must be met, and may include detailed descriptions of tasks, milestones, or excluded activities. By clearly delineating what is and is not included in the technical aspects of a project, this clause helps prevent misunderstandings, scope creep, and disputes over responsibilities."}, "json": true, "cursor": ""}}