{"component": "clause", "props": {"groups": [{"samples": [{"hash": "UOcMnlRmWB", "uri": "/contracts/UOcMnlRmWB#technical-design", "label": "Contract for Design and Manufacture", "score": 25.9158110883, "published": true}, {"hash": "hrHq4WTZFuD", "uri": "/contracts/hrHq4WTZFuD#technical-design", "label": "Contract for Design, Manufacture, Assembly, Commissioning and Delivery of a Cutter Suction Dredger", "score": 25.6379192334, "published": true}], "snippet_links": [{"key": "all-information", "type": "clause", "offset": [0, 15]}, {"key": "technical-details", "type": "clause", "offset": [17, 34]}, {"key": "the-offer", "type": "clause", "offset": [66, 75]}, {"key": "goods-information", "type": "clause", "offset": [95, 112]}, {"key": "submitted-by", "type": "definition", "offset": [157, 169]}, {"key": "returnable-schedules", "type": "clause", "offset": [221, 241]}, {"key": "signed-and-dated", "type": "clause", "offset": [329, 345]}, {"key": "a-list", "type": "definition", "offset": [373, 379]}, {"key": "will-be-given", "type": "clause", "offset": [398, 411]}, {"key": "signed-date", "type": "clause", "offset": [441, 452]}, {"key": "name-position", "type": "clause", "offset": [453, 466]}], "size": 2, "snippet": "All information, technical details and/or data (or particulars of the offer) called for in the Goods Information or in the referenced specifications will be submitted by the tendering Supplier with his tender as separate returnable schedules in appropriate format. Each schedule will be titled to reflect its content and will be signed and dated by the tendering Supplier. A list of such schedules will be given in this returnable schedule. Signed Date Name Position Tenderer", "hash": "39986db87f09b9734c282f1966583fe8", "id": 3}, {"samples": [{"hash": "9dqIzD4xMaG", "uri": "/contracts/9dqIzD4xMaG#technical-design", "label": "Contract", "score": 18.5811088296, "published": true}, {"hash": "eAwVwwGKb6N", "uri": "/contracts/eAwVwwGKb6N#technical-design", "label": "Contract", "score": 18.5783709788, "published": true}, {"hash": "hYCVnfdwzuJ", "uri": "/contracts/hYCVnfdwzuJ#technical-design", "label": "Contract", "score": 18.575633128, "published": true}], "snippet_links": [{"key": "the-provider-shall", "type": "clause", "offset": [0, 18]}, {"key": "and-tools", "type": "clause", "offset": [42, 51]}, {"key": "the-market", "type": "definition", "offset": [96, 106]}, {"key": "a-technical", "type": "clause", "offset": [136, 147]}, {"key": "system-design", "type": "clause", "offset": [148, 161]}, {"key": "requirements-traceability-matrix", "type": "definition", "offset": [177, 209]}, {"key": "relationship-between", "type": "clause", "offset": [225, 245]}, {"key": "design-elements", "type": "clause", "offset": [263, 278]}, {"key": "the-design", "type": "clause", "offset": [327, 337]}, {"key": "provide-the", "type": "clause", "offset": [361, 372]}, {"key": "informal-review", "type": "definition", "offset": [399, 414]}, {"key": "information-and-documentation", "type": "clause", "offset": [415, 444]}, {"key": "system-development", "type": "clause", "offset": [471, 489]}, {"key": "the-technical", "type": "clause", "offset": [523, 536]}, {"key": "system-components", "type": "clause", "offset": [594, 611]}, {"key": "approval-of", "type": "clause", "offset": [708, 719]}, {"key": "updated-requirements", "type": "definition", "offset": [751, 771]}, {"key": "all-issues", "type": "definition", "offset": [843, 853]}, {"key": "approved-design", "type": "definition", "offset": [863, 878]}, {"key": "the-issues", "type": "clause", "offset": [952, 962]}, {"key": "issues-log", "type": "definition", "offset": [970, 980]}, {"key": "access-to-the", "type": "clause", "offset": [1088, 1101]}, {"key": "responsibilities-of-the-provider", "type": "clause", "offset": [1148, 1180]}, {"key": "design-responsibilities", "type": "clause", "offset": [1220, 1243]}, {"key": "design-deliverables", "type": "definition", "offset": [1273, 1292]}, {"key": "database-design", "type": "clause", "offset": [1316, 1331]}, {"key": "the-deliverables", "type": "clause", "offset": [1390, 1406]}, {"key": "review-and-approval-process", "type": "clause", "offset": [1491, 1518]}, {"key": "review-and-approve", "type": "clause", "offset": [1565, 1583]}, {"key": "reference-material", "type": "clause", "offset": [1676, 1694]}, {"key": "as-needed", "type": "clause", "offset": [1715, 1724]}, {"key": "design-phase", "type": "definition", "offset": [1726, 1738]}, {"key": "business-process-reengineering", "type": "clause", "offset": [1741, 1771]}, {"key": "state-department", "type": "definition", "offset": [1845, 1861]}, {"key": "business-processes", "type": "clause", "offset": [1874, 1892]}, {"key": "approved-system", "type": "definition", "offset": [1908, 1923]}, {"key": "new-business", "type": "clause", "offset": [1966, 1978]}, {"key": "the-future", "type": "clause", "offset": [2021, 2031]}, {"key": "state-business", "type": "definition", "offset": [2032, 2046]}, {"key": "benefits-of", "type": "clause", "offset": [2170, 2181]}, {"key": "in-scope", "type": "definition", "offset": [2235, 2243]}, {"key": "for-approval", "type": "definition", "offset": [2355, 2367]}, {"key": "provider-business", "type": "definition", "offset": [2456, 2473]}, {"key": "organizational-change-management-plan", "type": "clause", "offset": [2730, 2767]}, {"key": "the-activities", "type": "clause", "offset": [2842, 2856]}, {"key": "for-the-department", "type": "definition", "offset": [2867, 2885]}, {"key": "business-performance", "type": "clause", "offset": [3019, 3039]}, {"key": "this-plan", "type": "definition", "offset": [3041, 3050]}, {"key": "provide-a", "type": "definition", "offset": [3057, 3066]}, {"key": "gap-analysis", "type": "definition", "offset": [3067, 3079]}, {"key": "processes-and-procedures", "type": "clause", "offset": [3116, 3140]}, {"key": "staff-roles-and-responsibilities", "type": "clause", "offset": [3145, 3177]}, {"key": "impact-analysis-report", "type": "definition", "offset": [3215, 3237]}, {"key": "based-on", "type": "clause", "offset": [3238, 3246]}, {"key": "the-model", "type": "clause", "offset": [3247, 3256]}, {"key": "change-management-activities", "type": "clause", "offset": [3311, 3339]}, {"key": "department-business", "type": "clause", "offset": [3488, 3507]}, {"key": "in-business", "type": "definition", "offset": [3609, 3620]}, {"key": "interpretation-of", "type": "clause", "offset": [3669, 3686]}, {"key": "applicable-statutes", "type": "clause", "offset": [3687, 3706]}, {"key": "guidance-documents", "type": "definition", "offset": [3750, 3768]}, {"key": "develop-and-implement", "type": "clause", "offset": [3786, 3807]}, {"key": "policy-changes", "type": "definition", "offset": [3812, 3826]}, {"key": "requirements-definition", "type": "clause", "offset": [3978, 4001]}, {"key": "in-detail", "type": "clause", "offset": [4046, 4055]}, {"key": "external-interfaces", "type": "clause", "offset": [4280, 4299]}, {"key": "information-needed", "type": "clause", "offset": [4320, 4338]}, {"key": "the-interface", "type": "clause", "offset": [4472, 4485]}, {"key": "the-entity", "type": "clause", "offset": [4521, 4531]}, {"key": "meeting-minutes", "type": "clause", "offset": [4809, 4824]}, {"key": "status-meetings", "type": "clause", "offset": [4873, 4888]}, {"key": "requirements-specification", "type": "clause", "offset": [4929, 4955]}, {"key": "other-systems", "type": "definition", "offset": [4997, 5010]}, {"key": "interface-requirements", "type": "clause", "offset": [5176, 5198]}, {"key": "the-software", "type": "clause", "offset": [5230, 5242]}, {"key": "provide-documentation", "type": "clause", "offset": [5769, 5790]}, {"key": "frequency-and", "type": "definition", "offset": [5842, 5855]}, {"key": "project-director", "type": "definition", "offset": [6017, 6033]}, {"key": "conclusion-of", "type": "clause", "offset": [6058, 6071]}, {"key": "scope-of", "type": "definition", "offset": [6298, 6306]}, {"key": "assist-the", "type": "clause", "offset": [6335, 6345]}, {"key": "facilitation-of-activities", "type": "clause", "offset": [6358, 6384]}, {"key": "external-agencies", "type": "clause", "offset": [6390, 6407]}, {"key": "memorandum-of-understanding", "type": "definition", "offset": [6419, 6446]}, {"key": "development-of-the", "type": "clause", "offset": [6473, 6491]}, {"key": "subject-matter", "type": "clause", "offset": [6554, 6568]}, {"key": "interface-development", "type": "clause", "offset": [6787, 6808]}], "size": 4, "snippet": "The Provider shall use software languages and tools for which resources are widely available in the market. The Provider shall generate a technical system design and update the requirements traceability matrix to reflect the relationship between requirements and design elements. The Provider shall conduct informal reviews of the design as it is developed and provide the Department with access to informal review information and documentation. At the completion of the system development, the Provider shall confirm that the technical system design is updated to represent the \u201cas built\u201d new system components and any necessary integration points with the existing ACCESS Florida System. After the initial approval of the technical system design or updated requirements traceability matrix, or any portion thereof, the Provider shall report all issues with the approved design. The Provider shall maintain a database of all reported issues, document the issues in the issues log, and document the resolution of all reported issues. The Provider shall provide the Department with direct access to the issues log. The following sections define the responsibilities of the Provider and the Department. Provider Technical Design Responsibilities Prepare the technical system design deliverables. Create and refine the database design. Document technical system design issues and decisions in the deliverables. Conduct a walk-through of the deliverables. Revise deliverables as a result of the review and approval process. Department Technical Design Responsibilities Review and approve the technical system design deliverables. Provide policy, regulation, forms, and procedural reference material and interpretations as needed. Design Phase - Business Process Reengineering The Provider shall work with stakeholders to create reengineered, future state Department and Partner business processes to reflect the approved system design and shall document and rollout the new business processes to the Department and Partners. The future state business processes shall be designed to enable the stakeholders to effectively employ the new system components to realize the full benefits of the implementation of the new system components. All in scope business processes shall be documented in a final To-Be Process Models document and provided to the Department for approval. The following sections define the responsibilities of the Provider and the Department. Provider Business Process Reengineering Responsibilities Create future state Department and Partner business processes to reflect the new system components. Create business process deliverables. Revise deliverables as a result of the review and approval process. Prepare an Organizational Change Management Plan to prepare for the implementation of the new system components, including the activities necessary for the Department and Partners to successfully adopt the new system components and functionality while minimizing the impact to staff productivity and business performance. This Plan shall provide a gap analysis between existing and to-be business processes and procedures and staff roles and responsibilities. Prepare a Staffing and Productivity Impact Analysis Report based on the model for the new system components. Conduct organizational change management activities to help confirm successful implementation of the new system components. Rollout the reengineered business processes to the Department and Partners. Department Business Process Reengineering Responsibilities Review and approve business process deliverables. Participate in business process design and revision activities. Provide interpretation of applicable statutes, rules, Department and Partner policy, and guidance documents to the Provider. Develop and implement any policy changes required to support new business processes. Design Phase - Interface Definition The Provider shall define and document all interfaces as identified in Requirements Definition Document. Each interface shall be described in detail, specifying purpose, format, content, frequency, and processing for each interface transaction. The Provider shall provide at least one interface definition document per identified interface. The Provider shall use existing external interfaces if they provide the information needed by the new system components. For interfaces that do not provide the information needed by the new system components, concurrence on the interface description shall be required from the entity that controls the interfacing system. The Provider shall coordinate approval from the entity in these instances. The Provider shall coordinate with the Department when interface changes and approval are needed. The Provider shall support all meetings on the interface, prepare meeting minutes, and track interface coordination status in the status meetings. The Provider shall generate a software requirements specification that documents all the new interfaces to other systems, including unchanged existing interfaces, changed existing interfaces, and new interfaces. The Provider shall update the requirements traceability matrix to include interface requirements. After the initial approval of the software requirements specification and updated requirements, or any portions thereof, the Provider shall report all problems with approved interface definition. The Provider shall maintain a database of all reported problems, document the problems in the issues log and document the resolution of all reported problems. The Provider shall provide the Department with direct access to the issues log. The following sections define the responsibilities of the Provider and the Department. Provider Interface Definition Responsibilities Provide documentation on interfaces specifying purpose, format, content, frequency and processing for each interface transaction. Provide meeting minutes of each interface session, including issues addressed and decisions made, to the Department\u2019s Project Director within five (5) days of conclusion of the interface meeting. Prepare the interface deliverables. Revise deliverables as a result of the review and approval process. Department Interface Definition Responsibilities Work with the Provider to develop the prioritized scope of interfaces to be developed. Assist the Provider in facilitation of activities with external agencies. Provide a memorandum of understanding with each agency prior to development of the interface. Review and approve interface deliverables. Provide subject matter advisors to clarify interface issues. Provide policy, regulation, forms, and procedural reference material and interpretations as needed. Provide leadership in coordinating efforts with the Department and Partners for interface development.", "hash": "c4cbf45872ad4f403b9fe2132691c4c7", "id": 1}, {"samples": [{"hash": "clbijBzkmPP", "uri": "/contracts/clbijBzkmPP#technical-design", "label": "Framework Agreement for Professional and Technical Services", "score": 24.4455852156, "published": true}], "snippet_links": [{"key": "the-client", "type": "definition", "offset": [22, 32]}, {"key": "the-project-team", "type": "clause", "offset": [37, 53]}, {"key": "stage-3", "type": "definition", "offset": [66, 73]}, {"key": "stage-4", "type": "definition", "offset": [142, 149]}, {"key": "meetings-as-required", "type": "clause", "offset": [189, 209]}], "size": 4, "snippet": "In collaboration with the Client and the Project Team, review the Stage 3 report and agree the format, outputs and programme required for the Stage 4 report. Attend Client and Project Team meetings as required.", "hash": "f3279343ac98ae66fc0d4851263c78fd", "id": 2}, {"samples": [{"hash": "iqDkgUmTNvT", "uri": "/contracts/iqDkgUmTNvT#technical-design", "label": "Systems Integration Consulting Services Agreement (Predictive Systems Inc)", "score": 18.0, "published": true}, {"hash": "aYayfeupymZ", "uri": "/contracts/aYayfeupymZ#technical-design", "label": "Systems Integration Consulting Services Agreement (Predictive Systems Inc)", "score": 18.0, "published": true}], "snippet_links": [{"key": "work-to-be-performed", "type": "definition", "offset": [4, 24]}, {"key": "general-direction", "type": "clause", "offset": [36, 53]}, {"key": "in-connection-with", "type": "clause", "offset": [67, 85]}, {"key": "the-work", "type": "definition", "offset": [86, 94]}, {"key": "coordinated-with", "type": "definition", "offset": [105, 121]}, {"key": "approval-of", "type": "clause", "offset": [150, 161]}, {"key": "technical-representative", "type": "definition", "offset": [168, 192]}], "size": 2, "snippet": "All Work to be performed, including general direction and guidance in connection with the Work, is to be coordinated with, and will be subject to the approval of LCI's Technical Representative. Nothing in this paragraph shall diminish Contractor's responsibilities to supervise and manage the NOC project hereunder.", "hash": "9f523b4a9bb551d17b81617e2444c40f", "id": 4}, {"samples": [{"hash": "aFUgSHxLpgY", "uri": "/contracts/aFUgSHxLpgY#technical-design", "label": "Framework Agreement", "score": 26.0843072974, "published": true}], "snippet_links": [{"key": "health-and-safety-risk-management", "type": "clause", "offset": [69, 102]}], "size": 1, "snippet": "Comment on updated Project Strategies as necessary where they affect health and safety risk management.", "hash": "eb4d6f7909c40b6dcd47a57dcbf5feb2", "id": 5}, {"samples": [{"hash": "9TzBG0yKpPx", "uri": "/contracts/9TzBG0yKpPx#technical-design", "label": "Services Agreement", "score": 23.1704312115, "published": true}], "snippet_links": [{"key": "development-environment", "type": "clause", "offset": [16, 39]}, {"key": "production-environment", "type": "clause", "offset": [74, 96]}, {"key": "the-code", "type": "clause", "offset": [237, 245]}, {"key": "by-the-state", "type": "clause", "offset": [350, 362]}, {"key": "the-contractor-shall", "type": "clause", "offset": [364, 384]}, {"key": "as-specified", "type": "clause", "offset": [415, 427]}, {"key": "development-of", "type": "clause", "offset": [476, 490]}, {"key": "integrated-plan", "type": "definition", "offset": [494, 509]}, {"key": "the-plan", "type": "clause", "offset": [550, 558]}, {"key": "project-activities", "type": "definition", "offset": [572, 590]}, {"key": "contract-term", "type": "definition", "offset": [642, 655]}], "size": 1, "snippet": "Occurs when the Development environment is refreshed with a mirror of the Production environment code base. \uf0b7 Development: Occurs after code fixes have been installed in the Development environment. \uf0b7 UAT: Occurs after the deployment of the code base from the Development environment to the Stage environment. Once the Gate deliverables are accepted by the State, the Contractor shall proceed with the next Release as specified in the IMS. The Contractor shall participate in development of an integrated plan and schedule for DDI and M&O activities the plan will include project activities that are scheduled to occur through the end of the Contract term.", "hash": "cf8febff0c704f4508d3945b9276e274", "id": 6}, {"samples": [{"hash": "1rOCOMlBKut", "uri": "/contracts/1rOCOMlBKut#technical-design", "label": "Interface Control Agreement", "score": 23.8350444901, "published": true}], "snippet_links": [{"key": "the-technical", "type": "clause", "offset": [2, 15]}, {"key": "the-interface", "type": "clause", "offset": [26, 39]}], "size": 1, "snippet": "\u200c The technical design of the interface is not described in this document. It is fully described in the SAVE SDD.\u200c", "hash": "43ba2377f5add438a49c3e05aeaa715c", "id": 7}, {"samples": [{"hash": "gBLNjGDXOgO", "uri": "/contracts/gBLNjGDXOgO#technical-design", "label": "Contract for Installation and Maintenance of Electrical Equipment", "score": 24.3264887064, "published": true}], "snippet_links": [{"key": "the-tenderer", "type": "definition", "offset": [30, 42]}, {"key": "site-survey", "type": "definition", "offset": [125, 136]}, {"key": "traffic-survey", "type": "clause", "offset": [139, 153]}, {"key": "traffic-flow", "type": "clause", "offset": [244, 256]}, {"key": "vehicle-type", "type": "definition", "offset": [277, 289]}, {"key": "quality-of-equipment", "type": "clause", "offset": [403, 423]}], "size": 1, "snippet": "To obtain the optimal result, the Tenderer shall, before supplying and installing the equip- ment, perform the following:\n1. Site Survey\nA Traffic survey shall be conducted at each controlled site to measure the traffic condi- tions (including traffic flow, turning movements ,vehicle type, delay and queue length) for the Morning -Peak ,Midday -Peak ,Evening -Peak and Off -Peak hours.\n2. Capacity and Quality of Equipment", "hash": "3973d2d1cf8bafbaaf9aae4dfcb73b1e", "id": 8}, {"samples": [{"hash": "luSS1Y2M1tS", "uri": "/contracts/luSS1Y2M1tS#technical-design", "label": "Grant Agreement", "score": 25.4447789847, "published": true}], "snippet_links": [{"key": "the-technical", "type": "clause", "offset": [0, 13]}, {"key": "the-project", "type": "clause", "offset": [25, 36]}, {"key": "for-\u2587", "type": "clause", "offset": [75, 80]}, {"key": "student-needs", "type": "clause", "offset": [211, 224]}, {"key": "school-district", "type": "clause", "offset": [255, 270]}, {"key": "district-uses", "type": "clause", "offset": [276, 289]}, {"key": "user-accounts", "type": "clause", "offset": [345, 358]}, {"key": "google-account", "type": "definition", "offset": [444, 458]}, {"key": "google-classroom", "type": "clause", "offset": [473, 489]}, {"key": "a-third-party", "type": "clause", "offset": [706, 719]}, {"key": "management-software", "type": "clause", "offset": [727, 746]}, {"key": "online-resources", "type": "definition", "offset": [863, 879]}, {"key": "one-place", "type": "definition", "offset": [1000, 1009]}, {"key": "available-at", "type": "definition", "offset": [1011, 1023]}, {"key": "access-to-the", "type": "clause", "offset": [1119, 1132]}, {"key": "applications-for", "type": "clause", "offset": [1161, 1177]}, {"key": "evenly-distributed", "type": "definition", "offset": [1399, 1417]}, {"key": "the-room", "type": "clause", "offset": [1432, 1440]}, {"key": "learning-environments", "type": "clause", "offset": [1504, 1525]}, {"key": "for-all-students", "type": "clause", "offset": [1526, 1542]}, {"key": "ability-to", "type": "definition", "offset": [1548, 1558]}, {"key": "the-teacher", "type": "definition", "offset": [1643, 1654]}, {"key": "to-the-class", "type": "clause", "offset": [1673, 1685]}, {"key": "provide-the", "type": "clause", "offset": [1765, 1776]}, {"key": "new-teacher", "type": "definition", "offset": [1806, 1817]}, {"key": "student-information-system", "type": "definition", "offset": [1958, 1984]}, {"key": "resources-for", "type": "clause", "offset": [2002, 2015]}, {"key": "things-you", "type": "clause", "offset": [2117, 2127]}, {"key": "a-student", "type": "definition", "offset": [2206, 2215]}, {"key": "interactive-learning", "type": "definition", "offset": [2739, 2759]}, {"key": "site-licenses", "type": "definition", "offset": [2931, 2944]}, {"key": "development-software", "type": "definition", "offset": [2983, 3003]}], "size": 1, "snippet": "The technical design for the Project mirrors that of DDSD\u2019s previous grant for \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 Elementary. Technology includes equipping 18 3-5 grade classrooms and nine classrooms serving a variety of ELL and SPED student needs. As a Google Suite, \u201cG Suite\u201d school district, the District uses Chromebooks to allow students to have their own unique user accounts, which they can access from any device that they sign into. Each student will have a Google account and access to Google Classroom, Google Docs, Google Presentation, and Google Spreadsheets. These collaborative tools will be shared between students, teachers and parents. G Suite also makes it easy to manage devices. There is no need to purchase a third party Mobile Management software as it comes with the Chromebook. Chromebooks are able to access the online math curriculum, LearnZillion, including online resources and online assessments. The new SMART Panel is an updated SMART board. The SMART Panel puts everything teachers need in one place, available at the touch of a finger without the need for a projector. The embedded computer offers one-touch access to the robust SMART Learning Suite applications for interactive lessons, game-based activities and online co-creation. The RedCat all-in-one classroom audio system with a flat-panel speaker design and wireless teacher microphone delivers highly intelligible speech that is evenly distributed everywhere in the room. Classroom Audio Technology effectively enhances listening and learning environments for all students. The ability to communicate to all students at once without projecting one\u2019s voice saves energy for the teacher, and communicates to the class that this a calm, focused environment conducive to learning. The District will provide the following for the Project: \u25cf New Teacher Macbook Laptops \u25cf LearnZillion Curriculum including online components and assessments \u25cf Google Classroom and Google Suite (G Suite) tied to Student Information System \u25cf MobyMax online resources for math and language \u25cf Google Suite and classroom resources from \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587: Purchased in 2017-18 \u25cb 50 Things You Can Do with Google Classroom \u25cb 50 Things to Go Further with Google Classroom: A Student-Centered Approach The MHCRC grant will provide the following for the Project: \u25cf 780 Chromebooks for 3rd-5th grade classrooms: \u25cb 18 3rd-5th grade classrooms \u25cb 3 ESL classrooms \u25cb 2 SPED classrooms \u25cb 1 Behavior multi-grade classroom \u25cb 3 SLP-A classrooms \u25cf 75 Tablets (iPads/Androids) for Menlo Park SLP-A classes (25/classroom x 3 classrooms) \u25cf 27 Chromebook carts \u25cf 2,565 Headsets for Chromebooks w/ mic \u25cf 375 Headsets for Chromebooks without mic \u25cf 27 SMART Interactive Panels (Updated SMART Board) with 27 stands \u25cf 53 SMART Interactive Learning Software \u25cf 27 MacBook to SMART interactive panel cables \u25cf 27 RedCat All-in-one classroom audio system with a flat-panel speaker design and wireless teacher microphone \u25cf 2 Site Licenses/year over 3 years for Online Language Development software (Imagine Learning).", "hash": "00e300e5b917d3ac19e3c3d9502cfb4b", "id": 9}, {"samples": [{"hash": "amPbj9RbfMj", "uri": "/contracts/amPbj9RbfMj#technical-design", "label": "Power Purchase Agreement", "score": 24.1813826146, "published": true}], "snippet_links": [{"key": "the-technical", "type": "clause", "offset": [4, 17]}, {"key": "metering-systems", "type": "definition", "offset": [32, 48]}, {"key": "consistent-with-the", "type": "clause", "offset": [64, 83]}, {"key": "technical-specification", "type": "clause", "offset": [84, 107]}, {"key": "set-out", "type": "definition", "offset": [108, 115]}, {"key": "schedule-6", "type": "definition", "offset": [119, 129]}, {"key": "prudent-utility-practices", "type": "clause", "offset": [134, 159]}, {"key": "agreed-by", "type": "clause", "offset": [170, 179]}, {"key": "engineering-design", "type": "clause", "offset": [215, 233]}, {"key": "the-facility", "type": "definition", "offset": [237, 249]}, {"key": "location-of", "type": "definition", "offset": [278, 289]}, {"key": "metering-devices", "type": "definition", "offset": [295, 311]}, {"key": "as-specified", "type": "clause", "offset": [321, 333]}, {"key": "according-to", "type": "definition", "offset": [341, 353]}, {"key": "single-line-diagram", "type": "definition", "offset": [358, 377]}, {"key": "presented-by", "type": "definition", "offset": [378, 390]}, {"key": "basis-of", "type": "clause", "offset": [491, 499]}, {"key": "maintenance-of-the", "type": "clause", "offset": [569, 587]}, {"key": "from-time-to-time", "type": "clause", "offset": [614, 631]}, {"key": "provided-that", "type": "clause", "offset": [718, 731]}, {"key": "in-accordance-with", "type": "definition", "offset": [752, 770]}, {"key": "to-the-extent", "type": "clause", "offset": [798, 811]}, {"key": "laws-of-vietnam", "type": "definition", "offset": [869, 884]}, {"key": "subject-always-to", "type": "clause", "offset": [890, 907]}, {"key": "rights-of-the", "type": "clause", "offset": [912, 925]}, {"key": "change-in-law", "type": "definition", "offset": [960, 973]}, {"key": "provisions-of-the", "type": "clause", "offset": [974, 991]}, {"key": "amendments-to-the", "type": "clause", "offset": [1045, 1062]}, {"key": "terms-of-this-agreement", "type": "clause", "offset": [1127, 1150]}, {"key": "not-required", "type": "definition", "offset": [1212, 1224]}, {"key": "in-good-faith", "type": "definition", "offset": [1325, 1338]}], "size": 1, "snippet": "(a) The technical design of the Metering Systems which shall be consistent with the technical specification set out in Schedule 6 and Prudent Utility Practices, shall be agreed by EVN and the BOT Company during the engineering design of the Facility. The exact number, type and location of such metering devices shall be as specified by EVN according to the single line diagram presented by the BOT Company for EVN\u2019s approval.\n(b) The technical design of the Metering Systems shall form the basis of installation, fixing, supplementing, commissioning and operation and maintenance of the Metering Systems. EVN may from time to time request amendments, subsequently to the technical design of the Metering Systems, but provided that such amendments are in accordance with Prudent Utility Practices. To the extent such amendments are required in order to comply with the Laws of Vietnam, but subject always to the rights of the BOT Company or the MOIT under the Change in Law provisions of the BOT Contract, the BOT Company shall incorporate such amendments to the technical design of the Metering Systems in accordance with the terms of this Agreement. To the extent the BOT Company considers such amendments are not required in order to comply with the Laws of Vietnam, EVN and the BOT Company shall discuss those amendments in good faith, provided that the BOT Company shall not be obliged to incorporate such amendments to the technical design of the Metering Systems unless such amendments are consistent with the Laws of Vietnam.", "hash": "508439e11607e97c7cfb68737dab78da", "id": 10}], "next_curs": "ClkSU2oVc35sYXdpbnNpZGVyY29udHJhY3RzcjULEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ihl0ZWNobmljYWwtZGVzaWduIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"size": 24, "children": [["conformance-criteria", "Conformance Criteria"], ["interfaces", "Interfaces"], ["implementation-expectations", "Implementation Expectations"], ["persistence-implementation", "Persistence Implementation"], ["", ""]], "parents": [["retention-of-operations-bond", "Retention of Operations Bond"], ["annual-report", "Annual Report"], ["initial-inspection-of-electrical-interconnection-facilities", "Initial Inspection of Electrical Interconnection Facilities"], ["persistence-module", "Persistence Module"], ["detailed-module-design", "Detailed Module Design"]], "title": "Technical Design", "id": "technical-design", "related": [["final-design", "Final Design", "Final Design"], ["technical-interfaces", "Technical Interfaces", "Technical Interfaces"], ["software-development", "Software Development", "Software Development"], ["technology-access", "Technology Access", "Technology Access"], ["manufacturing-technology-transfer", "Manufacturing Technology Transfer", "Manufacturing Technology Transfer"]], "related_snippets": [], "updated": "2025-07-07T12:36:18+00:00", "also_ask": ["What are the essential elements that must be included in a Technical Design clause to ensure clarity and enforceability?", "How can parties strategically allocate responsibility for design errors or omissions in this clause?", "What are the most common risks or ambiguities in Technical Design clauses that could lead to disputes?", "How does the enforceability of Technical Design obligations differ across key jurisdictions?", "What negotiation levers exist to balance flexibility for design changes with the need for certainty?"], "drafting_tip": "Specify design standards, require approval procedures, and set timelines to ensure clarity, quality control, and timely completion.", "explanation": "The Technical Design clause defines the requirements and standards for the technical aspects of a project or deliverable. It typically outlines the specifications, methodologies, and technologies to be used, and may require the submission and approval of detailed design documents before work proceeds. This clause ensures that all parties have a clear understanding of the technical expectations, reducing the risk of misunderstandings and ensuring the final product meets agreed-upon criteria."}, "json": true, "cursor": ""}}