ESCROW MATERIAL Sample Clauses

ESCROW MATERIAL. BANK OF NORTH DAKOTA shall safe keep said ESCROW MATERIAL and shall release ESCROW MATERIAL Packages to LICENSEE upon receipt of the following exclusive conditions:
Sample 1

Related to ESCROW MATERIAL

  • Source Code Escrow Pursuant to 62 O.S. § 34.31, if customized computer software is developed or modified exclusively for a State agency, the Supplier has a continuing obligation to comply with such law and place the source code for such software and any modifications thereto into escrow with an independent third party escrow agent. Supplier shall pay all fees charged by the escrow agent and enter into an escrow agreement, the terms of which are subject to the prior written approval of the State, including terms that provide the State receives ownership of all escrowed source code upon the occurrence of any of the following:

  • Data Escrow Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).

  • Source Code 5.1 Nothing in this XXXX shall give to the User or any other person any right to access or use the Source Code or constitute any licence of the Source Code.

  • Missing or Insufficient Review Materials Upon receipt of the Review Materials, the Asset Representations Reviewer will review the Review Materials to determine if any Review Materials are missing or insufficient for the Asset Representations Reviewer to perform any Test. If the Asset Representations Reviewer determines any missing or insufficient Review Materials, the Asset Representations Reviewer will notify the Servicer promptly, and in any event no less than 20 calendar days before completing the Asset Representations Review. The Servicer will have 15 calendar days to give the Asset Representations Reviewer access to the missing Review Materials or other documents or information to correct the insufficiency. If the missing Review Materials or other documents have not been provided by the Servicer within 15 calendar days, the related Review Report will report a Test Fail for each Test that requires use of the missing or insufficient Review Materials.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • Client Records 26.2.1 CONTRACTOR shall prepare and maintain accurate and complete records of clients served and dates and type of services provided under the terms of this Contract in a form acceptable to ADMINISTRATOR.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Receivable Files Complete There exists a Receivable File pertaining to each Receivable. Related documentation concerning the Receivable, including any documentation regarding modifications of the Contract, will be maintained electronically by the Servicer in accordance with customary policies and procedures. With respect to any Receivables that are tangible chattel paper, the complete Receivable File for each Receivable currently is in the possession of the Custodian.

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • Project Records ‌ As further described below, Project records include but are not limited to Grantee, financial, and voucher records. All Project records must be retained for a period of three (3) years after final payment under this Grant. All Project records are subject to audit pursuant to Section P of this Grant Agreement. Upon completion of the third year of record retention, the Grantee shall submit all Project records to CARB. Hardcopy of electronic records are suitable. Acceptable forms of electronic media include hard drives, CDs, DVDs, and flash drives. Other forms of electronic media may be allowed based on prior written concurrence from CARB.

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