Current Standards Process for Reliability, Resilience, and Security
The current standards process focuses on ensuring reliability, resilience, and security in regulatory directives. It involves remanding standards to committees, convening technical conferences, re-ballingoting within 45 days, and considering input for further work. The process also covers the initiation of new sections, issuing notices and directives, and acting on urgent reliability issues. Special rules apply for standards not meeting regulatory directives.
Download Presentation
![](/assets/img/so-down.gif)
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Current Standards Process 1 RELIABILITY | RESILIENCE | SECURITY
Special Rule for Regulatory Directives - Section 321 Standard submitted to Board that does not meet regulatory directives Remand to Standards Committee with instructions Standard passes final ballot Standard development process reinitiates by either: Reinitiating project with existing SAR Developing new SAR and project to address directives 2 RELIABILITY | RESILIENCE | SECURITY
Section 321 Remand to Standards Committee with instructions Convene technical conference Prepare memo Re-ballot standard within 45 days Standard fails in ballots to timely meet regulatory directives Yes Adopt standard and file Achieve 66 2/3% approval? No Issue notice of intent to adopt, solicit comment Convene technical conference (optional) Considering the record and input: Adopt Adopt as draft and file as non- enforceable Remand for further work Yes Achieve 60% approval? No Direct SC and/or NERC staff to draft Convene technical conference (optional) Considering the record and input: Adopt Adopt as draft and file as non- enforceable Remand for further work 3 RELIABILITY | RESILIENCE | SECURITY
Proposed Section 322 Board issues notice; opens comment period Board considers input Board sees inadequate or no progress on urgent reliability issue Board issues directive SDT acts on directive (feedback) 4 RELIABILITY | RESILIENCE | SECURITY
Potential Section 322 Initiation 5 RELIABILITY | RESILIENCE | SECURITY
Potential Section 322 Initiation 6 RELIABILITY | RESILIENCE | SECURITY
Special Rule for Regulatory Directives - Section 321 Standard submitted to Board that does not meet regulatory or Board directives Remand to Standards Committee with instructions Standard passes final ballot Standard development process reinitiates by either: Reinitiating project with existing SAR Developing new SAR and project to address directives 7 RELIABILITY | RESILIENCE | SECURITY
Proposed Revised Section 321 Remand to Standards Committee with instructions Standard fails in ballots to timely meet regulatory or Board directives Convene technical conference Prepare memo Re-ballot standard within 45 days Yes Adopt standard and file Achieve 66 2/3% approval? No Issue notice of intent to adopt Convene technical conference (optional) Considering the record and input Adopt Adopt as draft and file as non- enforceable (regulatory directives only) Remand for further work Yes Achieve 60% approval? No Direct SC and/or NERC staff to draft Convene technical conference (optional) Considering the record and input Adopt Adopt as draft and file as non- enforceable (regulatory directives only) Remand for further work 8 RELIABILITY | RESILIENCE | SECURITY