Challenge Summary
Welcome to the Managed Risk - Custom Reporting Module Wireframe Challenge! In this challenge, we are looking for you to design wireframes for a new, custom reporting module that will be added to an existing application. The existing managed risk application includes pre-built reports, however, if the data a user wants is not contained in a specific report, then customized report creation is needed to create the report or graph. This new reporting module will allow users to create their own reports, charts, and graphs to meet their reporting needs.
For this challenge, we need you to create wireframes for the new custom reporting module. We have provided details below on the application use cases and required functionality for you to understand what should be included in your wireframes. Your submission should show how all of these screens / functionality will flow together in the actual application.
We look forward to seeing your creative wireframe designs!
Round 1
Round 1 will focus on the following functionality for the new application:
1) Reporting Module Dashboard (main screen)
2) Generate Custom Report
3) View Report (including charts / visualizations)
NOTE: If anything is unclear, please ask for clarification on the forum and we will be happy to help!
Round 2
In Round 2, you will need to include all Round 1 screens (updated based on checkpoint feedback). For Round 2, you must also include all the remaining functionality described in the project documentation, including the following screens:
1) Reporting Module Dashboard (main screen)
2) Generate Custom Report
3) View Report (including charts / visualizations)
4) Save or Export Report
NOTE: If anything is unclear, please ask for clarification on the forum and we will be happy to help!
Challenge Details
The goal for this challenge is to create wireframes for a new, user controlled reporting module that offers access to the underlying data by allowing users to create their own reports, charts, and graphs to meet their reporting needs.The reporting module will need to include the functionality described below.
Project Background
The client for this project has an existing risk management solution that provides companies in the industrial commodities sector with a structured approach for addressing two fundamental issues associated with hedge programs and their interdependence: understanding the risk to financial goals that volatile commodities cause, and adopting a lucid hedge structure to protect the goals. The solution also incorporates regulatory and compliance requirements, as well as the complexities and nuances of financial reporting for the energy industry.
The client currently has a web-based risk management system which provides users and clients with access to a hosted deal capture, valuation, risk quantification, and risk reporting solution. This existing web application primarily leverages static dashboards and customized, but pre-defined reports. The system produces a robust data set on a daily basis from valuations to probabilistic distributions of costs, earnings, gross margins, to position and fixed prices across the portfolio and book structure and different time horizons. However, users currently don’t have access to this full set of data - if it’s not contained in a specific report, then customized development is needed to create the report or graph.
The client would like to develop a new, user controlled reporting module where they can provide access to the underlying data and users can create their own reports, charts, and graphs to meet their reporting needs. User’s would be able to create simple graphs and reports based on the data that gets generated daily.
Key features of the Reporting Module (i.e. what types of functionality you need to include):
- Ability to generate customized reports to access the underlying data.
- Users should be able to select what type of data to include in their report. In other words, the reporting module should include the ability for clients to query data based on their needs.
- Users should be able to export the reports they generate (and select the format to export in).
- Users should be able to save the reports they create.
Wireframe Requirements
- The wireframe designs will be added to the existing application under a “Reporting” tab.
- All screens / functionality described in this challenge spec must be included in your submission.
- You may use placeholders for visualizations. These will be expanded on in the upcoming design challenges.
- You must also identify any gaps and fill them in to show how the new application will work.
- You must create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities of the new reporting module.
- The reporting module must be very easy to use and intuitive. Keep that in mind when you create your solution for the layout and flow information.
- Use 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.
Example Reports
The client has provided details and sample data for the type of reports the new module is expected to generate (see the attached excel file “Managed Risk Sample Data v2.xlsx” for the data and more details).
| Report Type | Description | Data elements |
| Market Price Chart | Plot the daily monthly forward curve for multiple commodities | Price data tab |
| Market Price v. Weighted Average Fixed Price | Plot the daily monthly forward curve and the weighted average fixed position (for a counterparty, for a book) inclusive of all trades (for that particular counterparty or book) at either the monthly or annual granularity | Price data tab; Trade Data - quantity and price |
| Mark-to-Market by Counterparty | Plot the monthly/annual MtM by counterparty based on the individual transactions | Trade Data - MtM and counterparty |
| Mark-to-Market by Trade Type | Plot the monthly/annual MtM by trade type based on the individual transactions | Trade Data - MtM and trade type |
| Mark-to-Market by Book | Plot the monthly/annual MtM by book based on the individual transactions | Trade Data - MtM and book |
| Volume & Weighted Average Fixed Price | For a trade type (or counterparty, or book), plot the volume and weighted average fixed price either monthly or annually | Trade Data - volume, price, counterparty/book/trade type |
| Volume and MtM By Counterparty | By counterparty, plot the volume and MtM either monthly or annually | Trade Data - volume, MtM, counterparty/book/trade type |
| MtM and Volume Concentration By Counterparty | Calculate each individual counterparty's MtM and Volume percentage contribution to the total of all counterparties | Trade Data - volume, MtM, counterparty |
Supporting Documents
- Existing application screenshots (includes existing reports).
- “Managed Risk Sample Data v2.xlsx” - Sample data from the client, along with a list of example reports the client would like this new tool to generate.
Learn Axure
- New to Axure? Here are some quick tutorials to help you get started.
- http://www.axure.com/learn
Target Audience
- Users of the existing system
Judging Criteria
- User Experience of the reporting module.
- Completeness and accuracy of the wireframe as defined in the attached requirements.
- How well your wireframes provide a consistent user flow.
- How well your wireframe captures all the reporting requirements.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client).
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. The resulting files are not critical in this Challenge. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.
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.