# Infor LN PMC Solution Backlog Patch Effort Calculator

> Source: https://netray.co/tools/infor-ln-pmc-solution-backlog-patch-effort-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Size the work of installing a backlog of LN solutions with PMC, including missing prerequisites, collisions with your customizations and regression testing.

## Category

infor-ln

## Erp

Infor LN

## Audience

- ERP administrator
- LN developer
- IT manager

## Tool

**Kind:** calculator

**Inputs:**

#### Solutions to install

**Key:** sol

**Type:** number

**Default:** 120

**Min:** 1

**Step:** 5

**Unit:** solutions

#### Average prerequisite solutions per solution

**Key:** deps

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

**Unit:** solutions

#### Prerequisites not yet installed

**Key:** miss

**Type:** slider

**Default:** 30

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

#### Solutions touching customized objects

**Key:** coll

**Type:** slider

**Default:** 15

**Min:** 0

**Max:** 100

**Step:** 1

**Unit:** %

**Help:** Share of solutions changing objects you also changed in your own VRC.

#### Retrofit hours per collision

**Key:** retro

**Type:** number

**Default:** 6

**Min:** 0

**Step:** 1

**Unit:** hours

#### Install minutes per solution per environment

**Key:** inst

**Type:** number

**Default:** 5

**Min:** 0

**Step:** 1

**Unit:** minutes

#### Environments

**Key:** envs

**Type:** number

**Default:** 3

**Min:** 1

**Step:** 1

**Unit:** environments

**Help:** For example development, test and production.

#### Regression test hours per affected session

**Key:** test_h

**Type:** number

**Default:** 1.5

**Min:** 0

**Step:** 0.5

**Unit:** hours

#### Affected sessions per solution

**Key:** sess

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

**Unit:** sessions

#### Team size

**Key:** team

**Type:** number

**Default:** 3

**Min:** 1

**Step:** 1

**Unit:** people

#### Hours per person per week

**Key:** hpw

**Type:** number

**Default:** 30

**Min:** 1

**Step:** 1

**Unit:** hours

**Outputs:**

#### Solutions including missing prerequisites

**Key:** total_sol

**Expr:** ceil(sol * (1 + deps * miss / 100))

**Format:** integer

#### Collisions with customizations

**Key:** colls

**Expr:** ceil(total_sol * coll / 100)

**Format:** integer

#### Retrofit hours

**Key:** retro_hrs

**Expr:** colls * retro

**Format:** hours

#### Install hours

**Key:** inst_hrs

**Expr:** total_sol * inst * envs / 60

**Format:** hours

#### Regression test hours

**Key:** test_hrs

**Expr:** total_sol * sess * test_h

**Format:** hours

#### Total effort

**Key:** effort

**Expr:** retro_hrs + inst_hrs + test_hrs

**Format:** hours

**Primary:** true

#### Elapsed weeks for the team

**Key:** weeks

**Expr:** effort / (team * hpw)

**Format:** weeks

**Chart:**

#### Total effort (hours) vs solutions in backlog

**Type:** line

**X:** sol

**From:** 10

**To:** 500

**Steps:** 25

**Series:**

- effort

**Disclaimer:** 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.

## Content

**Intro:** 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.

**Sections:**

#### Where the effort goes

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### How do I know the latest version of Infor LN?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

infor ln latest version, infor ln release notes, infor ln pmc, infor ln solutions install, ttpmc2101m000, infor ln patch effort, infor ln vrc customization retrofit

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json