Velos - Truck Tracking Application Design Concepts Challenge

Welcome to the Velos – Truck Tracking Application Design Concepts Challenge! In this challenge, we are looking for your initial design concepts that will help us visualize the screens needed for new application. Velos is a global leader of shipping services.  This application will be used to optimize routes for trucks, help truck drivers with their task management, help dispatch personnel track their trucks’ location and status.

We currently do not have any formal requirements beyond the listed use case scenarios. We are looking for you to provide design concepts and click-paths based on the provided information.

Round 1

Submit your design for a Checkpoint feedback:
0. Navigation.
1. Landing page.
2. Dashboard page.
3. Route Optimization page.
4. Driver Mobile Login
5. Task Management page (mobile)
- If you have time - please provide us with a click map for your design.
- Readme.jpg : Provide notes about your submission.
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

Round 2

Final Design plus Checkpoint feedback:
0. Navigation.
1. Landing page.
2. Dashboard page.
3. Route Optimization page.
4. Task Management page.
5. Truck Location Monitoring page.
6. Truck OBD2 Port Statistics.
- If you have time - please provide us with a click map for your design.
- Readme.jpg : Provide notes about your submission.
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

Challenge Description:
The Purpose of this challenge is to come up with initial design concepts for a web application that will help all users do their jobs easily and perfectly.

We are looking for the [topcoder] design Community to help us with planning our new "user experience" (UX).

Note: Velos is a code name.

Branding Guidelines:
- Branding guidelines (BrandingColors.png.zip)

Design Concept Goals:
- Looking for modern, intuitive user interface
- Focus on the design being a great user experience, think simple but effective solutions!
- Give importance to the overall layout and think on how a user would interact with the content on the page.
- Show all the screens and provide a user flow/click-path and navigation, so we can see how the interactions fit together in the application
- How should this desktop application look?
- How should the mobile aspect look in relation to the desktop views?
- Read the user story and decide what should the priority features be (what is the priority navigation for this user?)
- How quickly the user can find what he wants?
- The application should be easy to use.
- The mobile aspect to this application will be HTML5 within a native application shell
- Responsive design is to be kept in mind even though most user scenarios are for single form factors

Screen Sizes:
- Standard Desktop design resolution 1280x800
- Mobile Resolution: Design for iPhone 6 Retina Display 750px x 1334px.
Make sure you create graphic in 'shape' format, so when resize for retina versions, graphic still look sharp! It will be great if you can provide the landscape version.

Application Features:
1- Route Optimization:
- Enable users to calculate truck delivery routes on a daily basis.
- The system should be able to accept a file upload containing all truck information and destination information.
- Example Information:
-- 10 trucks with 4,054 cubic feet of capacity each.
-- Origin address for all trucks, 123 ABC Street.
-- List containing address information of all 85 destinations.
-- Cubic volume of order for each destination.
- The system must use the uploaded file to calculate optimized truck routes for all listed trucks and destinations.
- Each truck route will have the destinations listed as tasks to be completed in order.

2- Task Management:
- Drivers will have the ability to view each destination on their route as tasks on a mobile device.
- Turn by turn navigation will help the driver navigate between destinations.
- Tasks will be marked complete by the driver as deliveries are made.
- Drivers should be able to capture information about their delivery if follow up action is required
- Include sample alerts for things helpful to the driver if an error is found on their OBD2 Port (e.g. tire pressure low)

3- Truck Location Monitoring:
- A central dispatch person needs to be able to monitor the GPS location of the trucks during their route.
- Geo Fence areas will be setup for each destination.
- Trucks will change status on the dashboard as they go in and out of each destination Geo Fence area.
- Statistics will be kept for the total time in route, time between destinations, and time spent at a destination.

4- Truck OBD2 Port Statistics:
- Trucks will be remotely monitored by a wireless OBD2 port.
- The truck operational data will be displayed on a dashboard for dispatch to view truck information.
- Sample Data:  speed, RPM, engine temp, fuel rate, battery, error codes.

Required Screens:
- We would like you to suggest features/screens that this app should incorporate
0) Navigation:
- How does the user navigate this application?
- Include navigation that you think fits with this application.
- Focus on the priority items and how things should be sized.

1) Landing Page:
This is the landing page for the application.
- This page should reflect the Velos branding and look "premium" in design.
- Creating a logo for “Velos” will help give your design a complete look and feel; just make something simple that fits the type of company we describe in the summary.  Use the logo where and when it makes sense
in the application overall.
- It should very clearly show what user can do with this application and what the application is all about.
- A user can login from this page.  User type determines if they are taken to A - Routes Manager screens or C - Central Dispatch User

The following screens depends on user role:
A- Routes Manager: (Desktop)
2) Dashboard page:
- In this page the manager will be able to view a list of all available truck, a search and filter features can be included.
- If the user selects a truck he will be available to view important information related to it:
-- Truck location (Maybe a map here).
-- All the tasks related to the truck.
-- Suggest what else should be included here as cool or nice things to have.

3) Route Optimization page:
- This should cover route optimization feature described above.

B- Driver: (Mobile)
4) Driver Mobile Login:  
-This should be a simple branded login screen for drivers to access the Task Management screen (5)

5) Task Management screen:
- This should cover task management feature described above.

C- Central Dispatch User: (Desktop)
5) Truck Location Monitoring page:
- This should cover truck location monitoring feature described above.
- A mobile version of this page can be included as an extra feature for the User

6) Truck OBD2 Port Statistics:
- This should cover truck OBD2 port statistics feature described above.

Important:
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance

Target Users:
- Routes Manager.
- Truck driver.
- Central dispatch person.

Judging Criteria:
- How well you plan the user experience and capture your ideas visually.
- Cleanliness of your graphics and design
- Your design should possible to build and make sense as a web and mobile application
- Creativity and ease-of-use is key to the success as it must be engaging to users.

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 layered PSD file, or Adobe Illustrator as a layered AI file.

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.