Challenge Summary
Welcome to the “Auto Dealer Portal Wireframe Challenge”. In this challenge we are looking for your help to design an intuitive and easy to follow user experience, with wireframes and user flows, for a new dealer portal and DBS looks like system that will be used on desktop devices.
Modern UI/UX best practices should be considered when creating the wireframe designs and user flows.
This Studio competition will be run as a two-round tournament with a total prize purse of $2,500.
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
1) Login page
2) Landing pages
3) Sales Home Page
Feel free to add any screens which are necessary to explain your concept.
2) Landing pages
3) Sales Home Page
4) Parts Home Page
5) Service Home Page
Feel free to add any screens which are necessary to explain your concept
Project Description
From dealer users point of view, dealer portal and DBS looks like on system, but actually they are separate two system, but Dealer portal will work as a front end web UI to access DBS data at backend.
Need support current Dealer portal UI platform and integrate with it seamlessly, need access DBS data and logic by microservice / mini service and also need provide the DBS UI feature, such as list screen, entry screen, tree structure, need support keyboard screen control without touching mouse.
Provide dealer ONE single system including dealer portal function and DBS UI function
Who will be using this application?
- US and Canada 1500 dealers, around 5000 dealer users, and 1000 to 1500 corporate users.
- Each user’s responsibilities, permissions and functions.
- For dealer users, normally they are sale, sales manager or parts manager, for service, they are warranty admin, service advisor, they may have different permission based what they need to access.
- For corporate or internal users, some users can access all US dealers, some may access all Canada dealers, but they have some region or district users, they only can access their region or area dealer data, so which kind of data they can view area based on business hierarchy.
Required Screens / Functionalities
1) Login page
- Can be accessed by dealer users and internal users.
- Need input user name and password.
- Forgot password/reset password.
- All users that want to logon dealer portal/DBS must be maintained (created, updated or deleted).
2) Landing pages
- The 1st page after user logon dealer portal/DBS screen.
- Need show company announcements that apply to that users.
- Need show the coming Events apply to that users.
- Need show Alert messages that apply to that users.
- Need a quick search features for Announcement, Events and Alerts.
- Need show logon user name information there, such as last name and first name, and
need have some action item there, such as view my profile, click help and Logout.
- Need have an option to let user to change language.
- Need have an option to let internal user change brand (Nissan or Infiniti).
- Need show a LiveChat button or link.
- Need show a Quick dashboard for sales, such as, how many cars have been RDRed last month, current month, YTD, how many cars in dealer inventory now and how many cars in SIT status and how many cars in ONS status.
- May need show an action list that user need take.
3) Sales Home Page
- Whenever user click Sales Tab, DBS will navigate to Sales Home Page.
- Need show a Quick dashboard for sales, such as, how many cars have been RDRed last month, current month, YTD, how many cars in dealer inventory now and how many cars in SIT status and how many cars in ONS status.
- Need show a list for old vehicles that means those vehicles are staying in dealer inventory too long, dealer need find a way to get rid of them.
- Need show a list for vehicles searched by other dealers, when, model and dealer info.
- Need show some vehicle incentive programs News or Events.
- May need show a dashboard for vehicle sales breakdown by model line and model year.
4) Parts Home Page
- Whenever user click Sales Tab, DBS will navigate to Parts Home Page.
- Need show Quick dashboard for parts, current month sales, YTD sales, current parts inventory, current month purchase, current month return allowance, and current month return due date.
- Need show Parts Activity Transaction Status, which is an interface from DMS to DBS to send all parts activity to DBS, based on that data, backend system can calculate parts order and parts return automatically for that dealer, so that means this interface will be very critical for Automatic Stock Replenishment Parts Order and Return.
- Need show an action zone to tell dealer to take some action, such as create parts order, submit parts return etc.
- SVC parts order list (service campaign parts order), for each campaign or recall vehicle, dealer have to create a parts order and send to NNA for review and approval, would be nice to have high level tracking list for each dealer.
- May have small area to show dealer parts KPI.
5) Service Home Page
- Whenever user click Service Tab, DBS will navigate to Service Home Page.
- May need show current WIP work order list and highlight with non-qualified assigned technician.
- Need show a current Warranty Claim Status dashboard, new, Open, Error, Warning, Submitted, Suspended, Approved or Denied.
- Need show a reminder list for warranty claim submission, right now NNA have a policy to request dealer have to submit warranty claim after repair work has been closed.
- Need show a message section, sometime NNA send messages to dealer technician and service advisor to tell them something wrong with that car and stop to repair that car and waiting for further instruction.
- Show Early Detected problem for some repair order.
- Show Serviced vehicle with open campaign, that means those cars have been serviced by dealer with open campaign open (campaign issues not fixed) and let the car go, could be driver doesn’t have time today or dealer doesn’t have that part inventory etc.
Target Device
- Design for Web Desktop: 1280px width and height adjusted when is necessary.
Tools & Deliverables
You are free to work with any of the following tools:
Axure: Your deliverable must be a fully clickable HTML wireframe
Sketch: You can also work with static images (PNG/JPG - Black and White) created in Sketch but you must include a fully navigable prototype in HTML created in Marvel App or Invision.
You are also allowed to submit pure HTML wireframes
Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent 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
Wireframes should be built in HTML or Axure, Black and White prototype created in Sketch and providing fully clickable prototype on Invision or MarvelApp.
Source Files
All original source files of the submitted ideas. Please remember to include design thinking in the notes.txt file with your submission.
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths
Modern UI/UX best practices should be considered when creating the wireframe designs and user flows.
This Studio competition will be run as a two-round tournament with a total prize purse of $2,500.
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
Round 1
Submit your initial wireframes for checkpoint review.1) Login page
2) Landing pages
3) Sales Home Page
Feel free to add any screens which are necessary to explain your concept.
Round 2
1) Login page2) Landing pages
3) Sales Home Page
4) Parts Home Page
5) Service Home Page
Feel free to add any screens which are necessary to explain your concept
Project Description
From dealer users point of view, dealer portal and DBS looks like on system, but actually they are separate two system, but Dealer portal will work as a front end web UI to access DBS data at backend.
Need support current Dealer portal UI platform and integrate with it seamlessly, need access DBS data and logic by microservice / mini service and also need provide the DBS UI feature, such as list screen, entry screen, tree structure, need support keyboard screen control without touching mouse.
Provide dealer ONE single system including dealer portal function and DBS UI function
Who will be using this application?
- US and Canada 1500 dealers, around 5000 dealer users, and 1000 to 1500 corporate users.
- Each user’s responsibilities, permissions and functions.
- For dealer users, normally they are sale, sales manager or parts manager, for service, they are warranty admin, service advisor, they may have different permission based what they need to access.
- For corporate or internal users, some users can access all US dealers, some may access all Canada dealers, but they have some region or district users, they only can access their region or area dealer data, so which kind of data they can view area based on business hierarchy.
Required Screens / Functionalities
1) Login page
- Can be accessed by dealer users and internal users.
- Need input user name and password.
- Forgot password/reset password.
- All users that want to logon dealer portal/DBS must be maintained (created, updated or deleted).
2) Landing pages
- The 1st page after user logon dealer portal/DBS screen.
- Need show company announcements that apply to that users.
- Need show the coming Events apply to that users.
- Need show Alert messages that apply to that users.
- Need a quick search features for Announcement, Events and Alerts.
- Need show logon user name information there, such as last name and first name, and
need have some action item there, such as view my profile, click help and Logout.
- Need have an option to let user to change language.
- Need have an option to let internal user change brand (Nissan or Infiniti).
- Need show a LiveChat button or link.
- Need show a Quick dashboard for sales, such as, how many cars have been RDRed last month, current month, YTD, how many cars in dealer inventory now and how many cars in SIT status and how many cars in ONS status.
- May need show an action list that user need take.
3) Sales Home Page
- Whenever user click Sales Tab, DBS will navigate to Sales Home Page.
- Need show a Quick dashboard for sales, such as, how many cars have been RDRed last month, current month, YTD, how many cars in dealer inventory now and how many cars in SIT status and how many cars in ONS status.
- Need show a list for old vehicles that means those vehicles are staying in dealer inventory too long, dealer need find a way to get rid of them.
- Need show a list for vehicles searched by other dealers, when, model and dealer info.
- Need show some vehicle incentive programs News or Events.
- May need show a dashboard for vehicle sales breakdown by model line and model year.
4) Parts Home Page
- Whenever user click Sales Tab, DBS will navigate to Parts Home Page.
- Need show Quick dashboard for parts, current month sales, YTD sales, current parts inventory, current month purchase, current month return allowance, and current month return due date.
- Need show Parts Activity Transaction Status, which is an interface from DMS to DBS to send all parts activity to DBS, based on that data, backend system can calculate parts order and parts return automatically for that dealer, so that means this interface will be very critical for Automatic Stock Replenishment Parts Order and Return.
- Need show an action zone to tell dealer to take some action, such as create parts order, submit parts return etc.
- SVC parts order list (service campaign parts order), for each campaign or recall vehicle, dealer have to create a parts order and send to NNA for review and approval, would be nice to have high level tracking list for each dealer.
- May have small area to show dealer parts KPI.
5) Service Home Page
- Whenever user click Service Tab, DBS will navigate to Service Home Page.
- May need show current WIP work order list and highlight with non-qualified assigned technician.
- Need show a current Warranty Claim Status dashboard, new, Open, Error, Warning, Submitted, Suspended, Approved or Denied.
- Need show a reminder list for warranty claim submission, right now NNA have a policy to request dealer have to submit warranty claim after repair work has been closed.
- Need show a message section, sometime NNA send messages to dealer technician and service advisor to tell them something wrong with that car and stop to repair that car and waiting for further instruction.
- Show Early Detected problem for some repair order.
- Show Serviced vehicle with open campaign, that means those cars have been serviced by dealer with open campaign open (campaign issues not fixed) and let the car go, could be driver doesn’t have time today or dealer doesn’t have that part inventory etc.
Target Device
- Design for Web Desktop: 1280px width and height adjusted when is necessary.
Tools & Deliverables
You are free to work with any of the following tools:
Axure: Your deliverable must be a fully clickable HTML wireframe
Sketch: You can also work with static images (PNG/JPG - Black and White) created in Sketch but you must include a fully navigable prototype in HTML created in Marvel App or Invision.
You are also allowed to submit pure HTML wireframes
Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent 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
Wireframes should be built in HTML or Axure, Black and White prototype created in Sketch and providing fully clickable prototype on Invision or MarvelApp.
Source Files
All original source files of the submitted ideas. Please remember to include design thinking in the notes.txt file with your submission.
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.