Business Process Mapping

Start with a goal or purpose of this replacement. Usually a short statement of deficiencies in SAP and new features in your ERP system. Then map it back to the old vision statement of your old SAP implementation plan. Usually that also provide a sanity check, does it really worth the replacment.

Break it down to current process area, modules, features and data. Get another person to do the same for the new system. Then 2 person sit together to do the mapping. Its best to find two person who are true believers of their own system, ie. one SAP expert, another ERP. The facilitator should be their boss or a very process oriented person.

As for tracking of this mapping, try Rational Requisite Pro which can definitely do the job but expensive. The other extreme is ofcourse, Excel.

Just through in a bit more nonsense of mine, stereotypically replacing system with a one-to-one mapping replacement is not the best move. But if replacement had to happen anyway, then you may as well take the chance to review actual processes, enhance and implement new processes with the new system. That way, you may get more beneifts than just the initial ROI.

In terms of process mapping software, I start with existing documentation and try and create an outline of the process in bullet points.

Once I have an outline, I create a VISIO flowchart of the existing. For processes such as an ERP, I would create a process flow which included "swimlanes", which is a way of dividing up a flowchart into zones. For an ERP I would use Inputs, Outputs, Processes and Controls.

Once you have created the processes, you need to verify them with a subject matter expert. This is an interative process with some back and forth.

Once you have all the processes that you want mapped, you might try looking into some of the Six Sigma techniques - Value Stream mapping -where you determine which parts of the process add value, and which parts do not. The idea then is to reduce or eliminate the non-value added parts fo the process.

You might also want to hold meetings to determine what the issues are with the current process. I use Ishikawa diagrams(fishbones) to try and get to root cause.

Once you have the above information, the design should become easier.

James