Forecasts and tensions
Forecasts and tensions: what exists, what is being prepared
Today, the schedule. Anticipation by EVA is under development.
The schedule per truck and per driver already shows overlapping slots, the requests to be scheduled and each driver’s status. Spotting a tension before it happens and proposing an adjustment is the intended role of EVA, the anticipation engine Nereva is developing. This page gives the status of each capability.
15-day free trial · 2 licences included · No payment method required
Status per capability
Each capability has a status, spelled out in full
What exists today is a reading of the schedule and of the data produced; anticipation is EVA’s development in progress. The status of each capability is written out in full.
| Capability | Status | What it means |
|---|---|---|
| Slot conflicts | Available today, by reading | The schedule per truck shows overlapping slots; the dispatcher arbitrates by moving a mission or warning the site. |
| Resource availability | Available today, by reading | Trucks, drivers (online or offline) and requests to be scheduled can be read in the schedule; the dispatcher decides with the real situation in front of them. |
| Schedule tensions | Under development (EVA) | Spotting converging slots and rotations to shift, then flagging them with a proposal. |
| Adjustment proposals | Under development (EVA) | Shift, group, reorder: proposals submitted to the dispatcher, who validates or ignores. |
| Load forecast | Under development (EVA) | Estimating the load of a day or a week from the requests received: designed as an aid, never as an autopilot. |
| Demand forecast | Vision | Anticipating future requests before they are placed: a research direction. |
| Anomalies | Vision | Flagging what is out of the ordinary in the flows: a research direction. |
A capability changes status when it is actually delivered. Statuses are identical in the site’s four languages.
The schedule per truck: what the dispatcher sees before arbitrating
The per-truck and per-driver view shows the day’s missions, the requests to be scheduled and the requests postponed by the driver. Changes propagate to the site and the driver according to roles and permissions. It is a reading, not a forecast.
- Missions per truck and per driver, in daily or weekly view
- Requests to be scheduled and requests postponed by the driver, visible in the schedule
- Status of each driver: online or offline
- Notifications when a client modifies or cancels a request
Under development
How a forecast would come about, once EVA is ready
The principle is set: three stages, always in the same order, and a decision that remains human.
The field feeds
Each request, each timestamped step, each cancellation and each wait recorded in the platform form the base. No additional entry.
Platform · todayEVA spots and proposes
Two removals and a delivery converging on the same slot: the tension would be flagged with a concrete adjustment, to be validated.
EVA · under developmentYour dispatchers decide
Shift, group, anticipate or ignore: the proposal never triggers on its own.
Transport back office · always
The outputs of the models are of an indicative nature: the decision belongs to the teams (AI and data policy, art. 22).
Analytics and forecasting
Reading what happened, or anticipating what is coming: two different things
Analytics: available today
- Dashboard: closed requests, kilometres driven, skips on sites, costs per site
- Daily and monthly statements, per-truck reports
- History per site, per client and per truck
- Indications on data already produced
Forecasting: under development or vision
- Scheduling tensions and adjustment proposals: under development (EVA)
- Load forecast: under development (EVA)
- Demand forecast and anomalies: vision
- Proposals submitted to the teams, who decide
The Analytics page describes the available readings; the EVA page describes the development programme.
A capability becomes available when it is actually delivered.
It then moves to “available” status, in the tools your teams already use. Until then, the schedule and analytics do the job, and your dispatchers stay in control.
Developments in progressGo further
The pages related to forecasts
- EVAThe anticipation engine, under development: statuses and data used
- Analytics and reportsDashboard, statements, history: the available readings
- Alerts and notificationsThe notifications that exist today
- Transport featuresSchedule, dispatch, missions, drivers
- Developments in progressThe product work in progress
Your questions
Forecasts and tensions, plainly
How are slot conflicts handled today?
By the dispatcher: the schedule per truck shows overlapping slots and they arbitrate, by moving a mission or warning the site. Automatic tension detection and adjustment proposals by EVA are under development.
Does Nereva display forecasts?
Today, the dashboard and the statements read data already produced: closed requests, kilometres driven, skips on sites. Anticipation (demand, load, tensions) falls under EVA, under development.
Does Nereva optimise rounds?
The dispatcher stays in control of their rounds, with the schedule per truck and per driver to organise them. The schedule proposal by EVA (mission order, groupings, slots) is under development: it will be submitted to the dispatcher, never imposed.
Will EVA take decisions instead of the teams?
No. The proposals will be of an exclusively indicative nature: your dispatchers validate, modify or ignore. No automated decision is taken about people.
When will forecasts be available?
Each capability will change status when it is actually delivered, in the tools your teams already use.
Does Nereva step into the commercial relationship?
No. Your partners and your business relationships remain yours. Nereva synchronises operations without stepping into the commercial relationship. It takes no commission on flows.
Other questions? The general FAQ and the EVA page complete these answers.
Go furtherThe schedule per truck today, anticipation with EVA under development.
15-day free trial with 2 licences. No payment method required. Monthly subscription afterwards, no long-term commitment.