Auto CMO Excel Tool Replacement Wireframe Challenge

Welcome to Auto CMO Excel Tool Replacement Wireframe Challenge!

The purpose of this tool is to take the bond probe file (an input file containing security information) and display it in a customer web application so that we can identify securities that are not currently included in the bond probe process and monitor them to determine if they should be converted into the bond probe process. This is determined based on the market value of the securities and if they are priced below $xx.xx (a configurable amount). After securities are tracked to be pricing below $xx.xx for 30 days. If the security should be converted into the bond probe process (that process takes place outside of this tool). We use the output of the tool to track the responses and the required dates for quarterly follow ups.

Round 1

Submit your wireframe for a Checkpoint feedback
1. Login.
2. Main Functionality.
Notes.jpg: Any comments about your design for the Client.

Round 2

Final wireframe plus Checkpoint feedback
1. Login.
2. Main Functionality.
Notes.jpg: Any comments about your design for the Client.

Challenge Description:
The goal of this challenge is to take the existing excel  tool and convert it into a web application.

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 of the portal

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 (width 1280px and height as required).
- Feel free to suggest any tools/functions that can bring good User Experience for this tool.

Supporting Documents:
- Screen shots of the process (screenshots.zip).

User Roles:
- The application is required to have an Analyst role and a Read-Only role.
- Optionally, an Admin role can be added.

Design Consideration:
- The daily input file is large (around 20 K records). Your tool will need to have tools for viewing the large data sets, but also filtering down with minimal effort to the critical records.

Current Tool Description:
- An ASCII file in delimited format is delivered to the LAN by an internal application. The users open the Excel tool and hit the browse button. They will then navigate to the LAN folder, which is mapped as a drive on their system. They select the file to be processed (it will be for the prior business day as it is an overnight file). Once the file is selected, they hit the “Pull Data” button. This will parse the file and load the data in to the “Staging” tab and the “Import” tab. All headers etc. are created dynamically. The data in the “Import” tab is not used by the operations team. They only work on the “Staging” tab. The steps they go through are:
1. Select row #2 and enable Excel filters (“Data -> Filter”). Please refer Screenshot1.png.
2. Navigate to Column C (“99-20 Category”) and from the filter drop down select Securities that are marked as “NEW 99-20” and “NOT 99-20” and hit the “OK” button. Please refer Screenshot2.png.
3. Navigate to Column O (“Market Value Price”) and select all prices that are below 80 dollars. Please refer Screenshot3.png.
4. Manually highlight each unique Security with a different color (specific choice of color is not important, just that they be unique for easy identification) Please refer Screenshot4.png.
5. Comments are then manually added for each of the securities in the same color as the Security for easy association. Note that if a Security has shown up in the same list for multiple days, then the same color is applied for easy association and the number is manually incremented by 1. For ex: If the prior day comment for a given Security was “Pricing below $xx.xx day 4 of 30 – monitoring this”, if it was below $xx.xx the following day too, the Analyst comment would be “Pricing below $xx.xx day 5 of 30 – monitoring this”.
6. The Analyst will follow up with the Treasurer’s office for all Securities that hit the 30 day threshold on whether they should be “converted” (a separate process). The Treasurer’s office may ask to continue tracking and follow up by a certain date. The Analyst would track that in the comments section. As each day a new instance of the Excel Spreadsheet is used, any comments are manually carried forward (by opening the prior day’s instance of the spreadsheet and copying / pasting.
7. Once the manual follow ups are completed, the Spreadsheet is saved to the LAN folder. This is a manual step.

Required Functionality:
1. Login:
- Each user needs to sign in by filling:
-- Username.
-- Password.
-- Forgot password link.
-- Remember me checkbox.
-- Login button.
- Single Sign on should be supported.

2. Main Functionality:
- The Excel tool described above should be replaced by a web application.
- The application should have the concept of file dates, which represents all data associated with a specific business day:
-- The data that the app accepts will be related to a file day (a date). Each date will have its own set of data. The user should be able to navigate between different days to see the data from that particular day.
-- File date can be overridden by an Analyst. An update to File Date should update the entire data set. Plan for error handling if the user tries to change a date to overwrite an existing date.
- Add a column that auto-computes the days stale:
-- Days stale means the number of business days a particular row of data has a value below x. If x=100 and bond y has been $90 for 10 days, then that piece of data should have Days Stale = 10.
- Add a column to allow users to enter free form comments / track actions for the security:
-- Any stale item should be able to have comments added to it. These comments should carry on from one day to the next.
- Warning / Error messages should be externalized.
- Error messages should have enough contextual information to help with diagnosis.
- User should be able to filter/sort the data in an intuitive manner. See design considerations above for more information.

Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn

Target audience:
- Analyst employees.

Judging Criteria:
- User Experience of the web 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.