I have a field / farm
Scenario. A night harvest on an open vineyard, with transfer into a cold tank.
Output. A briefing for that field and activity — evidence, official warning, MetOry advisory.
Impact. Rain or wind can close the picking window before the crew is in place.
I have a route / I am travelling
Scenario. A timed night handover at a port plus a motorway window.
Output. A corridor briefing. Official warnings stay on their own card.
Impact. Wind or rain can delay the handover. This is not turn-by-turn navigation.
I have a construction site / field operation
Scenario. Coastal scaffold and a crane window tied to a work shift.
Output. A site briefing that names what must still be confirmed before work proceeds.
Impact. Wind can stop the crane; MetOry does not certify the engineering stop rule.
I have a business / facility
Scenario. A warehouse with limited open loading and a weekday shift.
Output. Activity-specific context for the open yard versus the closed hall.
Impact. The same building is not one risk profile.
I have a city / community
Scenario. A municipality that must brief crews and the public when weather becomes operational.
Output. A community briefing that keeps official warnings attributed to the issuer.
Impact. Missing warning-source data is not treated as “no warning”.
I have a portfolio
Scenario. Several sites, teams and corridors under one operating profile.
Output. A request path for scoped portfolio monitoring — not a self-serve control room.
Impact. Volume does not turn illustrative demos into live operational engines.
I have customers / members
Scenario. A professional body that needs members to prepare in their own work language.
Output. A shared briefing pattern members can reuse. Not a second official warning service.
Impact. An alert that never reaches the person who must act still fails.