We have started the process of looking at a variety of ERP systems that
will fit our business. In evaluating the functionality of each system we ran into the problem that for the most part each system under review performed a similar function.
We therefore looked at how the systems match each of our business processes. We documented each process in a variety of swim-lane diagrams that shows the major areas/systems the process touches and the end result. It was a worthwhile endeavor that gave tremendous insight into broken processes. We then developed a series of requirements and from there built a matrix with our “current state” and “target state”. Our target state being where we want to be with all the bells and whistles.
We took this information and built a matrix with Actions required and assigned a Value and Score. The score is internal this this project but can be changed accordingly. Below is a sample to give you an idea.
Action |
Value |
Score |
Data Entry – New Item |
Core System |
10 |
Data Entry – New Item |
Support system |
5 |
Data Entry – New Item |
Not Supported |
0 |
Data Entry – Update |
Core System |
10 |
Data Entry – Update |
Support system |
5 |
Data Entry – Update |
Not Supported |
0 |
Information Look Up |
Core System |
10 |
Information Look Up |
Support system |
5 |
Information Look Up |
Not Supported |
0 |
Document Creation |
Automated within Core System |
15 |
Document Creation |
Manual- within Core system |
10 |
Document Creation |
Manual – Support System |
5 |
Document Creation |
Not Supported |
0 |
Document Attachment |
Requirements fully supported |
10 |
Document Attachment |
Requirements partially supported |
5 |
Document Attachment |
Not supported |
0 |
Workflow Configuration |
Auto apply from rule book |
10 |
Workflow Configuration |
Set up work flow every time |
5 |
Workflow Configuration |
No workflow supported |
0 |
Sequential Workflow |
Requirements fully supported |
10 |
Sequential Workflow |
Requirements partially supported |
5 |
Sequential Workflow |
Not supported |
0 |
Rule Based Workflow |
Requirements fully supported |
10 |
Rule Based Workflow |
Requirements partially supported |
5 |
Rule Based Workflow |
Not supported |
0 |
For CIOs, trying to compare systems, utilizing a score card approach give insight into what direction to take beyond using just cost and functionality information.
Filed under: CIO, CIO/CTO, IT Process Tagged: project evaluations, score card, technology
