Pre-advice needs to reach the TOS before operations need it
EDI pre-advice still creates work if staff copy the data or search for the corresponding order. Terminal and depot integration must match units, references and services to the management system, while distinguishing planned information from confirmed movements. Scope follows the journey from the operator’s message to the TOS record and the information available for a response.
Operator EDI and SIMPLE connectivity need defined scopes
If you also need S.I.M.P.L.E., reuse available information without treating the exchanges as identical. An Ediprism proposal should identify TOS source data, confirming events and adaptations for each destination. Ask for included flows, handling of incomplete information and maintenance ownership. Keeping your existing software requires checking its interfaces as well as the operator message.
Pre-advice needs to reach operations
Information from a shipping line or operator only adds value when matched to the equipment, services and orders the terminal manages. We assess where the data belongs and which operational decisions depend on it before defining the connection.
From confirmed movement to outgoing message
Outbound communication matters too: an event should be sent when the agreed milestone occurs, using the correct references. We define its source, the relationship between TOS and partner statuses, and the handling of corrections or retries.
SIMPLE as an additional flow
S.I.M.P.L.E. connectivity is assessed against data and events available in your system. Shipping-line exchanges and platform reporting are not automatically the same flow: each requires its own scope, requirements and checks.
What we review before quoting
Identify existing software, the partner and its documentation, inbound and outbound flows and available interfaces. This enables agreement on test scenarios, exception ownership and readiness criteria. The proposal should reflect adaptations needed for the specific exchange.
Before you choose a provider
When is Ediprism a fit for my business?
When you need to connect a partner exchange to existing software and can define the operation it should produce. Fit is confirmed by reviewing messages, interfaces, data and responsibilities, not industry membership alone.
Must I replace my existing software?
The proposal uses your existing application. We first confirm its import, export or API capabilities; configuration or adaptation may be required.
What determines the cost for this case?
Partner count, documents and their variants, mappings, interfaces and testing. Pricing follows a defined scope rather than assuming every connection in the industry is identical.
How does Ediprism connect systems in my industry?
Define the journey between Operator pre-advice and TOS or terminal system. Ediprism adapts references and structures for the available interface and agreed responses.
Which documentation is needed?
Partner guidelines, anonymised examples and software documentation. Operations confirms data meaning and required results alongside technical review.
How are customer changes handled?
Distinguish new data, amendments and retries. Match messages to operations and define automatic updates versus review.
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.
Can we start with one customer?
A limited useful flow can be scoped, with boundaries and extension conditions defined.