CCET Discovery Across Texas Data Quality Plan - Overview

Slides:



Advertisements
Similar presentations
Marianna Vaiman, V&R Energy
Advertisements

© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 Troubleshooting Working at a Small-to-Medium Business or ISP – Chapter 9.
1 A survey of Internet Topology Discovery. 2 Outline Motivations Internet topology IP Interface Level Router Level AS Level PoP Level.
Firewall Security Chapter 8. Perimeter Security Devices Network devices that form the core of perimeter security include –Routers –Proxy servers –Firewalls.
1 Interconnecting LAN segments Repeaters Hubs Bridges Switches.
Firewalls and VPNS Team 9 Keith Elliot David Snyder Matthew While.
THE SYSTEMS LIFE CYCLE ANALYSE DESIGN IMPLEMENT MAINTENANCE IDENTIFY/INVESTIGATE.
“Discovery Across Texas” New Technology Solutions for Wind Integration in ERCOT Synchrophasor Project Status Update Bill Muston Oncor Electric Delivery.
S/W Project Management
Synchrophasor Measurement Implementation in ERCOT
Current Job Components Information Technology Department Network Systems Administration Telecommunications Database Design and Administration.
Cisco S2 C4 Router Components. Configure a Router You can configure a router from –from the console terminal (a computer connected to the router –through.
18 Copyright © Oracle Corporation, All rights reserved. Workshop.
13 Step Approach to Network Design Steps A Systems Approach 8Conduct a feasibility Study 8Prepare a plan 8Understand the current system 8Design.
PwC New Technologies New Risks. PricewaterhouseCoopers Technology and Security Evolution Mainframe Technology –Single host –Limited Trusted users Security.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—3-1 Implementing a Scalable Multiarea Network OSPF- Based Solution Lab 3-5 Debrief.
November 16, 2012 Synchrophasor Meeting Dynamic Model Validation Project Jonathan Rose Engineer, Resource Integration Sidharth Rajagopalan Engineer, Dynamic.
Managing of Limits during Loss of Analysis Tools/ EMS April 23, 2014.
NERC Lessons Learned Summary LLs Published in September 2015.
AN OVERVIEW Rocky K. C. Chang13 Sept The web 2.
Demand Response Task Force. 2 2 Outline  Overview of ERCOT’s role in the CCET Pilot  Overview of Stakeholder Process – What’s been done to date?  Questions.
Virtual Machine Movement and Hyper-V Replica
Disaster Recovery Planning (DRP) DRP: The definition of business processes, their infrastructure supports and tolerances to interruptions, and formulation.
PART1 Data collection methodology and NM paradigms 1.
25/09/ Firewall, IDS & IPS basics. Summary Firewalls Intrusion detection system Intrusion prevention system.
I/Watch™ Weekly Sales Conference Call Presentation (See next slide for dial-in details) Andrew May Technical Product Manager Dax French Product Specialist.
Quality and Value for the Exam 100% Guarantee to Pass Your Exam Based on Real Exams Scenarios Verified Answers Researched by Industry.
1 Computer Networks Chapter 5. Network layer The network layer is concerned with getting packets from the source all the way to the destination. Getting.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
Discovery Across Texas: Technology Solutions for Wind Integration in ERCOT Using Synchrophasor Technology for Wind Integration and Event Monitoring in.
MISO – Synchrophasor GPA Users Forum Sept 7th, 2011.
Systems Analysis and Design in a Changing World, Fifth Edition
Monitoring Windows Server 2012
Chapter 19: Network Management
Instructor Materials Chapter 8: Network Troubleshooting
Webinar Series Kickoff
Chapter 8 Environments, Alternatives, and Decisions.
NERC Lessons Learned Summary
NET 536 Network Security Firewalls and VPN
Online RadFET reader for beam loss monitoring system
Distributed Network Traffic Feature Extraction for a Real-time IDS
Layered Architectures
Chapter 4: Routing Concepts
MONITORING MICROSOFT WINDOWS SERVER 2003
Top-Down Network Design Chapter Nine Developing Network Management Strategies Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Conditions Data access using FroNTier Squid cache Server
Chapter 2: Static Routing
The Move to Hosted Ezproxy Experienced by Texas Tech University
NERC CIP Implementation – Lessons Learned and Path Forward
18-WAN Technologies and Dynamic routing
TASK 4 Guideline.
Chapter 8: Monitoring the Network
Network Core and QoS.
File Transfer Issues with TCP Acceleration with FileCatalyst
Chapter 12: Physical Architecture Layer Design
CS 501: Software Engineering Fall 1999
Performance And Scalability In Oracle9i And SQL Server 2000
EE 122: Lecture 7 Ion Stoica September 18, 2001.
Implementation of ICT-related solutions
Distributed Systems CS
Decompression Flaws in PI Historian
Use Case Document Definitions
5 POINT PLAN THE SYSTEMS LIFE CYCLE ANALYSE DESIGN
Requirements Definition
Ch 17 - Binding Protocol Addresses
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Network Core and QoS.
Top-Down Network Design Chapter Nine Developing Network Management Strategies Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Distributed Systems CS
Presentation transcript:

CCET Discovery Across Texas Data Quality Plan - Overview November 15, 2012 John Ballance – EPG

Data Quality Plan In order for ERCOT to achieve a production quality phasor monitoring that can be relied upon in real-time operations, three conditions must be met: The data must be flowing reliably from the PMU to the operator’s console, The data must be valid, and The data must be monitoring the critical locations (right places). The Data Quality Plan will address the first condition 10.11.12

Dropout is Observable RTDMS Reports show significant dropout data on some signals (60-99%) Observation of ePDC Management Tool shows major dropouts (60-99%) in real-time data streams Data availability testing performed on the RTDMS DB confirms the presence of data dropouts Examination of one-second and one-minute tables in RTDMS database confirms down sampled data is missing on signals as well 10.11.12

Goals Identify nodes in phasor network affecting data availability (i.e., data dropouts) Classify identified dropout issues by severity and frequency Determine likely causes of data dropouts at identified locations Propose solutions to help eliminate identified data availability problems 10.11.12

Phasor Data Network AEP ePDC Oncor PDC Phasor Archiver Phasor Database 10.11.12

Possible Locations of Data Dropout RTDMS Reports (and/or RTDMS ISG) to RTDMS database interface RTDMS Server to RTDMS Database interface ePDC to RTDMS Server interface problems ePDC input and/or output configuration problems Problems on the inbound ePDC stream (e.g. T.O. PDC/PMU problems, PMU installation problems, etc.) 10.11.12

Review Process Dropout Location Identification Severity Classification From end-point back to source Severity Classification Minor – less than 1% loss of data Moderate – 1-5% loss of data Severe – greater than 5% loss of data Issues may be recurring or non-recurring Likely cause determination 10.11.12

Data Sources for Investigation Extracts from the following sources for a 24 hour period will be used to analyze data quality: ERCOT RTDMS Data Base ERCOT Phasor Archiver Data Base (from ePDC) AEP Phasor Archiver Data Base this represents the stream being sent to ERCOT Oncor recorded PDC Output Stream 10.11.12

Likely Causes of Data Loss Application configurations, including ePDC I/O settings RTDMS Server settings Database Database scripting errors Database to server configuration problems Hardware Improper host machine configurations Physical network or firewall problems Source Measurements/Incoming Data Improper or undocumented PMU/PDC configurations Unavailable or dead PMU signals Communication link between TO PMU/PDC to ERCOT ePDC Firewall, Router, IP address issues 10.11.12

Likely Solutions The difficulty of identifying a cause, and the time and resources required to implement a solution may vary considerably for different problems. In general, Configuration issues will be fairly easy to identify and eliminate Database and hardware-level problems may be straightforward to identify at a high level, but difficult to pinpoint if the cause is an individual piece of network hardware or a corrupt database. Incoming data dropouts will be relatively easy to identify after local problems have been eliminated, but solutions will require cooperation with the entities that manage and document the remote PMU or PDC installations. 10.11.12

Study Plan Select date for data base extract AEP-ERCOT data stream intermittency (mid-September) has now been resolved Extract the data and send to EPG EPG will perform analysis, recommend configuration tuning and potential network/server interface adjustments EPG will prepare a summary report and recommendations 10.11.12

Questions 10.11.12