Terminals and depots: connect your operations

Pre-advice in the TOS. Movement information with its context.

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.

When a unit is already recorded but staff copy its data again

An operator sends pre-advice and staff search for service, unit and reference before registration. Amendments arrive later and movements are reported elsewhere. Edichemy scopes the connection to your TOS so available information supports agreed exchanges and discrepancies remain visible.

Plans and movements need different triggers

Pre-advice receipt does not confirm physical entry. Identify the fact authorising each response and keys linking visit, service and unit. Agree review for unmatched events instead of inventing another operation merely to finish processing.

Define the SIMPLE workflow separately

Identify documentation and sources for your terminal’s required SIMPLE exchange. TOS information may be reused, but an operator message does not establish another destination’s requirements. Separate terminal registration, outbound events and acceptance tests.

Before buying

Provide initial pre-advice, an amendment and an unknown reference. Check the TOS record, response and exception owners. State interface functions and maintainer work. This assesses the actual scope without promising every platform or software version.

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.

What should we prepare?

A representative operation, current software and partners. For terminals and depots, assessment focuses on the references and events described on this page.

Must we replace the software?

Retention is the starting point. Interfaces, permissions and available operations determine feasibility; state required adaptation in the offer.

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