Case Study Field service · Operations

A small checklist that stopped very expensive return trips.

A European pump manufacturer's technicians could travel hundreds of kilometres and discover that one belt, fitting or seal was missing. Costel built a focused product-specific pick-list that turns vehicle loading into a physical verification step. It launched in 2019, ran for seven years without maintenance, and remains part of the team's daily work.

Client
Anonymized European pump manufacturer
Business unit
Netherlands service branch
Engagement
Pick-list workflow tool
Initial launch
2019
Platform update
2026
An industrial pump technician checking service parts before a field visit
Industrial Pump Pick-List: A product-specific checklist made vehicle loading verifiable and stayed useful for seven years.
By the numbers
5Service teams
500Pumps in the system
100Product series
7 yearsContinuous production use

One forgotten part could turn one service visit into two.

Technicians loaded their own vehicles from memory. Missing a drive belt, bolt, fitting, seal or small accessory could mean driving 200 kilometres or more back to the branch.

The cost was larger than fuel: lost technician time, delayed repairs, disrupted schedules and a customer waiting while a preventable trip was repeated.

Select the pump, print the right list, check every item by hand.

Costel kept the application deliberately small. A user selects the relevant pump, and the system generates a list with the product photo, required parts, materials, accessories and an empty checkbox beside every item.

The list can be printed or emailed. During vehicle loading, the technician marks each box with a pen. The workflow does not automate the technician out of the process; it places a reliable control at the exact point where the errors happened.

About 500 pumps across 100 series and ten brands are mapped to a catalogue of roughly 100 service parts. No ERP, inventory or service-history integration was needed.

A deliberately narrow product: select, verify, print and load.

Engineering note

The best scope was the smallest one that controlled the failure. By avoiding unrelated ERP and inventory features, the tool stayed simple enough to survive seven years without maintenance while still changing the physical loading behavior.

Costel Project partner · the build

The client says picking errors became practically nonexistent.

Five service teams moved from a memory-based loading process to the same repeatable check.

The original CodeIgniter and MySQL application entered production in 2019 and continued for roughly seven years without maintenance or feature work. When Costel checked back in 2026, it was still used every day.

The framework and PHP environment were then upgraded while the familiar field workflow stayed unchanged.

CodeIgniter PHP MySQL Printable PDF Email delivery
Role
Workflow analysis, architecture & delivery
Partner
Costel
Model
Focused internal tool
Status
Daily production use
Project partner Costel

Removing field-service errors? See field services and events, software builds, or the software ROI calculator.

Next / Your build

Taking on new builds

Have something in mind?

Tell us what you're making. We reply within one business day, and you get a fixed price and a date in writing before any code.