Technical Meetings Sample Clauses
Technical Meetings. At least once a month during the Term, at a fixed date to be agreed by the Parties (e.g. the first Monday of the month), and as often as the Parties deem necessary (provided an advance written (or e-mail) notice of no less than five (5) Business Days is served by one of the Parties), the Parties’ respective employees or Representatives (which should include the SPOC and the Quality Persons of both Parties) shall meet (in person or by phone) to follow-up with scientific and/or technical issues relating to the Services (“Technical Meetings”).
Technical Meetings. (a) In addition to the initial familiarization meeting, other technical meetings may be necessary to assure that any additional technical conditions that have been communicated to the CAAI are well understood, and that any outstanding technical issues are resolved. These meetings should be held as early as possible in the certification process in order to permit timely design changes. All technical meetings will normally be arranged through the CAAI and will normally have both authorities’ representatives in attendance.
(b) Early in the program, based on the known design and information presented in the familiarization and technical meetings, the FAA will identify the areas in which further FAA activity will be required (e.g., required data, reports, tests and test witnessing, areas of concern or special emphasis). The anticipated level of activity by the FAA will be documented in writing. This written arrangement may be revised if the initial design definition is incomplete or subsequent design changes are made.
(c) As part of its involvement in any aspect of the program, the FAA may exercise the option to retain the compliance determinations.
(d) The CAAI will keep the FAA informed of the progress of its domestic type certification program on a regular basis. The CAAI should notify the FAA Project Manager as soon as possible of all additional novel or unusual design features, and all other design features that might cause or have caused the CAAI to develop a special condition or to make an equivalent level of safety finding.
Technical Meetings. The Proponent shall hold one Technical Review Meeting to discuss the progress on the Project. The date for this meeting shall be chosen in consultation with the Minister's representative and it shall be held on or before January 31, 1998.
Technical Meetings. RIATA and MANTI shall periodically meet to discus activities within the AMI, to designate Areas of Interests, to designate Prospect Areas, additional work to be conducted, AFE’s and to formulate plans and strategies of the next succeeding quarter as well as conducting technical reviews of any leads or Prospects. Either party may call such a meeting and shall provide a minimum of at least ten (10) days advance written notice, by facsimile, telegram or overnight delivery to the other party of such meeting.
Technical Meetings. (a) In addition to the initial familiarization meeting, other technical meetings may be necessary to ensure that any additional technical conditions that have been communicated to the CAA are well understood, and that any outstanding technical issues are resolved. These meetings should be held as early as possible in the certification process in order to permit timely design changes. All technical meetings will normally be arranged through the CAA and will normally have both authorities’ representatives in attendance.
(b) Early in the program, based on the known design and information presented in the familiarization and technical meetings, the FAA will identify the areas in which further FAA activity will be required (e.g. review of required data, reports, tests and test witnessing, areas of concern or special emphasis). The anticipated level of activity by the FAA will be documented in writing. This written arrangement may be revised if the initial design definition is incomplete or subsequent design changes are made.
(c) The CAA will keep the FAA informed of the progress of its type certification program on a periodic basis. The CAA should notify the FAA Project Manager as soon as possible of all additional novel or unusual design features, and all other design features that might cause or have caused the CAA to develop a special condition or to make an equivalent level of safety finding.
Technical Meetings. 3.2.8.1 In addition to the initial familiarization meeting, other technical meetings may be necessary to ensure that any additional technical conditions that have been communicated to the CAA are well understood, and that any outstanding technical issues are resolved. These meetings should be held as early as possible in the certification process in order to permit timely design changes. All technical meetings will normally be arranged through the CAA and will normally have both authorities in attendance.
3.2.8.2 Early in the program, based on the known design and information presented in the familiarization and technical meetings, the FAA will identify the areas in which further activity by the FAA will be required. The anticipated level of activity by the FAA will be documented in writing. This document may be revised if the initial design definition is incomplete or subsequent design changes are made.
3.2.8.3 The CAA will keep the FAA informed of the progress of its type certification program on a periodic basis. The CAA should notify the FAA’s Project Manager as soon as possible of all additional novel or unusual design features, and all other design features that might cause or have caused the CAA to develop a special condition or to make an equivalent level of safety finding.
Technical Meetings. As soon as practical after the execution of this Agreement, the Parties shall meet at Xxxxxxx’x offices to discuss exploration plans and budgets for the remainder of Phase I. Thereafter, at periodic intervals, as required, but no less frequently than every 30 days, Xxxxxxx shall schedule and hold periodic technical meetings (the “Periodic Meetings”) at which meetings Xxxxxxx shall inform Providence of the exploration activities it proposes to conduct as Operator under the provisions of this Agreement during Phase I. At such Periodic Meetings, there shall be a presentation of geological, geophysical, engineering, budget, accounting and land data in sufficient detail to apprise Providence of the opportunities and costs it can expect to incur under this Agreement. At subsequent Periodic Meetings, Xxxxxxx will provide an update of the information presented at previous Periodic Meetings and will provide new information developed and acquired since the prior meeting.
Technical Meetings. The CAA convenes technical meetings if it considers it necessary for issuance of a Type Acceptance Certificate (TAC).
3.7.8.1 These meetings should be held as early as possible in the certification process in order to permit timely design changes. All technical meetings will normally be arranged through the FAA and will normally have both authorities’ representatives in attendance.
3.7.8.2 The CAA may identify the areas in which further CAA activity will be required. The anticipated level of activity by the CAA will be documented in writing. This written arrangement may be revised if the initial design definition is incomplete or subsequent design changes are made.
Technical Meetings. Hawker shall notify and offer Federal the opportunity to participate with Hawker in industry technical meetings and Equipment manufacturers' engineering coordination meetings, provided the meetings relate to Federal's Equipment or the Services provided by Hawker.
Technical Meetings. In addition to the Review Meetings described in 2.4 above, the Parties shall regularly communicate and discuss by phone the geological, geophysical, accounting and land data to enable the Parties to evaluate and agree on the exploration activities to be conducted.