Welcome to "
Xerox BlockChain - Product Lifecycle Tracking Design Concepts Challenge". In this challenge, we need your creative skills to help us create the best possible UX/UI for our Product Lifecycle Tracking app that will utilize BlockChain technology. 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 your initial design for a Checkpoint Feedback
01) Login Screen
02) Xerox Administrator/Partner Screen (IMPORTANT SCREEN!)
03) Xerox Sales Person Screen
04) Xerox Configuration Engineer 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 correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Round 2
Submit your Final Design plus Checkpoint Updates
01) Login Screen
02) Xerox Administrator/Partner Screen (IMPORTANT SCREEN!)
03) Xerox Sales Person Screen
04) Xerox Configuration Engineer Screen
05) Xerox Customer Screen
06) Xerox - Rigger Screen
07) Xerox - Shipping Carrier Screen - Manufacture to Xerox
08) Manufacture Company - Factory Engineer 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 correct flow. Use the proper file numbers, (1, 2, 3, etc.)Background Overview
This challenge purpose is intended to demonstrate how Blockchain technology can be used to provide new levels of visibility into a Xerox-related value chain: the print hardware lifecycle. This application will show how blockchain supports the autonomous functioning of each supply chain element while providing consistent information to Xerox and its partners. These elements include:
- Delivery from the manufacturer
- Warehousing / Print Hardware Inventory
- Device contracted to a customer
- Device configuration
- Delivery to customer
- Use by customers
- Model Reliability
- Disposal
Challenge Goal
Create the best possible UI/UX for Product Lifecycle Tracking app that follows client guidelines and able to simulate various of possible scenario needed in the app
App Workflow
1) Needs to simulate a user interface that:
- For individual devices
-- Allows the user to pick a particular device by serial number
-- Allows the user to filter the display to shows the device’s current geographic location and/or all of its previous locations (manufacturing facility; warehouse; customer site; disposal facility) on a map
-- Presents a dashboard that shows the device’s current state (configured / not configured; configuration name; under contract / not under contract and the history of those states)
- For a particular model
-- Allows the user to select a particular model
-- Allows the user to filter the display to show the current and/or previous locations of all instances (individual devices) of the selected model (e.g. 140 in France; 211 in the UK) on a map
---- the map should be zoomable see the granular details within a nation: number of devices in a city; number of those devices at a customer site
---- If you zoom in far enough, it should be able to show the individual device serial numbers at a given location (for the selected model)
- An authorized Xerox user can see any device or model
- An authorized Xerox partner can see only the devices that are at his/her customer's sites
- An authorized user can analyze the data related to a particular device or model
2) A simulation of different people entering data with different applications about the device at different stages of the device’s lifecycle. For example:
- A manufacturing quality assurance engineer certifying that the device construction is complete and ready to ship
- A carrier picking up the device for shipment to a Xerox warehouse
- A salesperson specifying a contract for that device
- A salesperson specifying a configuration for that device for a prospective customer
- A configuration engineer configuring a device with a particular known configuration with several exceptions
- A carrier picking up the device for shipment to the customer
- A rigger installing the device
- A customer using the device
- A customer ordering service for the device
- A recycler picking up the device
- A recycler reselling the device's parts
- Other examples where partners sell the devices can also be included
3) The underlying data elements and blockchain that supports the user interface will be graphically represented so that someone unfamiliar with databases can understand what is happening and how it is happening. (see page 5 from Xerox requirements.docx)
Branding Guidelines
- Use Xerox logo as part of your design
- Main Font is Arial
- Design Style is open to Designers
Screen Requirements
01) Login Screen
Wireframes Page 2
- All user will logged in to the app using this screen
- Ordinary login form (username/password/submit button)
- Might need forgot password link added to the screen
- Need to have error login scenario
02) Xerox Administrator/Partner Screen (IMPORTANT SCREEN!)
Wireframes Page 4, 5
- This screen is the MOST IMPORTANT screen that you need to focus on this challenge!
- There are 2 separate screens that the administrator can see in this app: Map Search and Dashboard
Map Search
- Default view that user will see once logged in to the app
- There are 2 main design elements in this screen, filter area, and map area
- We'll want the user to be able to read the information on the screen. An authorized user can analyze the data related to a particular device or model
- We need the feature of zoom in and out where the user will be able to read (or at least identify) the information on a particular region (e.g. an American state or a European nation)
- Please see this video reference on how the map UI scalability needs to be created (it has the kind of interactions that we want in the map, see how the zoom in and out works to show informations):
https://www.youtube.com/watch?v=YdgfbhQJxpY
- We included the video above as an example of the kinds of tools available to display information about map data
- For the Map Design, feel free to use Google Map (Other map source needs to be confirmed in the forum first)
- The map should be zoomable see the granular details within a nation: number of devices in a city; number of those devices at a customer site
- If you zoom in far enough, it should be able to show the individual device serial numbers at a given location (for the selected model)
- We're gonna need to cover/simulate the following main interactions on the map:
-- For Individual Device (one device), allows the user to pick a particular device by serial number and allows the user to filter the display to shows the device’s current geographic location and/or all of its previous locations (manufacturing facility; warehouse; customer site; disposal facility) on a map
-- For Particular Model (multiple devices), allows the user to search and filter particular model. Allows the user to filter the display to show the current and/or previous locations of all instances (individual devices) of the selected model (e.g. 140 in France; 211 in the UK) on a map
-- Use Case 2a: Individual Device Lifecycle Inspection (Xerox requirements.pdf -> Page 12, 13)
-- Use Case 2b: Individual Device Lifecycle Inspection (Xerox requirements.pdf -> Page 14, 15)
-- Use Case 2c: Model Lifecycle Inspection (Xerox requirements.pdf -> Page 16, 17)
-- Use Case 2d: Model Lifecycle Inspection (Xerox requirements.pdf -> Page 18, 19)
-- Use Case 2e: Model Lifecycle Data Analysis (Xerox requirements.pdf -> Page 20)
Dashboard
- Presents a dashboard that shows the device's current state (configured / not configured; configuration name; under contract / not under contract and the history of those states)
03) Xerox Sales Person Screen
Wireframes Page 6
- This screen is for Xerox Sales Person to create a contract for particular Xerox device
- As a Xerox salesperson, I want to be able to document a device's contracted entitlements (in a Xerox contract database) so that Xerox and the customer will both be able to understand and agree to their contractual obligations related to that device in practice
- Default form field will be Model name, Device Serial Number (Ready to Ship, Manufacture Pending), Device Services
- If user choose "Ready to Ship" in Device serial number, show the additional "Ready to Ship" form
- If user chooses "Manufacture Pending" in Device serial number, show the additional "Manufacture Pending" form
- Once User filled all form fields and click submit, show success message.
04) Xerox Configuration Engineer Screen
Wireframes Page 7
- This screen is for Xerox Engineer to configure particular Xerox device
- As a Xerox configuration engineer working in a Xerox warehouse, I want to configure a device according to the appropriate specifications and record that configuration (in a device configuration database) so that the configuration can be replicated or restored if necessary in the future.
- Default form fields will be: Model Name, Device Serial Number, Standard Configuration, Firmware Version, Non-Standard Configuration
- Once user click submit, show the success message
05) Xerox Customer Screen
Wireframes Page 8
- This screen is for Xerox customer to confirm that the device has been received
- As a Xerox customer, I want to record in (in my company's equipment inventory database) that a shipping carrier has delivered a particular device to my company so that we can confirm that the device was delivered as agreed.
- Default form fields will be: Model Name, Device Serial Number, Delivered Date, Delivered Time, Customer Facility, Customer/Employee Name
- Once user click submit, show the success message
06) Xerox - Rigger Screen
Wireframes Page 10
- This screen is for Xerox Rigger to configure Xerox devices
- As a Xerox rigger, I want to be able to record (in a Xerox Service database) that I have installed a device at a customer site and to record the customer’s confirmation that the device is working as expected so that Xerox is protected from potential legal disagreements about Xerox’s contractual obligations (e.g. related to device installation date) with the customer in the future.
- Default form fields will be: Model Name, Device Serial Number, Installation Date, Installation Time, Rigger Name (read only, populated from db), Select Customer, Select Facility, Device Room Number/Name
- Once user click submit, show the success message
07) Xerox - Shipping Carrier Screen - Manufacture to Xerox
Wireframes Page 11
- This screen is for Xerox Shipping Carrier to confirmed about device picked up
- As an employee of a shipping carrier, I want to record (in my company's database) my confirmation that I have picked up a particular device from a Xerox warehouse for delivery to a Xerox customer site so that I can have legal confirmation that the device is on-route to the specific customer site.
- Default form fields will be: Model name, Device serial number, Pickup date, Pickup time, Carrier Company (read only, populated from db), carrier company address, destination xerox address, xerox employee name, xerox employee contract number
- Once user click submit, show the success message
08) Manufacture Company - Factory Engineer Screen
Wireframes Page 14
- This screen is for Xerox manufacturer to add and mark Xerox devices
- As a manufacturing quality assurance engineer for a vendor that manufactures Xerox-branded multifunction devices, I want to record (in my company’s database) my confirmation that a particular device has passed all its qualifications so that it can be shipped to Xerox for addition to its warehouse inventory.
- There will be 2 tabs in this screen, Mark Device Complete and Add New Devices:
-- Add New Devices, form fields will be: Model Name, Device State, Manufacture Date. Once user click submit, show the success message for each tab
-- Mark Device Complete, user will be able to search model using selectbox or doing free search text, and the result will be shown in table below it. User will be able to select one or any particular models and mark it as complete. Once user click submit, show the success message for each tab
Important:
- Keep things consistent. This means all graphics styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to fajar.mln@gmail.com (Challenge Copilot)
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment this link while you upload).
Target Audience
- Analysts (Admin/Partner, Analytics for Admin/Partner)
- Value Chain Drivers (Manufacturer, QA Engineer, Shipping Carrier 1, Xerox Warehouse Employee, Sales Person, Config Engineer, Delivery, Shipping Carrier 2, Customer, Rigger)
Target Devices
- Desktop: Minimum 1366px Width & Height up to your design
- Your design needs to consider for Bigger Screen Resolution
Documentation
- Static Wireframes (Static Wireframes.pdf)
- Functional Documents (Xerox requirements.docx)
- Xerox Logo description
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- The overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
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 image files based on Challenge submission requirements stated above
- MarvelApp link for review and to provide feedback
Source Files
All source files of all graphics created in either Adobe Photoshop, Illustrator (might need to convert it to photoshop later), XD, or Sketch and saved as editable layer
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colours) or modify overall colours.
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.