Receive SIMPLE information in your TOS to organise terminal operations

For terminals seeking to reuse TOS records and reduce repeated data entry.

In your TOS

Unit pre-advice
Unit
Already recorded by your team
Service
Its reference in the TOS
Movement
The fact confirming the operation

Your team already works with this information.

edichemy

Your system’s pre-advice, prepared for SIMPLE.

Edichemy uses your terminal record to prepare the exchange your operation needs to communicate.

  • Reuse information already in the TOS.
  • Adapt references and fields to the agreed flow.
  • Link the response to its source operation.
The work you want to avoid

Avoid finding and re-entering the same information in another form.

Explore SIMPLE connectivity

Illustrative example. Interfaces and rules are scoped for your terminal.

Use incoming information to prepare the terminal

Identify received information that supports arrival planning, resource allocation or movement coordination. Integration should relate it to the correct unit or service in your TOS.

Start with one terminal operation

Choose a representative pre-advice or movement. Locate its unit, service references and confirmation point in the current TOS. This provides a practical basis for assessing the SIMPLE connection.

Review TOS interfaces

Identify read and write interfaces, permissions and amendment handling. Edichemy scopes the exchange around these capabilities. Any TOS adaptation needs an identified owner, cost and timeline.

Request a scoped proposal

Specify source fields, validation, available responses and incident handling. Test a valid record and a correction. Tell Edichemy your TOS, terminal type and priority exchange to begin scoping.

Questions that help you decide.

Clear answers about scope, existing software and your team’s work.

Can Edichemy receive information as well as send it?

Scope may include receiving and sending. We define participant data, your team’s needs and how to use it in your software. Connectivity supports planning and coordination, subject to available data, permissions and interfaces.

DEFINE YOUR CONNECTION

Your next step,
with a clear scope.

Tell us about your software and required exchange. We will review the journey to prepare a proposal your team can assess.

Discuss my operation

Scope your Edichemy connection

Move from your required workflow to a clear purchasing scope.

S.I.M.P.L.E.Cost and scopeImplementationRequest a proposal