Challenge Summary
We need to see intuitive and easy to use "wireframe concepts" that will let us design and build the final user interfaces in the next stage of this project.
Think about what are the best UI/UX practices when creating this wireframe. This will be the first challenge of a very large project, so have in mind that your initial concepts will be the starting point and the base for this project.
Round 1
Submit your initial wireframes for the checkpoint review.
1. Persona: End Customer
2. Persona: Leasing Partner
3. Persona: Supply Chain Team
Feel free to add any screens which are necessary to explain your concept
Round 2
Submit your final wireframes plus checkpoint feedback implemented.
1. Persona: End Customer
2. Persona: Leasing Partner
3. Persona: Supply Chain Team
4. Persona: Installation Partner
5. Persona: Factory / Manufacturing Unit
Feel free to add any screens which are necessary to explain your concept
We need you to develop a “wireframe concepts” for the provided overall user flow on what happens when a typical end customer orders for electronic device(s), subsequent flows and various other personas related user flows.
Keep in mind, this web application will be a responsive - so think through that!
Background Information:
Client of this challenge is a global electronic device and its related components manufacturer. They would like to improve the efficiency/turn around time in their manufacturing related supply chain sub-process(s) and ensure its transparency by providing the status of electronic device(s) / component(s) at various stages, visible to all the concerned stakeholders through the digital technologies like Blockchain and form the block chain consortium among the various stakeholders as mentioned below.
Currently, the sub processes like Invoicing process and Asset Tracking are considered.
There are about 5 users personas, as the list below will be using this application and you will be creating user flow/screens for each of them. NOTE: Some of the screens will be common among the users - so please make sure your screens are consistent.
1. Persona: End Customer
2. Persona: Leasing Partner
3. Persona: Supply Chain Team
4. Persona: Installation Partner
5. Persona: Factory / Manufacturing Unit
Required user Flows and Required Screens:
Screen _ 01 ) Common Login Screen (only by Authorized users)
- Username and Password,
- Forgot password
Screen _ 02 ) Required features for Customer (Gary):
1. Dashboard
- Once logged in, Gary would see this landing page where he would see all the status, and activities / tasks required action
1.2. Status : – Gary sees status of order & items, invoice, acceptance, agreement regarding his electronic device(s)
1.2.1 Order:
- List of All Orders including items with Status (Open, In Process, Closed)
- Actions - View
1.2.2 Invoice:
- List of Invoices with Status (Active, Cancelled)
- Actions: View
1.2.3 Acceptance:
- List of acceptance with the status ( Not accepted, Accepted)
- Actions - View, Sign acceptance
1.2.3.1 Acceptance by agreement:
- Actions - View, Sign acceptance by agreement
2) Signing of acceptance, acceptance by agreement : System should provide an option to sign off the acceptance and acceptance by agreement. On successful, acceptance, the status need to be set to “accepted”.
3) Basic Search capability
Screen_03) Required features for Leasing Partner (Nate):
1. Dashboard
Once logged in, Nate would see this landing page where he would see all the status, and activities / tasks required actions.
1.2. Status: Nate sees all information regarding the orders
1.2,1 Orders
- List of All Orders including items with Status (Open, In Process, Closed)
- Actions - View
1.2.2 Acceptance
Acceptance:
- List of acceptance with the status ( Not accepted, Accepted)
- Actions - View
Acceptance by agreement:
- Actions - View, Create
2.3 Invoices
- List of all Invoices with Status (Active, Cancelled)
- Actions - View
2) Generate New Acceptance by agreement:
- He should be able to generate new acceptance by agreement as per the format given in the sample data sheet
3) Basic Search capability
Screen _ 04 ) Required features for Supply Chain Team (TOM) :
1. Dashboard
Once logged in, Tom would see this landing page where he would see all the status, and activities / tasks required actions.
1.2. Status: Tom sees all information regarding the ordersOrders
1.2.1 List of All Orders with Status ( Open, In Process, Closed)
- Actions - View
1.2.2 Acceptance
Acceptance:
- List of acceptance with the status ( Not accepted, Accepted)
- Actions - View, Create
Acceptance by agreement:
Actions - View
1.2.3 Invoices
- List of All Invoices with Status (Active, Cancelled)
- Actions - View | Edit | “Create New Invoice”
2. Create New Invoice
- Tom would be able to generate New Invoice from this page for specific orders and able to cancel the invoices also. Default status for the invoice would be Active on creation and would be changed cancel on cancellation of the invoice.
3. Create new Agreement
- Tom would be able to generate new agreement from this page for the specific/ selected orders / items. Default status for the acceptance would be Not accepted.
4. Basic Search capability
Screen _ 05 ) Required Screens for Installation Partner (David):
1. Dashboard
- Once logged in, David would see this landing page where he would see all the status, and activities / tasks required actions
1.2. Orders – David sees all information regarding the Order
1.2.1 List of All Orders with Status (Open, In Process, Closed)
- Actions - View
1.2.2 Acceptance
List of acceptance with the status ( Not accepted, Accepted)
Actions - View
3. Basic Search capability
Screen _ 06 ) Required Screens for Factory / Manufacturing Unit (LEO)
1. Dashboard
Once logged in, Leo would see this landing page where he would see all the status, and activities / tasks required actions
1.2. Orders – Leo sees all information regarding the orders
1.2.1 - List of All Orders with Status (Open, In Process, Closed)
- Actions - View,
1.2.2 Acceptance
- List of acceptance with the status ( Not accepted, Accepted)
- Actions - View
3. Basic Search capability
Target Users
- Corporates Companies
- Supply Chain Team
- Leasing Companies
- Software Installers
- Device Manufacturer
Tools Sketch / HTML:
- We are asking to work with Axure: http://www.axure.com/support
- You can also work with static images but you must include a fully navigable prototype in HTML.
NOTE: If you are designing in the sketch or Adobe XD then it is mandatory that you create the flow using Marvelapp / Invision as we are expecting to see a clickable wireframe in this challenge.
- You are also allowed to submit pure HTML wireframes
- For sample data, more user flow, data element and its hierarchy, please request for more details in the forum.
Judging Criteria
- User Experience of the application/editor
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
- This is a data heavy application. Ease of actions and views takes priority
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
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
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.