Characteristics of braking systems Sample Clauses

Characteristics of braking systems. 5.2.1. Vehicles of categories M2, M3 and N
AutoNDA by SimpleDocs

Related to Characteristics of braking systems

  • Characteristics The Initial Contracts have the following characteristics: (i) all the Contracts are secured by Motorcycles; (ii) no Initial Contract has a remaining maturity of more than 84 months; and (iii) the final scheduled payment on the Initial Contract with the latest maturity is due not later than June 2014. Approximately 77.89% of the Principal Balance of the Initial Contracts as of the Initial Cutoff Date is attributable to loans for purchases of new Motorcycles and approximately 22.11% is attributable to loans for purchases of used Motorcycles. No Initial Contract was originated after the Initial Cutoff Date. No Initial Contract has a Contract Rate less than 3.989%. The last scheduled payment date of the Contracts (including any Subsequent Contracts) is due not later than September 2014. Approximately 98.98% of the Principal Balance of the Initial Contracts as of the Initial Cutoff Date is attributable to loans to purchase Motorcycles manufactured by Harley-Davidson or Buell and approximately 1.02% of the Principal Balance of the Initial Contracts as of the Initial Cutoff Date is attributable to loans to purchase Motorcycles not manufactured by Harley-Davidson or Buell.

  • Components Patheon will purchase and test all Components (with the exception of Client-Supplied Components) at Patheon’s expense and as required by the Specifications.

  • CHARACTERISTICS OF THE ACADEMY 10) The characteristics of the Academy set down in Section 1(6) of the Academies Act 2010, are that:

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to <<customer_name>> via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage 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.

  • Characteristics of Receivables As of the Cut-Off Date (or such other date as may be specifically set forth below), each Receivable:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • ODUF Physical File Characteristics 6.2.1 The ODUF will be distributed to Dialtone & More via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. 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.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

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

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