Skip to content

Southern Germany

Laravel development for companies in Regensburg

Projects in Regensburg often centre on an unassuming requirement: for a part that has shipped, it has to be possible to say what it was made from and when.

Traceability is a chain

The requirement sounds harmless. For every part shipped, it should be possible to follow what it consists of and how it came about. In practice that breaks down into many small links, all of which have to be unbroken. Goods received, batch, lot, machine, test result, sign-off.

Break the chain in one place and the rest is worthless, because you have to guess at exactly the break. So we build applications like these so that a missing capture stands out rather than being passed over quietly. More on line-of-business applications like these under Laravel development.

The interface belongs on the line, not at a desk

Part of these applications is operated not in the office but in the hall. On a tablet, with gloves on, under time pressure, sometimes in poor light.

That changes the design more than it sounds. Large areas instead of fine buttons. As few entries as possible, because every second in the cycle counts. Feedback you can read from two metres away. And an error message saying what to do rather than showing a code.

So we look at workplaces like these on site. A screen that looks good at a desk fails on the line in the first week.

Alongside the ERP, not inside it

An ERP system can do a great deal, but rarely exactly what one particular production line needs. What makes sense then is a slim application alongside it, covering the part close to production and handing results back to the leading system. That keeps you independent of a vendor whose customisations are expensive. How we cut integrations like these is under API and backend development.

What works well at a distance and what does not

Regensburg is not a short trip from Stuttgart. We come out for capturing a process all the same, because production processes are hard to describe on the phone. Anyone who has never stood in the hall builds past reality.

After that the work continues well at a distance, with interim states your people try out on a real device. For the rollout on the first line we come out again, because those are the days that show what the capture missed.

Süddeutschland

Weitere Städte in Süddeutschland

All locations

FAQ

Questions from Regensburg

Our customer demands traceability. Is a label enough?
The label is the easy part. The hard part is the chain behind it: which batch went into which lot, which machine ran with which settings, who signed it off. If those links are not captured throughout, the finest number will not help.
Can the application carry on without a network on the shop floor?
Up to a point, and it should be discussed beforehand. Capturing and holding can happen locally, with reconciliation later. You pay for that with rules for the case where both sides have changed the same thing. Whether the effort is worth it depends on how often the network is actually gone at your site.
How long do we have to keep data like this?
Your industry sets that, and the periods are longer than software usually lives. So we take care that the data can be read without our application too. A cleanly described data model outlasts every change of technology.
Does capture run on devices on the shop floor?
Usually yes, on tablets or fixed terminals. That changes the design of the interface noticeably: large areas, few entries, usable with gloves and in poor light. A screen that looks good at a desk is often unusable on the line.
Can we fit out one line first?
That is the route we recommend. One line shows within a few weeks whether the capture keeps up with the cycle and whether people get on with it. After that the rollout is a repetition rather than an experiment.

A project in Regensburg?

If traceability currently hangs off a spreadsheet, this is a good moment for a conversation.