BONUS: 4‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

The client for this project runs a business where they fill and ship containers of liquid helium.  The current process of planning and scheduling container fills and shipments is partially done via their existing web application (ASP.NET 3.5), but it also includes manual steps.  The goal for this project is to build a new Production Planning web application that works with the existing web app and removes the manual steps in the process of creating the “Fill and Ship” schedule.

For this contest, we need you to create Wireframes for the new Production Planning web application.

We look forward to seeing your creative designs!

Round 1

Round 1 will focus on the following user functionality for the SAS web application:

1) Home Screen - The home screen for the new web application, which should also demonstrate how the new web application fits in to the existing system.
2) Dashboard - The dashboard provides the user with the ability to view all the data from the existing system necessary to create the Fill and Ship schedule.
3) Fill and Ship Schedule: Calendar View - This screen allows the user to create / edit the draft Fill and Ship schedule using drag-and-drop commands on a calendar.
4) Fill and Ship Schedule: Table View - This screen allows the user to create / edit the draft Fill and Ship schedule using a table view with rows and columns for data.

NOTE: See the requirements in the Conceptualization document to understand what functionality is needed for the new Production Planning system.  If anything is unclear, please ask for clarification on the forum and we will be happy to help!

Round 2

In Round 2, you will need to include all Round 1 screens (updated based on milestone feedback).  For Round 2, you must also include all the remaining functionality descibed in the project documentation.


Primary Goals:
The goal of this project is to design and develop a new Production Planning web based application that fits into the existing web application.

For this challenge, we are asking you to put together wireframes for the new Production Planning web application.  The requirements for the Production Planning web application are detailed in the attached documentation.

The screen shots located in the Conceptualization document show the type of data collected by the existing web application.  The requirements in the Conceptualization document also explains what functionality the new Production Planning system.  In particular, we are looking for your creative designs for the drag-and-drop Calendar view (for editing a draft version of the Fill and Ship schedule), and the dashboard view that displays the data from the existing system so the users of the new application have access to the information necessary to create the Fill and Ship schedule.

General Requirements:

- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The web application must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all use cases mentioned and described in the project document.
- The new web application MUST fit in with the existing web application.  The new web application needs to match the look-and-feel of the existing logistics system.
- Your wireframe must represents all pages and flows from project documentation. You should use that as a guide, but if there is better way to display any information, feel free to reflect that on your wireframe.
- You must use wireframes notes on every single page you design to explain what items are addressed on that page, what things you added/changed/removed, and to make your idea easier to understand so the client can provide constructive feedback.
- IMPORTANT NOTE: Logistics Planners have dual 24" monitors and that would allow them to make a "pop-out" screen containing alot more data than the normal header would allow. As the planner uses the planning screen, the popped out dashboard could be updated to reflect the schedule as drafted.

Project Description:

The client for this project runs a business where they fill and ship containers of liquid helium.  The current process of planning and scheduling container fills and shipments includes manual steps, such as adding data to Excel files.  For this project, the client is looking to create a web application that fits into their existing system and can be used to eliminate these manual steps and streamline the process of production planning for their liquid helium business.

The existing logistics planning system uses a combination of manual processes, including data from paper/excel spreadsheets and live data in the client’s existing production logistics system.  This current logistics system collects data from existing, client facing systems and orders entered via an order entry system.  All of this data will need to be consumed by the new web application.

On a weekly basis in the current process (or somewhat real-time when conditions change), logistics personnel will gather data from multiple different sources and make a draft schedule. If everything appears good with that draft schedule, they will create a “fill and ship” schedule to deliver to the client’s plants. This schedule tells the plant employees what container to fill, for which customer, and when to ship it. The plant employees are sent repeated schedules if there are any changes from unforeseen conditions.

The new web application will need to integrate with the existing systems and fill in the gaps where manual steps are currently involved.  The end product produced by the system will be the fill and ship schedule.

Project Documentation:

The following documents are attached to this challenge specification to explain what is required for the wireframes:

1. Conceptualization v2 - Helium Production Planning App - 7-31-14.zip:  Conceptualization Document explaining the project and new application requirements.
2. Proposed Dashboard.ppt:  A rough draft of what the proposed dashboard in the new application may look like (we are open to any ideas or improvements you can make to these screens).
3. ProPlanDocumentation.pdf:  Includes screenshots of the existing logistics planning system.
4. Existing App Screen Shots.docx:  Screenshots from the existing application

 

Wireframe Requirements:

Please see the Conceptualization document for detailed requirements and current system screenshots!  Below are some of the main requirements to help you understand the new Production Planning application being built:

- Dashboard: The dashboard provides the user with the ability to view all the data from the existing system necessary to create the Fill and Ship schedule.
- Calendar View: This screen allows the user to create a draft Fill and Ship schedule using drag-and-drop commands.

 

Look and Feel:

The new Production Planning web application MUST fit in with the existing web application.  The new web application needs to match the look-and-feel of the existing logistics system.

IMPORTANT: The attached Concepualization document and screenshots document includes examples of the existing logistics system. 

 

Target Audience
Existing users of the current logistics planning web application.

Judging Criteria
- User Experience
- Simplicity and Consistency
- Completeness and accuracy of the wireframe.
- How well your wireframes provide a consistent user flow.
- How well you implement the idea
- Any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)

What to Submit:
Preview JPG/PNG Image File
- 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 ZIP File
- All requested contest requirements as clickable HTML files generated by Axure.  All the content must be listed and the pages are linked together to show page flow.

Source ZIP File
- Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
- All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the side bar should be included in your Source zip file.

Final Fixes
- As part of the final fixes phase you may be asked to complete one round of minor changes to ensure your submission meets the stated requirements of this contest. 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.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2015 topcoder Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30043952