Statistical Testing Procedures Sample Clauses

Statistical Testing Procedures. Parity metric measurements that meet the sample size criteria in Section B will be evaluated according to the statistical test procedures defined below. These procedures test the null hypothesis that FairPoint NNE’s wholesale performance is at parity (at least equal to or better than FairPoint NNE’s retail performance) against the alternative hypothesis of no parity (that FairPoint NNE’s wholesale performance is worse than FairPoint NNE’s retail performance.) Exception: For parity metrics for which the small sample rules do not apply (as identified in Appendix4), if the sample size is insufficient for statistical testing but there is activity in retail (“ILEC activity”), performance will be evaluated based on a straight (not involving statistical procedures) comparison to retail performance to determine met or miss. In addition, for parity metrics identified as having small sample rule “3 months Roll Up” in Appendix4, the following procedures apply:  for each of the metrics with parity standards identified as having small sample rule “3 months Roll Up,” FairPoint will combine and report the numerator values and the denominator values as the sum of the three states for the ILEC and CLEC, respectively.  If, after combining the values from the three states, there is insufficient sample size for statistical testing (ILEC or CLEC) but there is ILEC and CLEC activity, CLEC performance will be determined based on a straight comparison to ILEC performance to determine whether CLEC performance is a met or miss.  If there is CLEC activity but no ILEC activity after combining the values from the three states, FairPoint will roll up the results for three months (i.e., 3 states across 3 months – the current month and the two previous months) and then do a straight comparison to ILEC performance to determine CLEC met or miss performance.  If there is still no ILEC activity after rolling up results over the three states and three months, CLEC results will be reported as “SS”.
AutoNDA by SimpleDocs

Related to Statistical Testing Procedures

  • Testing Procedures Testing will be conducted by an outside certified Agency in such a way to ensure maximum accuracy and reliability by using the techniques, chain of custody procedures, equipment and laboratory facilities which have been approved by the U.S. Department of Health and Human Services. All employees notified of a positive controlled substance or alcohol test result may request an independent test of their split sample at the employee’s expense. If the test result is negative the Employer will reimburse the employee for the cost of the split sample test.

  • Reporting Procedures Enter in the XXX Entity Management area the information that XXX requires about each proceeding described in paragraph 2 of this award term and condition. You do not need to submit the information a second time under assistance awards that you received if you already provided the information through XXX because you were required to do so under Federal procurement contracts that you were awarded.

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.‌ b. A description or identification of the statistical sampling software package used by the IRO.‌

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

  • Evaluation Procedures The following procedures for employee evaluation shall be utilized for the term of this Agreement: 1. Orientation materials related to evaluation procedures will be provided to all employees by the 10th school day. 2. Employees shall submit to their evaluator a complete listing of proposed objectives, and measurement activities related thereto, to be considered in the annual evaluation by the 25th school day. 3. The evaluator shall have completed by 30th school day annual objective setting conference with employee. 4. The evaluator shall by the 40th school day determine and shall provide the employee with a complete listing of actual objectives from those proposed by the evaluator and employee, and measurement activities from those proposed by the evaluator and employee, and measurement activities related thereto, that will be incorporated in the annual evaluation that the evaluator will prepare for the employee. The objectives and related measurement activities referred to herein shall be in accordance with the employee job description prescribed by the District. The District will make every attempt to have the number of objectives required to be uniform from site to site. 5. Within a reasonable time after the request, the evaluator shall be provided with a written progress report from the employee containing the latter's perception of the progress being made toward the achievement of the objectives prescribed in Item 3, above. During the course of the evaluation period, circumstances may change which may result in the modification of the original standards and objectives. These changes may be initiated by the supervisor or the employee. Agreement of both parties is required. 6. The evaluator, by the 145th school day, shall have conducted classroom observations in order to gather data on employee performance as the evaluator believes to be related to: A. The actual objectives and measurement activities described in Item 3, above; B. Other criteria for employee evaluation and appraisal that are established by the District Xxxxx Act Guidelines. At the discretion of the evaluator, tenured teachers may receive only one (1) formal instructional observation per year. Probationary teachers will receive two (2) formal instructional observations per year. Prior to conducting formal instructional observations regarding the teacher's duties related to the instructional objectives herein described, the teacher shall be notified of the observation prior to the beginning of the teacher's actual instructional day. Upon the request of the evaluatee or when, in the evaluator's judgment, additional instructional classroom observations are necessary, such observations may be conducted. Within a reasonable time, an employee shall be provided with a written statement regarding instructional observations that have been conducted. Such written statements shall contain a summary of the instructional activities observed, and any suggestions being made by the observer for possible improvement by the employee to include, but not be limited to, the following: 1) Specific directives for improvement 2) Assistance to implement such directives as (a) Provisions of additional resources; (b) Mandatory training programs designed to improve performance to be paid by the District. A final and written report of the achievement of objectives, and measurement information related thereto shall be submitted by the employee to the evaluator by the 140th school day. 7. The evaluator shall prepare a written District evaluation form of employee performance and transmit the evaluation to the employee. The employee may submit a written reaction or response to the evaluation and such response shall be attached to the evaluation and placed in the employee's permanent personnel file which shall be maintained in the District Office. Permanent employees shall be evaluated at least once every other year, and in no event later than 30 days before the last school day scheduled on the school calendar of the current school year. Probationary employees shall be evaluated at least once each year and in no event later than the 150th school day. 8. Employees who meet each of the following conditions shall be evaluated up to every five

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Standard Operating Procedures Standard Operating Procedures shall not contravene the Canada Labour Code, the Canadian Human Rights Code, or the Collective Agreement, and an allegation of such contravention is subject to the grievance procedure.

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

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

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