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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Sancus - Fund Accounting Yield Web Application Wireframe Challenge. Through this challenge we are looking for your help to wireframe a web application that helps calculate the SEC Yield, which is a standardized yield used across the industry to compare the yields of income generating funds.

At the end of this wireframe challenge, we are looking to have a solution that allows us to understand the administrator experience

Round 1

Submit your initial wireframe solution for checkpoint feedback
01 Main Page
03 Fund Review Page
04 Holdings View Page
05 What if Analysis
05.1 Adjustment Process


Notes.jpg: Any comments about your design for the Client.

Round 2

Submit final wireframe solution plus checkpoint feedback.
01 Main Page
02 Maintenance Page (admin only)
03 Fund Review Page
04 Holdings View Page
05 What if Analysis
05.1 Adjustment Process
06 Approval and Unapproval Process 
07 Reporting Page


Notes.jpg: Any comments about your design for the Client.

We are looking for the topcoder community to come up with the wireframe that will help define the user experience, flow for this new web application!

Background Information:
For a specific set of mutual funds, the federal government requires that certain calculations are done daily in order to measure the fund’s success against other, similar funds. The main measure for this is an SEC Yield (also know as standardized yield). This is a percentage that tells you, for every share owned, how much money I could expect to earn in a year. The percentage is calculated by taking all income earned on a given day, subtracting out all expenses incurred on a given day, and then dividing by the days in the year and shares outstanding. Every other calculation and piece of information gathered for this project is to go towards fulfilling that calculation or extrapolating further information based on it.

These values are expected to be calculated daily. First by calculating income on all securities held, and then using those numbers to find the fund’s total income.

Important Considerations:
- Please have your wireframe screens of size 1024 / 1280 px width and height as required.
- Please keep in mind that ultimately we will be building a web application.
- Looking for a modern, intuitive UI/UX
- Focus on the wireframe being a great user experience, think simple but effective solutions!
- Come up with designs that shows out-of-the-box solutions.
- Show all the screens and provide a user flow/click-path and navigation, so we can see how the interactions fit together in the application
- Please make sure your capture every details in the wireframe.

Challenge Assets:
Data Input / Output: Please use the attached file for data and its data type to be shown in each page.
Glossary of Terms: Please find explanation for the terms used in this project /challenge.

Required Pages:
We need below screens to be captured but if it requires more screens to show your flow, feel free to add them to the wireframes - we are open to your ideas!

01 Main Page
- Assume a user will be already logged in to this application!
- Lists out number of fund level warnings
- - - Clicking on link brings you to fund page showing their tolerance breaks (please see below)
- Lists out number of larger security level warnings
- - - Clicking on link brings you to security page showing their tolerance breaks (please see below)
- For data on page, please take a look at UI Wireframe Input/output dataset

02 Maintenance Page (admin only):
- Note this page will be accessed only by admin, provide a way for them to access this page from navigation.
- Admin will be responsible for the maintenance of Funds, Tolerances, Equity
- We are open to your thoughts on how this page need to be put up!

Fund Maintenance:
- Determine whether fund needs Money Market Yields, SEC Yields, or Fixed Income and Equity (FIE) Distribution Yields
- Determine whether fund needs to transmit out to FIRS, UNITY, Both, or Neither
- For Money Market funds, determine if its TAXABLE or TAX FREE

Tolerance Maintenance:
Admin will be able to set the tolerance for the fields:
- Fund Level Tolerances
- Security Level Tolerances
- Position Level Tolerances

Equity Maintenance: (these will be percentages)
- MLP Rates
- REIT Rates

03 Fund Review Page:
Sec Yield:
- We will show a list of funds in this page
- User will be able to select the fund to further see the holdings view
- Need to show the fund level warnings (Next to the offending field/record, we want to see some kind of ‘Warning’ graphic. Like a stop light, or different colored text. Mousing over the graphic would bring up more information on the error/ clicking would give a user the ability to add comments - if you have better ideas, feel free to show them)
- There is a one to many relationship between Funds and Classes
- Should have the ability to sort and sorts based on Tolerance Breaks
- Provide various filtering options, looking for your thoughts on what filter options will be required..make sure that user is able to select different dates to view.
- Should have the ability to search through the funds, looking for your thoughts on how this need to be put up!
- User can submit funds from this screen to FIRS and UNITY, you just need to provide buttons that will help send the data to the two reporting tools mentioned above!
- If security level adjustments have been made, this screen clearly marks affected funds (this is based on the adjustments process shown below in What if analysis).

Money Market:
- Each row of data is a separate fund class
- Shows Fund and Class level warnings
- Clicking on Funds brings you to Distributable Income View
- Should have the ability to sort and sorts based on Tolerance Breaks
- Provide various filtering options, looking for your thoughts on what filter options will be required..make sure that user is able to select different dates to view.
- Should have the ability to search through the funds, looking for your thoughts on how this need to be put up!
- User can submit funds from this screen to FIRS and UNITY, you just need to provide buttons that will help send the data to the two reporting tools mentioned above!
- Need a way to refresh these money market information.

FIE Distribution Yield:
- Each row of data is a separate fund class
- Shows Fund and Class level warnings
- Should have the ability to sort and sorts based on Tolerance Breaks
- Provide various filtering options, looking for your thoughts on what filter options will be required..make sure that user is able to select different dates to view.
- Should have the ability to search through the funds, looking for your thoughts on how this need to be put up!
- User can submit funds from this screen to FIRS and UNITY, you just need to provide buttons that will help send the data to the two reporting tools mentioned above!

04 Holdings View Page:
Sec Yield:
- Each row of data is a separate security
- Clearly shows securities breaking security level tolerances
- Clearly shows securities breaking position level tolerances
- Separate area shows position level detail
- Separate area shows Security Type specific fields
- Clearly shows securities with manual adjustments
- Should be easily sortable by security type and tolerance breaks
- Should be easy to move from this page to What If Analysis, more information on this can be found below (this is upto you on how a user should move to the what if analysis - user can have a button for each of the security and reach the what if analysis screen by clicking on the button)

Money Market:
- Each row of data is a separate security
- Clearly shows securities breaking tolerance for yields
- Clearly shows securities breaking tolerance for positions
- Separate area shows position level detail
- Data sortable by fund and tolerance levels
- Shows In State and Out of State holdings (What are these: Money Markets hold municipal bonds. If you purchase a municipal bond for Massachusetts while living in Massachusetts, you don’t have to pay taxes on it. When we say In State, and Out of State, we are determining what percentage of a Massachusetts based fund’s holdings are Outside of Massachusetts. In State = Massachusetts. Out of State = Anywhere else. The LOGIC is done outside of the UI, but the UI needs to show whether or not a row is in state or out of state.)

05 What if Analysis:
- User able to search directly by security
- Yields recalculate immediately upon changing a value
- Show changes to all positions when changes are made to Security level
- Committing a change adds adjustments to all positions, does not change underlying values
- Changes cannot be committed without writing within a comments field.
- Input fields and options change depending on security type
- All committed changes are viewable in an audit log.

05.1 Adjustment Process:
- User retrieves data by putting in a CUSIP (security)
- User continues to adjust values and submits for recalculation until they are satisfied with the results
- User Submits the adjustment
- The adjusted calculations (impacted Security, Positions, Funds) are now stored to the table and the overridden values are stored to the table
- Adjustment comments, Amounts that changed (overwritten values), user who made the change
- These changes will now need to be tracked as “waiting for approval”
- Event log records the fact
- User can re-do the process which would repeat steps 1 - 6. The previous instance does not need to be stored, it would be an update

06 Approval and Unapproval Process
Approval Process:
- When a user adjusts a security or position using What If Analysis, this needs to be approved as well. THESE approvals have to come from someone with the position of ‘Approver.’ A fund cannot be submitted while these specific Tolerance Breaks are unapproved.
- Every Tolerance Break gives a user the chance to enter comments and approve. Approving hides the warning from view. A user is unable to approve unless a comment has been entered.
- Retrieve all open items i.e. anything that is updated via “What if analysis” needs to be approved.
- This list should be readily available somewhere within the UI for someone with access to approve.
- Standard Tolerance breaks do NOT need this kind of attention, but being able to look at all records with Tolerance breaks would be very helpful.
- Approve each individually with a specific comment and the approval flag should be set
- Store who approved it, the comments

Unapproval Process
- Retrieve open items
- User unapproves a specific item and submits it
- The overwritten values will be deleted and the adjusted calculations are deleted
- Everything reverts back to original as if no adjustments were ever made
- We need an event log entry to capture

07 Reporting Page:
- Should clearly show all report options available to user group
- Reports should also be viewable via available interface
- Fund Groupings should be utilized to pull certain things
- Reporting outputs should be populated in either Excel, PDF, or Tableau
- User should be able to submit funds via some of the report screens
- Certain reports should be restricted by admin group

NOTE: You are welcome to add additional screens if you feel it will improve the user experience. We are open to your creative ideas around how to plan this platform.

Target Audience
The actual users of this interface will be:
- Rank and File Fund Accountants, who would be using this to research anomalies, submit funds through the process, maintain daily operations
- Fund Accounting Managers, who would be using this to research anomalies, generate reports, approve changes done by Accountants
- Auditors, who would be reviewing changes and discrepancies
- Systems Administrators, who would be adding maintenance information for users and funds

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

Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your wireframes
- 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
Wireframes should be built in HTML or Axure

Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.

Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.

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.

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