# Infor M3 BE Upgrade Modification Retrofit Effort Calculator

> Source: https://netray.co/tools/infor-m3-be-upgrade-modification-retrofit-effort-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Size the retrofit of MAK modifications, H5 scripts, MEC maps and custom list APIs plus test cycles for an on-prem M3 BE 13.x upgrade.

## Category

infor-cloudsuite

## Erp

Infor M3

## Audience

- M3 technical consultant
- M3 developer
- IT manager

## Tool

**Kind:** calculator

**Inputs:**

#### MAK modifications, simple

**Key:** ms

**Type:** number

**Default:** 20

**Min:** 0

**Step:** 1

**Unit:** mods

#### MAK modifications, medium

**Key:** mm

**Type:** number

**Default:** 10

**Min:** 0

**Step:** 1

**Unit:** mods

#### MAK modifications, complex

**Key:** mc

**Type:** number

**Default:** 4

**Min:** 0

**Step:** 1

**Unit:** mods

#### Hours per simple mod

**Key:** hs

**Type:** number

**Default:** 8

**Min:** 0

**Step:** 1

**Unit:** hours

#### Hours per medium mod

**Key:** hm

**Type:** number

**Default:** 24

**Min:** 0

**Step:** 1

**Unit:** hours

#### Hours per complex mod

**Key:** hc

**Type:** number

**Default:** 60

**Min:** 0

**Step:** 5

**Unit:** hours

#### H5 scripts

**Key:** h5

**Type:** number

**Default:** 30

**Min:** 0

**Step:** 1

**Unit:** scripts

#### Hours per H5 script

**Key:** h5h

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

**Unit:** hours

#### MEC maps

**Key:** mec

**Type:** number

**Default:** 25

**Min:** 0

**Step:** 1

**Unit:** maps

#### Hours per MEC map

**Key:** mech

**Type:** number

**Default:** 3

**Min:** 0

**Step:** 0.5

**Unit:** hours

#### MDBREADMI / custom list APIs

**Key:** api

**Type:** number

**Default:** 15

**Min:** 0

**Step:** 1

**Unit:** APIs

#### Hours per API

**Key:** apih

**Type:** number

**Default:** 0.5

**Min:** 0

**Step:** 0.5

**Unit:** hours

#### Test cycles

**Key:** cycles

**Type:** number

**Default:** 3

**Min:** 1

**Step:** 1

**Unit:** cycles

#### Hours per test cycle

**Key:** cyh

**Type:** number

**Default:** 120

**Min:** 0

**Step:** 10

**Unit:** hours

#### Team size

**Key:** team

**Type:** number

**Default:** 4

**Min:** 1

**Step:** 1

**Unit:** people

#### Hours per person per week

**Key:** hpw

**Type:** number

**Default:** 35

**Min:** 1

**Step:** 1

**Unit:** hours

**Outputs:**

#### MAK retrofit hours

**Key:** retro

**Expr:** ms * hs + mm * hm + mc * hc

**Format:** hours

#### Scripts, maps and API hours

**Key:** integ

**Expr:** h5 * h5h + mec * mech + api * apih

**Format:** hours

#### Test hours

**Key:** test

**Expr:** cycles * cyh

**Format:** hours

#### Total effort

**Key:** total

**Expr:** retro + integ + test

**Format:** hours

**Primary:** true

#### Elapsed weeks

**Key:** weeks

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

**Format:** weeks

**Primary:** true

#### Share of effort from MAK mods

**Key:** mak_share

**Expr:** retro / total * 100

**Format:** percent

**Chart:**

#### Total effort (hours) vs complex MAK modifications

**Type:** line

**X:** mc

**From:** 0

**To:** 40

**Steps:** 21

**Series:**

- total

**Disclaimer:** Hours per object are assumptions; replace them with figures from your last fix or upgrade. Data migration, infrastructure and training are not included.

## Content

**Intro:** This calculator estimates the retrofit and test effort for upgrading an on-prem Infor M3 Business Engine 13.x installation to a later 13.x level when you carry Java modifications made with MAK. It separates modification retrofit from scripts, MEC maps, custom APIs and testing, so you can see what drives the plan.

**Sections:**

#### Why MAK modifications dominate

**Body:** Modifications built with MAK (the M3 Adaptation Kit) change the M3 Java programs themselves. When the upgrade delivers new versions of those programs, each modified program has to be compared and merged with the new standard code, rebuilt and tested; Lifecycle Manager tracks the fixes and modifications on the installation. H5 scripts, MEC maps and custom list APIs sit outside the standard programs, so they usually only need checking against changed fields, panels and API transactions. That is why a few complex MAK mods often cost more than dozens of scripts.

**Bullets:**

- Retrofit = simple x h + medium x h + complex x h
- Scripts, maps and APIs = H5 x h + MEC x h + APIs x h
- Total = retrofit + scripts/maps/APIs + test cycles x hours per cycle

#### How to build the inventory

**Body:** List the modified programs from MAK and the modification and fix records in Lifecycle Manager for the installation, and classify each by size of change: a few lines in one program is simple, changes across several programs or panels medium, new logic or database changes complex. Export the H5 scripts deployed in H5 administration, the MEC agreements and maps in use, and custom MDBREADMI list transactions or other custom APIs. Count only objects still used in production; retiring dead mods is the cheapest retrofit.

#### Worked example

**Body:** 20 simple, 10 medium and 4 complex mods at 8, 24 and 60 hours give 640 hours of retrofit. 30 H5 scripts at 2 hours, 25 MEC maps at 3 hours and 15 custom APIs at half an hour add 142.5 hours. Three test cycles of 120 hours add 360. Total about 1,143 hours, about 8.2 weeks for 4 people at 35 hours. MAK mods are 56 percent of the effort; the chart shows each extra complex mod adding 60 hours.

#### Replacing mods instead of retrofitting

**Body:** Before retrofitting, ask whether each modification can become an H5 script, an MEC flow, a custom list API or a configuration change. Those survive upgrades with much less work and match the extensibility approach Infor recommends for M3. Replacing a complex mod costs more once but removes it from every future upgrade.

**Cta:** If you want users to ask M3 about orders, stock and items in plain English on your own servers, without adding new modifications, we can set that up.

**Faq:**

#### What is Infor M3?

**Answer:** Infor M3 is an ERP for manufacturing and distribution, built on the M3 Business Engine (Java) with programs such as MMS001 for items and OIS100 for customer orders. It runs on-prem as M3 13.x or as the Infor-hosted CloudSuite. On-prem installations can carry Java modifications made with MAK.

#### What does an Infor M3 technical consultant do in an upgrade?

**Answer:** They inventory and retrofit MAK modifications, check H5 scripts, MEC maps and custom APIs against the new level, apply fixes with Lifecycle Manager, and support test cycles. The share of their time spent on MAK retrofit is what this calculator helps you estimate.

#### How many test cycles should an M3 upgrade plan include?

**Answer:** Plan at least two full cycles plus a final regression before go-live; three is common when modifications are numerous. Each cycle covers order to cash, procure to pay, manufacturing and finance with the integrations running. Use your previous upgrade's hours per cycle if you have them.

#### Do H5 scripts need rework in an M3 upgrade?

**Answer:** Usually less than MAK mods, but they read panel fields and call APIs, so changed panels, field names or API transactions can break them. Test each script on the target level and fix the ones that fail, which is why a small number of hours per script is included.

## Search terms

infor m3 technical consultant, what is infor m3, infor m3 upgrade effort, m3 mak modifications, m3 be 13 upgrade, m3 h5 script retrofit, m3 mec map upgrade

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