1 /1/17/2011

Architecture Developmentfor the Smart Grid

Mark Adamiak

GE Digital Energy

2 /1/17/2011

Mark’s Definition of the Smart Grid:• Finally implementing what was proposed more than 20 years ago…

• “Homeostatic Utility Control”, F.C. Schweppe et al, IEEE Transactions on Power Apparatus and Systems, Vol. PAS-99, Number 3, May 1980 - (Schweppe mentions five minute updates of prices)

• A New Measurement Technique for Tracking Voltage Phasors, Local System Frequency, and Rate of Change of Frequency – IEEE 1982 Summer Meeting

• Development and Pilot Demonstration of Hardware for an AEP System Test Program Relative to the Variable Spot Pricing of Electricity – American Power Conference – 1990.

• EPRI Distribution Automation Project – 1990.

• EPRI Electric Vehicle Program - 1978

3 /1/17/2011

Central GeneratingStation

Step-Up Transformer

DistributionSubstation

ReceivingStation

DistributionSubstation

DistributionSubstation

Commercial

Industrial Commercial

Gas Turbine

RecipEngine

Cogeneration

RecipEngine

Fuel cell

Micro-turbine

Flywheel

Residential

Photovoltaics

Batteries

Residential Data Concentrator

Control Center

Data network Users

2. Distributed Computing Infrastructure

1.Power Infrastructure

The Power System– in the beginning

Two Infrastructures must now be managed

4 /1/17/2011

Communication & Sensing Environments

5 /1/17/2011

Example: Environment 18:Customer to Electric Service Provider

ESPESP

Encompasses:• Distributed processing• Security• Data management

Typical applications:

• Automatic meter reading

• Monitoring / control of DER

• Demand response

• Real Time Pricing

Requirements:

• Large volumes of data

• Frequent re-configuration

• Large number of nodes

• Broadcast of information

6 /1/17/2011

Narratives & Use Cases of Power System OperationsFunctional Requirements

Distributed Information – Common Object

Models and Services

Potential TechnicalSolutions and Best Practices

High LevelArchitectural

Concepts

System Designers submit queries based on specific functional

requirements

Domain and Architecture Experts analyze and extract

distributed information requirements

Technology Experts link distributed information requirements to

potential technology solutions and best practices

IntelliGrid and StakeholderDomain Experts

Provide System Designer with potential solutions and best

practices

Domain Experts provide expert descriptions of

functional requirements

Architecture Experts establish high level

architectural conceptsIntelliGrid & StakeholderArchitecture Experts

Architecture Experts describe potential solutions, based on high level concepts, their capabilities, advantages, and disadvantages,

(including certain legacy technologies)

Power Engineers

Power Engineers review relevant Use Cases

Provide Power Engineer with

functional requirements

System Designers

Architecture Development Process

7 /1/17/2011

Requirements Capture Template• Function name• Description – by Domain Expert• Actors (stakeholder) / roles• Activities / Services• Quality of Service

– Availability– Performance– Volume of Information– Security

• Current implementation status• Interaction requirements• Sequence of Functioning (Data Flow)

8 /1/17/2011

Standards are Good!

“Standards are great. Everyone should have one.”

– Bob Metcalfe, Co-inventor of Ethernet

but Fewer of the Right Standards are Better

9 /1/17/2011

Smart Grid Interoperability Standards Framework –Ver 1.0 - Final - Now 75 Standards defined by NIST

Protocol & ApplicationAMI-SEC System Security Requirements

ANSI C12.19/MC1219 – Revenue Metering

BACnet ANSI ASHRAE 135-2008/ISO 16484-5 – Building Automation

DNP3 - Substation and feeder device automation

IEC 60870-6 / TASE.2 - Inter-control center communications

IEC 61850 - Utility automation and protection

IEC 61968/61970 - Application level energy management system interfaces

IEC 62351 Parts 1-8 - Information security for power system control operations

IEEE C37.118 - Phasor measurement unit (PMU)communications

10 /1/17/2011

Technology Independent Architecture

Discoverable Information

Models

Common Services/Interfaces *

Composite Applications Data Mining

and AnalysisPortalsPortalsComposite Composite Data Mining

Local Legacy Applications

Wholesale and Retail Market

Operations

Utility Field

Devices

Networking and

Computer Hardware

* Includes: security, object naming,

platform services (transactions, time,

etc.)

** Includes: domain objects, se curity

objects, managed device objects, etc.

Databases, Directories, and Registries

Databases, Directories, and Registries

Web Pages & Documents

Web Pages & Documents

Other File Types (e.g. email, etc.)Other File Types (e.g. email, etc.)

* Includes: security, object naming,

platform services (transactions, time,

etc.)

** Includes: domain objects, security

objects, managed device objects, etc.

11 /1/17/2011

Optical Current Sensor Development

• Better Accuracy• Large dynamic range• No saturation• Able to measure DC• Can be installed over the existing infrastructure

12 /1/17/2011

Temperature and Pressurevia Fiber Bragg

13 /1/17/2011

Needs: New Coating Technology

14 /1/17/2011

The Work Ahead• Harmonize the existing common services, information models, and interfaces

– Work in progress between 61850 & CIM– Security profiles being proposed

• Integrate security, systems, network management, and technical development• Identify the Gaps and work to fill-in

– IEEE 1588 for Utilities– Mapping of Synchrophasors into 61850– Optical Sensing

Architecture development is a process– not an end point