What is our primary use case?
My organization only uses the finance module, but it depends on the modules your company needs.
What is most valuable?
The most valuable aspect for me is the finance module. I've worked with various companies, but I'm typically involved in finance. However, my previous position was with a utility company, so that involved distribution, HR, and the supply chain.
All the modules are valuable in their own right, but everything has to go through the ERP. IFS has done an excellent job integrating the various modules to complete these processes. My expertise is in the finance module, but I have used the other verticals. It's an all-around good product.
What needs improvement?
I'm a business analyst, so I do a lot of customer-facing work. I take calls from businesses I have to troubleshoot. One thing that bugs me is the error messages you get from IFS. If I get an error message, I have to dig to find the cause because, often, the error message doesn't precisely describe the problem. It'll hint about where the problem lies, but you have to work to find the root cause. It doesn't help in my situation. You expect an error message to point to the field or what is causing the issue.
If they cleaned up their error messages, it would make things so much easier. Typically, an error message will focus on one field. It's one comment. Obviously, you don't want to see a lengthy message on the screen. I don't know if it's a translation issue because the organization is Swedish, but the wording of the messages isn't native English.
There's another issue for anyone using the system. IFS is based on companies. You create a company in the system called Company 100. When you bring on another plant or office, you need to make another company called Company 101. IFS has this popup box, so you need to be conscious of the company you're working with at any time. If you need to switch to another company, you must click on this right mouse button and say "Change company." It brings up a dialogue box with all the companies you can access; then, you put a checkmark in the box of the company you want to go to.
When people start using IFS, they have difficulty grasping this concept, but you constantly have to switch companies depending on what you're doing. I think everybody's in agreement that you have to go through this process. I don't know what they can do about it, but it causes issues.
They do have a popup at the bottom of the screen that indicates which company you're working in. However, people don't always look at that when they are busy. They might start processing invoices in Company 100 when they should be working at Company 101. You have to manually switch companies, which frustrates users. I'm sure IFS has heard this over and over.
When each user is set up, they're assigned a default company. My default company could be 100, so I start in Company 100 when I log into IFS, but if I have to do business with two other companies, I have to select the company and click back to the original company when I'm done. I can't say it's a minor thing because it causes a lot of frustration.
For how long have I used the solution?
I have been using IFS Applications for around 14 years.
What do I think about the stability of the solution?
I rate IFS nine out of 10 for stability. In the last 14 years, the only crashes or outages have been due to internal problems, not the application. For example, the first company ran IFS on an in-house server, and we had server issues. The application itself is solid. Any issues have been caused by hardware on our end or a server problem on the cloud platform where it's hosted.
What do I think about the scalability of the solution?
I rate IFS eight out of 10 for scalability. Each release has several updates before they bring out the new release. For example, my company is on version 10, update 7. Some of the issues or projects we want to do require us to be on update 19. At times, it isn't easy to go from update 7 to update 12
We have to check with IFS to see if we can automatically go from 7 to 12 and not have to implement the update incrementally. We contacted IFS, and they told us there are no significant code changes so we can go straight to 12. Sometimes, there are restrictions depending on the code that's been changed. Or they might have added new functionality that requires you to update step by step rather than make that big jump between updates.
The other day, we talked about going from 12 to 19, which is a significant jump. We're unsure if we can do that directly or if we must apply other updates along the way. You don't want the current processes affected by moving to a higher update. Our team has to do a lot of work to test all our processes in a test environment with 12. If you do it incrementally, you have to try each update.
When it's time to implement these updates, they should know what issues they might encounter. Not every customer will have the same problems. A lot of it comes down to customization. If we've requested modifications to the core system, that also factors into our testing. IFS is delivering the update to the core solution, but we have to consider custom fields, venues, pages, etc., that we have in place. We have to make sure that these work with the updates.
How are customer service and support?
I rate IFS support eight out of 10. IFS technical support is excellent. Their 24/7 support center is based in Sri Lanka, but they have a North American support center in Michigan. They're responsive and available. Sometimes, we have to submit tickets to IFS because we can't figure out what's going on. For example, we might run into a problem during an upgrade, and we need to contact them to see if there's a bug fix or workaround.
It's all based on severity and the terms outlined in the SLA. Critical incidents, like a system shutdown, get an immediate response, but they're a bit delayed for a medium-severity issue. You'll explain the problem to them in the ticket, and they'll eventually come back with a patch or some other fix. Sometimes they're not the quickest for mid-level stuff.
Overall, it's not an issue, but some cases are passed from one department to another, and it takes them a while to get back to us. The technical support is generally excellent. There might be room for improvement in how they handle case submissions. It seems to get bogged down a little bit.
How would you rate customer service and support?
How was the initial setup?
I rate IFS seven out of 10 for ease of setup. IFS has done a great job on the documentation. The setup's complexity depends on the implementation you're doing. We originally had IFS on in-house servers then they migrated to the cloud. There are different setups, so the deployment will also vary depending on the version you're using, but they're excellent at leading you through the implementation process and making their resources available to help you.
What about the implementation team?
IFS will assign specific resources to support your implementation, and your team doesn't change, so you know who you're dealing with. You work with the same people through the implementation unless someone goes on vacation or leaves the company. There's consistency in the team you work with.
What's my experience with pricing, setup cost, and licensing?
IFS is competitively priced. I've been in several selection processes where the company has narrowed it down to three or four ERPs. You go through a process where everybody has input. In all the evaluations I've been involved in, IFS has always come up as number one or two.
That's considering feedback from various departments like finance. Can we use it? Is it going to do what we want for, say, manufacturing? IFS has always been a top choice, and part of that is cost.
What other advice do I have?
I rate IFS Applications eight out of 10. I have been using it for 14 years, so they're doing something right.
Disclosure: I am a real user, and this review is based on my own experience and opinions.