Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek

Overview Purpose: Develop Use Cases and Functional Requirements for Demand Response Systems Focus on immediate SDG&E requirements for California State PUC filing Attempt to generalize this work across the industry to extent practicable Introduced the effort to UCA in Knoxville last quarter Group has been meeting weekly since late Oct 2008; two face to face meetings in November and December respectively. Timeframe – October 2008 Use case development begins – February2009 Use case development complete – March 2009 Functional requirements complete

January 2009 Status Review On-going review of existing Public Domain Use Case Models Selected Enterprise Architect as our tool kit for use case development – Developed Business Process Model – Defined Users – Developing Use Cases Gradually achieving consensus among participants as reflected in the following slides

Illustration

Timing

Business Process Model analysis Business Process Model The Business Process Model describes both the behavior and the information flows within an organization or system. As a model of business activity, it captures the significant events, inputs, resources, processing and outputs associated with relevant business processes. Business Context + Strategies + Stakeholders + Topology Business Objects + datastore + report1 Business Workflows + Process + Event1 + Input + Result The Business Context package contains models of all involved stakeholders, mission statements, business goals and physical structure of the business "as-is". The Business Objects package contains a domain model of all objects of interest and their respective data. The Workflows package documents business processes, drawing on stakeholders, structures and objects defined in the Context and Object packages showing how these work together to provide fundamental business activities.

DR Business Process Model

Actors uc Actors Distributed Energy Resource Control (DERC) Metering Agent Settlement Agent Billing Agent ISODistributor Small-Scale Merchant Generator Large C/I Customer and Co-Generator Aggregator Customer ResidentialCustomer CommercialCustomer Industrial Customer A system that collects detailed information about customer loads and customer response patterns. It also maintains information regarding the number of times a customer has complied in a given time period vs the compliance requirements of the tariff applicable to that customer. This information is brought together for the user so that the user can see what probable load is available to be curtailed in total and at various points in the network. The system will also receive and process requests for curtailment and will balance the requests across subscribers «role» «generalization» «role»

Use Case Model uc Use Case Model The Use Case model is a catalogue of system functionality described using UML Use Cases. Each Use Case represents a single, repeatable interaction that a user or "actor" experiences when using the system. A Use Case typically includes one or more "scenarios" which describe the interactions that go on between the Actor and the System, and documents the results and exceptions that occur from the user's perspective. Use Cases may include other Use Cases as part of a larger pattern of interaction and may also be extended by other use cases to handle exceptional conditions Actors are the users of the system being modeled. Each Actor will have a well- defined role, and in the context of that role have useful interactions with the system. A person may perform the role of more than one Actor, although they will only assume one role during one use case interaction. An Actor role may be performed by a non-human system, such as another computer program. Actors + Aggregator + Billing Agent + Customer + Customer Commercial + Customer Industrial + Customer Residential + Distributor + Energy Service Provider + ISO + Large C/I Customer and Co-Generator + Metering Agent + Settlement Agent + Small-Scale Merchant Generator + Mission Statement + Entity1 Primary Use Cases + Actor1 + ISO + Manage Demand for Mainenance Purpose + Manage Demand in respond to Pricing Signal + Curtail Demand + Decrease Supply + Demand Bid + Demand Response + Direct Load Control + Dynamic Pricing + Increase Supply + Manage Aggregator + Manage Demand + Manage Demand for Economic Effect + Manage Demand Side Program + Manage Demand through Direct Load Control + Manage DR Customer + Manage DR Program + Manage Load + Manage Market Operations + Manage Supplier + Manage Supply + Manage Supply through Direct Control + Manage Supply through Price Signal + Provision Demand Response Equipment + Trading This package contains use cases which define how an Actor will interact with the proposed system. Each interaction may be specified using scenarios, sequence diagrams, communication diagrams and other dynamic diagrams or textual descriptions which together how the system when viewed as a "black-box" interacts with a user.