What is our primary use case?
The needs are similar to most companies. However, the thing is that the processes are mainly engineering and customization. They have a lot of intercompany transfers as well. Also, regarding the budget, people look at the budget too and eventually went for Infor LN based on pricing.
What is most valuable?
The pricing is good.
I like the way that you can diagram flows and add layers. It has a tree view that gives you a good idea about all the pieces involved in specific procedures.
It's stable.
The solution scales well.
The initial setup is easy.
Support is responsive and ready to help.
What needs improvement?
It's not that intuitive. Sometimes it can be a bit of a counterintuitive situation, meaning you are expecting to find certain options or parameters in some places, and yet they are not there. You have to go through a whole different path that doesn't make sense.
Their menu is so chaotic it confuses people.
They should ease up on the setup of the roles. They should make it much easier to access that area.
For how long have I used the solution?
I've been using the solution for two years.
What do I think about the stability of the solution?
We have never had issues with stability. There aren't bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
It is a scalable product.
How are customer service and support?
Support was helpful. They always replied on time. They were very professional too.
Which solution did I use previously and why did I switch?
I'm also familiar with SAP.
The pro of Infor is that it's relatively cheaper than SAP, for instance, or some other major solution. That said, it's also good for engineering companies. It's the new way to manage engineering companies, especially their production side. Engineering production is customized every time. Every time you have customized production so the setup in general, is slightly different from a company that uses, say, SAP, and they're doing production and sales. Here, it's a different kind of business industry, so the processes that they follow and the procedures are different too. Infor LN is good for this kind of work.
Basically, if you compare SAP and Infor LN, SAP is better in some ways, meaning it can handle much more. However, it's not meant for engineering.
How was the initial setup?
In our case, the initial phase was migration. They were changing from one system to another. They were going from a Microsoft-based ERP system, NVision, to Infor. In that case, it's easier to manage since you already have a layout of the procedures and processes and what they should look like. So communicating all that to Infor LN was not that hard. They're set up for that.
The complexity was the menu, which made it difficult.
Its maintenance is not necessarily difficult, however, it depends. If you're a person that is really used to ERP systems, you will find Infor not that hard to use since everything is out there. It's just chaotic. It just needs better organization. In terms of everything else, everything is there. You can even track your session with the session numbers. Even if you don't know how to get somewhere, if you know your session number, you can go to that session directly.
What about the implementation team?
Info helped handle the deployment part of the implementation.
What's my experience with pricing, setup cost, and licensing?
Many clients use the solution based on reasonable pricing.
Packages are licensed on a yearly basis. I didn't close the deal with a client for that, so I'm not 100% sure if that's the case or if there are other options. I just spoke with the consultant. Our clients always made the deal on their end.
What other advice do I have?
We are using the latest version of the solution.
If a company wants to use the solution, it needs to put in the data in the right places. They need to assign the right information to the right places so that they don't have faults when trying to understand the procedures that they're going to try and do on Infor because the information is part of the conditions. Sometimes the conditions needed to move forward with some steps are difficult to figure out.
It's always good to have organized data, so then you can migrate everything and have procedures working according to their conditions.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
*Disclosure: My company has a business relationship with this vendor other than being a customer: Partner