End User Information Requirements Sample Clauses

End User Information Requirements. End User shall provide the necessary information for each Service Location as requested by Service Provider based upon the actual services being ordered. The required information will be set forth in applicable Service Order Forms, Exhibits and/or Attachments.
AutoNDA by SimpleDocs
End User Information Requirements. End User shall provide the necessary information for each Service location set forth in the Order or as otherwise may be requested by Service Provider from time to time. This Exhibit and/or Service Orders, is part of, and subject to, the EUSA. All Services provided hereunder are subject to the EUSA, and in the event of a conflict between the EUSA and this Exhibit, this Exhibit will prevail.

Related to End User Information Requirements

  • Information Requirements (a) The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder of Registrable Securities and take such further reasonable action as any Holder of Registrable Securities may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder of Registrable Securities, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company's most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Information Requirement The successful bidder's shall be required to advise the Office of Management and Budget, Government Support Services of the gross amount of purchases made as a result of the contract.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Information Required Such records must contain the name; Social Security number; last known address, telephone number, and email address of each such worker; each worker's correct classification(s) of work actually performed; hourly rates of wages paid (including rates of contributions or costs anticipated for bona fide fringe benefits or cash equivalents thereof of the types described in 40 U.S.C. 3141(2)(B) of the Xxxxx-Xxxxx Act); daily and weekly number of hours actually worked in total and on each covered contract; deductions made; and actual wages paid.

  • Publication Requirements Those seeking to include renderings of more than 10 images from the UND Biometrics Database in reports, papers, and other documents to be published or released must first obtain approval in writing from the UND Principal Investigator. In no case should the face images be used in a way that could cause the original subject embarrassment or mental anguish.

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Documentation Requirements (a) An employee must apply for personal leave in writing in the form required by the CEO as soon as it is reasonably practicable for the employee to make the application.

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave.

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!