CHECK AIRMEN AND MAINTENANCE TEST-PILOTS Sample Clauses

CHECK AIRMEN AND MAINTENANCE TEST-PILOTS. Section 1. Check Airmen with no previous FAR 135 check airmen experience must have been on the Xxxxxxx US LLC or Xxxxxxx Alaska, Inc. pilot seniority roster for the preceding 24 months. Section 2. Check Airmen with previous FAR 135 check airmen experience must have been on the Xxxxxxx US LLC or Xxxxxxx Alaska, Inc. pilot seniority roster for the preceding 12 months. Section 3. All Check Airman and Maintenance Test-Pilot positions will be posted, but will be awarded at the discretion of the Company subject to the requirements of III. Section 1 and III. Section 2. Section 4. Check Airman, on hitch, will not be used to fill a vacant position on the line, unless warranted by business conditions or to fill a vacancy due to immediate operational requirement which may necessitate canceling training.
Sample 1
AutoNDA by SimpleDocs

Related to CHECK AIRMEN AND MAINTENANCE TEST-PILOTS

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Installation, Maintenance, Testing and Repair Unless otherwise agreed in writing by the Parties, to the extent required by Applicable Law, Interconnection provided by a Party shall be equal in quality to that provided by such Party to itself, any subsidiary, affiliates or third party. If either Party is unable to fulfill its obligations under this Section 14.2, it shall notify the other Party of its inability to do so and will negotiate alternative intervals in good faith. The Parties agree that to the extent required by Applicable Law, the standards to be used by a Party for isolating and clearing any disconnections and/or other outages or troubles shall be at parity with standards used by such Party with respect to itself, any subsidiary, affiliate or third party.

  • Planned Maintenance (a) Subject to any modification or amendment of this Agreement made pursuant to Section 4.2(c) or Section 7.3(d), Planned Maintenance occurring during the Delivery Term shall be coordinated and scheduled in accordance with this Section 9.6. Seller shall perform all Planned Maintenance (including Major Planned Maintenance) in a manner that optimizes the generation and benefits to Buyer of the Contract Energy, Storage Energy, and other Products (e.g., during off-peak periods and low-irradiance periods) and, without limiting the foregoing, either (i) outside of Daylight Hours or (ii) during the months of October and November only, during Daylight Hours; provided, however, that the foregoing restrictions shall not apply to any Planned Maintenance that Seller is required to perform pursuant to any applicable manufacturer warranty that cannot reasonably be performed by Seller subject to such restrictions. (b) Seller shall deliver to Buyer a proposed schedule for Planned Maintenance in respect of each Contract Year (“Planned Maintenance Schedule”) no later than ninety (90) Days before the start of such Contract Year. Planned Maintenance Schedules submitted by Seller shall (i) comply with the second sentence of Section 9.6(a) and (ii) include reasonably detailed descriptions of the Planned Maintenance to be performed, the Days and times in which each type of Planned Maintenance is scheduled to be performed, the estimated amount(s) of Contract Capacity and Storage Capacity that will be unavailable due to Planned Maintenance and the total number of hours that Seller expects that the Contract Capacity and Storage Capacity will be unavailable due to Planned Maintenance. The general form for the Planned Maintenance Schedule is set forth in Schedule 9.6. (The Planned Maintenance descriptions reflected in the general form set forth in Schedule 9.6 are provided for indicative purposes only, and are not necessarily representative of the detail, time periods, or certainty required for a Planned Maintenance Schedule hereunder.) (c) Buyer shall have the right to disapprove, in its reasonable discretion (provided that Buyer shall have the right to disapprove, in its sole and absolute discretion, any Planned Maintenance proposed by Seller that is inconsistent with the terms of this Agreement), any Planned Maintenance set out in any Planned Maintenance Schedule proposed by Seller for any Contract Year, except for any Planned Maintenance that (i) is scheduled to occur outside of Daylight Hours or during Daylight Hours during the months of October and November or (ii) Seller is required to perform pursuant to any applicable manufacturer warranty and that is scheduled to occur in compliance with Section 9.6(a). If Seller submits its Planned Maintenance Schedule for a Contract Year in accordance with the requirements of this Agreement and Buyer does not disapprove of any Planned Maintenance set out in such Planned Maintenance Schedule by sixty (60) days after submission, then such Planned Maintenance Schedule shall be deemed approved. If Buyer, in the exercise of its discretion as set forth above, disapproves any Planned Maintenance in such Planned Maintenance Schedule within the applicable time period specified above after its submission, Buyer shall notify Seller and the Parties shall use Commercially Reasonable Efforts to agree upon and finalize a mutually acceptable Planned Maintenance Schedule for the applicable Contract Year. Seller shall conduct Planned Maintenance during such Contract Year only in accordance with an agreed Planned Maintenance Schedule; provided, however, that Seller may (A) move Planned Maintenance included in an agreed Planned Maintenance Schedule that is not Major Planned Maintenance, so long as such move is consistent with the terms of this Agreement (including the second sentence of Section 9.6(a)) or, with respect to Major Planned Maintenance, if such Major Planned Maintenance is scheduled to occur outside of Daylight Hours or during Daylight Hours during the months of October and November and (B) schedule and perform Planned Maintenance not reflected in the Planned Maintenance Schedule so long as such Planned Maintenance is scheduled to be performed outside of Daylight Hours or during Daylight Hours during the months of October and November and Seller provides Buyer at least two (2) weeks’ prior written notice of such Planned Maintenance; provided further that Buyer shall have the right to advise Seller of periods when Buyer prefers, based on solar irradiance, supply, market and other conditions, that any Major Planned Maintenance be deferred, and Seller shall use Commercially Reasonable Efforts to comply with such request. (d) Seller shall use Commercially Reasonable Efforts to complete any Planned Maintenance and place the Facility back into full commercial operation as soon as reasonably possible. If Seller determines that any Planned Maintenance scheduled in an agreed Planned Maintenance Schedule no longer needs to be completed or will not consume the entire time scheduled therefor in the agreed Planned Maintenance Schedule, Seller shall provide (i) a Generation Forecast to Buyer reflecting the forecasted amount of Delivered Energy during each affected interval that takes into account such change and (ii) in the case of any Major Planned Maintenance, a written notice declaring the cessation and termination of the applicable Major Planned Maintenance period (in which event, the Major Planned Maintenance period shall terminate in accordance with the terms of such Generation Forecast and written notice).

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Equipment Testing and Inspection 2.1.1 The Interconnection Customer shall test and inspect its Small Generating Facility and Interconnection Facilities prior to interconnection. The Interconnection Customer shall notify the NYISO and the Connecting Transmission Owner of such activities no fewer than five Business Days (or as may be agreed to by the Parties) prior to such testing and inspection. Testing and inspection shall occur on a Business Day. The Connecting Transmission Owner may, at its own expense, send qualified personnel to the Small Generating Facility site to inspect the interconnection and observe the testing. The Interconnection Customer shall provide the NYISO and Connecting Transmission Owner a written test report when such testing and inspection is completed. The Small Generating Facility may not commence parallel operations if the NYISO, in consultation with the Connecting Transmission Owner, finds that the Small Generating Facility has not been installed as agreed upon or may not be operated in a safe and reliable manner. 2.1.2 The NYISO and Connecting Transmission Owner shall each provide the Interconnection Customer written acknowledgment that it has received the Interconnection Customer’s written test report. Such written acknowledgment shall not be deemed to be or construed as any representation, assurance, guarantee, or warranty by the NYISO or Connecting Transmission Owner of the safety, durability, suitability, or reliability of the Small Generating Facility or any associated control, protective, and safety devices owned or controlled by the Interconnection Customer or the quality of power produced by the Small Generating Facility.

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.

  • Support and Maintenance Where Licensee purchases support and/or maintenance services, Licensee’s initial support and/or maintenance term will begin upon delivery to Licensee of the Licensed Software and continue for one (1) year thereafter (or the length of the term if less than a year for any subscription/term license) unless otherwise specified in the applicable annual support and/or maintenance agreement, Product Order, or other written agreement executed between Licensor and Licensee. Where Licensee purchases support and/or maintenance for any Licensed Software, Licensee hereby agrees that it shall purchase such support and/or maintenance services for all of Licensee’s licensed units of such Licensed Software product. Support and/or maintenance services provided by Licensor will be subject to Licensor’s then current applicable standard annual support and/or maintenance agreement unless otherwise agreed by the parties in writing.

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Routine Maintenance (i) CRC shall be responsible for Routine Maintenance when necessary or desirable to maintain the Shared Assets in a safe operating condition, and to permit and facilitate (A) the performance by CRC of its obligations pursuant to this Agreement, and (B) the use of Shared Assets by the Operators in accordance with this Agreement. (ii) CSXT or NSR, directly or through their respective affiliates, may perform the work which CRC performed prior to the date of this Agreement when (A) CRC does not possess the skills needed for such work, (B) CRC lacks the necessary employees to do such work in a timely fashion, or (C) CRC does not possess the equipment needed to do such work. CRC and the party performing the work shall agree to a reasonable fee for such work prior to performance. CRC, CSXT and NSR may agree to have additional work performed either by CSXT, NSR or their affiliates.

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