AMI-Enterprise

1
AMI-Enterprise

• Systems Requirements Specification Team
• Status and Breakout Session

2
Topics

• Status Update
• SRS Draft v03 Highlights
• Breakout Session Topics

3
Status Plan

• SRS Draft v03 released on 04/08/09
• First complete draft
• Included comments/edits from SRS team members
• Plan
• Discuss and determine a few directional topics
  today
• Finalize scope and level of detail for version
  1.0
• Develop a plan and timeline for completion of
  version 1.0

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 AM
I-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
Breakout Session Topics

• General feedback on SRS v03
• Discussion topics
• The requirements versus architecture  there is a
  desire/recommendation to create an overall openSG
  reference architecture document, which contents
  from this document could be leveraged, as with
  other SRS documents in openSG TFs.  So we need to
  understand the openSG direction on this and how
  to manage that for this document going forward.
• Functional and technical requirements while
  functional requirements for integration services
  are clearly driven by business processes and use
  cases, the technical requirements will need to be
  flushed out in more detail.  We will discuss how
  the team can accomplish that with some
  prioritization.
• Team members and participation discuss team
  participation/commitment and working
  process/procedure to drive this to the point of
  ratification by utilities.

9

• 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