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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the Styx - MCS Upgrade Thick Client Application Wireframes! Styx provides a Key Management system for tracking users of mechanical keys. They expects to replace the existing Manufacturing Control System (MCS) which is a C++ / MFC / C# / SQL Server application by reverse engineering the existing application and splitting functionality into a web application and a thick client application(windows forms application). For this contest, the client is looking clean, simple, impressive and user-friendly  wireframe design for the thick client application.

Round 1

1) Initial wireframe for the following pages:

View Home Screen
View Orders, View Products, and View Cartons
Manage Station Records
Configure Stations
Assign Orders and Products to Station
View Returns History
Perform Searching

2) Any note for the client about your submission

Round 2

1) Final wireframe submission with all the features mentioned in the Requirement section
2) Any note for the client about your submission

 

 


Primary Goal & Design Considerations

For this contest, you are going to create the wireframes for for Styx - MCS upgrade thick client application based from the provided conceptualization document, and with the features outlined below.

Requirement

We need the following screens and features. Please refer to provdied conceptualization document while working on this contest.

Login/Logout
- The registered users can login by providing his/her credentials (like user name and password).
- The Worker can perform logout from this MCS Client application to ensure high security.
- More details can be found in the conceptualization
View Home Screen
- The application will provide a useful home screen to the Worker after login.
- The user can get the most important information on that page – like summary data on orders, products, cartons, assignments to the station, returns, etc.
View Help
- The Worker can easily get help information on the MCS Client application usage.
View Orders, View Products, and View Cartons
- For the worker, they can view orders/products/cartons and can't edit them.
Manage Station Records
- The Worker can freely manage all the MCS station in the system.
- The Worker can manage the type of the station (i.e. create, edit, delete, or view list and detailed page) and assign the proper type to the related station.
Configure Stations
- The Worker can freely configure all the options of the MCS Stations.
- The Worker can configure error codes and types (i.e. error type and description) for the programming – those codes can be created, edited, removed, viewed (as a list or on a detailed page).
- For more details, please refer to the conceptualization document.
Assign Products to Station
- The Worker will be able to assign his/her MCS station for some products.
Scan/Enter Serial Number
- The Worker can manually enter the serial number information of the device, key, or accessory to the application if needed (like if the bar code scanner is not available)
- The Worker can scan bar code with the serial number information of the device, key, or accessory by using a special scanner
Program Devices/Keys Pages
- The Worker can perform programming of the manufactured device by using the PB attached to his/her MCS station.
- The Worker can perform programming of the manufactured key by using the PB attached to his/her MCS station or directly (if the key has USB interface).
- Please refer to conceptualization document for more details.
Diagnose Devices/Keys
- The Worker can perform diagnostic on the programmed devices and keys.
Manage Device/Key/Accessory Returns
- The Worker can fully manage returned keys/devices/accessories.
- please refer to section 4.4.40, 4.4.41 and 4.4.42 for more details
View Returns History
- The Worker can view all the history on the returns of products.
- The information about product type, serial number, date/time of returning and the details of the related product will be available.
Print Label
- The Worker can print labels for accessories or programmed devices/keys on a EK, DK, SK, or Special label printers.
- The label will be printed and can be attached to the related product by the Worker.
Perform Searching
- The Worker can search for all the data in the MCS system.
- Please note, searching can be used as a part of any user task in the MCS Client application, or it can be called as an individual function.
Print Screens
- The Worker will be able to print any screen of the MCS Client application (like orders, products, assignments, some configuration, etc.) on the regular printer (not on the label printer).
Integrate with PB/Label Printers/Scanner/USB Keys

Export Fulfilled Orders and Products to LeniDB
- Note that LeniDB and KIM Pods are the same things
Upload Programmed Products to KIM Pods
- Note that LeniDB and KIM Pods are the same things
Localize GUI Screens
- The Client application system will automatically retrieve all the needed internationalized strings from the existing DLL.

Target Audience
- Worker

Judging Criteria
Your submission will be judged on the following criteria:
- User Experience
- Completeness and accuracy of the wireframe as defined in the 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
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
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.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

 

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:

2012 TopCoder(R) 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

5 submissions

ID: 30025923