Technical Level of Publications Sample Clauses

Technical Level of Publications. The level of Publications at delivery of any Aircraft will correspond to the configuration level of any such Aircraft as defined [*****] before such delivery. The Aircraft configuration level at delivery will be introduced into the Technical Publications at the first revision following the delivery. Significant modifications applied to any Aircraft when delivered and not dealt with in the Technical Documentation shall be covered in advance copies or temporary revisions. [*****] Confidential material redacted and filed separately with the Securities and Exchange Commission.
AutoNDA by SimpleDocs

Related to Technical Level of Publications

  • Specifications and Standards a) All articles supplied shall strictly conform to the specifications, trademark laid down in the bidding document and wherever articles have been required according to ISI/ ISO/ other applicable specifications/ certifications/ standards, those articles should conform strictly to those specifications/ certifications/ standards. The supply shall be of best quality and description. The decision of the competent authority/ purchase committee whether the articles supplied conforms to the specifications shall be final and binding on the supplier/ selected bidder.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.

  • Scientific Publications During the Research Program Term, neither Party shall first publish or first present in a public forum the scientific or technical results of any activity performed pursuant to this Agreement without the opportunity for prior review and comment by the other Party. Each Party agrees to provide the other Party with the opportunity to review any proposed abstract, manuscript or scientific presentation (including any verbal presentation) that relates to its activities performed pursuant to this Agreement during the Research Program Term, at least [**] days prior to its intended submission for publication and agrees, upon request, not to submit any such abstract or manuscript for publication until the other Party is given a reasonable period of time up to [**] to secure patent protection for any material in such publication that it believes to be patentable. Both Parties understand that a reasonable commercial strategy may require delay of publication of information or filing of patent applications first with respect to activities performed or results obtained pursuant to this Agreement during the Research Program Term, or not to publish at all if necessary to preserve trade secrets. The Parties agree to review and decide whether to delay publication of such information to permit filing of patent applications. Neither Party shall have the right to publish or present any Confidential Information of the other Party, except as provided in Section 9.2. After the Research Program Term, each Party and its Affiliates may publish or present results, data or scientific findings of any of their activities without the prior review of the other Party, provided that such publication or presentation does not disclose any of the other Party’s Confidential Information. Nothing contained in this Section 9.3 shall prohibit the inclusion of information necessary for a patent application; provided that the non-filing Party is given a reasonable opportunity to review the information to be included prior to submission of such patent application in accordance with Section 8.2. Nothing contained in this Section 9.3 shall prohibit either Party from disclosing the results, data or scientific findings of any activity performed by the other Party or its Affiliates pursuant to this Agreement without prior review and prior written consent of the other Party, where required, as reasonably determined by the disclosing Party’s legal counsel, by applicable law; provided that if a Party is required by law to make any such disclosure, to the extent it may legally do so, it will give reasonable advance notice to the other Party of such disclosure and will use its reasonable efforts to secure confidential treatment of such information prior to its disclosure (whether through protective orders or otherwise).

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

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