PAP 14 Working Session

PAP 14 Agenda

• PAP 14 Background• Scope Redefinition Discussion

– Existing PAP 14 Objectives – Strategies for Prioritizing

• Prioritizing Criteria Critique and Tool Development• Nokhum Presentation• Candidate Use Case Lists• Next Steps

PAP 14 Objectives

• Develop strategies to expand and integrate MultiSpeak, IEC 61850, IEC 61968, IEC 61970, IEEE PC37.237 (Time Tagging), IEEE PC37.239 (COMFEDE) and the future IEEE Common Settings file format for Smart Grid Applications.

• Develop a summary of information required from the power system for various Smart Grid applications.

• Map that information with the already defined models from MultiSpeak, IEC 61970, IEC 61968-11, and IEC 61850.

• Coordinate with the SDOs to extend the existing models.

PAP 14 Objectives Continued

• Identify setting information that is required to perform an automatic verification of the power system configuration to prevent failures due to mis configurations. This information shall include both settings in the devices as well as parameters of the power network that need to be available for verification. – long-term issue (two-year effort) and is Use Case-based; step one: IEEE group work PSRC H5;

• Coordinate with the SDO to extend the existing standards as a result of defining next generation Smart Grid T&D functions.

• JUMP to Twiki– Comfede– Relay Settings

STATUS FROM TWIKI

• C37.239 Comfede Developed into Full IEEE Standard– Event Model “Superset” of IEC 61850– Followon needed for specific 61850 Integration

• IEEE PSRC: Relay Settings Document Available– Some Categories of Settings Addressed– More needed

ACCOMPLISHMENTS WITHIN SDOS

PAP 14 Priority Criteria: Dual Track Priority Criteria

• Key Application Needs• Cross Cutting Applications• Big Picture Applications• Don’t replicate other PAPs

addressing key needs• PAP 14 can add “breadth” to other

related PAP “Depth”• Select a small number of

transmission operations functions which have:

a. Significant cross-cutting needsb. Are architecturally significant, i.e.

• Involve most of the actors• Require critical performance

characteristics

• Integration, Harmonization, Unification of Field Equipment and Back Office

• Event Model Integration• Relay Setting Standards• Electronic Tagging• Several Standards to Be Integrated=>

Rosetta Stone

Key Application Needs Key Standards Gaps

PA P 14:

Tra

ns mi

ssi

on

an d Dis

tri

bu tio n Po we

r Sys

te ms

Mo

del

Ma

ppi

ng:

Sco

pe

Per

spe

cti ves

AMIDistribution automation

Substation automation

WAMACWind integration

DER integration

Powe

r Sys

tem

Reso

urce

sCo

ntro

ls

sens

ors

Com

mun

icat

ion

Infra

stru

ctur

eDa

ta

inte

grat

ion

Appl

icat

ions

Power procurementMarket operations

Regional TransmissionOperator

Distribution Control Center External corporations

IEC 61400-25IEC 61850

IEC 61968

IEC 61970 Multispeak

IEEE C37.239 ASHRAE

SSPC 201

• IEEE Power System Relay Committee– H5 Relay Settings– H2 Event Model IEEE C37.239 (Comfede)– H2 Smart Grid Applications– C2 Relay Information For Smart Grid

• International Electrotechnical Commission– TC 57 WG 10 Substations (IEC 61850)– TC 57 WG 19 Architecture/Harmonization– TC 57 WG 13 Unified T&D Modeling (CIM)

• NASPI net– Use Cases

SSOS EXECUTING PAP 14 RELATED WORK

• Rescope to Key Priority Areas– Cross Cutting Standards Issues– Key Application Development

• Focus on Transmission Applications and Integration with Distribution and Customers

• Initial Focus on Transmission Bus Load Model• Scope PAP 14 Against the Backdrop of the Following

– Other PAP work related to Transmission – Work taking place (or not taking place within

SDO’s)• Use Priority Process to Rescope

STRATEGY

PAPs related to PAP 14

7

12

8

17

13

11

93

16

Vehicles

Wind Distribution Automation

Storage

2

1

DNP/61850

Pricing

DR

Customer Data

PAP 14 “Breadth”

Phasors/Time

PAP 14 Scoping Criteria and Scoring System

• Applications Track– 1A Critical Applications Development– 1B Supports Cross Cutting Applications– 1C Provides Breadth to Complement Depth of Other PAPs– 1D Supports Applications not Covered by Others

• Key Standards Issues– 2A Complements SDO Work Underway– 2B Assists in Development of Key Interfaces Between

Standards/Application Domains– 2C Assists Harmonization/Integration/Unification– 2D Specifically Identified Priority in PAP Charter: Relay Settings– 2E Specifically Identified Priority in PAP Charter: Events

• 1A Critical Applications Development– Critical to SG:”5”….Not Critical to SG: “0”

• 1B Supports Cross Cutting Applications– Cuts Domain/Environments “5” No Cross: “0”

• 1C Provides Breadth to Complement Depth of Other PAPs– Breadth: “5” Narrowly focused “0”

• 1D Supports Applications not Covered by Others– No One Else Covering: “5”, Covered by Others “0”

APPLICATIONS TRACK SCORING

• 2A Complements SDO Work Underway– Complements “5” Duplicates SDO work: “0 “

• 2B Assists in Development of Key Interfaces Between Standards/Application Domains– Assists: “5”, Isolated “0”

• 2C Assists Harmonization/Integration/Unification– Assists in Stds Integration;”5” Stand alone: “0”

• 2D Specifically Identified Priorities in PAP Charter: Relay Settings

• 2E Specifically Identified Priorities in PAP Charter: Events

KEY STANDARDS ISSUES CRITERIA AND SCORING

Proposed Priority Process

• Finalize Initial List of Candidate Use Cases• Define Criteria for Prioritizing• Recruit and Send out directions to PAP 14 participants for

selecting• If you are interested in participating please send an email to

jhughes@epri.com

16

COMMUNICATIONS AND DISTRIBUTED COMPUTING INFRASTRUCTURE MUST BE ENABLING

Jump to Nokhum Presentation

USE CASES FOR THE SELF-HEALING GRID

n.markushevich@smartgridoperations.comwww.smartgridoperations.com

12/2/2010

ACTIVE DISTRIBUTION NETWORKS (ADN)HIGH PENETRATION OF:

– Load dependent on • Real-time pricing• Embedded DER• Demand Response• PEV• Technology• Other

– Large DER/ES/MG dependent on• Weather• Technology• Maintenance• Price• Volt/var control mode and

settings• Protection settings

– Load Shedding Remedial Action Schemes dependent on

• Operations of MG (connected – autonomous)

• Load behavior (see above)• Overlapping with other

schemes• Changing priorities• Pre-armed settings

– DMS applications dependent on • Objectives• Available tolerances• Available controls

AGGREGATED LOAD OF ADN AT TRANSMISSION BUSES• Significant deviations from conforming (typical, proportional) load shapes• Significantly changing load-to-voltage dependences due to

– Embedded DER– DER with Volt/Var control capabilities in different modes– DER/MG with voltage protection– Intermittent operations of DER– Changing combinations, mode of operations, and settings of voltage and var

controlling devices– Demand Response with different PF

• Significantly changing load-to-frequency dependences due to– Embedded DER– DER/MG with frequency protection– Intermittent operations of DER– Changing number of DER on-line– Different frequency control capabilities

Short-tem predictability (minutes)

ARCHITECTURALLY CRITICAL INFORMATION EXCHANGES FOR THE SHG

• SCADA data• PMU data• Data on the behavior of Active Distribution Networks under

normal and emergency conditions

AGGREGATION OF INFORMATION ON ADN IN TRANSMISSION BUS LOAD MODEL (TBLM)

• Aggregated models of – Distributed Energy Resources and their behavior under normal

and emergency conditions• Controllable and uncontrollable reactive power resources• Demand Response and its behavior• VVWO behavior• PEV performance• Aggregated MW and Mvar dependences on voltage • Aggregated MW and Mvar dependences on frequency (• Dispatchable real and reactive loads via:

– VVWO– Demand Response– DER control– Emergency Load Shedding

EXAMPLENEAR-REAL-TIME ANALYSIS OF POTENTIAL ISLANDING

PRE-ARMI

NG

OF

ISLANDIN

G REQ

UIRES

• Prediction of real power balance in the potential island (frequency)

• Prediction of reactive power balance in the potential island (voltage)– Islands are formed to minimize the load-generation

imbalance• Prediction of the reaction of the Active Distribution Network

(~ 20% of DER, Micro-grids, Demand Response, VVWO, etc.) Adaptive near-real-time analyses based on

Transmission model updatePMU dataReaction of the Active Distribution Network

Two-area load-rich potential island (before the separation)

DisconnectedConnected

G11 G12 G21 G22

P-jQ

Load 1 Load 2UFLS, UVLS

for Sub-Area 1

DER1/MG DER2/MG

UFLS, UVLSfor Sub-Area 2

Area 1 Area 2

Pt-jQt

VVWODR

Two-area load-rich island (after the separation)

DisconnectedConnected

G11 G12 G21 G22

Load 1 Load 2UFLS, UVLS

for Sub-Area 1

DER1/MG DER2 /MG

UFLS, UVLSfor Sub-Area 2

Area 1 Area 2

VVWODR

P-jQ

QUESTIONS TO BE ANSWERED BY THE ANALYSES OF POTENTIAL ISLANDING

• Is the load-generation imbalance manageable during the island situation?– Will DER separate due to frequency or voltage, or both – with or

without load?– Will the weak tie be overloaded?– Is the load shedding sufficient, etc.?– Are the priorities of load shedding adequate?– How will the situation develop during prolong islanding?– What is the latency and the possible contribution of Demand

Response and VVWO?– What is the risk (uncertainty) factor?

• What re-coordination of protection and RAS would be needed?

?? ?• What is the expected cold-load pickup?• What is the latency and possibilities of DER

resynchronization?• What should be the priorities of load restoration?

The TBLM should contain information that is needed to answer these questions.

Questions Continued

INFORMATION AND CONTROL FLOWS

T&G devices

Subst. LTC, Shunts, SVC

DMSDOMAVVWO

FLIREmerg.

apps

AMI

DER/ES/MG

DR

PEV

Load model Processor

Topology Processor

TBLM Processor

TBLM

Topology model

PMU

SCADA

EMSSECA

SCDPre-armRestora-

tion………

RAS

DSCADADataControl

Distribution domain

T&G domains

PRIORITY USE CASES FOR OPERATIONS OF SHG, ADDRESSING THE CROSS-CUTTING OVER DOMAINS • Creation and updates of Transmission Bus Load Model

• State Estimation• Contingency Analyses with prioritization based on PMU and

TBLM• Security Constrained Dispatch – for preventive measures• Pre-arming of Corrective Measures• Restoration after emergency

Nee

d to

use

PM

U a

nd T

BLM

THANK YOU!

• Need PAP 14 subgroup to help integrate prospective use cases from variety of sources and cull the list down for the priority tool

• Identify Sources of Transmission Operations Use Cases

• Categorize into Hierarchy• Populate Tool with Use Case Listings for Priorities• Forward Priority Tool to SDO’s, Consortia, and T&D

DEWG

USE CASE LIST AND TOOL COMPLETION STRATEGY

• PAP 14 Introduced• List from Transmission Bus Load Model• List from EPRI Intelligrid/ IKB• List from EPRI Harmonization Documents (on PAP 14

Twiki)• List from IEEE PSRC H2, C2, H5, H7• List from NASPI net• Possible List from PAP 13 (Need to Identify for Wide

Area Measurement and Control…Phasor based)

USE CASE LISTS

PAP 14 Introduced Use Cases• Fault Location• Automated Fault Analysis• Back-up protection• Protective relay application testing• State Estimation• Electronic Tagging

IEEE PES Power Systems Relay Committee (PSRC) H2 Use Cases

• Dynamic Settings based on Real-Time Conditions• Reclosing Supervision Based on Smart Grid Data• Conservation Voltage Reduction• Fault Location• Applications of Power Quality Data• Time Management (Local and Wide Area)• Applications of GOOSE• Distributed Energy Resources Protection• Load Shedding and Load Based Applications

H2 Applications for Smart Grid, Chair Mark Simon

Extra: SGIP Rosetta Stone Project Development

Ros

ett a Sto

ne

Bac

kgr

ou nd

• Background and Need– Several PAPs Working on Application Level Communications

(Semantics) within their respective application space– Several Standards Exist and In Development to codify semantics for

Smart Grid– Generic Need for Harmonization/Integration/Unification of

Standards for Application Level Communications– Need to avoid replication of work within SDOs working on PAPs

• Objectives– Evaluate Approaches and Methods to appropriately

Harmonize/Integrate/Unify Smart Grid Standards– Develop common methods and tools to H/I/U existing and

developing standards across different operating environments– Develop Contributions to SDOs and User Groups as Appropriate

Rosetta Stone Project In Development• Approach

– Identify Standards from PAP Requirements and documentation needing H/I/U

– Evaluate Prior Work related to Harmonization, Integration or Unification (i.e. IEC 61400-25 under TC88 has mappings to five other standards)

– Identify Key Related SDO Activity (i.e. IEC TC57 WG 19, Other)– Close Cooperation with SGAC Semantic Working Party– Investigate Methods to Integrate Standards as Appropriate

• Use of Unified Modeling Language, Use of OWL, • Development of XML Schema, Id Syntax and Structure and

Remaining Issues– Develop Recommendations for H/I/U development that can be applied by

respective PAP development work• Status: Initial Draft Statement of Work: Discussed in T&D DEWG, Tech

Champions. Next Draft…May develop under SGAC Semantics

PAP Relationships: SGIP SGAC Activities Continued

• Semantic Working Group– Whitepaper– Semantic Terms Paper– Technical Approach Development in Progress– http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/

SGIPSemanticModelSGAC• Security Working Group

– NISTIR Integration– PAP Specific Work Items

• PAP Development and Relationships Activity– Cross PAP Issues

Twiki:http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/CrossPAPIssues

– Cross PAP Dependency Matrix with Narratives– Some PAP Descriptions Contain PAP to PAP Relationship Narratives– Rosetta Stone Project Draft

• IKB Information Objects:– Applications Level Communications Integration– Currently Identifying Targeted Standards by PAP

• IKB Use Cases– Requirements Archiving by PAP

• Model Development

http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/InteroperabilityKnowledgeBase

Generic Standards Integration Harmonization IssuesTC57 Ontology

CIMOntology

IEC 61850Ontology

Equipment

Asset

Measurement

tSubstation

Substation

No Overlap or Conflict between Definitions: Model Association using UML

Possible Overlap or Conflict between Definitions: Model Association using OWL

Possible Conflict: Class Modeled in OWL

No Conflict: Class Modeled in UML

Data Attribute

Server

Logical Node

Proposed Methods to Integrate Standards

IEC 61968 / 61970

IEC 61850-7IEC 61850-6

Configuration Run Time

Generic Harmonization Strategy Development

OPERATIONS and MAINTENANCE ENVIRONMENT

SUBSTATION ENVIRONMENT

Field Device Comms I/F

Power System Model Server

Substation Configuration

Tool

OtherApplications

IED IED IED

Convertor

CIM XML

SCD File

OWLMapping

GID ServicesCIM XML

orGID

Services

CID Files

IEC 61850Services

Run-Time Configuration TimeSemantic Set-up

ICD Files

Modeling Difference For How Measurements are Associated with Topology

Conducting Equipment

Conducting Equipment

Conducting Equipment

Conducting Equipment

Conducting Equipment

CT1 CB1SW1

Measurement

IEC 61850

CIM