Oniqua → IBM Maximo Inventory Optimization
About the project
Date:
Client:
Vinovest
Services:
UI/UX
Motion
Project Details
The people using Oniqua are inventory analysts and maintenance planners. Every decision they make is a trade-off between the risk of running out and the cost of holding stock, backed by deep data: usage history, forecasts, lead times, criticality and business impact.
The product had to turn that data into a clear next step. Work queues rank items by risk and savings, so analysts always start with what matters most, and opening a queue turns it into a worklist they can step through without going back to the list.
The item detail screen leads with the recommendation and puts the evidence around it. On one motor, cutting stock from 4 to 2 saves $5,796, and the change, the unit price and the saving all sit on the same screen, so an analyst can check the math before approving. Forecast and what-if views show the usage behind each recommendation and let planners test a change before committing to it.
When IBM acquired Oniqua, the product had to fit into Maximo, a platform its users already knew. We followed Maximo's patterns wherever possible, so new capabilities appeared in familiar places instead of feeling bolted on.
Things I Did
I designed the product's UI and UX, from work queues and item detail screens to forecasting, what-if and business impact views. I worked on interaction patterns for dense data: sorting and filtering large lists, moving between items without losing context, and editing recommendations in place. I defined motion for state changes such as recalculating, approving and deferring items, so users could see what changed. After the acquisition I worked with product and engineering on integrating the product into IBM Maximo.
