If your business runs BPCS or Infor LX on IBM i, you have almost certainly heard something about managed services that gave you pause. Maybe it raised concerns about losing control of your environment. Maybe it sounded like a solution for companies without internal resources — not for a shop that still has a team. Maybe it just sounded like outsourcing your entire IT operation to someone who doesn’t know your system.
None of those concerns are unreasonable. None of them are accurate either.
What follows are the three misconceptions that most consistently prevent BPCS and Infor LX shops from making a decision that is clearly in their interest — and what is actually true in each case.
IBM i skills are now the top concern for 69% of IBM i users, according to the 2026 Fortra IBM i Marketplace Survey, surpassing cybersecurity for the first time in nine years.
Misconception 1: Managed Services Means Outsourcing Your Whole IT Department
Traditional managed services cover infrastructure: system monitoring, OS patching, PTF updates, backup, and hardware management. That is a well-defined and valuable service.
What it does not cover is your ERP configuration, your BPCS or Infor LX business rules, your RPG customizations, your EDI trading partner mappings, or the institutional knowledge your team has spent decades building. Those are application-layer responsibilities — and they require a different kind of provider entirely.
This matters because the managed services market for IBM i shops operates across separate, stackable layers.
Most engagements cover the infrastructure layer: the MSP is responsible for keeping the IBM i OS current, applying PTFs on schedule, managing backups and disaster recovery, and monitoring the environment around the clock.
VIRTUTEM operates at the application layer: ERP support and configuration for BPCS and Infor LX, RPG and CL code, manufacturing workflow coverage, business process management, and EDI — including translator support, trading partner mapping, and VAN liaison.
As an Infor Alliance Partner since 2016, and Infor’s only designated business partner for PRMS services in North America, VIRTUTEM brings application-layer depth that a generalist IBM i MSP cannot replicate.
That is a distinct engagement from infrastructure managed services, and it is the layer where the real expertise gap exists for BPCS and Infor LX shops. Your infrastructure provider keeps the IBM i running. VIRTUTEM keeps the business running.
Seventy percent of IBM i shops run custom applications, according to Fortra’s 2025 survey. That investment stays with your team unless you’ve explicitly agreed otherwise.
Misconception 2: Managed Services Means Giving Up Control
The control risk with ERP LX managed services is real — but it comes not from engaging a provider, but from engaging one without a governance structure that keeps accountability on the client side.
In practice, ERP LX managed services engagements without built-in accountability mechanisms drift in predictable ways: Infor LX configurations go undocumented, enhancement backlogs accumulate without resolution, and month-end job streams start taking longer without anyone flagging the cause.
The client has shed internal application expertise, has no one left to evaluate what is being delivered, and the contract does not enforce accountability with sufficient specificity to surface the gap.
The contract is only as strong as the oversight that enforces it.
What that looks like in practice:
- Contractual audit rights to configuration logs, enhancement records, and monitoring data on request
- SLAs with specific metrics — not just general uptime language, but Infor LX job stream performance thresholds, incident response windows, and enhancement delivery timelines
- A designated client-side owner with enough application familiarity to review a delivery report and ask the right question
- Periodic independent technical reviews by Infor LX specialists who have no stake in the MSP relationship
None of this requires a full internal Infor LX or BPCS team. It requires a structure defined before the contract is signed.
VIRTUTEM builds this governance structure into every managed services engagement by default. Configuration changes are logged when they are made and are accessible to the client on demand. SLAs cover ERP batch job performance thresholds and EDI transaction integrity, not just system uptime. Monthly delivery reports give the client-side owner a clear view of what was done, what is outstanding, and what is coming.
The documentation produced during the engagement belongs to the client — it does not disappear if the relationship ever ends. That is what accountability looks like in practice, not just in a contract clause.
Misconception 3: IBM i ERP Managed Services Is Only for Companies Without Internal Resources
The organizations moving most deliberately toward ERP LX Managed Services are not the ones without internal teams.
They are the ones with strong internal teams who have recognized that the people retiring are the people who know the Infor LX environment. The ones who know where every BPCS customization lives, how the MRP job stream was configured fifteen years ago, and why that RPG program produces the output it does.
That is application knowledge, and when it walks out the door, the IBM i keeps running. It is the ERP that becomes unmanageable.
IBM i skills have risen from a top concern for 45% of IBM i shops in 2020 to 69% in 2026. That’s a 24-percentage-point climb in six years.
The demographic driver is direct: the core IBM i workforce was built by a generation whose youngest members are now 62.
The replacement cohort with genuine depth in Infor LX configuration, BPCS customization history, and manufacturing ERP operations does not exist at a comparable scale.
What managed services preserve is continuity at the application layer: the ERP configuration remains understood, the business logic remains documented, and the manufacturing workflows continue to run as expected.
That is the gap VIRTUTEM is built to fill. With over 30 years of experience supporting BPCS and Infor LX environments across North American manufacturing and distribution, a dedicated in-house EDI team, and Infor Alliance Partner status, VIRTUTEM provides the application-layer continuity that strong internal teams rely on when their most experienced people move on.
In one current engagement, a global industrial manufacturer’s internal BPCS team was deliberately transitioned onto a concurrent SAP implementation. VIRTUTEM stepped in, onboarded through structured shadowing, and reached primary support ownership within five months — without disrupting the transformation program or the legacy operations running alongside it. That engagement is still active today.
Where to Start
Once these misconceptions are out of the way, what remains is a practical question: which layer of your BPCS or Infor LX environment needs external specialist depth, and what governance structure ensures your provider is actually delivering it.
If you are evaluating providers, our guide to what to look for in an IBM i ERP Managed Services provider covers the specific questions to ask, the SLA terms that matter, and how to evaluate EDI capability — before you sign anything.
For most organizations reading this, the application layer is the urgent answer.
The right time to act is while someone who knows the environment is still available to participate in the transition. Once that person retires or resigns, the onboarding takes longer, costs more, and carries more risk. If a departure is on the horizon within the next 12 to 24 months, this evaluation should be underway now.
IBM i is not a platform in transition. Forty-five percent of shops plan no changes to their footprint; 20% plan to expand usage.
Start with VIRTUTEM’s Complimentary ERP Environment Assessment
Not sure whether managed services are the right fit for your environment? That is exactly the right question — and it is one VIRTUTEM’s ERP Architects can answer specifically, not generically.
The ERP Environment Assessment is a structured review of your BPCS or Infor LX configuration on IBM i: active job streams, RPG customization inventory, EDI setup, and current support coverage gaps. It is delivered as a written report with no obligation. If managed services make sense for your environment, the assessment will show exactly what scope they would need to cover. If they don’t, that report is still a useful picture of where your environment stands.
Request your complimentary ERP Environment Assessment at virtutem.com/contact-us or call us directly to describe your environment.
Frequently Asked Questions
Does IBM i ERP managed services mean my internal IT team becomes redundant?
No. ERP managed services at the application layer cover the BPCS or Infor LX configuration, RPG customizations, job streams, and EDI environment — the knowledge that walks out when experienced staff retire. Your internal IT team retains ownership of infrastructure, user access, and day-to-day operations.
The two are complementary, not competing. Most engagements are structured specifically to keep the client in control while closing the application expertise gap.
How do I maintain control over my BPCS or Infor LX environment with a managed services provider?
Through contractual governance built into the agreement before it is signed. That means audit rights to configuration logs and enhancement records, SLAs that cover ERP application performance, not just system uptime, a designated client-side owner, and periodic independent reviews.
A provider who resists this structure is a provider who does not want to be held accountable. Walk away.
Is IBM i ERP managed services only for companies that have lost their internal team?
The opposite is often true. The organizations that engage managed services most effectively are those that still have an experienced internal resource and use the transition period to transfer knowledge in an orderly way.
Waiting until after a retirement means onboarding without the one person who could explain what everything does. Earlier is always better.
Does BPCS or Infor LX managed services include EDI support?
It depends on the provider. Most generalist IBM i MSPs do not have dedicated EDI staff and exclude EDI from their contracts.
VIRTUTEM includes EDI as part of its application-layer managed services: translator support (Gentran, TrustedLink, IBM Sterling Commerce), in-house mapping, and VAN liaison. Confirm EDI scope explicitly with any provider before signing — it is one of the most common gaps in IBM i ERP managed services contracts.
What is the difference between IBM i managed services and IBM i ERP managed services?
IBM i managed services typically refer to infrastructure-layer support: OS management, PTF maintenance, backups, hardware, and monitoring. IBM i ERP managed services cover the business application running on that infrastructure — the BPCS or Infor LX configuration, RPG and CL code, job streams, EDI, and business logic.
Both are necessary. They are provided by different specialists and should be scoped and contracted separately.