Procedures for regular testing, assessing and evaluating Sample Clauses

Procedures for regular testing, assessing and evaluating. Data protection management, including regular employee training courses; • Incident-Response-Management;
AutoNDA by SimpleDocs

Related to Procedures for regular testing, assessing and evaluating

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • PROCEDURES AND/OR CRITERIA FOR COURSE ARTICULATION a. Complete the ROP Careers with Children course at Freedom High School with a grade of “B” or better.

  • PROCEDURES FOR EVALUATION A. The evaluations of school year employees covered by this agreement shall be completed no later than May 30 of each school year for 9-month employees and by June 30 for 10/12-month employees. The evaluation shall be reviewed with the employee, with a copy given to the employee at the conclusion of the review. An employee may present written comments, which shall be attached to the written evaluation document. The evaluator and employee shall sign the evaluation document. The employee’s signature does not constitute approval or disapproval, but only that the evaluation has been reviewed with the employee.

  • Billing and Payment Procedures and Final Accounting 6.1.1 The Connecting Transmission Owner shall xxxx the Interconnection Customer for the design, engineering, construction, and procurement costs of Interconnection Facilities and Upgrades contemplated by this Agreement on a monthly basis, or as otherwise agreed by those Parties. The Interconnection Customer shall pay all invoice amounts within 30 calendar days after receipt of the invoice.

  • Important Information About Procedures for Opening a New Account To help the government fight the funding of terrorism and money laundering activities, Federal law requires all financial organizations to obtain, verify, and record information that identifies each person who opens an account. What this means for you: When you open an account, you are required to provide your name, residential address, date of birth, and identification number. We may require other information that will allow us to identify you.

  • Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.

  • Monitoring and Evaluation a. The AGENCY shall expeditiously provide to the COUNTY upon request, all data needed for the purpose of monitoring, evaluating and/or auditing the program(s). This data shall include, but not be limited to, clients served, services provided, outcomes achieved, information on materials and services delivered, and any other data required, in the sole discretion of the COUNTY, that may be required to adequately monitor and evaluate the services provided under this Contract. Monitoring shall be performed in accordance with COUNTY’S established Noncompliance Standards, a copy of which is attached hereto and incorporated by reference as Attachment “C”.

  • Procedures for Providing LNP ( “Long-term Number Portability”). The Parties will follow the LNP provisioning process recommended by the North American Numbering Council (NANC) and adopted by the FCC. In addition, the Parties agree to follow the LNP ordering procedures established at the OBF. The Parties shall provide LNP on a reciprocal basis.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 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, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • REPORTING AND EVALUATION The Provider agrees to comply with 7 AAC 81.120, Confidentiality and 7 AAC 81.150, Reports, and other applicable state or federal law regarding the submission of information, including the provisions of Section VI of this Agreement. The Provider agrees to submit any reporting information required under this Agreement and to make available information deemed necessary by DHSS to evaluate the efficacy of service delivery or compliance with applicable state or federal statutes or regulations. The Provider agrees to provide state officials and their representatives access to facilities, systems, books and records, for the purpose of monitoring compliance with this Agreement and evaluating services provided under this Agreement. On-site Quality Assurance Reviews may be conducted by DHSS staff to ensure compliance with service protocols. The Provider will ensure that DHSS staff has access to program files for the purposes of follow-up, quality assurance monitoring and fiscal administration of the program.

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