The Hidden Cost of Every PMC Post.
Every PMC cycle, XA calculates run time, setup time, and variances — then purges it all. Advanced Labor History permanently fixes this. No new systems. No workflow changes.
Guide Techologies is an Infor Gold Resell Partner
What Changes Once Labor History is Permanent
The Difference
Without Advanced Labor History
- Labor data gone after every PMC Post
- No historical trend analysis within XA
- Variance analysis requires manual spreadsheets
- Routing errors compound silently over time
- Over-standard employees go undetected for months
With Advanced Labor History
- Every labor transaction kept permanently
- Multi-level drill-down from daily totals to MO detail
- Actual vs. standard variance auto-calculated & color-coded
- No separate batch process or additional systems needed
- Full history from existing MOTRAN records, day one
Built on XA. Not bolted on.
Permanent Labor History
LBACSUM stores one record per employee per day. LBACDTL captures every MO/operation. All transactions retained indefinitely, including your existing MOTRAN data.
Multi-Dimensional Drill-Down
Slice by employee, date, MO, department, work center, or item. Built-in IDF subsets get you there in two clicks from the workbench.
Native IDF — No New Tools
Standard IDF business objects and a pre-built Powerlink or Netlink workbench. Your team works exactly where they already do, no new training curve.
Real-Time. Always Current.
SQL views read from XA’s own MOTRAN and MOROUT tables. No batch jobs, no ETL, no separate capture step, no maintenance overhead.
Four Variance Types Tracked
Run Labor
Actual vs. standard run labor hours per transaction
Run Machine
Actual vs. standard run machine duration
Setup Labor
Actual vs. standard setup labor hours per operation
Setup Machine
Actual vs. standard setup machine time
One data source, four different jobs
Production Supervisors
Daily Exception Review – Did all MOs report labor yesterday? Who’s significantly over standard? Spot missed clock-offs and productivity issues in seconds,before they cascade into cost overruns.
Industrial Engineers
Routing Standard Validation – Are standard run hours accurate? Consistent overruns across multiple employees on the same operation point to a routing error, not a people issue. Fix it once.
Operations Managers
Labor Trend Analysis – Which employees or work centers are driving labor overruns this quarter? Actual data for targeted coaching, capacity planning, and headcount decisions.
Cost Accountants
Job Costing Accuracy – Do reported actuals align with what standard costing expects? Surface systemic over- or under-reporting patterns to strengthen profitability analysis.
Common Questions
Do operators change how they enter labor?
No. Standard PMC ON/OFF labor entry is completely unchanged. Data capture is transparent to the shop floor, no new steps, no new screens.
Can we see historical data that already exists?
Yes. The solution reads from MOTRAN, which retains historical records. Existing labor activity appears immediately, with no go-live cutoff date for prior data.
Do we need any additional systems or software?
No. All data is read in real time from XA’s own tables via SQL views. No separate systems, batch capture, or extra software required.
Does it work with Netlink as well as Powerlink?
Yes. Both interfaces are fully supported. Guide configures both during deployment using the right approach for each environment.
Can data be exported to Excel?
Yes. Standard IDF export capabilities allow any LBACSUM or LBACDTL view to be exported to Excel, CSV, or other formats supported by your IDF version.
What XA version and modules are required?
Infor XA 9.2.1 or later with PMC and OBPM active. Powerlink or Netlink. IBM developer access for Guide during deployment.
More Products for XA
EFIN Essentials
Modernize XA Efin
FormPack
Document Management
Item Availability
Inventory Management
Scan-N-Track
RF Data Capture
System-Link Toolkit
Data Management
ERP 2 EDI
Simplify EDI Transactions