Characteristics of braking systems Sample Clauses

Characteristics of braking systems. 5.2.1. Vehicles of categories M2, M3 and N 5.2.1.1. The set of braking systems with which a vehicle is equipped shall satisfy the requirements laid down for service, secondary and parking braking systems. 5.2.1.2. The systems providing service, secondary and parking braking may have common components so long as they fulfil the following conditions: 5.2.1.2.1. there shall be at least two controls, independent of each other and readily accessible to the driver from his normal driving position. For all categories of vehicles, except M2 and M3, every brake control (excluding an endurance braking system control) shall be designed such that it returns to the fully off position when released. This requirement shall not apply to a parking brake control (or that part of a combined control) when it is mechanically locked in an applied position; 5.2.1.2.2. the control of the service braking system shall be independent of the control of the parking braking system; 5.2.1.2.3. if the service braking system and the secondary braking system have the same control, the effectiveness of the linkage between that control and the different components of the transmission systems shall not be liable to diminish after a certain period of use; 5.2.1.2.4. if the service braking system and the secondary braking system have the same control, the parking braking system shall be so designed that it can be actuated when the vehicle is in motion. This requirement shall not apply if the vehicle's service braking system can be actuated, even partially, by means of an auxiliary control; 5.2.1.2.5. without prejudice to the requirements of paragraph 5.1.2.3. of this Regulation, the service braking system and the parking braking system may use common components in their transmission(s), provided that in the event of a failure in any part of the transmission(s) the requirements for secondary braking are still ensured; 5.2.1.2.6. in the event of breakage of any component other than the brakes (as defined in paragraph 2.6. of this Regulation) or the components referred to in paragraph 5.2.1.2.8. below, or of any other failure of the service braking system (malfunction, partial or total exhaustion of an energy reserve), the secondary braking system or that part of the service braking system which is not affected by the failure, shall be able to bring the vehicle to a halt in the conditions prescribed for secondary braking; 5.2.1.2.7. in particular, where the secondary braking system and the service...
AutoNDA by SimpleDocs

Related to Characteristics of braking systems

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

  • 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 The characteristics of the Academy set down in Section 1(6) of the Academies Act 2010, are that:

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

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

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

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

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!