Accommodation of Requesting Airlines on Preferential Use Gates Sample Clauses

Accommodation of Requesting Airlines on Preferential Use Gates. If a Passenger Carrier, including any Passenger Carrier seeking to expand its service or a Passenger Carrier seeking entry into the Airport, requests from City the use of a Gate to accommodate its expanded or new service, City and Airline shall comply with the following procedures to accommodate the Requesting Airline on Preferential Use Gates:‌ (1) City shall first determine whether the Requesting Airline can be accommodated on Common Use Gates, including Common Use Gates with Priority Use Rights. (2) If City is unable to accommodate the Requesting Airline on a Common Use Gate, including a Common Use Gate with Priority Use Rights, City shall serve written notice to all Signatory Airlines (a) describing the Requesting Airline’s request and City’s efforts to accommodate the Requesting Airline; (b) specifying‌ the Period(s) of Use that City seeks to accommodate through accommodation on Preferential Use Gates; and (c) requesting voluntary accommodation by the Signatory Airlines. (3) The Signatory Airlines shall have thirty (30) days from the delivery of the notice under Section 5.03.D(2) above to notify City that the Requesting Airline’s flights will be accommodated. Such notice shall be provided in writing by the Accommodating Airline and shall specify the terms upon which the Requesting Airline shall be accommodated.‌ (4) If City does not receive a response from a Signatory Airline under Section 5.03.D(3) above, City shall have the right, in accordance with the rules and priorities set forth in Sections 5.03.E and 5.03.F below, to specify one or more Designated Gates, including rights of ingress and egress, the right to use the associated aircraft parking positions and the right to use associated passenger loading bridges and other appurtenant equipment which are reasonably necessary for the effective use of the Gate. In selecting a Gate, City shall first consult with the Accommodating Airline and use reasonable efforts to consider the preference of the Accommodating Airline with respect to which of its Preferential Use Gates is to be selected. City shall select a Gate that is configured such that the Requesting Airline’s aircraft could operate on such Gate. In addition, the Gate selected by City shall be adjacent to either a Domestic Common Use Gate or the Preferential Use Gate of a Signatory Airline other than the Accommodating Airline, if the Accommodating Airline leases such a Gate. City shall provide sixty (60) days’ notice to the Accommodating Airline...
AutoNDA by SimpleDocs

Related to Accommodation of Requesting Airlines on Preferential Use Gates

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.

  • Application of this Revenue Sharing Agreement to Notes The terms of this Revenue Sharing Agreement shall apply to each Note as if the terms of this Revenue Sharing Agreement were fully set forth in each Note.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Subloop that may diminish the capability of the Loop or Subloop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the BellSouth’s TR 73600 Unbundled Local Loop Technical Specification. 2.5.2 BellSouth will remove load coils only on copper Loops and Subloops that are less than eighteen thousand (18,000) feet in length. 2.5.3 For any copper loop being ordered by NewPhone which has over six thousand (6,000) feet of combined bridged tap will be modified, upon request from NewPhone, so that the loop will have a maximum of six thousand (6,000) feet of bridged tap. This modification will be performed at no additional charge to NewPhone. Loop conditioning orders that require the removal of bridged tap that serves no network design purpose on a copper Loop that will result in a combined total of bridged tap between two thousand five hundred (2,500) and six thousand (6,000) feet will be performed at the rates set forth in Exhibit A. 2.5.4 NewPhone may request removal of any unnecessary and non-excessive bridged tap (bridged tap between zero (0) and two thousand five hundred (2,500) feet which serves no network design purpose), at rates pursuant to BellSouth’s SC Process as mutually agreed to by the Parties. 2.5.5 Rates for ULM are as set forth in Exhibit A. 2.5.6 BellSouth will not modify a Loop in such a way that it no longer meets the technical parameters of the original Loop type (e.g., voice grade, ADSL, etc.) being ordered. 2.5.7 If NewPhone requests ULM on a reserved facility for a new Loop order, BellSouth may perform a pair change and provision a different Loop facility in lieu of the reserved facility with ULM if feasible. The Loop provisioned will meet or exceed specifications of the requested Loop facility as modified. NewPhone will not be charged for ULM if a different Loop is provisioned. For Loops that require a DLR or its equivalent, BellSouth will provide LMU detail of the Loop provisioned. 2.5.8 NewPhone shall request Loop make up information pursuant to this Attachment prior to submitting a service inquiry and/or a LSR for the Loop type that NewPhone desires BellSouth to condition. 2.5.9 When requesting ULM for a Loop that BellSouth has previously provisioned for NewPhone, NewPhone will submit a SI to BellSouth. If a spare Loop facility that meets the Loop modification specifications requested by NewPhone is available at the location for which the ULM was requested, NewPhone will have the option to change the Loop facility to the qualifying spare facility rather than to provide ULM. In the event that BellSouth changes the Loop facility in lieu of providing ULM, NewPhone will not be charged for ULM but will only be charged the service order charges for submitting an order.

  • Default Not Exceeding 10% of Firm Securities or Option Securities If any Underwriter or Underwriters shall default in its or their obligations to purchase the Firm Securities or the Option Securities, if the Over-allotment Option is exercised hereunder, and if the number of the Firm Securities or Option Securities with respect to which such default relates does not exceed in the aggregate 10% of the number of Firm Securities or Option Securities that all Underwriters have agreed to purchase hereunder, then such Firm Securities or Option Securities to which the default relates shall be purchased by the non-defaulting Underwriters in proportion to their respective commitments hereunder.

  • Right to Refuse to Cross Picket Lines (a) All employees covered by this Agreement shall have the right to refuse to cross a picket line arising out of a dispute as defined in the appropriate legislation. Any employees failing to report for duty shall be considered to be absent without pay. (b) Failure to cross a picket line encountered in carrying out the Employer's business shall not be considered a violation of this Agreement nor shall it be grounds for disciplinary action.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

  • Increasing Seat Belt Use in the United States E.O. 13043, amended by E.O. 13652, requires Recipients to encourage employees and contractors to enforce on-the-job seat belt policies and programs when operating company- owned, rented or personally-owned vehicle.

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