Challenge Summary
Welcome to the "GET - Rapid UX - SIMS Yard Visualization Design Concepts Challenge"! We are looking for your help in creating UI/UX design concepts for our SIMS Yard Visualization Application. The goal of this application is to create the Yard visualization with all the essential components in a way that is realistic where a user should be able to look at the yard and identify what each component is. We are looking for a light weight design so it can be easily rendered on the web.
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 for all GET 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 Start: Thursday, 23rd March 2017 5PM EDT (UTC-4)
- Rolling Checkpoint Review Start: Monday, 27th March 2017 7AM EDT (UTC-4)
- Challenge Ends: Thursday, 30th March 7AM EDT (UTC-4)
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 Background Overview
Yard Visualization is a digital, visual representation of an intermodal yard. Yard visualization is meant to provide users with live movement of equipment, containers and resources in the yard. Importantly, it's purpose is to allows users to:
- Have access to key yard operational data that is not readily available in the current system
- Surface/highlight risks that could lead to the hub failing its goals for the day, and allow users to take actions to mitigate those risks.
Design problem
The current problem we have is the yard visualization is too hyper realistic, and gets in the way of user interactions and the display of pertinent data that a user needs to consumer to quickly make decisions.
We are offering 5 Prize Placements
1) 1st Placement: $1700
2) 2nd Placement: $800
3) 3rd Placement: $300
4) 4th Placement: $200
5) 5th Placement: $100
- Plus 5 placements for Rolling Checkpoint prizes @ $50 each!
Challenge Goals
We are looking for visually impressive, yet highly functional designs. We want medium to high fidelity designs that showcases the yard, the equipment, and the data interactions that occur on the map.
Important Rolling Checkpoint Details
- Rolling Checkpoint Review Start: Monday, 27th March 2017 7AM EDT (UTC-4)
- Adroc and GE Team will be available to answer your questions.
- Get your questions in early to avoid any doubts and misunderstanding regarding the requirements!
- You must watch the Forum for your feedback!
*All initial qualifying checkpoint submissions will win $50 (5 Placements)
Challenge Documents
- Yard visualization-ui kit.pdf (Branding Guidelines)
- Personas.png (Target Audience)
- Yard Visualization use case - storyboard.png (User Flow)
- Design challenge.pdf (Wireframe)
Design Consideration
- SIMS is a cloud based application running on GE's Predix platform. The designs you create should adhere to the following standards:
-- Buildable: we should be able to take your designs and hand them over to a developer with minimal questions asked about the technology that will be required to build your designs
-- Responsive: we should be able to adapt your design to at most a tablet screen.
- Clean and streamlined design and user flow
- Easy to find all the necessary information
- 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 and Tablet application.
- Focus on Desktop for this challenge.
- Desktop: Big Screens, 2 x 24 inch Monitor, 1920px x 1080px
Branding Guidelines
- Follow Branding Guidelines in "yard visualization-ui kit.pdf" attached in challenge details.
- This should be a serious/useful designed application
- We are looking for concepts and ideas!
User Flow
Check "Yard Visualization use case - story board.png”
1. The yard is congested and my outbond train is Going to depart late. I need help
2. Have we called the back up crew?
3. We've called for back up, how are you holding up?
4. I need all my crew to be focused right now, so why is John Smith all the way on the other side of the yard?
5. I have been re-routed to avoid congestion. Things are clearing up. Thanks.
Data and Interactions
Trains
For trains, we want the following data to be visualized:
- Train ID
- The number of blocks on the train
- Number of rail cars by type (big or small)
- The number of tracks the train is sitting on
- Goal failures (on inbound trains, which units are not going to meet the customer promised goal)
- Railcar/well utilization metric (in percentage) – for outbound trains
Container stacks
Containers can be stacked on a railcar or in a stacking lot. For stacks, the following information needs to be displayed on a click:
- Positions and tier of all the containers in the well/cell
- Container IDs
- Sizes
- Weights
- Special handling codes if any
- Last free day (if inbound unit)
- Train ID
- Hazmat Flag
- Shippers
- Current task (if any)
Containers can also be parked in a parking lot on a chassis. A container parked in a lot must display the following information on a click:
- Container ID
- Size
- Weight
- Special handling codes if any
- Last free day (if inbound unit)
- Train ID
- Hazmat Flag
- Shipper
- Mated chassis ID
- Mated chassis pool
- Current task (if any)
Crane
Crane data to be displayed on click includes:
- Crane ID
- Crane operator name and ID
- Current task (if any)
- Task route – this includes from and to location, task type; unit being handled by the crane, task duration
- Last known location
Hostler
Hostler data to be displayed on click includes:
- Hostler ID
- Hostler operator ID and Name
- Current task (if any) – current task include the unit or equipment currently being handled by the hostler; the task type; the from and to locations; the duration of the task (start and end time), and the route of the task.
Railcar
Railcar data to be displayed on click includes:
- Railcar initial number
- Well
- Train id
- Inbound/Outbound
- AAR car type
- Rail block
Health Gauges
These gauges include:
1. Trains
For inbound trains, the following information should be represented
- Inbound train line up (defined over a shift or a rolling horizon of 24 hours)
- Train symbols
- Estimated time of arrival
- Actual time of arrival vs planned arrival time
- Planned track (s) vs actual track (s)
- Number of wells broken down by type (big vs small)
- Weight (in tonnage)
- Length (footage)
- Number of units on train
- Progress unloading train
- Number of assigned resources working on train broken down by type
- Goal failures – suggested action to mitigate/reduce risk of failure
For Outbound trains, the following information should be represented
- Outbound train line up (defined over a shift or a rolling horizon of 24 hours)
- Train symbols
- Planned release time vs actual release time
- Planned departure time vs actual departure time
- Number of wells broken down by types (big vs small)
- Weight of train (tonnage)
- Units
- Progress of loading train
- Number of assigned resources broken down by type
- Release failures and suggested action to mitigate risk of failure
2. Tasks
This gauge shows the distribution of work per resource over a period of time (shift or rolling horizon). This gauge should show:
- Planned number of tasks per resource type (crane, hostler)
- Number of completed tasks by resource
- Compliance to the plan (in percentage)
- Productivity per hour (measure in moves for hostlers and in lifts for cranes)
- Chart showing work load distribution per hour per resource over a period of time (chart should show actual work load vs future/planned work load)
3. Inventory
This gauge shows the distribution of inventory (containers), in the yard over a period of time. This gauge should show:
- Actual inventory on hand broken down by type (containers, railcars, chassis)
- Location of these inventory (satellite or mainyard)
- Inventory projection level over a period of two days
- Distribution chart of inventory (broken down by type), over a period of a week.
Suggested Features
01) Yard Section
- Reference "Design Challenge.pdf" Page 2
- Create a design concept for a section of the yard, which should include at least a track, a parking lot, a driving lane, and a building (in 2D and 3D)
02) Yard Equipment
- Reference "Design Challenge.pdf" Page 3
- Create a design concept for yard equipment, which should include a chassis, a container, a crane, a hostler, and outside driver (OTR), a train and a rail car
03) 2D/3D Visual Stacks
- Reference "Design Challenge.pdf" Page 4&5
- Create a design concept that able to visualizing 2D and 3D stacks of containers and chassis with corresponding interaction
04) Health gauges
- Reference "Design Challenge.pdf" Page 6
- Create adesign concept for Health Gauges, which lives on the map. Health gauges can be expanded or collapsed. When collapsed, a user can receive alerts/notifications when one of the gauges receives an important update that requires action. (Health gauges are explained below).
05) Crane and hostler task and route visualization
- Reference "Design Challenge.pdf" Page 7
06) Crane and hostler data displayed on click
- Reference "Design Challenge.pdf" Page 8
07) Play the plan
- Reference "Design Challenge.pdf" Page 9
- Shows a time lapse/video of a train either being loaded or unloaded.
- A user may fast forward, rewind, select a section of the plan and save it.
08) Additional Features/Screens
- Feel free to create new features/screens for any other functionality that you think important for this apps.
09) 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
Target Audience
Read “Personas.png” for more details about these user:
- Hub Manager, This person is in charge of creating the plan for the yard over period of 72Hours.
- Ramp Supervisor, This person is in charge of ensuring that trains on tracks that they supervise meet their goals
- Crane Operator, This person is in charge of loading outbound trains and unloading inbound trains.
- Hostler, This person is responsible for moving equipment and assets in the yard.
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
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 for all GET 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 Start: Thursday, 23rd March 2017 5PM EDT (UTC-4)
- Rolling Checkpoint Review Start: Monday, 27th March 2017 7AM EDT (UTC-4)
- Challenge Ends: Thursday, 30th March 7AM EDT (UTC-4)
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 Background Overview
Yard Visualization is a digital, visual representation of an intermodal yard. Yard visualization is meant to provide users with live movement of equipment, containers and resources in the yard. Importantly, it's purpose is to allows users to:
- Have access to key yard operational data that is not readily available in the current system
- Surface/highlight risks that could lead to the hub failing its goals for the day, and allow users to take actions to mitigate those risks.
Design problem
The current problem we have is the yard visualization is too hyper realistic, and gets in the way of user interactions and the display of pertinent data that a user needs to consumer to quickly make decisions.
We are offering 5 Prize Placements
1) 1st Placement: $1700
2) 2nd Placement: $800
3) 3rd Placement: $300
4) 4th Placement: $200
5) 5th Placement: $100
- Plus 5 placements for Rolling Checkpoint prizes @ $50 each!
Challenge Goals
We are looking for visually impressive, yet highly functional designs. We want medium to high fidelity designs that showcases the yard, the equipment, and the data interactions that occur on the map.
Important Rolling Checkpoint Details
- Rolling Checkpoint Review Start: Monday, 27th March 2017 7AM EDT (UTC-4)
- Adroc and GE Team will be available to answer your questions.
- Get your questions in early to avoid any doubts and misunderstanding regarding the requirements!
- You must watch the Forum for your feedback!
*All initial qualifying checkpoint submissions will win $50 (5 Placements)
Challenge Documents
- Yard visualization-ui kit.pdf (Branding Guidelines)
- Personas.png (Target Audience)
- Yard Visualization use case - storyboard.png (User Flow)
- Design challenge.pdf (Wireframe)
Design Consideration
- SIMS is a cloud based application running on GE's Predix platform. The designs you create should adhere to the following standards:
-- Buildable: we should be able to take your designs and hand them over to a developer with minimal questions asked about the technology that will be required to build your designs
-- Responsive: we should be able to adapt your design to at most a tablet screen.
- Clean and streamlined design and user flow
- Easy to find all the necessary information
- 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 and Tablet application.
- Focus on Desktop for this challenge.
- Desktop: Big Screens, 2 x 24 inch Monitor, 1920px x 1080px
Branding Guidelines
- Follow Branding Guidelines in "yard visualization-ui kit.pdf" attached in challenge details.
- This should be a serious/useful designed application
- We are looking for concepts and ideas!
User Flow
Check "Yard Visualization use case - story board.png”
1. The yard is congested and my outbond train is Going to depart late. I need help
2. Have we called the back up crew?
3. We've called for back up, how are you holding up?
4. I need all my crew to be focused right now, so why is John Smith all the way on the other side of the yard?
5. I have been re-routed to avoid congestion. Things are clearing up. Thanks.
Data and Interactions
Trains
For trains, we want the following data to be visualized:
- Train ID
- The number of blocks on the train
- Number of rail cars by type (big or small)
- The number of tracks the train is sitting on
- Goal failures (on inbound trains, which units are not going to meet the customer promised goal)
- Railcar/well utilization metric (in percentage) – for outbound trains
Container stacks
Containers can be stacked on a railcar or in a stacking lot. For stacks, the following information needs to be displayed on a click:
- Positions and tier of all the containers in the well/cell
- Container IDs
- Sizes
- Weights
- Special handling codes if any
- Last free day (if inbound unit)
- Train ID
- Hazmat Flag
- Shippers
- Current task (if any)
Containers can also be parked in a parking lot on a chassis. A container parked in a lot must display the following information on a click:
- Container ID
- Size
- Weight
- Special handling codes if any
- Last free day (if inbound unit)
- Train ID
- Hazmat Flag
- Shipper
- Mated chassis ID
- Mated chassis pool
- Current task (if any)
Crane
Crane data to be displayed on click includes:
- Crane ID
- Crane operator name and ID
- Current task (if any)
- Task route – this includes from and to location, task type; unit being handled by the crane, task duration
- Last known location
Hostler
Hostler data to be displayed on click includes:
- Hostler ID
- Hostler operator ID and Name
- Current task (if any) – current task include the unit or equipment currently being handled by the hostler; the task type; the from and to locations; the duration of the task (start and end time), and the route of the task.
Railcar
Railcar data to be displayed on click includes:
- Railcar initial number
- Well
- Train id
- Inbound/Outbound
- AAR car type
- Rail block
Health Gauges
These gauges include:
1. Trains
For inbound trains, the following information should be represented
- Inbound train line up (defined over a shift or a rolling horizon of 24 hours)
- Train symbols
- Estimated time of arrival
- Actual time of arrival vs planned arrival time
- Planned track (s) vs actual track (s)
- Number of wells broken down by type (big vs small)
- Weight (in tonnage)
- Length (footage)
- Number of units on train
- Progress unloading train
- Number of assigned resources working on train broken down by type
- Goal failures – suggested action to mitigate/reduce risk of failure
For Outbound trains, the following information should be represented
- Outbound train line up (defined over a shift or a rolling horizon of 24 hours)
- Train symbols
- Planned release time vs actual release time
- Planned departure time vs actual departure time
- Number of wells broken down by types (big vs small)
- Weight of train (tonnage)
- Units
- Progress of loading train
- Number of assigned resources broken down by type
- Release failures and suggested action to mitigate risk of failure
2. Tasks
This gauge shows the distribution of work per resource over a period of time (shift or rolling horizon). This gauge should show:
- Planned number of tasks per resource type (crane, hostler)
- Number of completed tasks by resource
- Compliance to the plan (in percentage)
- Productivity per hour (measure in moves for hostlers and in lifts for cranes)
- Chart showing work load distribution per hour per resource over a period of time (chart should show actual work load vs future/planned work load)
3. Inventory
This gauge shows the distribution of inventory (containers), in the yard over a period of time. This gauge should show:
- Actual inventory on hand broken down by type (containers, railcars, chassis)
- Location of these inventory (satellite or mainyard)
- Inventory projection level over a period of two days
- Distribution chart of inventory (broken down by type), over a period of a week.
Suggested Features
01) Yard Section
- Reference "Design Challenge.pdf" Page 2
- Create a design concept for a section of the yard, which should include at least a track, a parking lot, a driving lane, and a building (in 2D and 3D)
02) Yard Equipment
- Reference "Design Challenge.pdf" Page 3
- Create a design concept for yard equipment, which should include a chassis, a container, a crane, a hostler, and outside driver (OTR), a train and a rail car
03) 2D/3D Visual Stacks
- Reference "Design Challenge.pdf" Page 4&5
- Create a design concept that able to visualizing 2D and 3D stacks of containers and chassis with corresponding interaction
04) Health gauges
- Reference "Design Challenge.pdf" Page 6
- Create adesign concept for Health Gauges, which lives on the map. Health gauges can be expanded or collapsed. When collapsed, a user can receive alerts/notifications when one of the gauges receives an important update that requires action. (Health gauges are explained below).
05) Crane and hostler task and route visualization
- Reference "Design Challenge.pdf" Page 7
06) Crane and hostler data displayed on click
- Reference "Design Challenge.pdf" Page 8
07) Play the plan
- Reference "Design Challenge.pdf" Page 9
- Shows a time lapse/video of a train either being loaded or unloaded.
- A user may fast forward, rewind, select a section of the plan and save it.
08) Additional Features/Screens
- Feel free to create new features/screens for any other functionality that you think important for this apps.
09) 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
Target Audience
Read “Personas.png” for more details about these user:
- Hub Manager, This person is in charge of creating the plan for the yard over period of 72Hours.
- Ramp Supervisor, This person is in charge of ensuring that trains on tracks that they supervise meet their goals
- Crane Operator, This person is in charge of loading outbound trains and unloading inbound trains.
- Hostler, This person is responsible for moving equipment and assets in the yard.
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
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.