Documented use cases

What these companies do in Nereva

Pilot company, case study, attributed testimonials.

Each case follows the same grid: company, context, problem, configuration, flows, interfaces, what is documented, links to the evidence. Each testimonial is signed by an identified person.

15-day free trial · 2 licences included · No payment method required

The cab of an M. Ducret SA truck at a site entrance, red-and-white barriers and a worker in a yellow vest in the background, still from the Nereva film
  • Colas logoConstruction · case study
  • M. Ducret SA logoTransport · pilot company
  • Piasio SA logoCivil engineering · testimonial
  • TRDémolition SA logoDemolition · testimonial
Case 1

M. Ducret SA and Colas: a transport company and a construction company, connected

Companies
M. Ducret SA, transport company for construction (Nereva’s pilot company, Geneva); Colas, a player in infrastructure construction and maintenance (case study).
Context
Shared sites in French-speaking Switzerland: skips, evacuations and deliveries ordered by the site teams and executed by M. Ducret SA trucks.
Problem
Coordination by phone, with orders to be asked for again and addresses to be clarified.
Configuration
A Construction account with its foremen on Nereva Commandes; a Transport account with its dispatch in the back office and its drivers on Nereva Transports; a partnership between the two accounts.
Flows
On their shared sites, the foremen order from their phone; at the depot, the orders arrive structured, dispatch assigns and the evidence is filed with the mission.
Interfaces
Nereva Commandes, Construction back office, Transport back office, Nereva Transports.
What is documented
M. Ducret SA’s status as pilot company, Colas’s status as case study and the testimonial below, as published on the Our references page; the video shot in real conditions with an M. Ducret SA truck.

« The site orders directly from the mobile app, and our dispatch receives the information immediately. No more phone calls to pass on or confirm an order: everyone works on the same information. »

Nicolas DucretDirector, M. Ducret SA · Company website
Case 2

Piasio SA, Colas group: joining Nereva through its existing flows

Company
Piasio SA, civil engineering, Colas group (testimonial).
Context
A usual carrier already on Nereva: the flows existed before the account.
Problem
Keeping evidence of what was actually ordered on each site, and finding the requests and the transports carried out.
Configuration
A Construction account connected to its usual carrier through a partnership; its foremen on Nereva Commandes.
Flows
The foremen order from the site; the company finds, site by site, the requests, their evolution and the transports carried out.
Interfaces
Nereva Commandes, Construction back office.
What is documented
The testimonial below, attributed and published on the Our references page.

« Nereva allows us to keep digital evidence of what was actually ordered on each site. We find the requests, their evolution and the transports carried out, site by site. »

Julie ChanrionTechnical secretary, Piasio SA, Colas group · Company website
Case 3

TRDémolition SA: requests leave from the site

Company
TRDémolition SA, demolition (testimonial).
Context
Skip and evacuation requests issued directly by the sites.
Problem
Multiplying phone calls to pass on or confirm a request to the carrier.
Configuration
A Construction account, its sites and its foremen on Nereva Commandes, a connected partner carrier.
Flows
Requests leave directly from the site; the carrier receives the information; what is planned, what changes and what is done are visible in the same place, according to roles.
Interfaces
Nereva Commandes, Construction back office.
What is documented
The testimonial below, attributed and published on the Our references page.

« With Nereva, our requests leave directly from the site and the carrier receives the information without us having to make call after call. We see what is planned, what changes and what is done, in the same place. »

Luca LavanaWorks manager, TRDémolition SA · Company website

The typical flow

The skip exchange, seen from both sides

The typical sequence of a skip exchange between a connected site and carrier. It describes the product, not a particular site.

  1. The foreman orders

    Request type, skip type, waste type, time slot: in a few steps from the site.

    Nereva Commandes
  2. The request reaches the depot

    Structured, with the address and the skip type, in the Transport back office.

    Transport back office
  3. Dispatch assigns

    A truck, a driver, a time slot; the driver receives the mission with the delivery point and truck navigation.

    Transport back office · Nereva Transports
  4. The site follows

    The request status evolves in Nereva Commandes; the carrier is on the way.

    Nereva Commandes
  5. Skip exchanged, evidence filed

    The full one leaves, the empty one is in place; timestamped photos and delivery note stay attached to the request.

    Nereva Transports · back offices

The actual sequence of each operation is visible to both companies, in their interfaces, according to roles and permissions.

Filmed in real conditions

A skip exchange carried out by an M. Ducret SA truck

The camera follows the order, the notification and the mission, on a real site.

Video loaded only when played.

Contexts

Where offline mode matters

These contexts are generic examples of use of the field apps, not facts about the companies mentioned: within the supported scope, Nereva Transports and Nereva Commandes let you keep working when the connection drops, then synchronise when it returns.

  • Tunnels and basements
  • Underground car parks
  • Mountain areas
  • Remote sites
  • Quarries and gravel pits
  • Depots and industrial areas with poor coverage
Limits
  • Nothing is transmitted to other users before the connection returns.

How to read these cases

Use cases, in plain terms

Why are these cases presented without figures?

Because no measured indicator is documented for these companies: we publish what is established, statuses, configurations, flows and attributed testimonials.

What does “pilot company” mean?

M. Ducret SA was Nereva’s pilot company in Geneva: the platform was proven on its flows. This status is distinct from that of customer.

Are the testimonials genuine?

They are attributed to an identified person, with their function and their company, and published on the Our references page.

Do these companies use offline mode?

We do not document it. The contexts mentioned on this page are generic examples of use of the field apps.

Does Nereva intervene in the commercial relationship?

No. Your partners and your business relationships remain yours. Nereva synchronises operations without stepping into the commercial relationship.

The references and their statuses are kept up to date on the Our references page.

Go further

Pilot company, case study, attributed testimonials: evidence of use.

15-day free trial with 2 licences. No payment method required. Monthly subscription afterwards, no long-term commitment.