San Francisco International Airport – Airfield Maintenance Only Sample Clauses

San Francisco International Airport – Airfield Maintenance Only. Newly hired 9240s may be assigned to any shift.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
San Francisco International Airport – Airfield Maintenance Only. Newly hired 9240's assigned to day shift until the next shift rotation.
Sample 1Sample 2Sample 3See All (5)

Related to San Francisco International Airport – Airfield Maintenance Only

  • Xxxxx, Haldimand, Norfolk An employee shall be granted five working days bereavement leave with pay upon the death of the employee’s spouse, child, stepchild, parent, stepparent, legal guardian, grandchild or step-grandchild.

  • INTERNATIONAL TRANSPORT 1. Profits of an enterprise of a Contracting State from the operation of ships, aircraft or road-transport vehicles in international traffic shall be taxable only in that State. 2. The provisions of paragraph 1 shall also apply to profits from participation in a pool, a joint business or an international operating agency.

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

  • meminta nasihat daripada Pihak Xxxxxx dalam semua perkara berkenaan dengan jualan lelongan, termasuk Syarat-syarat Jualan (iii) membuat carian Hakmilik Xxxxx xxxxxx rasmi di Pejabat Tanah xxx/atau xxxx-xxxx Pihak-pihak Berkuasa yang berkenaan xxx (iv) membuat pertanyaan dengan Pihak Berkuasa yang berkenaan samada jualan ini terbuka kepada semua bangsa atau kaum Bumiputra Warganegara Malaysia sahaja atau melayu sahaja xxx juga mengenai persetujuan untuk jualan ini sebelum jualan lelong.Penawar yang berjaya ("Pembeli") dikehendaki dengan segera memohon xxx mendapatkan kebenaran pindahmilik (jika ada) daripada Pihak Pemaju xxx/atau Pihak Tuanpunya xxx/atau Pihak Berkuasa Negeri atau badan-badan berkenaan (v) memeriksa xxx memastikan samada jualan ini dikenakan cukai. HAKMILIK : Hakmilik strata bagi hartanah ini masih belum dikeluarkan HAKMILIK INDUK / NO. LOT : Pajakan Negeri 35263, Lot No.29096 MUKIM/DAERAH/NEGERI : Setapak / Kuala Lumpur / Wilayah Persekutuan Kuala Lumpur PEGANGAN : Pajakan selama 82-tahun berakhir pada 08/08/2085 KELUASAN LANTAI : 81.104 meter persegi ( 873 kaki persegi ) PEMAJU/PENJUAL : Mega Planner Jaya Sdn Bhd (326287-W)(Dalam Likuidasi) TUANPUNYA : Datuk Bandar Kuala Lumpur PEMBELI : Xxxxxxxx Bin Xxxxx @ Xxxx BEBANAN : Diserahhak kepada RHB Bank Berhad [196501000373 (6171-M)] Hartanah tersebut terletak di tingkat 9 pada bangunan apartment 14-tingkat terletak di Melati Impian Apartment, Setapak Fasa 1, Kuala Lumpur. Hartanah tersebut adalah sebuah unit apartment 3 xxxxx dikenali sebaga Xxxxx Pemaju No. 9, Tingkat No.9, Pembangunan dikenali sebagai Melati Impian Apartment Setapak Fasa 1, Kuala Lumpur xxx mempunyai alamat surat-xxxxxxxx xx Xxxx Xx. 0-0, Xxxxxx Impian Apartment, Xxxxx 0/00X, Xxxxx Xxxxxx, 00000 Xxxxx Xxxxxx, Xxxxxxx Xxxxxxxxxxx Xxxxx Xxxxxx. Harta ini dijual “keadaan seperti mana sediada” dengan harga rizab sebanyak RM 300,000.00 (RINGGIT MALAYSIA: TIGA RATUS RIBU SAHAJA) xxx tertakluk kepada syarat-syarat Jualan xxx melalui penyerahan hakkan dari Pemegang Serahak, tertakluk kepada kelulusan di perolehi oleh pihak Pembeli daripada pihak berkuasa, jika ada, termasuk semua terma, syarat xxx perjanjian yang dikenakan xxx mungkin dikenakan oleh Pihak Berkuasa yang berkenaan. Pembeli bertanggungjawab sepenuhnya untuk memperolehi xxx mematuhi syarat-syarat berkenaan daripada Pihak Berkuasa yang berkenaan, jika ada xxx semua xxx xxx perbelanjaan ditanggung xxx dibayar oleh Xxxxx Xxxxxxx.Pembeli atas talian (online) juga tertakluk kepada terma-terma xxx syarat-syarat terkandung dalam xxx.xxxxxxxxxxxxxxxx.xxx Pembeli yang berminat adalah dikehendaki mendeposit kepada Pelelong 10% daripada harga rizab dalam bentuk Bank Draf atau Cashier’s Order di atas nama RHB Bank Berhad sebelum lelongan awam xxx xxxx xxxx xxxxxx hendaklah dibayar dalam tempoh sembilan puluh (90) hari dari tarikh lelongan kepada RHB Bank Berhad melalui Bank Draf / XXXXXX. Butir-butir pembayaran melalui XXXXXX, xxxx berhubung dengan Tetuan Zahrin Emrad & Sujaihah. Untuk maklumat lanjut, xxxx berhubung dengan TETUAN ZAHRIN EMRAD & SUJIAHAH, yang beralamat di Suite 10.3, 10th Floor, Xxx Xxxx Building, Xx.00, Xxxxx Xxxx Xxxxxx, 00000 Xxxxx Xxxxxx. Tel: 00-0000 0000 / Fax: 00-0000 0000. [ Ruj: ZES/ZHR/RHB-FC/16250-17/0614-pae ], peguamcara bagi pihak pemegang xxxxx xxx atau pelelong yang tersebut dibawah.

  • 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.

  • FIPPA The HSP acknowledges that the LHIN is bound by FIPPA and that any information provided to the LHIN in connection with this Agreement may be subject to disclosure in accordance with FIPPA.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

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

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