{"component": "clause", "props": {"groups": [{"snippet": "The existing manual driver\u2019s licence register shows that there are approximately 600,000 licences. It is estimated that 80% of these licences are still active. The records also show that approximately 70% of all driver\u2019s\u2019 licences were issued in Dar as Salaam. If the regional distribution of driver\u2019s licences follows a similar distribution pattern as that of the motor vehicles then the number of active licence holders in the major regions would be as shown in the table on Table 1 below Region Total Transactions per day if three years transition period Dar es Salaam 250,000 380 Tanga 20,000 30 Arusha 20,000 30 Mwanza 20,000 30 Iringa 15,000 23 Kagera 15,000 23 Kilimanjaro 5,000 8 Mbeya 5,000 8 Morogoro 5,000 8 Zanzibar 5,000 8 Remaining regions 40,000 61 TOTAL 400,000 609", "size": 2, "snippet_links": [{"key": "the-records", "type": "clause", "offset": [160, 171]}, {"key": "issued-in", "type": "definition", "offset": [236, 245]}, {"key": "distribution-of", "type": "clause", "offset": [277, 292]}, {"key": "motor-vehicles", "type": "definition", "offset": [365, 379]}, {"key": "number-of", "type": "definition", "offset": [389, 398]}, {"key": "licence-holders", "type": "definition", "offset": [406, 421]}, {"key": "as-shown", "type": "definition", "offset": [452, 460]}, {"key": "table-1", "type": "clause", "offset": [477, 484]}, {"key": "total-transactions", "type": "definition", "offset": [498, 516]}, {"key": "per-day", "type": "definition", "offset": [517, 524]}, {"key": "transition-period", "type": "definition", "offset": [540, 557]}], "samples": [{"hash": "i1rRHtThayu", "uri": "/contracts/i1rRHtThayu#current-system", "label": "Build, Operate and Transfer (Bot) Agreement (On Track Innovations LTD)", "score": 23.2039699554, "published": true}, {"hash": "b8DlMZRSZAW", "uri": "/contracts/b8DlMZRSZAW#current-system", "label": "Build, Operate and Transfer (Bot) Agreement (On Track Innovations LTD)", "score": 22.9657764435, "published": true}], "hash": "640e86abf457e37958c5619a8a2b1b5b", "id": 1}, {"snippet": "The Grantee is authorized and required to operate Grantee\u2019s existing Cable System as set forth in Section 4(a) and (b) and to provide service meeting all applicable standards.", "size": 1, "snippet_links": [{"key": "the-grantee", "type": "definition", "offset": [0, 11]}, {"key": "to-operate", "type": "definition", "offset": [39, 49]}, {"key": "cable-system", "type": "definition", "offset": [69, 81]}, {"key": "to-provide", "type": "clause", "offset": [123, 133]}, {"key": "applicable-standards", "type": "clause", "offset": [154, 174]}], "samples": [{"hash": "lywH2SIAu2M", "uri": "/contracts/lywH2SIAu2M#current-system", "label": "Franchise Agreement", "score": 21.0, "published": true}], "hash": "f57961c21c0644eac92c47aa5f4e4875", "id": 2}, {"snippet": "The City currently oversees the functions of an in-house PIR management tool, and any new system under consideration should possess enhanced capabilities from the current tool. Specifications outlined here within reflect the capabilities of a system that would operate at an enhanced level from the current system. The current system does not provide for the publication of PIR-related information to the City\u2019s open data portal (\u2587\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/). Included in this section the current City of Austin Information Request process for the Office of the Chief Information Officer and other city departments. City of Austin Statement of Work Public Information Request System", "size": 1, "snippet_links": [{"key": "functions-of", "type": "clause", "offset": [32, 44]}, {"key": "management-tool", "type": "clause", "offset": [61, 76]}, {"key": "new-system", "type": "clause", "offset": [86, 96]}, {"key": "under-consideration", "type": "definition", "offset": [97, 116]}, {"key": "the-current", "type": "clause", "offset": [159, 170]}, {"key": "provide-for", "type": "definition", "offset": [343, 354]}, {"key": "related-information", "type": "clause", "offset": [378, 397]}, {"key": "to-the-city", "type": "clause", "offset": [398, 409]}, {"key": "open-data-portal", "type": "definition", "offset": [412, 428]}, {"key": "city-of-austin", "type": "clause", "offset": [499, 513]}, {"key": "request-process", "type": "clause", "offset": [526, 541]}, {"key": "office-of-the-chief-information-officer", "type": "definition", "offset": [550, 589]}, {"key": "other-city", "type": "definition", "offset": [594, 604]}, {"key": "statement-of-work", "type": "clause", "offset": [633, 650]}, {"key": "public-information-request", "type": "clause", "offset": [651, 677]}], "samples": [{"hash": "amVc6rGHNQB", "uri": "/contracts/amVc6rGHNQB#current-system", "label": "Contract for Public Information Request System Services", "score": 23.2245044708, "published": true}], "hash": "b4849c193b5558a2a726968ca75d4e2b", "id": 3}, {"snippet": "The current EMS Data System is provided by Lancet Technology, Inc., located in Boston, Massachusetts. It includes three (3) separate modules; Central - One, Trauma \u2013 One, and Certification \u2013 One. These modules are not web based and currently have no interoperability between the three (3) databases. The nature of each current data system is summarized below: \uf0b7 Manual data entry from the PCR or Base Hospital Report (BHR) is completed by each of the seven (7) designated Base Hospitals pursuant to a contractual agreement that each one has entered into with OCEMS. \uf0b7 Each Base Hospital\u2019s (BH) EMS Data application is set up identically, but updates must be completed individually. Each BH has a separate software maintenance contract with Lancet Technology. \uf0b7 The current EMS Data Set is based on locally created standards, and is very limited in its scope and focus. \uf0b7 Data is only entered for patient encounters that meet OCEMS Advanced Life Support (ALS) patient Treatment Guidelines; no Basic Life Support (BLS) patients are entered into the system. Annual ALS patient volume is approximately 40% of the system; therefore, only 50,000 \u2013 60,000 patient encounters per year are entered. \uf0b7 Data is submitted to OCEMS as an email attachment in a .zip file by each BH on a rotating schedule twice per month. Data is then manually imported by the EMS Data Entry Specialist. \uf0b7 Database is SQL and resides on the server managed by OCHCA IT. Trauma \u2013 One: \uf0b7 Manual data entry for each patient who enters the Orange County Trauma System (by 9-1-1 or Walk-In) is completed by three (3) designated Trauma Center\u2019s pursuant to a contractual agreement that each one has entered into with OCEMS. Data from an OCEMS designated Trauma Center that is based outside of the County is manually entered on-site by the EMS Data Entry Specialist. \uf0b7 The current Trauma Registry Data Set is based on the National Trauma Data Bank (NTDB) and locally created standards; however, OCEMS currently only requires a data set that is limited in its scope and focus. \uf0b7 Each Trauma Center is required to maintain a comprehensive Trauma Patient Registry; however, OCEMS does not have access to it. Historically, OCEMS has only required that a small sub-set of data elements be submitted. \uf0b7 Each Trauma Center\u2019s Trauma Registry Data application is set up differently. System-wide updates are very difficult, or impossible. Each Trauma Center has a separate software maintenance contract with Lancet Technology. \uf0b7 Data is submitted to OCEMS as an email attachment in a .zip file by each Trauma Center on a rotating schedule once per month. Data is then manually imported by the EMS Data Entry Specialist. \uf0b7 Database is SQL and resides on the server managed by OCHCA IT. Certification \u2013 One (CERT): \uf0b7 The \u201cTrauma \u2013 One\u201d application has been modified by Lancet Technology at OCEMS\u2019 request to meet the need to comprehensively track all EMS personnel who are Certified and/or Accredited by OCEMS. \uf0b7 Manual data entry for information pertaining to the Certification or Accreditation of EMS personnel who operate within the OCEMS System is completed by OCEMS clerical/support staff members. \uf0b7 Database is SQL and resides on the server managed by OCHCA IT.", "size": 1, "snippet_links": [{"key": "the-current", "type": "clause", "offset": [0, 11]}, {"key": "data-system", "type": "definition", "offset": [16, 27]}, {"key": "located-in", "type": "definition", "offset": [68, 78]}, {"key": "separate-modules", "type": "definition", "offset": [124, 140]}, {"key": "nature-of", "type": "clause", "offset": [304, 313]}, {"key": "current-data", "type": "definition", "offset": [319, 331]}, {"key": "data-entry", "type": "clause", "offset": [369, 379]}, {"key": "base-hospital", "type": "definition", "offset": [396, 409]}, {"key": "completed-by", "type": "clause", "offset": [426, 438]}, {"key": "designated-base", "type": "clause", "offset": [461, 476]}, {"key": "pursuant-to-a", "type": "definition", "offset": [487, 500]}, {"key": "contractual-agreement", "type": "definition", "offset": [501, 522]}, {"key": "entered-into", "type": "clause", "offset": [541, 553]}, {"key": "must-be-completed", "type": "clause", "offset": [650, 667]}, {"key": "a-separate", "type": "definition", "offset": [694, 704]}, {"key": "maintenance-contract", "type": "definition", "offset": [714, 734]}, {"key": "data-set", "type": "clause", "offset": [777, 785]}, {"key": "based-on", "type": "clause", "offset": [789, 797]}, {"key": "scope-and", "type": "clause", "offset": [852, 861]}, {"key": "advanced-life-support", "type": "definition", "offset": [931, 952]}, {"key": "treatment-guidelines", "type": "definition", "offset": [967, 987]}, {"key": "basic-life-support", "type": "definition", "offset": [992, 1010]}, {"key": "the-system", "type": "definition", "offset": [1043, 1053]}, {"key": "per-year", "type": "definition", "offset": [1168, 1176]}, {"key": "rotating-schedule", "type": "clause", "offset": [1273, 1290]}, {"key": "per-month", "type": "clause", "offset": [1297, 1306]}, {"key": "orange-county", "type": "definition", "offset": [1504, 1517]}, {"key": "trauma-system", "type": "definition", "offset": [1518, 1531]}, {"key": "designated-trauma-center", "type": "definition", "offset": [1580, 1604]}, {"key": "the-county", "type": "definition", "offset": [1755, 1765]}, {"key": "registry-data", "type": "definition", "offset": [1849, 1862]}, {"key": "the-national", "type": "clause", "offset": [1879, 1891]}, {"key": "data-bank", "type": "definition", "offset": [1899, 1908]}, {"key": "to-maintain", "type": "clause", "offset": [2070, 2081]}, {"key": "patient-registry", "type": "definition", "offset": [2105, 2121]}, {"key": "access-to", "type": "definition", "offset": [2152, 2161]}, {"key": "data-elements", "type": "definition", "offset": [2228, 2241]}, {"key": "ems-personnel", "type": "definition", "offset": [2900, 2913]}, {"key": "for-information", "type": "clause", "offset": [2980, 2995]}, {"key": "pertaining-to", "type": "definition", "offset": [2996, 3009]}, {"key": "the-certification", "type": "clause", "offset": [3010, 3027]}, {"key": "staff-members", "type": "definition", "offset": [3137, 3150]}], "samples": [{"hash": "jM9v7e4OqNW", "uri": "/contracts/jM9v7e4OqNW#current-system", "label": "Contract for Medical Emergency Data System", "score": 23.4016876221, "published": true}], "hash": "defb50fb4640cf0130fb9befa29f251f", "id": 4}, {"snippet": "The current Automated Materials Handler (TotalAMH) was installed in 2020. In the past 5 years the number of items in transit between library locations has greatly increased, averaging 5000+ items per day running through the TotalAMH. The TotalAMH and corresponding transit bins increased the capacity for daily transit and has made the sorting process more efficient and accurate. Contractor shall provide all necessary maintenance, repair, and updates to hardware and software used by the TotalAMH. Contractor shall provide transit bins (SmartBins) that work with the existing TotalAMH as described herein.", "size": 1, "snippet_links": [{"key": "the-current", "type": "clause", "offset": [0, 11]}, {"key": "materials-handler", "type": "clause", "offset": [22, 39]}, {"key": "number-of-items", "type": "clause", "offset": [98, 113]}, {"key": "per-day", "type": "definition", "offset": [196, 203]}, {"key": "contractor-shall-provide", "type": "clause", "offset": [381, 405]}, {"key": "hardware-and-software", "type": "definition", "offset": [456, 477]}], "samples": [{"hash": "4lMdq4JiELt", "uri": "/contracts/4lMdq4JiELt#current-system", "label": "Contract for Automated Materials Handler Items and Warranty Continuation for Hardware and Software", "score": 34.0700683594, "published": true}], "hash": "6c438815d09ec18a965d9cabf63c8e4a", "id": 5}, {"snippet": "The Grantee is authorized and required to operate Grantee\u2019s existing Institutional Network, and to provide service substantially equivalent to its existing service, within its Franchise Area as of the Effective Date of this Agreement, until such time as the Institutional Network is upgraded, as provided herein.", "size": 1, "snippet_links": [{"key": "the-grantee", "type": "definition", "offset": [0, 11]}, {"key": "to-operate", "type": "definition", "offset": [39, 49]}, {"key": "institutional-network", "type": "clause", "offset": [69, 90]}, {"key": "to-provide", "type": "clause", "offset": [96, 106]}, {"key": "substantially-equivalent", "type": "definition", "offset": [115, 139]}, {"key": "existing-service", "type": "clause", "offset": [147, 163]}, {"key": "franchise-area", "type": "definition", "offset": [176, 190]}, {"key": "effective-date-of-this-agreement", "type": "definition", "offset": [201, 233]}], "samples": [{"hash": "im2STUpI2Ux", "uri": "/contracts/im2STUpI2Ux#current-system", "label": "Cable Franchise Agreement", "score": 25.4228801727, "published": true}], "hash": "b341f3e06ace3564cd9af586108d3613", "id": 6}, {"snippet": "(1) The Franchisee is authorized and required to operate its existing System, and to provide service substantially equivalent to its existing service, within the County as of the Effective Date of this Agreement.\n(2) The Franchisee shall implement a preventive maintenance plan to sweep and balance the trunk of the entire distribution system, including all trunk amplifiers from the headend to the last bridger amplifier, including any active return path. As picture quality problems unrelated to frequency response are discovered as the System is swept and balanced, that portion of plant will be inspected and any plant-related problems causing poor pictures will be corrected. The Franchisee shall carry out this maintenance plan pursuant to a reasonable implementation plan that it establishes in consultation with the County. If in testing the System after sweeping and balancing it is found that portions of the distribution system nonetheless demonstrate poor quality related to frequency problems, then at a minimum the remaining part of those portions of the distribution system will also be swept and balanced.\n(3) The Franchisee shall provide the County with a monthly report on its system\u2019s status with regard to the maintenance plan specified in Section 6(b)(2), to be delivered on or before the tenth of each month. Such report shall indicate the number of service calls and the reason for the calls during the previous month.", "size": 1, "snippet_links": [{"key": "to-operate", "type": "definition", "offset": [46, 56]}, {"key": "existing-system", "type": "clause", "offset": [61, 76]}, {"key": "to-provide", "type": "clause", "offset": [82, 92]}, {"key": "substantially-equivalent", "type": "definition", "offset": [101, 125]}, {"key": "existing-service", "type": "clause", "offset": [133, 149]}, {"key": "the-county", "type": "definition", "offset": [158, 168]}, {"key": "effective-date-of-this-agreement", "type": "definition", "offset": [179, 211]}, {"key": "maintenance-plan", "type": "clause", "offset": [261, 277]}, {"key": "distribution-system", "type": "definition", "offset": [323, 342]}, {"key": "quality-problems", "type": "clause", "offset": [468, 484]}, {"key": "frequency-response", "type": "clause", "offset": [498, 516]}, {"key": "the-system", "type": "definition", "offset": [535, 545]}, {"key": "pursuant-to-a", "type": "definition", "offset": [734, 747]}, {"key": "implementation-plan", "type": "clause", "offset": [759, 778]}, {"key": "in-consultation-with", "type": "definition", "offset": [799, 819]}, {"key": "the-distribution", "type": "clause", "offset": [915, 931]}, {"key": "poor-quality", "type": "definition", "offset": [963, 975]}, {"key": "related-to", "type": "clause", "offset": [976, 986]}, {"key": "provide-the", "type": "clause", "offset": [1147, 1158]}, {"key": "monthly-report", "type": "definition", "offset": [1173, 1187]}, {"key": "with-regard-to", "type": "clause", "offset": [1211, 1225]}, {"key": "the-maintenance", "type": "clause", "offset": [1226, 1241]}, {"key": "number-of", "type": "definition", "offset": [1362, 1371]}, {"key": "service-calls", "type": "clause", "offset": [1372, 1385]}], "samples": [{"hash": "1LgNBGjigK1", "uri": "/contracts/1LgNBGjigK1#current-system", "label": "Franchise Agreement", "score": 19.0, "published": true}], "hash": "70396592e865ec1aa57ce334f3f609ad", "id": 7}, {"snippet": "The Grantee is authorized and required to operate Grantee's Cable System as it exists on the date hereof, including without limitation the existing Institutional Network, and to provide service substantially equivalent to its existing service, within its Franchise Area as of the Effective Date of this Agreement, until such time as the HSN and Institutional Network are upgraded, as provided herein.", "size": 1, "snippet_links": [{"key": "the-grantee", "type": "definition", "offset": [0, 11]}, {"key": "to-operate", "type": "definition", "offset": [39, 49]}, {"key": "cable-system", "type": "definition", "offset": [60, 72]}, {"key": "date-hereof", "type": "clause", "offset": [93, 104]}, {"key": "including-without-limitation", "type": "clause", "offset": [106, 134]}, {"key": "institutional-network", "type": "clause", "offset": [148, 169]}, {"key": "to-provide", "type": "clause", "offset": [175, 185]}, {"key": "substantially-equivalent", "type": "definition", "offset": [194, 218]}, {"key": "existing-service", "type": "clause", "offset": [226, 242]}, {"key": "franchise-area", "type": "definition", "offset": [255, 269]}, {"key": "effective-date-of-this-agreement", "type": "definition", "offset": [280, 312]}], "samples": [{"hash": "bcR5nsgyhKB", "uri": "/contracts/bcR5nsgyhKB#current-system", "label": "Cable Franchise Agreement (Media General Inc)", "score": 18.0, "published": true}], "hash": "8b8724776d62b49488a1c661fc60c516", "id": 8}, {"snippet": "The current Genetec Security Video Management System consists of: \u2022 Genetec Security Center 5.11 Surveillance OS \u2022 800 Omnicast camera licenses \u2022 One (1) Genetec Streamvault 2020E series Directory server", "size": 1, "snippet_links": [{"key": "the-current", "type": "clause", "offset": [0, 11]}, {"key": "management-system", "type": "definition", "offset": [35, 52]}], "samples": [{"hash": "gTNZhxBNwbb", "uri": "/contracts/gTNZhxBNwbb#current-system", "label": "Maintenance and Support Services Agreement", "score": 33.664691925, "published": true}], "hash": "2b9ebe2262bd8b8153512567d289dab7", "id": 9}, {"snippet": "The current SirsiDynix ILS was installed in June 2003 and is presently SaaS hosted by SirsiDynix. Currently the library is using SirsiDynix Symphony Workflows 4.1.0.0.1371 Unicode for the staff catalog and Enterprise 5.2.1.2 for the patron catalog. OCPL uses the following modules: Acquisitions, Administration, Cataloging, Circulation, Configuration, Reports and Serial Control. OCPL uses BlueCloud Analytics, SirsiDynix\u2019s data reporting tool. OCPL uses EDI for ordering. OCPL uses SIP2 for self-check, ecommerce, pc reservation and print release stations. Patrons can pay bills online through the Enterprise catalog, as well as place, suspend and manage holds, renew items, manage their accounts, check out ebooks and eaudiobooks, and add items to lists.", "size": 1, "snippet_links": [{"key": "the-current", "type": "clause", "offset": [0, 11]}, {"key": "by-sirsidynix", "type": "clause", "offset": [83, 96]}, {"key": "reporting-tool", "type": "definition", "offset": [429, 443]}, {"key": "pay-bills", "type": "clause", "offset": [570, 579]}, {"key": "the-enterprise", "type": "clause", "offset": [595, 609]}, {"key": "check-out", "type": "definition", "offset": [699, 708]}], "samples": [{"hash": "bqJv6wWzMtd", "uri": "/contracts/bqJv6wWzMtd#current-system", "label": "Integrated Library System Contract", "score": 34.1690948451, "published": true}], "hash": "f353d4f0b9dd79227b8309fa086b7f4b", "id": 10}], "next_curs": "ClcSUWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjMLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhdjdXJyZW50LXN5c3RlbSMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"children": [], "size": 13, "parents": [["amendment-of-franchise-agreement", "Amendment of Franchise Agreement"], ["system-maintenance", "System Maintenance"], ["employee-eligibility-verification", "Employee Eligibility Verification"], ["order-dates", "Order Dates"], ["upgrade-option", "Upgrade Option"]], "title": "Current System", "id": "current-system", "related": [["management-system", "Management System", "Management System"], ["quality-management-system", "Quality Management System", "Quality Management System"], ["dtc-direct-registration-system-and-profile-modification-system", "DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM", "DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM"], ["system-logging", "System Logging", "System Logging"], ["system-timeout", "System Timeout", "System Timeout"]], "related_snippets": [], "updated": "2025-07-17T06:09:22+00:00", "also_ask": ["What are the essential elements that must be defined in a 'Current System' clause to avoid ambiguity?", "How can the scope of 'Current System' be strategically limited or expanded during negotiations?", "What are the most common risks or liabilities associated with an inadequately defined 'Current System'?", "How have courts interpreted disputes over the definition or boundaries of a 'Current System'?", "What industry standards or benchmarks should be referenced to strengthen the enforceability of a 'Current System' clause?"], "drafting_tip": "Specify the components and functions of the 'Current System' to avoid ambiguity; reference relevant documentation to ensure clarity; define update procedures to maintain accuracy.", "explanation": "The \"Current System\" clause defines the specific version or configuration of a system, software, or process that is in use at the time an agreement is made. This clause typically outlines the technical specifications, features, or operational parameters of the system as it exists, ensuring all parties have a shared understanding of the baseline. For example, it may reference a particular software release or hardware setup. Its core function is to establish a clear reference point, preventing disputes about what constitutes the agreed-upon system and providing a basis for evaluating future changes or upgrades."}, "json": true, "cursor": ""}}