Challenge Summary
Welcome to the QPM Supplier Data Dashboard Wireframe Contest. The objective of this contest is to create the HTML wireframes for new QPM Supplier Data Dashboard based on provided conceptualization document.
In the end of this contest we are looking for a process flow and layout design of the pages mentioned below that are part of the whole application. This application must be user friendly, intuitive, and easy to use.
Round 1
Your submitted solution for client review.
A. User Functionality
B. Admin User Functionality
Any comments about your wireframe, make sure all pages have correct flow!
Round 2
Round Two (2)
Final pages of wireframe contains these functionality
A. User Functionality
B. Admin User Functionality
Any comments about your wireframe, make sure all pages have correct flow!
Contest Details
The purpose of this project is to build a new Supplier Data Dashboard application that will monitor files being received from suppliers (and processed by the current system). This wireframe contest is our first step to build the application, so we expected the wireframe capture the best layout and show any great User Experience that will help the app functionality.
QPM Supplier Data Dashboard Wireframe Requirements:
General
- Your wirefame solutions must useful. So, it can save a web designer so much time and energy!. All pages/elements must linked each others. Show us correct flow.
- The application will build as website application.
- Your wireframe must represents all pages and flows from Conceptualization_Document.doc. You should use that as a guide, but if there is better way to display information, feel free to reflected on your wireframe design.
- As possible we need capture all these functionality in less page, need your ideas how to present that in your wireframe.
- For any samples data need reprensent in your wireframe please check concept document.
- Feel free to suggest any idea to leverage User Experience of the application
A. User Functionality
1. View Help
- The application will display a simple help page with basic content for the user to browse through.
- The help page will include some technical information for anyone who wants to understand what the numbers in the dashboard mean.
2. View Overall Supplier Data
- This is default page after user logged in, this is dashboard of the application.
- Data displayed includes trend chart graphic
- The default view should give a glimpse of all suppliers/all commodities.
- The dashboard overview must display all the problems found (alerts) to allow the user to see problems at a glance.
- Commodity data can be viewed by day, week, month, or year
- Timeframe is selectable by user
- User will have the ability to drill down into lower level details
- The data available on the dashboard will be updated every time the application is run.
3. View Specific Commodity / Supplier Data
- The user *may* view data for a specific part number (or all part numbers)
- Commodity data can be viewed by day, week, month, or year
4. View Specific Part Data
- The user *may* view data for a specific supplier (or all)
- Commodity data can be viewed by day, week, month, or year
5. View ETL Failure Rates
- The user will select a specific supplier
- The application will calculate the ETL failure rate for the supplier
- The ETL Failure rate will be displayed.
B. Commodity Threshold Settings
Users can set threshold values to indicate when alerts will be triggered. Thresholds may apply to all parts within a commodity of specific part number. Users can view, create and remove thresholds. This portion of the UI is optional because it can be managed via an internal wiki, however an elegant configuration UI would be considered a big plus in the final judging.
Target Audience
Internal User.
Judging Criteria
- User Experience
- Completeness and accuracy of the wireframe as defined in the attached requirements.
- How well your wireframes provide a consistent user flow
- How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)
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. The resulting files are not critical in this contest. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.
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.