DaR user application and registration Sample Clauses

DaR user application and registration. All passengers who make use of the DaR service are required to register for the service with the Operator through the DaR App, Website or Call Centre. As part of the registration, process prospective users are required to be interviewed and examined by an Occupational Therapist (OT) or Duly Registered Medical Practitioner. The Data Management Platform will facilitate user application, registration and issuing of a unique DaR Identification number. The interfaces that must be available for an applicant to register for the DaR service will include a DaR Website, DaR mobile application for iOS and Android mobile operating systems, DaR Call Centre and USSD, Email, social media platforms and SMS. In order to register for the Dial-a-Ride service the applicant needs to provide the Operator with their personal details: • First name and surname; • ID number; • Email address; • Preferred language; • Contact name and number in case of emergency; • Residential and postal address; • Work hours and work address; • Preferred method of contact; and • Information related to their disability, whether they use a mobility aid and whether they will require a personal care attendant (and their details) or guide dog to accompany them during travel. Applicants shall also be required to provide information about their anticipated regular trips: • Travel time; • Origin and destination; and • Trip purpose.
AutoNDA by SimpleDocs

Related to DaR user application and registration

  • LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.

  • NERC Registration If and to the extent any of the NTO’s facilities are NERC jurisdictional facilities, the ISO will register for certain NERC functions applicable to those NTO facilities. Such functions may include, without limitation, those functions designated by NERC to be “Reliability Coordinator” and “Balancing Authority” and “Transmission Planner” and “Planning Coordinator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.

  • Registration Data Upon placing an order for Pilot Voice, and at subsequent times as requested by Pilot, Customer agrees to provide Pilot with its (i) true, accurate, current, and complete business name, (ii) physical addresses where Voice Service will be used, (iii) 911 registered address for each applicable endpoint, (iv) a designated Account Administrator, and (v) user email addresses, phone numbers, and any other requested data which may be necessary to administer its Voice Service account (the “Account”) (collectively, “Registration Data”). Customer represents and warrants that the information it provides is accurate, current, and complete, and agrees to promptly update any of the information if it changes. If Customer provides Registration Data that is false, inaccurate, not current, incomplete, fraudulent, or otherwise unlawful, Pilot has the right, in its sole discretion, to suspend or terminate the Voice Services and refuse any and all current or future use of all Voice Services by Customer, its business(es), affiliates and all users of its Account. Upon provision of all Registration Data and acceptance of Customer’s Service Order, Pilot may provide Customer’s designated Account Administrator and other Pilot Voice users with, as applicable, administrator or user web portal logins and other Account information. Customer is solely liable for any transactions or activities by it or any third- party that occurs on its Account. Customer shall immediately notify Pilot of any unauthorized use of its Account or if any other breach of security has occurred. In no event shall Pilot be liable for any unauthorized, third-party use of your Account.

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

  • Expenses of Registration All expenses incurred in connection with registrations, filings or qualifications pursuant to Sections 2 and 3, including, without limitation, all registration, listing and qualifications fees, printers, legal and accounting fees shall be paid by the Company.

  • USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.

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