Misoperations Information Data Analysis System (MIDAS)

Similar documents
EASTERN INTERCONNECTION RELIABILITY ASSESSMENT GROUP (ERAG) AGREEMENT

Top Ten Compliance Issues for Implementing the NERC CIP Reliability Standard

Governance. What s a Governance?

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

Federal Energy Regulatory Commission. Small Entity Compliance Guide Mandatory Reliability Standards (Order No. 693)

Entering Claims Spreadsheet Processor

Using the ABB Supplier Inquiry Form

121 FERC 61,143 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION

On-Site vs. Off-Site Electric Power Supply in Refineries in the USA: The Use of Cogeneration in Texas and Louisiana

Re: NERC Notice of Penalty regarding Pacific Gas and Electric Company FERC Docket No. NP10-_-000

CCMS Bulk Claim Upload Pilot Use Only

Midwest Reliability Organization Procedure For NERC PRC-012

NPCC Implementation of the NERC Compliance Monitoring And Enforcement Program (CMEP)

PG&E Web Tool for Reporting Information Related to. NERC Reliability Requirement Compliance

Government of Saskatchewan Executive Council. Oracle Sourcing isupplier User Guide

152 FERC 61,208 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION. 18 CFR Part 39. [Docket No. RM ]

Help Guide. PSI Continuing Education Online For Education Providers

LEA FTP Instructions

Program Guide for Risk-based Compliance Monitoring and Enforcement Program. ERA-01 Rev. 1. NPCC Manager, Entity Risk Assessment

Cyber Security Standards Update: Version 5

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

Single Audits FTP Instructions

Is It Possible to Charge Market-Based Pricing for Ancillary Services in a Non-ISO Market?

Employer Portal User Guide Last Updated: October 2015

Remote. Web Client Overview Version 8.0

Duke Energy Progress Standards of Conduct Transmission Function Employee Job Titles and Job Descriptions 9/1/13

The North American Process: Steps Toward Stronger Partnership A Working Symposium

Alberta Reliability Standard Cyber Security Configuration Change Management and Vulnerability Assessments CIP-010-AB-1

124 FERC 61,317 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION. Communication Protocols for Public Utilities ORDER NO.

AURORA Vulnerability Background

San Diego Gas & Electric Company FERC Order 717 Transmission Function Employee Job Descriptions June 4, Electric Grid Operations

North American Electric Reliability Corporation. Compliance Monitoring and Enforcement Program. December 19, 2008

Detailed Claim Information via DCA Access Online User s Guide

San Diego Gas & Electric Company FERC Order 717 Transmission Function Employee Job Descriptions August 10, Electric Grid Operations

AAPG 2011 Annual Convention & Exhibition April 10, 2011

Federal Cyber-Security Law and Policy: The Role of the Federal Energy Regulatory Commission

PROCEDURE. Ontario Technical Feasibility Exception PUBLIC. Issue 0.2 IESO_PRO_0680

Alberta Reliability Standard Cyber Security System Security Management CIP-007-AB-5

3. Purpose: To improve the reliability of the Bulk Electric System by requiring the reporting of events by Responsible Entities.

PRC Review & Update. Phil O Donnell, WECC Manager Operations & Planning Audits

A. Introduction. B. Requirements. Standard PER System Personnel Training

JOHN H. STOUT PRESIDENT, MARINER CONSULTING SERVICES, INC LAKEWAY DRIVE TAYLOR LAKE VILLAGE, TEXAS

Hearing on Oversight of Federal Efforts to Address Electromagnetic Risks. May 17, 2016

Spreadsheet File Transfer User Guide. FR 2915 Report of Foreign (Non-U.S.) Currency Deposits

Alberta Reliability Standard Cyber Security Security Management Controls CIP-003-AB-5

TREE CUTTING & TRIMMING INFORMATION As of

Customer admin guide. UC Management Centre

CIP Cyber Security Security Management Controls

NERC Alert System Overview

WebGrants. Registration Tutorial. Minnesota State Arts Board October 2012

Electronic Bid Submission Supplier Guide

COLORADO SPRINGS UTILITIES ATTACHMENT K TO OPEN ACCESS TRANSMISSION TARIFF

DISCUSSION PAPER: Peak Reliability Performance Metrics

NB Appendix CIP NB-1 - Cyber Security Personnel & Training

San Diego Gas & Electric Company FERC Order 717 Transmission Function Employee Job Descriptions. Electric Grid Operations

WHITE PAPER CYBER SECURITY AND ELECTRIC UTILITY COMMUNICATIONS WHAT NERC/CIP MEANS FOR YOUR MICROWAVE

Sprint Supplier Registration Guide

CIP Cyber Security Electronic Security Perimeter(s)

Updated November 20, Director, System Planning

The economic impact. of current Investment Trends in. Infrastructure

GeneSys. Unit Six.Two: Administering a 360 Project. genesysonline.net. psytech.com

Mass Announcement Service Operation

Alberta Reliability Standard Cyber Security Personnel & Training CIP-004-AB-5.1

CSV Notes. English and Irish versions are located on this document

Electric Transmission Planning under FERC Order No. 1000

Can I automatically be notified when new positions open?

Project Tracking and Cost Estimation Tool Member Impacting Project Overview

How To Register With The University Of West Florida

Student Blue Portal. Table of Contents

4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s)

Instructions How to use and send the PIT (Physician in Training) Permit Application Spreadsheet

Bahamas Tax Information Exchange Portal Documentation

Process: Self Service

HOW TO SUBMIT enbs IN THE KEY

How to claim Gift Aid Online

Florida Department of Environmental Protection Office of Technology and Information Services

NERC Cyber Security Standards

Alberta Reliability Standard Cyber Security Physical Security of BES Cyber Systems CIP-006-AB-5

Import: Create Teachers

Managing Submissions via ExpressO: A Guide for Law Review Editors

Chris Christie Governor Kim Guadagno Lt. Governor. Robert M. Czech Chair/Chief Executive Officer

I. Setting Listserv password

MEMORANDUM OF UNDERSTANDING THE INDEPENDENT ELECTRICITY SYSTEM OPERATOR THE NORTH AMERICAN ELECTRIC RELIABILITY CORPORATION

Cisco Unified Communications Manager 7.1 SIP Configuration Guide

Labor Law Compliance Management System (LCMS) Frequently Asked Questions

Assessment of. Demand Response and Advanced Metering. Staff Report

Center for Careers, Life, and Service (CLS) Online Application Tutorial

Creating Proposals and Managing Grants

EDI Reference Manual for NJPDES Monitoring Report Forms 6/19/03 Edition

152 FERC 61,200 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION. 18 CFR Part 40. [Docket No. RM ]

The North American Electric Reliability Corporation ( NERC ) hereby submits

Accounts Receivable Invoice Upload

EVENT REGISTRATION UPLOADER DOCUMENTATION

Standard CIP 007 3a Cyber Security Systems Security Management

Evaluating a File. How to Upload and Evaluate a File To upload and evaluate a file, follow these steps.

Electronic Invoicing. InvoiceWorks Supplier User Guide For Atlas Air

UNDERSTANDING THE UG RESEARCH GRANTS ONLINE APPLICATION SYSTEM (User Guide)

ReliabilityFirst CIP Evidence List CIP-002 through CIP-009 are applicable to RC, BA, IA, TSP, TO, TOP, GO, GOP, LSE, NERC, & RE

How to Use the H-ITT Analyzer Version 2.4.4

Report on Outages and Curtailments During the Southwest Cold Weather Event of February 1-5, 2011

Transcription:

Misoperations Information Data Analysis System (MIDAS) End User Guide February 1, 2016 NERC Report Title Report Date I

Table of Contents 1. Preface... iii 2. Reporting Obligations... 4 2.1 Entities Obligated to Report Misoperations... 4 2.1.1 Including / Excluding Entities from Misoperations Obligations... 4 3. Reporting Misoperations and Protection System Operations... 4 3.1 Using the Submission Site... 4 3.1.1 Submission... 4 3.1.2 Resubmittal... 5 4. Email Notifications... 5 4.1 Submission Confirmation Email... 5 4.2 Records Processed Email... 6 4.3 Reminder Emails... 6 5. Appendix A: List of Validations... 7 5.1 Misoperations... 7 5.1.1 Required and non required fields... 7 5.2 Protection System Operations... 8 5.2.1 Required and non required fields... 8 NERC Report Title Report Date ii

1. Preface The North American Electric Reliability Corporation (NERC) is a not for profit international regulatory authority whose mission is to assure the reliability of the bulk power system (BPS) in North America. NERC develops and enforces Reliability Standards; annually assesses seasonal and long term reliability; monitors the BPS through system awareness; and educates, trains, and certifies industry personnel. NERC s area of responsibility spans the continental United States, Canada, and the northern portion of Baja California, Mexico. NERC is the electric reliability organization (ERO) for North America, subject to oversight by the Federal Energy Regulatory Commission (FERC) and governmental authorities in Canada. NERC s jurisdiction includes users, owners, and operators of the BPS, which serves more than 334 million people. The North American BPS is divided into several assessment areas within the eight Regional Entity (RE) boundaries, as shown in the map and corresponding table below. The Regional boundaries in this map are approximate. The highlighted area between SPP and SERC denotes overlap as some load serving entities participate in one Region while associated transmission owners/operators participate in another. FRCC MRO NPCC RF SERC SPP RE Texas RE WECC Florida Reliability Coordinating Council Midwest Reliability Organization Northeast Power Coordinating Council ReliabilityFirst SERC Reliability Corporation Southwest Power Pool Regional Entity Texas Reliability Entity Western Electricity Coordinating Council NERC Report Title Report Date iii

2. Reporting Obligations 2.1 Entities Obligated to Report Misoperations All Entities that are registered for compliance obligations for the following functions: TO, GO, and DP are obligated to report on misoperations every quarter. 2.1.1 Including / Excluding Entities from Misoperations Obligations Entities can be excluded from receiving email reminders by navigating to that entity and setting the MIDAS Exempt field under General to Yes. 3. Reporting Misoperations and Protection System Operations 3.1 Using the Submission Site 3.1.1 Submission Navigate to the Misoperations Submission site (https://misops.nerc.net ): Fill out the required fields, starting with the NCR Number.

As a user starts typing in an NCR number, a list will automatically start populating with all entities that match the characters typed in the field. Those characters don t have to be at the beginning of the NCR, e.g. typing in 401 will return NCR11401. Once the entity has been chosen, the Lead Region field will be populated with all regions for which the entity is registered as a TO, DP or GO. Likewise, questions regarding whether there are protection system operations and / or misoperations for each region will appear. These must be filled out before the record can be submitted. Clicking on submit will complete the process of submission. Note the following: A user cannot choose a quarter + year that is in the future. The key code is sent to registered entities through an alternative path (e.g. email) and should be entered into the field exactly. If yes is answered for any region for either question Do you have [misoperations / protection system operations] to report for the following regions?, then a misoperations file must be uploaded. The misoperations file must be an.xlsx file and use the NERC approved format. 3.1.2 Resubmittal If you are resubmitting data, select the Resubmittal Only button, and the questions regarding whether there are misoperations or protection system operations to report will not appear. 4. Email Notifications 4.1 Submission Confirmation Email Once a record has submitted, an email notification will be sent to the following: MIDAS End User Guide 5

1) The email address supplied on the submission form 2) All Contacts associated to the Submitting NCR, who are subscribed to receiving MIDAS notifications 4.2 Records Processed Email Once a submission is received, it is processed, which includes validating all entries in the spreadsheet. Users will receive notification that the submission has been processed, with one of the following statuses: Processed Successfully This status indicates that all records in the spreadsheet were processed. Processed with Some Failed Records This status indicates that some records were processed and some were not. For records that were not processed successfully, a file for each record type (PS Operation and Misoperations) is created that describes the error encountered during processing. These files are attached to the email. 4.3 Reminder Emails If a qualified entity does not report for a particular quarter, email reminders will be sent out periodically. MIDAS End User Guide 6

5. Appendix A: List of Validations 5.1 Misoperations 5.1.1 Required and non-required fields * indicates conditionally required (see additional validations below) Required Not required Misoperation ID Fault Type Region Where Misoperation Occurred Restoration Method NERC Compliance Registry Number Incorrect Settings et. al. Sub Cause Code Jurisdiction Communication Sub Cause Misoperation Date Communication System Type Misoperation Time Protection System Schemes Time Zone Protection Systems/Components that Misoperated Faculty Name Relay Technology Equipment Name Microprocessor Relay Manufacturer Equipment Type TADS Elements Faculty Voltage GADS Elements Equipment Removed from Service Corrective Action Plan Event Description CAP Target Completion Date * Misoperation Category CAP Actual Completion Date * Cause(s) of Misoperation Additional Contact Name Is this a TADS reportable event? Additional Contact s Phone Number Is this a GADS reportable event? Additional Contact s Email Address Analysis and Corrective Action Status Comments Reported By Reported By Phone Reported By Email Date Reported 5.1.2 Additional Validation requirements A spreadsheet cannot contain duplicate Misoperation IDs Email Addresses must be a valid email format All dates and times must be a valid date format If Is this a GADS Reportable Event = yes, then GADS Elements cannot be blank If Is this a TADS Reportable Event = yes, then TADS Elements cannot be blank If Cause(s) of Misoperation equals any of the following then Components and Relay Technology fields cannot be blank: o Relay failures/malfunctions o Incorrect settings o Logic errors MIDAS End User Guide 7

o Design errors If Analysis and Corrective Action Status equals Corrective Action Completed, then the CAP Actual Completion Date cannot be blank If Analysis and Corrective Action Status equals Corrective Action In Progress, then the CAP Target Completion Date cannot be blank 5.2 Protection System Operations 5.2.1 Required and non-required fields * indicated conditionally required (see additional validations below) Required Not required Date Reporting Year Date Reporting Quarter Region Entity NCR Total Number of Operations* Voltage Class 5.2.2 Additional Validation Requirements Total Number of Operations cannot be blank. If there are no operations for a particular region, 0 must be entered. MIDAS End User Guide 8