Hestia - DViz Supply Plan Dashboard Design Concepts Challenge

Welcome to "Hestia - DViz Supply Plan Dashboard Design Concepts Challenge". In this challenge, we are looking to explore design concepts for a new Data Visualization Dashboard that will be implemented using "Microsoft Power BI". In this challenge, we are going to design the Data Visualization experience for use by people at various roles (Management, Analyst, Vendors) at Hestia.

We recommend you to start by digging into data visualization design best practices, research Microsoft Power BI and think about cool & creative ways to provide data visualization experiences.

We are really excited to kick off this new Hestia DViz Design Concepts Challenge.

Round 1

Submit your initial designs for a checkpoint feedback
01 Allison -  DC Management (Receiving Plan)
02 Bob - DC Configuration Analyst (Receiving Plan)
03 Patrick - Vendor (Supply Plan)
(Please try your best to complete as much as possible, so you can look to have feedback from the client on that)

- 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 correct flow! Use correct file numbering. (00, 01, 02, 03)

Round 2

Submit your final designs with all checkpoint feedback implemented.
01 Allison -  DC Management (Receiving Plan)
02 Bob - DC Configuration Analyst (Receiving Plan)
03 Patrick - Vendor (Supply Plan)

- 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 correct flow! Use correct file numbering. (00, 01, 02, 03)

In this challenge, we are looking to design creative (and useful) data visualization dashboards that will make it easier for the respective users to analyze the data in an intuitive way which will help them with their day-to-day operations and also understand the requirements for effective planning. We have taken the time to understand and list out the user needs, their day-to-day "actions" to help you understand what is important to them and would be important in their respective dashboards.

Background Overview
What is Receiving Plan?
The Receiving Plan is data that shows incoming shipments to a DC. For example Inbound volume by the vendor, by product type, by containers, by pallets, by cartons and/or by individual product SKUs. The Receiving Plan will be used by the DC Configuration Analyst to help plan and run the operation of receiving product and putting it away in the DC.

What is Supply Plan?
The Supply Plan is data projecting future purchase volume from a manufacturer (vendor) by Hestia.  The manufacturer uses this data to plan the production and shipment of product to Hestia. Manufacturers need to quickly and easily visualize future purchases over multiple timeframes (weeks, months, 6 months) and by different product types and classifications (appliances, valves, faucets, pipe).  Manufacturers need to see comparisons against previous timeframes as well as trending stats to help with their planning. The Supply Plan is a combination of the Visualization Dashboard and detailed purchasing data provided by Hestia.

DC = Distribution Center (essentially a warehouse that receives, stores and ships products to other Hestia locations and directly to Hestia customers)
Manufacturer = Vendor (these terms are used interchangeably at Hestia)

Design Considerations
- We are looking for 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)
- Colors and branding is up to you - do some analysis in this area of what colors work well for Data Visualizations

Branding Guidelines
- Follow provided guide: MRKT_Guide_DataVisualization (Please see forums)
- 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.

Required Dashboard Designs
We are looking for you to design dashboards for each of the user personas listed below:
- Overall think through the provided Persona's and their needs. It is easy to just show data on the dashboard but want to show what data matters to them and allows them to take action and perform their job more efficiently
- Realize one user might need the specific level of detail and another user might need a more granular or higher level view of the same data. How do they interact, drill in or filter this?
- Take a look at the features of Power BI and look to incorporate features that you think would be useful.
- We are providing sample data for you to use in data visualization / you will need to do some research on how the data can be effectively used (Please find sample data in the forums)

User Personas:
01 Allison -  DC Management (Receiving Plan):
I am Allison and I’m a part of the DC Management team and need a Receiving Plan including a visualization and supporting data file to identify: The total number of cartons/handling units by *GPH and put away ID for each SKU in weekly buckets by day of the week and shift that will be received at each DC so that I can understand labor requirements and estimate workforce planning.

I spend my days at Hestia HQ (or) traveling to DC locations where my daily focus is on leading the day-to-day operations of the distribution centers including planning for labor resources.

Here is the data and information that I’m most interested in:
- Volume Projected: Inbound and Outbound for the day
- Inbound Schedule from what work was left the night before
- Do they have any staffing no-shows
- Do they have any trailers dropped (these are the trailer/containers that dropping off the shipment to the DC) in the yard
- How busy does the schedule of the DC manager look for that day
- What does the staffing look like?  Any call outs? People they thought were supposed to be here that isn’t? (staff that was expected at the DC or on a task, but aren't)

*GPH is Product Hierarchy. There are different levels of detail when describing products. Ex: Level 1: Pipe, Valves, and Fittings; Level 2: Pipe and Tubing Fittings - Copper; Level 3: Copper Pipe Fittings - Pressure; Level 4: Copper Pressure Pipe Fittings

Volume:
- Looks at Volume at a high level,  so this is across all DC’s (we should be able to drill down into individual DC's) -  this way I could know where we are busy?  Where are we not busy?
- What volume do they have at the beginning of the day and what’s projected for that night or the next shipment?
- Demand Volume is most important (outgoing shipping volume).
- If Demand Volume is heavy, they will pull staffing resources from Inbound receiving and send them to Outbound shipping.
- I want to see the number of people she has, and the work expected.
- - - Am I covered or do I need to call in people for overtime?  Do we have overtime scheduled for today?

Long-Term Forecasting (Data Visibility):
Allison manages 10 DCs + 4 Pipeyards = 14 Instances, She works at HQ and uses a Desktop computer
- Long-term data visibility is currently a Pain Point and she wants to be able to see weeks in advance. The range could be within 4 weeks (we can get a good level of accuracy).  For 6 months and beyond the accuracy and details don’t have to be as exact, it is only necessary to show percentage increases in forecasted activity, seeing if vendor activity will be going up or down in 6 months would be helpful.

Projected Staffing:
- How far out do we have to schedule out staffing on the receiving side to meet receipts/demand...
- Expectations of work coming in, this determines projected staffing

Containers:
- Wants to see the forecast of Import Containers
- What’s coming in from the port, on the rail, on water?
- International Inbound?
- Domestic Inbound?
- Show what’s coming into the DC over a 4 week period with good accuracy, and far out projections of incoming with, ok accuracy.
- Drill down and show the hierarchy of shipments: Container/Truckload/Palette/Carton/Interpack/Each

02 -  Bob - DC Configuration Analyst (Receiving Plan):
I’m Bob, and I am a DC Configuration Analyst and need a Receiving Plan including a visualization and supporting data file to identify the total number of cartons/handling units by GPH and put away ID for each SKU in weekly buckets that will be received at each DC so that I can manage slotting and storage locations.

I spend my days onsite in the distribution center warehouse where my daily focus is ensuring the optimal level and age of inventory to minimize storage costs and meet the organization’s production and customer demands.

Here is the data and information that I’m most interested in:
- Slotting (place into a slot) and Product Grouping and zones within the product warehouse
- Do I have existing space (or) is my receiving schedule better after outbound has put away their inventory
- Similar insights to Manager but on a Micro level i.e. they wouldn't necessarily see across multiple DCs, they are mainly concerned with the one they are in and focused mainly on Product and where to put it in the DC.
- Not as concerned about staffing, but more about the product
- Looking at shorter timelines 2 - 4 week windows
- Manages distribution (shipping directly to customers, on time, reliability, accurate data)
- Needs to have places to receive product
- Concerned with storage requirements of flammable, combustible, corrosive materials, they have to be stored in a way where they don’t interact with each other. Huge possibility of OSHA violation or injury
- Concerned about safety (SAFETY FIRST) - Hazmat (Hazardous material) certification - Product that is susceptible to damage - porcelain or china.
- Include some type of blurb about safety, a small visualization about safety.

03 -  Patrick - Vendor (Supply Plan):
I am Patrick and I’m part of a vendor forecast planning team and need a Supply Plan including a visualization and supporting data file to identify the total number of SKUs forecast to be shipped to each DC so that I can collaborate on monthly forecasting calls with Hestia, incorporate the plan into my manufacturing plans and compare it to my internally generated forecast.

I spend my days onsite at my vendor headquarters and traveling to customer locations like Hestia where part of many of my customer-facing responsibilities is ensuring we have enough inventory planned to meet our service level agreement with Hestia.  Hestia is typically one of my largest customers.

Here is the data and information that I’m most interested in:
- Procurement department places the orders to the vendors through the DC.
- Expected purchases of the future relate back to the receiving plan
- Hestia’s order entry and purchasing ERP systems drive the demand forecasts for future purchases.
- They use this information to plan their manufacturing and their shipments
- Show the supply plan, and have the ability to drill into the categories of products
- Show projections of products needed in the future, the service level of how their products are performing with Hestia
- Vendors are limited from competitors information - they will only see their information.
- They currently don’t have visibility as to what Hestia is buying 4 months from now.  It makes it difficult to do production planning.

Filters
- Purchasing Date (estimate)
- Expected Ship Date (when Hestia expects the vendor to ship it out)
- Receipt Date which drives the Hestia DC Receiving team

Important:
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance.
- Focus on User Experience / how 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 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
- Distribution Center (DC) Management, DC Configuration Analyst, Vendor

Judging Criteria
- How well you plan the user experience and capture your ideas visually.
- Cleanliness of your graphics and design.
- Overall design, UI and user experience.
- Consistency across the UX/UI
- How well you interpret the example screens (business relevance) and show us new ideas and concepts.

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.