Power Play Use the power of simulation to predict the future Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Table of contents Power Play Table of contents Problem Statement Problem Characteristics Current Process Flow Our Solution: Simulation-Based Process Flow Spark: Simulation Engine Ignite: Web-Based Application Major Functional Components Solution Design User Stories Version Control Hardware Requirements Software Requirements Agile Development Work Breakdown Structure Site Map Risk Analysis: Customer Risk Analysis: Technical (T1,T2) Risk Analysis: Technical (T3,T4) Main Game Flow Graph Display Load Scenario Load R&D Data Run Simulation Power Plant Planning Information Bar Display Load Static Data Q&A Works cited Double column Slide numbers No blue Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Problem Statement Utility companies need an approach for strategically analyzed decision making within defined geographic regions based upon predefined scenarios. Design presentation CS 410 –Black Team December 6th 2016

Problem Characteristics Decisions are made in response to events affecting regional power plants. Results of decisions take years to materialize Adjusting decisions a reactive, instead of proactive process Misinformed decisions cost time and money Problem Characteristics Design presentation CS 410 –Black Team December 6th 2016

Strategic Decision Making Current Process Flow Information from Various Departments within a Corporate Infrastructure at the End of a Fiscal Year Forecasted Information based on Research and Development Operational Performance Financial Performance Forecasted Demands Emerging Technologies Annual Planning Process Annual Performance Review Reliability Challenges Production Efficiency Service Generation Mix Regulatory Pressures Examples of Key Decisions Maintenance of Current Assets Technological Investments Distribution & Transmission Investments Cost Reduction End User Incentives Strategic Decision Making Performance Documentation Observational Period Implementation of Strategic Decision Reference: Strategies& (2015) Time Consuming & Detrimental to Company’s Performance and System Infrastructure Design presentation CS 410 –Black Team December 6th 2016 Note: Decisions Process that Occurs Outside of a Company’s Annual Planning Process not Included*

Strategic Decision Making Our Solution: System Process Flow Real-World Decision Making Process can be Simulated Power Play Users Registration and Login User’s Past Decisions and Results Retrieve User Granted Permission to Access Annual Performance Review Forecasted Information Annual Planning Process User Information Stored and Retrieved Decision Information Stored Strategic Decision Making Implementation of Decisions Unit Commitment & Capacity Expansion Model *Simulated Forecast Information Users’ Past Decisions and Gameplay Results Iterative Gameplay Results Stored Simulations Results Stored Presented as Historical Data Forecast Information Provided by External R&D Team Algorithm-Based Platform Provides Decision Options Examples of Forecast Information Energy Cost Forecast Technological Capital Cost Forecast Demand Forecast Gameplay Moderators Initial Scenario Provided Discrete Event Simulation Model Dispatch and Power Flow Simulation Model Modifications to the Gameplay Scenarios Design presentation CS 410 –Black Team December 6th 2016 *Note: Yellow – Spark Simulation Engine; Red – Game Administrator

Strategic Decision Making Spark: Simulation Engine Real-World Decision Making Process can be Simulated Dispatch and Power Flow Simulation Model Annual Performance Review Scenario Forecast Information Annual Planning Process Discrete Event Simulation Model Decision Implementation Strategic Decision Making Forecast Simulation Model Forecast Information Provided by External R&D Team Examples of Forecast Information Energy Cost Forecast Technological Capital Cost Forecast Demand Forecast Unit Commitment & Capacity Expansion Model Utility Company *Dominion Power Algorithm-Based Platform Provides Decision Options Modifications to the Gameplay Scenarios Design presentation CS 410 –Black Team December 6th 2016 *Note: Yellow – Spark Simulation Engine; Red – Game Administrator

Strategic Decision Making Ignite: Web-Based Application Iterative Gameplay Process Login Page Login Authorization Home Page Logged In Gameplay Actions Information Review Performance Review User Login User Information Retrieved From Database User Information Stored in Database Forecast Information User Registration End Process Log Out Decision Options Spark Simulation Engine Password Recovery Implement Decision Decision Commitment Gameplay Tour Page Decisions Stored in Database View Previous Decisions and Results Gameplay Results Results Stored in Database Home Page Gameplay Pages Design presentation CS 410 –Black Team December 6th 2016

Major Functional Components Web-Based Front End to Interact with the Gaming Platform SQL Server Pushes and Pulls Game Variables to and from Front End and Simulation Engine Players can Play on Mobile or PC Browser Simulation Engine Models and Simulates Power Plant Decision Making Process Store and Present Reports and Outcomes Based on Gameplay Behaviors Player Information Reporting Simulation Engine ‘Spark’ Gameplay Information Web Server Web Page Front End Gaming Results User devices Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Solution Design Scenario based simulation engine Customizable simulations Web Front end Different user experiences for users, administrators, and analysts User profiles with detailed gameplay history and achievements Immersive visuals help to engage the user Reporting Interface Download reporting based on game data. Data visualization using Flask Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 User Stories: As an Analyst I would like to: view all player decision data view data by event view data by region view my data by type interact with the data download the data download the data by region download the data by date As an administrator I would like to: create and remove players change and set passwords reset collected data create game scenarios for players have access to players game results notify players of updates As a player, I would like to: retire a plant     refurbish a plant     build a new plant     see resources available     see environmental impact     see potential earnings Design presentation CS 410 –Black Team December 6th 2016

Hardware Requirements 100 Simultaneous users 10,000 – 20,000 monthly page views. Modest hardware requirements. Component Minimum Recommended* CPU socket 1.4 GHz (64-bit processor) or faster for single core 1.3 GHz (64-bit processor) or faster for multi-core 3.1 GHz (64-bit processor) or faster multi-core Memory (RAM) 2 GB 8 GB Hard disks and available storage space 160 GB hard disk with a 60 GB system partition Design presentation CS 410 –Black Team December 6th 2016

Software Requirements MongoDB - https://www.mongodb.com/ Flask Web Framework - http://flask.pocoo.org/ Microsoft Windows Server OS - https://www.microsoft.com/en-us/windows Microsoft Internet Information Services - https://www.iis.net/ Various open source frameworks – HTML, CSS, Javascript, Python 3 Documentation: Pydocs Unit Testing: Selenium, J Unit Version Control:Git Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Agile Development Adapt to change. Iterative development cycles. User feedback. Prioritize wanted product features. Encourage collaboration. Design presentation CS 410 –Black Team December 6th 2016

Work Breakdown Structure Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Site Map Seen by all users Locked by Role Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Risk Analysis C1- Failure of Customer Adoption [Probability 3, Impact 5] C2- Failure of End User Adoption [Probability 1, Impact 5] T1- Interoperability [Probability 3, Impact 3] T2- Failure of End User Adoption [Probability 1, Impact 4] T3- Security Issues [Probability 2, Impact 3] T4- UI Issues [Probability 4, Impact 3] Design presentation CS 410 –Black Team December 6th 2016

Risk Analysis- Customer C1- Failure of Customer Adoption [Probability 3, Impact 5] Description: Description: The preferred customers don't like the idea and never use this product Mitigation: Market the game as a possible education tool or work implemented training tool C2- Failure of End User Adoption [Probability 1, Impact 5] Description: There is not enough end-users willing to play the game, leading to little data collection. Mitigation: Customers, such as professors, require students use as a class assignment. Game play will include exciting scenarios and graphics to engage players. Design presentation CS 410 –Black Team December 6th 2016

Risk Analysis-Technical T1- Interoperability [Probability 3, Impact 3] Description: Ignite will not work together properly with all or some aspects of spark causing crashes, missing functionality or erroneous data. Mitigation: Having pre-loaded or hardcoded data T2- Failure of End User Adoption [Probability 1, Impact 4] Description: There is not enough end-users willing to play the game, leading to little data collection. Game becomes unpredictably popular straining server resources and robustness of code. Mitigation: Ensure code is robust enough to run well under heavy load by using extensive unit testing. Ensure we can easily and quickly migrate the project and associated databases to more robust hardware, or use scalable hosting such as Amazon Web Services. Design presentation CS 410 –Black Team December 6th 2016

Risk Analysis- Technical T3- Security Issues [Probability 2, Impact 3] Description: Vulnerabilities in database could cause loss of company data and user information. Mitigation: Secure Username and Password using standard practices. Power play will not collect any personally identifiable customer information or non public proprietary company information. Ensure power play is hosted on a server that is not shared. T4- UI Issues [Probability 4, Impact 3] Description: UI is too complex for the end users to understand Mitigation: Test the UI internally and to select users for feedback Design presentation CS 410 –Black Team December 6th 2016

Algorithms Main Gameflow Design presentation CS 410 –Black Team December 6th 2016

Algorithms Graph display Design presentation CS 410 –Black Team December 6th 2016

Algorithms Loads R&D data Design presentation CS 410 –Black Team December 6th 2016

Algorithms Load Scenario Design presentation CS 410 –Black Team December 6th 2016

Algorithms Run Simulation Design presentation CS 410 –Black Team December 6th 2016

Algorithms Power plant planning Design presentation CS 410 –Black Team December 6th 2016

Algorithms Information Bar Display Design presentation CS 410 –Black Team November 9th 2016

Algorithms Load Static Data Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Database Schema Users Design presentation CS 410 –Black Team December 6th 2016

Database Schema Power Plants Design presentation CS 410 –Black Team December 6th 2016

Database Schema Scenarios and Actions Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Questions? Design presentation CS 410 –Black Team December 6th 2016

Design presentation CS 410 –Black Team December 6th 2016 Works Cited “Agile Manifesto." Web. 29 November. 2016. <http://agilemanifesto.org/>. MongoDB - https://www.mongodb.com/ Flask Web Framework - http://flask.pocoo.org/ Microsoft Windows Server OS - https://www.microsoft.com/en-us/windows Microsoft Internet Information Services - https://www.iis.net/ Design presentation CS 410 –Black Team December 6th 2016