Compare 12 leading ERP products at 1 event

The traditional means of doing To-Be process development and design is to document each As-Is process before performing a gap analysis to identify improvement opportunities.

We believe that in most cases it is not necessary to document As-Is processes, as we can identify the gaps by carrying out Pain Point analysis and Business Process Benchmarking. We have further accelerated To-Be process development by building an extensive library of good practice business processes which provide a ready-made starting point for the design work.


Lumenia worked with Peel Ports to define and map our ‘to-be’ business processes, to inform the specification, selection and implementation of our new ERP system. They combined their knowledge of industry-standard and good-practice processes with the needs and peculiarities of our own business, and challenged our current ways of working where necessary. Richard Farrar, Group Head of IT, Peel Ports

ERP To-Be Process Development and Design


The To-Be development work is led by a Lumenia consultant in a workshop environment involving the business process owner(s) and subject matter experts, using the inputs shown above. The outputs are captured in Visio format during and following each workshop. Often a single follow-up review session is all that is required to finalise each process design.

The To-Be process documents will be used in the ERP selection process to assess vendor and product capability and during the ERP implementation to accelerate the design stage of the project.

The business process review with Lumenia has really given WD-40 the opportunity to think in different ways. Jonathan McCoy, General Manager - IT, WD-40
Set up call decorative image to left of form

Setup a call with our team to discuss your needs