Before connecting the systems
A terminal receives operator pre-advice and enters part of it into the TOS. Movement information is later returned through another channel. A specific S.I.M.P.L.E. exchange also needs operational data. This scenario identifies an integration need. It does not describe an actual implementation or customer results.
Who needs the solution and what they must decide
The illustrative terminal needs separate pre-advice, registered operations and confirmed movements. Receiving a document would not establish acceptance. Operations must recognise the unit and service in the TOS, with SIMPLE flows defined against their own requirements.
Information exchanged
Pre-advice, unit and service references, orders and TOS events. The SIMPLE flow uses data required by its specific scope, separately from operator messages. Review anonymised examples, specifications and availability of each field before mapping. Missing data or unavailable interfaces must be included in scope.
Proposed Ediprism integration
Import pre-advice through the TOS interface, map references and prepare outbound messages from confirmed events. Define SIMPLE mapping, communication and responses separately. Ediprism sits between third-party software and the business system. Define receipt, transformation, delivery and any required return flow. Confirm interfaces and available functions with the teams maintaining both systems.
Changes, retries and exceptions
Unmatched units, amended pre-advice, unconfirmed events or destination rejection require separate technical receipt, TOS registration and platform acceptance states. Distinguish received messages, accepted records and confirmed responses. Identify who reviews cases that cannot be automated and which information is needed to resolve them.
Implementation approach
Start with one operator's pre-advice and the TOS registration interface, testing amendments and unknown references. Scope outbound events next and identify applicable SIMPLE exchanges expressly rather than equating shared data with identical workflows.
Intended improvement and measurement
Review manual pre-advice entry, pending references and discrepancies between forecasts and confirmed events. Assess responses for the specified SIMPLE flow separately. These are hypothetical evaluation criteria, not achieved reductions or evidence of certification.
What to request in a comparable proposal
Commercial scope would name permitted TOS operations, partners, outbound events and maintainer tasks. SIMPLE documentation and acceptance remain distinct. Assess Ediprism against confirmed journeys without turning a first phase into universal coverage of the terminal.
Before you choose a provider
Is this an actual customer case?
No. It is a fictional scenario explaining a possible application. No customers, testimonials or actual implementation results are attributed.
What must be confirmed for my business?
Software on both sides, available interfaces, partner specifications, data and operational scope. These establish a specific proposal.
What would the cost and timeline be?
They depend on scope and identified dependencies. This example does not imply a price, available connectors or universal delivery time.
Must I replace my software?
The proposal starts with existing systems. Interfaces, functions and permissions are reviewed; configuration or adaptation may be needed.
How much does integration cost?
Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.
How long does implementation take?
Timing depends on scope, access and participant availability. There is no universal deadline for all systems and partners.
Who maintains the connection?
Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.