ERP Integration FAQ & Troubleshooting

Purpose: Comprehensive FAQ covering common ERP connector and MES product questions.

Version: 1.0
Last Updated: January 2026
Review Cycle: Monthly

Setup & Configuration

Operator Mapping

Q: How do I map an operator in MachineMetrics?

Operator mapping connects your ERP employee records to MachineMetrics user accounts, enabling labor ticket synchronization.

Prerequisites:

IT Admin access to MachineMetrics
Operator's ERP employee ID
Operator's badge ID (if using badge scanning)

Steps:

Navigate to Settings → Operators
Click Add Operator or find existing operator
Enter the operator's ERP Employee ID (must match exactly)
Enter the operator's Badge ID if using badge scanning
Assign to appropriate Machine Groups if using resource restrictions
Save changes

Verification:

Create a test labor ticket for the mapped operator
Verify no "operator id not mapped" errors appear in ERP Error Log

Q: What happens when an operator isn't mapped?

When an operator referenced in a labor ticket hasn't been mapped in MachineMetrics:

Symptoms:

ERP Error Log shows "operator id not mapped" errors
Labor tickets from unmapped operators fail to sync
Operator activity not tracked in MachineMetrics

Resolution:

Add the operator mapping in Settings → Operators
Ensure the ERP Employee ID matches exactly (case-sensitive)
Re-sync or wait for next sync cycle

Note: Historical errors may not auto-resolve after mapping is added. The fix prevents future errors but doesn't clear past entries from the error log.

Q: Can resources be mapped to multiple machines?

Yes, with considerations:

One ERP resource can map to multiple MachineMetrics machines
Labor ticket attribution follows the mapping configuration
Multi-machine setups need clear part count attribution rules

Use cases:

Work cells with multiple machines
Operators who move between machines
Shared resources across a department

Configuration: Set up machine group mappings in ERP Data Studio to define which ERP resources correspond to which MachineMetrics machines.

ERP Connection Setup

Q: How do I connect my ERP to MachineMetrics?

ERP connection setup varies by system but follows a general process:

Prerequisites:

ERP admin credentials or IT support
Network access between Edge device and ERP server
MachineMetrics Edge device installed

General Steps:

Contact your Solution Delivery Manager (SDM) or support@machinemetrics.com
Work with your ERP/IT administrator to configure secure access (API keys, ODBC, or file drop)
Define mappings for jobs, parts, routings, and machines
Validate sync in a staging environment
Go live and monitor using built-in diagnostics

Verification: Work orders appear in MachineMetrics after successful sync; no connection errors in logs.

Q: What data syncs between the ERP and MachineMetrics?

Inbound Data (ERP → MachineMetrics):

Work orders and operations
Part numbers and routings
Scheduled quantities and due dates
Production standards (cycle times, setup times)

Outbound Data (MachineMetrics → ERP):

Completed quantities and labor tickets
Operator time and scrap events (for supported ERPs)

Sync frequency: Typically every 5-15 minutes, configurable during implementation.

Job Tracking Mode Selection

Q: What is the difference between ShopPulse-Driven and ERP-Driven mode?

MachineMetrics supports two job tracking modes:

Aspect	ShopPulse-Driven	ERP-Driven
Primary Interface	MachineMetrics ShopPulse	ERP barcode terminals
Labor Entry	Operators clock in/out via ShopPulse	Operators use existing ERP process
Data Flow	MM writes labor tickets to ERP	MM reads labor tickets from ERP
Best For	New implementations, paperless shops	Existing ERP workflows, gradual adoption

How to choose:

ShopPulse-Driven: When you want MachineMetrics to be the operator's primary interface
ERP-Driven: When operators must continue using existing ERP terminals

Q: How do I switch between ShopPulse-Driven and ERP-Driven mode?

Mode switching requires configuration changes and should be coordinated with MachineMetrics support.

Prerequisites:

Understanding of current workflows
Stakeholder alignment on new process
Training plan for operators

Process:

Contact your Solution Delivery Manager (SDM)
Discuss business requirements and timeline
MachineMetrics configures the mode change
Test in staging environment
Train operators on new workflow
Go live with monitoring

Note: Mode changes affect how labor tickets are created and synced. Plan for a transition period.

Environment Configuration

Q: What environment variables are required for ERP connectors?

Environment variables vary by ERP system. Common variables include:

General (All Connectors):

Database connection strings
API credentials or ODBC settings
Sync interval configuration
Read/write mode settings

Example (Infor Visual):

VISUAL_DATABASE=<database_name>
VISUAL_IP=<server_ip>
VISUAL_USERNAME=<username>
VISUAL_PASSWORD=<password>
VISUAL_SITE=<site_id>
READ_ONLY=<true/false>

Verification: Refer to your ERP-specific connection guide for complete variable lists.

Q: How do I configure the OLDEST_CLOSE_DATE setting?

OLDEST_CLOSE_DATE defines the earliest date MachineMetrics looks back in ERP history to find Work Orders and Labor Tickets.

Format: yyyy-mm-dd (e.g., 2024-01-01)

Best practices:

Set to a recent date for new implementations (past 30-90 days)
Extend further back if historical data is needed
Avoid setting too far back (increases sync time and database load)

Impact: Work orders closed before this date will not sync to MachineMetrics.

Troubleshooting

Labor Ticket Sync Issues

Q: Why aren't my labor tickets syncing to MachineMetrics?

Symptoms:

Labor tickets created in ERP not appearing in MachineMetrics
Operator activity not being tracked
Reports showing missing labor data

Diagnostic Steps:

Check ERP Error Log
- Location: https://erp-error-log.svc.machinemetrics.com/
- Look for specific error messages
Common Error Messages and Fixes:

Error	Cause	Fix
"operator id not mapped"	Operator not configured	Add operator mapping in Settings
"overlapping tickets"	Multiple open tickets for same resource	Review and close duplicate tickets
Connection errors	Network or credential issues	Verify connectivity and credentials

Verify Sync Status
- Check connector health in admin interface
- Verify last successful sync timestamp

Verification: After fixes, new labor tickets should sync within 5-15 minutes.

Escalation Trigger: If errors persist after mapping corrections or connection verification, contact MachineMetrics support with error log exports.

Q: Why do I see "operator id not mapped" errors?

Symptoms:

ERP Error Log shows repeated "operator id not mapped" messages
Specific operators' labor tickets not syncing

Root Cause: The operator's ERP Employee ID doesn't have a corresponding mapping in MachineMetrics.

Resolution Steps:

Identify the Unmapped Operator
- Check error log for the specific operator ID
- Verify the ID format (may include leading zeros)
Add the Mapping
- Navigate to Settings → Operators
- Add new operator with exact ERP Employee ID
- Save and verify
Test the Fix
- Create a new labor ticket for that operator
- Verify no new errors appear

Prevention: Establish a process to map new operators when they're added to your ERP.

Q: What causes "overlapping labor tickets" errors?

Symptoms:

Error log shows overlapping ticket warnings
Part count attribution issues
Dashboard showing unexpected states

Root Cause: Multiple labor tickets are open simultaneously for the same resource. Common scenarios:

Multiple operators on one operation — Operations requiring 2+ people
Process techs logged in — Support staff alongside operators
Shift handoff overlap — Brief overlap during shift changes
Forgotten clock-out — Previous operator didn't clock out

Resolution Options:

Scenario	Recommended Action
Multi-operator operation	Accept overlap; consider process change
Process tech overlap	Don't map process techs if not running jobs solo
Shift handoff (5-10 min)	Normal; no action needed
Forgotten clock-out	Close the orphaned ticket in ERP

Work Order Issues

Q: Why don't I see my work order in MachineMetrics?

Symptoms:

Work order exists in ERP but not visible in MachineMetrics
Operators can't select the job from their dashboard

Diagnostic Steps:

Verify Work Order Status in ERP
- Is the work order "Released"?
- Draft, Planned, Closed, or Cancelled orders won't sync
Check Operations Have Mapped Resources
- Each operation must be assigned to a resource
- That resource must be mapped to a MachineMetrics machine
Review Connector Logs
- Check ERP Error Log for sync errors
- Look for work order-specific issues
Verify Date Range
- Some connectors exclude work orders outside a date window
- Check OLDEST_CLOSE_DATE configuration

Verification: Work orders appear in MachineMetrics after meeting all sync criteria.

Escalation Trigger: If work orders meet all criteria and no errors appear, escalate with specific work order numbers and ERP screenshots.

Q: Why is a completed job still showing on the operator dashboard?

Symptoms:

Job marked complete in ERP still appears in MachineMetrics
Operator sees old jobs in their selection list

Root Cause: The operation's "Closed Date" hasn't been set, or sync hasn't completed.

Resolution Steps:

Verify ERP Status
- Confirm operation is truly closed in ERP
- Check for any pending transactions
Check ERP Data Studio
- Navigate to Production Order Operations
- Verify "Closed Date" is populated
Force Closure (IT Admin)
- If stuck, edit the operation in ERP Data Studio
- Set the Closed Date manually
- Save changes
Wait for Sync
- Allow 5-15 minutes for sync cycle
- Refresh operator dashboard

Dashboard Display Issues

Q: Why does the dashboard show "Setup" (yellow) instead of "Active" (green)?

Symptoms:

Dashboard shows yellow "Setup" state when production is running
Multiple operators logged in but wrong activity type displayed

Root Cause: In ERP-Driven mode, when multiple labor tickets are open simultaneously, the system prioritizes ticket types. Setup tickets may override production tickets.

Workaround Options:

Don't Map Secondary Personnel
- If process techs log in alongside operators, consider not mapping them
Coordinate Ticket Timing
- Have setup personnel clock out before production personnel clock in
Accept Current Behavior
- Dashboard state doesn't affect data accuracy, only visual display

Note: This is a known behavioral quirk being evaluated for improvement.

Operator Correction Scenarios

Q: How do I fix an operator who selected the wrong operation?

Symptoms:

Operator started Op 20 instead of Op 30
Labor ticket attributed to wrong operation

Resolution Steps:

Stop the Incorrect Run
- Have operator stop the current run in MachineMetrics
Fix in ERP (if synced ticket)
- Remove the labor ticket for the incorrect operation in source ERP
Remove Incorrect Production Run (Supervisor or IT Admin)
- Navigate to Production Runs page
- Select the incorrect run → Activities → Delete Production Run
Start Correct Operation
- Have operator select the correct operation from dashboard
Adjust Start Time (if needed)
- Navigate to Production Runs → Select correct run
- Adjust start time to reflect actual start

Who Can Fix:

Action	Operator	Supervisor	IT Admin
Stop incorrect run	✅	✅	✅
Delete production run	❌	✅*	✅
Fix ERP labor ticket	❌	❌	✅

*With permissions enabled

Q: How do I handle an operator who was left clocked in overnight?

Symptoms:

Operator appears to have worked unrealistic hours
Production run showing excessive duration

Resolution Steps:

If NO Parts Were Made Overnight:

Identify the forgotten ticket (still open from previous shift)
Correct the clock-out time:
- Synced tickets: Fix in source ERP system
- Non-synced tickets: IT Admin edits in ERP Data Studio
Adjust production/operator runs in MachineMetrics

If Parts WERE Made Overnight (Unattended Operation):

Determine correct attribution (how to split between shifts)
Manually reconfigure labor tickets
Adjust production runs to reflect actual periods

Prevention:

Enable job start/end time selection feature
Enable labor ticket reconciliation prompts at sign-out
Implement daily checks for open labor tickets

API and Performance Issues

Q: Why am I getting 500 errors from the ERP API?

Symptoms:

Sync failures with 500 error codes
Intermittent connection issues
Slow dashboard performance

Common Causes:

API capacity issues — Too many connectors pulling data simultaneously
Inefficient data fetching — Queries returning too much data
Database resource constraints — ERP database overloaded

Resolution Options:

Reduce sync frequency — Contact support to adjust intervals
Optimize data filters — Exclude old/closed work orders
Vertical scaling — Work with IT to increase database resources

Escalation Trigger: If 500 errors persist, contact MachineMetrics support with timestamps and affected operations.

Q: What happens when API requests fail after retries?

After 3 retries with exponential backoff, the sync job fails.

Error example:

production-order-operations-individual: API request failed after 3 retries

Investigation Steps:

Check resource constraints (CPU, memory)
Review Datadog logs for corresponding errors
Verify network connectivity during failure window

Error Log Behavior

Q: Why don't errors show as resolved after I fix the underlying issue?

Symptoms:

Fixed an operator mapping but error still shows
Corrections made but error log status unchanged

Explanation:

Currently, fixing some issues (like operator mappings) doesn't automatically mark historical errors as resolved. This is because:

The error log is a historical record
Mapping updates don't trigger reprocessing of old tickets
New tickets will process without errors

How to Verify Your Fix Worked:

Create a new labor ticket for the corrected operator
Verify it syncs without errors
Historical errors remain but no new errors should appear

Product Behavior

Job Tracking Modes

Q: How does ShopPulse-Driven mode work?

In ShopPulse-Driven mode, MachineMetrics is the primary interface for operators:

Workflow:

Operator logs into ShopPulse on machine tablet
Operator selects a job from the available work orders
Operator starts production run
Parts are counted automatically (or manually entered)
Operator submits labor ticket when complete
MachineMetrics writes labor ticket to ERP

Key Characteristics:

Real-time job tracking from operator actions
Automatic labor ticket creation
Bi-directional data sync with ERP
Operators don't need to use ERP terminals

Q: How does ERP-Driven mode work?

In ERP-Driven mode, operators continue using their existing ERP process:

Workflow:

Operator clocks into job via ERP barcode terminal
ERP creates labor ticket
MachineMetrics reads labor ticket from ERP (sync interval)
MachineMetrics tracks machine activity against the job
Operator clocks out via ERP terminal
MachineMetrics updates production run with final data

Key Characteristics:

Minimal change to existing operator workflow
Labor tickets originate in ERP
MachineMetrics provides visibility overlay
Sync delay based on interval (typically 5-15 minutes)

Part Count Behavior

Q: How does MachineMetrics count parts?

MachineMetrics uses multiple methods to track part counts:

Method	How It Works	Best For
Automatic (Machine Signal)	Reads cycle complete signal from machine	CNC machines with program output
Automatic (Cycle Detection)	Infers from machine activity patterns	Machines without direct output
Manual Entry	Operator enters count in ShopPulse	Assembly, inspection, manual processes

Part Count Attribution:

Parts are attributed to the active production run
If multiple operators are logged in, parts attribute to the most recent clock-in
Part counts update in real-time on dashboards

Q: What does the Parts Goal performance wheel show?

The Parts Goal wheel displays progress toward the expected quantity for the current operation:

Visual Indicators:

Green fill: On pace or ahead of expected
Yellow fill: Slightly behind expected
Red fill: Significantly behind expected

Calculation:

Compares actual parts made vs. expected based on elapsed time and cycle time standards
Updates in real-time as parts are completed

Note: Requires valid cycle time standards in ERP for accurate pacing.

Machine State and Downtime

Q: How does MachineMetrics detect downtime?

MachineMetrics automatically categorizes machine states based on signals:

State Detection:

State	Detection Method
Active	Machine executing program, spindle running
Idle	Machine on but no program running
Downtime	No activity for configured threshold
Offline	No communication with machine

Downtime Categories:

Operators can classify downtime reasons
Categories are configurable per organization
Unclassified downtime shows as "Unknown"

Q: What do the machine status colors mean?

Color	Status	Meaning
Green	Active/Production	Machine running production
Yellow	Setup	Machine in setup mode
Orange	Idle	Machine on but not producing
Red	Downtime	Machine stopped, requires attention
Gray	Offline	No communication with machine
Blue	Scheduled Downtime	Planned maintenance or break

Note: Colors may vary slightly based on configuration and customer preferences.

Labor Ticket Behavior

Q: What is a labor ticket?

A labor ticket is a record that captures:

Who: Operator performing the work
What: Work order and operation
When: Start and end times
How Much: Parts completed, scrap quantities

Labor tickets drive:

Job progress tracking
Operator time attribution
Costing and payroll data (when synced to ERP)
OEE calculations

Q: Why is there a 3-day limit on labor tickets?

MachineMetrics enforces a 3-day (72-hour) maximum duration for labor tickets.

Why this limit exists:

Prevents unrealistic labor durations from data entry errors
Catches forgotten clock-outs
Ensures data accuracy for reporting

What happens when exceeded:

Ticket is flagged for review
May require manual correction

Prevention:

Train operators on proper clock-out procedures
Enable reconciliation prompts at shift end

Q: How does MachineMetrics handle overlapping labor tickets?

MachineMetrics only supports tracking one operator per machine at any given time.

Overlap Prioritization:

The labor ticket with the more recent clock-in takes priority
Older ticket's overlap period is effectively ignored for tracking

Common Scenarios:

Scenario	Behavior
Shift handoff (5-10 min overlap)	Normal; newer operator takes over
Multiple operators on one machine	Only most recent tracked
Forgotten clock-out + new clock-in	New operator takes over

Work Order Behavior

Q: How does MachineMetrics handle work order quantities?

MachineMetrics syncs ordered quantity from ERP and tracks production against it.

Standard Behavior:

Progress shows "Parts Made / Parts Required" (e.g., "101 / 100")
OEE calculations use actual vs. expected counts
Completion percentage updates in real-time

Known Limitation — Fixed Hours Jobs:

MachineMetrics doesn't currently support hour-based job tracking. Jobs configured as "fixed hours" will display incorrectly:

Job Setup	Display	Problem
"4 fixed hours"	"Need to run 4 pieces"	Incorrect interpretation

Workarounds:

Report as jobs with no standards
Exclude from OEE reporting

Q: What happens when a production order is completed?

When an operation is marked complete:

All open production runs are automatically ended
- Exception: Runs with open labor tickets remain active until ticket closes
Operation's "Closed Date" is set
Job removed from operator dashboard

Tracking Which Ticket Closed a Job:

Audit log contains closeWorkOrderOperation with timestamp
ERP Data Studio shows which ticket caused the close

Setup Time Tracking

Q: How does MachineMetrics track and display setup time?

MachineMetrics tracks setup time against configured expectations.

Setup Status Indicators:

Status	Display	Meaning
Just Started	"44m 59s Remaining"	Setup began, showing countdown
In Progress	"30m 12s Remaining"	Countdown continues
Overtime	"5m 34s Overtime" (red)	Exceeded expected time
No Standard	"In Setup" + elapsed	No expectation configured

Expected Setup Time:

Synced from ERP routing standards
Defines total time expected for setup
Used for schedule calculations

Data Sync Behavior

Q: Can MachineMetrics write data back to my ERP?

Yes, for supported connectors with bi-directional sync enabled.

What can be written back:

Labor tickets (in ShopPulse-Driven mode)
Completed quantities
Work order status updates

Requirements:

READ_ONLY=false in configuration
ERP user has write permissions
ShopPulse-Driven mode active

Q: What happens when production standards change in the ERP?

When standards (cycle times, setup times) are updated in ERP:

Changes sync on next cycle (5-15 minutes)
New standards apply to future calculations
Historical data retains original standards
Schedule Intelligence recalculates completion estimates

Note: Standard changes don't retroactively affect past production data.

ERP-Specific Guidance

Supported ERP Systems Overview

Q: Which ERP systems does MachineMetrics support?

MachineMetrics supports the following ERP systems with pre-built connectors:

ERP System	Integration Type	Supported Modes	Unique Features
Infor Visual	REST API	ShopPulse-Driven, ERP-Driven	Automatic indirect labor ticket creation, labor proration
Epicor Kinetic	REST API	ShopPulse-Driven, ERP-Driven	Dual integration option (API or CSV)
Epicor 10.x	ODBC or CSV	ERP-Driven	Legacy connector for older versions
JobBOSS²	REST API	ShopPulse-Driven	Cloud and on-prem support
JobBOSS Classic	ODBC	ShopPulse-Driven, ERP-Driven	Legacy connector
Infor XA	ODBC	ShopPulse-Driven	-
Infor Syteline	ODBC	ShopPulse-Driven	-
ECI ProfitKey	ODBC	ShopPulse-Driven	-
Sage X3	REST API	ShopPulse-Driven, ERP-Driven	-

All connectors sync: Work orders, operations, routings, part details, and labor tickets.

Additional ERPs targeted for 2026: Dynamics 365, PLEX, ProShop, GlobalShop.

Note: Additional ERP systems may be supported via custom solutions or middleware. Contact support@machinemetrics.com for assistance.

Q: What are the minimum supported versions for each ERP?

ERP System	Minimum Supported Version	Notes
Infor Visual	7.1.2+	Recommended 9.0+; versions 6.x.x may work but are not officially supported
Epicor Kinetic	10.2.600+	Verified and tested
JobBOSS²	v1+ (all versions)	On-prem has an API limitation requiring SQL route for some operations
Infor Syteline	2023.3.1.7+	-
ECI ProfitKey	8.1+	-

Why version matters: Older ERP versions may lack required API endpoints or have different database schemas that affect data synchronization reliability.

Infor Visual Specific

Q: What makes the Infor Visual connector different from other ERP connectors?

Infor Visual has two unique capabilities not available in other connectors:

Automatic Indirect Labor Ticket Creation: The Visual connector can automatically create indirect labor tickets when operators clock in without selecting a job, capturing non-productive time like breaks, meetings, or maintenance.
Labor Proration: When operators run multiple machines simultaneously, Visual can automatically split labor hours across operations based on configurable proration settings.

Configuration Variables Specific to Visual:

Variable	Purpose	Options
PRORATION_TYPE	Controls how labor is split for multi-machine operators	HOURS, COST, or NONE
READ_ONLY	Controls write-back capability	true (read-only) or false (bi-directional)
VISUAL_ENTITY	Accounting entity ID	From dbo.ACCOUNTING_ENTITY.ID table

Q: How do I configure labor proration for Infor Visual?

Labor proration determines how operator time is distributed when running multiple jobs simultaneously.

To configure proration in Infor Visual:

Log in to Infor VISUAL as SYSADM
Navigate to Admin tab → Preferences Maintenance
Go to System → System Management → User Preferences
Select the MachineMetrics integration user
Find the Barcode Labor Entry section
Configure the Multiple Jobs column:
- ProrateCost — Distribute time based on operation cost
- ProrateHours — Distribute time based on hours worked
Save changes
In MachineMetrics environment variables, set:
```
PRORATION_TYPE=HOURS    # or COST or NONE
```

When to use each option:

Proration Type	Best For
HOURS	Equal time distribution across concurrent operations
COST	When operation cost should weight time allocation
NONE	When operators should not run multiple machines simultaneously

Q: Why are labor tickets showing as "FAILED" for Infor Visual even though they appear in the ERP?

This is a known display issue specific to the Visual connector and typically does not indicate actual sync failure.

Common causes:

Checkpointing issues — The connector retries already-succeeded tickets
Failure queue population — The Visual integration may populate the failed queue even for successful syncs
Timing mismatches — Status displayed before ERP confirmation received

How to verify actual status:

Check the actual Visual ERP system to confirm tickets synced correctly
Review ERP Data Studio for the operation's labor ticket history
The displayed "FAILED" status may not reflect actual sync status

Resolution: This is a known issue being addressed. Check the actual ERP system rather than relying solely on the MachineMetrics status display.

Epicor Kinetic Specific

Q: What are my integration options for Epicor Kinetic?

Epicor Kinetic supports one primary integration method:

Method	Best For	Sync Direction
REST API	Real-time bi-directional sync, full feature set	Bi-directional

REST API is recommended because it enables:

Real-time work order synchronization
Automatic labor ticket write-back
Live schedule updates
Lower administrative overhead

Some optional functionality requires an ODBC connection, but most Job Tracking MES functionality works with the default REST API connection.

Q: What causes overlapping labor ticket errors in Epicor ERP-Driven mode?

Overlapping labor tickets occur when multiple labor tickets are open simultaneously for the same resource in Epicor.

Common causes:

Multiple operators needed — Operations requiring 2+ people
Process techs logged in — Support staff logged alongside operators
Shift handoff overlap — Typical 5-10 minute overlap during shift changes

Impact of overlaps:

Part count attribution may be split or unclear
Dashboard may show unexpected states (e.g., "Setup" instead of "Active")
Operator performance metrics may be affected

Recommendations:

Avoid mapping process techs if they don't typically run jobs solo
Train operators on proper handoff procedures (clock out before new shift clocks in)
Accept brief overlaps during shift changes as normal (5-10 minutes)

JobBOSS Specific

Q: What is the difference between JobBOSS² and JobBOSS Classic connectors?

Feature	JobBOSS²	JobBOSS Classic
Integration Type	REST API	ODBC
Supported Modes	ShopPulse-Driven	ShopPulse-Driven, ERP-Driven
Cloud Support	Yes	No
On-Prem Support	Yes (with limitation)	Yes
Setup Complexity	Lower (API-based)	Higher (database connection)

Known limitation for JobBOSS² On-Prem: There is an API bug in on-prem versions that requires using a SQL route for certain operations. Cloud versions are not affected.

Q: Can I use ERP-Driven mode with JobBOSS²?

No. JobBOSS² currently supports ShopPulse-Driven mode only.

Why: The JobBOSS² REST API does not provide the real-time labor ticket webhook events required for ERP-Driven mode.

Alternatives:

Use ShopPulse-Driven mode (recommended) — operators start/stop jobs in MachineMetrics
Use JobBOSS Classic connector with ODBC if ERP-Driven mode is required

Cross-ERP Considerations

Q: Which ERPs support ERP-Driven vs. ShopPulse-Driven mode?

ERP System	ShopPulse-Driven	ERP-Driven
Infor Visual	✅	✅
Epicor Kinetic	✅	✅
Epicor 10.x	❌	✅
JobBOSS²	✅	❌
JobBOSS Classic	✅	✅
Infor XA	✅	❌
Infor Syteline	✅	❌
ECI ProfitKey	✅	❌
Sage X3	✅	✅

How to choose:

ShopPulse-Driven — Operators use MachineMetrics as primary interface; MachineMetrics writes labor tickets to ERP
ERP-Driven — Operators continue using ERP barcode scanners; MachineMetrics reads labor tickets from ERP

Q: What is the typical ERP sync interval and can it be adjusted?

Default sync interval: Every 5-15 minutes, depending on connector configuration.

What syncs inbound (ERP → MachineMetrics):

Work orders and operations
Part numbers and routings
Production standards and expected times
Schedule dates and priorities

What syncs outbound (MachineMetrics → ERP):

Labor tickets (in ShopPulse-Driven mode)
Completed quantities
Work order status updates

Adjusting sync interval:

Contact MachineMetrics support to modify sync frequency
More frequent syncs increase database load
Consider business need vs. resource impact

Advanced Features & Tools

ERP Data Studio

Q: What is ERP Data Studio and what can I do with it?

ERP Data Studio is a configuration and diagnostic interface in MachineMetrics used to view, validate, and manage how ERP data is imported and mapped into the platform.

Key capabilities:

View	What You Can See
Work Orders	Job IDs, scheduled quantities, part numbers, due dates, job statuses
Operations	Individual routing steps with setup/run times, assigned machines, operation numbers
Parts	All parts in the ERP sync including name, number, description, revision
Machines	ERP-defined resources or work centers mapped to MachineMetrics machine groups
Labor Tickets	Labor records including who worked on what, for how long, and when

Common use cases:

Verify jobs are flowing correctly from ERP
Troubleshoot why a job isn't appearing on operator dashboards
Validate routing and machine group assignments
Audit labor ticket data for accuracy
Diagnose Schedule Intelligence alignment issues

Q: Who can access and edit data in ERP Data Studio?

Access is role-restricted:

Role	Access Level
IT Administrator	Full edit access to ERP Data Studio
Operators	No access — work only in ShopPulse
Supervisors	No access to edit — view dashboards and reports only
Managers	No access to edit — view dashboards and reports only
MachineMetrics Staff	Full access (for support purposes)

Critical distinction for editing:

Data Type	Who Can Edit	Where to Edit
Synced labor tickets	ERP System Administrator	Source ERP system only
Non-synced labor tickets	IT Administrator	ERP Data Studio

Why this matters: Changes to synced labor tickets made in ERP Data Studio will not persist — the next ERP sync will overwrite them. Always edit synced data in the source ERP system.

Q: Can I make changes directly in ERP Data Studio?

It depends on the data type:

You CAN edit (IT Administrators only):

Non-synced labor tickets (manual entries or tickets created outside ERP)
Production order operations (clearing closed dates, updating status)
Resource mappings
Machine configurations

You CANNOT edit (read-only):

Synced labor tickets — must be edited in source ERP
Work order data that originated from ERP
Part information synced from ERP

Why some data is read-only: ERP remains the system of record for synced data. Any changes made directly in MachineMetrics would be overwritten on the next sync cycle. This ensures data integrity between systems.

Q: How do I use ERP Data Studio to troubleshoot a missing job?

When a work order operation isn't visible on the operator dashboard, use ERP Data Studio to diagnose:

Step 1: Check if the work order exists

Open ERP Data Studio from the MachineMetrics admin interface
Navigate to Work Orders view
Search for the work order number
Verify the job is present and has correct status

Step 2: Check operation status

Navigate to Operations (or Tables → Production Order Operations)
Find the specific operation (match work order + sequence number)
Check for these blocking conditions:
- Closed Date populated — Operation appears complete
- Status = COMPLETED — Operation marked as finished
- No machine group assigned — Operation not linked to a resource

Step 3: Resolution (IT Administrator only)

If Closed Date is incorrectly populated:

Click Edit on the operation
Clear the "Closed Date" field
Save changes

If status is incorrect:

Re-open the operation in the source ERP
Wait for next sync cycle (5-15 minutes)

If machine group is missing:

Update routing in source ERP to assign correct work center
Verify machine group mapping in MachineMetrics

Q: Where can I find the ERP Connector Logs?

ERP Connector Logs location:

Environment	URL
Commercial	https://erp-error-log.svc.machinemetrics.com/
GovCloud	https://app.machinemetrics-us-gov.com/app/apps/erp-error-log

Alternative access: The logs are also accessible from the My Apps section if you have Work Order Operations or ERP Driven enabled and are an IT Admin.

What you can find in the logs:

Sync success/failure status
Error messages with timestamps
Specific record failures (operator mapping issues, overlapping tickets, etc.)
API request/response details for troubleshooting

Schedule Intelligence

Q: What is Schedule Intelligence and how does it work?

Schedule Intelligence is MachineMetrics' modern approach to production scheduling — one that continuously adapts to real-time shop floor conditions.

How it differs from traditional scheduling:

Traditional ERP Scheduling	Schedule Intelligence
Static plan created in advance	Continuously updated with live data
Outdated as soon as production starts	Reflects actual machine performance
Planners manually adjust when issues occur	Automatic re-calculation of completion times
No visibility into real-time progress	Real-time view of job status and risk

Key capabilities:

Live completion estimates — Based on actual cycle times, not just standards
At-risk job identification — Highlights jobs that may miss delivery dates
Capacity utilization visibility — Shows 7-day capacity outlook
Drag-and-drop scheduling — Planners can manually adjust priorities
Operator visibility — Schedule changes appear instantly in ShopPulse

Q: What are the requirements to use Schedule Intelligence?

Requirement	Details
Module	Schedule Intelligence (Add-On SKU)
Data Requirements	ERP integration with work orders, routings, and part info
Machine Requirements	Real-time connection for status, part count, and program tracking
Recommended Access	Planner, Supervisor, or Manager roles

Why ERP integration is required: Schedule Intelligence needs work order data, due dates, and routing information to calculate completion estimates and identify at-risk jobs.

Scheduled Reports & Dashboards

Q: What are Scheduled Reports and how do I set them up?

Scheduled Reports automates the delivery of MachineMetrics reports and dashboards to stakeholders via email.

Key features:

Feature	Description
Flexible frequency	Daily, weekly, or monthly delivery
Specific timing	Schedule for specific days/dates and times
Multiple recipients	Send to individuals or groups
PDF attachment	Include report data as attachment for offline viewing
Custom messaging	Add personalized context to accompany the report
Expiration dates	Set end dates for temporary reporting needs

Setup process:

Navigate to any report or dashboard
Click "Send"
Choose between "Send now" or "Schedule"
For scheduled reports:
- Name the schedule for easy management
- Select recipients from user list
- Choose frequency (daily, weekly, monthly)
- Set specific days or dates as needed
- Configure delivery time
- Optional: Set expiration date
- Customize email subject and message
- Optional: Include report as PDF attachment
Save to activate the schedule

Data Filtering & Best Practices

Q: What are best practices for ERP data in MachineMetrics?

Data quality best practices:

Parts and routings:

Ensure parts and routings are well-defined and structured in ERP
Use consistent operation naming for clean reporting
Keep revisions current and accurate

Sync configuration:

Enable two-way sync where supported to capture actual performance
Set sync rules to exclude closed, canceled, or archived jobs
Configure appropriate sync intervals (5-15 minutes typical)

Machine mapping:

Routings should reference actual machine groups used on the shop floor
Verify machine group assignments in ERP Data Studio
Keep inactive resources clean and archived

Labor tracking:

Map all operators who will use MachineMetrics
Review operator mappings when onboarding new employees
Audit labor tickets periodically for accuracy

Role-Based Access & Permissions

Q: What can each role do in MachineMetrics?

Capability	Operator	Supervisor	Manager	IT Admin
Use ShopPulse interface	✅	✅	✅	✅
View dashboards	❌	✅	✅	✅
View reports	❌	✅	✅	✅
Edit ERP Data Studio	❌	❌	❌	✅
Delete production runs	❌	✅*	✅*	✅
Manage users	❌	❌	❌	✅
Configure integrations	❌	❌	❌	✅

*If permissions are enabled for the role.

Q: How do non-admin users request ERP data corrections?

When operators or supervisors need ERP data corrections, they must follow the request process:

Request process:

Document the issue — Capture work order, operator, times, and description of problem
Submit request to IT Administrator — Via established internal process
IT Administrator evaluates — Determines if data is synced or non-synced

Resolution path:

Non-synced data → IT Admin edits in ERP Data Studio
Synced data → IT Admin directs request to ERP System Administrator

Why this matters: Only IT Administrators have edit access to ERP Data Studio, and synced data must be corrected at the source (ERP system) to persist.

API & Integration

Q: Does MachineMetrics have an API for data export?

Yes. MachineMetrics offers extensive API capabilities:

API Type	Use Case
Open APIs	Export machine data, production metrics, and reports
GraphQL API	Query specific data with flexible filtering
ERP Connectors	Pre-built integrations with major ERP systems
Webhooks	Real-time event notifications for custom workflows

Common integration patterns:

Export labor ticket data to payroll systems
Feed production data to BI tools (Power BI, Tableau)
Trigger maintenance work orders in CMMS systems
Stream data to cloud services (AWS, Azure)

Access: API documentation and developer portal available for customers with appropriate subscription level.

Q: Can I integrate MachineMetrics with other systems beyond ERP?

Yes. MachineMetrics is designed to be part of your broader manufacturing technology stack:

Common integrations:

System Type	Integration Capability
CMMS / Maintenance	Trigger work orders from machine alerts
BI Tools	Export data to Power BI, Tableau, etc.
Quality Systems	Connect inspection data to production runs
HR / Payroll	Export labor data for time tracking
Cloud Platforms	AWS, Azure data streaming

Integration approaches:

Pre-built connectors — For ERP and select enterprise systems
Open API — For custom development
Middleware — For complex multi-system workflows
File export — CSV for batch processing

Getting Help

Before Contacting Support

Gather this information:

Hardware/System Details:

ERP system name and version
Module (eRP connector type)
Can you access ERP Error Log?

Problem Details:

What signals/data are affected?
Error messages with timestamps
Expected vs. actual behavior

Configuration:

Current environment variables (sanitized)
Recent configuration changes
Screenshots of error logs or dashboards

Contact Options

MachineMetrics Support:

Email: support@machinemetrics.com
Include all information above
Attach error log exports
Include work order/operator IDs

For ERP System Questions:

Contact your ERP administrator
Verify ERP system configuration
Confirm user permissions

Ready to optimize your ERP integration?

Review your current connector configuration
Map all operators in MachineMetrics
Verify work orders are syncing correctly
Train operators on proper workflows
Monitor ERP Error Log regularly
Contact support for advanced configuration

Questions? Contact support@machinemetrics.com or your Solution Delivery Manager (SDM).

Setup & Configuration​

Operator Mapping​

ERP Connection Setup​

Job Tracking Mode Selection​

Environment Configuration​

Troubleshooting​

Labor Ticket Sync Issues​

Work Order Issues​

Dashboard Display Issues​

Operator Correction Scenarios​

API and Performance Issues​

Error Log Behavior​

Product Behavior​

Job Tracking Modes​

Part Count Behavior​

Machine State and Downtime​

Labor Ticket Behavior​

Work Order Behavior​

Setup Time Tracking​

Data Sync Behavior​

ERP-Specific Guidance​

Supported ERP Systems Overview​

Infor Visual Specific​

Epicor Kinetic Specific​

JobBOSS Specific​

Cross-ERP Considerations​

Advanced Features & Tools​

ERP Data Studio​

Schedule Intelligence​

Scheduled Reports & Dashboards​

Data Filtering & Best Practices​

Role-Based Access & Permissions​

API & Integration​

Getting Help​

Before Contacting Support​

Contact Options​

Setup & Configuration

Operator Mapping

ERP Connection Setup

Job Tracking Mode Selection

Environment Configuration

Troubleshooting

Labor Ticket Sync Issues

Work Order Issues

Dashboard Display Issues

Operator Correction Scenarios

API and Performance Issues

Error Log Behavior

Product Behavior

Job Tracking Modes

Part Count Behavior

Machine State and Downtime

Labor Ticket Behavior

Work Order Behavior

Setup Time Tracking

Data Sync Behavior

ERP-Specific Guidance

Supported ERP Systems Overview

Infor Visual Specific

Epicor Kinetic Specific

JobBOSS Specific

Cross-ERP Considerations

Advanced Features & Tools

ERP Data Studio

Schedule Intelligence

Scheduled Reports & Dashboards

Data Filtering & Best Practices

Role-Based Access & Permissions

API & Integration

Getting Help

Before Contacting Support

Contact Options