Challenge Summary
Welcome to the "GET - Rapid UX - Positive Train Control Design Concepts Challenge"! We are looking for your help in creating UI/UX design concepts for our Positive Train Control (PTC) application. This application allows users the ability to view the overall health of a train, details about train failures and the ability to diagnose issues.
What is a GET "Rapid UX Challenge"?
GE Transportation is excited to include the Topcoder Design Community within their design process. The GET (GE Transportation) Rapid UX Challenge is leveraging ideas from our famous RUX challenges and integrating it into how the GE team would like to rapidly create concepts for their design workshops and customers. This challenge has a specific format that we are looking to repeat in future challenges.
The GET "Rapid UX Challenges" provides you with an opportunity to showcase your design concepts and user experience (UI/UX) design skills to one of the largest companies in the world!
Rapid UX Challenge Format
- Challenge starts: Thursday 5 pm EST
- GE is available on Friday for Q&A (get your questions in early!)
- Rolling Checkpoint is Monday morning 7 am EST
- The GE Design team has scheduled time on Monday to review and workshop with your design concepts.
- The GE Design team will provide Checkpoint feedback by end of day Monday.
- Final Designs are due next Thursday 7 am EST.
Note: You do not need to have any design challenge experience to join this challenge - Just jump in and give it a try! Make sure to follow the challenge details, the challenge forum and ask questions.
Challenge Details
The goal of this challenge is to take the provided design problem, analyze the user experience and provide design concepts and visual ideas on how the application might look and work!
Design Problem
In today’s world, locomotive troubleshooting personnel do not have an easy way to view overall health of a train, details about a specific train failure, or the ability to diagnose those failures. Furthermore, the current solution does not offer an intuitive way to assign those issues to the appropriate party for failure mitigation. This application is intended to solve those specific needs and pain points.
We are offering 5 Prize Placements
1) 1st Placement: $1700
2) 2nd Placement: $850
3) 3rd Placement: $350
4) 4th Placement: $200
5) 5th Placement: $100
- Plus 5 placements for Rolling Checkpoint prizes @ $50 each!
Note: Important Rolling Checkpoint Details
- GE Team and adroc will be available on Friday, and Monday-Thursday for questions. (Get your questions in early!)
- Fajar will be available Saturday/Sunday for questions
- You must watch the Forum for your feedback!
*All initial qualifying checkpoint submissions will win $50 (5 Placements)
Challenge Documents
- PTC_Designers_Documentation_V1.pdf
- Wireframes
User Persona's
- Help Desk Persona.png
PTC Storyboard Flow
- Storyboard (Flow).png
User: Help Desk Agent
0) We need help! Our train has stopped...
- Train #238 is traveling along and then stops dead on the tracks for some reason. The crew sees that a PTC "enforcement" has taken place. They check everything they can to see if they can solve the problem but end up having no real option except to call the help desk and ask for assistance.
1) What Train are you guys on?
- The train crew calls the help desk and provide their train number to the help desk agent exits from watching cat videos and proceeds to search for their specific train number so he can find information that might pertain to what is causing the issue.
2.1) OK, I'm pulling your info up...
- Upon searching, the help desk agent finds the train using the PTC app and pulls up an overview page that displays a lot of helpful information about the overall health of the train, it's history, railroad assets around the location of the train, as well as other information.
2.2) I found the problem!
- The application makes it easy to find out what's wrong with the train system by automatically surfacing failures or errors on the screen first. The agent sees what part of the train is reporting a failure and clicks on that specific part of the system to try and find out more about what's wrong with it.
3) Digging a little bit deeper now...
- After selecting the identified item of failure, the help desk agent browses through the information to learn more about the failure code, location, history of issues, crew info, and data logs. The application also surfaces potential troubleshooting actions that he can take to potentially fix this issue.
- Sometimes, simply rebooting or pinging or pinging a module within the system can correct the failure. The agent tries all the options, but ends up with no other options other than creating a work order so a mechanic can physically tend to the problem.
4) That didn't work. Gotta create a work order.
- The agent proceeds with creating a work order. He knows that it's an issue with one of the central processing units on the train, so he provides as much as information as possible to help the mechanics out and assigns the order to the nearest in-route repair shop. It is a pretty severe issue in regards to safety, so he sets the work order's priority to "High".
5) Get Going! Mechanics are expecting you.
- The work order is successfully created and makes it's way to the repair shop mechanics at the speed of light. The help desk agent can either begin a search for a new issue or, he can return back to the case he was just working if that's what he wants to do.
User: Mechanic
6) Another High Priority work order?
- A mechanic is monitoring his list of work orders and notices a new order pop-up on the screen. It's marked as "High Priority", so he immediately selects the order to view more details in preparation for the incoming train and crew.
7.1) Looks like this train has a failing CPU...
- Upon arrival of the train and crew, the mechanic opens the work order back up and parses through all the information specific to the failing CPU.
7.2) Let's figure out what's going on.
- All information captured by the help desk agent in the work order is provided as well as the failure code, history of issues, crew info, and data logs. The application also surfaces potential troubleshooting actions that he can take to potentially fix this issue.
- The mechanic can either complete the ticket if he's able to resolve the failure, run a test to check for corrections, or, he can escalate the ticket if a new part needs to be ordered or a specialist is required to make the repairs.
8) You're good to go!
- The mechanic is able to correct the failure and elects complete the work order since he replaced the CPU and all systems pass the required tests. The train and it's crew continue on their way and thank the mechanic for his help.
Design Consideration
- Clean and streamlined design and user flow
- Easy to find all the necessary information, monitor and view Train and railroad data
- Show us concepts and ideas for how things could be designed and function. Maybe it is one screen (dashboard) with overlays and flyout windows. Maybe it is multiple screens and panels for different kinds of functionality and tasks. We are open and looking for your ideas and solutions.
General Requirements
- This application is going to be developed as a Desktop Web Application
- Screen Sizes: This will be used on a large screen!
- Desktop Standard (1920px by 1080px - Landscape)
Branding
- Branding is completely open (we will provide feedback at the checkpoint)
- This should be a serious/useful designed application
- We are looking for concepts and ideas!
Required Screens/ Functionality
1) Search for Train Screen
Wireframe Reference “1 - Search Trains.png”
Help Desk agent will use this screen to find Train information
This screen needs to be simple but able to present the app purpose
2) Dashboard - Train Health Screen (Version A) (Checkpoint Priority)
Wireframe Reference “2 Version A - Train Health.png”
The information presented in this screen will be real time connected with the train condition in the field, where if there is failure happens, there will be notifications about the possible issue/problem so Help Desk Agent can inform the Train Crew about troubleshooting action that they can perform to solve the issue.
3) Dashboard - Location Health Screen (Version B)
Wireframe Reference “2 Version B - Location Health.png”
4) Diagnostic Screen (Checkpoint Priority)
Wireframe Reference “3 - Diagnostics.png”
5) Create Work Order Screen
Wireframe Reference “4 - Create Work Order.png”
6) Work Order Submitted Screen
Wireframe Reference “5 - Submitted.png”
7) Work Order List Screen (Checkpoint Priority)
Wireframe Reference “6 - Work Order List.png”
This screen is for Mechanic to monitor new and active working order that comes to them from Help Desk Agent
8) Work Order Details Screen
Wireframe Reference “7 - Work Order Details.png
9) Work Order Completed Screen
Wireframe Reference “8 - Work Order Completed.png”
10) Marvel Prototype
- As part of this challenge, you must upload your files to MarvelApp
- We want to use Marvel App to provide direct and fast feedback!
- No additional functionality is required! Just make sure your screen(s) are in the correct viewing order (number them 00, 01, 02, 03, etc.)
- If you do not have access to the Topcoder Marvel App Account please contact adroc@topcoder.com or fajar.mln@gmail.com
- You MUST include your Topcoder Marvel App URL (share view, not project view) within your Notes file
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- Overall design and user experience
- Cleanliness of screen design and user flow
Target Audience
- Train Helpdesk and Train Mechanic Employee
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
Submit JPG/PNG for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as a layered PSD file, or Adobe Illustrator as a layered AI file or Sketch!
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
What is a GET "Rapid UX Challenge"?
GE Transportation is excited to include the Topcoder Design Community within their design process. The GET (GE Transportation) Rapid UX Challenge is leveraging ideas from our famous RUX challenges and integrating it into how the GE team would like to rapidly create concepts for their design workshops and customers. This challenge has a specific format that we are looking to repeat in future challenges.
The GET "Rapid UX Challenges" provides you with an opportunity to showcase your design concepts and user experience (UI/UX) design skills to one of the largest companies in the world!
Rapid UX Challenge Format
- Challenge starts: Thursday 5 pm EST
- GE is available on Friday for Q&A (get your questions in early!)
- Rolling Checkpoint is Monday morning 7 am EST
- The GE Design team has scheduled time on Monday to review and workshop with your design concepts.
- The GE Design team will provide Checkpoint feedback by end of day Monday.
- Final Designs are due next Thursday 7 am EST.
Note: You do not need to have any design challenge experience to join this challenge - Just jump in and give it a try! Make sure to follow the challenge details, the challenge forum and ask questions.
Challenge Details
The goal of this challenge is to take the provided design problem, analyze the user experience and provide design concepts and visual ideas on how the application might look and work!
Design Problem
In today’s world, locomotive troubleshooting personnel do not have an easy way to view overall health of a train, details about a specific train failure, or the ability to diagnose those failures. Furthermore, the current solution does not offer an intuitive way to assign those issues to the appropriate party for failure mitigation. This application is intended to solve those specific needs and pain points.
We are offering 5 Prize Placements
1) 1st Placement: $1700
2) 2nd Placement: $850
3) 3rd Placement: $350
4) 4th Placement: $200
5) 5th Placement: $100
- Plus 5 placements for Rolling Checkpoint prizes @ $50 each!
Note: Important Rolling Checkpoint Details
- GE Team and adroc will be available on Friday, and Monday-Thursday for questions. (Get your questions in early!)
- Fajar will be available Saturday/Sunday for questions
- You must watch the Forum for your feedback!
*All initial qualifying checkpoint submissions will win $50 (5 Placements)
Challenge Documents
- PTC_Designers_Documentation_V1.pdf
- Wireframes
User Persona's
- Help Desk Persona.png
PTC Storyboard Flow
- Storyboard (Flow).png
User: Help Desk Agent
0) We need help! Our train has stopped...
- Train #238 is traveling along and then stops dead on the tracks for some reason. The crew sees that a PTC "enforcement" has taken place. They check everything they can to see if they can solve the problem but end up having no real option except to call the help desk and ask for assistance.
1) What Train are you guys on?
- The train crew calls the help desk and provide their train number to the help desk agent exits from watching cat videos and proceeds to search for their specific train number so he can find information that might pertain to what is causing the issue.
2.1) OK, I'm pulling your info up...
- Upon searching, the help desk agent finds the train using the PTC app and pulls up an overview page that displays a lot of helpful information about the overall health of the train, it's history, railroad assets around the location of the train, as well as other information.
2.2) I found the problem!
- The application makes it easy to find out what's wrong with the train system by automatically surfacing failures or errors on the screen first. The agent sees what part of the train is reporting a failure and clicks on that specific part of the system to try and find out more about what's wrong with it.
3) Digging a little bit deeper now...
- After selecting the identified item of failure, the help desk agent browses through the information to learn more about the failure code, location, history of issues, crew info, and data logs. The application also surfaces potential troubleshooting actions that he can take to potentially fix this issue.
- Sometimes, simply rebooting or pinging or pinging a module within the system can correct the failure. The agent tries all the options, but ends up with no other options other than creating a work order so a mechanic can physically tend to the problem.
4) That didn't work. Gotta create a work order.
- The agent proceeds with creating a work order. He knows that it's an issue with one of the central processing units on the train, so he provides as much as information as possible to help the mechanics out and assigns the order to the nearest in-route repair shop. It is a pretty severe issue in regards to safety, so he sets the work order's priority to "High".
5) Get Going! Mechanics are expecting you.
- The work order is successfully created and makes it's way to the repair shop mechanics at the speed of light. The help desk agent can either begin a search for a new issue or, he can return back to the case he was just working if that's what he wants to do.
User: Mechanic
6) Another High Priority work order?
- A mechanic is monitoring his list of work orders and notices a new order pop-up on the screen. It's marked as "High Priority", so he immediately selects the order to view more details in preparation for the incoming train and crew.
7.1) Looks like this train has a failing CPU...
- Upon arrival of the train and crew, the mechanic opens the work order back up and parses through all the information specific to the failing CPU.
7.2) Let's figure out what's going on.
- All information captured by the help desk agent in the work order is provided as well as the failure code, history of issues, crew info, and data logs. The application also surfaces potential troubleshooting actions that he can take to potentially fix this issue.
- The mechanic can either complete the ticket if he's able to resolve the failure, run a test to check for corrections, or, he can escalate the ticket if a new part needs to be ordered or a specialist is required to make the repairs.
8) You're good to go!
- The mechanic is able to correct the failure and elects complete the work order since he replaced the CPU and all systems pass the required tests. The train and it's crew continue on their way and thank the mechanic for his help.
Design Consideration
- Clean and streamlined design and user flow
- Easy to find all the necessary information, monitor and view Train and railroad data
- Show us concepts and ideas for how things could be designed and function. Maybe it is one screen (dashboard) with overlays and flyout windows. Maybe it is multiple screens and panels for different kinds of functionality and tasks. We are open and looking for your ideas and solutions.
General Requirements
- This application is going to be developed as a Desktop Web Application
- Screen Sizes: This will be used on a large screen!
- Desktop Standard (1920px by 1080px - Landscape)
Branding
- Branding is completely open (we will provide feedback at the checkpoint)
- This should be a serious/useful designed application
- We are looking for concepts and ideas!
Required Screens/ Functionality
1) Search for Train Screen
Wireframe Reference “1 - Search Trains.png”
Help Desk agent will use this screen to find Train information
This screen needs to be simple but able to present the app purpose
2) Dashboard - Train Health Screen (Version A) (Checkpoint Priority)
Wireframe Reference “2 Version A - Train Health.png”
The information presented in this screen will be real time connected with the train condition in the field, where if there is failure happens, there will be notifications about the possible issue/problem so Help Desk Agent can inform the Train Crew about troubleshooting action that they can perform to solve the issue.
3) Dashboard - Location Health Screen (Version B)
Wireframe Reference “2 Version B - Location Health.png”
4) Diagnostic Screen (Checkpoint Priority)
Wireframe Reference “3 - Diagnostics.png”
5) Create Work Order Screen
Wireframe Reference “4 - Create Work Order.png”
6) Work Order Submitted Screen
Wireframe Reference “5 - Submitted.png”
7) Work Order List Screen (Checkpoint Priority)
Wireframe Reference “6 - Work Order List.png”
This screen is for Mechanic to monitor new and active working order that comes to them from Help Desk Agent
8) Work Order Details Screen
Wireframe Reference “7 - Work Order Details.png
9) Work Order Completed Screen
Wireframe Reference “8 - Work Order Completed.png”
10) Marvel Prototype
- As part of this challenge, you must upload your files to MarvelApp
- We want to use Marvel App to provide direct and fast feedback!
- No additional functionality is required! Just make sure your screen(s) are in the correct viewing order (number them 00, 01, 02, 03, etc.)
- If you do not have access to the Topcoder Marvel App Account please contact adroc@topcoder.com or fajar.mln@gmail.com
- You MUST include your Topcoder Marvel App URL (share view, not project view) within your Notes file
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- Overall design and user experience
- Cleanliness of screen design and user flow
Target Audience
- Train Helpdesk and Train Mechanic Employee
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
Submit JPG/PNG for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as a layered PSD file, or Adobe Illustrator as a layered AI file or Sketch!
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.
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.