Tommorrow’s Secure, Intelligent, interoperable Metering and Customer Communications Infrastructure
Smart Metering West CoastAugust 18, 2008EPRI Palo Alto, CA
Joseph Hughes
Sr. Technical Manager
2© 2007 Electric Power Research Institute, Inc. All rights reserved.
Architecture and Communications Infrastructure Presentation Overview
• Goals:– Present Status and Issues Related to
Infrastructure Development For the Future Energy System
– Propose Approaches to Standards and Architecture Development
3© 2007 Electric Power Research Institute, Inc. All rights reserved.
Drivers For Open Standards and Architecture Development
Open Systems and Standards Development
Capital Cost Reductions
Life Cycle Cost Reductions
Systems Engineering
Methods
Robust Designs Enabling
Infrastructures
Shared Infrastructures
Bundled and New Applications
Communications Asset Utilization
Increase ValueDecrease Costs
4© 2007 Electric Power Research Institute, Inc. All rights reserved.
External Corporations
Corporate UtilityMarket
participants
Energy System Comprises Many Distributed Computing “Environments”
Industry Architecture Requires Establishing Key Points of Interoperability/Interworkability
5© 2007 Electric Power Research Institute, Inc. All rights reserved.
• Some Standards in use… but not enough use
Where’s the Architecture?
Today…
Communication Systems
Limited Visibility across the system
Little integration between IT and Field Automation
Islands of automation
• Older difficult to maintain protocols
Proprietary “Solutions”
• Little or no enterprise level integration
• Patchwork of “legacy” SystemsNo Customer Integration
6© 2007 Electric Power Research Institute, Inc. All rights reserved.
Industry Architecture Driver: Two Infrastructures Must be Managed
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
7© 2007 Electric Power Research Institute, Inc. All rights reserved.
Advanced Metering and Customer Communications Infrastructure Cuts Across Industries…Plan for it
Energy efficiency and demand response must be architected correctly to
integrate across industries and utility operations
EfficientBuildingSystems
UtilityCommunications
Integrated T&D
DynamicSystemsControl
DataManagement
DistributionOperation
Protection
DistributedGeneration& Storage
-EV and Hybrids
IntegrationLife-Cycle Management
End- UseDevices
HVAC ControlAdvancedMetering
Customer IntegrationDynamic Ops
Secure Comm Renewable Integration
PV Integration
8© 2007 Electric Power Research Institute, Inc. All rights reserved.
Introduction to Communications, Interoperability and Distributed Computing
Network CommunicationsInformation
2 - Registers
6 - LoadProfile
7 - Events
MeterInc. Model 12b2 Phase, 120VAC, 200AUCAUCAUCAUCAUCAUCAUCAUCA
TM
C12.22 Device
Address 135.35.5.2
End Device (Meter)
0 - Identification......
...
...
Meter Data
Message
“Letter”
ANSI Standard Communications
“Envelope”
Revenue MeterData Packet
9© 2007 Electric Power Research Institute, Inc. All rights reserved.
What is A Common Language?
3. Communications Message “Object”
1. Physical Communications
Media…
Intelligent-Communicating Remote Device
(Meter)
MeterInc. Model 12b2 Phase,
120VAC, 200A
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
2. Communications
“Envelope”
“Master Station”’Computer Communications
Interfaces
10© 2007 Electric Power Research Institute, Inc. All rights reserved.
Simplified View on Layered Communications…
MeterInc. Model 12b2 Phase,
120VAC, 200A
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
“Master Station”’Computer
MeterInc. Model 12b2 Phase,
120VAC, 200A
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
MeterInc. Model 12b2 Phase,
120VAC, 200A
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
Brand X
Brand Y
Brand Z
“Wireless”
“Fiber Optic”
“Wired”
11© 2007 Electric Power Research Institute, Inc. All rights reserved.
Security Architecture Must Encompass Varied Systems and Security Domains
DataUUUUUUUU
CCCCCCCC
AAAAAAAA
TM
“Consistent Implementation of Security Policies”
Brand X
Brand Y
Brand Z
Data
Data
“Wireless”
“Fiber Optic”
“Wired”
Encryption
Intrusion Detection,
Access Controls
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
Monitoring,
Other
Forensics,
Other…
12© 2007 Electric Power Research Institute, Inc. All rights reserved.
Customer Communications (AMI) Scope: Integrated Wide Area and Local Area Networks
13© 2007 Electric Power Research Institute, Inc. All rights reserved.
Key Standards Organizations Involved in the Development of Industry Level Infrastructure
ISO IECInternationalstandards-developing organizations
National Organizations
Trade, technical,and government
Consortia anduser groups
JTC 1
ANSI(US) EIA/CEMA IEEEASHRAE
SAE
UCAInternational
Zigbee Alliance
AEIC MeterGroup
BACnet™Users
ITU
IEC 61970/68CIM Users
IEC 61850Users Open AMI
AHAM
Utility AMI Open HAN
BACnet™Mfrs
JTC 1 WG 25
*Representative Sample
ASHRAESSPC 135 UIWG
ANSI C12Series
EPRI IWG
ISA
IETF
CENELEC
Other Projects
NIST
RD&D
ProjectsEPRI ProjectsCEC Projects DOD ProjectsDOE Projects
14© 2007 Electric Power Research Institute, Inc. All rights reserved.
Standards alone are not enough for interoperable product development...
Standards Developed by Formal Standards Organizations (SDO’s)
Interoperability Agreements
from Consortia
End-Users Desired Interoperability (Plug and Work)
Universe of networking and distributed computing op tions
Users Agreements
Management and Security (Future)
IEC 61850,61970
ANSI C12
15© 2007 Electric Power Research Institute, Inc. All rights reserved.
Interoperability..the devil is in the details…
Data Semantics
Data Type
Data Precision
Data Sign
Data Encoding
Data Syntax
Significant Bits
Some options and possible combinations for a five digit “meter read”
kWh, pulses, Wh, kVarh, kW, Demand, etc…
Cumulative, direct read, ad hoc, other…
floating point, integer, alphanumeric, boolean, enumeration, real, character type, strong type .
8bit, 16bit, 32bit, 64bit
Unsigned, signed
ASN.1, XDR, IDL, Other
Big endian, little endian
16© 2007 Electric Power Research Institute, Inc. All rights reserved.
Methods: Use Systems Engineering and Architecture Development… Requirements Elicitation First
Reference Requirements
Sources
Initial Ideas and Concepts
Project Team Develop Initial
Drafts
Draft Requirements and “Use Cases”
Scenarios of vision and
future operations functions
Iterate
Iterate
Reviews
Stakeholders Review
17© 2007 Electric Power Research Institute, Inc. All rights reserved.
Recommended Approaches: Develop Functional and Non-Functional Requirements Together
• Applications: – System must support the requirements coming from
power engineering needs• Systems and Network Management:
– Installed communications networks and intelligent equipment must be able to be observed and maintained
• Security:– System must include adherence to security policies
and include system “hardening” as well as managing residual risk
18© 2007 Electric Power Research Institute, Inc. All rights reserved.
General “Methods” Approach: Requirements Driven Process
Industry Policies
(In Progress)
Technical Requirements In
Progress
19© 2007 Electric Power Research Institute, Inc. All rights reserved.
Architecture
Development
Applications and Infrastructure Development Needs t o Occur in Parallel: Designs are Critical to Architec ture
Requirements
Analyses Designs
Implement
Bench/Develop
Field Test
Small/Develop
Field Test
Large/Demo
Commercial
Rollout
Energy Specific
Standards
User Groups
ManufacturerManufacturer
ManufacturerManufacturer
Individual
Project work
Interoperable Equipment
Standards Based
Technology
Adoption
Refinement
20© 2007 Electric Power Research Institute, Inc. All rights reserved.
User Groups
Reference D
esigns
Standards
Architecture Development
Ingredients for Industry-Level Interoperable and Managed Systems Development
Three Legged Stool: For Interoperable Products
2) Involved User Group: Interoperability Agreements, Labeling, Testing, Tissues Resolution
3) Reference implementations and Designs: Focused Development Projects, Developer Tools, Standards Implementations and test implementations, Open Source
1) Open Mature standards: Protocols, test schemas, object models
21© 2007 Electric Power Research Institute, Inc. All rights reserved.
A Sample of Industry Infrastructure work that has taken place and needs to be built upon…
IEC 61970/61968 for Enterprise “IT” Integration
IEC 61850 for Real-Time Field Automation, DER Integration
IEEE P37.118
For Phasor Measurement
Units
ASHRAE/ANSI 135 for Building Automation
ISA for Industrial ANSI C12
Revenue Metering
SAE For PHEVs
22© 2007 Electric Power Research Institute, Inc. All rights reserved.
What is an Industry Level Architecture?
Architecture: The Structure of Components, their relationships, and the principles and guidelines governing their design and
evolution over time*.
*DoD Integrated Architecture Panel, based on IEEE Std 610.12
23© 2007 Electric Power Research Institute, Inc. All rights reserved.
Architecture Vision
• Uses Consistent Policies Across Operating Domains• Integrates a Wide Variety of Networks• Integrates a Wide Variety of Physical Media• Enables Interoperability among Intelligent equipment• Uses a Carefully Integrated Set of Standards from
Different Industries• Standards are Supported by Effective User Groups• Industry Requirements are Shared across the industry• Interoperable Equipment is available Across the Industry• Conformance and Interoperability Testing widely adopted• Standardized Notation and Systems Engineering is
Widely Used to Specify and Manage Systems
24© 2007 Electric Power Research Institute, Inc. All rights reserved.
Integration Across Both Information Technology (IT) and Field Equipment (“Real-Time”) is Required
Customer IntegrationDistribution
automation
Substation
automation
Transmission Ops
WAMAC
PP integration
DER integration
Po
wer
Sys
tem
Res
ou
rces
Rea
l Tim
e
Ap
plic
atio
ns
Co
mm
un
icat
ion
Infr
astr
uct
ure
Dat
a
Man
agem
ent
En
terp
rise
Ap
plic
atio
ns
Power procurement
Market operations
Regional Transmission
Operator
Distribution Control Center External corporations
DER integration
25© 2007 Electric Power Research Institute, Inc. All rights reserved.
Develop/Harmonize Common Meter Data Models for Integration of MDMS with Field Operations
OMSCIS
Customer Communications
DistributionAutomation
“Service Oriented Architecture”
ProprietaryMetering A
AM/FM/GIS
ANSI/IEC Metering “Field
Operations”
Meter Data Management
IEC 61970/61968 Common Information Model (CIM) Enterprise Application Integration
Proprietary
Metering B
Meter Master Station
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
R&D Needed: Integrate Across Standards=> Common Mete r Data Model
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
UUUUUUUU
CCCCCCCC
AAAAAAAA
TM UUUUUUUU
CCCCCCCC
AAAAAAAA
TM
26© 2007 Electric Power Research Institute, Inc. All rights reserved.
ISAAHAM
Application Language Strategy for Working with Industry: Mutual Respect For Domain Knowledge
AHAM
ANSI
C12 Series
Electric
ISAASHRAE
SSPC 135DMTFSAE
Automotive Industry
IndustrialAppliancesBuildings & HVAC
Computers
Meters
LBL DRASIEEE
PES
IEC
TC 57 Utility AMI
Open AMI
AMI SEC
Zigbee
Power Industry
Open HAN
ASHRAE
Customer Communications
Focused
R&DDMTFSAE
Electric
Develops Into
Composite
27© 2007 Electric Power Research Institute, Inc. All rights reserved.
Needed Steps: Work to Be Done
7:Application
6:Presentation
5: Session
4:Transport
3: Network
2: Data Link
1: Physical
Application (Central)
1: Physical
2: Data Link
3: Network
4:Transport
5: Session
6:Presentation
7:Application
Application (Remote)Application Level Device
Models/Objects and Harmonize with CIM
Develop Common
Approaches Adopt as
Appropriate
=>Investigate Issues with
Management & Maturity
“Physical Media”=> Understand
and Use as Appropriate
“Middle Stack”
28© 2007 Electric Power Research Institute, Inc. All rights reserved.
Moving Forward: A Ten Step Program
1. Work toward consistent industry level policies for customer communications infrastructure
2. Use Systems Engineering and Architecture Development Methods andTools
3. Use a “Requirements Driven” approach to technology adoption and development
4. Work toward an industry level strategic architecture model and development pathway in key areas such as customer interface
5. Do not do “one off” or custom projects that are not on a strategic open systems architecture pathway
6. Do not “wait” for standards: Use, adopt, further develop, contribute to and procure to key industry level standards
7. Understand where the technology “gaps” and “overlaps” are and work on collaborative solutions
8. Adopt technology from other industries only as appropriate making sure it meets energy/power industry requirements
9. Develop energy specific standards where needed: i.e. applications level language
10. Recognize where collaborative R&D is needed and actively participate
29© 2007 Electric Power Research Institute, Inc. All rights reserved.
Contact Information
• Visit epri.com for information on publicly available documents from IntelliGrid Architecture
• Industry Use Cases and Templates for Requirements
Joe Hughes, Sr. Technical Manager Electric Power Research [email protected] 855 8586
