Skip to main content

ERP Integration

Connect business orders to terminal execution.

Connect ERP orders, stock, loading transactions, and billing records without forcing operators into double entry.

Talks to

ERPTASStockBilling

Operating chain view

1ERP
2TAS
3Stock
4Billing

Prior implementation: TAS ↔ NAVISION ERP for Puma Energy.

Our founder participated in the implementation of TAS integrations with Puma Energy's Microsoft Dynamics NAV (Navision) ERP, collaborating with the Navision team to integrate TAS with NAVISION ERP across multiple sites — enabling synchronization of customer/product master, orders, loading confirmations, goods movements and reconciliation between the terminal floor and the Puma Navision ERP. Specific scope and locations disclosed under NDA.

What we cover

A focused scope before implementation starts.

01

Order-to-cash data flow design

02

Master data alignment & reconciliation

03

Interface timing, retry & exception handling

04

Three-way reconciliation (ERP ↔ TAS ↔ physical)

Architecture

Engineered architecture, end-to-end.

1

Layer 4

ERP

Business planning, orders, inventory accounting, billing, and master data.

2

Layer 3

TAS

Loading authorization, bay workflow, driver access, and movement records.

3

Layer 2

SCADA / HMI

Operator visibility, alarm response, process status, and event history.

4

Layer 1

PLC / VFD / Safety PLC

Control execution, pump behavior, valve states, permissives, and trips.

5

Layer 0

Field equipment

The measured reality of product movement, custody transfer, and equipment state.

ERP-to-TAS integration architecture showing bidirectional data flow between SAP, Navision, Dynamics, JD Edwards, Oracle and terminal systems via an integration middleware layer.
ERP-to-TAS integration architecture — bidirectional, audited, encrypted.

Scope and outcomes

What we deliver — and what it changes.

Technical work that connects business intent to loading execution.

  • SAP — ECC / S/4HANA / IS-Oil (HPM, TSW, TD); SAP TPI; standard TAS interfaces (load IDs, pickup checks, delivery confirmation, goods movements).
  • Microsoft Dynamics NAV (Navision) — direct prior experience: TAS-to-Navision interface delivered for Puma Energy. Customer & product master, sales orders, deliveries, posted invoices, item ledger, location transfers.
  • Microsoft Dynamics 365 Finance & Operations / Business Central — REST APIs, OData, sales orders, inventory postings.
  • Oracle JD Edwards EnterpriseOne — Sales Order Management, Bulk Stock Inventory, AIS Server / Business Services / IDocs / REST.
  • Oracle Cloud — Order Management & Inventory Management REST APIs.
Show all 8 items
  • Middleware patterns — IDoc, OData, REST, Kafka, OPC UA.
  • Customer & product master · Sales/delivery order download · Loading authorization · Goods movement & inventory postings · Billing trigger.
  • Three-way reconciliation — ERP ↔ TAS ↔ physical stock with exception handling, retry, and audit trail.

Representative scenarios

From projects we have participated in.

West African coastal terminal

Challenge

Multiple handoffs between business orders, loading control, and stock records.

Solution

Map ERP, TAS, and field events into a shared operating-chain view.

Outcome

A clearer path for reconciliation, shift review, and phased modernization.

Southern African inland depot

Challenge

Lean operations team needed better stock confidence and movement traceability.

Solution

Define BulkStock™ entry points around depot movements and daily controls.

Outcome

A practical roadmap for inventory visibility without replacing every system at once.

Multi-product tank farm

Challenge

Planning decisions depended on disconnected reports and manual checks.

Solution

Model constraints with a digital twin and expose KPI signals for operations.

Outcome

Better scenario review before changes reached live yard operations.

FAQ

Questions to settle before scope hardens.

Talk to us

Map your operating chain. We will show you where time, money, and traceability are leaking.

A focused discovery call gives you a practical view of the systems, field signals, and operating handoffs that deserve attention first.

We reply within two business days.