Cost Factors To Assess When Moving From IBM i To Windows
I frequently hear about IBM i users that are thinking of moving to Windows because it is “more modern” or “mainstream.” We have all heard the IBM i basher point out that “character-based screens” is “old technology.”
Unfortunately, those who want Windows do not really understand IBM i technology and its remarkable architecture. Those who favor IBM i struggle to explain how IBM i is superior for business critical applications.
All too often the decision is made with incomplete information.
Perhaps if those who want to jump ship from IBM i to Windows understood how much it really costs they may think twice – and not make the leap.
So let’s look at the cost factors to move to Windows.
1. New software and annual software fees. New systems often begin with the business application. Well, it is a whole lot more. While the software provider may know their applications, they often are unaware or have unrealistic ideas of what else you will need.
Besides business application licensing, implementation and customization, checkout:
a. Multiple Windows server licensing and Client Access Licenses (CALS)?
b. Windows MS-SQL licensing and CALS?
c. VMware costs and Citrix or Remote desktop in some cases?
d. Supporting software such as WebSphere (it is free with iSeries vs. how much for with Windows)?
2. I have seen many companies neglect these additional licensing costs in their initial feasibility study. How much will this cost?
3. New servers, disk storage, and desktops. Windows business applications tend to be compute- intensive for both servers and desktops. Frequently you need at least 2 servers, often more, – 1) application server (business logic) and 2) database (managed by SQL). Depending on the applications and volumes, you may need more servers. This can mean that you will invest in a SAN (centralized and virtualized disk storage) for your application and data base servers (which are a combination of physical and virtual servers). You may also have to replace the desktops to support new versions of Windows with 8-12+ GB of RAM memory.
How much will this cost?
4. New infrastructure. Windows business applications tend to be client-server. This means that both the servers and the desktops process workloads. This also means there is a lot traffic between the servers and desktops which translates into the need for more bandwidth. Frequently, you will need to re-cable your on-premise environment to handle the extra workload. It can also mean you need more internet bandwidth to support remote user access.
Besides bandwidth, you may need to upgrade your:
a. Routers,
b. Firewall,
c. Backup,
d. Disaster Recovery, and
e. Security (protection from viruses, ransomware, malware, hacking, etc.)
How much will the new infrastructure cost?
5. Implementation, customization and integration. Clearly the business software requires implementation and customization. So do all the parts outlined above that make up the whole for the new system. You will discover you need different teams with different specialties to set up the servers, the desktops, the SAN, and the infrastructure. And, unless you have good coordination, the teams may periodically interfere with each other. (Too frequently I have seen this.)
Who integrates all this to make sure it works? How do you handle cases where sub-systems or devices are not working as expected?
How much does this cost?
6. New staffing and Ongoing Support. New technology requires new and different technology staffing. And, with Windows, you will need a larger IT staff – either with on-site personnel, off-site managed service providers or a combination. How many people will you need? I have read studies where you need from 1 IT person per 25 users to 100 users. While the number of IT staff per user varies, you WILL need more IT personnel for Windows than for IBM i.
Ask the users of the software you are thinking about to understand how they support the application with a combination of onsite and remote technical help?
7. Retraining of personnel. Often this can be the most painful and costly part, trying to get all users to learn new methods and processes.
Additionally, you will require ongoing support for application and software updates. As these updates are applied, there can be a ripple affect where other programs are adversely affected and need remediation.
How much does this cost?
Conclusion
The cost to implement any new business system is expensive. And, stressful of all who are part of the project.
With that said, I have rarely seen businesses do a thorough evaluation of the cost to implement a new system AND consider ALL the associated factors I outlined above.
As a case in point, a client of mine needed to upgrade their custom software to a real ERP solution. We proposed an IBM i solution for $200,000 including the software, implementation, training, report customization and a new IBM server.
They selected a Windows solution instead. I explained that this solution would cost $500,000 for software, implementation, training, report customization and new hardware. I presented a complete documented analysis to support my position.
I was wrong.
It cost them $650,000.
I know because they hired us to set up the Intel servers, integrate the MS licenses and CALS, and the rest. The ERP software that had been budgeted for $150,000 actually cost $300,000, due to “misunderstandings” (I have heard that before. I cannot tell you how many times the software team tripped over our setup so we had to rework much of the integration.)
In my opinion, if business management truly understood the total cost and the stress of implementing a new system…and also factored in that about 80% of all software projects fall short of expectations (the number of out-right failures is very high as well), they would not rush headlong into Windows and abandon the IBM i.
Clearly, decisions must be made based on software, not platform. It is always best to find the software that meets all the business objectives, and then run it on whatever platform is required. Never make a decision based on hardware type.
And if the IBM i system is getting the job done, why change?
My sense is if business management understood the real costs and risks, they would ask, “Where is the ROI to leave the IBM i?”
Leave a Reply