OPEN BOOK DATA Sample Clauses

OPEN BOOK DATA. The Service Provider acknowledges the importance to the Purchaser of the Financial Transparency Objectives and the Purchaser’s need for complete transparency in the way in which the Charges are calculated. During the Term, and for a period of 7 years following the end of the Term, the Service Provider shall maintain and retain the Open Book Data; and disclose and allow the Purchaser and/or the Audit Agents access to the Open Book Data.
AutoNDA by SimpleDocs
OPEN BOOK DATA. 2.1 The Service Provider acknowledges the importance to the Authority of the Financial Transparency Objectives and the Authority’s need for complete transparency in the way in which the Charges are calculated.
OPEN BOOK DATA. The Supplier acknowledges the importance to the Authority of the Financial Transparency Objectives and the Authority’s need for complete transparency in the way in which the Charges are calculated. During the Term, and for a period of 7 years following the end of the Term, the Supplier shall: maintain and retain the Open Book Data; and disclose and allow the Authority and/or the Audit Agents access to the Open Book Data.

Related to OPEN BOOK DATA

  • 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.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.

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

  • Customer Data 5.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.

  • COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.

  • Reference Materials The Board agrees to continue to make available to employees the reference materials maintained by the district. Principals are encouraged to provide additional reference materials of high use in schools where feasible.

  • Invoice Data The Contractor shall report invoice data from each paid or remitted invoice within 30 calendar days after the end of the reporting quarter, including the invoice data on task orders issued through the GSA AAS Business System Portal. (Note: Whatever method the Contractor chooses (e.g., “each paid” or “remitted”) the Contractor must be consistent in their reporting method throughout the term of the OASIS Contract). If no Invoice Data was received during a required reporting period for a specific task order, the Contractor shall report in the “Zero Invoice Data” screen located in the CPRM system for that particular task order. Regardless of contract type, the Contractor shall report the following into the CPRM:

  • 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.

  • Web site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

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