GE - Energy Connections Powerflow Wireframe Challenge

Welcome to the GE - Energy Connections Powerflow Wireframe Challenge! In this challenge, we are looking for your concepts, ideas and wireframe solutions to help plan out our new and improved Network Model Manager (NMM) Application.

At GE we have Power System Engineers that monitor, manage and analyze power flow at a broad scale through an existing system of tools and software. We would like to take the workflow and use case concepts and work to create a new and improved Power Systems Engineer experience within a single application.

This wireframe challenge is focused on mapping out the potential Power Systems Engineer user experience (from beginning to end) as it relates to creating and analyzing energy models.

We want you to focus on the workflow and to bring simple (creative) solutions to how this application should work. At the end of this wireframe challenge, we are looking to have a solution that allows us to understand from a high level how we can start to improve the Power Engineer experience.

~
Additional GE Challenge Rules:
- Please refer to the attached GE Official Rules applicable to this challenge.
- To the extent there is any conflict between these Official Rules and additional Topcoder Terms and Conditions of Use referenced off the Website, these Official Rules govern.
- Winners from this challenge need print, sign and send back to us the IP Rights document from GE before eligible for the prizes.

Round 1

Submit initial wireframe concepts for client feedback
(What would we like to see by the Checkpoint)
1) Manage Workspace
2) Import Data
3) Run Applications
4) Connectivity Model

 

Round 2

Final Wireframes with Checkpoint feedback included
- Any Checkpoint feedback from Round 1

Overview:
The Network Model Manager (NMM) is an application which allows power systems engineers to analyze data representing an electrical network. Users can import data, run calculations, and analyze and export results.

User:
The user of this application is a power systems engineer who analyzes transmission network models. He may be modeling an existing real-world model to validate that it works before pushing it to production. He may also be looking ahead to a future addition to the network, running analysis on the hypothetical model to validate that the proposed change is acceptable.

Design Problem
We have a legacy system that current lacks a great user experience. We want to explore a better Engineer experience where they are able to quickly analyze network models and validate or troubleshoot issues.

We are looking for your wireframe concepts to help us plan the potential of this application and platform. Key things to think about is how the Power Engineer will need to access and analyze the different items of data. Think of the problem and work through the potential experience. Make sure to use modern user interface patterns and techniques. This process can become complex as different Engineers will be modeling different parts… so everything needs to be validated before it goes to production.

Current Workflow:
Please see Use Case Diagram

1. Workspace Management
All data import and analysis must be done within a workspace. The user must see a list of workspaces, be able to create new ones, duplicate workspaces, delete workspaces, and select one to work in.

1.1 Select Existing Workspace
The user wants to see a list of existing workspaces and select one from it.

Requirements: 
- List of existing workspaces
- Selection of a single workspace

1.2 Add Workspace
The user wants to create a new workspace.

Requirements: 
- Ability to create a new workspace and give it a name.

1.3 Delete Workspace
The user wants to delete an existing workspace.

Requirements: 
- Confirmation of deletion or ability to undo

1.4 Duplicate Workspace
The user wants to take an existing workspace and create a copy. 

Requirements: 
- Ability to select existing workspace, copy it, and give the resulting copy a name.

2. DATA Import
The user wants to import a file or, more likely, a set of files which will build his model. Some files are dependent on other files. 

File properties:
- Name
- File Type
- Timestamp
- Dependencies
- Supersedes 
- Description

File Types: 
- The following are examples of file types: EQ-BD, EQ, SSH, TP. 
- We may assume the user is familiar with what these mean and which type he wants.

Dependency: 
A file which “comes with” another file. Dependencies can be and often are “nested,” meaning that a file is dependent on another file which is dependent on yet another file, and so on.

Example: A user selects file A1 with dependencies B1 and C1. File B1 also has dependencies: B2 and, B3. Therefore, when selecting A1 the user must be able to see that it has 4 dependencies: B1, B2, B3, and C1.

Supersedes: 
- Another list of files, just like dependencies. We may assume the user knows what this list means.

Description: 
- Text field with a description of the file.

Timestamp: 
- A field which indicates the applicability of the data to a particular time / day / date. 

2.1 Find a File
The user wants to browse the repository configured in the server and select a file to begin with. 

Requirements: 
- Browse a file structure
- See, filter on, and search the following file properties:
- Name
- File type
- Time or time range
- Description text
- See the following file properties:
- Dependencies (and how they are “nested” (see Dependency above))
- Supersedes 

2.2 Select/Deselect a File’s Dependencies
Once the user has found a file and selected it, all the “Dependency” files should also be selected. However, the user has the ability to override that recommendation and select/deselect the ones he wants.

Requirements:
- See all dependent files and how they are “nested” (see Dependency above)
- When file is selected, all dependencies are also selected by default
- Deselect files which he does not want to include, including all subsequent ones which are “nested” under this file

2.3 Import All Selected Files
The user wants to Import the full list of selected files.

2.4 Add More files
At any point after the first import, the user can go back and select more files for import. However, once imported, files cannot be removed. This is because the data is “merged” upon import. This cannot be undone. In order to remove a file, the user will have to start over with a new workspace.

Requirements:
- Add more data files to existing set

3. Run Applications
There is a set of power systems applications available to the user which he can run on the imported data. Each set comes with a set of parameters the user can edit before running the application.

3.1 Run Powerflow
The user wants to run the Powerflow application on the imported data.

Requirements:
- Run Powerflow 
- Ability to edit a large set of parameters if there are problems as part of the analysis. The user initially starts with the default set of the parameters and if there are problems as a part of analysis steps he / she may tweak this as an iterative process.  

3.2 Run Topology
The user wants to run the Topology application on the imported data.

Requirements:
- Ability to edit the following parameters:
• Minimum # of busses in a group to consider the group as a viable electric island
- Run Topology

3.3 Run Contingency Analysis
The user wants to run the Contingency Analysis (CA) application on the imported data. Note the Contingency Analysis application is unique because it will run all the other applications as well. In order to run CA, everything else (Powerflow + Topology) will automatically run in the background as well.

Requirements:
- Run Contingency Analysis.
- Ability to edit a large set of parameters if there are problems as part of the analysis. The user initially starts with the default set of the parameters and if there are problems as a part of analysis steps he / she may tweak this as an iterative process.  

4. Analyze Results
The user wants to have an overview of the results of the applications and be able to drill down into more details. 

4.1 See High-Level Results
The user wants to see a high-level result of whatever Application(s) have ran. 
The following high-level results are possible:

Powerflow
- Converged 
- Not Converged
- Island summary: Details of each electrical island with information on number generating units, loads, shunt devices, lines transformers, stations, etc. (essentially the Island displays but only showing the number of elements). Total MW reserve, Total generation, total load for each island.
- Abnormal Voltage summary: The location (buses not Geographical location) where the voltage was computed to be higher than the allowed limit or lower than the allowed low limit.
- Violations: List of outputs generated by powerflow which summarizes the problems (or violations) in the network. 

Topology
- Ran to completion
- The number of buses in each electrical island with information on number generating units, loads, shunt devices, lines transformers, stations, etc. (essentially the Island displays but only showing the number of elements). It would be worthwhile to also show the reserve capacity of each island such as MW reserve, MVAR reserve. 

Contingency Analysis 
Contingency analysis is basically a what-if study on multiple contingencies. It repeatedly runs the powerflow and analyzes the results for each powerflow execution for each contingency and ranks the analysis results 
- Violations – similar to powerflow results but with associated contingency which created these violations
- Abnormal contingencies – Contingency which causes Island or loss of generation or loss of load etc. 

4.2 See Detailed Results
The user wants to drill further into the details of the results. 

The following displays are available:
Common Network Model information
- Data for different devices as tabular or tree view displays

Powerflow
- Iteration summary result with display navigation capability to the tabular displays. 
- Violations summary result with display navigation capability to the tabular displays. 
- Expert user display with more control over which part of the algorithm to be re-executed. 
- Display showing the log of the execution of the powerflow analysis

Topology
- Island information and a network topology diagram (buses display) with display navigation to other network tabulars. 

Contingency Analysis
- Contingency violations displays with display navigations to tabular displays and other displays mentioned above. 
- Display showing the log of the execution of the contingency analysis with a filter based on contingencies. 

5. Export Results
5.1 Export Results
The user wants to export the results of his work.

Requirements:
- Export the solution data in the CIM format based on parameters such as:
- Specific profile
- Filtering based on MAS
- Binary or XML format
- Export the solution data in different formats such as PSSE, PSLF, IEEE
- Export the solution as-is in binary format so that it can be persist (Save)

Potential Screens and Interactions:
- Focus on modern design patterns and interactions (ex. drag and drop)

Workspace Management
Review the Workspace Management use case
- What is the potential for this area of the application? How will a user manage this?
- What will the user see as part of their workspace?
- What is the flow from selecting a workspace into importing data?
- What modern application experience might apply here?

Data Import Flow
Review Data Import use case
- Ability to upload XML files (multiple files)
- Need a good UI to select files 
- Before running the Power Flow Analysis is should detect if the file is the correct format
- Each File has additional metadata that is presented
- This potentially could work similar to a wizard process? Other patterns?
- If there are issues in the model the information needs to go back to modeler or model owner
- Issues found should allow for capturing of notes, screen caps, etc.
- This process is like baking cookies… you can add more items but you cannot remove them once they are mixed/merged within.

Run Applications
Review the Run Applications use case
- How does the Engineer interact with the different applications?
- How is the Engineer able to edit the parameters based on the application?
- Once the Engineer makes their edits and runs the application how do they analyze the results?

Analyze/Detailed Results Views
Review the Analyze Results use case

Export Results
Review the Export Results use case

Connectivity Model 
- The Engineer should be able to see a graphic view of the model
- The Engineer is able to click into the graphic view/zoom and analyze information
- The idea is the graphic view helps the user visualize the connections
- View network connectivity as well as devices that are not connected to the network
- Engineer can see issues like lines of service
- Modern UI/UX can animate or allow visualization of this information
- Possible split screen information to analyze connectivity and the bus detail

Target Audience:
- Power Engineers

Wireframe Expectations:
- You should create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The application must be very easy to use and intuitive. Keep that in mind when creating your solution for the layout and flow information.
- You MUST cover all requirements mentioned in challenge details.

Branding Guidelines:
- Create your wireframe for responsive (desktop focus)
- Minimum width 1024px with height adjusting accordingly.

NOTE: You are welcome to add additional screens or combine some of these screens if you feel it will improve the user experience. We are open to your creative ideas around how to plan this platform.

Learn Axure:
- New to Axure? Here are some quick tutorials to help you get started.
- http://www.axure.com/learn

Judging Criteria:
- User Experience of the application/portal/dashboard/workspace
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow

Submission & Source Files:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File:
Wireframes should be built in HTML or Axure. The resulting files are not critical in this Challenge. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.

Source Files:
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.

Final Fixes:
As part of the final fixes phase, you may be asked to modify content or user click paths.