1 / 5

AMI-Enterprise

This document provides an overview of the AMI-ENT Use Case Team's progress, current status, and future plans. It includes information on the purpose of the team, meeting schedule, timeframe, and breakout session topics. Additionally, it highlights the incorporation of security requirements and the use of secure coding best practices.

rafaeld
Download Presentation

AMI-Enterprise

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. AMI-Enterprise Use Case Team Status Kay Stefferud Columbus OH, July 14 2009, Hosted by AEP

  2. Overview • Purpose: Develop Use Cases and Functional Requirements for AMI-ENT • Group has been meeting regularly since late Oct 2008 • Face to face meetings in November, December 2008, and January, April, July 2009 Timeframe • October 2008 Use case development begins • February 2009 Use case development complete • March 2009 Functional requirements complete • April 2009 Present use cases and functional requirements • July 2009 Propose ratification of version 1.0 • ? 2010 Complete AMI ENT use case unification

  3. Use Case Examples The DR solution shall manage demand resources.  The DR solution shall communicate with organizations that manage the grid. The DR solution shall provide for participation of independent third party electric distributors.

  4. Breakout Session Topics • Outage Management use cases • Business Process Models (BPM) • Existing use case status • Diagram using EA • Incorporate recent comments • Arizona Public Service Company • Scope AMI ENT use cases • Plans to incorporate existing use cases • Stakeholders for EA model • Incorporation of security requirements • Barriers to use and incorporation

  5. Security Requirements • Defined by AMI-SEC group • Included by reference in AMI-ENT requirements • Concern: How to implement security • Leverage industry group expertise (CERT, SANS, CISSP) • Use Secure Coding best practices (threat model with mitigations, secure coding standards, secure design patterns, training/certification, etc.) Secure Coding UCA 2009.pptx • Advanced: Critical Information Protection, Anti-Tamper

More Related