september 18, 2013 – reliability committee

6
SEPTEMBER 18, 2013 – RELIABILITY COMMITTEE Jerry Elliott LEAD ANALYST – SYSTEM OPERATIONS SUPPORT Periodic Reviews Operating Procedures

Upload: tate-kaufman

Post on 31-Dec-2015

24 views

Category:

Documents


4 download

DESCRIPTION

September 18, 2013 – Reliability committee. Jerry Elliott. Lead Analyst – System Operations support. Periodic Reviews. Operating Procedures. Operating Procedure Reviews - Current Process. ISO conducts required periodic reviews of all Operating Procedures as follows, - PowerPoint PPT Presentation

TRANSCRIPT

S E P T E M B E R 1 8 , 2 0 1 3 – R E L I A B I L I T Y C O M M I T T E E

Jerry ElliottL E A D A N A L Y S T – S Y S T E M O P E R A T I O N S S U P P O R T

Periodic Reviews

Operating Procedures

2

Operating Procedure Reviews - Current Process

• ISO conducts required periodic reviews of all Operating Procedures as follows,– OP-4, OP-6, OP-7 and OP-19 at least annually– All other OPs at least every two years

• OP documents are often times changed more frequently due to business and compliance requirements

• If necessary changes are identified they are highlighted and put through the document change process which includes NEPOOL consideration and upon approval a new revision number is assigned, the revision history is updated and the new document is published

• If no changes are identified as part of these reviews, the document is still considered valid and remains unaltered as the official version– The fact that a review was conducted is logged and tracked separately

3

Operating Procedure Reviews – Identified need to revise the process

• When an OP review identifies no changes are required a document can remain in effect for several years and outwardly appear as if no review has been conducted– This routinely raises questions as to the validity of the document

• These concerns are resolved once the ISO produces the review history

• Transparency of the review process is needed

4

Operating Procedure Reviews – Future Process

• ISO will enhance the recording of periodic Operating Procedure reviews in the revision history of the published document– This includes when no changes were identified

• When no changes are identified– The revision history will be updated to reflect the review and the

revision number will be advanced by .1 • For instance; if the current OP -7 Rev 10 is reviewed with no changes, it will

be republished as Rev 10.1

• The appropriate NEPOOL Technical Committee will be notified of the review as part of the Chairman’s Remarks. – OP9 is considered by the Markets Committee, all other OPs are

considered by the Reliability Committee

5

Operating Procedures – Future Process

• No change to the process when changes are identified– The changes are highlighted and put through the document change

process which includes NEPOOL consideration and upon approval a new revision number is assigned, the revision history is updated and the new document is published• For instance; if the current OP-7 Rev 10 is reviewed and changes are

identified, once approved it will be published as Rev 11

6