A good crossing starts with connected work.

One crossing connects four perspectives.

A sailing change affects travel information, ticket use and the operational record. Ferryon brings those relationships into the application.

1. Travellers plan and pay

   With the Riveer app, travellers plan a crossing, buy tickets and check themselves in. Current sailing times, notifications and invoices are available in the same place.

2. The crew keeps sailings current

   A delay, cancellation or extra sailing changes more than the timetable. The Ferryon platform connects operational changes with the information travellers need.

3. The operator checks and reconciles

   Tickets, check-ins, payments and exceptions come together in daily work. The platform supports checks and financial reconciliation around the same crossing.

4. Public authorities gain insight

   Reporting on use, revenue and performance supports the management and accountability of the ferry service.

Explore the Riveer app Discover the Ferryon platform

The ferry service shapes how the platform works.

Routes, ticket types, fares, sailings and responsibilities belong to the business model. Ferryon is built with APPSS to connect those agreements with what travellers, crew and finance staff need to do every day.

Ferryon connects the whole operation.

• Journey planning and current information for travellers.
• Digital tickets, payments and check-in around the same journey.
• Roles, checks and exceptions for daily operations.
• Financial reconciliation and reporting for the organisation.

The business process behind the ticket

Paid, valid and used are different facts.

Ferryon describes tickets, payments and check-ins as parts of the same operation. Their different meanings show why an application needs more than separate screens: each matters differently to the traveller, crew and finance team.

• Payment

  The amount has been processed

  The financial question: which payment belongs to which purchase, and what still needs reconciliation? A payment alone does not tell you whether someone has travelled.

• Validity

  The ticket fits the journey

  The business rule: for which route, traveller, ticket type and period may this ticket be used? Those agreements determine what a ticket check needs to assess.

• Check-in

  Use has been recorded

  The operational question: what use has been recorded, and what does that mean for the ticket, its handling and reporting?

This explains the relationships, not Ferryon's complete internal rules. For your business, we similarly establish which facts and decisions need to support everyday operations.

Publicly described production use

More than a concept screen.

• about 74,000

  check-ins per week at Riveer

• 99.7%

  of transactions directly matched at Riveer

Ferryon publishes these figures for Riveer's production environment. They are not independently verified savings or performance claims for other APPSS projects. See the figures published by Ferryon