Corporate Formalities The Borrower will strictly observe limited liability company formalities in its dealings with the Servicer, the Parent, the Performance Guarantor, the Originators or any Affiliates thereof, and funds or other assets of the Borrower will not be commingled with those of the Servicer, the Parent, the Performance Guarantor, the Originators or any Affiliates thereof except as permitted by this Agreement in connection with servicing the Pool Receivables. The Borrower shall not maintain joint bank accounts or other depository accounts to which the Servicer, the Parent, the Performance Guarantor, the Originators or any Affiliate thereof (other than the Servicer solely in its capacity as such) has independent access. The Borrower is not named, and has not entered into any agreement to be named, directly or indirectly, as a direct or contingent beneficiary or loss payee on any insurance policy with respect to any loss relating to the property of the Servicer, the Parent, the Performance Guarantor, the Originators or any Subsidiaries or other Affiliates thereof. The Borrower will pay to the appropriate Affiliate the marginal increase or, in the absence of such increase, the market amount of its portion of the premium payable with respect to any insurance policy that covers the Borrower and such Affiliate.
Formalities Parties to this Agreement
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
Delivery of Additional Documentation Required Borrower shall from time to time execute and deliver to Bank, at the request of Bank, all Negotiable Collateral, all financing statements and other documents that Bank may reasonably request, in form satisfactory to Bank, to perfect and continue perfected Bank's security interests in the Collateral and in order to fully consummate all of the transactions contemplated under the Loan Documents.
Due Formation The Purchaser is duly formed, validly existing and in good standing in the jurisdiction of its organization. The Purchaser has all requisite power and authority to carry on its business as it is currently being conducted.
Escrow Format Specification 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.
Reimbursements and Purchase Orders Expense reimbursement is not guaranteed and, when possible, Board members should seek pre- approval of expenses by providing an estimation of expenses on the Board's standardized estimated expense approval form, except in situations when the expense is diminutive. When pre-approval is not sought, Board members must seek reimbursement on the Board's standardized expense reimbursement form. Expense reimbursements and purchase orders shall be presented to the Board in its regular bill process.
DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.
Contract Formation Subject to FAR Sections 1.601(a) and 43.102, the Government Order must be signed by a duly warranted contracting officer, in writing. The same requirement applies to contract modifications affecting the rights of the parties. All terms and conditions intended to bind the Government must be included within the contract signed by the Government.
ODUF Packing Specifications 6.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.
