Local Agency Project File Sample Clauses

Local Agency Project File. (Original & Contract)
AutoNDA by SimpleDocs

Related to Local Agency Project File

  • SYSTEM AGENCY DATA A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.

  • Inspection Checklist (check one) ☐ In order to avoid disagreements about the condition of the Premises, at the time of accepting possession of the Premises, Tenant will complete the Inspection Checklist incorporated herein by reference and attached hereto as Exhibit B and record any damage or deficiencies that exist at the commencement of the Term. Landlord will be liable for the cost of any cleaning or repair to correct damages found at the time of the inspection. Tenant will be liable for the cost of any cleaning and/or repair to correct damages found at the end of the Term if not recorded on the inspection checklist, normal wear and tear excepted. ☐ The Tenant is NOT required to complete an inspection checklist.

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

  • Inventory Report – Remote Premises The locations of the Remote Premises (e.g., Feeder Distribution Interfaces, "FDI") and the End User Customer addresses served by each Remote Premises are available to CLEC through the Raw Loop Data Tool. Remote Premises with digital loop carrier and pair gain equipment will be provided on the web site in the ICONN database. (ICONN is available through the Qwest web site located at xxxx://xxx.xxxxx.xxx/iconn.) If CLEC is unable to determine the information it seeks regarding the Remote Premises after using such database tools, Qwest will provide CLEC with a report that contains the information. The Parties agree that a charge may apply to such report, based on time and material, unless the database information is inaccurate or unusable for the Remote Premises then no charge would apply. Qwest will provide CLEC access to relevant plats, maps, engineering records and other data in accordance with Section 10.8.2.4. In addition, CLEC can request a copy of Qwest's distribution area map associated with the Remote Premises, with a charge for time and material.

  • Grievance File Records involving the processing of an employee's grievance, such as the grievance form, step appeals/responses, and settlement documents, will be kept in a file separate from the employee’s personnel file. It is not the intent of this section to exclude from the employee's personnel file final disciplinary action documents, including those that result from a settlement agreement.

  • System Agency 1. will monitor Grantee for programmatic and financial compliance with this Contract and;

  • Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -­‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-­‐key cryptography, Symmetric-­‐key cryptography, Hash and Compression are those enumerated in XXX 0000, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-­‐free. The process to follow for the data file in original text format is:

  • Inspection Report The Client and the Company agree that the Company, and its inspector(s), will prepare a written home inspection report which shall:

  • Inspection Reports A "full inspection report" comprises a Site Master File (compiled by the manufacturer or by the inspectorate) and a narrative report by the inspectorate. A "detailed report" responds to specific queries about a firm by the other Party.

  • Grievance Files Written grievances and responses will be maintained separately from the employee’s personnel file.

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