EDIPRISM · EDI INTEGRATION

EDI integration with your TOS

Connect shipping-line and operator messages to your terminal operating system.

HOW INFORMATION FLOWS
01Pre-advice or eventSource information
02Terminal rulesMapping and rules
03TOS and partnersData where it is used

Conceptual diagram. The actual flow is defined using your data, interfaces and partner specifications.

IN YOUR OPERATIONS

Connect shipping-line and operator messages to your terminal operating system.

Keep your systemConnectivity starts with the software you already use.

Use the informationDefine where it belongs and which action it should trigger.

Understand the scopePartners, adaptations and maintenance, defined.

The TOS keeps managing the terminal; integration brings data closer

Terminal teams need pre-advice in the correct record and movement reporting based on confirmed events. This requires mapping units, references and statuses between operator and TOS. An Ediprism proposal identifies reusable interfaces and tasks retained by the existing system. SIMPLE requirements, if included, are documented separately to clarify shared data and additional adaptations.

Match equipment, orders and events

The TOS needs to recognise which unit or service a message represents. Identifiers, references and statuses are reviewed alongside rules for accepting orders or updating existing records.

Choose the milestone that triggers communication

Planned and executed movements have different meanings. We define which TOS event triggers a message, which references it carries and how to prevent a planning change being reported as completed work.

Separate EDI exchanges from SIMPLE connectivity

Shipping-line, customer and S.I.M.P.L.E. flows are documented separately. We assess reusable TOS data and additional information needed for each destination without treating their models as equivalent.

What we need to assess the connection

Software identity and version, available interface documentation and an anonymised example exchange. Permissions, test environments and responsibilities are reviewed with the vendor or developer. Connectivity is confirmed by scope; brand compatibility is not claimed without verification.

Before you choose a provider

Does the system need changes?

It depends on available interfaces and the intended result. Configuring an import may be enough, or an interface may need adding. This is identified before agreeing the proposal.

How is it verified?

Through agreed creation, amendment, retry and error scenarios. Acceptance must confirm the destination-system result and any responses required by the partner.

What does my software need to connect?

An interface supporting required input or output, available permissions and documentation. The vendor confirms operations and necessary adaptations.

Does Ediprism directly modify the database?

That access is not assumed. Agree an appropriate interface with the system maintainer and document registration before implementation.

How is document registration confirmed?

Define destination responses or evidence. Distinguish file receipt from operational registration to detect pending work.

What about missing references or duplicates?

Agree retry detection, original-document references and incomplete-data handling, with update, rejection and intervention rules.

Who maintains the connection?

Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.

How much does integration cost?

Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.

Define your connection.

Review the partner, your system and the result you need. A proposal starts with that scope.

Assess my integration

Privacy preferences

The website works without measurement. Your preference is stored for 180 days.

Necessary preference

Stores your choice across pages. It is not used for tracking.

See technologies and retention