To build the integration project between the Tractian platform and your company’s ERP, it’s essential to understand the available types of integration. These fall into two main categories: time-based (periodic or event-driven) and data flow direction (one-way or two-way).
Time-Based Integration
Event-Driven Integration
This type of integration is triggered whenever a specific event happens on the Tractian platform. Examples of events include:
Creating a new work order
Updating asset data
Deleting a record
When such an event occurs, it acts as a trigger to automatically start the integration with the ERP. This approach is ideal when:
Real-time updates are needed
Immediate synchronization is critical
Delays in data transfer must be avoided
Example: When a new work order is created on Tractian, it’s immediately registered in the ERP.
Scheduled Integration
In this model, integration runs at predefined time intervals, regardless of whether specific events have occurred. It can be set to run:
Every hour
Daily
Weekly
This approach is useful when:
Real-time updates are not required
ERP calls need to be minimized
Data volume is predictable
Important note: Even if no events occur, data will still be synchronized on schedule.
Direction of Data Flow
One-Way Integration
In one-way integration, data flows in a single direction, usually from Tractian to the ERP (or vice versa). It is recommended when:
Data has a clear origin and destination
No immediate response or feedback is needed from the receiving system
Example: Maintenance data generated in Tractian is sent to the ERP without expecting a response.
Two-Way Integration
Two-way integration allows data to flow in both directions, enabling ongoing, synchronized communication between Tractian and the ERP. This model is ideal when:
Both systems must stay updated in real time
Changes in either platform should be reflected in the other
Example: Updating a customer record in the ERP is also updated in Tractian, and vice versa.
Choosing the Right Integration Model
Before starting the integration project, you need to decide:
When should the data be integrated?
In real time (event-driven)
On a set schedule (periodic)
How should the data flow?
In one direction only (one-way)
In both directions (two-way)
This decision will shape an efficient integration architecture tailored to your operation’s needs.