Planning versus execution: define the operational meaning
Start by describing planning versus execution through an example from your operations.
A terminal may receive planned information, record a movement and communicate confirmation. These are related but different states. Define the trigger and confirmed information for each message; receiving pre-advice does not establish that a unit has physically passed through the facility or completed the intended operational step.
Unit reference: establish the actual scope
Reviewing unit reference separates available functions from remaining work.
A unit reference needs the relevant operational context. Check which keys distinguish visits, services and orders in the TOS. When the unit appears again, each message should relate to its intended operation rather than update the first matching record simply because the equipment identifier is the same.
Partner acceptance: identify evidence of completion
For partner acceptance, distinguish sending information from actually using it.
Agree event sources so planning data cannot trigger an executed-movement confirmation. Identify which TOS action or other system confirms the movement. Where staff review the information later, explain when it becomes reportable and what level of confirmation the receiving partner can reasonably infer from the message.
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. Review scope: EDI integration for terminals and depots.
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. Review scope: EDI integration for terminals and depots.
An example to frame the decision
Illustrative scenario, not attributed to an actual customer. 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. Check movement information arriving before pre-advice or before a destination reference exists. Define a pending state and review owner where appropriate. The connection should neither invent information to close the sequence nor silently discard an event operations needs to investigate before the workflow can continue correctly.
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. Test the complete sequence: pre-advice, amendment, movement and response. Include a correction and an unmatched reference. Verify that each step affects the correct operation and staff recognise pending cases. A standalone inbound example does not validate the full cycle or the outbound information generated by the terminal.
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.
Compare proposals using the same workflow
Give each provider the same incoming document, intended result and required response. Ask how it covers planning versus execution, unit reference and partner acceptance. Compare partner adaptation, existing-software tasks and acceptance criteria. Identify the effect of adding documents or changing specifications. A lower price may cover fewer stages; a broader project may include functions you do not yet need. Compare useful scope before comparing price, so the decision reflects the workflow your team actually needs.
Prepare the first discussion
Identify software name and version, partner and available documentation. Draw one unit's operational sequence and identify the source of every fact when requesting a proposal. Add incoming messages, TOS events and required confirmations. This exposes gaps before pricing and separates a useful first phase from later extensions that need additional information sources or software work.
Where Ediprism fits
Ediprism is EDI integration software between your business systems and third-party applications. Ediprism can connect terminal exchanges with the TOS and other in-scope systems. Adaptation follows available events and interfaces. Using an EDI layer should not imply automatic coverage of every platform or requirement affecting the facility; each relevant workflow needs its own confirmed sources and destination rules.
Initial cost, continuity and later changes
Separate implementation, third-party services and maintenance. List incoming and outgoing messages in the quote instead of grouping everything under terminal EDI. Ask which TOS operation feeds each outbound message and whether adaptation is required. Applicable SIMPLE workflows should be explicitly identified where they form part of the contracted project rather than inferred from general terminal connectivity.
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.
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.
A first flow with standalone value
For a limited phase, define one document, one partner and one useful operational result. If several sources can report a movement, decide which is authoritative for the contracted flow. Two messages about the same unit are not necessarily two separate facts. Rules should prevent duplicate confirmation and support investigation of timing or content differences without simply preferring whichever message arrived last.
References that help investigate exceptions
Users reporting differences need to locate the corresponding message and operation. Operations and support need to distinguish planned, executed and reported information. Agree evidence for partner disputes and who approves corrections. A sending history is insufficient unless the team can explain which physical event supported each message and how later rectification affects the information already communicated.
Distinguish objectives from verified capabilities
A business need describes the result sought but does not prove the system has every required function. Include units already within the operational cycle at transition. Mark previously reported messages and those continuing through the new route. A boundary based only on activation time can leave an exchange incomplete when its operation began before cutover and finishes afterwards through a different reporting process.
Decide the next step
Identify the unresolved question and information needed to answer it: perhaps an ERP interface, amendment meaning or customer response. Request an event map with source, emission condition and recipient. This gives the terminal a complete lifecycle view even when partners receive different documents. Operations should be able to explain the exchange without confusing the technical message sequence with the physical execution of terminal activities it represents.
1. Identify the exchange
Capture the business need, partner specification and existing system. Confirm the result each document should produce and the data it requires.
2. Agree the solution and ownership
Define interfaces, mappings, validation and responses. Responsibilities across Ediprism, your team, software vendor and partner must be documented alongside prerequisites.
3. Test realistic scenarios
Agree inbound and outbound examples, amendments, retries and exceptions. Testing verifies final-system data and partner responses. Timing also depends on access and third parties.
4. Prepare go-live and continuity
Determine monitoring ownership, incident escalation and maintenance before operation. Version and specification changes need a review, testing and acceptance process.
A module in your existing software
A module may fit if it covers required documents, partners, versions and business rules. Ask what is included and what needs configuration or development. Check the effect of adding customers or changing specifications, since fit depends on scope and maintenance.
Custom integration development
This can fit when your team intends to build and maintain the workflow and understands the systems and partner requirements. Include interpretation, mapping, responses, tests and subsequent changes. The first transmission is not the whole project: identify incident ownership and documentation responsibilities.
An exercise to evaluate the proposal before buying
Assessment scenario; not results from an actual customer.
Represent a unit's journey from pre-advice to movement confirmation. Identify the originator, holding system and relationship keys at each stage. Keep planning separate from execution: a planned message or unconfirmed TOS date should not automatically trigger confirmation of a physical fact.
Add pre-advice amendment, a movement preceding its reference and a later correction. Identify applied and pending cases with review owners. Where several sources report one fact, establish duplicate prevention and discrepancy rules. Show the complete resulting state rather than isolated message examples.
Link unit, relevant visit or service, event and response in evidence. Identify any in-scope SIMPLE requirements and tests expressly instead of inferring them from other documents. This compares terminal lifecycle proposals without implying coverage of platforms or requirements whose real documentation and interfaces remain unreviewed.
Reference documentation
Partner and system specifications define the project. These references describe the framework, not Ediprism compatibility or certification.
Before you choose a provider
How do I apply this guide to my case?
Identify your software, partner and intended result. Assessment should review planning versus execution, unit reference, partner acceptance using examples and available interface conditions.
How do I compare providers?
Provide both with the same document, system and intended result. Compare workflow coverage, interfaces, responses, implementation, support, changes and cost.
How much does integration cost?
Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.