Divisan: Industrial Operations Platform

Turning factory-floor production records into structured data for real-time operational reporting

Role

UX Engineer

Team

3-person studio + Divisan team

Timeline

2026 · In production · Ongoing

Tools

Paper, Vue 3, Pinia, GitHub, Ollama

Scope

Stakeholder discovery, UX/UI, Component system, Frontend implementation

Divisan: Industrial Operations Platform — Turning factory-floor production records into structured data for real-time operational reporting

Outcome

Three production workflows are live with 20 registered factory-floor users.

Key decision

Shift from long forms to guided steps with validation before advancing.

Trade-off

Reduced visible complexity without removing the operational detail dashboards need.

Next measure

Error-rate reduction and capture time are still being measured after launch.

Reliable records on the factory floor

Divisan manufactures livestock identification. Notebooks, spreadsheets, and Google Forms produced incomplete or inconsistent entries that the data analyst had to correct.

Starting in May 2026, I designed and implemented mobile forms within the existing system and its permission model.

Less load, the same detail

The analyst needed reliable monthly reporting; operators needed clear data entry on phones and tablets.

We had one sprint, no extra budget, and no direct operator access. I worked with Gabriela on design; Mario owned the backend and final decisions.

Simplifying the form did not mean removing information. It meant asking for it at the right moment—one step at a time.

Evidence and limits

The analyst and Divisan team reported recurring errors in products, quantities, and operator entries. Their feedback guided the design.

We reviewed the implementation in development before release. Direct usability testing with operators remains a next step.

Representation of the previous manual recording process using notebooks and spreadsheets — The process Divisan relied on before the guided digital forms.

Progress visibility and interruption recovery

Multi-step flow over vertical scroll

The team chose a step-by-step approach over my initial vertical proposal, reducing how much information appears at once on mobile screens.

Validation before advancing

Each stage validates required data before allowing progression, with clear error messages and backward navigation without losing entered information.

Local draft persistence

A shared composable stores the current step and form state in localStorage so an accidental refresh or tab close does not restart the task.

One system across three forms

Shared headers, progress indicators, validation patterns, and responsive rules keep raw-material, scrap, and laser-waste workflows visually consistent.

Overview of the three Divisan guided form workflows — Three production workflows—materia prima, vena y scrap, scrap almacén y laser—built from a shared interaction system.

Step 1 of the raw material form on mobile: production date, operator, and machine selection — Step 1 of 6: the form starts with production context—date, operator, and machine.

Review screen showing all captured data before submission — Step 5 of 6: a full summary lets operators verify all entries before sending.

Three flows, one shared foundation

I implemented 4–6-step forms in Vue 3, using dynamic components and shared composables to persist state in localStorage.

Each flow combines visible progress, validation, and a final review. The layout adapts to mobile and preserves entries when going back.

Mobile flow showing step progression across the three Divisan forms — Start, step, and review remain legible and usable in a narrow mobile viewport.

Live, with impact being measured

All three flows are integrated and update dashboards in real time. The system has 20 registered users.

Error reduction and completion time are still being measured.

Production dashboard showing real-time data from the guided forms — Dashboards update in real time as operators complete each form.

What I would carry into the next operational product

→Joining an existing codebase requires understanding its rules before proposing new ones.
→Owning both design and implementation closes interaction gaps that often appear in handoff.
→Define measurement before launch instead of attempting to reconstruct it afterward.

See an opportunity to work together?

Let’s discuss a role or project

Next Project