1. Comp 410 Client Meeting 11-5-11

2. Outline Design Concept Implementation on Azure Revised Use Cases Revised GUI Mockup Demo Timeline Clarifications

3. Design Concept Andrew Emil

4. Design Concept Goals Flexible framework able to simulate wide variety of models Provide ability to run simulations of arbitrary complexity and size Allow for easy visualization and editing of models

5. Solution: Module-Based Modeling Each module can be defined through 1.Compositing 2.Code Composite-based Modules: – Made up of collection of interconnected sub-modules – Each sub-module can itself be a composite Code-based Modules: – Can contain formulas of arbitrary complexity Modules can have any number of inputs and outputs

6. Module Advantages: Complexity Modules allow for entire simulation to be broken into small pieces Simulation framework can maintain arbitrary number of modules for each simulation No need for centralized computing, work can be spread out as desired

7. Module Advantages: Flexibility Module definitions allow for varied internal behavior of modules Arbitrary connectivity relates modules to each other Any module may connect to any other module with compatible inputs and outputs

8. Module Advantages: Elasticity Encapsulation of work means that simulations are just a collection of modules and connections between them Easy to set up, no need for lots of resources to be ready on hand at all times TODO - Can allocate system resources appropriately?

9. Module Advantages: Usability Concept of different levels of view High level understanding of a model is achievable without having to see details Easy to follow logic from high level to low level Encapsulation of sections of model – Can change one aspect of model without having to change others

10. Example of a Basic Model Supply-demand curve: Supply: power production capacity Demand: power demanded Feedback drives system towards equilibrium Simple consumer-producer relationship

11. Module Representation Producer Outputs: -Energy Supply -Energy price -Pollution Consumer Inputs: -Energy Supply -Energy price -Pollution Regulation Environmental Inputs: -Pollution from Producer Environmental Outputs: -Regulation for Consumer Producer module requires: -Initial price of energy -Initial supply of energy -Slope of initial supply curve Producer Inputs: -Demand for energy Environmental module requires: -Strength of regulation Consumer module requires: -Demand curve slope -Price of energy Consumer Outputs: -Energy demand At the start of the simulation:

12. Implementation on Azure Weibo He

13. Why Microsoft Azure? Scalability Cost-Performance Stability

14. Revised Use Cases Elizabeth Fudge

15. Basic User Typical member of public May have no knowledge of energy industry No authentication required “Free” to CFAE

16. Basic User Use Case Visits CFAE website, goes to simulation page Selects a predefined model with plan Views simulation results Views plan Views model

17. Authenticated User Has enough domain knowledge to make basic edits to model and/or plan Authenticates with credentials supplied by CFAE Costs money for each set of basic edits they save and for each simulation they run Paid for by user or by CFAE

18. Authenticated User Use Cases All use cases for Basic User and … Logs in Selects a predefined model with plan Changes numerical parameters of the model and/or plan May save numerical parameters for future use Runs simulation Views new simulation results

19. Expert Authenticated User Has enough domain knowledge to make advanced edits to model and/or plan Authenticates with credentials supplied by CFAE Costs money for each model they edit and save and for each simulation they run Paid for by user or by CFAE

20. Expert Authenticated User Use Cases All uses cases for Authenticated User and … Selects a predefined model with plan, or one of their own saved models with plan Uploads code and adds to model Runs simulation Views new simulation results

21. Clarification: Publishing Models/ Plans Would be confusing for Basic User to see all saved models/plans CFAE may want to change models/plans which are visible to Basic User Could have “publish” option for authenticated users, would have to be approved by CFAE Could have “publish” option for only some authenticated users (CFAE staff)

22. Clarification: Worst Case Plan Is worst case plan no change in current behavior? Or absolutely no actions taken? Ex., coal power plant goes offline from old age – is it replaced with another coal plant or not replaced at all?

23. Revised GUI Mockups Jesus Cortez

24. Mockup Overview

26. UI Walkthrough: Basic Use Case

29. UI Walkthrough: Authenticated Use Case

34. Demo Robert Brockman