BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the "GE - Future of Air & Surface System Management Software Wireframe Challenge".

In this challenge we are looking for you to take a series of concepts and ideas generated from a workshop and start to merge, expand upon, and wireframe out the best overall user experience to create a cohesive single piece of software/ product design.

As a reminder, as a party to Topcoder’s Competition Confidentiality Agreement, which covers all Confidential Information provided in this challenge, including the name of the client, the goal of the challenge, and any non-public information provided to assist in this challenge.

Good luck and let us know any questions in the forum.
 

Round 1

Checkpoint Submission Requirements
Initial GE - Future of Air & Surface System Management Software Wireframe
Note: Submit as much application features as you can for our review.

Round 2

Final Submission Requirements
Final GE - Future of Air & Surface System Management Software Wireframe
Note: Address Checkpoint Feedback for the Final Round Submission
Challenge Description
Topcoder's client, GE Aviation, ran a multi-day workshop with their client to discover the key pain points with the current system and process, and identify possible solutions and ideas to solve those pain points. We are looking to the Topcoder community to take the outputs of the workshop, along with the user persona's, pain points, and additional requirements, and wireframe out the best possible experience. We are looking for you to take the workshop concepts and ideas and starts to roll them into a usable set of tools and a single piece of software that start to solve the problems.

What is the product?
The next generation of Air and Surface System Management Software delivers quality intelligence for decision making. The system captures, curates, crafts, and displays accurate real-time data, data trends, recommendations, and predictions based on advanced analytics; helping the users make informed and effective decisions based on their roles.

Here’s how it works. The system connects to all operational relevant data bases, weather, air traffic, airports and airport networks, FAA, crew personnel, etc. The product is adaptable and customizable delivering the information and trends appropriately to the users’ roles. From deep insights about a tactical operation to full-picture airport network capacity, the product allows the user to easily glance, drill down to get detail information to estimate the disruption impacts, prepare the plan to handle the foreseeable disruption, and recovery time and resource lost due the disruptions.

Core Competency
Serve up the right information at the right time to help users avoid disruption in air and surface operations

Client Input Document
The client has created a robust and extremely informative document that outlines their process, user persona, pain points, and their concepts/ ideas coming out of the workshop. This document will serve as your main source of input of this challenge.

The document is broken into 2 main sections that explore 2 different sets of concepts and ideas. However, both sets of concepts all have an underlying theme of "Disruption Prediction and Management". It is important that you completely read the client document to understand the entire scope of this challenge.

Problem Statement
How do you meet all the needs of the user, make it easy for them to zoom in and out, look forward in time, AND show them the right information to act proactively, not reactively.

What is presented under "Screen Requirements" in the Challenges Details are a series of concepts and ideas. We are looking for you to take the best ideas and concepts, expand upon them with any additional ideas and thoughts, and integrate them into a single toolset and application.

Screen Size
Desktop: 1440px(w) by 900px(h)
- Minimal scrolling of the entire screen

Included Documents
Client Input Document: https://drive.google.com/file/d/0B6kvOdxpqnKMY3AzNUd4XzducVk/view?usp=sharing

Screen Requirements
It's best to refer the Client Input Document, as this will have the most detailed and expanded information. We've outlined the general idea and concepts below, but they all follow the theme of "Disruption Prediction and Management".

Wireframe your vision of the end product based on the following ideas, concepts, and pieces of functionality. You do not need to include every idea/ concept. Choose the ones that make the most sense for the users and will compliment and complete the entire product.

Group 1). Proactive Situational Awareness
The below concepts are all focused around predicting or identifying situations/ issues before they happen and bringing them to the ATCs (Air Traffic Control) attention sooner. This allows them to be proactive instead of reactive.

Concept 1: The Constraint Manager
- Knowing ahead of time when there might be delays at the gate or when the path in/out could benefit how traffic is sequenced at the station.

Concept 2: Disruption Manager
- Disruptions come in all shapes and sizes. It’s the bane of every airline’s existence. When they hit, the operation has to recover as quickly as possible so as not to affect all the flights in the network and downstream.

Concept 3: Surface Manager
- If disruptions could be predicted, they will have much less of an impact on the airline and ultimately the passenger’s experience.

Group 2). Monitor, Calculate Impact of Possible Actions, & Solve
While this is focused on the ATC Specialist and his/her constituents, the same ideas of predicting station, gate, crew constraints, and disruptions resonated around the same issues Group 1 outlines above. This allows us to continue to develop the capability to deliver more wholistic visibility into surface data to provide more robust options for people like the ATC Specialist. Ability to predict when a Ground Delay Program (GDP) will occur due to various factors, giving the airline time to plan ahead

Concept 4: Predictive and Responsive
- Real-time data allows ATC specialists to monitor their airport effectively and make accurate plans

Concept 5: Disruption Prediction
- When a disruption is predicted, all data is a click away about that disruption, allowing the ATC specialist to take action to help solve the issue.

Concept 6: Collaborative Solutions
- Collaboration across the entire airline team to facilitate an agreed upon plan. Each team member is aware of the situation and the decisions allowing for faster responses and resolutions.

Group 3). Gamified Solution
Translates the ATC specialists workflow into a system using game mechanics. Allowing the user a prioritized a macro-to-micro level view to tackle high-value problems as they occur.

Concept 7: Network Prioritization
- Literal translation of how the ATC specialist chooses to analyze and address issues within the operation—tackling highest prioritized issues each hour as they arise.

Concept 8: Smartboard Prioritization
- Takes the painstaking process of zooming in and out of airports, fleets, and flights by aggregating all the addressable issues by your choice of priority criteria. Monitoring the entire operation just got easier.

Concept 9: Disruption Prediction
- The disruption manager provides a look- ahead prediction of potential delays and disruptions. From in-flight conflicts to surface constraints, the optimizer will deliver alternate routes and procedures to help you manage conflicts more efficiently.
- Could be combined with Concept 5 to create a single tool

Group 4). Unified Cockpit
ATC Specialists have challenging work stations. There are multiple machines and multiple keyboards, mice, and logins. The workflows and tools are scattered. Most of the decisions require the users to manually gather information and analyze. Unified Cockpit streamlines the workflow and aggregates all the needed functionalities the users need in one place.

Concept 10: Flight Data + Capacity
- Display unified flight and airport capacity data from FSM, ESM, and PFSM. The information is streamlined and consistent to keep all the parties involved on the same page.

Concept 11: Unified Forecast Maps
- The map displays the necessary predictive information such as, flight, routes, weather, disruption, etc. The user can “play” the forecast data in loops to analyze the disruption patterns and find solutions.

Concept 12: Find Opportunities to Recover
- The new system is constantly looking for opportunities to reduce time and to prepare for foreseeable disruptions. The system summarizes flights and opportunities into simple 5-star ratings while calculate when is the best time to act to take full advantage of the opportunity.

Concept 13: Keeping Track of Team Efforts
- The system encourages users to collaborate efficiently. All users have one common space to communicate, share information, assets, map, and directions

Target Audience
- Airline Traffic Control (ATC) Specialist
- There are robust persona details in the Client Input Doc
 
Judging Criteria
Your submission will be judged based on the product success criterion:
- User experience and information architecture
- The overall experience of the application/ toolset
- Expanding upon and creating unique features for the provided concepts
- Visual-driven, clear, concise, and meaningful data display
- Easy to navigate and gather information to make decision
- Keep dynamic collaboration between–ATC, FAA, operation personnel, crews, local airport, airport networks, airlines–seamless
- Adaptable and customizable
- Trustworthy Recommendations

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 Plain HTML/CSS/JS or you can generate from Axure application. 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.

 

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2017 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure
  • Sketch

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30058372