Challenge Summary
- Entity Onboarding section: Where new roles and users can be granted access to the network, and a running list of currently on-boarded members (either from within the same company or other companies).
- Asset Definition section: Where new assets, their attributes etc. are defined, and a running list of all on-boarded assets
- Process Modeler: Where the relationship between the onboarded entities and the assets is created.
- These sections may be either on a single page or spread across multiple pages. Each section should be very easy for the users for them to work on it on a daily basis without fatigue or boredom.
These screens are expected to have hundreds of entries within each section. So please plan accordingly. Make it very easy for the users to filter through and manage such huge volumes.
Round 1
For the first round provide the initial designs for the following screens:1) Entity Onboarding
2) Asset Definition
3) Process Modeler
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask in the Forum for a MarvelApp prototype link. You will receive 1 MarvelApp prototype for Mobile.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
Round 2
For the first round provide the final designs for the following screens:1) Entity Onboarding
2) Asset Definition
3) Process Modeler
- Important: As part of your final submission, you must update your submission to MarvelApp.
- Use the same MarvelApp prototype you received in checkpoint.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
Project Background
Client is creating a self-help setup and management tool for its customers to manage their global supply chain networks. These supply chain networks will span across almost all major industries: manufacturing, consumers, healthcare, government/regulatory, insurance, finance etc. and has numerous challenges that can be addressed using blockchain. We believe that customers need a mature production grade supply chain blockchain management setup in order to convince them towards adoption. This web page will be main User Interface for the Blockchain Supply Chain platform. This will allow them to configure their own networks, invite new partners/users, define assets, custom define their processes and alerts, create, track, manage and take actions against all their shipments.
Screens/Features
While the following screens are a starting point, please feel free to add any other screen that actually improves your UX based on your concept.
1) Entity Onboarding
This will have the following main sections:
a. Roles: These are all the roles that will be defined for within the company.
i. This should show the list of all existing roles, with search options. It should show the following fields, with an edit and save option:
- Role Name: example – Admin/Attester/ etc…
- Role Description: text field
ii. Option to create a new role within my organization. It should capture the following fields, with a save option:
- Role Name: example – Admin/Attester/ etc…
- Role Description: text field
b. Users: These are all the users from within the same company and the admin user from the other companies that are part of the supply chain network
i. This should show the list of all existing users within the company, with search options. It should show the following fields, with an edit and save option:
- Username
- Role
- Public Key (this will be a 256 character long text – so no need to show the entire text, show only partial text with an option to copy or create QR code with it)
ii. Option to create a new user within my organization. It should capture the following fields, with a save option:
- Username
- Email ID
- Role
- Password
- Confirm password
iii. The list of admins from other companies. This is just read only with no option to make changes to it.
- Username
- Email ID
- Company Name
- Company Role: example – manufacturer/logistics/warehouse/retailer etc
2) Asset Definition
This will have the following main sections:
a. This should show the list of all existing assets relevant to the company, with search options. It should show the following fields, with an edit and save option:
i. Asset Type ID
ii. Asset Type: example – cars/drugs/food/phone etc.
iii. Asset Description
b. Option to create a new user within my organization. It should capture the following fields, with a save option:
i. Asset Type Name
ii. Asset Description
iii. Attributes: This should be dynamically be selected by the user based on their choice from the various types of attributes such as: Numbers/Text/Dropdowns/Radio buttons/Files/GPS location etc. There will be 5-10 options for the user to choose from. Each of these attributes are assigned to the asset type.
3) Process Modeler
This will map the relationship between the entities and the assets:
a. This should show the list of all existing processes, with search options. It should show the following fields, with an edit and save option:
i. Process ID
ii. Process Description
b. Option to create a new supply chain process. It should capture the following fields, with a save option:
i. Select the asset/s from the existing assets list, example – car
ii. Select the entities from the existing companies list: example – manufacturerA, logisticsB, warehouseC
iii. Create a way to show which asset will travel from which entity to the next: example – car will travel from the manufacturer A to logistics B to warehouse. These options can easily get very complicated and very long depending on the number of entities and assets involved. One such typical example of the complexity is as shown on this sample.
Key Areas to Focus
- You should focus on creating an interactive webpage to display all its capabilities and flexibility. The user will use these screens for their daily operations.
- There is no restriction on the number of screens as long as the basic purpose of the website is fulfilled. Each section will have their own corresponding visual stats.
- This is a “White Label” design, this means that you will need to create the branding for your design. Think on:
- Professional and Clean Design
- Easy to Read
- Contrast
Please make sure your design supports the following roles.
- Supply Chain Customers = Public Access for customer
Form Factors
- For this challenge you will be working on creating the design concepts for these form factors:
- Desktop Web Application: Standard 1280px width and height increased if necessary.
- Out of scope (DO NOT DESIGN THIS)
- Tablet portrait and landscape
- Mobile portrait and landscape
Operating Systems
- Web Desktop Browsers
Branding Guidelines
- Branding is fully open to this challenge.
- Have in mind that will as the winner to create a Branding Document after this challenge ends. This new branding document will be used on follow up challenges.
- For the logo, use a placeholder with name “Supply Chain Customer Biz”
Final Deliverables
- All original source files.
- Files should be created in Adobe Photoshop and saved as a layered PSD file, Adobe Illustrator or as a layered AI file, Sketch or XD.
- Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to challenge copilot in the forum using the correct thread for this.
- You MUST include your Marvel app URL as a text file in your final submission labeled “MarvelApp URL” (in your marvel app prototype, click on share and then copy the link).
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.