Infor LN PMC Solution Backlog Patch Effort Calculator
This calculator sizes the catch-up work when an Infor LN 10.x system has fallen behind on solutions delivered through PMC (Product Maintenance and Control). It is for backlog patching on the current release, not for a full release upgrade.
Your numbers
Share of solutions changing objects you also changed in your own VRC.
For example development, test and production.
Your results
All rates are assumptions to replace with your own history. Testing scope depends on your risk policy; this model tests each affected session once per solution.
Total effort (hours) vs solutions in backlog
Sweeps Solutions to install from 10 to 500, holding your other inputs fixed.
Get your PMC backlog estimate reviewed
Send your solution list and customized object list and we will review the collision and test estimate.
Optional. The tool and every export work without this. No spam.
Where the effort goes
Installing a solution through Process Solutions (ttpmc2101m000) is quick; the time goes elsewhere. PMC checks prerequisite solutions, and a long backlog almost always pulls in prerequisites you did not plan for. Solutions that change objects you have customized in your own VRC must be retrofitted: the standard change and your change have to be merged and the customization re-tested. Finally the affected sessions need regression tests in each environment before production.
- Total solutions = backlog x (1 + prerequisites per solution x share missing)
- Collisions = total solutions x share touching customized objects
- Effort = collisions x retrofit h + solutions x install min x environments / 60 + solutions x sessions x test h
How to get the inputs from your system
Use the solution list you plan to install and let PMC report prerequisites for a sample of them; the ratio of extra solutions to planned ones is the prerequisite share. For collisions, compare the components changed by each solution with the objects present in your customer VRC; scripts, DAL hooks and forms copied into your VRC are the usual collisions. Use your last patch cycle to set install minutes and test hours.
Worked example
120 planned solutions with 2 prerequisites each, 30 percent missing, gives about 192 solutions. 15 percent collide with customizations, so 29 collisions at 6 hours is 174 hours of retrofit. Installing 192 solutions in 3 environments at 5 minutes is 48 hours. Testing 2 sessions per solution at 1.5 hours is 576 hours. Total about 798 hours, which is about 9 weeks for 3 people at 30 hours a week. Testing dominates, so grouping solutions by business area and testing each area once is the main lever.
Backlog patching or upgrade
If the backlog runs into many hundreds of solutions, compare this result with a move to the latest LN feature pack or release, which replaces the backlog with one larger upgrade project. Use the separate upgrade cost and regression test calculators for that comparison; this tool only covers PMC solution backlog and VRC collisions.
Frequently Asked Questions
How do I know the latest version of Infor LN?
Infor lists current LN releases and feature packs with their release notes on docs.infor.com and in the Infor support portal. For on-prem 10.x systems, the relevant question is usually which solutions and feature packs are released for your exact release and which are already installed in your VRC structure.
Where do I read LN release notes for solutions?
Each solution comes with documentation describing the problem fixed and changed components; Infor also publishes release notes per feature pack. Read the changed component list first, because that is what decides whether a solution collides with your customizations.
Why do PMC solutions collide with customizations?
Customizations are usually stored in your own VRC derived from the standard one. When a solution changes an object you have also copied and changed, your version hides the standard fix until you merge the change into it. Each such object needs a manual retrofit and test.
Can I skip testing for small solutions?
You can reduce it by grouping solutions per business area and testing the area once, but do not skip it for solutions touching customized objects or finance. Lower the test hours input to model grouped testing rather than leaving testing out.
If you want an assistant that reads solution notes and tells you which of your customized LN objects they touch, we can build that on your own servers.
Related Tools
Infor LN Upgrade Cost Estimator
Estimate the services cost and timeline for an Infor LN version upgrade or CloudSuite migration based on your users, sites, customizations, and integrations.
Infor LN & BaanInfor LN Regression Test Effort Calculator
Estimate test hours, defects and calendar weeks for an LN upgrade or change, and see how adding testers shortens the schedule.
Infor LN & BaanInfor LN Customization Complexity Scorer
Score how manageable your Infor LN customization portfolio is - and how much risk it adds to every upgrade, CloudSuite move, and support handover.
Infor LN & BaanInfor LN Bshell Application Server Memory and CPU Sizing Calculator
Estimate peak bshell count, RAM and CPU cores for an LN 10.x application server from your own measured bshell memory and concurrency.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN Company and Enterprise Unit Design Worksheet
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN and Baan Customization Inventory Worksheet
- Baan to Infor LN Data Conversion Mapping Worksheet
Keep exploring
Free tools
- Infor LN PMC Solution and Patch Installation ChecklistA 5-stage checklist for installing Infor LN solutions and patches through PMC on an on-prem system, from reading the release notes to recording what is installed in production.
- Infor LN Regression Test Effort CalculatorEstimate test hours, defects and calendar weeks for an LN upgrade or change, and see how adding testers shortens the schedule.
- Infor LN and Baan Customization Inventory WorksheetEditable worksheet to list every Baan or LN customization with type, owner, effort and a retire, keep or replace decision.