Rail operators: connect your operations

Services, units and events connected across participants.

In your rail application

Service and units
Service
The operation to identify
Units
Those related to the service
Event
The milestone and its confirming participant

Your team already works with this information.

edichemy

One operation, recognisable to operator and terminal.

Edichemy matches references across systems to preserve exchange context.

  • Retain service, unit and location relationships.
  • Distinguish planning from executed events.
  • Define treatment of amendments and pending references.
The work you want to avoid

Avoid rebuilding service and event relationships whenever a message arrives.

Request a proposal for my case

Illustrative example. Participants and interfaces are defined in the proposal.

Participants know the operation through different references

Operators and terminals may identify one service differently. Connect units, locations and events with the right context rather than moving isolated messages. Edichemy scopes this journey to reduce reconstruction across spreadsheets, applications and partner enquiries.

Event authority matters

Planned departure and executed departure mean different things. Identify the authoritative source and destination interpretation. An event preceding its matching reference needs agreed treatment rather than assignment to the first service containing a similar unit.

Connect existing operations to external workflows

Review application and partner interfaces. Separate requirements and tests for SIMPLE or eFTI preparation where included. Shared sources do not establish equivalent models or access to every rail platform.

What to request

Use a service with multiple units, a reassignment and an out-of-order event. Define outcomes and discrepancy owners. Name relationship keys, sources, destinations and participant tasks to assess operational continuity without assuming universal rail coverage.

Questions that help you decide.

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

What should we prepare?

A representative operation, current software and partners. For rail operators, 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