ROBIN - Dealer Management System App UI Design Challenge

Welcome to "Project ROBIN - Dealer Management System App Design Challenge". This challenge goal is to create a set of new user interfaces for our Dealer Management System (DMS) application called ROBIN that will be used to replace the old/current DMS in one of our businesses. 

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

Round 1

Submit the following screen requirements for checkpoint feedback:
02) DMS Home Screen
04) Manufacturer Hierarchy Screen
05) Customer Master Screen
06) Material Receipt Note (MRN) Screen

• As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit the complete screen requirements + interactions along with all feedback applied for final review: 
01) Login Screen
02) DMS Home Screen
03) Terms and Conditions - Dealer Branch Screen
04) Manufacturer Hierarchy Screen
05) Customer Master Screen
06) Material Receipt Note (MRN) Screen
07) Repair Order Search Screen

• As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
• If you're not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2

CHALLENGE OBJECTIVES

• UI design for a Responsive web application (focus on Desktop/web for now)
• Create 7 unique Desktop/Web screens for ROBIN DMS application
• Intuitive UI: must be very easy to use. Provide a clear and intuitive experience for users to examine and understand the content inside the app

EXPLORATION SCORE

• Creativity: Impactful - the solution is different or unique from what has already been used.
• Exploration: Flexible - use the provided screen requirements as a starting point, and propose improvements that positively impact the users’ goals.
• Aesthetics: Hi-fidelity design - provides a top-notch finished-looking visual design.
• Branding: Strict - carefully follow the provided guidelines and stick to them

BACKGROUND OVERVIEW

• We are a technology & innovation-led, global, federation of companies that provides a wide range of products, services & possibilities to people, enabling them to Rise.
• In this challenge, we want you to create a new Dealer Management System (DMS) application called ROBIN which will replace our existing/old system in one of our businesses that is focused and serves a purpose as a Dealer in the Automotive industry.
• Our Dealer businesses cater and help our other businesses in the Automotive industry which support processes like sales, service, spare parts, and CRM.
• The Core modules of the ROBIN DMS application will be:
  • Presales and Sales
  • Services
  • Schemes & Claims
  • Dealer CRM
  • Spare Parts
  • Financial Accounting
  • HR
  • Common and Admin
• In this challenge, we will create several screens to cover important features for the new DMS application, please read the details requirement below carefully!

GLOSSARY

• Dealer Management System (DMS): a software platform dealers use to manage their dealership. This app enables a dealership to perform all the day to day functions their dealership encounters from sales operations, financing operations, service operations and more; it is important that all these functions of a dealership work together.  

DESIGN GOALS 

• Create an application that is able to run Dealer's activities spanning from Showroom and Workshop operations
• Create User Interface design that will cover the overall look, feel and usability of the new DMS 2.0
• Provide a standardized and accurate view of the data, with direct paths to support detailed information
• Allow users to easily identify areas where attention is required and instantly drill into the details
• Clean interface with impeccable navigation design and information architecture, encouraging users to use every feature the application has to offer
• Simple and intuitive menu, to provide ease of navigation across large number modules, processes and functionalities
• Excellent visual hierarchy

TARGET AUDIENCE

• The following users will use the ROBIN DMS application and features asked in this challenge:
  • DMS Admin 
  • DMS Business User
  • Dealer Normal User
  • Dealer Admin User 

SCREENS / FEATURES REQUIREMENTS

01) Login Screen

• Reference old screen 01 Login.png
• User needs to logged in to the application in order to be able to use all features in the ROBIN DMS App
• The user should provide valid username and password to login into application
• The new User ID and Password will be created by the Application Administrator or respective Dealer Administrator
• In an event that the DMS user does not remember his/her password to access the system, the same should be reset using Forgot Password link 
• If the account is locked for any reason, he/she should contact the dealer admin user to reactivate the account
• Find the complete mapping content from This Document (login content), please make sure to include all those elements in your design
• Need to create screen interactions for error password and locked account

02) DMS Home Screen

• Reference old screen: 02 Homepage - Dashboard Screen.png, 02 Homepage - Main Nav.png, 02 Homepage - Sub Menu.png
• Home page shall display various widgets which include feature rich dashboard, data driven action item so that user can quickly navigate and take required action, Information on news, Upcoming events, reminders, Upcoming training, etc. 
• The home page shall provide the navigation facility to the user through a module wise menu
• Within the main menu (under some particular main menu item/module), there can be multiple items in terms of transactions, masters, reports, etc. Users should be able to navigate to these line items as well
• There shall be a provision to search the menu based on the keywords and mark mostly used function as favourites. This keyword-based search / favourite function shall allow user to navigate directly to the intended functionality.
• Menu/Navigation must come out very clearly  in the design
• Find the complete mapping content from This Document (DMS Home content), please make sure to include all those elements in your design

03) Terms and Conditions - Dealer Branch Screen

• Reference T&C Diagram
• There is a need to print terms and conditions, especially on customer facing documents
• This screen will help the Dealer to define their terms and conditions which are specific to that dealer branch in addition to the Manufacturer T&C for the corresponding document. The same will be printed on the document while taking a print or viewing it.
• There are several T&C list items in the ROBIN DMS application:
  • Terms & Conditions
  • Terms & Conditions – Manufacturer
  • Terms & Conditions – Dealer Branch
  • Terms & Conditions – Revised
  • Terms & Conditions – History
• User should be able to select which T&C that they want to printed and work on
• Find the complete mapping content from This Document (Terms and Conditions - Dealer Branch content), please make sure to include all those elements in your design

04) Manufacturer Hierarchy Screen

• Reference Manufacturer Hierarchy diagram
• Application Administrator shall be able to build Manufacturer Hierarchy for various Manufacturers through this user interface.
• This screens should simplify the way user to find informations about Manufacturer hierarchy in a structured tree
• Find the complete mapping content from This Document (Manufacturer Hierarchy content), please make sure to include all those elements in your design

05) Customer Master Screen

• Reference old screen Customer Details, Address, Credit Limit, Other Details, Profile Details, Family Details
• Once any financial transaction is done between dealer and prospect then the prospect will be treated as a customer. 
• Every customer will have an identification number which will be unique across the DMS network. 
• This transaction will allow the user to create and maintain the customer ID. 
• This transaction will be accessible to the dealer user
• To view the customer details of a customer ID generated by another dealership, the dealer needs to perform at least one transaction with that customer ID in DMS. 
• The details of the customer ID can be edited. There would be provision to have 360 degree view of the customer. The below picture depicts the possible information which can be displayed: Screenshot
• Find the complete mapping content from This Document (Customer Master content), please make sure to include all those elements in your design

06) Material Receipt Note (MRN) Screen

• Reference Old screen 07 MRN.png, 07 MRN Stock Details scrolled 1.png, 07 MRN Stock Details scrolled 2.png
• MRN can be generated against the Purchase Invoice No. dispatched to the dealer
• On entering or selecting MRN no. dispatched parts against selected MRN should be displayed in the screen
• Dealer user can further select the appropriate status against each part and submit
• On submitting, system should add received stock into Dealer Stock
• Local POs can be directly received in MRN with reference of PO id and counter sale id
• Find the complete mapping content from This Document (Material Receipt Note content), please make sure to include all those elements in your design

07) Repair Order Search Screen

• Reference old screen 10 Repair Order Search.png
• User should be able to search & view the Repair Order details for a particular date range or specific to a vehicle based on Registration Number/Chassis Number/Customer ID.
• Find the complete mapping content from This Document (Repair Order Search content), please make sure to include all those elements in your design

IMPORTANT!!

• We are looking for a base design template for the new ROBIN DMS application, for example, how the form elements are designed, how and where the navigation is etc.
• We are going to use the result of this challenge as a design guide for the rest of the remaining screens in the future

CHALLENGE FORUM

• If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum: https://apps.topcoder.com/forums/?module=ThreadList&forumID=840987

BRANDING GUIDELINES

• Please use the client’s branding guidelines as a high-level guide to palette and visual style 

DOCUMENTATION

• Client visual branding and styles (available in challenge forum!)

TARGET DEVICES

• Web/Desktop: minimum 1366px width and height as required

SUBMISSION AND SOURCE FILES

Submission File

• Submit JPG/PNG image files based on Challenge submission requirements stated above
• MarvelApp link for review and to provide feedback (Ask Prototype in Forum)
• Declaration files document contains the following information:
  • Stock Photos Name and Links from allowed sources
  • Stock Art/Icons Name and Links from allowed sources
  • Fonts Name and Links source from allowed sources
• Full Details of the Topcoder Policy can be found in this LINK

Source Files

• All source files of all graphics created in Figma or Adobe XD (Client Preference/Recommendation), or Sketch and saved as an editable layer

FINAL FIXES

• As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors
• Create Design assets (zeplin, marvel hand off, xd or figma prototype hand off), your source files must include all the design attributes/style sheets/colour codes & shapes specifications, etc