Characteristics The Contracts have the following characteristics: (i) all the Contracts are secured by Motorcycles; (ii) no Contract has a remaining maturity of more than 84 months; and (iii) the final scheduled payment on the Contract with the latest maturity is due no later than July 27, 2030. Approximately 63.90% of the Pool Balance as of the Cutoff Date is attributable to loans for purchases of new Motorcycles and approximately 36.10% is attributable to loans for purchases of used Motorcycles. No Contract was originated after the Cutoff Date. No Contract has a Contract Rate less than 0.010%.
CHARACTERISTICS OF THE ACADEMY The characteristics of the Academy set down in Section 1(6) of the Academies Act 2010, are that:
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers.
9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA.
9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups:
2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment;
2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and
2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic.
2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic).
2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions).
2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate.
2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,
Characteristics of Receivables Each Receivable (A) shall have been originated in the United States by a Dealer for the retail sale of the related Financed Vehicle in the ordinary course of such Dealer’s business, shall have been fully and properly executed by the parties thereto, shall have been purchased by the Seller from such Dealer under an existing agreement with the Seller, shall have been validly assigned by such Dealer to the Seller in accordance with its terms and, to the best knowledge of the Seller, shall have been sold by a Dealer without fraud or misrepresentation, (B) shall have created or shall create a valid, subsisting and enforceable first priority security interest in favor of the Seller in the related Financed Vehicle, (C) shall contain customary and enforceable provisions such that the rights and remedies of the holder thereof shall be adequate for realization against the collateral of the benefits of the security, (D) shall provide for level Monthly Payments (provided that the first or last payment in the life of the Receivable may be minimally different from the level payment) that fully amortize the Amount Financed over its original term and shall provide for a finance charge or shall yield interest at its APR, (E) shall provide for, in the event that such Receivable is prepaid, a prepayment that fully pays the Principal Balance and includes accrued but unpaid interest at least through the date of prepayment in an amount calculated by using an interest rate at least equal to its APR, (F) shall have an Obligor that is not a federal, state or local governmental entity and (G) is a retail installment contract.
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.
Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures.
5.2.2 When One-Way or Two-Way Interconnection Trunks are provisioned using a DS3 interface facility, if Onvoy orders the multiplexed DS3 facilities to a Frontier Central Office that is not designated in the NECA 4 Tariff as the appropriate Intermediate Hub location (i.e., the Intermediate Hub location in the appropriate Tandem subtending area based on the LERG), and the provision of such facilities to the subject Central Office is technically feasible, the Parties shall negotiate in good faith reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures.
5.2.3 Each Party will identify its Carrier Identification Code, a three or four digit numeric code obtained from Telcordia, to the other Party when ordering a trunk group.
5.2.4 For multi-frequency (MF) signaling each Party will out pulse ten (10) digits to the other Party, unless the Parties mutually agree otherwise.
5.2.5 Each Party will use commercially reasonable efforts to monitor trunk groups under its control and to augment those groups using generally accepted trunk- engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk-engineering techniques for trunks subject to this Attachment.
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.
Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection.
2.1.1 Each Party, at its own expense, shall provide transport facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA selected by PNG.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
