AMI Systems Design 1

Advanced
Metering
Infrastructure
Feb, 2011 Ismael Esteban Ossa

AMI
Systems Design

ieossa0969@gmail.com
IEO 2
METERING
Smart
Sub Metering
Person Licensed
CREG
Laws 142 A133.5
CCU
IEO
Source: IPCC 2007, figure (vs. 1990 level)
SUB METERING
Lecture
Accuracy
Security
Communication
Board
TOUmore
Standard
IEO
Proyect of Sub Metering
Products:
(5) ION 7550 ,
(2) Boards HDM from to16 meters PM750
(114) Boards HDM from to 8 meters PM750 or PM210
Software Continuum - TAC

HDM- High Density Metering
730 meters
PM210, PM750
IEO
Time Of Use

5
IEO
Framework Suggested

6
IEO 7
LOOP OF RESPONSIBILITY
IEO 8
IEC Committee 57
IEO 9
IEC TC 57 and WGs
IEO 10
System Design Goals
Develop requirements that anticipate customer needs and support
policy objectives through 2012
Develop an architecture framework leveraging leading industry
methodologies and principles that support AMI solution as a strategic
platform to enhance customer service and grid reliability
Use a systems engineering approach to conduct trade-off analysis
focused on the value of enabling scenarios in the AMI business case

Select designs and
technologies that mitigate the
risk of rapid technology and
functional obsolescence

As- is ( Today )
Incremental (1year )
Customer Experience
2014 ( 3-5 years )
10-15 years
(too unpredictable)
2014
IEO 11
Future-proofing AMI Solution
Given the varied pace of technology advancement in the
meter and communications industry the risk of technology
obsolesce to AMI is high
In order to manage this risk the AMI program focused on
the following:
Understanding the market and vendor solutions & technologies
Developing the layered architecture necessary to meet our
requirements, assess vendor offerings and understand any gaps
Developing strategies and technical points of view with an
emphasis on future-proofing AMI solution against the risk of rapid
technical obsolesce
Communicate with the industry to help increase the pace of
innovation and ensure basic architecture elements necessary for
future-proofing are available for implementation
IEO 12
Understanding Electric Residential Meter Technologies
2
nd
Generation vs. 3
rd
vs. 4
th
Generation difference in adoption of architecture based design
Solid State Gen2
Smart Meters Gen3
P
e
r
f
o
r
m
a
n
c
e

(
F
u
n
c
t
i
o
n
a
l

&

V
a
l
u
e
)

Time
2006 2008
SCE Technology Adoption Zones
2000 2010
$110
$65
2020
Smart Meters Gen4
IEO 13
Understanding Electric Meter Communication Technologies
Technology choices based on solving majority solution with an effective engineering economic
alternative while recognizing the rapid rate of communications alternatives
AMR
AMI
Broadband Application
for Advanced Metering
BPL v3
Muni WiFi
RF Canopy
WiMax
P
e
r
f
o
r
m
a
n
c
e

(
B
a
n
d
w
i
d
t
h
,

C
o
v
e
r
a
g
e

&

V
a
l
u
e
)

Time
Pervasive Customer
Broadband Access
2006 2008
SCE Technology Adoption Zone
2000 2010
BPL v2
BPL v1
PLC v2
RF Mesh
ERT
2020
SG
IEO 14
Developing SCEs AMI architecture
Systems Engineering approach
provides a method for
decomposing complex systems
into manageable elements using
Systems Thinking approach
AMI is a System of Systems
A collection of independent systems
organized to perform collaboratively to
achieve a purpose not achievable by
the individual systems
Systems Levels are iteratively
described in increasing levels of
detail as the AMI architecture
progresses to lower levels of
abstraction
IEO 15
AMI requirements-driven architecture perspectives
Use Cases & Business
Scenarios
Requirements
Information Needs
Technical capabilities required
to support uses of AMI
Component Architectures
Message Architecture
Reference Architecture
Open standards available to
support architecture
Vendor solutions and offerings
Enabling enterprise standards,
patterns & services
Development of conceptual, component & reference architectures has allowed us to examine AMI
from a number of architecture perspectives (Operational, System, Technical)
IEO 16
Conceptual Architecture Development Approach
Develop requirements
Functional
Non-functional
Understand Vendor
Capabilities
Develop a platform-
independent component
architecture
Understand candidate
standards
Understand the message
architecture necessary to
support the requirements
Map requirements to
enabling components
Understand gaps between
vendor offerings &
architecture needed to
support the requirements
This process was used to:
IEO 17
AMI Conceptual Component Diagram
Edge Data Center
Field Elements
Customer Premise
Data Center Aggregator
System Management Console
Meter Data Management System
Repeater
Distribution Automation Nodes
Neighborhood Aggregators
Premise Gateway
AMI Meter
Other Meters
Load Control Devices
In-home display
Building Management System
Programmable Communicating
Thermostat (PCT)
IEO 18
Electric Meter Communication Strategy
Technology choices need to balance standards, performance and cycle time
Reach for greater relative bandwidth (still in narrow range) for 2-way comms
Mitigate exposure to fast cycle technologies touching large number of
elements
Reliability and Security are significant issues
Commercial risk mitigation
Layered the network architecture to take advantage of the constantly evolving
communications landscape
IEO 19
AMI Meter & Device Strategies
1st Level: High level component
This layer provides a common
framework to understand scoping
boundaries and vendor offerings
2nd Level: Programmable elements
This layer includes a programmable layer that provides
capacity for remote deployment of additional capabilities to
adapt to changing customer needs and market conditions
3rd Level: Logical device layer
This layer is Including an event bus architecture and
shared resources which provides additional
flexibility and extensibility for the future
IEO 20
AMI overall systems strategies
Use the AMI Home Area Network (HAN) controller in the meter to
stimulate a robust eco-system of energy management products that
provide customers with new tools to manage their electricity usage and
allow SCE to develop new programs
Fast cycle technologies run the highest risk of obsolesce so we shall
be careful on how they are incorporated into the AMI solution
architecture
Design for a time when ubiquitous broadband exists across SCEs
service territory and understand how to leverage the technology for
AMI
Look for opportunities to extend AMI functionality with applications that
are aware of the entire network bus model including AMI elements in
the future. (outage management, distribution and procurement
optimizations, adaptive self-healing, etc.)
IEO 21
SCE AMI Technology Strategy Progress
System is designed to securely support customer energy choices
- TOU/CPP rates - 2008 T24 PCT - Solar metering
- Service automation - Plug-In Hybrids - 2011 T24 Ballasts
- RTP rates - Smart appliances - Home automation
- Cyber security

Systems open and flexible design is based on industry reference design principles
(DOEs Gridwise Architecture, EPRIs Intelligrid, OpenAMI and UtilityAMI)

Clean sheet requirements developed over the past 8 months have been vetted against
vendor product development plans and cost-benefit trade-off. Functional requirements
for meter, telecom and Meter Data Management System have been published.

Next generation meter products compatible with
our requirements are becoming available for
acceptance tests next month (Aug 2006)

One year has brought the future into our reach
SCE AMI Phase I selected as 2005-2006 Best
AMR Initiative in a North American IOU by
international utility peers. UPN-AMRA, Aug 9, 2006
IEO 22
AMI Conceptual Component Layers
2
nd
Level:
Future
Programmable
Configurable Layer
provides capacity for
remote deployment
of additional
capabilities to adapt
to changing customer
needs and market
conditions
IEO 23
AMI Conceptual Component Descriptions
3
rd
Level Component
Including a
bus architecture
and shared resources
provides additional
flexibility and
extensibility.

This platform
independent
Architecture is similar
to several vendor
solutions
under consideration
IEO 24
Security Framework Objectives
GUIDANCE and INSTRUCTION with regard to security system
design and architecture
Adaptive and extensible
Serve as a compass for current and future efforts
Clearly delineate priorities and objectives

Mechanism for SPECIFICATION, IMPLEMENTATION, and
INTEGRATION of AMI security systems into SCEs security
program and structure
Aligned to interface with corporate policy, procedure, and practices
Reference and re-use existing components wherever possible and practical
Only extend SCEs existing program for requirements specific to the AMI

Mechanism for continued MONITORING, MAINTENANCE,
EVOLUTION, and EXTENSION
Support steady-state operation as well as change and variation along two axes:
Definition and scope of the AMI
Definition and scope of the security framework itself

IEO 25
Security Framework Strategy & Tactics
Asset Identification
Threat Identification
Vulnerability Assessment
Risk Analysis
Risk Treatment
Cost / Benefit Analysis
Security
Domains
Policy
Protection
Profiles
TACTICS
IntelliGrid
Process,
Common
Criteria
IEO 26
Security Framework Deliverables
o GUIDANCE and INSTRUCTION with
regard to security system design and
architecture

o Mechanism for SPECIFICATION,
IMPLEMENTATION, and INTEGRATION
of AMI security systems into SCEs
security program and structure

o Mechanism for continued MONITORING,
MAINTENANCE, EVOLUTION, and
EXTENSION
Milestones
o Security Domains
o Identification
o Definition
o Risk Assessment
o Asset Identification
o Threat Identification
o Vulnerability Analysis
o Security Policy
o Guidance, Objectives
o Assets, Actions, & Auditing
o Specification
o Security Functionality
o Protection Profiles
IEO 27
Questions?
Many thanks for your kind attention!
IEO
Aditional

AMI Systems Design 1

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

AMI Systems Design 1

Transféré par

Droits d'auteur :

Formats disponibles

Advanced

Vous aimerez peut-être aussi