ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery.
6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC.
6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.
Physical File Characteristics 7.2.1 The EODUF feed will be distributed to Comcast Phone over their existing Optional Daily Usage File (ODUF) feed. The EODUF messages will be intermingled among Comcast Phone’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format (2476) with an LRECL of 2472. The data on the EODUF will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays).
7.2.2 Data circuits (private line or dial-up) may be required between BellSouth and Comcast Phone for the purpose of data transmission. Where a dedicated line is required, Comcast Phone will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Comcast Phone will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Comcast Phone. Additionally, all message toll charges associated with the use of the dial circuit by Comcast Phone will be the responsibility of Comcast Phone. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. Version 4Q01 12/01/01 All equipment, including modems and software, that is required on Comcast Phone’s end for the purpose of data transmission will be the responsibility of Comcast Phone.
Certain Characteristics of the Receivables (A) Each Receivable had a remaining maturity, as of the Cutoff Date, of not less than three (3) months and not more than eighty-four (84) months.
(B) Each Receivable had an original maturity, as of the Cutoff Date, of not less than three (3) months and not more than eighty-four (84) months.
(C) Each Receivable had a remaining Principal Balance, as of the Cutoff Date, of at least $250 and not more than $150,000.
(D) Each Receivable had an Annual Percentage Rate, as of the Cutoff Date, of not more than 20%.
(E) No Receivable was more than thirty (30) days past due as of the Cutoff Date.
(F) Each Receivable arose under a Contract that is governed by the laws of the United States or any State thereof.
(G) Each Obligor had a billing address in the United States or a United States territory as of the date of origination of the related Receivable.
(H) Each Receivable is denominated in, and each Contract provides for payment in, United States dollars.
(I) Each Receivable arose under a Contract that is assignable without the consent of, or notice to, the Obligor thereunder, and does not contain a confidentiality provision that purports to restrict the ability of the Servicer to exercise its rights under the Sale and Servicing Agreement, including, without limitation, its right to review the Contract. Each Receivable prohibits the sale or transfer of the Financed Vehicle without the consent of the Servicer.
(J) Each Receivable arose under a Contract with respect to which GM Financial has performed all obligations required to be performed by it thereunder.
(K) No automobile related to a Receivable was held in repossession inventory as of the Cutoff Date.
(L) The Servicer’s records do not indicate that any Obligor was in bankruptcy as of the Cutoff Date.
(M) No Obligor is the United States of America or any State or any agency, department, subdivision or instrumentality thereof.
Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.
SIGNIFICANT LANDS INVENTORY FINDING Find that this activity is consistent with the use classification designated by the Commission for the land pursuant to Public Resources Code section 6370 et seq.
Preservative-treated Wood Containing Arsenic Grantee may not purchase preservative-treated wood products containing arsenic in the performance of this Agreement unless an exemption from the requirements of Chapter 13 of the San Francisco Environment Code is obtained from the Department of the Environment under Section 1304 of the Code. The term “preservative-treated wood containing arsenic” shall mean wood treated with a preservative that contains arsenic, elemental arsenic, or an arsenic copper combination, including, but not limited to, chromated copper arsenate preservative, ammoniacal copper zinc arsenate preservative, or ammoniacal copper arsenate preservative. Grantee may purchase preservative-treated wood products on the list of environmentally preferable alternatives prepared and adopted by the Department of the Environment. This provision does not preclude Grantee from purchasing preservative-treated wood containing arsenic for saltwater immersion. The term “saltwater immersion” shall mean a pressure-treated wood that is used for construction purposes or facilities that are partially or totally immersed in saltwater.
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.
Loss Leader; Recycled Products Contractor shall not sell or use any article or product as a “loss leader” as defined in Section 17030 of the Business and Professions Code. If Contractor will sell to the Judicial Council, or use in the performance of this Agreement, goods specified in PCC 12207 (for example, certain paper products, office supplies, mulch, glass products, lubricating oils, plastic products, paint, antifreeze, tires and tire-derived products, and metal products), then with respect to those goods: (i) Contractor shall use recycled products in the performance of this Agreement to the maximum extent doing so is economically feasible, and (ii) upon request, Contractor shall certify in writing under penalty of perjury, the minimum, if not exact, percentage of post consumer material as defined in the PCC 12200, in such goods regardless of whether the goods meet the requirements of PCC 12209.
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.
Recovery Schedule If the initial schedule or any current updates fail to reflect the Work’s actual plan or method of operation, or a contractual milestone date is more than fifteen (15) days behind, Owner may require that a recovery schedule for completion of the remaining Work be submitted. The Recovery Schedule must be submitted within seven (7) calendar days of Owner’s request. The Recovery Schedule shall describe in detail Construction Contractor’s plan to complete the remaining Work by the required Contract milestone date. The Recovery Schedule submitted shall meet the same requirements as the original Construction Schedule. The narrative submitted with the Recovery Schedule should describe in detail all changes that have been made to meet the Contract milestone dates.
