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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to PGP Wegmans Portal Wireframe challenge.

In this challenge, we are looking for wireframe (Axure) solutions based on requirements from our client. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!

At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.

Round 1

Submit your initial wireframes for Checkpoint feedback
3. Search results screen.
Notes.jpg: Any comments about your design for the Client

Round 2

Your Final wireframes for all the required pages with all checkpoint feedback implemented.
1. Login Screen.
2. Store look up screen.
3. Search results screen.
Notes.jpg: Any comments about your design for the Client


About Project:
Our client, PGP (P&G Professional) is looking for fresh look for their new portal that they are contracting us for to service their client Wegmans. The portal in the end will be built on Salesforce Communities and leveraged via iPads. Their leadership staff and service agents will be the ends users. The portal in the end will enable the end users to submit service tickets, review the tickets and the ability to review checklists. All of which is critical to the success of the operation as a whole and drive a better UX for the users.

As stated above, the functionality that the portal will support at a high-level is:
Submit tickets
Review specific tickets
View checklists (a survey of sorts)

Style Theme:
We'd like to have a clean and simple design.

Wireframe Expectations:
Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
You MUST cover all use cases mentioned in challenge details below.
You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.

Supporting Documents:
- Screenshots (Wegmans_Portal.pdf.zip).

Note: There was a rough design concept done recently that was a starting point, however we want to take it back to wireframes and go through a more rigorous iteration of design/UI development to gather the best results. That PDF is attached, as a disclaimer we don’t need some of those screens such as the zip code look up etc. Only looking for the meat and potatoes if you will at this time.

Screen Size:
- Desktop/iPad 1024px width and height as required.

Suggested Screens:
We are looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions! Here are some of the items that we think should be included:

  1. Login Screen
    1. User should be able to provide his email address and password.
    2. We need “Don’t have an account?” & “Forgot password?” links.
    3. We need a sign in button.
  2. Store look up Screen
    1. We need a store look up by store number.
  3. Search Results Screen
    1. Show the store found.
    2. In this screen we will have three main options:
      1. Create Service Request
        1. Fields:
          1. Region
          2. Store
          3. Department
          4. Date Reported
          5. RSC Case number
          6. Equipment type
          7. Issue Reported
      2. View Wegmans Data
        1. Two different Service Ticket types that are essentially cases [Warewash and Sanitation
        2. List view with filters
        3. Fields:
          1. Region
          2. Store
          3. Department
          4. Date Reported
          5. RSC Case number
          6. Equipment type
          7. Issue Reported
          8. Resolution Status
      3. View PM Checklist
        1. Very similar to a survey
        2. Broken down by department
        3. Should only be one for the entire store’s checklist
        4. Structure
          1. Department:
          2. Area:
            1. Floor
            2. Shelves
            3. Storeroom
            4. Checkout
            5. Bathroom
          3. These areas will have sub fields or checklists that would open like an accordion or something (up to you)
            1. Rating 1-5 of upkeep?
            2. Sanitary 1-5
            3. Up to standard?

Target Audience:
Wegmans leadership staff.
Wegmans service agents.

Judging Criteria:
Your submission will be judged on the following criteria:
User experience
Completeness and accuracy of the areas of functionality and content
How well your wireframes provide a consistent user flow and clear information architecture for the application

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:

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

5 submissions

ID: 30045600