Procedures and Forms 2008 FRCC Compliance Workshop April 8-9, 2008.

Slides:



Advertisements
Similar presentations
MONITORING OF SUBGRANTEES
Advertisements

The HRPP FYI Process and the UPIRSO/SAE Review Sheet An IRB Infoshort February 2014.
Checking & Corrective Action
Frequently Asked Questions Alberta Reliability Standards Compliance Version 1.0 – Effective April 30, 2013 (Please visit the website to download the latest.
Key Reliability Standard Spot Check Frank Vick Compliance Team Lead.
ANRC AACD Arkansas Conservation Districts Training Program Power Point 6 Appointments and Election of Directors.
CIP Spot Check Process Gary Campbell Manager of Compliance Audits ReliabilityFirst Corporation August, 2009.
[INSERT APPLICABLE REGIONAL ENTITY NAME/LOGO] [ENTITY NAME] [FUNCTION CERTIFYING] Certification [LOCATION] – [DATES OF ON-SITE VISIT] [Presenter Name,
Compliance Application Notice Process Update and Discussion with NERC MRC.
S17: Field work. Session Objectives  To explain the manner in which field audit is carried out.  To explain the nature of evidence and the different.
Notice of Compliance Audit
D. Keane June Internal Quality Audits (4.14) -ISO Requirements for Internal Audits -The Audit Process -Templates for Meeting Requirements.
SAFETY AUDIT. 2.1 Definition of audit. Critical systematic inspection of an organization‘s activities in order to minimize losses due to accidents.
1 Addendum Fall 2006 Limited-Term RFP Detailed Instructions for Bidder Registration and Proposal Submission ENTERGY SERVICES, INC. September 11, 2006.
Current Status Of The ERO Transition Activities To Comply With The 2005 EPAC ERCOT Board Meeting February 21, 2006 Sam Jones, COO.
ERCOT Compliance Audits Robert Potts Sr. Reliability Analyst March 23, 2005.
Compliance Monitoring Audit Tutorial Version 1.0 April 2013.
FHSAA Eligibility and Compliance Allegations And Investigations Florida High School Athletic Association.
1 Texas Regional Entity Report December Performance Highlights ERCOT’s Control Performance Standard (NERC CPS1) score for October – Initial.
1 Arizona Corporation Commission BTA Workshop Presenter: Steven Cobb May 23, 2008.
Compliance Program Implementation Plan 2011 December 15, 2010 Ray Palmieri 1.
[INSERT APPLICABLE REGIONAL ENTITY NAME/LOGO] [ENTITY NAME] [FUNCTION CERTIFYING] Certification Review for [RELATED ENTITIES] [LOCATION] – [DATES OF ON-SITE.
SACS Reaffirmation Project Compliance Certification Team Leaders Meeting Friday, August 27, – 11:00AM 107 Main Building Jennifer Skaggs, Ph.D. SACS.
Michelle Groy Johnson Quality Improvement Officer Research Integrity Office Tough Love: Understanding the Purpose and Processes of Quality Assurance.
Update On The ERO Transition Activities To Comply With The 2005 EPAC ERCOT TAC Meeting March 9, 2006 Sam Jones, COO.
SPP.org 1. EMS Users Group – CIP Standards The Compliance Audits Are Coming… Are You Ready?
Texas Regional Entity Update Sam Jones Interim CEO and President Board of Directors July 18, 2006.
NERC Data Collection & Coordination. Rules of Procedure: Section 1600 Overview  NERC’s authority to issue a mandatory data request in the U.S. is contained.
Assessing Compliance. 2 NERC Compliance Workshop 11/02/07 Documentation of Compliance with NERC Reliability Standards Jeff Whitmer.
QUALITY OF EVIDENCE FRCC Compliance Workshop September/October 2008.
1 Texas Regional Entity 2008 Budget Update May 16, 2007.
Overview of WECC and Regulatory Structure
This PowerPoint has been produced for the public and is made available for non-commercial use (e.g. toolbox meetings,
Item 5d Texas RE 2011 Budget Assumptions April 19, Texas RE Preliminary Budget Assumptions Board of Directors and Advisory Committee April 19,
Date Meeting Title (optional) Enforcement and Sanctions Presenter Name Presenter Title (Optional)
1 You are a New Member of the JAC; NOW WHAT? As a new Journey-Level Advisory Council (JAC) member, you probably have many questions, including those about.
Problem Areas Updates Penalties FRCC Compliance Workshop September / October
AEER QUEECA PB and MB meetings, 15/16 Jan 2015, Porto, PT Association for Engineering Education of Russia The Trial Accreditations in CA countries with.
SACS Reaffirmation Project Compliance Certification Team Orientation Overview Thursday, September 30, – 11:00AM 209 Main Building – Lexmark Public.
Company Confidential Registration Management Committee RMC Auditor Workshop Charleston, SC July Supplemental Oversight AS9104/2A & Special.
Presented by: Jan Stanley, State Title I Director Office of Assessment and Accountability June 10, 2008 Monitoring For Results.
Compliance Monitoring and Enforcement Audit Program - The Audit Process.
Texas Regional Entity Report Mark Henry June 6, 2008.
2011 CIP Compliance Monitoring – On-site Audits for Entities with Critical Cyber Assets Lew Folkerth January 31,
2011 ReliabilityFirst 693 Compliance Audit Process for 6 Year Audit Cycle Entities Glenn Kaht Senior Consultant - Compliance ReliabilityFirst Corporation.
IDEA FORMAL COMPLAINTS Administrative Accountability Branch Kentucky Department of Education Understanding the Self-Investigation Process.
Texas Regional Entity ROS Presentation January 15, 2009 T EXAS RE ROS P RESENTATION J ANUARY 2009.
1 Power System Restoration. 2 Not Active 3 4 Compliance Audit Process APPA E&O Technical Conference – Atlanta April 16, 2007.
1 Addendum FALL 2004 RFP Detailed Instructions for Bidder Registration and Proposal Submission ENTERGY SERVICES, INC. November 2004.
WHAT YOU NEED TO KNOW ABOUT NERC ERO COMPLIANCE Louise McCarren Chief Executive Officer – WECC APPA National Conference June 16, 2009 Salt Lake City, Utah.
Compliance Program Update Lisa Milanes Manager of Compliance Administration.
1 Compliance Update June Control Performance Highlights  NERC CPS1 Performance April Performance  April performance comparison April 2007:
WORKSHOP ON ACCREDITATION OF BODIES CERTIFYING MEDICAL DEVICES INT MARKET TOPIC 9 CH 8 ISO MEASUREMENT, ANALYSIS AND IMPROVEMENT INTERNAL AUDITS.
Regional Accreditation Workshop For Asia and Eastern Europe Manila, Philippines th March, 2012.
1 Early Intervention Monitoring Wyoming DDD April 2008 Training.
Planning meetingCertification audit, stage 1 Pre-audit (optional) Document review Prior to every certification audit a planning meeting is conducted where.
Enforcement 101 Rachael Ferrin Associate Process Analyst.
Allegations & Investigations
Frequently Asked Questions Alberta Reliability Standards Compliance
Updated ERO Enterprise Guide for Internal Controls
MAC Board Effectiveness Survey
Overview of the FEPAC Accreditation Process
Background (history, process to date) Status of CANs
[INSERT APPLICABLE REGIONAL ENTITY NAME/LOGO]
[INSERT APPLICABLE REGIONAL ENTITY NAME/LOGO]
Coordinate Operations Standard
MAC Board Effectiveness Survey
CMEP Technology Project
ENTERGY SERVICES, INC. February 23, 2006
Standards Development Process
Presentation transcript:

Procedures and Forms 2008 FRCC Compliance Workshop April 8-9, 2008

2 The Eight (8) Compliance Monitoring Processes Process to collect information in order to make assessments of compliance: 1. Compliance Audits 2. Self-Certification 3. Spot Checking 4. Self-Reporting 5. Exception Reporting 6. Complaint 7. Compliance Violation Investigations 8. Periodic Data Submittals

3 Compliance Audits A systematic, objective review and examination of records and activities to determine whether a Registered Entity meets the requirements of applicable Reliability Standards. On-site Off-site

4

5 Compliance Audits The compliance audit scope will include all Reliability Standards applicable to the Registered Entity monitored in the NERC/FRCC Implementation Plans. The scope may also include other Reliability Standards and FRCC Regional Reliability Standards that have been approved by FERC.

6 Compliance Audits If the data retention requirements of a Reliability Standard does not cover the full period of the compliance audit, the audit will only be applicable to the data retention period specified in the Reliability Standard. Audit team members are required to sign and return FRCC Non-Disclosure Agreements.

7 Compliance Audits FRCC compliance staff notifies the registered entity of the audit, identifies the audit team members, and sends Pre-Audit Questionnaire and request for data. The registered entity completes and returns Pre-audit Questionnaire and requested documentation to the FRCC by the required data.

8 Compliance Audits FRCC compliance staff distributes completed Pre-Audit Questionnaire and documentation to the audit team for review. Compliance audit is conducted. Audit team drafts report, sends to registered entity for review, submits final audit report to FRCC compliance staff.

9 Compliance Audits FRCC compliance staff determines alleged violations. FRCC compliance committee reviews FRCC compliance staff determination. FRCC compliance staff determines applicable penalties and sanctions and sends notice of violation and penalty and/or sanctions to registered entity.

10 Self-Certification Attestation by a Registered Entity of compliance or non-compliance with Reliability Standards for which Self- Certification is required by the FRCC and that are included for monitoring in the FRCC Implementation Plan.

11 Self-Certification FRCC requires all registered entities to self- certify annually. FRCC sends the self-certification forms to the registered entities generally in the first week in November. FRCC compliance staff reviews the information provided by the registered entity to determine compliance with the reliability standards and may request additional data and /or information, if necessary.

12 Self-Certification FRCC compliance staff will provide a summary report of the self-certification results to the FRCC compliance committee for review.

13

14 Spot Checking A process in which the FRCC requests a Registered Entity to provide information to support the Registered Entity’s Self-Certification, Self-Reporting, or Periodic Data Submittal and to assess whether the Registered Entity complies with Reliability Standards. Spot Checking may also be random or initiated in response to events, as described in the Reliability Standards, or by operating problems or system events. Spot Checking may require an on-site review to complete.

15 Spot Checking Spot checks may be initiated at any time to verify or confirm compliance status. FRCC compliance staff sends notice of Spot Check and data request to the registered entity. Registered entity returns requested documentation to the FRCC compliance staff.

16 Spot Checking FRCC compliance staff selects the Spot Check review team members and schedules the review. Spot Check reviews are normally conducted at the FRCC office. The Spot Check review team will provide a report of findings to the FRCC compliance staff. Registered entities will have opportunity to review draft report to correct any errors.

17 Spot Checking FRCC compliance committee reviews FRCC compliance staff determination. Same process for final determination of alleged violation and applicable penalty and/or sanction.

18

19 Compliance Violation Investigations A comprehensive investigation, which may include an on-site visit with interviews of the appropriate personnel, to determine if a violation of a Reliability Standard has occurred.

20 Compliance Violation Investigations Can be initiated at any time in response to a disturbance, complaint, or notification of possible violation. FRCC compliance staff selects the investigation review team members. FRCC compliance staff will notify the registered entity and NERC within 2 business days of the decision to conduct a Compliance Violation Investigation.

21 Compliance Violation Investigations FRCC will provide at least 20 calendar days notice for data request. The investigation review team members will review preliminary information or data and determine if additional data or on-site inspections are needed. On-site inspection is scheduled, if needed.

22 Compliance Violation Investigations Registered entity returns requested data in the required format to the FRCC compliance staff. Investigation review team identifies a finding of compliance or non-compliance. Investigation review team provides a report of the findings to the FRCC compliance staff.

23 Compliance Violation Investigations FRCC compliance staff will provide the determination of alleged violation to the FRCC compliance committee. Same process for final determination of alleged violation and applicable penalty and/or sanction.

24

25 Self-Reporting A report by a Registered Entity of a violation of a Reliability Standard, based on its own assessment, in order to provide prompt reports of any Reliability Standard violation and the actions that were taken or will be taken to resolve the violation.

26 Self-Reporting Self-reporting is encouraged any time a registered entity becomes aware: –Of their violation of a reliability standard, or –A change in the violation severity level of a previously reported violation. Self reporting may be considered as a mitigating factor during the determination of a penalty and/or sanction.

27 Self-Reporting The process steps of self-reporting are as follows: Download the Self-reporting submittal form from the FRCC website at: Fill out the Self-reporting information and forward the applicable mitigation plan to the FRCC Compliance Manager at: The FRCC compliance staff will review the information to determine compliance and may request the registered entity to provide clarification or additional data and/or information.

28 Self-Reporting The FRCC compliance staff completes the assessment of the registered entity. Same process for final determination of alleged violation and applicable penalty and/or sanction.

29

30 Periodic Data Submittals Modeling, studies, analyses, documents, procedures, methodologies, operating data, process information or other information to demonstrate compliance with Reliability Standards and provided by Registered Entities to the FRCC on a time frame required by a Reliability Standard or an ad hoc basis.

31 Periodic Data Submittals In 2008, the FRCC requires monthly reporting for the following standards; BAL-001-0BAL BAL EOP-002-2FAC INT IRO-004-1IRO PER PER-004-1PRC PRC TOP-005-1TOP Reporting forms are located on the FRCC compliance website at:

32 Periodic Data Submittals Reports are due to the FRCC by the 10 th of each month. Submit to Each report will be for the calendar month preceding the 10 th of the month that it is submitted. Not applicable, fully compliant, or a violation severity level (level of non- compliance) must be indicated for each standard and requirement.

33 Periodic Data Submittals For reliability standard FAC-003-1, requirement 3 requires reporting of vegetation caused outages. –If during the reporting period you had an actual reportable vegetation caused outage, compete the Vegetation Management Report and outage details. For ALL reports of non-compliance, a mitigation plan is required. Please submit the mitigation plan to FRCC along with the monthly report.

34

35 Exception Reporting Information provided to the FRCC by a Registered Entity indicating that a violation of a Reliability Standard has occurred (e.g., a system operating limit has been exceeded). Some Reliability Standards require Exception Reporting.

36 Exception Reporting Some reliability standards require reporting of exceptions to compliance with the reliability standard as a form of compliance monitoring. FRCC requires registered entities to provide reports identifying any exceptions to the extent required by any reliability standard. FRCC requires registered entities to confirm the number of exceptions that have occurred in a given time period identified by NERC, even if the number of exceptions is zero.

37 Complaints An allegation that a Registered Entity violated a Reliability Standard.

38 Complaints Either NERC or FRCC may receive complaints alleging violations of a reliability standard. –FRCC will conduct a review of each complaint it receives to determine if the complaint provides sufficient basis for a compliance violation investigation. –NERC will conduct a review of each complaint That is related to FRCC. Where the FRCC determines it cannot conduct the review. If the complainant wished to remain anonymous. If the complainant specifically requests NERC to conduct a review of a complaint.

39 Complaints The complainant notifies NERC or the FRCC by using the NERC hotline, submitting a NERC complaint reporting form, or by other means. –A link to the complaint form is posted on the NERC and FRCC websites. The complainant should include sufficient information to enable NERC or the FRCC to make an assessment of whether the initiation of a compliance violation investigation is warranted. –NERC or FRCC may not act on a complaint if the complaint is incomplete and does not include sufficient information.

40

41

42 ? Questions