# Redzone and Infor M3: scheduled runs out, production counts back > Source: https://netray.co/stack/redzone-infor-m3-integration > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer Redzone's Infor M3 Integration Pack takes master data, rates and scheduled runs from M3 for shop-floor execution and returns completed runs and production counts so M3 can show labor and runtime variance. It uses Infor ION bulk APIs (EXPORTMI Select) together with Redzone's Public and Enterprise Collaboration APIs, and needs Redzone's Advanced Integrations add-on. ## Erp Infor M3 ## Erp Key infor-m3 ## On Prem true ## Product Redzone ## Vendor Redzone ## Category MES, connected workforce and OEE ## Integration **Method:** Infor ION bulk APIs (EXPORTMI/Select) **Detail:** Redzone reads M3 master data, rates and scheduled runs through ION API calls against the M3 EXPORTMI program with its Select transaction. This is a read pattern that pulls selected tables or views out of M3 on a schedule. **Method:** Redzone Public and Enterprise Collaboration APIs **Detail:** Redzone's own APIs carry the data into its platform and return completed runs and counts. The integration requires the Advanced Integrations add-on, so confirm licensing before scoping. ## Data Flows **From:** Infor M3 **To:** Redzone **Data:** Item, work centre and rate master data **Trigger:** Scheduled ION API pull **From:** Infor M3 **To:** Redzone **Data:** Scheduled production runs **Trigger:** Orders released or rescheduled in M3 **From:** Redzone **To:** Infor M3 **Data:** Completed runs and production counts **Trigger:** Run completed on the floor **From:** Redzone **To:** Infor M3 **Data:** Labor and runtime for variance **Trigger:** Run closed or shift end ## Setup ### Confirm licensing **Detail:** Check that the Advanced Integrations add-on is part of the Redzone contract and that your ION API access is licensed. ### Create the ION API client **Detail:** Register an ION API service account and authorised app with only the permissions needed for the M3 programs involved. ### Define the M3 selections **Detail:** Choose which facilities, work centres, items and order statuses feed Redzone, and how often the pull runs. ### Map work centres to Redzone lines **Detail:** Align M3 work centre and resource codes with Redzone lines and assets so scheduled runs appear in the right place. ### Agree reporting units **Detail:** Settle units of measure, scrap handling and rate bases so counts reported back match what M3 expects. ### Pilot on one line **Detail:** Run scheduled runs through Redzone and back for a single line, compare counts with M3 reporting, then expand. ### Monitor the sync **Detail:** Set alerts for failed pulls or rejected return posts and name an owner. ## Pitfalls - Scheduled runs changed in M3 after release but not refreshed in Redzone until the next pull, so operators run stale schedules. - Work centre or resource codes that do not map one-to-one to Redzone lines. - Unit of measure mismatches between M3 and the floor, producing wrong counts. - Scrap and rework counted differently by the floor and by M3 reporting. - ION API credentials or scopes expiring or changing after a security review. - Assuming the integration does everything MES does: it supplies schedule and execution data, and your M3 reporting setup still determines costing. ## Ai Layer ### Variance explanations **Description:** A private assistant reading Redzone events and M3 runtime and labor can explain why a run missed its rate, citing downtime and changeover records, with the query shown. ### Schedule drift detection **Description:** Flag runs where the M3 schedule and the Redzone schedule disagree, so planners fix the cause rather than discover it on the line. ### Count reconciliation **Description:** Compare production counts reported by the floor with M3 posted quantities and list the runs with differences for review. ### Shift handover questions **Description:** Supervisors can ask in plain language which runs are behind and why, getting an answer limited to their facility and role. ## Alternatives - Infor Factory Track for M3 if you mainly need handheld transactions and scan-based data capture rather than OEE and visual management. - Manual run reporting through M3 shop-floor transactions for small plants where OEE is not a driver. - Another MES with an M3 connector when you need deeper quality or genealogy capture. ## Faq ### Does Redzone write back to M3? **Answer:** Yes, according to Redzone's description it returns completed runs and production counts to M3 for labor and runtime variance. Posting behavior and which M3 transactions are used depend on how the integration is configured with your M3 partner, so confirm it in scoping. ### What is EXPORTMI? **Answer:** EXPORTMI is an M3 API program used to extract data from M3 tables or views, and Redzone uses its Select transaction through ION API for bulk reads. It is a read mechanism, so write-back uses a separate path. ### Can this run with on-premises M3? **Answer:** The integration uses ION APIs, which are available to M3 on-premises through ION. Redzone's platform itself is hosted by Redzone, so check network paths and whether shop-floor data may leave your site. ### Do I need the Advanced Integrations add-on? **Answer:** Redzone lists it as a requirement for the M3 integration. Confirm cost and scope with Redzone before building the business case. ## Source https://www.rzsoftware.com/integrations/infor-m3 ## Search terms redzone infor m3 integration, redzone m3 oee, infor m3 mes, m3 exportmi select redzone, redzone ion api, m3 production counts oee --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json