Epicor Kinetic Integration Guide
Connect Epicor Kinetic to MachineMetrics for bidirectional work order and labor tracking synchronization.
Overview
The MachineMetrics and Epicor Kinetic integration enables seamless data flow between your ERP system and the shop floor, providing real-time visibility and eliminating manual data entry.
Integration Type
| Attribute | Value |
|---|---|
| Direction | Bidirectional |
| Data Flow (Inbound) | Work orders from Epicor → MachineMetrics |
| Data Flow (Outbound) | Labor tickets from MachineMetrics → Epicor |
| Runs On | MachineMetrics Edge Device (physical or virtual) |
How It Works
1. Management — Work Order Transmission
Active work orders are automatically transmitted from Epicor Kinetic to MachineMetrics. This seamless transfer ensures that the latest work orders are always available for operators in real-time.
2. Tracking — Labor and Progress Reporting
As operators work on the transmitted orders within MachineMetrics, their labor inputs:
- Generate labor tickets
- Update the progress of work orders
- Maintain accurate records in real-time
3. Synchronization — Real-Time Updates
The generated labor tickets and any updates to work orders are synchronized back with Epicor. This ensures that all recorded data reflects the most current state of production activities.
4. Scheduling — Dynamic Visibility
Shop floor managers and production planners gain instant visibility into:
- Status of work in progress
- Whether production is on schedule
- If adjustments are needed
Schedule changes are immediately communicated to operators, enabling them to adjust their workflow accordingly.
Requirements
Prerequisites
| Requirement | Details |
|---|---|
| MachineMetrics Edge | Physical or Virtual Edge Device |
| Network Access | Edge device must have firewall access to Epicor's on-prem or cloud environment/APIs. See Network Requirements Guide for Edge connectivity requirements. |
| Epicor User Account | Dedicated user account with access to necessary tables/columns |
| BAQ Access | Business Activity Query for Part Operations |
| API Key | Generated in Epicor for MachineMetrics |
Step-by-Step Setup Guide
Step 1: Create a MachineMetrics Dedicated User in Epicor
Create a user for the integration with access to the following entities:
Erp.BO.BomSearchSvc/GetDatasetForTreeWithPartValidation
Erp.BO.ResourceGroupSvc/Resources
Erp.BO.CapabilitySvc/Capabilities
Erp.BO.ResourceGroupSvc/ResourceGroups
Erp.BO.JobEntrySvc/JobEntries
Erp.BO.JobEntrySvc/GetDatasetForTree
Erp.BO.EmployeeSvc/Employees
Erp.BO.LaborSvc/LaborDtls
Step 2: Create a BAQ (Business Activity Query)
This BAQ allows MachineMetrics access to your Part Operation table, which may not be available via API in some versions of Kinetic.
Required BAQ Columns:
| Column | Description |
|---|---|
PartOpr_Company | Company identifier |
PartOpr_PartNum | Part number |
PartOpr_RevisionNum | Revision number |
PartOpr_OprSeq | Operation sequence |
PartOpr_OpStdID | Operation standard ID |
PartOpr_OpCode | Operation code |
PartOpr_ProdStandard | Production standard |
PartOpr_Machines | Number of machines |
PartOpr_QtyPer | Quantity per |
PartOpr_OpsPerPart | Operations per part |
PartOpr_StdFormat | Standard format |
PartOpr_StdBasis | Standard basis |
PartOpr_OpDesc | Operation description |
PartOpr_AddlSetupHours | Additional setup hours |
PartOpr_RunQty | Run quantity |
PartOpr_AltMethod | Alternate method |
Example BAQ SQL:
select
[PartOpr].[Company] as [PartOpr_Company],
[PartOpr].[PartNum] as [PartOpr_PartNum],
[PartOpr].[RevisionNum] as [PartOpr_RevisionNum],
[PartOpr].[OprSeq] as [PartOpr_OprSeq],
[PartOpr].[OpStdID] as [PartOpr_OpStdID],
[PartOpr].[OpCode] as [PartOpr_OpCode],
[PartOpr].[ProdStandard] as [PartOpr_ProdStandard],
[PartOpr].[Machines] as [PartOpr_Machines],
[PartOpr].[QtyPer] as [PartOpr_QtyPer],
[PartOpr].[OpsPerPart] as [PartOpr_OpsPerPart],
[PartOpr].[StdFormat] as [PartOpr_StdFormat],
[PartOpr].[StdBasis] as [PartOpr_StdBasis],
[PartOpr].[OpDesc] as [PartOpr_OpDesc],
[PartOpr].[AddlSetupHours] as [PartOpr_AddlSetupHours],
[PartOpr].[RunQty] as [PartOpr_RunQty],
[PartOpr].[AltMethod] as [PartOpr_AltMethod]
from Erp.PartOpr as PartOpr
where [PartOpr].[PartNum] = PartOpr.PartNum
Reference: Follow Epicor's instructional video on deploying BAQ reports: Deploy BAQ Reports as Kinetic Applications
Step 3: Create an API Key in Epicor
- Using the general search, search and select "API Key maintenance"
- Select Create a new Key ID:
- Name:
MachineMetrics - Description:
MachineMetrics integration - Expiration Date: Set to a distant future date (can be changed later)
- Name:
- Save the new key
- Copy and securely store the API key — you'll only see it once
- Open Access Scope settings
- Create a new Access Scope:
- ID:
MachineMetrics - Check the Active box
- ID:
- Under Services, add these services and methods:
Erp.BO.BomSearchSvc/GetDatasetForTreeWithPartValidation
Erp.BO.ResourceGroupSvc/Resources
Erp.BO.CapabilitySvc/Capabilities
Erp.BO.ResourceGroupSvc/ResourceGroups
Erp.BO.JobEntrySvc/JobEntries
Erp.BO.JobEntrySvc/GetDatasetForTree
Erp.BO.EmployeeSvc/Employees
Erp.BO.LaborSvc/LaborDtls - Under BAQs, grant access to the BAQ created in Step 2
- Save the Access Scope
- Apply the scope to the "MachineMetrics" API Key
Step 4: Provide MachineMetrics with the API Token
Share the following information securely with your MachineMetrics implementation team:
- API Key
- Epicor server URL/endpoint
- Company ID
- BAQ name
Security Tip: Use a secure method like Snappass or your company's secure file sharing to transmit credentials.
After Setup
Once the integration is configured:
- Work orders will appear in MachineMetrics automatically
- Operators select jobs on their tablets
- Labor data syncs back to Epicor in real-time
- Production Schedule Intelligence shows accurate job status
Verifying the Integration
- Go to Production → Schedule in MachineMetrics
- Confirm work orders from Epicor are visible
- Have an operator start a job on a tablet
- Verify the labor ticket appears in Epicor
Troubleshooting
| Issue | Possible Cause | Solution |
|---|---|---|
| Work orders not appearing | API key expired or invalid | Regenerate API key in Epicor |
| Missing operations | BAQ not configured correctly | Verify BAQ includes all required columns |
| Labor not syncing back | User permissions insufficient | Check MachineMetrics user has write access |
| Connection errors | Firewall blocking Edge | Ensure Edge can reach Epicor API endpoint |
Related Articles
- ERP Integration Guide — General ERP integration overview
- ERP Data Studio — Mapping work centers
- Production Schedule Intelligence — Using the schedule view
- ShopPulse Interface Guide — How operators interact with jobs
Getting Help
- Setup Assistance: Contact your MachineMetrics Solution Delivery Manager (SDM)
- Technical Issues: Email support@machinemetrics.com
- Epicor Configuration: Consult your Epicor administrator or partner