Lockbox Specific a. All requested reports meet CDCR needs and have signed off approval of format.
Lockbox Specific Sample Clauses
Related to Lockbox Specific
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
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.
Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.
Transfer of Servicing Between Master Servicer and Special Servicer; Record Keeping (a) Upon determining that any Serviced Loan has become a Specially Serviced Loan, the Master Servicer shall promptly give written notice thereof to the Special Servicer, any related Serviced Companion Loan Holder (in the case of a Serviced Loan Combination), the Operating Advisor, the Certificate Administrator, the Trustee, the related Directing Holder (prior to the occurrence and continuance of a Consultation Termination Event with respect to the related Mortgage Loan) and, for posting to the Rule 17g-5 Information Provider’s Website pursuant to Section 12.13 of this Agreement, the Rule 17g-5 Information Provider and shall promptly deliver a copy of the Servicing File to the Special Servicer and concurrently provide a copy of such Servicing File to the Operating Advisor and shall use its reasonable efforts to provide the Special Servicer with all information, documents (but excluding the original documents constituting the Mortgage File, but including copies thereof) and records (including records stored electronically on computer tapes, magnetic discs and the like) relating to such Serviced Loan and reasonably requested by the Special Servicer to enable it to assume its duties hereunder with respect thereto without acting through a Sub-Servicer. The Master Servicer shall use its reasonable efforts to comply with the preceding sentence within five (5) Business Days of the date such Serviced Loan became a Specially Serviced Loan and in any event shall continue to act as Master Servicer and administrator of such Serviced Loan until the Special Servicer has commenced the servicing of such Serviced Loan, which shall occur upon the receipt by the Special Servicer of the Servicing File. With respect to each such Serviced Loan that becomes a Specially Serviced Loan, the Master Servicer shall instruct the related Mortgagor to continue to remit all payments in respect of such Serviced Loan to the Master Servicer. The Master Servicer shall forward any notices it would otherwise send to the Mortgagor of such a Specially Serviced Loan to the Special Servicer who shall send such notice to the related Mortgagor. Upon determining that a Specially Serviced Loan has become a Corrected Loan, the Special Servicer shall promptly give written notice thereof to the Master Servicer, the Trustee, the Operating Advisor, the Certificate Administrator, any related Serviced Companion Loan Holder, the related Directing Holder (prior to the occurrence and continuance of a Consultation Termination Event with respect to the related Mortgage Loan) and, for posting to the Rule 17g-5 Information Provider’s Website pursuant to Section 12.13 of this Agreement, the Rule 17g-5 Information Provider and, upon giving such notice and the return of the Servicing File to the Master Servicer, such Serviced Loan shall cease to be a Specially Serviced Loan in accordance with the first proviso of the definition of Specially Serviced Loans, the Special Servicer’s obligation to service such Serviced Loan shall terminate and the obligations of the Master Servicer to service and administer such Serviced Loan as a Serviced Loan that is not a Specially Serviced Loan shall resume. In addition, if the related Mortgagor has been instructed, pursuant to the preceding paragraph, to make payments to the Special Servicer, upon such determination, the Special Servicer shall instruct the related Mortgagor to remit all payments in respect of such Specially Serviced Loan directly to the Master Servicer.
Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.
Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
