Challenge Summary
Please Note that this is really fast contest with only 24hours available for submission phase. Copilot will be stay online during contest phase to answer all questions related to the requirements. Please Focus and prepares your times efficiently in this contest. We are waiting for your participation!!
Welcome to “FAST!! 24hrs Talos - Dispatch Heat Map Wireframes” contest. The goal of this project is to create an easy to use application that able to visualize and mapping geographic data (on a map) through historical / past data about dispatches jobs to making business decisions for user that provides tow and service business. In this contest, we need your help to design application flow for this application based on our conceptualization document.
At the end of this contest, we are looking an HTML wireframes which showing a new workflow and provides great user experience for the application and can be used as suggestion for the next development phase.
The client for this project has decided to create an application to help support a business where Tow Truck drivers and Service Delivery drivers (change a tire, perform a jumpstart, etc.) perform jobs at different locations. The goal of the application will be to visualize data geographically (on a map) from past dispatches jobs to increase knowledge base of client providers so that they can more effectively run their business. This would be achieved by providing them with easy to use mapping software that shows where historical dispatches (jobs) they have been located. If they can easily see on a map where they are busy and not busy, they can better position their trucks going forward.
Currently, our client got no system in place to visualize data from past dispatch jobs on a map. This past dispatch job information is useful to identify which geographical areas are busy during different time periods. Without analyzing those data, it’s hard to efficiently to locate their drivers.
This application will be create based on Google Maps where users can visualize past dispatch job over a map. Users of the application will be able to view a map where pins are displayed over the location where jobs have been performed in the past. Each pin will represent an individual job, along with details such as location of the job, the provider who handled the job, date and time of the job, the type of job (tow, service, other), and the job status (accepted or rejected).
Task Requirements
Here are list of requirements that needs to be create in this contest :
a. Provider User (Driver, Owner, and Dispatcher) and Admin User
1. Login/Logout to the application (4.4.1 – 4.4.2)
2. View Help (4.4.3)
3. View Map (4.4.4)
4. Zoom in On Map (4.4.5)
5. Zoom out On Map (4.4.6)
6. Set Display Settings (4.4.7)
7. Search For Locations (4.4.8)
8. Select Map Filters (4.4.9)
9. Select Date Range (4.4.10)
10. View Coverage Area (4.4.11)
11. Print Map (4.4.12)
12. Export Data (4.4.13)
b. Admin User
1. View Multiple Providers (4.4.14)
2. View All Providers (4.4.15)
3. Simulate Modified Provider Coverage Area (4.4.16)
Target Audience
There will be 4 kind of audiences that will use this application, which are :
a. Dispatcher (part of the Provider User role)
The dispatcher sees all jobs coming into the provider’s shop and decides whether to accept the job and which driver to assign it to. The dispatcher would also benefit from seeing historically where services have been located, to help understand how to best assign jobs to drivers.
b. Owner (part of the Provider User role)
The owner of the tow or service operation would have the ultimate say in how to position drivers and how many drivers to have working during any given shift. They will use the heat mapping application to help them make these decisions more effectively.
c. Driver (part of the Provider User role)
The driver would ultimately go out to the dispatch location. Their positioning will largely be determined by the Owners. Drivers won’t use the application directly for this phase of the project, but they are often paid by commission, so they will benefit from having better location decisions (quicker arrival times, able to complete a job faster and move on to the next job).
d. Admin Users
The “Admin” user is an employee of Talos. They will have access to more functionality than individual Provider users, such as the ability to look at data on the map for any specific provider or multiple providers. They will be able to view jobs completed for an entire area (such as a city), regardless of provider.
IMPORTANT : You must create scenario for all user above in your submission.
Judging Criteria
Your submission will be judged on the following criteria:
- User Experience
- Completeness and accuracy of the wireframe as defined in the requirements.
- How well your wireframes provide a consistent user flow
- How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Attachment :
- Conceptualization Document - Dispatch Heat Map Conceptualization.docx (conceptualization document)
- TopCoder%20-%20Dispatch%20Heat%20Mapping.docx (questionnaire document)
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.