Usability Testing: Add-on Explorer of MathWorks
Project Goal
Project Goal
Project Goal
Carry out a usability study examining how users interact with the product (especially the categorization panel)
Carry out a usability study examining how users interact with the product (especially the categorization panel)
Carry out a usability study examining how users interact with the product (especially the categorization panel)
Dashboard - Design Challenge
Dashboard - Design Challenge Context
- The web application is used by our customers to view summary statistics for their equipment fleets and to understand the time until equipment failure.
- The dashboard is the first view users have while logging into the application.
The current implementation is limited: there are many other data types, measurements, and information that users are asking for. Data that might be rendered in this view include:
-
Equipment Name
-
Manufacturer
-
Asset Type (for example, Network Transformer, GSU Transformer, Reverse Osmosis)
-
Asset status (one of In Use, Available, In Repair, Decommissioned, or Down.
-
Remaining Useful Life (the output of our analytics, abbreviated “RUL”)
-
Hazard (the probability of failure in the next twelve hours)
-
Failure Date (predicted failure date)
-
Equipment Photo (or a default icon for the asset type if no photo is available)
-
Location
-
Star/Unstar (similar to GitHub or Heroku designs)
-
Add log entry/Add User (additional actions tied to the equipment)
-
In alarm (binary: yes/no)
-
Serial Number
-
Last updated timestamp
The objective is to come up with a low fidelity mock up making any subset of this data available to users, replacing the existing table design.
Goal
- To Design a Dashboard for Equipment Manager in a Manufacturing company
Overall Flow
1. Business goal
2. Researched online:
- Website
- YouTube videos for manufacturing flow & design ideas
3. Considered the key features
4. Brainstormed for Design Ideation
5. Designed prototypes
6. UX Research to get manufacturing industry insights & prototype feedback
7. Prototype Iteration
Design Prototypes
Key features for the dashboard I picked:
- Equipment Name, Serial No. Asset Status, Hazard, Remaining Useful Life, In Alarm, Starred Item
Research
Participants:
1. Product Development Engineer
2. Data Scientist
3. Engineering Student
Insights and feedback from interview:
- Good Matrix and Data Collection is important
- Tracking Down time by reasons
- Present data graphically
- Proactive Systems before equipment breaks
- Combine graphs with quick access card
Prototypes Iteration
1. More Graphs
2. Data Visualization
3. Proactive System before failure
- Inspecting before repairing
- Inventory purchasing advice
Challenges & Opportunities
How to make suggestions on inventory purchasing? It is a big complicated calculating system.
Wire-framing Prototype
Quick Access Cards enable users to check out the most important issues
Graph on the left displays equipment status
Prediction of equipment inventory tells equipment manager when is the time to purchase inventory to prevent low inventory situation happening.
It provides tips / memo for inventory purchasing based on the historical data
It also provides supporting information or reasons to back up the inventory prediction.
The system also provide suggestions on when is time to inspect equipment before they break down.
Based on the historical down reason analysis, the inspector can quickly check the equipment status efficiently.
