ERP-Driven Job Tracking enables MachineMetrics to visualize job execution and labor performance using labor ticket data collected directly from your ERP system. Unlike ShopPulse-driven workflows, operators do not interact with MachineMetrics during their shift—instead, all job actions are managed entirely within the ERP environment.
This method is ideal for manufacturers that have standardized ERP-based job workflows and prefer to maintain a single source of truth for labor tickets and job execution data.
With ERP-Driven Job Tracking, MachineMetrics:
-
Pulls labor ticket records directly from your ERP via a read-only connector
-
Uses those records to populate job tracking data in reports, dashboards, and analytics
-
Associates labor events with machine activity for performance and utilization insights
Feature Availability
|
Requirement |
Details |
|---|---|
|
Module |
ERP Integration (Required). See list of supported ERPsERP Connectors |
|
Data Sync Direction |
Read-only from ERP to MachineMetrics |
|
Operator Interface |
Operators use ERP terminals, not MachineMetrics |
|
Clock In/Out |
Managed within ERP (MachineMetrics clockIn/ClockOut tracking is not used) |
How It Works
-
The operator goes to an ERP terminal (located in a shared area or at a station).
-
They start the job using the ERP interface—this logs the labor ticket.
-
The operator performs their work at the machine as usual.
-
When finished, the operator returns to the ERP terminal to end the job, log completed parts, and enter scrap (if applicable).
-
MachineMetrics later reads the ERP labor ticket and uses that information to:
-
Match labor time to machine activity
-
Attribute part counts and utilization
-
Display job completion data in dashboards and reports
-
Key Differences vs. ShopPulse-Driven Job Tracking
|
Feature |
ERP-Driven Job Tracking |
ShopPulse-Driven Job Tracking |
|---|---|---|
|
Job Start/Stop Location |
ERP system (e.g., ERP terminal) |
MachineMetrics ShopPulse dashboard |
|
Labor Ticket Source |
ERP system |
MachineMetrics labor tracking |
|
Data Sync Direction |
ERP → MachineMetrics (read-only) |
Bi-directional (read/write with supported ERPs) |
|
Clock In/Clock Out |
Handled in ERP or not tracked |
Tracked in MachineMetrics via ShopPulse |
|
Operator Interface |
ERP Terminal |
ShopPulse (tablet or kiosk at machine) |
|
Part/Scrap Reporting |
Entered in ERP |
Entered in ShopPulse |
Tips & Best Practices
-
Ensure ERP job numbers, operation numbers, and machine associations are clean and consistent—this enables MachineMetrics to align labor tickets with machine activity.
-
Encourage operators to start/stop jobs in real time to maintain accurate labor records.
-
Review ERP-to-MachineMetrics sync cadence (typically every 5–15 minutes) to ensure timely dashboard updates.
-
Use MachineMetrics reports to cross-validate labor activity against machine performance.
FAQs & Troubleshooting
Q: What happens if an operator forgets to end a job in the ERP?
A: MachineMetrics will display the job duration as-is, based on ERP timestamps. It’s important to reinforce complete labor ticket workflows in the ERP.
Q: Can MachineMetrics write labor data back into the ERP?
A: No. In ERP-driven mode, MachineMetrics does not write back any data—only reads from the ERP.
Q: Will operators see jobs in ShopPulse?
A: No. Operators do not use ShopPulse under ERP-Driven Job Tracking. ShopPulse job queues are disabled or hidden in this workflow.
Related Articles
-
[ERP Connectors Overview]
-
[ShopPulse-Driven Job Tracking]
-
[Schedule Intelligence]
-
[Labor Ticket Review in ERP Data Studio]
Comments
0 comments
Please sign in to leave a comment.