Third and Additional Positive Test Results Sample Clauses

Third and Additional Positive Test Results. The provisions below apply to an Employee, who tests positive three or more times pursuant to such random testing, sporadic testing or any other testing under this policy:
AutoNDA by SimpleDocs

Related to Third and Additional Positive Test Results

  • Positive Test Results In the event an employee tests positive for drug use, the employee will be provided, in writing, notice of their right to explain the test results. The employee may indicate any relevant circumstance, including over the counter or prescription medication taken within the last thirty (30) days, or any other information relevant to the reliability of, or explanation for, a positive test result.

  • Test Results The employer, upon request from an employee or former employee, will provide the confidential written report issued pursuant to 4.9 of the Canadian Model in respect to that employee or former employee.

  • Previously Reviewed Receivable; Duplicative Tests If any Review Receivable was included in a prior Review, the Asset Representations Reviewer will not conduct additional Tests on such Review Receivable, but will include the previously reported Test results in the Review Report for the current Review. If the same Test is required for more than one representation and warranty, the Asset Representations Reviewer will only perform the Test once for each Review Receivable, but will report the results of the Test for each applicable representation and warranty on the Review Report.

  • TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.

  • Extended Reporting Period If any required insurance coverage is on a claims-made basis (rather than occurrence), Contractor shall maintain such coverage for a period of no less than three (3) years following expiration or termination of the Contract.

  • Root Cause Analysis Upon Vendor's failure to provide the Services in accordance with the applicable Service Levels (for any reason other than a Force Majeure Event) Vendor will promptly (a) perform a root-cause analysis to identify the cause of such failure, (b) provide Prudential with a report detailing the cause of, and procedure for correcting, such failure, (c) obtain Prudential's written approval of the proposed procedure for correcting such failure, (d) correct such failure in accordance with the approved procedure, (e) provide weekly (or more frequent, if appropriate) reports on the status of the correction efforts, and (f) provide Prudential with assurances satisfactory to Prudential that such failure has been corrected and will not recur.

  • Evaluation Cycle Goal Setting and Development of the Educator Plan A) Every Educator has an Educator Plan that includes, but is not limited to, one goal related to the improvement of practice; one goal for the improvement of student learning. The Plan also outlines actions the Educator must take to attain the goals established in the Plan and benchmarks to assess progress. Goals may be developed by individual Educators, by the Evaluator, or by teams, departments, or groups of Educators who have the similar roles and/or responsibilities. See Sections 15-19 for more on Educator Plans. B) To determine the goals to be included in the Educator Plan, the Evaluator reviews the goals the Educator has proposed in the Self-Assessment, using evidence of Educator performance and impact on student learning, growth and achievement based on the Educator’s self-assessment and other sources that Evaluator shares with the Educator. The process for determining the Educator’s impact on student learning, growth and achievement will be determined after ESE issues guidance on this matter. See #22, below. C) Educator Plan Development Meetings shall be conducted as follows: i) Educators in the same school may meet with the Evaluator in teams and/or individually at the end of the previous evaluation cycle or by October 15th of the next academic year to develop their Educator Plan. Educators shall not be expected to meet during the summer hiatus. ii) For those Educators new to the school, the meeting with the Evaluator to establish the Educator Plan must occur by October 15th or within six weeks of the start of their assignment in that school iii) The Evaluator shall meet individually with Educators with PTS and ratings of needs improvement or unsatisfactory to develop professional practice goal(s) that must address specific standards and indicators identified for improvement. In addition, the goals may address shared grade level or subject matter goals. D) The Evaluator completes the Educator Plan by November 1st. The Educator shall sign the Educator Plan within 5 school days of its receipt and may include a written response. The Educator’s signature indicates that the Educator received the plan in a timely fashion. The signature does not indicate agreement or disagreement with its contents. The Evaluator retains final authority over the content of the Educator’s Plan.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Evaluation Period Until 5:00 p.m. Eastern time on August 16, 2002 (the "Evaluation Period"), Purchaser and its authorized agents and representatives (for purposes of this Article V, the "Licensee Parties") shall have the right, subject to the right of any Tenants, to enter upon the Real Property at all reasonable times during normal business hours to perform an inspection of the Real Property, the Improvements and the Personal Property. Purchaser will provide to Seller notice (for purposes of this Section 5.1(a), an "Entry Notice") of the intention of Purchaser or the other Licensee Parties to enter the Real Property at least 24 hours prior to such intended entry and specify the intended purpose therefor and the inspections and examinations contemplated to be made and with whom any Licensee Party will communicate. At Seller's option, Seller may be present for any such entry and inspection. Purchaser shall not communicate with or contact any of the Tenants or any of the Authorities without the prior written consent of Seller, which consent shall not be unreasonably withheld or delayed. If Purchaser shall elect to communicate with any of the Authorities and Seller consents thereto, Purchaser shall give Seller prior notice thereof, and Seller and Seller's representatives shall have the right, but not the obligation, to attend, and participate in, all such meetings. Notwithstanding anything to the contrary contained herein, no so-called Phase II environmental physical testing or sampling shall be conducted during any such entry by Purchaser or any Licensee Party upon the Real Property without Seller's specific prior written consent, which consent shall not be unreasonably withheld or unduly delayed. TIME IS OF THE ESSENCE with respect to the provisions of this Section 5.1.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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