KUKA Compose | Robot Selector
UI/UX Designer
KUKA Robotics
Robot Selector is part of the KUKA Compose experience and is the first step towards enabling automation from planning to production in a single platform. It eases the process of selecting and analyzing robots.
My role
-
The lead designer for KUKA Compose and designed key MVP components for its launch in October 2019.
-
I worked with a squad of a product manager, back-end developer, front-end developer, and tech doc writer to launch it.
Results
-
Redesigned the layout to accomodate adding additional payloads for analysis
-
Re-formatted the PDF reports to focus more on the data
-
Designed concepts for future features like project management and a mobile app
Users first choose the relevant parameters to select robots for their application. They can select up to three to compare.
Once they've selected their robots, they can input their load data for summation and see if it's approved for the robots.
Users can generate a report to show KUKA the robot purchase is approved for their payload.
Product clickthrough
Design process
As we prepared for the launch, new features needed to be added to match the current product.
-
Adding additional payloads to the analysis.
-
Reformatting the current analysis reports
The old selection and analysis software
Source: KUKA.Load
Adding payloads
The initial layout was fine for simple analyses with one load case. But it wasn't future-proof for adding more payload data.
Problem 1: Adding the main payload data for each robot was cumbersome.
Problem 2: The current layout didn't work well for adding additional separate payloads.
First layout
Layout iteration examples
Adding payloads - Final design
I organized all editable data on the left and the results on the right. This is consistent with the paradigm on the filters page.
Analysis reports
In order to get approval to use the selected robots, users need to download and submit a report and sign-off sheet to KUKA.
Problem 1: The current report had too many pages for all the payload and analysis data.
Problem 2: The style of the report needed to be aligned with the style of the app.
The old report design
Report design iterations
Analysis reports - Final design
I removed all images since they were unnecessary and I prioritized the data. I then optimized the charts for size and readability to use the space as efficiently as possible.
I've done more on Compose and Selector and I'd be happy to talk more about it. Thanks for reviewing!