Challenge Summary
Welcome to the Meli - ACES Staging Screen Design Challenge.
In this challenge, we are looking to redesign a layout/screen based on the current design that will improve the speed and efficiency of the representative working with an input screen.
Good luck! We are looking forward to your designs!
Round 1
Submit your initial designs for Checkpoint Feedback
- ACES Staging Screen
Feel free to add any other additional screens which are necessary to explain your concept.
Notes.jpg: Please note any comments about your design for the Client
Round 2
Your Final designs for all the required designs with all Checkpoint Feedback implemented.
- ACES Staging Screen
- Please submit a documentaion about the flow of the screen!
Feel free to add any other additional screens which are necessary to explain your concept.
Notes.jpg: Please note any comments about your design for the Client
Challenge Description:
We are looking to create a layout for an input screen in SAP WEBDYNPRO. This screen will be used by the internal customer representative personnel to create and modify PDRs. PDR's refers to Pricing and Delivery Request - It's when customer send requests for quotes, PDR is created to process the request.
The purpose of the layout is to improve the speed and efficiency of the representative working with the PDR. The PDRs have four main functions:
- Input data
- Calculated results
- Display data
- Modify data
Design Guidelines:
- We would like you to follow the design styles shown in SAP WEBDYNPRO Screens.zip, and it must be easily supported by SAP WEBDYNPRO (Please follow the reference designs).
- Follow the colors given in Digital Primary Palette, the design must adhere to the digital primary palette esthetic. (make sure the red is used sparingly for label as it could denote an error).
- The design must help promote the speed and efficiency of the user.
- Feel free to suggest any user experience that would help the user.
Design Size:
The design layout must display well on a 14” screen at standard resolution and require no horizontal scrolling, vertical scrolling is fine (and expected)!
- 1280px width and height as required
Required Screen Elements:
Please see the provided ACES Staging Screen (ACES Staging Screen.png), this screen can be divided into three parts:
a) Header Level Information
b) Item Level Information
c) Data Processing
NOTE: The data flow is unidirectional from Header to Line item and Header & Line Item to Load Matrix, but any changes to Line Item will not impact Header data.
a) Header Level Information:
This part is shown in a. Header Level Information.png
ACES Type Selection via Radio Buttons:
- Create New PDRs (SFDC Case Number - 10 digit text field)
- Create data entry (SFDC Case Number - 10 digit text field)
- Update existing PDR (PDR Number -10 digit text field)
���
ACES Type Section Display (Labels):
- SFDC Case Number (10 digit display)
- PDR Number (10 digit display)
Sold to Customer Address:
Provide a single address field of length 25 characters. At the end of the Address field, provide display an icon to click and view the full address of the customer on a pop-up screen (within this pop-up, we need below fields)
- - Name (20 digit text field)
- - Attention (20 digit text field)
- - Street Address (20 digit text field)
- - Suite (10 digit text field)
- - City (10 digit text field)
- - State (2 digit text field)
- - Zip Code (10 digit text field)
- - Country (20 digit text field)
Ship to Customer Address:
Provide a single address field of length 25 characters. At the end of the Address field, provide display an icon to click and view the full address of the customer on a pop-up screen (within this pop-up, we need below fields)
- - Name (20 digit text field)
- - Attention (20 digit text field)
- - Street Address (20 digit text field)
- - Suite (10 digit text field)
- - City (10 digit text field)
- - State (2 digit text field)
- - Zip Code (10 digit text field)
- - Country (20 digit text field)
Other fields:
- Customer Contact ID (20 digit text field)
- Customer Contact Name (20 digit text field)
- Customer Contact email (20 digit text field)
- Payment Terms (4 digit text field - 20 digit character description)
- Incoterms - Dropdown menu (3 digit text field, 10 digit character description)
- SBU - dropdown menu (3 digit text field)
- End Use (default to items) - Dropdown menu (4 digit text field)
- Sales Org (default to items) - Dropdown menu (4 digit text field)
- RFQ Number (10 digit text field)
- Solicitation Number (10 digit text field)
- Contract Number (10 digit text field)
- Estimate Type (Dropdown menu)
- Price Type (Dropdown menu)
- Program Name/App (Dropdown menu)
- OM Team (10 digit text field)
- Administrator (10 digit text field)
- Currency (4 digit text field)
- Document Type - Dropdown menu (3 digit text field)
- Workflow - Dropdown menu (3 digit text field)
- Received Date (Date field)
- Quote Due Date (Date field)
- Required Delivery (Date field)
- Partial Quote Allowed (Check box)
- Days Valid (3 digit text field)
- Access Class (10 digit text field)
- PDR Number (10 digit text field)
Actions:
- Clone Header (Button)
- Save Header (Button)
b) Item Level Information
This part is shown in b. Item Level Information.png
Top Level:
- National Stock Number (Radio Button - 10 digit text field)
- Batch Upload Parts (Button)
Table Level:
- We need a way to hide and reveal columns so the user can customize his view
- We want to have vertical scrolling, but avoid horizontal scrolling
- - Select Parts (Radio Button)
- - Part Number (18 digit text field)
- - Quantity (5 digit text field)
- - Material Description (40 digit display)
- - Costing Site (4 digit display)
- - Quoting Site (4 digit text field)
- - MP# Type (1 digit display)
- - Plant-sp Matl Stat (2 digit display)
- - Demand PFEP (5 digit display)
- - Dchain Spec-Stat (5 digit display)
- - Material Info (Button)
- - End Use (Dropdown menu - 4 digit text field)
- - Work Scope (10 digit display)
- - DC (2 digit display)
- - Sales Office (4 digit display)
- - LI Estimator (10 digit display)
- - Item Reqd Date (Date display)
- - Calculated Dely Date (Date display)
- - Replacement Part (10 digit display)
- - LI Status (10 digit display)
c) Data Processing:
This part is shown in c. Data Processing.png
Interactive Elements
- Delete Items (Button)
- Refresh Master Data Radio Buttons (Select Items, All Items)
- Acro PDM (Link)
- Haystack (Link)
- HIA to Mat’l Coordination (Launch email)
- Save Header and Items (Button)
- Load DC, Sales Office Info (Button)
- Generate PDRs (Button)
- Go to PDRs Search (Button)
Table Display
- End User (5 digit display)
- Distr Channel (2 digit display)
- Sales Office (4 digit display)
- Sales Org (4 digit display)
- Workflow (10 digit display)
- PDR Number (5 digit display)
Target Audience:
- Internal customer representative personnel
Judging Criteria:
We will be judging on:
- How well does your design align with the objectives of the challenge
- How well does your design fit in with SAP WEBDYNPRO
- How well does your design align with the overall company branding
- How well does your design increase speed and efficiency of the user
- Cleanliness of your graphics and design
- Overall Design and User Experience
Submissions and 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 for your submission files.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.
Final Fixes
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback. 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.