EDIPRISM · EDI INTEGRATION

EDI integration for rail transport

Connect operator, terminal and customer data to your rail systems. Match services, units and events without relying on email coordination.

HOW INFORMATION FLOWS
01Service informationSource information
02Units and eventsMapping and rules
03Rail system or TMSData where it is used

Conceptual diagram. The actual flow is defined using your data, interfaces and partner specifications.

IN YOUR OPERATIONS

Services, units and events with consistent references.

Ediprism is an EDI integration solution connecting rail transport exchanges to existing software. Each project is scoped by partner, data and destination system.

Keep your systemConnectivity starts with the software you already use.

Use the informationDefine where it belongs and which action it should trigger.

Understand the scopePartners, adaptations and maintenance, defined.

Service information should stay connected across operators and terminals

Teams need to match services, units, locations and events even when participants use different references. Changes arriving through separate channels require checking what is current and where to update it. Rail EDI integration identifies the source and operational meaning of each datum, defines amendments and agrees the responses needed by other participants.

What a proposal should resolve for rail operations

Describe the operators, terminals and customers involved and what your system must do with their information. Assessing Ediprism requires reviewing service data, shared references and available milestones. Any specific SIMPLE requirement is documented within the applicable scope. Contracting should clarify interfaces, event ownership and acceptance of the full journey, including exceptions and changes.

One service, several organisations

Operators, railway undertakings, terminals and customers may use different references and applications. The project must identify which part of the service each datum represents and who can authoritatively communicate an update.

Match units, services and locations

Translating a field is not enough. We need to check unit identifiers, service relationships and the meaning of locations and statuses in both systems. Rules are agreed with partners to avoid records that arrive but cannot be used.

Events that can actually be communicated

We review which milestones are recorded in the system and which require additional information. A SIMPLE connection is scoped separately when needed; it is not inferred merely because a business operates rail transport.

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.

Before you choose a provider

When is Ediprism a fit for my business?

When you need to connect a partner exchange to existing software and can define the operation it should produce. Fit is confirmed by reviewing messages, interfaces, data and responsibilities, not industry membership alone.

Must I replace my existing software?

The proposal uses your existing application. We first confirm its import, export or API capabilities; configuration or adaptation may be required.

What determines the cost for this case?

Partner count, documents and their variants, mappings, interfaces and testing. Pricing follows a defined scope rather than assuming every connection in the industry is identical.

How does Ediprism connect systems in my industry?

Define the journey between Service information and Rail system or TMS. Ediprism adapts references and structures for the available interface and agreed responses.

Which documentation is needed?

Partner guidelines, anonymised examples and software documentation. Operations confirms data meaning and required results alongside technical review.

How are customer changes handled?

Distinguish new data, amendments and retries. Match messages to operations and define automatic updates versus review.

Who maintains the connection?

Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.

How much does integration cost?

Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.

Can we start with one customer?

A limited useful flow can be scoped, with boundaries and extension conditions defined.

Define your connection.

Review the partner, your system and the result you need. A proposal starts with that scope.

Assess my integration

Privacy preferences

The website works without measurement. Your preference is stored for 180 days.

Necessary preference

Stores your choice across pages. It is not used for tracking.

See technologies and retention