An electronics-protection manufacturer
The implementation that needed no custom code
A manufacturer replacing an ageing core system received a full industrial Priority implementation — and the specification records explicitly that not one software adaptation was required.
- Priority ERP
- Industrial implementation
- System replacement
- Data migration
This customer is described by organisation type, as agreed with them.
- Sector
- Electronics protection manufacturing
- Status
- Delivered and in operation.
The challenge
Accounting, sales, procurement and inventory ran on a core system that had aged. Quality control, service and production were managed in spreadsheets, in documents and in a separate system. This is the common situation in industry: an ageing core system, surrounded by a ring of spreadsheets filling in what it does not do.
Why a standard implementation was not enough
The temptation in a project like this is to reproduce everything the old system did and develop the difference. That is the fast route to an expensive project and a system that is hard to upgrade.
Architectural approach
The approach was the opposite: fit the process to the standard product wherever possible, and develop only where there is no alternative. The specification is built around three separate questions for every need — how the need is met in the standard system, what data migration is required, and what software adaptation is required, if any. That separation forces an explicit decision at every gap instead of deferring it to the development phase.
What was delivered
- A full industrial Priority implementation: procurement, inventory, production and finance
- A quality module
- Bills of material
- Billing and time reporting
- Data migration from the ageing system
- An operating manual written for the customer