140 likes | 146 Views
This document outlines the purpose, scope, and approach of the AMI-ENT Requirements Specification (SRS) for integrating applications within the utility enterprise. It focuses on interoperability, guiding principles, reference architecture, and architecture views across business, application, data, and technical domains.
E N D
SG Systems Systems Requirements Specification Approach Overview
Topics • Purpose and Scope • Interoperability Philosophy • Documentation Approach • Guiding Principles • Reference Architecture • Architecture Views • Business • Application • Data • Technical
Purpose and Scope • The purpose of the SRS is to provide the architecture vision and requirements to serve as the “rules of engagement” for how vendors and utilities could implement recommended requirements and design specifications. • Main focus in this presentation is on the AMI-ENT • AMI-Ent is about how applications within the utility enterprise are to be integrated and composed to support AMI related business processes and functions. • It deals with inter-application related business functions and stops at the boundaries of applications and the edge of utility enterprise. • Edge applications are those applications that communicate with networks and devices in the field, as well as those that communicate with other businesses or enterprises (generally defined as third parties).
Documentation Approach • According to The Open Group, there are four architecture domains that are commonly accepted as subsets of an overall enterprise architecture, all of which TOGAF is designed to support: • The Business Architecture defines the business strategy, governance, organization, and key business processes. • The Data Architecture describes the structure of an organization's logical and physical data assets and data management resources. • The Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization. • The Technology Architecture describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc.
Guiding Principles [mjz1]{AEP} Something should be said about companies' tendency to overestimate their differentiators. After all, a utility-driven process is the default and results in everybody rolling their own. [mjz2]{AEP} Standards that are almost, but not quite, good enough may be worse than no standard at all. The key is knowing HOW to build upon a standard (and knowing how to build a standard that can be built upon). This is something that a lot of people think is obvious and easy. It's...not. [mjz3]{AEP} The phrase "common information model" is here used in its plain-English sense, but it is also the name of a body of standards, inviting confusion.
Business View (AMI) Business Processes: B1 - Meter Reading B2 - Remote Connect/Disconnect B3 - Detect Theft B4 - Contract Meter Reading Consolidated Demand Response and Load Control C1 - Price Based DR and Voluntary Load Control C2 - Customer Views Energy Data C3 - Prepayment C4 - Third Parties Use AMI Network D2 - Distribution Automation D3 - Distributed Generation D4 - Outage Location and Restoration G1 - Gas System Measurement G2 - Gas System Planning G3 - Gas System Corrosion Control I1 - AMI System Installation I2 - AMI System Life-cycle Management I3 - Utility Updates AMI System S1 - AMI System Recovery
Contact Info. • Here is the link to the AMI-ENT SRS v1.0 document (under SRS folder): http://osgug.ucaiug.org/sgsystems/OpenAMIEnt/Shared%20Documents/Forms/AllItems.aspx • If you have comments and/or wish to join and contribute to the SRS effort, please contact Joe Zhou at jzhou@xtensible.net