DCC DATA Sample Clauses

DCC DATA. ‌ The parties agree that as at the Signature Date, the provisions of clause 28.1 below do not apply to this agreement on the basis that the contractor will not receive either any transactional data or industry registration data in the performance of its services. In the event that a future requirement arises which means that the contractor will need to come into possession of either transactional data and / or industry registration data, then this clause 28.1 would become applicable once an appropriate Change Authorisation Note has been agreed between the parties for the requirement concerned.
Sample 1Sample 2See All (4)
DCC DATA. 35.1 The Contractor shall not delete or remove any proprietary notices contained within or relating to the DCC Data.
Sample 1

Related to DCC DATA

  • Electronic Data 7.1.1 The parties recognize that Contract Documents, including drawings, specifications and three-dimensional modeling (such as Building Information Models) and other Work Product may be transmitted among Owner, Design-Builder and others in electronic media as an alternative to paper hard copies (collectively “Electronic Data”).

  • Electronic Data Interchange (EDI This standard establishes the data contents of the Invoice Transaction Set (810) for use within the context of an EDI environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services.

  • Electronic Data Interchange If both Parties elect to facilitate business activities hereunder by electronically sending and receiving data in agreed formats (also referred to as Electronic Data Interchange or “EDI”) in substitution for conventional paper-based documents, the terms and conditions of this Agreement shall apply to such EDI activities.

  • EDI - Electronic Data Interchange The exchange of business data in a standardized format between business computer systems.

  • ETU Picnic Day In accordance with picnic day provision the Company shall require from an employee proof of picnic day attendance, ie ETU ticket purchase before payment will be made for the day. A ticket purchased in relation to an alternative union picnic day is not sufficient for the purposes of payment. Where possible no work shall be scheduled on the first Monday of December each year which is the Annual Building Industry Picnic Day.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Responsibility for Electronic Data The Student is solely responsible for any data stored on the Computer. It is the sole responsibility of the Student to backup such data as necessary.

  • Program Information The Heritage Greece Program is generally described in the literature provided to the Student and available online at: xxxx://xxx.xxx.xxx. It is understood and agreed that the information contained therein is descriptive only and may be changed in the discretion of ACG which reserves the right to make Program changes at any time and for any reason, with or without notice. ACG and/or the Sponsor shall not be liable to the Student because of any such change. ACG reserves all rights, in its sole discre tion, to cancel the Program or any aspect thereof prior to or after departure, and in the case of cancellation after departure, to require the Student to return to the United States, if ACG determines or believes it is in the best interests of the Student.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

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