ico-arrow-big-left

NASA - REALM System - Item Management Wireframe Challenge

Key Information

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

Register
Submit
The challenge is finished.
Show Deadlines

Challenge Summary

Welcome to NASA - REALM System - Item Management Wireframe Challenge!

A User Interface (UI) application is needed to interact with a university developed Complex Event Processing (CEP) System. The UI application abstracts, simplifies, and provides necessary data translation between groups of users and the CEP system.

This is the first challenge in a series of challenges to build the User Interface, in this challenge we will be focusing on Item Management.

Round 1

Round One (1)
- Submit your initial wireframe solution for checkpoint feedback.
- Submit an initial version of your solution.
Notes.jpg: Any comments about your design for the Client.

Round 2

Round Two (2)
- Submit final wireframe solution plus checkpoint feedback.
- Submit final version of your solution.
Notes.jpg: Any comments about your design for the Client.

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.

Full Description & Project Guide

Background of the problem:
Radio Frequency Identification (RFID) ­enabled Autonomous Logistics Management (REALM) is an International Space Station (ISS) experiment directed at demonstrating the ability to use RFID and complex event processing (CEP) related technologies to better localize items on the ISS, and for demonstrating and evolving the technology for Exploration use. The current Inventory Management System (IMS) on ISS is heavily dependent upon crew involvement for finding and cataloging item location(s) within ISS. The storage environment, the number of items, the fact that items do not always stay where a crewmember last put them, and the varied requirements for running experiments makes conducting operations challenging; particularly since the crew and operations are highly scheduled on ISS.
 
To address the evolving inventory and challenges associated with the current system, the REALM system; enabled by RFID and CEP is being developed. The CEP system interacts with the raw RFID data reads from six RFID readers deployed at locations in three of the ISS modules. The CEP system infers the state of RFID tagged items on ISS and needs to be able to convey this information to users of the REALM system, in a manner that is usable to the REALM system team members and the Inventory Stowage Officers (ISOs). See Attachment 1 “System Use Case Scenarios” which provide additional detail about the REALM architecture and context for the UI software. The delivered software must address these scenarios and fit within the REALM architecture. See Attachment 2 “CEP System Interfaces” for information about the REALM architecture.

Challenge Description:
A viable solution is required to address all System User Case Scenarios for the system and the user application requirements. The solution can be web based or developed completely around a particular framework, e.g., Unity 3D, which can be run on a variety of platforms. The key is that the solution needs to be able to abstract all expected user interactions with the system, to provide the CEP system with the necessary and properly formatted inputs and accept outputs from the CEP system such that item location information is conveyed to a user.
We are looking for wireframe (Axure) solutions based on requirements below. 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.
 
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 screens mentioned in required sections below, if any requirement is missing in final submission the client will not look at it, so make a checklist for the required screens to make sure you designed all of them.
- Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
- 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.
Notes:
- Your wireframe submissions need to be able to drill down for all page flow.
- Show your wireframe solution for:
-- Desktop view: Design for desktop display 1280px and height as required.
- Please consider responsiveness while designing the solution as the client want the solution to be usable on mobile devices as well.
- Feel free to suggest any tools/functions that can bring good User Experience for this tool.

Challenge Goal:
- This challenge will focus on item specific features. The challenge will consider the input and search items required of users of different types, and define features for easy filtering, search refinement, etc.
- This challenge will also consider location rendering that will be provided by Unity3d mappings.

Required Features:
- Have the ability to enable an on demand search of the CEP system to determine an item's location.
- Have the ability to interface to a Unity 3D representation of the instrumented ISS modules to display location and location trajectories of item(s) queried.
- Enable on demand searches for either a single or multiple items; multiple items are delimited using commas.
- Have the ability to request a date range for the item(s) location history.
- Have the ability to query for an item(s) last M locations, where M is an integer valued variable.
- Have the ability to request an item(s) containment history.
- Have the ability to query for an item(s) last N containment relationships, where N is an integer valued variable.
- Have the ability to interface with an existing Inventory Management System (IMS); querying it for information needed to enable user interactions with the CEP system, whereby an item(s) location is requested, and the barcode(s) for item(s) are unknown or are not desired as a search term.
- UI application interfaces to the IMS system using the Open IMS API.
- UI application translates the CEP system provided locations (x, y, z) into a user understandable, rack level location of an item.

Supporting Documents:
- Attachment 1 - System Use Case Scenarios.pdf.zip; which provide additional detail about the REALM architecture and context for the UI software.
- Attachment 2 - CEP System Interfaces.pdf.zip; for information about the REALM architecture.
 
Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn
 
Target audience:
- RELAM Team.
- ISO Team.

Judging Criteria:
- User Experience of application.
- Completeness and accuracy of the wireframe as defined in the spec requirements.
- How well your wireframes provide a consistent user flow.

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

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.

Reliability Rating and Bonus

For challenges that have a reliability bonus, the bonus depends on the reliability rating at the moment of registration for that project. A participant with no previous projects is considered to have no reliability rating, and therefore gets no bonus. Reliability bonus does not apply to Digital Run winnings. Since reliability rating is based on the past 15 projects, it can only have 15 discrete values.
Read more.

ELIGIBLE EVENTS:

2017 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.

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