Skip to main content
Meytal Dahan
Back to insights

Industrial Planning Systems: How Do You Design a UI That Works With Complex Hardware and Harsh Spatial Constraints?

ZammitEngineering LeadersIndustry 4.0 / Manufacturing
Zammit — Designed the Retail Shelving Planning System - the platform's most demanding configurator, where every dimension, shelf, edge profile, and placement rule is defined - into a spatial design tool retail professionals could use without CAD knowledge.
Engineering leaders who run software projects for the production floor know it's a unique technical challenge. Unlike office systems that run on standard computers, industrial systems sometimes run on ruggedized touchscreens, in environments with shifting lighting angles, and with hardware constraints (CPU power, memory, bandwidth). All of these affect the design. In the manufacturing platform project, the design was done with full consideration of the production floor's hardware constraints. The screens were designed with large UI components suited to being pressed with work gloves. Color contrast was set so the screens remain clearly visible even under strong fluorescent light or direct sunlight. Every animation and transition was tested on the designated hardware to ensure smooth performance. In addition, we created "environment-specific error states" — when the system loses its connection to the plant's internal network, it doesn't crash but instead enters Offline Mode, which lets the operator keep working. The data syncs automatically when the connection returns. Edge cases like these, which capture a real production-floor scenario, save hours of work and prevent costly failures. For CTOs working on industrial systems, the insight is: require your product designer to work against the designated hardware, not just on a standard desktop. A design that ignores the real environmental conditions fails on the production floor. A design that's adapted to the hardware and the environment makes the system a natural part of the plant.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Zammit
Project ManagersUsability Testing

Testing a Spatial Configurator Without CAD

On Zammit's shelving configurator, we asked people to lay out custom shelving — dimensions, shelf count, depth, placement — with zero CAD knowledge. That is a usability risk you cannot hand-wave. So I ran testing as a recurring checkpoint tied to delivery milestones, not a one-off before launch. The payoff is for project managers as much as designers: testing turns a scary, vague risk ('can buyers do this without a salesperson?') into specific, scheduled, fixable issues. And inside an engine with real constraints, testing early tells you which problems are worth engineering time and which a better sequence solves for free. Predictability beats surprises.

Read
Zammit
Product ManagersMicro-interactions & Animation

Micro-interactions That Made an Engine's Rules Feel Like Feedback

Rule-heavy configurators feel like the system is fighting you — unless feedback shows why. On Zammit, micro-interactions turned the engine's logic into a conversation: a value recalculating, the summary shifting, an invalid option visibly settling out of reach instead of vanishing. PMs, the test for every animation: does it explain the system's behavior, or just decorate it? Only the former protects flow completion.

Read
Zammit
Project ManagersDelivery & Handoff to Development

Handing Off 40 Configurators Without Losing the Thread

Handing off ~40 configurators, 25 e-commerce flows, and 6 onepagers — solo, over ~2 years — taught me that handoff isn't an event, it's a rhythm. At that volume the real risk a project manager loses sleep over is drift: checkout behaving one way here, another way there. My defense was deliberate pattern reuse and handing off the decision logic, not just visuals — especially for configurators bound to the DriveWorks engine's rules. Shared patterns are schedule insurance: estimates hold, review cycles shrink, and developers implement without guessing. Clear intent plus clear constraints beats a backlog of clarifying questions every time.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.