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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to "KPI Dashboard - Power BI Dviz Design Concepts Challenge". In this challenge, we are looking to explore design concepts for new Data Visualization reports that will be implemented using "Microsoft Power BI". The client is looking for topcoder community design expertise in coming up with creative design concepts.

We recommend you to start by digging into data visualization design best practices, research Microsoft Power BI and think about simple ways to provide data visualization experiences.
We are really excited to kick off this DViz Design Concepts Challenge.

Challenge Objectives
  • Power BI Dashboard Designs
  • 3 Dashboard screens

Round 1

Submit your initial designs for a checkpoint feedback
01 General Dashboard Features
02 Key Performance Indicators Dashboard
03 Service Level Overview Dashboard

- As a part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Make sure to include a URL/comment the link to your marvelapp while uploading your submission
- Make sure all pages have the correct flow! Use correct file numbering. (00, 01, 02, 03)

Round 2

Submit your final designs with all checkpoint feedback implemented.
01 General Dashboard Features
02 Key Performance Indicators Dashboard
03 Service Level Overview Dashboard
04 Service Level Overview Dashboard

- As a part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Make sure to include a URL/comment the link to your marvelapp while uploading your submission
- Make sure all pages have the correct flow! Use correct file numbering. (00, 01, 02, 03)

Background Information:
Currently, the client manually uploads data from different sources into Power BI and different reports are created for different audiences, so we are seeking BI efficiency by centralizing the Data visualization in Power BI.

Through this challenge, the client is looking for the topcoder community to come up with a design for a set of reports that will be displaying relevant information for internal stakeholders such as Operations teams and COOs. We would like to create the reports in PowerBI, so it is easy to consume by everyone.

Design Considerations
- We are looking for a simple, easy-to-use, Informative, modern design.
- Try not to have too much information on your dashboard, you can make them compelling by making the visualization interactive and enable users to walk through or drill into the different insights.
- Use color, visual comparison, and drill-down charts to highlight comparison.
- Have your designs of size: 1366 x 768px (Desktop only, Power BI is responsive by nature so just need to design/ build once)
- We have provided some reference images for ideas on the type of KPI’s but please don’t follow them as we are looking for something creative from the topcoder design community.

Power BI Requirements:
- All principles of good UX design e.g. minimize user clicks, make the experience more intuitive, minimal time to reach desired selection criteria, store user selections for multiple reports and performance, good color and font themes, etc, these are all critical success factors for this challenge.
- Needs to follow Power BI Design Best Practices and also take a look at the Design Tips
- Please do some research on the Power BI software and get familiar with its purpose, limitations, and what's possible.
- There needs to be a way to view it as a live dashboard and/or with flexible filtering

Data Samples:
We have shared data samples (in the forums) that you can use in your designs
The provided sample data contains mainly information about issues, requests, outages or services within the ITSM (IT Service Management) framework that are mainly submitted and handled through ServiceNow. We use other tools like Nexthink to monitor devices or an ad hoc tool for users’ profiles and access management. All our services are IT related. We have also shared some screenshots of the tool that will help you understand what we are targeting.

Required Dashboard Designs
01 General Dashboard Features:
  • Think through the filters that are required for this challenge
  • Provide a way for the user to drill-down information as required
  • Dashboard access to all relevant reports, accessible in an intuitive way
  • Implementation of role-based access control for groups of stakeholders
02 Key Performance Indicators Dashboard:
  • The report needs to show at least 9 different KPIs in your designs.
  • The KPI you can include in your designs are:
    • Ongoing issue/outage time
    • Resolution time within the agreement Y/N
    • Resolved by the first line of support Y/N
    • Request type x delivered on time Y/N (several types of request but the concept is always the same: delivered within the agreed time yes/no)
    • Tickets flagged as “incorrect details”
    • Tickets opened for the same issue the same end-users by the same helpdesk agent
    • Devices not seen online in a certain amount of days (90 days for example)
    • Anything else you can come up with?
  • Above KPIs apply to different countries but the calculation is standard across regions. 
  • There are two types of geographic information in the reports: a location which is the full address and country or country code or region (it depends) that might be the country/ISO code for the country
  • The report will need data visualization and some simple mathematical calculations (For example, if we check “backing data_7 master tracker.xlsx”, column H, we should have the following calculation:
    • for KPI2: tickets flagged as FCR=YES divided by Total tickets (sum of true and false)
    • for KPI5,8b,9 should be: tickets that met the SLA divided by total tickets (excluded are, as the type of tickets says, “Excluded”))
03 Service Level Overview Dashboard:
This is a report that gives more an overview of services rather than only specific KPIs or calculations. Here information about new employees or leavers should be included (refer to backing data_6_HR.xlsx) or printing volumes. This is the report that needs role-based visualization as there are 3 main regions and each COO should have visibility only on their region
 
  • Report that will provide an overview regarding certain services, covering different areas, all based on criteria already defined. 
  • Visibility should vary following a role-based model i.e.
    • let’s say that we define a template with the following graphs (only as an example):
      • graph 1 – incident
      • graph 2 – new joiners
      • graph 3 – leavers
      • graph 4 – printing 
      • graph 5 – requests
    • The COO for region 1 should see only information related to region 1 (that is defined either by “location” or “country”). The COO for region 2 should see only information related to region 2 etc. Basically all will see the same but with the region, but filter applied.
  • Some of the charts used in Report 1 will be leveraged for this one.
04 Application/Infrastructure Dashboard:
  • Report(s) that will cover services provided as part of the infrastructure/application catalog.
  • The report(s) will need to show ITSM services such as incidents, problems, outages, the volume of requests, etc 
  • At the moment there are separate reports that ideally should merge in one complete report.
Important:
- Keep things consistent. This means all graphics styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance.
- Focus on User Experience / how the user interacts within the dashboard.
 
Reference
Example dashboards design reference for your considerations:
- https://community.powerbi.com/t5/Data-Stories-Gallery/bd-p/DataStoriesGallery
- https://docs.microsoft.com/en-us/power-bi/service-dashboard-create
- https://id.pinterest.com/steffuhnee/power-bi-dashboards/?lp=true
- https://dribbble.com/powerbidesign
 
MarvelApp Prototype
- We need you to upload your screens to the Marvel App
- Please send your Marvel app request to csystic@gmail.com (challenge copilot)
- You MUST include your Marvel app URL in notes /comments while uploading (in your marvel app prototype, click on share and then copy the link & share it within your notes while you upload).
 
Target Audience
- Internal stakeholders such as operations teams as well as COOs.
 
Judging Criteria
- How well you plan the user experience and capture your ideas visually.
- Cleanliness of your graphics and design.
- The overall design, UI and user experience.
- Consistency across the UX/UI
 
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
- Submit JPG/PNG for your submission files
- Submit Marvelapp as part of your submission.
 
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop, Illustrator, XD, or Sketch!
 
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.

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.

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:

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

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • Layered PSD files created in Adobe Photoshop or similar
  • AI files created in Adobe Illustrator or similar
  • Sketch
  • Adobe XD

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30120715