Current System Sample Clauses

Current System. The existing manual driver’s 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’s’ licences were issued in Dar as Salaam. If the regional distribution of driver’s 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 Table 1 Transactions per Region (220 working days per year) 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
Sample 1Sample 2
AutoNDA by SimpleDocs
Current System. (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.
Sample 1
Current System. The Grantee is authorized and required to operate Grantee’s 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.
Sample 1
Current System. 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’s open data portal (xxxxx://xxxx.xxxxxxxxxxx.xxx/). 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 Table A: Office of the Chief Information Officer Information Request Process Flow Diagram : City of Austin Statement of Work Public Information Request System Table B: Information Request Workflow : City of Austin Statement of Work Public Information Request System
Sample 1
Current System. The Grantee is authorized and required to operate Grantee’s existing Cable System as set forth in Section 4(a) and (b) and to provide service meeting all applicable standards.
Sample 1
Current System. The current EMS Data System is provided by Lancet Technology, Inc., located in Boston, Massachusetts. It includes three (3) separate modules; Central - One, Trauma – One, and Certification – 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: Central – One:  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.  Each Base Hospital’s (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.  The current EMS Data Set is based on locally created standards, and is very limited in its scope and focus.  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 – 60,000 patient encounters per year are entered.  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.  Database is SQL and resides on the server managed by OCHCA IT. Trauma – One:  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’s 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.  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.  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.  Each Trauma Center’s 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.  Data ...
Sample 1
Current System. 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.
Sample 1
AutoNDA by SimpleDocs
Current System. The current EMS Data System is provided by Lancet Technology, Inc., located in Boston, Massachusetts. It includes three (3) separate modules; Central - One, Trauma – One, and Certification – 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: County of Orange Health Care Agency 17 MA-042-10013343 Orange County – Medical Emergency Data System Central – One: 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. Each Base Hospital‟s (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. The current EMS Data Set is based on locally created standards, and is very limited in its scope and focus. 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 – 60,000 patient encounters per year are entered. 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. Database is SQL and resides on the server managed by OCHCA IT. Trauma – One: 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‟s 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. 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. 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. Each Trauma Center‟s Trauma Registry Data application is set up differently. System-wide updates are very difficult, or impossible. Each Trauma Ce...
Sample 1

Related to Current System

  • DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM (a) Notwithstanding the provisions of Section 2.4 of the Deposit Agreement, the parties acknowledge that DTC’s Direct Registration System (“DRS”) and Profile Modification System (“Profile”) apply to the American Depositary Shares upon acceptance thereof to DRS by DTC. DRS is the system administered by DTC that facilitates interchange between registered holding of uncertificated securities and holding of security entitlements in those securities through DTC and a DTC participant. Profile is a required feature of DRS that allows a DTC participant, claiming to act on behalf of an Owner of American Depositary Shares, to direct the Depositary to register a transfer of those American Depositary Shares to DTC or its nominee and to deliver those American Depositary Shares to the DTC account of that DTC participant without receipt by the Depositary of prior authorization from the Owner to register that transfer.

  • Monitoring System In each case in which the Custodian has exercised delegated authority to place Assets with a Foreign Custodian, the Custodian shall establish a system, to re-assess or re-evaluate selected Foreign Custodians, at least annually in accordance with Rule 17f-5(c)(3).

  • PFPC System PFPC shall retain title to and ownership of any and all data bases, computer programs, screen formats, report formats, interactive design techniques, derivative works, inventions, discoveries, patentable or copyrightable matters, concepts, expertise, patents, copyrights, trade secrets, and other related legal rights utilized by PFPC in connection with the services provided by PFPC to the Fund.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

  • IT Systems Except as would not, individually or in the aggregate, have a Material Adverse Effect, the Company reasonably believes that (i) the Company and the Subsidiaries own or have a valid right to access and use all computer systems, networks, hardware, software, databases, websites, and equipment used to process, store, maintain and operate data, information, and functions used in connection with the business of the Company and the Subsidiaries (the “Company IT Systems”), (ii) the Company IT Systems are adequate for, and operate and perform as required in connection with, the operation of the business of the Company and the Subsidiaries as currently conducted and (iii) the Company and the Subsidiaries have implemented reasonable backup, security and disaster recovery technology consistent with applicable regulatory standards;

  • Measurement and Monitoring Tools Contractor shall implement measurement and monitoring tools and procedures reasonably designed to measure its performance of the Services and assess such performance against any applicable service levels. Contractor shall provide LAUSD with a monthly report of service level performance under any applicable Work Order. Upon LAUSD’s request, Contractor shall provide LAUSD with access to the measurement and monitoring tools described herein, and to any information that they generate.

  • Data Retention The Company will hold and use the Data only as long as is necessary to implement, administer and manage the Grantee’s participation in the Plan, or as required to comply with legal or regulatory obligations, including under tax and security laws.

Time is Money Join Law Insider Premium to draft better contracts faster.