AMI-Enterprise

1
AMI-Enterprise

• Systems Requirements Specification Team
• Status and Breakout Session

2
Topics

• Status Plan Update
• SRS Draft v04 Highlights
• OpenADE Initial Framework Highlights
• Breakout Session Topics

3
Status Plan

• Status
• SRS Draft v03 released on 04/08/09, it was the
  first complete draft that included comments/edits
  from SRS team members.
• Feedback to date mainly points to the need for
  inclusion of security related requirements,
  updated to SRS Draft v04.
• Started to work on an initial framework for
  systems requirements and architecture to support
  ADE.
• Plan
• Discuss level of detail needed to include
  security requirements and how that is going to
  impact the architecture design and patterns.
• Get consensus on SRS v1.0 scope and ratification
  voting process.
• Discuss plan to start the ADE and ADR related
  systems requirements development.

4
SRS Table of Content
Contents 1. Introduction 1.1 Purpose 1.2 Scope 1.3
Acronyms and Abbreviations 1.4 External
Considerations and References 1.5 Document
Overview 2. Architecture Overview 2.1 Architecture
Vision 2.2 Architecture Guiding
Principles 2.3 Architectural Considerations 2.4
Security Considerations 2.5 AMI-ENT Reference
Model 3. AMI-ENT Systems Architecture 3.1 AMI-ENT
Business Architecture View 3.1.1 Integration
Requirements Framework 3.1.2 Business
Architecture Components 3.2 Integration
Requirements Specification 3.2.1 Functional
Requirements Business Processes 3.2.2
Functional Requirements Integration
Services 3.2.3 Technical Requirements
Integration Services
3.3 AMI-ENT Application Architecture
View 3.4 AMI-ENT Data Architecture View 3.4.1
Meter Reading and Event View 3.4.2 Asset and
Customer Information View 3.4.3 End Device
Control View 3.4.4 Outage Record and Work
Order 3.5 AMI-ENT Technical Architecture
View 3.5.1 Service Patterns 3.5.2 Intra-system
vs. Inter-system 3.5.3 Service Aggregation 3.5.4
Master Data Management 3.5.5 Complex Event
Processing 3.5.6 Governance 4. Appendices 4.1 Ter
ms and Definitions
5
Reference Model
6
Services Inventory View
7
System of Systems
Source Accelerating Utility Industry Standards
Adoption
8
The Changing Dynamics of Energy Services
With the advent of Smart Grid, consumer oriented
companies such as Google will want to provide
bundled and value-added energy management
services to the mass market. Such services can
only be enabled if utilities can provide
necessary data in an automated fashion.
9
What is ADE?

• The automated delivery or availability of
  customer usage data on a daily basis in a
  specified format to customers and/or authorized
  3rd parties.
• It is automated data exchange interface that does
  not require further action once configured.
• It will be secure, monitored and managed.
• Once the infrastructure is established, it could
  support future data exchange needs with third
  parties.

10
ADE Basic Use Cases
11
ADE Conceptual Architecture
Secure, managed and automated data exchange.
12
Breakout Session Topics

• General feedback on SRS v04
• Discussion topics
• The security requirements and their impact on
  architecture  
• how do we leverage AMI-SEC specification?
• How and how much do we need to include the
  security requirements into the current SRS
  version.
• What are utilities doing with regard to security
  implementation for integration? Assuming Web
  Services is a predominate approach for
  integration, what WS security standards are
  utilities using today?
• ADE systems requirements ADE systems
  requirements and architecture work will begin and
  we welcome participation.
• ADR systems requirements how do we collaborate
  with OpenADR?

13

• If you have comments and/or wish to join and
  contribute to the AMI-ENT SRS effort,
• please contact Joe Zhou
• at jzhou_at_xtensible.net