{"component": "clause", "props": {"groups": [{"snippet_links": [{"key": "technical-work", "type": "definition", "offset": [4, 18]}, {"key": "the-project", "type": "clause", "offset": [26, 37]}, {"key": "scope-of-this", "type": "clause", "offset": [114, 127]}, {"key": "technical-development", "type": "clause", "offset": [150, 171]}, {"key": "delivered-software", "type": "definition", "offset": [231, 249]}, {"key": "development-partner", "type": "definition", "offset": [396, 415]}, {"key": "conference-calls", "type": "clause", "offset": [501, 517]}, {"key": "face-to-face", "type": "clause", "offset": [544, 556]}, {"key": "a-year", "type": "definition", "offset": [572, 578]}, {"key": "development-schedules", "type": "clause", "offset": [623, 644]}], "size": 3, "snippet": "The technical work inside the project is coordinated by the Technical Co-Ordinator within the Technical Team. The scope of this team is to coordinate technical development actions (mainly across WP3 \u2013 WP7) and thus ensure that all delivered software in a specific WP is of good quality and interoperable with software developed in other WPs. The Technical Team includes representatives from each development partner and lead institutions of WP3 \u2013 WP7. The Technical Team has internal telephone/online conference calls every month and will meet face to face at least twice a year with the main scope of aligning semi-annual development schedules.", "samples": [{"hash": "lYgNxb3A4Ar", "uri": "/contracts/lYgNxb3A4Ar#technical-team", "label": "Grant Agreement", "score": 26.0651457244, "published": true}, {"hash": "7715esq5wnO", "uri": "/contracts/7715esq5wnO#technical-team", "label": "Grant Agreement", "score": 25.2548849206, "published": true}], "hash": "5b45cdf20e5f8a144fbefca7c08b4d5b", "id": 2}, {"snippet_links": [{"key": "the-technical", "type": "clause", "offset": [0, 13]}, {"key": "context-of-the", "type": "clause", "offset": [69, 83]}, {"key": "critical-issues", "type": "definition", "offset": [124, 139]}, {"key": "environmental-and-social", "type": "clause", "offset": [152, 176]}, {"key": "based-on", "type": "clause", "offset": [243, 251]}, {"key": "core-values", "type": "definition", "offset": [276, 287]}, {"key": "technical-documents", "type": "definition", "offset": [385, 404]}, {"key": "working-group", "type": "definition", "offset": [449, 462]}, {"key": "technical-experts", "type": "clause", "offset": [474, 491]}, {"key": "work-and", "type": "clause", "offset": [611, 619]}, {"key": "and-evaluation-criteria", "type": "clause", "offset": [697, 720]}, {"key": "member-commitment", "type": "clause", "offset": [825, 842]}, {"key": "to-ensure", "type": "clause", "offset": [955, 964]}, {"key": "responsibility-to-communicate", "type": "clause", "offset": [1023, 1052]}, {"key": "local-stakeholders", "type": "clause", "offset": [1121, 1139]}, {"key": "same-person", "type": "definition", "offset": [1146, 1157]}, {"key": "summit-county", "type": "definition", "offset": [1180, 1193]}, {"key": "project-staff", "type": "definition", "offset": [1343, 1356]}, {"key": "information-and-data", "type": "clause", "offset": [1376, 1396]}, {"key": "to-assist", "type": "clause", "offset": [1420, 1429]}, {"key": "the-process", "type": "clause", "offset": [1474, 1485]}, {"key": "the-project", "type": "clause", "offset": [1525, 1536]}, {"key": "working-with", "type": "definition", "offset": [1540, 1552]}, {"key": "decision-making", "type": "definition", "offset": [1600, 1615]}, {"key": "alternative-evaluation-process", "type": "clause", "offset": [1650, 1680]}, {"key": "the-evaluation-process", "type": "clause", "offset": [1828, 1850]}], "size": 1, "snippet": "The Technical Team (TT) members are the first to define the specific context of the segments and then identify the specific critical issues, technical, environmental and social/economic in a segment. The TT evaluates concepts and alternatives based on the critical issues and core values for the corridor and segment. To this end, the TT will have ample time to interact with maps and technical documents through interactive activities. The TT is a working group made up of technical experts and experts in multi- disciplinary fields. \uf0b7 Assists in developing alternatives. \uf0b7 Examines how different alternatives work and identifies trade-offs \uf0b7 Assists in evaluating alternatives using Core Values and Evaluation Criteria developed by the PLT and TT. \uf0b7 TT members are expected to come to the table and show up to meetings. TT member commitment and consistency are key to a successful process. \uf0b7 An overall schedule will be developed, along with key topics to ensure that appropriate TT members are present. \uf0b7 The TT has the responsibility to communicate TT meeting discussions and outcomes with their PLT representatives. Local Stakeholders \u2013 The same person on both TT and PLT. \uf0b7 Summit County \u2013 \u2587\u2587\u2587 \u2587. \uf0b7 Town of Frisco \u2013 \u2587\u2587\u2587\u2587 G \uf0b7 Town of \u2587\u2587\u2587\u2587\u2587\u2587 \u2013 \u2587\u2587\u2587 and \u2587\u2587\u2587\u2587\u2587 \uf0b7 Town of Silverthorne \u2013 \u2587\u2587\u2587 \u2587. \uf0b7 I-70 Coalition - \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 B \uf0b7 USFS \u2013 \u2587\u2587\u2587\u2587 \u2587. \uf0b7 Project Staff serves to organize information and data for the PLT and TT and to assist with organization, funding and facilitating the process. \uf0b7 Project Staff will deliver and lead the project by working with the PLT to champion the CSS process and enable decision making. \uf0b7 Project Staff will develop the alternative evaluation process by 1) developing evaluation criteria that reflects participant, members and stakeholders\u2019 interests and concerns and 2) gaining the endorsement of the evaluation process from the PLT members.", "samples": [{"hash": "60WFgZD1Qnk", "uri": "/contracts/60WFgZD1Qnk#technical-team", "label": "Leadership Team Chartering Agreement", "score": 21.3456536619, "published": true}], "hash": "d95ff64e7672a0d90306f098ed310591", "id": 3}, {"snippet_links": [{"key": "cooperative-group", "type": "definition", "offset": [12, 29]}, {"key": "technical-issues", "type": "definition", "offset": [53, 69]}, {"key": "restoration-project", "type": "definition", "offset": [110, 129]}, {"key": "responsible-for", "type": "clause", "offset": [146, 161]}, {"key": "actions-required", "type": "clause", "offset": [187, 203]}, {"key": "the-planning", "type": "clause", "offset": [217, 229]}, {"key": "decisions-of-the", "type": "clause", "offset": [256, 272]}, {"key": "members-of-the", "type": "clause", "offset": [278, 292]}, {"key": "each-of-the-parties", "type": "clause", "offset": [327, 346]}, {"key": "training-and-experience", "type": "clause", "offset": [383, 406]}, {"key": "technical-aspects", "type": "clause", "offset": [434, 451]}, {"key": "responsibility-of-the", "type": "clause", "offset": [516, 537]}, {"key": "not-limited", "type": "clause", "offset": [558, 569]}, {"key": "environmental-compliance", "type": "definition", "offset": [574, 598]}, {"key": "construction-monitoring", "type": "clause", "offset": [600, 623]}, {"key": "planning-activities", "type": "definition", "offset": [625, 644]}, {"key": "engineering-and-design", "type": "clause", "offset": [646, 668]}, {"key": "estate-actions", "type": "definition", "offset": [687, 701]}, {"key": "public-involvement", "type": "definition", "offset": [703, 721]}, {"key": "project-manager", "type": "definition", "offset": [793, 808]}, {"key": "support-facilities", "type": "clause", "offset": [895, 913]}, {"key": "federal-funding", "type": "definition", "offset": [945, 960]}], "size": 4, "snippet": "The TT is a cooperative group established to address technical issues arising as a result of implementing the Restoration Project. The TT will be responsible for the necessary day-to-day actions required to implement the planning, design, and construction decisions of the PMT. Members of the TT include representative(s) from each of the Parties, DWR and the SWRCB with appropriate training and experience to effectively address the technical aspects of implementing the Restoration Project. Disciplines within the responsibility of the TT include, but are not limited to, environmental compliance, construction monitoring, planning activities, engineering and design, permitting, real estate actions, public involvement, and construction. All unresolved technical issues will be referred to Project Manager for resolution or elevation to the PMT. Funding for the administrative, clerical, and support facilities for the TT will be provided by federal funding described in Section", "samples": [{"hash": "9F5pGR0DQ33", "uri": "/contracts/9F5pGR0DQ33#technical-team", "label": "Memorandum of Understanding", "score": 31.3390373502, "published": true}, {"hash": "8Vb376NrHnD", "uri": "/contracts/8Vb376NrHnD#technical-team", "label": "Memorandum of Understanding", "score": 26.1704312115, "published": true}, {"hash": "5FQyTAYayby", "uri": "/contracts/5FQyTAYayby#technical-team", "label": "Memorandum of Understanding", "score": 26.1704312115, "published": true}], "hash": "4bcc4a7a117277459456267eaffb395d", "id": 1}, {"snippet_links": [{"key": "chief-investment-officer", "type": "definition", "offset": [21, 45]}, {"key": "partnership-director", "type": "definition", "offset": [46, 66]}, {"key": "portfolio-manager", "type": "clause", "offset": [89, 106]}, {"key": "fund-advisor", "type": "definition", "offset": [125, 137]}, {"key": "finance-manager", "type": "clause", "offset": [169, 184]}, {"key": "rural-development", "type": "clause", "offset": [237, 254]}], "size": 1, "snippet": "\u200c \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 Chief Investment Officer/Partnership Director \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587 Senior Portfolio Manager \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587 Senior Fund Advisor \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 Sub-awards and Finance Manager/Deputy Partnership Director \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587 Colombian Rural Development Specialist \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 Local Smallholder Agricultural Markets and Finance Specialist (he will be replaced in January with someone with more smallholder agriculture experience)", "samples": [{"hash": "ev4SmjWk3pW", "uri": "/contracts/ev4SmjWk3pW#technical-team", "label": "Cooperative Agreement", "score": 19.71321013, "published": true}], "hash": "1eacbe3a5e2d51c4e935c77d0510d3f4", "id": 4}, {"snippet_links": [{"key": "a-permanent", "type": "clause", "offset": [26, 37]}, {"key": "purpose-of", "type": "clause", "offset": [57, 67]}, {"key": "and-support", "type": "clause", "offset": [121, 132]}, {"key": "of-the-standard", "type": "clause", "offset": [147, 162]}, {"key": "the-technical", "type": "clause", "offset": [164, 177]}, {"key": "comprised-of", "type": "clause", "offset": [186, 198]}, {"key": "technical-representatives", "type": "definition", "offset": [211, 236]}, {"key": "meetings-of-the", "type": "clause", "offset": [397, 412]}, {"key": "required-to-attend", "type": "clause", "offset": [435, 453]}, {"key": "team-meetings", "type": "clause", "offset": [488, 501]}, {"key": "matters-for-consideration", "type": "clause", "offset": [556, 581]}, {"key": "technical-working-group", "type": "definition", "offset": [613, 636]}, {"key": "the-chairperson", "type": "clause", "offset": [698, 713]}, {"key": "documents-available", "type": "clause", "offset": [739, 758]}, {"key": "for-review", "type": "clause", "offset": [759, 769]}, {"key": "before-the-meeting", "type": "clause", "offset": [799, 817]}, {"key": "special-meetings", "type": "definition", "offset": [819, 835]}, {"key": "the-primary", "type": "clause", "offset": [925, 936]}, {"key": "provision-of-notice", "type": "clause", "offset": [951, 970]}, {"key": "via-electronic-mail", "type": "clause", "offset": [980, 999]}, {"key": "electronic-mail-address", "type": "definition", "offset": [1068, 1091]}, {"key": "the-records", "type": "clause", "offset": [1109, 1120]}, {"key": "the-consortium", "type": "clause", "offset": [1124, 1138]}, {"key": "provided-that", "type": "clause", "offset": [1140, 1153]}, {"key": "recipient-shall", "type": "clause", "offset": [1159, 1174]}, {"key": "receipt-of", "type": "clause", "offset": [1196, 1206]}, {"key": "electronic-message", "type": "definition", "offset": [1211, 1229]}, {"key": "telephone-call", "type": "definition", "offset": [1264, 1278]}, {"key": "working-days", "type": "clause", "offset": [1296, 1308]}, {"key": "first-notification", "type": "definition", "offset": [1316, 1334]}, {"key": "by-telephone", "type": "definition", "offset": [1388, 1400]}, {"key": "electronic-means", "type": "definition", "offset": [1422, 1438]}, {"key": "a-technical", "type": "clause", "offset": [1517, 1528]}, {"key": "place-of", "type": "clause", "offset": [1607, 1615]}, {"key": "absent-member", "type": "definition", "offset": [1621, 1634]}, {"key": "pursuant-to-a", "type": "definition", "offset": [1635, 1648]}, {"key": "signed-by", "type": "clause", "offset": [1655, 1664]}, {"key": "participate-in", "type": "definition", "offset": [1715, 1729]}, {"key": "participating-in", "type": "definition", "offset": [1836, 1852]}, {"key": "in-person", "type": "clause", "offset": [1981, 1990]}, {"key": "from-time-to-time", "type": "clause", "offset": [2073, 2090]}, {"key": "management-team", "type": "definition", "offset": [2098, 2113]}, {"key": "provisions-of-law", "type": "clause", "offset": [2205, 2222]}], "size": 1, "snippet": "The MHL Technical Team is a permanent Working Group, the purpose of which is to draft and maintain the MHL Specification and support the evolution of the standard. The Technical Team is comprised of one or more Technical Representatives from each of the Promoters and Associate Promoters. Each Promoter and Associate Promoter Technical Representative on the Technical Team has the right to attend meetings of the Technical Team and is required to attend no less than 75% of all Technical Team meetings. Each Promoter and Associate Promoter has one vote on matters for consideration before the Technical Team. The Technical Working Group shall meet regularly upon fourteen (14) days prior notice by the chairperson, with the agenda and all documents available for review no later than seven (7) days before the meeting. Special meetings of the Technical Team may be called by the chairperson upon seven (7) days prior notice. The primary means for the provision of notice shall be via electronic mail from the chairperson of the Technical Team to each recipient at its electronic mail address as it appears on the records of the Consortium, provided that each recipient shall acknowledge personal receipt of the electronic message by a return electronic message or telephone call within three (3) working days of the first notification. Personal notification may also include notification by telephone, facsimile, or other electronic means. Meetings of the Technical Team shall be coordinated over by the chairperson. A Technical Representative may designate an alternate Technical Representative to Vote in place of said absent member pursuant to a proxy signed by said absent member. Technical Representatives may participate in meetings through use of teleconference, videoconference, or similar communications, so long as all people participating in such meeting can hear one another during such meeting. Participation in a meeting pursuant to this Section constitutes presence in person at such meeting. Meetings shall be governed by such procedures as may be approved from time to time by the Management Team, insofar as such rules are not inconsistent with or in conflict with these Bylaws, or with provisions of law.", "samples": [{"hash": "gRmzWxJKrOo", "uri": "/contracts/gRmzWxJKrOo#technical-team", "label": "Bylaws", "score": 21.6228610541, "published": true}], "hash": "b896ce77f5ee3f75c97516a5a5854a29", "id": 5}, {"snippet_links": [{"key": "business-days-of", "type": "clause", "offset": [16, 32]}, {"key": "the-effective-date", "type": "clause", "offset": [33, 51]}, {"key": "each-party", "type": "clause", "offset": [53, 63]}, {"key": "associated-with", "type": "definition", "offset": [193, 208]}, {"key": "development-agreement", "type": "clause", "offset": [214, 235]}, {"key": "the-members", "type": "clause", "offset": [256, 267]}, {"key": "technical-representatives", "type": "definition", "offset": [282, 307]}, {"key": "authority-and", "type": "clause", "offset": [324, 337]}, {"key": "make-recommendations", "type": "clause", "offset": [352, 372]}, {"key": "with-respect-to", "type": "clause", "offset": [373, 388]}, {"key": "sole-discretion", "type": "clause", "offset": [495, 510]}, {"key": "notice-to-the", "type": "clause", "offset": [516, 529]}, {"key": "other-party", "type": "definition", "offset": [530, 541]}, {"key": "costs-and-expenses", "type": "definition", "offset": [573, 591]}, {"key": "related-to", "type": "clause", "offset": [592, 602]}, {"key": "the-technical", "type": "clause", "offset": [603, 616]}, {"key": "purpose-of-the", "type": "clause", "offset": [627, 641]}, {"key": "determine-the", "type": "clause", "offset": [663, 676]}, {"key": "types-of-projects", "type": "clause", "offset": [677, 694]}, {"key": "the-project", "type": "clause", "offset": [767, 778]}, {"key": "existing-projects", "type": "definition", "offset": [798, 815]}, {"key": "not-limited", "type": "clause", "offset": [832, 843]}, {"key": "schedule-changes", "type": "definition", "offset": [847, 863]}, {"key": "project-modification", "type": "definition", "offset": [899, 919]}, {"key": "engineering-resources", "type": "clause", "offset": [1016, 1037]}, {"key": "allocated-to", "type": "definition", "offset": [1044, 1056]}, {"key": "owned-technology", "type": "clause", "offset": [1119, 1135]}, {"key": "section-53", "type": "clause", "offset": [1151, 1162]}, {"key": "alliance-agreement", "type": "definition", "offset": [1251, 1269]}, {"key": "patent-protection", "type": "clause", "offset": [1299, 1316]}, {"key": "final-decision", "type": "definition", "offset": [1372, 1386]}, {"key": "the-first-meeting", "type": "definition", "offset": [1458, 1475]}, {"key": "time-and-location", "type": "clause", "offset": [1515, 1532]}, {"key": "mutually-agreed", "type": "clause", "offset": [1536, 1551]}, {"key": "initial-projects", "type": "definition", "offset": [1595, 1611]}, {"key": "deemed-necessary", "type": "definition", "offset": [1852, 1868]}, {"key": "senior-managers", "type": "definition", "offset": [1943, 1958]}, {"key": "negotiate-in-good-faith", "type": "definition", "offset": [1991, 2014]}, {"key": "the-issue", "type": "clause", "offset": [2026, 2035]}, {"key": "reasonable-period-of-time", "type": "clause", "offset": [2045, 2070]}, {"key": "within-thirty", "type": "clause", "offset": [2101, 2114]}, {"key": "calendar-days", "type": "definition", "offset": [2120, 2133]}, {"key": "notwithstanding-the-foregoing", "type": "clause", "offset": [2178, 2207]}, {"key": "neither-party-shall", "type": "clause", "offset": [2209, 2228]}, {"key": "liability-for", "type": "clause", "offset": [2335, 2348]}, {"key": "such-party", "type": "clause", "offset": [2349, 2359]}], "size": 1, "snippet": "Within ten (10) business days of the Effective Date, each Party shall assign one (1) member (\"Member\") to a joint technical steering team to meet and cooperate to define and manage the efforts associated with this Development Agreement (\"Technical Team\"). The Members shall include technical representatives with sufficient authority and experience to make recommendations with respect to the selection and implementation of the prospective Projects. Either Party may replace its Members in its sole discretion upon notice to the other Party. Each Party shall bear its own costs and expenses related to the Technical Team. The purpose of the Technical Team is to determine the types of Projects and timetables for each Project (\"Project Roadmap\"), to add Projects to the Project Roadmap, to change existing Projects, including, but not limited to schedule changes, and to cancel existing Projects (\"Project Modification\").\n(a) The Technical Team shall determine the priority of different Projects, and the amount of engineering resources to be allocated to each Project.\n(b) The Technical Team shall review all Jointly-Owned Technology (as defined in section 5.3) proposed for patenting, and make recommendations to the Commercial Team (see Corporate Alliance Agreement) as to the merits of seeking patent protection on such inventions. The Commercial Team shall make the final decision as to whether or not, and in what countries, to seek patent(s).\n(c) At the first meeting of the Technical Team, to be held at a time and location as mutually agreed, the Members shall discuss and approve the initial Projects and the amount of engineering resources to be allocated to each Project (\"Initial Project Roadmap\"). At least the first meeting of the Technical Team shall be face-to-face. The Technical Team shall revise and publish the Project Roadmap as deemed necessary.\n(d) If the Technical Team cannot reach a decision on a particular issue, senior managers of Quantum and GM will meet and negotiate in good faith to resolve the issue within a reasonable period of time. If the issue is not resolved within thirty (30) calendar days, the Project Roadmap will remain unchanged. Notwithstanding the foregoing, neither Party shall be required to implement a decision of the Technical Team if such decision may reasonably result in legal liability for such Party.", "samples": [{"hash": "52nOdIxW4W3", "uri": "/contracts/52nOdIxW4W3#technical-team", "label": "Master Technical Development Agreement (Impco Technologies Inc)", "score": 18.0, "published": true}], "hash": "2c83b55daa0a67d719f8be5379071f87", "id": 6}, {"snippet_links": [{"key": "responsible-for", "type": "clause", "offset": [44, 59]}, {"key": "system-administration", "type": "definition", "offset": [68, 89]}, {"key": "the-technical", "type": "clause", "offset": [115, 128]}, {"key": "for-the-city", "type": "definition", "offset": [199, 211]}, {"key": "be-responsible", "type": "clause", "offset": [257, 271]}, {"key": "current-system", "type": "clause", "offset": [388, 402]}, {"key": "team-members", "type": "definition", "offset": [414, 426]}, {"key": "key-resources", "type": "clause", "offset": [484, 497]}, {"key": "technical-tasks", "type": "clause", "offset": [511, 526]}, {"key": "technical-aspects", "type": "clause", "offset": [609, 626]}, {"key": "the-project", "type": "clause", "offset": [630, 641]}, {"key": "technical-resources", "type": "definition", "offset": [643, 662]}, {"key": "updates-and-releases", "type": "clause", "offset": [826, 846]}, {"key": "according-to", "type": "definition", "offset": [847, 859]}, {"key": "release-plan", "type": "definition", "offset": [875, 887]}, {"key": "as-needed", "type": "clause", "offset": [945, 954]}, {"key": "training-days", "type": "clause", "offset": [959, 972]}, {"key": "conversion-data", "type": "clause", "offset": [1003, 1018]}, {"key": "control-reports", "type": "clause", "offset": [1023, 1038]}, {"key": "conversion-schedule", "type": "definition", "offset": [1049, 1068]}, {"key": "new-users", "type": "clause", "offset": [1078, 1087]}, {"key": "system-maintenance", "type": "definition", "offset": [1127, 1145]}, {"key": "all-users", "type": "clause", "offset": [1157, 1166]}, {"key": "training-sessions", "type": "definition", "offset": [1231, 1248]}, {"key": "software-updates", "type": "definition", "offset": [1322, 1338]}, {"key": "hardware-installation", "type": "clause", "offset": [1340, 1361]}, {"key": "system-setup", "type": "clause", "offset": [1376, 1388]}, {"key": "remote-access", "type": "definition", "offset": [1401, 1414]}, {"key": "support-personnel", "type": "definition", "offset": [1425, 1442]}], "size": 1, "snippet": "The City\u2019s technical team will be primarily responsible for overall system administration, security, and workflow. The Technical Team will also handle all data conversions, interfaces, and reporting for the City. It is expected that the Technical team will be responsible for system administration post go-live. Because the Technical Team is tasked with maintaining the City\u2019s customized current system, technical team members also possess functional knowledge and are expected to be key resources not only for technical tasks, but also functional tasks. The City\u2019s technical team will be responsible for all technical aspects of the project. Technical resources will also be responsible for coordinating with Tyler\u2019s installation team to support the implementation. The City Technical Team will be responsible for: \u25aa Loading updates and releases according to the Update and Release Plan \u25aa Copying source databases to training/testing databases as needed for training days \u25aa Extracting and transmitting conversion data and control reports following conversion schedule \u25aa Adding new users and printers \u25aa Performing basic server system maintenance \u25aa Ensuring all users understand log-on process and have necessary permission for all training sessions \u25aa Coordinating IT functions such as system backups, loading releases and software updates, hardware installation and operating system setup \u25aa Providing remote access for Tyler support personnel upon need / request", "samples": [{"hash": "aq8RxLwpHYj", "uri": "/contracts/aq8RxLwpHYj#technical-team", "label": "Software License Agreement", "score": 23.0301163587, "published": true}], "hash": "0f0e1d1e6f6f25d5bd03ae3b357160aa", "id": 7}, {"snippet_links": [{"key": "working-committees", "type": "clause", "offset": [11, 29]}, {"key": "the-technical", "type": "clause", "offset": [39, 52]}, {"key": "responsible-for", "type": "clause", "offset": [66, 81]}, {"key": "development-of-the-product", "type": "clause", "offset": [86, 112]}, {"key": "research-and-development-projects", "type": "definition", "offset": [118, 151]}, {"key": "approved-by", "type": "definition", "offset": [210, 221]}, {"key": "the-relevant", "type": "clause", "offset": [233, 245]}, {"key": "research-and-development-expenses", "type": "clause", "offset": [246, 279]}, {"key": "development-results", "type": "definition", "offset": [367, 386]}, {"key": "intellectual-property-and-know", "type": "clause", "offset": [410, 440]}, {"key": "terms-of-this-agreement", "type": "clause", "offset": [492, 515]}], "size": 1, "snippet": "One of the Working Committees would be the technical team that is responsible for the development of the Product. The research and development projects and directions of the development of the Product shall be approved by NT Pharma. The relevant research and development expenses are to be borne by NT Pharma. NT Pharma shall be the sole proprietary owner of all the development results including any patents, Intellectual Property and Know-How, and are not restricted by any contradictatory terms of this Agreement.", "samples": [{"hash": "b2mJUhadz39", "uri": "/contracts/b2mJUhadz39#technical-team", "label": "Development and License Agreement", "score": 31.63568875, "published": true}], "hash": "82c9de347faab69691c95b7193976cf7", "id": 8}, {"snippet_links": [{"key": "provide-a", "type": "definition", "offset": [20, 29]}, {"key": "to-operate", "type": "definition", "offset": [56, 66]}, {"key": "responsibility-of-the", "type": "clause", "offset": [95, 116]}], "size": 1, "snippet": "The Franchisor will provide a two-member technical team to operate planetarium. It is the sole responsibility of the Franchisor to conduct shows.", "samples": [{"hash": "87bSBS2yYlO", "uri": "/contracts/87bSBS2yYlO#technical-team", "label": "Franchise Agreement", "score": 22.8562628337, "published": true}], "hash": "ad6b482564f0c5e14d0a6d0d667d0004", "id": 9}, {"snippet_links": [{"key": "responsible-for", "type": "clause", "offset": [39, 54]}, {"key": "system-administration", "type": "definition", "offset": [63, 84]}, {"key": "the-technical", "type": "clause", "offset": [110, 123]}, {"key": "custom-reporting", "type": "clause", "offset": [180, 196]}, {"key": "for-city", "type": "definition", "offset": [249, 257]}, {"key": "be-responsible", "type": "clause", "offset": [303, 317]}, {"key": "technical-aspects", "type": "clause", "offset": [408, 425]}, {"key": "the-project", "type": "clause", "offset": [429, 440]}], "size": 1, "snippet": "City's Technical Team may be primarily responsible for overall system administration, security, and workflow. The Technical Team will also handle all data conversions, interfaces, custom reporting and reporting submission responsibilities reporting for City. It is expected that the Technical team will be responsible for system administration post go-live. City's technical team will be responsible for all technical aspects of the project. \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 IT Analyst \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587 IT Analyst \u2587\u2587\u2587\u2587\u2587 Trail IT Analyst \u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 IT Analyst", "samples": [{"hash": "e8nM7nKxRbG", "uri": "/contracts/e8nM7nKxRbG#technical-team", "label": "Information Technology Agreement", "score": 27.4355511809, "published": true}], "hash": "af838956e5ea3b8e34f0a87a9ea82846", "id": 10}], "next_curs": "ClcSUWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjMLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ihd0ZWNobmljYWwtdGVhbSMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"title": "Technical Team", "size": 17, "parents": [["cdfg", "CDFG"], ["reporting-and-notice-requirements", "Reporting and Notice Requirements"], ["organizational-structure-and-responsibilities", "Organizational Structure and Responsibilities"], ["internal-communications", "Internal Communications"], ["third-party-beneficiary", "Third-Party Beneficiary"]], "children": [], "id": "technical-team", "related": [["project-team", "Project Team", "Project Team"], ["project-managers", "Project Managers", "Project Managers"], ["liaisons", "Liaisons", "Liaisons"], ["project-manager", "Project Manager", "Project Manager"], ["technical-support-services", "Technical Support Services", "Technical Support Services"]], "related_snippets": [], "updated": "2025-07-07T12:37:53+00:00", "also_ask": ["What are the essential qualifications and roles that must be specified for the Technical Team?", "How can the Technical Team clause be leveraged to allocate liability or limit exposure?", "What are the most common pitfalls or ambiguities in drafting Technical Team provisions?", "How do Technical Team requirements compare across similar contracts or jurisdictions?", "What standards do courts use to assess the adequacy and enforceability of Technical Team clauses?"], "drafting_tip": "Specify team composition and qualifications to ensure competency; define roles and responsibilities to prevent overlap; require regular reporting to maintain accountability.", "explanation": "The 'Technical Team' clause defines the group of individuals responsible for managing and executing the technical aspects of a project or agreement. This clause typically outlines the composition of the team, their qualifications, and their specific roles and responsibilities, such as overseeing system implementation, troubleshooting issues, or ensuring compliance with technical standards. By clearly designating the technical team, the clause ensures accountability and streamlines communication, helping to prevent misunderstandings and ensuring that technical tasks are handled by qualified personnel."}, "json": true, "cursor": ""}}