Integration Math

How to Calculate Integration Workload, API Volume, and Sync Savings

Work through the core math behind ERP, MES, PLM, and WMS integrations: call volume, mapping effort, defect rate, and sync savings, each with units and worked examples.

Start with API call volume, because it sizes everything downstream. The formula is calls per day = (transactions per hour times active hours times polling factor) plus retries. If your MES posts 1,200 work-order updates per hour across 16 active hours, that is 19,200 base calls. A polling connector that also checks status every 30 seconds on 40 endpoints adds 40 times 2,880, or 115,200 calls per day. Add a 4 percent retry rate and you reach roughly 139,700 calls daily, or about 51 million per year. The API Call Volume calculator turns this into peak calls per second, which is what your gateway rate limit must survive.

Peak load matters more than the daily average for sizing. Convert with peak calls per second = daily calls divided by (active seconds times evenness factor). Using 139,700 calls over 16 active hours (57,600 seconds) gives an average of 2.4 calls per second, but real traffic clusters. Apply an evenness factor of 0.35 to model shift-change bursts and you get an effective peak near 6.9 calls per second. If a single endpoint answers in 180 milliseconds, one connection thread clears about 5.5 calls per second, so you need at least 2 parallel threads plus headroom, typically sizing for 3 to handle 20 percent growth.

Data mapping effort drives most of the build hours, so calculate it explicitly. Effort in hours = fields mapped times minutes per field, divided by 60, times a transformation multiplier. A PLM-to-ERP interface moving 320 fields at 12 minutes each is 64 base hours. Straight passthrough fields carry a multiplier of 1.0, but 90 of those fields need unit conversion, lookups, or concatenation, so apply 2.5 to that subset. That reworks to (230 times 12 plus 90 times 30) divided by 60, or 91 hours. The Data Mapping Effort calculator and the PLM ERP Integration Workload tool both use this field-weighted method rather than a flat per-interface guess.

Integration defect rate tells you whether the interface is trustworthy in production. The formula is defects per million transactions (DPM) = (failed transactions divided by total transactions) times 1,000,000. If a WMS-to-ERP feed processes 84,000 inventory moves in a week and 37 fail schema validation or post to the wrong account, that is (37 / 84,000) times 1,000,000, or 440 DPM. Track it by failure class: mapping errors, timeout retries exhausted, and business-rule rejects. The Integration Defect Rate calculator separates these so you know whether to fix a transform, a timeout setting, or an upstream data problem.

ERP MES sync savings quantify the payback in labor hours, not dollars here. Savings per year = (manual entries per day times minutes per entry times working days) divided by 60, times automation coverage. If planners rekey 220 production confirmations per day at 3.5 minutes each across 250 working days, that is 220 times 3.5 times 250 divided by 60, or 3,208 hours annually. An interface that automates 92 percent of those confirmations saves about 2,951 hours. The ERP MES Sync Savings calculator applies coverage explicitly, because the last 8 percent of exception cases almost always stays manual and inflated estimates ignore that residual.

Interface monitoring workload is a recurring cost you must compute, not assume. Monitoring hours per month = number of interfaces times checks per day times minutes per check times working days, divided by 60, plus incident hours. Twelve interfaces checked twice daily at 4 minutes each over 21 working days is 12 times 2 times 4 times 21 divided by 60, or about 34 hours. Add incident handling: at 440 DPM across 1.8 million monthly transactions you expect roughly 792 failures, and if 6 percent escalate to manual triage at 25 minutes each, that adds 20 hours. The Interface Monitoring Workload calculator sums both into a staffing figure.

Chain these figures so the numbers reconcile. Call volume feeds gateway sizing, mapping effort feeds the build estimate, defect rate feeds monitoring load, and sync savings feeds the payback case. A quick sanity ratio: healthy integrations run under 1,000 DPM and monitoring under 3 hours per interface per month. If your worked numbers show 5 hours per interface, the defect rate is driving rework, so revisit the mapping effort inputs rather than adding staff. The QMS ERP Integration Cost and WMS ERP Data Sync calculators reuse these same inputs, so define fields, transactions, and active hours once and carry them through every step.

Published 2026-07-01.