Styx - Global Production Commissioning Application Wireframes Contest 2nd Phase

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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Styx - Global Production Commissioning Application Wireframes Contest 2nd Phase. The client of this application would like to build a web site that is used by STYX internal resources, external distributors and representatives to generate and store of data associated to the installation and parameterization of the products at the customers’ sites. This data is known as commissioning data, as it is part of the product commissioning process. The data is organized into sets of objects, each holding a specific value.

Round 1

NOTE: you should finish your design based on the original Wireframe, because the original wireframe relates to the requirements in this contest, it is your responsibility to  integrate them.  Please also consider the requirements from 4.4.1 to 4.4.22, it may need some adjustment.
4.4.23    Manage Commissioning Data Definitions
4.4.24    Manage Products
4.4.25    Manage Product Versions
4.4.26    Manage Commissioning Data List
4.4.28    Manage Customers
4.4.29    Manage Customer Sites
4.4.30    Manage Business Units
4.4.31    Manage User List
4.4.32    Manage Product List

Round 2

NOTE: you should finish your design based on the original Wireframe, because the original wireframe relates to the requirements in this contest, it is your responsibility to  integrate them.  Please also consider the requirements from 4.4.1 to 4.4.22, it may need some adjustment.
All Required uses cases from Round 1
4.4.27    Set Commissioning Data Default Values
4.4.33    Merge Business Units
4.4.34    Manage Users
4.4.35    Manage User Permissions
4.4.36    Archive Audit Records
4.4.37    Archive Logs
4.4.38    Configure Application


Onity operates as a global company leveraging both internal resources and distributors/representatives as needed.   A key step while selling a product is to generate and store (for later retrieval) a set of data objects (referred to as "commissioning data") used to install the system.

These objects can vary widely in nature such as: 
•  the customer ID and contact information, 
•  a site code to identify equipment at a customer site, 
•  a licensing key to enable functions in the product
•  a "default data" set to initialize functions in the product

Onity is in need of a commissioning system to generate, store, view and revision control these objects. These objects are key to upgrading customer systems either with new features or to replace a system in case of a catastrophic failure at the customer site.  Due to the nature of the business, the objects may be generated either  internally within Onity or externally at distributors'  facilities.   In  the past, the objects were not centrally stored.  Upgrading or replacing a system  involved  long searches for the data objects and in many cases the complete recreation of the objects.  This is not only inefficient but also represents undesirable  business practices,  such as issuing  two licenses or two site codes for the same customer since the original cannot be retrieved.

 The primary goal of this contest is continuation wireframe from our 1st Phase contest, the scope of this contest is from 4.4.23 to 4.4.38. You need create some way to access new pages as stated in the contest requirements on existing pages. Make sure they have proper link flow.

Target Audience

1. User
A STYX employee or representative that will use the application to generate and manage the commissioning data associated to product deployment and maintenance.
2. Super User
It represents a special user that will have enabled permissions for all the application features. There will be a single Super User on the system, and it won’t be possible to delete it or change its permissions.
3. Application Developer
It represents a STYX developer that will be responsible of creating Commissioning Data Modules and integrate them with the application.

 

Judging Criteria

1. Completeness and accuracy of the wireframe as defined in the attached requirements.
2. How well your wireframes provides a consistent user flow.
3. How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the clients).

 

Submission & Source Files Requirements:

Preview Image
Create a 1024x1024 JPG or PNG file and place a screenshot from your submission within it.

Submission File
All requested contest requirements/screens as clickable HTML files unless otherwise stated in the contest details.

Source Files
All original source files of the wireframe (such as Axure .rp files) as required by the contest.

Final Fixes 
As part of the final fixes phase you may be asked to modify your Wireframes.

 

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: 30024901