Everything starts from r-ioga: the use case is loaded into the knowledge space, then every other application is opened from the project row, so that it works in the context of the project.

1. In r-ioga, Projects workspace, click the card Crisis Event Show Parc des Princes.
2. In Use case loading options, click Load without changing anything. When asked whether to create a specific collaboration for the predefined users, answer No.
3. Close Use-case successfully loaded !!! with OK: r-ioga opens Project List.

ResultThe project row shows the Collaborative and Crisis domains, nine model extensions (Electronic Tools, Urban, Road Network, Furniture, Electrical Network, Water Network, Urban Rail Network, Animal, Industry) and twelve launchers in the Applications column.

The context of the event is a stadium in Paris and the staff who run it: spectator services, security, technical services, reception, ticketing, each person with a role.

1. In Project List, launch r-ioda.
2. Open the Context And Partners tab, then zoom out with the editor toolbar.

ResultThe diagram shows Stade du Parc des Princes, the Parc des Princes site inside Paris, and the staff around it (Marc Dubois, Spectator Services Staff; Camille Leroy, Security Manager; Lucas Bernard, Chief of Reception…).

r-ioplay opens on the plan of the stadium, with its gates (A to P), the staff and the push buttons that act as sensors. The MAP selector switches to the world map or to the 3D views.

1. Launch r-ioplay from Project List.
2. In the MAP selector, choose World.
3. Then choose 3D Parc des Princes and zoom in with the mouse wheel.

ResultThe map follows the selector without reloading the page; the 3D view comes with its MOVE / LOOK / ALT / ZOOM panel.

Before the first incident, r-iota, the crisis tracking cockpit, has nothing to report.

1. Launch r-iota from Project List and keep it open for the whole scenario.

Resultr-iota shows No alert detected !!! and a green status.

The Full scenario game scenario plans three incidents. The first one is the actuality Door Breakdown on Gate B, raised by the CEP rule of the Gate B sensor. Two objectives answer it: one treats the door itself, the other one redirects the crowd.

1. Launch r-iosemit: the timeline of Full Scenario shows 3 dates and 6 DATA steps.
2. Click Next step (16:03:33, Door Breakdown on Gate B).
3. In r-iota, click OPEN DETAILS to read the problems, then Cancel.

Resultr-iota shows 2 SURE ALERTS and a red status; two red pulsars blink on Gate B. The details list Door Breakdown on Gate B twice, once with Treats Door Breakdown, once with Treats Crowd Orientation.

The Crisis strategy deduces a collaborative process for both objectives, deploys it and supervises it. Each task is a human task in the to-do list of r-ioga; r-iota follows the process live.

1. In r-iota, click FIND SOLUTION(S); keep the preselected strategy Drools - Crisis Satisfaction Strategy and click Find.
2. Open the Execution graph tab of r-iota.
3. In r-ioga, open To Do List. For each task, tick its box, then click Save in Set real value on indicators of the task. (Since October 2026 the to-do list has no tick box: click the task, then Accept, then Done.) Follow the graph of r-iota between two tasks.
4. Back in r-iota, once every task is done, click Delete positive deviations (the add_circle button), leave the objectives on YES, click Delete, then Refresh.

ResultThe deduction plans 10 tasks (total: 10 = Total tasks 10): five start at once (identify the fault, check the IT and ticketing systems, check the door, request its closure), then Confirm door closure unlocks the four tasks that redirect the public and inform the managers. At the end, RESOLVED / TARGET 2 / 2 and the pulsars turn orange. After Delete positive deviations, both objectives are deleted, the supervision ends and the pulsars disappear.

The second date references the frozen actuality Broken Seat of the stadium: r-iosemit creates an active clone, Broken Seat number 11, with its picture. Two objectives answer it: one for the seat, one for the spectator who sat on it.

1. In r-iosemit, click Next step (16:17:44).
2. In r-iota, OPEN DETAILS, then Cancel; then FIND SOLUTION(S) → Find.
3. In r-ioga, complete the seven new tasks as before, following the graph of r-iota.
4. In r-iota, Delete positive deviations → Delete → Refresh.

Resultr-iota shows 2 SURE ALERTS: Broken Seat number 11 with Treats Spectateur and with Treats Broken Seat. The deduction plans 7 tasks: take charge of the spectator, assign a new location, escort them, evaluate the handling with the Spectator Services Manager; mark the seat as broken in the ticketing system, secure it and schedule the repair. Once done, the pulsars turn orange, then Delete positive deviations removes both objectives.

The last date raises Metro line breakdown at Aera 2, from the metro line sensor. A single objective answers it: reorganise the access to the stadium.

1. In r-iosemit, click Next step (16:36:02).
2. In r-iota, OPEN DETAILS, Cancel, then FIND SOLUTION(S) → Find.
3. In r-ioga, complete the six new tasks.
4. In r-iota, Delete positive deviations: this time the dialog lists the objective and the actuality. Delete, then Refresh.

Resultr-iota shows 1 SURE ALERTS: Metro line breakdown at Aera 2 with Treats Metro line breakdown. The deduction plans 6 tasks (inform the teams, coordinate access to the stadium, then direct spectators to the right entrances, unlock all tickets on all doors, inform the security personnel, reinforce staffing around the station). Once done, the pulsar turns orange; Delete positive deviations deletes the objective and the actuality, and r-iota is back to No alert detected.