REQUEST A DEMO

IFS Connect: Why does a modern organization need to be competitive?

This year's edition of #IFSConnect truly blew me away – even more than last year's (which I covered in detail in [an article available here - link to be inserted]). What really surprised me was the sheer number of new participants ready to dive into the discourse about the state of Polish enterprises.

For the past week, I've been running on an adrenaline high, a feeling I haven't experienced since tech events 15-20 years ago... But now that the initial excitement has somewhat settled, I've decided to sketch out a brief summary of this year's IFS Connect. Ready? Let's dive in!


IFS at the forefront of ERP providers (again!)

It's such a great feeling to see a system I worked on as a young programmer still thriving and dictating terms to other ERP systems on the market. Of course, having IFS isn't a mandatory requirement for every manufacturing company, but its cohesion and scalability allow for efficient implementation of changes in processes and IT architecture itself, without having to build things from scratch.

Observing implementations and improvements in manufacturing environments, I've seen how dynamically the IFS ecosystem is developing and how many new solutions it offers to companies seeking flexibility and operational advantage. I particularly focused on the seemingly endless list of functionalities that further enrich IFS's already broad offering. Among them:

  • Extensive configuration capabilities,
  • The Camunda process management engine (BPMS), now fully integrated with the IFS application,
  • The layered architecture of IFS Cloud, enabling system modifications by both IFS partners and their clients.

Like any technology, IFS sometimes needs the hand of a skilled solutions architect to unlock its full potential for a company. With years of experience, I can confidently say that subsequent software versions are slowly but surely providing answers to customer demands – whether it's customization options or core functionalities. I'm keeping my fingers crossed for the continued development of this technology!

What's up with AI?

In my previous post, I mentioned that Artificial Intelligence was omnipresent at this conference; it felt like it was everywhere – I half-expected it to be serving me coffee! To delve even deeper into the topic, on Monday evening, we organized a meeting with leaders/experts where AI and ML were the main focus. Together with @Magdalena Foltyn, we moderated a discussion about "where, what for, and why." We dissected AI with representatives from 6 manufacturing companies.

The conclusions fill me with cautious optimism and motivate further work in terms of:

  • Defining the business objective: precisely identifying where exactly in the business process we want to use AI/ML. This ranges from a relatively common "email reader" to a production line leader supported by an AI/ML-driven toolset in their daily work, or even in planning and decision-making processes, where an optimizer based on a genetic algorithm or PSO would feel right at home.
  • Preparing and defining the IT systems architecture to be ready for AI/ML adoption – e.g., connecting data sources, systems, and services using an integration platform.
  • Ensuring access to "private access" AI/LLM engines and algorithms, because, beware, while using open, publicly available ones (e.g., ChatGPT) is okay, it can lead to uncontrolled data leaks.
  • It's time to start thinking about an environment where we can create and control AI agents ourselves.

Let's remember, however, that AI is just a tool – and, contrary to popular belief, not as super new as it might seem. We can't expect to apply super-efficient algorithms that act as a quick fix for every dysfunctional process in a company. Quite the opposite – when we accelerate these processes without proper foundations, we risk a chaotic mess.

That's why we need to talk about AI and the role artificial intelligence plays in a given company. And we need to do it loudly and publicly, so this branch of digitalization can fulfill its role in enterprises 100%.

BiModal Scheduler – a classic challenge for polish enterprises

I decided that on our booth's TV, we'd showcase our latest brainchild: BiModal Scheduler. I knew how crucial this topic is for manufacturing companies. Honestly, I didn't expect such a positive reaction and so many engaging discussions. It definitely reinforced my belief that, like other processes, production scheduling is a highly individual matter for each enterprise. Of course, there are some standard fundamentals, but handing this process over to a "black box" called APS probably isn't the best idea.

This solution, based on the most advanced heuristic algorithms and the most beautiful schedule visualization in the world, captivated many visitors to the BiModal booth. Consequently, I know exactly what the #biModalPlanning team will be doing for the next 2 months: preparing POVs for furniture, profile, and chemical product manufacturers, and I'm also hoping for a visit to a few food & beverage companies.

May the PSO be with you!

Resilient ERP: how to implement ERP to be fully adaptable to a changing business environment?

And I almost forgot – I had the pleasure of presenting the concept and methods we use to implement IFS projects, supported by low-code platforms. As usual, the audience was great and actively participated in my 30-minute speech, which I'll tell you more about in an upcoming article.


IFS Connect 2025: conclusion

This is just a small slice of those two exceptionally intense days. One thing makes me happy – and from what I see, it also made me happy at last year's edition of the event: the growing awareness of the need for businesses to go through the digitalization process and gain knowledge about digital transformation. Thank you for the opportunity to participate!

If we didn't have a chance to meet at IFS Connect, or if we left any discussions open – don't hesitate to reach out! We can schedule a meeting right away.


Request a demo

Leave us your phone number. We will contact you shortly!

  • United States+1
  • United Kingdom+44
  • Afghanistan (‫افغانستان‬‎)+93
  • Albania (Shqipëri)+355
  • Algeria (‫الجزائر‬‎)+213
  • American Samoa+1
  • Andorra+376
  • Angola+244
  • Anguilla+1
  • Antigua and Barbuda+1
  • Argentina+54
  • Armenia (Հայաստան)+374
  • Aruba+297
  • Ascension Island+247
  • Australia+61
  • Austria (Österreich)+43
  • Azerbaijan (Azərbaycan)+994
  • Bahamas+1
  • Bahrain (‫البحرين‬‎)+973
  • Bangladesh (বাংলাদেশ)+880
  • Barbados+1
  • Belarus (Беларусь)+375
  • Belgium (België)+32
  • Belize+501
  • Benin (Bénin)+229
  • Bermuda+1
  • Bhutan (འབྲུག)+975
  • Bolivia+591
  • Bosnia and Herzegovina (Босна и Херцеговина)+387
  • Botswana+267
  • Brazil (Brasil)+55
  • British Indian Ocean Territory+246
  • British Virgin Islands+1
  • Brunei+673
  • Bulgaria (България)+359
  • Burkina Faso+226
  • Burundi (Uburundi)+257
  • Cambodia (កម្ពុជា)+855
  • Cameroon (Cameroun)+237
  • Canada+1
  • Cape Verde (Kabu Verdi)+238
  • Caribbean Netherlands+599
  • Cayman Islands+1
  • Central African Republic (République centrafricaine)+236
  • Chad (Tchad)+235
  • Chile+56
  • China (中国)+86
  • Christmas Island+61
  • Cocos (Keeling) Islands+61
  • Colombia+57
  • Comoros (‫جزر القمر‬‎)+269
  • Congo (DRC) (Jamhuri ya Kidemokrasia ya Kongo)+243
  • Congo (Republic) (Congo-Brazzaville)+242
  • Cook Islands+682
  • Costa Rica+506
  • Côte d’Ivoire+225
  • Croatia (Hrvatska)+385
  • Cuba+53
  • Curaçao+599
  • Cyprus (Κύπρος)+357
  • Czech Republic (Česká republika)+420
  • Denmark (Danmark)+45
  • Djibouti+253
  • Dominica+1
  • Dominican Republic (República Dominicana)+1
  • Ecuador+593
  • Egypt (‫مصر‬‎)+20
  • El Salvador+503
  • Equatorial Guinea (Guinea Ecuatorial)+240
  • Eritrea+291
  • Estonia (Eesti)+372
  • Eswatini+268
  • Ethiopia+251
  • Falkland Islands (Islas Malvinas)+500
  • Faroe Islands (Føroyar)+298
  • Fiji+679
  • Finland (Suomi)+358
  • France+33
  • French Guiana (Guyane française)+594
  • French Polynesia (Polynésie française)+689
  • Gabon+241
  • Gambia+220
  • Georgia (საქართველო)+995
  • Germany (Deutschland)+49
  • Ghana (Gaana)+233
  • Gibraltar+350
  • Greece (Ελλάδα)+30
  • Greenland (Kalaallit Nunaat)+299
  • Grenada+1
  • Guadeloupe+590
  • Guam+1
  • Guatemala+502
  • Guernsey+44
  • Guinea (Guinée)+224
  • Guinea-Bissau (Guiné Bissau)+245
  • Guyana+592
  • Haiti+509
  • Honduras+504
  • Hong Kong (香港)+852
  • Hungary (Magyarország)+36
  • Iceland (Ísland)+354
  • India (भारत)+91
  • Indonesia+62
  • Iran (‫ایران‬‎)+98
  • Iraq (‫العراق‬‎)+964
  • Ireland+353
  • Isle of Man+44
  • Israel (‫ישראל‬‎)+972
  • Italy (Italia)+39
  • Jamaica+1
  • Japan (日本)+81
  • Jersey+44
  • Jordan (‫الأردن‬‎)+962
  • Kazakhstan (Казахстан)+7
  • Kenya+254
  • Kiribati+686
  • Kosovo+383
  • Kuwait (‫الكويت‬‎)+965
  • Kyrgyzstan (Кыргызстан)+996
  • Laos (ລາວ)+856
  • Latvia (Latvija)+371
  • Lebanon (‫لبنان‬‎)+961
  • Lesotho+266
  • Liberia+231
  • Libya (‫ليبيا‬‎)+218
  • Liechtenstein+423
  • Lithuania (Lietuva)+370
  • Luxembourg+352
  • Macau (澳門)+853
  • North Macedonia (Македонија)+389
  • Madagascar (Madagasikara)+261
  • Malawi+265
  • Malaysia+60
  • Maldives+960
  • Mali+223
  • Malta+356
  • Marshall Islands+692
  • Martinique+596
  • Mauritania (‫موريتانيا‬‎)+222
  • Mauritius (Moris)+230
  • Mayotte+262
  • Mexico (México)+52
  • Micronesia+691
  • Moldova (Republica Moldova)+373
  • Monaco+377
  • Mongolia (Монгол)+976
  • Montenegro (Crna Gora)+382
  • Montserrat+1
  • Morocco (‫المغرب‬‎)+212
  • Mozambique (Moçambique)+258
  • Myanmar (Burma) (မြန်မာ)+95
  • Namibia (Namibië)+264
  • Nauru+674
  • Nepal (नेपाल)+977
  • Netherlands (Nederland)+31
  • New Caledonia (Nouvelle-Calédonie)+687
  • New Zealand+64
  • Nicaragua+505
  • Niger (Nijar)+227
  • Nigeria+234
  • Niue+683
  • Norfolk Island+672
  • North Korea (조선 민주주의 인민 공화국)+850
  • Northern Mariana Islands+1
  • Norway (Norge)+47
  • Oman (‫عُمان‬‎)+968
  • Pakistan (‫پاکستان‬‎)+92
  • Palau+680
  • Palestine (‫فلسطين‬‎)+970
  • Panama (Panamá)+507
  • Papua New Guinea+675
  • Paraguay+595
  • Peru (Perú)+51
  • Philippines+63
  • Poland (Polska)+48
  • Portugal+351
  • Puerto Rico+1
  • Qatar (‫قطر‬‎)+974
  • Réunion (La Réunion)+262
  • Romania (România)+40
  • Russia (Россия)+7
  • Rwanda+250
  • Saint Barthélemy+590
  • Saint Helena+290
  • Saint Kitts and Nevis+1
  • Saint Lucia+1
  • Saint Martin (Saint-Martin (partie française))+590
  • Saint Pierre and Miquelon (Saint-Pierre-et-Miquelon)+508
  • Saint Vincent and the Grenadines+1
  • Samoa+685
  • San Marino+378
  • São Tomé and Príncipe (São Tomé e Príncipe)+239
  • Saudi Arabia (‫المملكة العربية السعودية‬‎)+966
  • Senegal (Sénégal)+221
  • Serbia (Србија)+381
  • Seychelles+248
  • Sierra Leone+232
  • Singapore+65
  • Sint Maarten+1
  • Slovakia (Slovensko)+421
  • Slovenia (Slovenija)+386
  • Solomon Islands+677
  • Somalia (Soomaaliya)+252
  • South Africa+27
  • South Korea (대한민국)+82
  • South Sudan (‫جنوب السودان‬‎)+211
  • Spain (España)+34
  • Sri Lanka (ශ්‍රී ලංකාව)+94
  • Sudan (‫السودان‬‎)+249
  • Suriname+597
  • Svalbard and Jan Mayen+47
  • Sweden (Sverige)+46
  • Switzerland (Schweiz)+41
  • Syria (‫سوريا‬‎)+963
  • Taiwan (台灣)+886
  • Tajikistan+992
  • Tanzania+255
  • Thailand (ไทย)+66
  • Timor-Leste+670
  • Togo+228
  • Tokelau+690
  • Tonga+676
  • Trinidad and Tobago+1
  • Tunisia (‫تونس‬‎)+216
  • Turkey (Türkiye)+90
  • Turkmenistan+993
  • Turks and Caicos Islands+1
  • Tuvalu+688
  • U.S. Virgin Islands+1
  • Uganda+256
  • Ukraine (Україна)+380
  • United Arab Emirates (‫الإمارات العربية المتحدة‬‎)+971
  • United Kingdom+44
  • United States+1
  • Uruguay+598
  • Uzbekistan (Oʻzbekiston)+998
  • Vanuatu+678
  • Vatican City (Città del Vaticano)+39
  • Venezuela+58
  • Vietnam (Việt Nam)+84
  • Wallis and Futuna (Wallis-et-Futuna)+681
  • Western Sahara (‫الصحراء الغربية‬‎)+212
  • Yemen (‫اليمن‬‎)+967
  • Zambia+260
  • Zimbabwe+263
  • Åland Islands+358
Thank you! Your message has been sent.
Unable to send your message. Please fix errors then try again.