Orleans Flood Crisis models the George-V bridge, its tram line, its quay, the people who close and inspect it, and a water level sensor of the Loire whose CEP rules drive the risk and the flood. Each act starts from a fresh r-io: restart the distribution and load the use case again. The actors booked by a previous act would otherwise stay booked on the same dates.

1. In r-ioga, Projects workspace, click the card Orleans Flood Crisis, then Load.
2. Close Use-case successfully loaded !!! with OK: r-ioga opens Project List.
3. From the APPLICATIONS column, open R-IOSEMIT and R-IOTA, each in its own tab.

Resultr-iosemit shows the scenario Loire Flood At Orleans: 20 dates · 40 DATA steps, Forecasts on · 4; r-iota shows No alert detected !!!.

The timeline holds two tracks: the measures of the sensor (every 3 h) and four forecasts of Vigicrues (06:00, 12:00, 18:00 and 00:00, each over 24 h). In this act r-io must not receive any forecast.

1. In r-iosemit, TIMELINE, click the purple button 📉 Forecasts on · 4.
2. Click ▶, choose Discrete and Start: Discrete · step 0 / 20.

ResultThe button reads Forecasts off · 4, the four forecast cards are greyed and struck through, and the counter reads 20 dates · 40 DATA steps · 4 muted: they will not be played.

Each Next step plays one date. The level goes 2 → 2.3 → 2.7 → 3.1 → 3.6 → 4.1 m; each threshold crossed raises the probability of the risk (0.2, 0.5, 0.8). At 0.8 the risk becomes an alert.

1. Click Next step six times, waiting each time for the counter, until 14/11/2026 18:00 (step 6 / 20).
2. In r-iota, read the alert, then open the Forecast tab (second tab).

Resultr-iota shows 1 SURE ALERTS and a red status: George-V bridge flood risk at George-V bridge, prevented by Prevent the George-V bridge flood risk. The Forecast tab confirms the forecasts are off: No forecast published yet: the projection appears as soon as a forecast of a sensor is received. The supervision timeline stops at now: nothing is projected.

Without forecast, the deduction only knows that the risk is at 80 %: it plans to prevent it, and keeps the corrective procedure in reserve in case the flood comes anyway.

1. Click FIND SOLUTION(S): Include forecast stays at NO (no forecast was received). Set Advanced options strategy to YES and click Find.
2. In Drools - Crisis Satisfaction Strategy, the risk has Preventive and Corrective checked: Close a bridge to traffic prevents it, Secure the surroundings of a threatened bridge treats the flood. Click Deduce.
3. Read Solution found, then click Deploy and supervise.

Result27 task(s) in the process: Start → Nominal SubTask → End, and from the Nominal SubTask an Event_Flow (CE) towards Secure the surroundings of a threatened bridge, which only starts if the actuality Loire flood at George-V bridge appears.

r-iosemit can play the field: in Auto, each task is accepted as soon as the process reaches it and ends after its duration, moving the clock forward.

1. In r-iosemit, tab TASKS, check AUTO in the header of the situation George-V bridge flood risk at George-V bridge.
2. Watch the clock: Stop a tram line 18:02 → 18:18, then Close a bridge to traffic from 18:18, for 2 h 30.

Resultr-iota shows total: 27, 0 / 2 objectives and a blue status. The expected duration of the plan is an interval, 12:15:00 – 1d 06:15:00: the waits of the corrective last from 6 to 24 hours.

At 20:00 the level reaches 4.6 m: the risk becomes the actuality Loire flood at George-V bridge. The bridge closure, started at 18:18, ends only at 20:48: the preventive procedure cannot be completed before the flood. Its Event_Flow fires and the corrective procedure starts.

1. Let the clock run past 20:00 (the end of a task plays the steps of the timeline met on the way).
2. In r-iota, scroll to Objectives realized; in r-ioga, open the To Do List.

Resultr-iota: the objective counter goes to 0 / 1, with Objective ‘Prevent the George-V bridge flood risk’ replaced by ‘Secure the George-V bridge threatened by the flood’: the risk became the actuality. To Do List: the preventive tasks not started (Set up a detour, Run replacement buses, Inform the population, the preventive inspection and reopening) are Abandoned; Stop a tram line, already done by the preventive, is marked done in the corrective; the corrective tasks start at 21:00.

The corrective holds two Wait Until tasks run by the process engine: Wait until the flood has receded and Wait until a bridge can be inspected. They read their condition again and again; the model only says how long they usually last.

1. In the To Do List, click Wait until the flood has receded (orange).

ResultThe task started at 22:00. Its expected duration is the modelled interval, 21600 – 86400 seconds (6 to 24 hours): without forecast nothing narrows it, and the To Do List shows its end as not yet known (projected).

The flood is released when the level stays under 4.0 m for 6 hours: on 16/11 at 00:00 in this timeline.

1. In r-iosemit, tab TIMELINE, click Next step until 16/11/2026 00:00 (step 18 / 20).
2. Let the last tasks run, then read r-iota and the To Do List.

ResultBoth waits end at 00:00; Inspect a bridge after a flood and Restore the utility networks run 00:00 → 02:00, Reopen a bridge to traffic 03:00 → 04:00, Announce the reopening 04:00 → 04:30. r-iota shows 1 / 1, 2 achieved tasks on 2 expected (total: 27) + 17 corrective, No alert detected !!! and a green status.