Customer Originated Changes (COC Sample Clauses

POPULAR SAMPLE Copied 13 times
Customer Originated Changes (COC. If the Buyer wishes to introduce Buyer originated data (hereinafter “COC Data”) into any of the customized Technical Data that are identified as eligible for such incorporation in the Seller’s then current Customer Services Catalog, the Buyer will notify the Seller of such intention. The incorporation of any COC Data will be performed under the methods and tools for achieving such introduction and the conditions specified in the Seller’s then current Customer Services Catalog.
Customer Originated Changes (COC. Upon the Buyer’s request, Buyer-originated data (“COC Data”) may be incorporated into any of the Technical Data eligible for such incorporation as defined in the Seller’s then current CS Catalog. COC Data shall be developed and introduced by the Buyer according to the methods and tools for achieving such introduction and the conditions set forth in the CS Catalog. The Buyer shall ensure that any COC Data is in compliance with the requirements of its local Aviation Authorities. Incorporation of any COC Data shall be at the Buyer’s sole risk, and the Buyer shall indemnify the Seller against any liability whatsoever with respect to the contents, effect of incorporations or costs attributable to incorporation of COCs.
Customer Originated Changes (COC. In the event of the Buyer wishing to introduce Buyer originated data, including BFE Data after the initial issue of the Technical Data, (hereinafter “COC Data”) into any of the customized Technical Data that are identified as eligible for such incorporation in the Seller’s then current Customer Services Catalog, the Buyer shall notify the Seller of such intention. The incorporation of any COC Data shall be performed under the methods and tools for achieving such introduction and the conditions specified in the Seller’s then current Customer Services Catalog. Execution Version Avolon – A330neo Purchase Agreement, ref CLC-CT1404183 14.9.1 The Technical Data listed herebelow are provided on DVD and include integrated software (hereinafter together referred to as “AirN@v Family”). 14.9.2 The AirN@v Family covers several Technical Data domains, reflected by the following AirN@v Family products: • AirN@v / Maintenance, • AirN@v / Planning, • AirN@v / Repair, • AirN@v / Workshop, • AirN@v / Associated Data, • AirN@v / Engineering. 14.9.3 The licensing conditions for the use of AirN@v Family integrated software shall be as set forth in Part 1 of Exhibit I to the Agreement, “End-User License Agreement for Airbus Software”. 14.9.4 The revision service and the license to use AirN@v Family products shall be granted **** for the duration of the corresponding Revision Service Period. At the end of such Revision Service Period, the yearly revision service for AirN@v Family products and the associated license fee shall be provided to the Buyer under the commercial conditions set forth in the Seller’s then current Customer Services Catalog.
Customer Originated Changes (COC. Buyer-originated data that are introduced into Seller’s Technical Data and Documentation, as more completely set forth in Clause 14.10 of this Agreement. Customization Milestone Chart — as referred to in Clause 2.2 of this Agreement. Delivery — the transfer of title to the Aircraft from the Seller to the Buyer, in accordance with Clause 9. Delivery Date — the date on which Delivery will occur, or occurs, as the context may require. Delivery Locationthe facilities of the Manufacturer at the location of final assembly of the Aircraft, which is currently at Airbus France S.A.S. works in Toulouse, France, for the A320 model aircraft, and at Airbus Deutschland GmbH works in Hamburg, Germany, for the A319 and A321 model aircraft. Development Changes — as defined in Clause 2.1.2.4 of this Agreement. DGAC — the Direction Générale de l’Aviation Civile of France, or any successor thereto. EASA — European Aviation Safety Agency or any successor agency thereto. Excusable Delaydelay in delivery or failure to deliver an Aircraft due to causes specified in Clause 10.1 of this Agreement.
Customer Originated Changes (COC. In the event of the Buyer wishing to introduce Buyer originated data (hereinafter “COC Data”) into any of the customized Technical Data that are identified as eligible for such incorporation in the Seller’s then current Customer Services Catalog, the Buyer shall notify the Seller of such intention. The incorporation of any COC Data shall be performed under the methods and tools for achieving such introduction and the conditions specified in the Seller’s then current Customer Services Catalog. A350 XWB – TAM – 12/2007 “[***]” This information is subject to confidential treatment and has been omitted and filed separately with the commission.
Customer Originated Changes (COC. If the Buyer elects to include Buyer originated data (hereinafter “COC Data”) into any of the customized Technical Data that are identified as eligible for such incorporation in the Seller’s then current Customer Services Catalog, the Buyer shall notify the Seller of such election. The incorporation of any COC Data shall be perfomed under the methods and tools for achieving such introduction and the conditions specified in the then current ANACS Customer Services Catalog. COC Data will be developed by the Buyer according to the methods and tools for achieving such introduction issued by the Seller. The Buyer will ensure that any COC Data is in compliance with the requirements of the Buyer’s Aviation Authorities. Except for any Seller induced errors to the COC Data during its incorporation into the Technical Data, any COC Data will be at the Buyer’s sole risk, and [*] 9.1 The Technical Data listed below shall be provided through an advanced consultation tool (hereinafter referred to as “AirN@v Services”). The applicable Technical Data are the following: • AirN@v/Maintenance: • Aircraft Maintenance Manual, • Illustrated Parts Catalog (Airframe/ Powerplant), • Trouble Shooting Manual, • Aircraft Schematics Manual, • Aircraft Wiring Lists, • Aircraft Wiring Manual, • Electrical Standard Practices Manual. • AirN@v/Associated Data: • Consumable Material List, • Standards Manual, • Electrical Standard Practices Manual. • AirN@v/Engineering 9.2 The licensing conditions for the use of AirN@v Services shall be as set forth in Part 1 of Exhibit I to the Agreement, “Licence for Use of Software”. 9.3 The license to use AirN@v Services as described above shall be granted [*] for the Aircraft [*] the revisions of the affected Technical Data are [*] in accordance with Clause 14A.5. 10.1 The Technical Data defined in Exhibit “G” as being provided on-line shall be made available to the Buyer through the Secure Area of the Airbus customer portal Airbus|World (“Airbus|World”), as further described in Part 2 of Exhibit I to the Agreement.
Customer Originated Changes (COC. If the Buyer wishes to introduce Buyer originated data (“COC Data”) into any of the customized Technical Data that are identified as eligible for such incorporation in the Seller’s then current Customer Services Catalog, the Buyer shall notify the Seller of such intention. The incorporation of any COC Data shall be performed under the methods and tools for achieving such introduction and the conditions specified in the Seller’s then current Customer Services Catalog. ▇▇▇▇▇▇▇▇▇ – United Airlines, Inc. – A350-900XWB Purchase AgreementLetter Agreement No.5 LA5-6
Customer Originated Changes (COC. In the event of the Buyer wishing to introduce Buyer originated data. including BFE Data after the initial issue of the Technical Data, (hereinafter “COC Data”) into any of the customized Technical Data that are identified as eligible for such incorporation in the Seller’s then current Customer Services Catalog, the Buyer shall notify the Seller of such intention. The incorporation of any COC Data shall be performed under the methods and tools for achieving such introduction and the conditions specified in the Seller’s then current Customer Services Catalog. A320F NEO - CES 2013 Private & Confidential CT1302606