# Infor M3 Fit-Gap Analysis Worksheet > Source: https://netray.co/tools/m3-fit-gap-analysis-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Editable worksheet to classify each requirement as fit, configure, extend or gap, with effort and cost per line and totals by the end. ## Category infor-cloudsuite ## Erp Infor M3 ## Audience - M3 consultant - Project manager - Business analyst ## Tool **Kind:** worksheet **Mode:** editable **Currency:** $ **Columns:** #### Req ID **Key:** req_id **Type:** text #### Requirement **Key:** requirement **Type:** text #### M3 area **Key:** area **Type:** select **Options:** - Customer Order - Purchasing - Inventory - Manufacturing - Finance - Item and Product Structure - Warehouse - Other #### Resolution **Key:** resolution **Type:** select **Options:** - Standard fit - Configure - Extend (H5 or Infor OS) - Integrate (MEC or ION) - Custom development - Process change - Out of scope #### Priority **Key:** priority **Type:** select **Options:** - Must - Should - Could #### Effort (days) **Key:** days **Type:** number #### Day rate **Key:** rate **Type:** number **Format:** currency #### Estimated cost **Key:** cost **Type:** number **Expr:** days * rate **Format:** currency #### Owner **Key:** owner **Type:** text **Rows:** **Req id:** R-001 **Requirement:** Customer specific price lists with quantity breaks **Area:** Customer Order **Resolution:** Configure **Priority:** Must **Days:** 4 **Rate:** 900 **Owner:** Sales lead **Req id:** R-002 **Requirement:** Auto-allocate stock to promised delivery date **Area:** Inventory **Resolution:** Standard fit **Priority:** Must **Days:** 1 **Rate:** 900 **Owner:** Logistics lead **Req id:** R-003 **Requirement:** Label printing with customer barcode format **Area:** Warehouse **Resolution:** Extend (H5 or Infor OS) **Priority:** Should **Days:** 8 **Rate:** 900 **Owner:** Warehouse lead **Req id:** R-004 **Requirement:** EDI 850 orders from top three customers **Area:** Customer Order **Resolution:** Integrate (MEC or ION) **Priority:** Must **Days:** 15 **Rate:** 950 **Owner:** Integration lead **Req id:** R-005 **Requirement:** Approval of purchase orders above a value limit **Area:** Purchasing **Resolution:** Configure **Priority:** Should **Days:** 3 **Rate:** 900 **Owner:** Finance lead **Req id:** R-006 **Requirement:** Legacy shop-floor scrap report **Area:** Manufacturing **Resolution:** Custom development **Priority:** Could **Days:** 6 **Rate:** 850 **Owner:** Production lead **Totals:** #### Total effort (days) **Key:** days **Agg:** sum **Format:** number #### Total estimated cost **Key:** cost **Agg:** sum **Format:** currency #### Requirements logged **Key:** req_id **Agg:** count **Format:** integer **Summary:** #### Average effort per requirement (days) **Key:** avg_days **Expr:** sum_days / count **Format:** decimal #### Average cost per requirement **Key:** avg_cost **Expr:** sum_cost / count **Format:** currency **Notes:** Add one row per requirement. Filter the exported Excel by Resolution to produce the gap list for sign-off. Day rates and efforts shown are illustrative placeholders. ## Content **Intro:** A fit-gap worksheet is where an M3 implementation either stays honest or quietly grows. This one lets you log every requirement, classify how M3 will meet it, and put a day count and cost next to it before the contract is signed. **Sections:** #### How to use the worksheet **Body:** Run the fit-gap in workshops by process area, not by department. For each requirement, record the business statement in plain language, the M3 area it touches, and one resolution. Resolve in this order: standard fit, configure, process change, extend, integrate, custom development. Enter effort in days for the build and test, then the blended day rate. The cost column calculates itself and the totals update as you add rows. Export to Excel to share with the steering group or attach to the statement of work. **Bullets:** - One requirement per row, written as a verb plus an outcome - Always assign a priority so Could items can be dropped under pressure - Name an owner who can say yes or no on the business side - Re-baseline after each workshop and keep version history #### Choosing the right resolution **Body:** Standard fit means M3 does it with the base setup of programs such as customer order, purchase order and item master maintenance. Configure means settings, order types, status levels, number series, approval or document layouts change but no code is written. Extend covers H5 Client scripts, Infor OS or Mashup style front-end changes, and extensions that stay upgrade safe. Integrate means data moves through MEC, ION or MI APIs. Custom development should be the last resort, because it carries upgrade and support cost for the life of the system. **Bullets:** - Prefer process change when the legacy behavior has no business value - Label anything that touches M3 base tables as high risk - Count integration separately from extension so effort is not hidden #### Reading the totals **Body:** The total days and cost give you the delta between the base license scope and the real project. Look at the share of rows marked custom development or integrate: a large share is a signal that the process design needs another pass. Compare the average effort per requirement against your past projects. If one area such as warehouse or manufacturing holds most of the days, plan a dedicated design owner for that area and schedule it first in the project plan. #### Common mistakes **Body:** Teams often log solutions instead of requirements, which forces a gap by default. Others forget test effort, data conversion for new fields, training and documentation. Another frequent mistake is marking items Standard fit without anyone demonstrating them in the configured sandbox. Treat a fit as unproven until a consultant has shown it in the system with the customer data. **Cta:** If your requirement list is long and you want help checking it against how M3 really behaves, Netray partners can review the worksheet and flag items that are likely cheaper than they look. **Faq:** #### What is a fit-gap analysis in an Infor M3 project? **Answer:** It is a structured comparison of business requirements to what M3 does with standard functionality and configuration. Each requirement is classified as a fit, a configuration, an extension, an integration or a true gap, and costed so the project scope and price reflect reality. #### Should I include process changes in the worksheet? **Answer:** Yes. A requirement resolved by changing the business process still needs an owner, training and communication effort. Logging it keeps the work visible and shows leadership how many legacy habits are being retired rather than coded into M3. #### How granular should requirements be? **Answer:** Granular enough that one row can be tested with one scenario. Avoid rows like 'handle sales orders'. Prefer 'apply customer specific price with quantity break on order line'. Smaller rows give better estimates and clearer test cases later. #### Can I import this into my project tool? **Answer:** Export to Excel or CSV and import it into your tracker of choice. The Req ID column is meant to carry through to functional specs and test scripts so you keep traceability from requirement to test result. ## Search terms infor m3 fit gap analysis template, m3 fit gap excel, m3 requirements traceability matrix, infor m3 implementation requirements template, m3 gap analysis worksheet, m3 fit gap workshop --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json