Skip to main content

Software Engineering

Connecting the shop floor to the ERP

Production output recorded on clipboards and keyed into the ERP the following morning became live shop-floor capture, giving planners same-shift visibility and cutting scrap.

Client
Precision components manufacturer running two production sites
Industry
Manufacturing & Industrial
Engagement
Fixed-scope integration build
Duration
12 weeks
1 shift → 2 min
Output data latency
−24%
Scrap and rework
0
Paper production records

The situation

What was going wrong

  • 01

    Operators recorded output and downtime on paper, entered into the ERP the next day.

  • 02

    Planners scheduled against figures that were always at least one shift out of date.

  • 03

    Quality problems were often detected at final inspection, after further value had been added.

  • 04

    The ERP had an integration interface, but no one had the capacity to build against it.

Our approach

What we did, and why

  1. 01

    Designed for gloved hands and poor light

    Terminals were specified and tested on the floor. Large targets, high contrast, minimal typing, and no reliance on a keyboard determined the whole interface design.

  2. 02

    Made offline the normal case

    Shop-floor network coverage was unreliable, so capture works fully offline and synchronises when connectivity returns. Nothing is lost and nothing waits on the network.

  3. 03

    Integrated through the supported ERP interface

    We wrote against the vendor's documented API rather than touching the database directly, which kept the ERP supportable and upgradeable.

  4. 04

    Surfaced quality signals early

    In-process measurements now trigger alerts when a run drifts toward tolerance limits, so intervention happens during the run rather than at inspection.

The outcome

What changed

Planners work from output data that is current within minutes instead of a shift. Earlier detection of tolerance drift reduced scrap materially in the first quarter, and the paper trail between the floor and the ERP has been eliminated along with the transcription errors that came with it.

1 shift → 2 min
Output data latency
−24%
Scrap and rework
0
Paper production records

Related work

Other engagements you may find relevant

Software EngineeringFinancial Services & FinTech

Automating reconciliation for a payments provider

A finance team spending eight days a month matching settlement files by hand moved to an automated reconciliation engine with a clear exception queue — closing the month in under a day.

Month-end close time
8 days → <1

Month-end close time

Transactions auto-matched
94%

Transactions auto-matched

Adjustments with audit trail
100%

Adjustments with audit trail

Software EngineeringHealthcare & Life Sciences

Replacing a paper patient pathway with a secure portal

Referral, intake, and consent handled on paper and by phone became a patient portal with role-based clinical access, cutting administrative handling time per patient by more than half.

Admin time per new patient
22 → 9 min

Admin time per new patient

Appointment no-shows
−41%

Appointment no-shows

Intake completed before arrival
83%

Intake completed before arrival

Software EngineeringEducation & EdTech

A learning app that works without a connection

A web platform unusable on intermittent mobile data was replaced by an offline-first app that downloads coursework on Wi-Fi and syncs progress later, tripling course completion.

Course completion rate
3.1×

Course completion rate

Mobile data per module
−68%

Mobile data per module

Assessments usable offline
100%

Assessments usable offline

Next step

Tell us what you are trying to fix

Send a short description of the problem and we will reply within one business day. The first call is a 30–45 minute conversation with someone senior — free, and with no obligation.

sales@interwebservices.co.uk128 City Road, London, EC1V 2NX, United Kingdom