Compliance Monitoring Process Sample Clauses

Compliance Monitoring Process. Defines for each measure: • The specific data or information that is required to measure performance or outcomes. • The entity that is responsible for providing the data or information for measuring performance or outcomes. • The process that will be used to evaluate data or information for the purpose of assessing performance or outcomes. • The entity that is responsible for evaluating data or information to assess performance or outcomes. • The time period in which performance or outcomes is measured, evaluated, and then reset. • Measurement data retention requirements and assignment of responsibility for data archiving. Exhibit C – Amended and Restated NERC-NPCC Regional Delegation Agreement Exhibit C Northeast Power Coordinating Council, Inc. Regional Reliability Standards Development Procedure Approved by NPCC Board of Directors September 19, 2007 NPCC REGIONAL RELIABILITY STANDARDS DEVELOPMENT PROCEDURE TABLE OF CONTENTS I. EXECUTIVE SUMMARY 2 II. REGIONAL RELIABILITY STANDARD DEVELOPMENT PROCEDURE
Sample 1
AutoNDA by SimpleDocs
Compliance Monitoring Process. Texas RE’s regional standard development procedure or other governing documents contain the following language relative to this Common Attribute: See TRE Process – Appendix B, II. Regional Reliability Standard Characteristics and Elements, b. Elements of a Regional Reliability Standard – Table 2 – Compliance Monitoring Process: Deleted: ERCOT Deleted: ¶ ¶ Defines for each measure: • The specific data or information that is required to measure performance or outcomes. • The entity that is responsible for providing the data or information for measuring performance or outcomes. • The process that will be used to evaluate data or information for the purpose of assessing performance or outcomes. • The entity that is responsible for evaluating data or information to assess performance or outcomes. • The time period in which performance or outcomes is measured, evaluated, and then reset. • Measurement data retention requirements and assignment of responsibility for data archiving. • Violation severity levels.
Sample 1
Compliance Monitoring Process. Texas Regional Entity Standards Development Process Exhibit C to the Delegation Agreement Between NERC and ERCOT October 19, 2006 Table of Contents I. Introduction 2 II. Background 2 III. Regional Reliability Standards Definition 4 IV. Roles in the Texas Regional Entity (RE) Reliability Standards Development Process 4 V. Texas RE Reliability Standards Development Process 5 A. Assumptions and Prerequisites 5 B. Regional Reliability Standards Development Process Steps 6 C. Regional Reliability Standards Integration 12 Appendix A – Stakeholder Representation 14 I. Balanced Decision-Making in Committees 14 II. ERCOT Board of Directors (BOD) 14 III. Ballot Body 14 Appendix B – Principles, Characteristics, and Special Procedures 16 I. Principles 16 II. Regional Reliability Standard Characteristics and Elements 17 III. Maintenance of the Texas RE Reliability Standards Development Process 22 IV. Maintenance of Regional Reliability Standards 22 V. Urgent Actions 22 VI. Interpretations of Standards 23 VII. Appeals 24 Appendix C – Sample Standard Request Form 26 Appendix D – Process Flow Diagram 30 I. Introduction This document defines the fair and open process for adoption, approval, revision, reaffirmation, and deletion of an ERCOT-Specific Reliability Standard (Standard) by the Texas Regional Entity, a division of Electric Reliability Council of Texas, Inc. (“Texas RE”). Standards provide for the reliable regional and sub-regional planning and operation of the Bulk Power System (BPS), consistent with Good Utility Practice within a Regional Entity’s (“RE's”) geographical footprint. Due process is the key to ensuring that Standards are developed in an environment that is equitable, accessible and responsive to the requirements of all interested and affected parties. An open and fair process ensures that all interested and affected parties have an opportunity to participate in a Standard's development. Any entity (person, organization, company, government agency, individual, etc.) with a direct and material interest in the bulk power system has a right to participate by: a) expressing a position and its basis, b) having that position considered, and c) having the right to appeal. Proposed ERCOT-Specific Standards shall be subject to approval by NERC, as the electric reliability organization, and by FERC before becoming mandatory and enforceable under Section 215 of the FPA. No Standard shall be effective within the Texas RE area unless filed by NERC with FERC and app...
Sample 1
Compliance Monitoring Process. Defines for each measure: • The specific data or information that is required to measure performance or outcomes. • The entity that is responsible for providing the data or information for measuring performance or outcomes. • The process that will be used to evaluate data or information for the purpose of assessing performance or outcomes. • The entity that is responsible for evaluating data or information to assess performance or outcomes. • The time period in which performance or outcomes is measured, evaluated, and then reset. • Measurement data retention requirements and assignment of responsibility for data archiving. • Violation severity levels. Southwest Power Pool Regional Entity Standards Development Process Manual October 2, 2007 Table of Contents I. Introduction 3 II. Background 4 III. Regional Reliability Standard Definition, Characteristics, and Elements 5 A. Definition of a Regional Reliability Standard 5 B. Definition of SPP Criteria 5 C. Characteristics of a Regional Reliability Standard 5
Sample 1
Compliance Monitoring Process. ReliabilityFirst Corporation Reliability Standards Development Procedure ReliabilityFirst Reliability Standards Development Procedure ReliabilityFirst Corporation Reliability Standards Development Procedure Table of Contents Introduction 1 Background 2 Regional Reliability Standard Definition, Characteristics, and Elements 3 Roles in the Regional Reliability Standards Development Process 7 Regional Reliability Standards Development Process 8 Appendix A: Maintenance of Regional Reliability Standards Development Process 17 Appendix B: Standard Authorization Request 21 Appendix C: Flowchart for Standards Process 28 Appendix D: Ballot Pool Categories and Registration 30 ReliabilityFirst Reliability Standards Development Procedure ReliabilityFirst Corporation Reliability Standards Development Procedure Introduction This procedure establishes the process for adoption of a Regional Reliability Standard1 (hereinafter referred to as “Standard”) of the ReliabilityFirst Corporation (ReliabilityFirst) and the development of consensus for adoption, approval, revision, reaffirmation, and deletion of such Standards1. ReliabilityFirst Standards provide for the reliable regional and sub-regional planning and operation of the Bulk Power System2 (BPS), consistent with Good Utility Practice2 within the ReliabilityFirst geographical footprint. This procedure was developed under the direction of the ReliabilityFirst Board of Directors (Board), who may request changes to this ReliabilityFirst Reliability Standards Development Procedure (hereinafter referred to as “this Procedure”) as deemed appropriate. A procedure for revising this Procedure is contained in Appendix A. This Procedure is consistent with the North American Electric Reliability Council (NERC) Reliability Standards Development Procedure. Proposed Standards shall be subject to approval by NERC, as the electric reliability organization, and by the Federal Energy Regulatory Commission (FERC) before becoming mandatory and enforceable under Section 215 of the FPA. No Standard shall be effective within the ReliabilityFirst area unless filed by NERC with FERC and approved by FERC. ReliabilityFirst Standards shall provide for as much uniformity as possible with NERC reliability standards across the interconnected BPS. A ReliabilityFirst Standard shall be more stringent than a NERC reliability standard, including a regional difference that addresses matters that the NERC reliability standard does not, or shall be a regional...
Sample 1
Compliance Monitoring Process. Defines for each measure: • The specific data or information that is required to measure performance or outcomes. • The entity that is responsible for providing the data or information for measuring performance or outcomes. • The process that will be used to evaluate data or information for the purpose of assessing performance or outcomes. • The entity that is responsible for evaluating data or information to assess performance or outcomes. • The time period in which performance or outcomes is measured, evaluated, and then reset. • Measurement data retention requirements and assignment of responsibility for data archiving. • Violation severity levels. Attached Supporting Information Elements Interpretations Any interpretations of the SERC Regional Reliability Standards that were developed, and approved by the SERC Executive Committee, to expound on the application of the standard for unusual or unique situations. Implementation Plan Each SERC Regional Reliability Standard shall have an associated implementation plan describing the effective date of the standard or effective dates if there is a phased implementation. The implementation plan may also describe the implementation of the standard in the compliance program and other considerations in the initial use of the standard, such as necessary tools, training, etc. The implementation plan must be posted for at least one public comment period and is approved as part of the ballot of the standard. Supporting References This section references related documents that support reasons for, or otherwise provide additional information related to the standard Examples include, but are not limited to: • Glossary of Terms • Developmental history of the standard and prior versions • Responsible SERC Subgroup • Notes pertaining to implementation or compliance • Standard references • Procedures/Practices • Training and/or Technical Reference • Frequently Asked Questions Document Appendix E: Comment Form for Draft SERC Regional Reliability Standard (Latest approved version of form is posted on the SERC website: xxx.xxxx0.xxx) COMMENT FORM FOR [INSERT APPROPRIATE TITLE OF SERC REGIONAL RELIABILITY STANDARD] Please use this form to submit comments on [insert description]. Comments must be submitted by [date]. You must submit the completed form by emailing it to [insert appropriate contact names & e-mail addresses] with the words [insert appropriate subject] in the subject line. If you have questions please contact [insert...
Sample 1
Compliance Monitoring Process 
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Compliance Monitoring Process

  • Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee:

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

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

  • Project Monitoring Reporting Evaluation A. The Project Implementing Entity shall monitor and evaluate the progress of its activities under the Project and prepare Project Reports in accordance with the provisions of Section 5.08(b) of the General Conditions and on the basis of indicators agreed with the Bank. Each such report shall cover the period of one

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards.

  • Compliance Review During the Term, Developer agrees to permit the GLO, HUD, and/or a designated representative of the GLO or HUD to access the Property for the purpose of performing Compliance-Monitoring Procedures. In accordance with GLO Compliance-Monitoring Procedures, the GLO or HUD will periodically monitor and audit Developer’s compliance with the requirements of this Agreement, the CDBG-DR Regulations, the CDBG Multifamily Rental Housing Guidelines, and any and all other Governmental Requirements during the Term. In conducting any compliance reviews, the GLO or HUD will rely primarily on information obtained from Developer’s records and reports, on-site monitoring, and audit reports. The GLO or HUD may also consider other relevant information gained from other sources, including litigation and citizen complaints. Attachment G GLO Contract No. 19-097-041-B662 5.04 HAZARDOUS MATERIALS: INDEMNIFICATION

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Hiring Process i. School District and Teach For America will collaborate in good faith to facilitate the efficient hiring of individual Teachers, in accordance with the School District’s established District hiring practices.

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