Skip to content

Arena – ERP/MES Integration Guide

Abstract

This comprehensive guide assists Arena partners and customers in seamlessly integrating Arena with Enterprise Resource Planning (ERP) and Manufacturing Execution Systems (MES). It outlines essential preparations, required resources, key responsibilities, and common use cases to ensure successful implementation.

Audience

This guide is intended for Arena partners, customers, developers, and solution architects developing ERP/MES integration products.

1. Preparation: Concepts to Master

Before beginning development, your team should review the Arena documentation and recorded training events provided during onboarding. A strong understanding of the following Arena concepts is required:

  • Core Objects: Items, Change Orders, and File Editions.
  • Attributes: Categories, Lifecycles, and Custom Attributes.
  • Revision Management: The distinction between Item Revisions (Released) and Working Revisions (In-Progress).
  • Bill of Materials (BOM): Parent-Child structures and relationships.
  • Licensing: The Arena Machine User License (strictly required for system-to-system integrations).

Critical Technical Requirement: GUIDs

Arena uses Globally Unique Identifiers (GUIDs) to identify all objects (e.g., 2K4N1Y24FWFN6LDUC67B).

Best Practice: Do not rely on Item Numbers or Names for matching, as these can change. Always store the Arena GUID in your external ERP/MES to enable accurate updates and bi-directional syncing.

Usage: Include GUIDs in all PUT/POST requests when establishing relationships.

2. Resources and Responsibilities

Connecting critical enterprise systems (PLM, ERP, MES) requires collaboration across business units.

Business Stakeholders

  • Arena Administrator(s): Manages Arena configuration control and access policies.
  • Change Management Team: Manages engineering change processes, including approval workflows and the "triggers" for releasing data to manufacturing.
  • ERP/MES Administrator(s): Manages configuration control for the destination systems.
  • Manufacturing Product Team: Manages Item Masters and BOMs within the ERP/MES.

Technical Resources

  • For Arena: A developer capable of using the Arena Developer Platform (REST API and Event Engine) to extract and process data streams.
  • For ERP/MES: Developers familiar with the specific ERP/MES endpoints for Item Masters, BOMs, and Sourcing.

3. Common Use Cases

PLM → ERP / MES (Outbound)

  • New Item/BOM Release: Push a Change Order (ECO) containing new Items and BOM relationships to ERP/MES.
  • Revisions & Updates: Pushing subsequent revisions of Items or BOMs (e.g., quantity changes, reference designator updates).
  • BOM Redlines: Removing BOM relationships (redlines) when child assemblies are removed.
  • Bulk Processing: Handling multiple BOMs or Items modified within a single change event.

ERP → Arena (Inbound)

  • Cost & Inventory: Updating non-revision-controlled attributes in Arena (e.g., standard cost, inventory disposition) based on ERP data.

MES → Arena (Quality Loop)

  • Quality Feedback: A quality issue occurring in the MES triggers a workflow that pushes data into Arena Quality World for resolution. The resulting Engineering Change Order then flows back to MES to close the loop.

4. Integration Architecture & Best Practices

Triggers & Frequency

  • The "Released" Standard: The standard trigger is a Change Order entering a "Completed" status. This ensures only approved, effective revisions are sent downstream.
  • Sorting: Since multiple events may occur between API execution intervals, data must be sorted by Event Creation Date/Time to ensure changes are processed in the exact order they occurred.

Data Logic & Transforms

Integrations often require a mapping layer to handle data format differences between systems. This layer should be configurable without code recompilation.

1. Reference Designators (Ref Des)

Ref Des uniquely identify component instances within an assembly (e.g., R1, C4).

  • Range Handling: Arena supports ranges (e.g., R1-R10). Many ERP systems require discrete values. Your integration logic may need to parse ranges into individual instances (R1, R2, R3...) before ingestion.
  • Consistency: Ensure naming conventions are consistent to support accurate updates during design changes.

2. AML / AVL (Sourcing)

Arena manages Approved Manufacturer Lists (AML) and Approved Vendor Lists (AVL) by linking Items to Manufacturer Parts.

  • Relationships: The integration must respect the link between the Arena Item (Internal Part) and the Manufacturer Part.
  • Status Mapping: Manufacturer Parts have statuses (e.g., Approved, Potential, Disapproved). Integrations should map these statuses to the ERP to prevent purchasing of disapproved components.

3. BOM Quantity & UOM

  • Unit of Measure: Arena values (e.g., EACH) often need transformation to match ERP codes (e.g., EA).
  • Precision: Do not assume whole numbers for BOM quantities; support decimal precision as needed.

Bi-Directional Sync Architecture

For two-way synchronization:

  • Change Detection: Use Arena Outbound Events for real-time notifications. Implement timestamp/log detection on the ERP side.
  • Conflict Resolution: Implement a "source of truth" policy (e.g., most recent change wins) to handle simultaneous edits.
  • Queuing: Use a message queue for asynchronous processing to prevent system timeouts.

Error Handling

Arena follows standard HTTP status codes.

  • 4xx: Client-side issues (invalid input).
  • 5xx: Server-side issues.
  • Retry Policy: Arena does not provide a native retry policy. The client must implement retry logic for 5xx errors or network timeouts.
  • Logging: Logs should capture the full request/response details, timestamp, error code, and the specific Object GUID involved.

5. Getting Started Checklist

  1. Provision and set up the Arena Workspace.
  2. Configure Arena Users and assign an API Machine User License.
  3. Request Arena Support to enable the "Outbound Event" setting.
  4. Create the Trigger and Integration definition in Arena.
  5. Import sample data into Arena for testing.
  6. Complete the ERP Extraction Process: Monitor Queue → Export → Process → Handle Errors.

6. FAQ

Q: What is the API rate limit?

A: The default limit is 10,000 calls per 24-hour period. This limit is per customer workspace. Using the Event Engine is recommended as it consumes fewer API calls than polling.

Q: How can I re-process data for a trigger while testing?

A: You can manually regenerate events for testing:

  1. Navigate to User Menu → Workspace Settings → Integrations.
  2. Select the specific Integration.
  3. Go to Triggers → Manage Triggers.
  4. Click Reprocess, configure the start/end dates, and confirm.

Warning: Use cautiously in production as this generates duplicate events which may impact downstream systems.

Q: How do we handle reconciliation with the Event Engine?

A: You can reconcile by the entire event or by individual items within the event. If reconciling item-by-item, the event is considered fully reconciled only when the last item within it is marked complete.

Q: What Access Policy permissions does the Machine User need?

A: Grant "Least Privilege" access. Create a specific User Group (e.g., "ERP Integration Group") restricted to the specific categories (e.g., "Mechanical Items") required for the integration.