+19
Hello
Can any IFS Customers, Partners or IFS Consultants in the Community elaborate on an upgrade you’ve made from IFS App9 to the Cloud?
We are in App9 UPD14, we are debating to go through App10 or not. What do you think?
We have quite a lot of customizations and configurations and maybe, only maybe, some of them will not be needed after the upgrade.
Thanks!
+4
It was suggested as an option for time and potential cost saving for the first part of the overall upgrade project.
Just re-read this thread. We have recently started the upgrade from 9 to 10 project that I mentioned above and the golive date in prod is almost a year from now. We have a bunch of customizations (n ~200).
Our biggest reasons not to jump to IFS Cloud directly:
A) upgrading the customizations without having to re-plan every process at once (which would have required waay too much effort. It would be a partial re-implementation with changes needed to many e2e processes and also to other connecting systems).
B) continue using IEE to avoid a big bang project
C) agreement related reasons
We have tried to “cut the elephant to smaller pieces” by doing a technical code upgrade first and acknowledge that there are many continuation projects to do when first in IFS10. These include the integration technique change to using rest api’s, the switch to Aurena UI and some internal component switchovers from older to newer component (like budgeting functionalities).
At the same time it already worries a lot thinking about the possible later Cloud project. How can you have a reasonable business case to justify the project financially? How can you get rid of your customizations if the result is that effectiveness suffers and manual work increases. It sounds like reinventing the wheel when you have to re-implement all your processes (A on the list above) moving from 10 to Cloud.
+21
Hi
I’ve been following the IFS Application 10 to IFS Cloud upgrade discussions carefully because we have been thinking of upgrading to IFS Cloud potentially in 4Q 2023. We keep all our servers on-premise and we are looking at replacing our servers in 2023 and I’d like to account for IFS Cloud as part of the server analysis we will be doing in the coming weeks and months.
Do either of you have real world IFS Cloud performance and server configurations as part of your testing? I’m concerned about memory, processor and network band width on the application server and database servers in particular. IFS Cloud changing the application server equation with Aurena and I’m assuming the application server will require more resources to provide similar performance to using IEE.
Any information you have would be of help.
Regards,
William Klotz
I’ll see what I can find that I can share.
Expect that whatever you had for IEE, needs to be twice as good and you can no longer share servers as we did with our non-Prod environments previously. It is three servers per environment and if they arent close to the recommended specs, performance with Cloud is abysmal.
The only server we are sharing right now it is the DB non-prod. Like
Our go live is planned for begin December, so we are working already on memory, working and processor optimization.
Thanks,
Gianni Neves
+1
Interesting read...
We are currently looking to upgrade from IFS apps 9 to on prem IFS cloud within the next 4 months...
We have a prod and dev environment 2 servers each (app server and database server)
How flexible are the licensing with cloud, is it like MS Office licenses - scale up and down as you need?
Just re-read this thread. We have recently started the upgrade from 9 to 10 project that I mentioned above and the golive date in prod is almost a year from now. We have a bunch of customizations (n ~200).
Our biggest reasons not to jump to IFS Cloud directly:
A) upgrading the customizations without having to re-plan every process at once (which would have required waay too much effort. It would be a partial re-implementation with changes needed to many e2e processes and also to other connecting systems).
B) continue using IEE to avoid a big bang project
C) agreement related reasons
We have tried to “cut the elephant to smaller pieces” by doing a technical code upgrade first and acknowledge that there are many continuation projects to do when first in IFS10. These include the integration technique change to using rest api’s, the switch to Aurena UI and some internal component switchovers from older to newer component (like budgeting functionalities).
At the same time it already worries a lot thinking about the possible later Cloud project. How can you have a reasonable business case to justify the project financially? How can you get rid of your customizations if the result is that effectiveness suffers and manual work increases. It sounds like reinventing the wheel when you have to re-implement all your processes (A on the list above) moving from 10 to Cloud.
Just an update on my previous comments on this discussion. We have now been live in IFS10upd16 for a month and situation is fairly stabile. The project went on schedule but a lot over budget thanks to f.ex. higher than anticipated work related to keepin the customizations along. We did get rid of some CRIM’s, mostly in areas like HR where we have moved to other solutions. Most of the other CRIM’s we still need because getting rid of them would cause more manual work or getting rid of them would cost more than continue paying for them until the Cloud project starts.
Now the focus is shifting to the above mentioned “continuation projects” where the aim is to pave way for the Cloud version.
One of my main concerns regarding Cloud right now is to have a realistic understanding of the money and resources needed to keep along in the Release-and-update train. There are some good videos here on Community explaining this that I have to look deeper into but in general I’d appreciate less marketing talk and more hard facts about the requirements the Cloud version has to a customer compared to the older Apps versions.
We have bitten the bullet and signed the contract to upgrade from IFS APPS9 to Cloud! Anyone else on the same journey? Am curious on how easy it is to uplift your crims?
Coming up on 2 years since we made the initial inquiry to IFS on the upgrade….still not live, still working through it. The newer versions are getting close to what is required, but it has been an arduous road.
Can I ask Shawn what your biggest pain points are? I was hoping that the later releases would have eased some of the bug issues.
Are you getting reasonable support now from IFS?
We are currently planning on starting a Apps9upd17->Apps10upd15 project. The 10-upgrade was first thought around 2019 but it did not provide anything special then so we have done two Apps9 sub-version updates since then instead (you could argue were they worth it). Main driver for the 10-upgarade is keeping up in supported versions and trying to minimize the tech debt. During the Apps10 usage the aim is to do step-by-step integration renewals and transitions to the new UI.
The remaining supported life of 6 years until 2028 for Apps10 is not that long when you wonder the business case for the total implementation projects and related work and trouble. Reading the above thread about all the challenges the Cloud brings along it really makes one think is this work with a meaning :D.
+1
Hi
Hi
How is the progress with your upgrade to cloud?
+3
We have just started looking at the academy for training and received our first install to start testing with. We have not even got that up and going yet. No real experience with the APP other than sandbox/race environment.
Basically, nothing to report yet.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.