Selection Process for Full-Time Dispatcher Sample Clauses

Selection Process for Full-Time Dispatcher. ‌ (a) Where there are no Dispatch qualified or insufficient Dispatch qualified applicants for a Dispatcher posting, the Employer shall give equal consideration to knowledge and skill to a total of nintety per cent (90%). Seniority shall be weighted based on one per cent (1%) for each completed year of full-time service to a maximum value of ten per cent (10%). The successful candidate(s) shall be the employee(s) with the highest total score. (b) Employees may not bid out of their initial appointment to a Dispatch position for at least three (3) years following such appointment. (c) Employees who are unsuccessful in Dispatch training may not reapply for three (3) years.
Sample 1Sample 2
AutoNDA by SimpleDocs
Selection Process for Full-Time Dispatcher. (a) Where there are no Dispatch qualified or insufficient Dispatch qualified applicants for a Dispatcher posting, the Employer shall give equal consideration to knowledge and skill to a total of 90%. Seniority shall be weighted based on 1% for each completed (b) Employees may not bid out of their initial appointment to a Dispatch position for at least three years following such appointment. (c) Employees who are unsuccessful in Dispatch training may not reapply for three years.
Sample 1
Selection Process for Full-Time Dispatcher. ‌ (a) Where there are no Dispatch qualified or insufficient Dispatch qualified applicants for a Dispatcher posting, the Employer shall give equal consideration to knowledge and skill to a total of 90%. Seniority shall be weighted based on 1% for each completed year of full-time service to a maximum value of 10%. The successful candidate(s) shall be the employee(s) with the highest total score. (b) Employees may not bid out of their initial appointment to a Dispatch position for at least three years following such appointment. (c) Employees who are unsuccessful in Dispatch training may not reapply for three years.
Sample 1

Related to Selection Process for Full-Time Dispatcher

  • Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;

  • Sick Leave Verification Process a. The new school district shall provide the employee with the necessary verification form at the time the employee receives confirmation of employment in the school district. b. An employee must initiate the sick leave verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of commencing employment with the new school district. c. The previous school district(s) shall make every reasonable effort to retrieve and verify the sick leave credits which the employee seeks to port.

  • CONTRACT INVOICING a. Invoicing. Contractor and the dealers/distributors/resellers designated by the Contractor, if any, shall provide complete and accurate billing invoices to each Authorized User in order to receive payment. Billing invoices submitted to an Authorized User must contain all information required by the Contract and the State Comptroller or other appropriate fiscal officer. Submission of an invoice and payment thereof shall not preclude the Commissioner from requesting reimbursement or demanding a price adjustment in any case where the Product delivered is found to deviate from the terms and conditions of the Contract or where the billing was inaccurate. b. Payment of Contract Purchases made by an Authorized User when the State Comptroller is responsible for issuing such payment. The Authorized User and Contractor agree that payments for invoices submitted by the Contractor shall only be rendered electronically unless payment by paper check is expressly authorized by the Commissioner, in the Commissioner’s sole discretion, due to extenuating circumstances. Such electronic payments shall be made in accordance with ordinary State procedures and practices. The Contractor shall comply with the State Comptroller’s procedures to authorize electronic payments. Authorization forms are available at the State Comptroller website at xxx.xxx.xxxxx.xx.xx, by e-mail at xxxxxx@xxx.xxxxx.xx.xx, or by telephone at 000-000-0000. Contractor acknowledges that it will not receive payment on any invoices submitted under this Contract that are payable by the State Comptroller if it does not comply with the State Comptroller’s electronic payment procedures, except where the Commissioner has expressly authorized payment by paper check as set forth above. c. Payment of Contract Purchases made by an Authorized User when the State Comptroller is not responsible for issuing such payment The Authorized User and Contractor agree that payments for such Contract purchases shall be billed directly by Contractor on invoices/vouchers, together with complete and accurate supporting documentation as required by the Authorized User. Such payments shall be as mandated by the appropriate governing law from the receipt of a proper invoice. Such Authorized User and Contractor are strongly encouraged to establish electronic payments.

  • Seniority Verification Process i. The new school district shall provide the employee with the necessary verification form at the time the employee achieves continuing contract status. ii. The employee must initiate the seniority verification process and forward the necessary verification forms to the previous school district(s) within ninety (90) days of receiving a continuing appointment in the new school district. iii. The previous school district(s) shall make every reasonable effort to retrieve and verify the seniority credits which the employee seeks to port.

  • CONTRACTOR CUSTOMER SERVICE REPRESENTATIVE Contractor shall designate a customer service representative (and inform Enterprise Services of the same) who shall be responsible for addressing Purchaser issues pertaining to this Contract.

  • Selection Procedure 10.2.4.1 Internal applicants shall be defined as all applicants with seniority in accordance with Article 12.5. 10.2.4.2 In filling a posted vacancy, first consideration shall be given to internal applicants who meet the stated qualifications. All Faculty members who meet the stated qualifications for the posted vacancy shall be interviewed by the Selection Committee. Past service and evaluations shall be considered by the Committee. The best qualified candidate shall be recommended for appointment to the position. 10.2.4.3 Where the qualifications of two or more of the applicants are relatively equal, the applicant with the greatest seniority shall be recommended for appointment to the position. 10.2.4.4 In establishing the qualifications, and in evaluating the qualifications and past performance of the applicants, the committee shall act in good faith, in a fair and reasonable manner, and shall not act in an arbitrary or discriminatory fashion. 10.2.4.5 Following the interviews, the committee will submit its recommendations containing a list of qualified candidates in order of preference, through the appropriate Xxxx to the President or delegate. 10.2.4.6 New faculty members shall be appointed only when there are no qualified internal applicants. 10.2.4.7 If there are no qualified internal applicants, the selection committee may consider external applications, in accordance with the procedure outlined above. 10.2.4.8 Internal applicants will be advised as soon as possible of the selection committee's decision that the committee will be considering external applications in accordance with Article 10.2.4.7.

  • CONTRACTOR INVOICE Contractor shall submit properly itemized invoices to Purchaser’s designated invoicing contact for Services delivered under this Contract. Such invoices shall itemize the following: (a) Contract No. 14822; (b) Contractor name, address, telephone number, and email address for billing issues (i.e., Contractor Customer Service Representative); (c) Contractor’s Federal Tax Identification Number; (d) Date(s) of delivery; (e) Applicable Services; (f) Invoice amount; and (g) Payment terms, including any available prompt payment discounts. Contractor’s invoices for payment shall reflect accurate Contract prices. Invoices will not be processed for payment until receipt of a complete invoice as specified herein.

  • Billing Services 6 SECTION 3.01.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • Billing Unless otherwise provided in the Grant Agreement, Grantee shall bill the System Agency in accordance with the Grant Agreement. Unless otherwise specified in the Grant Agreement, Grantee shall submit requests for reimbursement or payment monthly by the last business day of the month following the month in which expenses were incurred or services provided. Grantee shall maintain all documentation that substantiates invoices and make the documentation available to the System Agency upon request.

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