Challenge Summary
Introduction:
The client for this project has decided to create a new mobile application to help manage and track tools for automotive manufacturers / Original Equipment Manufacturers (OEMs). We have already run a design concepts challenge to come up with the initial screens for this mobile application. The next step is to refine the designs we currently have as well as add additional functionality, features and user flows.
For this challenge, we need you to refine the screen designs for the new Asset Tracker mobile application. You will be using the designs from our previous mobile application design challenge as the starting point for this challenge.
We look forward to seeing your design updates and refinements!
Round 1
Round 1 will focus on the following screens for the new Asset Tracker mobile application:
01 - Mobile: Add New Tool
02 - Mobile: Editing/Adding/Confirming Scanned Tool Location
03 - Mobile: Add Tools to Shipper
04 - Mobile: Reporting
NOTE: See the challenge goals below to understand the screens / functionality needed for the new Asset Tracker application. If anything is unclear, please ask for clarification on the forum and we will be happy to help!
Round 2
In Round 2, you will need to include all Round 1 screens (updated based on milestone feedback). For Round 2, you must also include all the remaining functionality descibed in the project documentation, including the following screens:
01 - Mobile: Add New Tool
02 - Mobile: Editing/Adding/Confirming Scanned Tool Location
03 - Mobile: Add Tools to Shipper
04 - Mobile: Reporting
05 - Mobile: Leaderboard
NOTE: See the challenge goals below to understand the screens / functionality needed for the new Asset Tracker application. If anything is unclear, please ask for clarification on the forum and we will be happy to help!
Primary Goals
The goal for this challenge is to refine the Asset Tracker mobile app designs we currently have as well as add additional functionality, features and user flows. You will be using the designs from our previous mobile design challenge as the starting point for this challenge.
Project Background:
Manufacturers / Original Equipment Manufacturers (OEMs) have historically not done a good job of managing, tracking and monitoring their multi-billion dollar annual investments in tooling throughout its 10-20+ year lifecycle. OEMs have a complex multi-tier supply chains where tool information is spread across many stakeholders, making it difficult to find and maintain over time. The sources of tooling information and the actual location of the tools is highly decentralized and degrades throughout the life of the asset. Ultimately, critical tooling information becomes disconnected from the tool and the probability of poor financial and operational outcomes increases over time.
A smartphone-based app will enable rapid deployment to a vast number of users across the global supply base of each Automotive OEM. A mobile-device based app will also avoid the cost and challenges associated with infrastructure and hardware requirements associated with other types of asset tracking systems. The OEM and suppliers would be able to send, receive, and access critical tooling information shared through a cloud-based system. OEMs would also have access to a responsive web app (administrative and management type view) and will be able to run analytics based on accurate tooling information leading to better decision-making and more effective tooling management processes.
Challenge Goals:
We’ve outlined some key features, updates and additions that we need to see. We have also included some specific details and user flows around each of these and we are looking to you to best integrate these into the existing designs. This could include adding new screens and/or editing the existing screens.
What's Needed:
01 Mobile: Add New Tool
A task/alert would show up saying data for a New Tool has been added to the system (Please show this as part of designs/user flow for this screen). The user taps the notification and is presented the Add New Tool screen.
- The user is presented with the details of the tool and prompted to scan the tool. When the new tool is scanned the following should occur:
- The user should be asked to confirm the Tier 1 supplier for the tool based on the location (select from suppliers within a 20* mile radius of the current location).
- If that is not the supplier for the tool, the current location should be added as a sub-tier site and the user should be able to search for a tier 1 supplier or add a new supplier (if a new supplier is added the OEM should be notified - added to the tools that might not be in the right location list).
- A final Add New Tool button should confirm selections.
02 Mobile: Editing/Adding/Confirming Scanned Tool Location
This is a step between scanning the tool and hitting Confirm. When a tool is scanned, the following scenarios need to be dealt with:
- Generally when a tool is scanned the tool detail view is shown
- If there is an outstanding task for the tool it should be displayed somehow
- If the tool is scanned in a location that is more than, 20 miles for example (could be a variable filter, scrubber, dropdown, etc), from the last confirmed physical location it was at then the supplier should have the following options and the previous supplier and OEM should be notified using the tool tracking or reporting functionality:
- Update supplier for the tool (new tier 1 supplier for the tool)
- Confirm the tier 1 supplier for the tool and update the physical location (tier 1 supplier unchanged but tool is physically located at another supplier)
- Don't change the supplier or the physical location of the tool but add a comment to explain
- We would also like to ability to use NFC as an option when viewing the scan screen. This could be a toggle towards the top to switch between QR scanning and NFC. For the actual NFC screen think about UX patterns flows that resemble ApplePay or GoogleWallet. A simple screen with some brief directions and a circle or something other icon that turns to a checkmark (or something similar) to let you know it has successfully scanned.
03 Mobile: Add Tools to Shipper
The user would receive a task/alert that a tool, or series of tools, needs to be added to a shipper.
(Please show this as part of designs/user flow for this screen)
- Tap notification to open the Add Tools to Shipper screen
- Tap a + sign or “Add Tool” button to add a tool
- Adding a tool requires the user to Scan it and confirm it’s current location. Clicking confirm adds the tool to the list
- Needs to have to the ability to edit the tool information after its been added to the list.
- Can add additional tools by tapping the + sign again.
- Needs the ability to enter shipper destination
- Submit the shipper/list of tools by tapping Generate Shipper. This will generate a PDF and send it to the OEM/Supplier.
- Confirmation screen
04 Mobile: Reporting
Add in a button that says Generate Report on the Tool Details view screen. This will take you to the Reporting Dashboard.
- List of all your tools that you’ve checked in/scanned.
- Status of each. Incomplete vs. Complete. Incomplete tools move to the top of the list.
- Clicking on an incomplete tool item opens an overlay as to why its incomplete
- Generating a Report is a 3 step process
1. Select who you would like to send that report to: OEM, supplier, client, etc.
2. Select which tools from your list that you would like to include in that Report
3. Send Report
- After a tool has been sent as part of a Report is should be indicated in the list somehow.
05 Mobile: Leaderboard
Add a nav item that says Leaderboard. The Leaderboard Dashboard is a screen for the user to monitor specific challenges that they are entered in as well as their progress, ranking, and awards received. Challenges include how many tools a user has scanned and checked into the system. The screen is divided into 3 areas. This could be treated as tabs or something other mobile UX pattern that makes sense. That 3 areas include:
Dashboard Tab
- Main content of the Leaderboard Screen
- Overall user progress/how many tools the user has scanned
- Current challenges they are entered in and their progress/where they rank for each. Assume the user could be in up to 5 challenges at once.
Challenges Tab
- List of current challenges and their details. i.e. How many tools need to be scanned in X amount of time.
- Ability to “sign up” or “enter” for a challenge
- What are the prizes for the challenges. Generally these would include gift cards, but could be work related items i.e. A day off
Awards Tab
- Shows which awards the user has won
- Which awards they are currently eligible to win (based on which challenges they signed up for)
NOTE: If anything is unclear, please ask for clarification on the forum and we will be happy to help!
General Requirements:
- Produce front-end screen designs (Storyboard) that can be used to demonstrate all screens / mentioned functionality as required in the challenge spec.
- Required designs are for a new, cross-platform PhoneGap mobile application (the Auto Assets Tracker mobile application).
- The design should have a clean, modern, look-and-feel that matches the design concept screens.
- The design must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in contest round details (and described in the challenge spec).
- Your design must represents all pages and flows from the challenge spec. You should use these descriptions as a guide, but if there is better way to display any information, feel free to reflect that on your design.
Branding and Guidelines:
- Your design must fit mutiple mobile devices: iOS (iPhone 5 should be 640x1136 px) and Android (720x1280px) screen resolutions. The mobile app is being created in PhoneGap so your design should be scalable for different devices.
- As for color requirements, please stick to similar colors to the design concept screens.
- Creativity is also welcome!
- Use web-safe fonts for the pages content. Please make sure to declaring your fonts according to the Studio font policies.
- Show all the hover states for all UI elements you create (buttons, hyperlinks, dropdowns, etc).
Storyboard Requirements:
Overall:
- Follow the workflow and user flow guidance from the challenge spec above. You need to create screens to cover all these pages.
- Make sure to provide screens for popups, collapase/expandable features, error forms, and so on.
- As a suggestion, look at all the buttons in the forms to understand the interaction features of the application.
Project Documentation:
1) Existing PSDs from Mobile Design Challenge. Use these files as a starting point and to pull styles and UI elements from.
2) Current brand guidance: Please use these as a guideline, creativity is also welcome!
Target Audience
Plant workers who check-in/report on large tools and/or assemble parts from many different OEMs to help create an end product.
Judging Criteria
- Overall look and feel of the design
- Simplicity and consistency in the design
- Completeness and accuracy of how the design matches the screens / user flow described in the challenge spec.
- How well you follow the client's branding / design guidelines.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client)
What to Submit
Preview JPG/PNG Image File
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 ZIP File
All requested contest requirements/screens as JPG or PNG files.
Source ZIP File
All fully editable original source files of the submitted design as required by the contest under "Source Files" in the side bar.
Final Fixes
As part of the final fixes phase you may be asked to complete one round of minor changes to ensure your submission meets the stated requirements of this contest. See more information about Final Fixes.
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.