Wing Plows. Each employee will receive training by a certified instructor in the operation of a truck with a wing plow.
Wing Plows Sample Clauses
Related to Wing Plows
Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.
Variable Registry-‐Level Fee (a) If the ICANN accredited registrars (accounting, in the aggregate, for payment of two-‐thirds of all registrar-‐level fees (or such portion of ICANN accredited registrars necessary to approve variable accreditation fees under the then-‐current registrar accreditation agreement), do not approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for any ICANN fiscal year, upon delivery of notice from ICANN, Registry Operator shall pay to ICANN a variable registry-‐level fee, which shall be paid on a fiscal quarter basis, and shall accrue as of the beginning of the first fiscal quarter of such ICANN fiscal year (the “Variable Registry-‐Level Fee”). The fee will be calculated and invoiced by ICANN on a quarterly basis, and shall be paid by Registry Operator within sixty (60) calendar days with respect to the first quarter of such ICANN fiscal year and within twenty (20) calendar days with respect to each remaining quarter of such ICANN fiscal year, of receipt of the invoiced amount by ICANN. The Registry Operator may invoice and collect the Variable Registry-‐Level Fees from the registrars that are party to a registry-‐ registrar agreement with Registry Operator (which agreement may specifically provide for the reimbursement of Variable Registry-‐Level Fees paid by Registry Operator pursuant to this Section 6.3); provided, that the fees shall be invoiced to all ICANN accredited registrars if invoiced to any. The Variable Registry-‐Level Fee, if collectible by ICANN, shall be an obligation of Registry Operator and shall be due and payable as provided in this Section 6.3 irrespective of Registry Operator’s ability to seek and obtain reimbursement of such fee from registrars. In the event ICANN later collects variable accreditation fees for which Registry Operator has paid ICANN a Variable Registry-‐Level Fee, ICANN shall reimburse the Registry Operator an appropriate amount of the Variable Registry-‐Level Fee, as reasonably determined by ICANN. If the ICANN accredited registrars (as a group) do approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for a fiscal year, ICANN shall not be entitled to a Variable-‐Level Fee hereunder for such fiscal year, irrespective of whether the ICANN accredited registrars comply with their payment obligations to ICANN during such fiscal year. (b) The amount of the Variable Registry-‐Level Fee will be specified for each registrar, and may include both a per-‐registrar component and a transactional component. The per-‐registrar component of the Variable Registry-‐Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year. The transactional component of the Variable Registry-‐Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year but shall not exceed US$0.25 per domain name registration (including renewals associated with transfers from one ICANN accredited registrar to another) per year.
Longer/Shorter Length of Coverage If none of the above rules determine the order of benefits, the benefits of the plan that covered a member or subscriber longer are determined before those of the plan that covered that person for the shorter term.
Church Conference Vote At least two-thirds (2/3) of the professing members present at a church conference of the Local Church must vote to disaffiliate from The United Methodist Church “for reasons of conscience regarding a change in the requirements and provisions of the Book of Discipline related to the practice of homosexuality or the ordination or marriage of self-avowed practicing homosexuals as resolved and adopted by the 2019 General Conference, or the actions or inactions of its annual conference related to these issues which follow.” Local Church shall provide documentation, to the satisfaction of Annual Conference, which evidences the result of the disaffiliation vote taken at the church conference. Such documentation must be certified by an authorized officer of Local Church and shall be included as an Exhibit A to this Disaffiliation Agreement.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Outside Activities of Limited Partners Subject to any agreements entered into by a Limited Partner or its Affiliates with the General Partner, Partnership or a Subsidiary, any Limited Partner and any officer, director, employee, agent, trustee, Affiliate or stockholder of any Limited Partner shall be entitled to and may have business interests and engage in business activities in addition to those relating to the Partnership, including business interests and activities in direct competition with the Partnership or that are enhanced by the activities of the Partnership. Neither the Partnership nor any Partners shall have any rights by virtue of this Agreement in any business ventures of any Limited Partner or Assignee. Subject to such agreements, none of the Limited Partners nor any other Person shall have any rights by virtue of this Agreement or the partnership relationship established hereby in any business ventures of any other Person, other than the Limited Partners benefiting from the business conducted by the General Partner, and such Person shall have no obligation pursuant to this Agreement to offer any interest in any such business ventures to the Partnership, any Limited Partner or any such other Person, even if such opportunity is of a character which, if presented to the Partnership, any Limited Partner or such other Person, could be taken by such Person.
Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement.
Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)
Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
