Download Revision 1

Power Play
Use the power of simulation to predict the future
Design presentation CS 410 –Black Team December 6th 2016
1
Table of contents
1.Power Play
2.Table of contents
3.Problem Statement
4.Problem Characteristics
5.Current Process Flow
6.Our Solution: Simulation-Based
Process Flow
7.Spark: Simulation Engine
8.Ignite: Web-Based Application
9.Major Functional Components
10.Solution Design
11.User Stories
12.Version Control
13.Hardware Requirements
14.Software Requirements
15.Agile Development
16.Work Breakdown Structure
17.Site Map
18.Risk Analysis: Customer
19.Risk Analysis: Technical (T1,T2)
20.Risk Analysis: Technical (T3,T4)
21.Main Game Flow
22.Graph Display
23.Load Scenario
24.Load R&D Data
25.Run Simulation
26.Power Plant Planning
27.Information Bar Display
28.Load Static Data
29.Q&A
30.Works cited
Design presentation CS 410 –Black Team December 6th 2016
2
Problem Statement
Design presentation CS 410 –Black Team December 6th 2016
3
• 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
4
Strategic Decision Making
Current Process Flow
Information from Various Departments within a Corporate
Infrastructure at the End of a Fiscal Year
Operational
Performance
Reliability
Challenges
Forecasted Information based on
Research and Development
Financial
Performance
Production
Efficiency
Annual Performance
Review
Annual Planning
Process
Performance
Documentation
Strategic Decision
Making
Observational
Period
Implementation of
Strategic Decision
Forecasted
Demands
Emerging
Technologies
Service
Generation Mix
Regulatory
Pressures
Examples of Key Decisions
 Maintenance of Current Assets
 Technological Investments
 Distribution & Transmission
Investments
 Cost Reduction
 End User Incentives
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*
5
Strategic Decision Making
Our Solution: System Process Flow
Real-World Decision Making Process can be Simulated
Power Play
User’s Past
Decisions and
Results Retrieve
User Information
Stored and
Retrieved
User Granted
Permission to
Access
Annual Performance
Review
Decision
Information Stored
Users’ Past Decisions
and Gameplay
Results
Gameplay
Moderators
Iterative Gameplay
Results Stored
Initial Scenario
Provided
Simulations Results Stored
Presented as Historical Data
Users
Registration and
Login
Annual Planning
Process
Forecasted
Information
Strategic Decision
Making
Implementation of
Decisions
Unit Commitment &
Capacity Expansion
Model
Algorithm-Based Platform
Provides Decision Options
Discrete Event
Simulation Model
*Simulated Forecast
Information
Forecast Information Provided
by External R&D Team
Examples of Forecast Information
 Energy Cost Forecast
 Technological Capital Cost
Forecast
 Demand Forecast
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
6
Strategic Decision Making
Spark: Simulation Engine
Real-World Decision Making Process can be Simulated
Dispatch and Power Flow
Simulation Model
Annual Performance
Review
Annual Planning
Process
Scenario Forecast
Information
Decision
Implementation
Strategic
Decision Making
Forecast Simulation
Model
Discrete Event
Simulation Model
Utility Company
*Dominion Power
Unit Commitment &
Capacity Expansion
Model
Forecast Information Provided
by External R&D Team
Examples of Forecast Information
 Energy Cost Forecast
 Technological Capital Cost
Forecast
 Demand Forecast
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
7
Strategic Decision Making
Ignite: Web-Based Application
Iterative Gameplay Process
Login Page
User Login
User Information
Stored in Database
Home Page
Logged In
Gameplay
Actions
Information
Review
User Information
Retrieved From
Database
Performance
Review
Forecast
Information
User
Registration
End Process
Log Out
Decision
Options
Password
Recovery
Implement
Decision
Gameplay Tour
Page
Home Page
View Previous
Decisions and
Results
Gameplay Pages
Design presentation CS 410 –Black Team December 6th 2016
Decision
Commitment
Spark Simulation Engine
Login
Authorization
Decisions Stored in
Database
Gameplay
Results
Results Stored in
Database
8
Major Functional Components
 Web-Based Front End to Interact
with the Gaming Platform
 SQL Server Pushes and Pulls
Game Variables to and from Front
Reporting
Player Information
End and Simulation Engine
 Players can Play on Mobile or PC
Simulation Engine
‘Spark’
Browser
Gameplay Information
Web Server
Web Page Front End
 Simulation Engine Models and
Simulates Power Plant Decision
Making Process
 Store and Present Reports and
Gaming Results
Outcomes Based on Gameplay
User devices
Design presentation CS 410 –Black Team December 6th 2016
Behaviors
9
Solution Design
Design presentation CS 410 –Black Team December 6th 2016
10
User Stories:
As an Analyst I would like to:
As an administrator I would like to:
As a player, I would like to:

view all player decision data

create and remove players

view data by event

retire a plant

change and set passwords

view data by region

refurbish a plant

reset collected data

view my data by type

build a new plant

create game scenarios for players

interact with the data

see resources available

have access to players game results

download the data

see environmental impact

notify players of updates

download the data by region

see potential earnings

download the data by date
Design presentation CS 410 –Black Team December 6th 2016
11
Hardware Requirements
Component
CPU socket
Memory (RAM)
Hard disks and
available storage
space
Minimum
Recommended*
1.4 GHz (64-bit
3.1 GHz (64-bit
processor) or faster for processor) or faster
single core
multi-core
1.3 GHz (64-bit
processor) or faster for
multi-core
2 GB
8 GB
160 GB hard disk with a
60 GB system partition
Design presentation CS 410 –Black Team December 6th 2016
12
Software Requirements
Design presentation CS 410 –Black Team December 6th 2016
13
Agile Development
Design presentation CS 410 –Black Team December 6th 2016
14
Work
Breakdown
Structure
Design presentation CS 410 –Black Team December 6th 2016
15
Site Map
Seen by all users
Locked by Role
Design presentation CS 410 –Black Team December 6th 2016
16
Risk Analysis
C1- Failure of Customer Adoption
C2- Failure of End User Adoption
T1- Interoperability
T2- Failure of End User Adoption
T3- Security Issues
T4- UI Issues
[Probability 3, Impact 5]
[Probability 1, Impact 5]
[Probability 3, Impact 3]
[Probability 1, Impact 4]
[Probability 2, Impact 3]
[Probability 4, Impact 3]
Design presentation CS 410 –Black Team December 6th 2016
17
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
18
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
19
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
20
Algorithms
Main Gameflow
Design presentation CS 410 –Black Team December 6th 2016
21
Algorithms
Graph display
Design presentation CS 410 –Black Team December 6th 2016
22
Algorithms
Loads R&D data
Design presentation CS 410 –Black Team December 6th 2016
23
Algorithms
Load Scenario
Design presentation CS 410 –Black Team December 6th 2016
24
Algorithms
Run Simulation
Design presentation CS 410 –Black Team December 6th 2016
25
Algorithms
Power plant planning
Design presentation CS 410 –Black Team December 6th 2016
26
Algorithms
Information Bar
Display
Design presentation CS 410 –Black Team November 9th 2016
27
Algorithms
Load Static Data
Design presentation CS 410 –Black Team December 6th 2016
28
Database
Schema
Users
Design presentation CS 410 –Black Team December 6th 2016
29
Database
Schema
Power Plants
Design presentation CS 410 –Black Team December 6th 2016
30
Database
Schema
Scenarios and
Actions
Design presentation CS 410 –Black Team December 6th 2016
31
Questions?
Design presentation CS 410 –Black Team December 6th 2016
32
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
33