Infor XA Factory Track: What It Does and How to Plan Shop Floor Data Collection
infor xa factory track
Also searched as
- infor factory track xa
- xa shop floor data collection
- mapics factory track
Short answer
Factory Track is the shop floor data collection offering associated with Infor XA. It captures labor, job and material transactions at the work centre, often with bar code terminals, and posts them to XA production control so that job status, costs and inventory stay current without re-keying. Details differ by release, so check your documentation before configuring anything.
Applies to: Infor XA (formerly MAPICS XA) on IBM i with the Production Control and Inventory modules. Capabilities and versions depend on what you are licensed for.
Plan a shop floor data collection setup for XA
- 1Define which transactions you want from the floor: job start and stop, labor time, quantity complete, scrap, material issues, inventory moves.
- 2Confirm the installed Factory Track version, its prerequisites and supported terminal hardware from your release documentation.
- 3Clean the master data first: work centres, operations, employee numbers, job and routing integrity. Data collection exposes every master data error.
- 4Set up terminals and bar codes for employees, jobs and operations, and decide who corrects bad scans.
- 5Test each transaction type against a non-production environment, then check that job status, costs and inventory in XA match the expected values.
- 6Define a daily exception routine: open labor, jobs without scans, quantity mismatches.
- 7Train supervisors first, then operators, and run in parallel with paper for a short period before cutover.
What data collection really changes
Without floor data, costs and job status depend on someone typing at the end of a shift, so WIP value, schedule adherence and labor variances lag by days. With scanning, the system reflects reality within minutes, which is what makes MRP, scheduling and cost analysis trustworthy.
The benefit appears only if the routing steps are meaningful and the operators agree with the operation definitions. A generic 'run' operation yields generic data.
Common failure points
Failures usually come from master data (an operator not set up, an operation not on the routing, a closed job), from terminal connectivity, and from transactions the host rejects. Decide how rejects are surfaced: a queue someone owns, not a log nobody reads.
Also plan the IBM i side: batch jobs that process collected transactions, their schedule and monitoring. A stalled batch job quietly stops cost updates.
Aging platform and alternatives
If your terminals, operating systems or Factory Track version are out of support, you have three options: keep it running with a documented support plan, replace the collection layer with a current MES or data collection tool that writes through supported interfaces, or modernize the ERP. See the related page on the M3 version of Factory Track for a comparable pattern and on XA integration options.
Try it here, free
Infor XA (MAPICS) Migration Readiness Assessment
Ten questions that score how ready you are to move off Infor XA (MAPICS), covering customizations, IBM i dependencies, data quality and ownership.
Common pitfalls
- !Going live without cleaning routings and employee setup.
- !No owner for rejected transactions.
- !Not monitoring the batch jobs that post collected data.
- !Running unsupported terminals or clients with no replacement plan.
How an ERP-grounded AI assistant handles this
A grounded assistant cannot replace scanning, but it can make the exception routine cheap. A private deployment of ERPray or DataRay can answer which jobs have labor open for more than a shift or which operators are missing from routings, based on read-only queries over XA data, and show the query. Write-backs such as correcting a transaction should stay with a human approval step.
Frequently asked questions
What is Factory Track in Infor XA?
It is Infor's shop floor data collection offering associated with XA, used to capture labor, job and material transactions at the floor and post them to XA production control.
Does Factory Track need bar code terminals?
Bar code terminals are the common approach, but the exact hardware and supported devices depend on your version. Check release documentation before buying hardware.
Why are my floor transactions not updating jobs?
Typical causes are rejected transactions from master data errors, a stopped batch job that posts collected data, or connectivity from the terminals. Check the reject queue and the IBM i job status first.
What replaces Factory Track if it is unsupported?
A current MES or data collection tool that posts through supported interfaces, or a broader ERP migration. Decide based on the number of users, the transaction types and your support position.
Related
Infor Factory Track for M3: Shop Floor Data Collection Explained
Infor Factory Track is a shop floor data collection and execution product used with M3 so that operators report production, time and materials at the machine instead of on paper or at an ERP terminal. It reads released manufacturing orders from M3 and writes reported quantities and times back, so M3 costing and planning see actuals.
How-toInfor XA REST API: expose XA through IBM i Integrated Web Services or ION
Infor XA has no single built-in REST API. Practical routes are IBM i Integrated Web Services (IWS), which turns RPG or SQL routines into REST endpoints on the same machine, and Infor ION where your environment supports it. For reads, SQL-backed services are straightforward. For writes, call XA's own programs so business rules run.
How-toInfor XA costing: cost types, roll-up and standard cost setup
Product costing in Infor XA builds an item's cost from its material, labor, and overhead using the bill of material and routing. Standard cost is the frozen planning cost used to value inventory and measure variance, while other cost sets are used for current or simulated views. A cost roll-up calculates costs from the lowest BOM level upward. Exact program names and options vary by release.
How-toHow to Send Production and Labor Reporting from MES to ERP
Treat the ERP work order as the system of record for cost and quantity, and the MES as the system of record for what physically happened. Send one confirmation message per operation (or per shift or lot) containing work order, operation sequence, good quantity, scrap quantity with reason, and labor start/stop per employee and work center, post it through the ERP's supported transaction API, and make the message idempotent so a retry never double-posts.
How-toInfor XA Net.Link: what it is, how it is configured and common issues
Net.Link is the web access layer associated with Infor XA (formerly MAPICS XA) that exposes XA functions through a browser, running on an IBM i web application server. It depends on the IBM i version, the web server profile and Java runtime, so most problems after changes trace to those components. Details vary by XA release, so confirm against your installation guide.
How-toInfor XA User List Report: Users, Status and Access for an Audit
Infor XA runs on IBM i, so a complete user list is built from two layers: the IBM i user profiles (who can sign on, status, last sign-on, group profiles, special authorities) and the XA application security tables (which menus, functions and facilities each user may run). Export the first with DSPUSRPRF or the QSYS2.USER_INFO view, add the second from your XA security setup, and join them by user ID.
AI for ERPAI for Infor XA on IBM i: On-Prem, No Replatforming Required
Add AI to Infor XA on IBM i (AS/400) without a migration project. Read DB2 for i directly, ground answers in live XA data, keep everything on-prem.
Stuck on Infor XA (IBM i)?
Talk to engineers who work inside Infor XA (IBM i) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor XA (MAPICS) Migration Readiness AssessmentTen questions that score how ready you are to move off Infor XA (MAPICS), covering customizations, IBM i dependencies, data quality and ownership.
- MAPICS and Infor XA AI Assistant Sizing and Value CalculatorEstimate GPU count, token volume, index size, hours saved and payback for a private on-prem AI assistant on MAPICS and Infor XA.
- MAPICS and Infor XA Private AI Layer Blueprint GeneratorGenerate a shareable architecture plan for adding a private, on-prem AI assistant to MAPICS and Infor XA, with components, security controls and a three-phase rollout.
ERP fixes and how-tos
- Infor Factory Track for M3: Shop Floor Data Collection ExplainedWhat Infor Factory Track does for M3 manufacturers: shop floor data collection feeding M3 orders, how the integration is structured and how to plan the setup.
- How to add a private AI layer to Infor Factory Track on-premReference architecture to add AI to Infor Factory Track on-prem: read-only data path, retrieval, permissions, local GPUs, write-back control and rollout.
- How to add a private AI layer to Infor XA on-premReference architecture to add AI to Infor XA on-prem: read-only data path, retrieval, permissions, local GPUs, write-back control and rollout.
Runs with your ERP
- Infor Factory Track Shop Floor with SyteLine: paperless labor, job and WIP reportingHow Factory Track Shop Floor kiosks record labor, job operations and WIP in SyteLine, with setup steps, common pitfalls and where a private AI layer helps.
- Infor Warehouse Mobility (Factory Track) and Infor LN: RF scanningHow Infor Warehouse Mobility with Factory Track lets RF scanners post warehouse and shop-floor transactions to Infor LN, with setup, pitfalls and AI.
- Infor Factory Track Time Track with SyteLine: attendance and labor captureHow Infor Factory Track Time Track captures clock-ins, breaks, absences and labor for SyteLine, applies attendance rules and prepares payroll data.
Guides
- Shop Floor Data Collection: Connecting Machines and Operators to Your ERPShop floor data collection guide: connect CNC machines, barcode scanning, and IIoT sensors to ERP. Covers OPC UA, MTConnect, Factory Track, costs, and AI agents.
- Mobile Shop Floor Reporting for SyteLine ProductionImplement mobile shop floor data collection in SyteLine. Configure labor reporting, operation completions, and production data capture on handheld devices.
- MAPICS to SyteLine Migration Planning GuidePlan your MAPICS XA or MAPICS AS/400 migration to Infor SyteLine or CloudSuite Industrial. Data mapping, timeline, and risk mitigation strategies.
Integrations
- How to add AI agents to Infor XA on IBM iHow to add AI agents to Infor XA on IBM i: a tool layer over Db2 for i and RPG programs, approval gates, on-prem models, and realistic expedite and exception flows.
- How to add WhatsApp to Infor XA on IBM iHow to connect WhatsApp Business to Infor XA on IBM i: Db2 for i triggers, data queues, template messages, approvals and replies back into XA safely.