#energy
#saas
#logistics
Concept
Lumen • What if Suez closes tomorrow?
Lumen • What if Suez closes tomorrow?
A concept for the routing data page in Lumen, FGE NexantECA’s gas and LNG scenario platform. Analysts can switch off a route or a whole canal, choose for how long, and see straight away whether the change moves the price.
A concept for the routing data page in Lumen, FGE NexantECA’s gas and LNG scenario platform. Analysts can switch off a route or a whole canal, choose for how long, and see straight away whether the change moves the price.

14
LNG routes in one place, as cards or a table
5
chokepoints, from Suez and Panama to Hormuz
3
route states with clear rules between them
The Problem
The Problem
Shipping chokepoints like Suez or Panama can close overnight, and traders need to know what that means for supply and price. In Lumen, routes could only be switched off one by one inside the Scenario Builder. There was no way to close a canal and every route that uses it, no way to say for how long, and no clear signal of what the change did to the market.
The risk was a scenario that looked fine but carried hidden edits nobody remembered making.
Shipping chokepoints like Suez or Panama can close overnight, and traders need to know what that means for supply and price. In Lumen, routes could only be switched off one by one inside the Scenario Builder. There was no way to close a canal and every route that uses it, no way to say for how long, and no clear signal of what the change did to the market.
The risk was a scenario that looked fine but carried hidden edits nobody remembered making.
The Solution
The Solution
1
Canals as master switches
A Canals bar sits above the routes. Turning Suez off disables every route that transits it, locks those rows with a canal tag and marks them as auto-disabled. Manual and automatic states stay separate, so a route can’t be switched back on while its canal is closed.
1
Canals as master switches
A Canals bar sits above the routes. Turning Suez off disables every route that transits it, locks those rows with a canal tag and marks them as auto-disabled. Manual and automatic states stay separate, so a route can’t be switched back on while its canal is closed.

2
Disable for a set period
Every switch-off asks for a window: until re-enabled, or from one month to another. Routes come back on by themselves when the window ends, so a temporary closure never becomes a permanent change by mistake.
2
Disable for a set period
Every switch-off asks for a window: until re-enabled, or from one month to another. Routes come back on by themselves when the window ends, so a temporary closure never becomes a permanent change by mistake.


3
Show the price impact straight away
After confirming, a toast tells the analyst what the change did. If the route was the marginal source, it shows the price jump at the hub and where the volume went. If not, it says so clearly: no price impact.
3
Show the price impact straight away
After confirming, a toast tells the analyst what the change did. If the route was the marginal source, it shows the price jump at the hub and where the volume went. If not, it says so clearly: no price impact.


Route Logic
Route Logic
Every route can be in one of three states, and the rules between them decide what the analyst is allowed to do. A canal switch always wins over a single route, and every disable window ends with an automatic return to active.
Every route can be in one of three states, and the rules between them decide what the analyst is allowed to do. A canal switch always wins over a single route, and every disable window ends with an automatic return to active.

Price Impact
Price Impact
Closing a route only moves the price if that route was supplying the last, most expensive unit of demand at the hub. Lumen re-solves after every change and tells the analyst which case they are in.
Closing a route only moves the price if that route was supplying the last, most expensive unit of demand at the hub. Lumen re-solves after every change and tells the analyst which case they are in.

Why It Works
Why It Works
🔒
No silent edits
Auto-disabled routes are locked and tagged, so the scenario always shows why a route is off.
🔒
No silent edits
Auto-disabled routes are locked and tagged, so the scenario always shows why a route is off.
⏱️
Temporary by default
Every closure has an end date, which matches how real outages work.
⏱️
Temporary by default
Every closure has an end date, which matches how real outages work.
💡
Impact, not just state
The toast answers the trader’s real question: did this move the price?
💡
Impact, not just state
The toast answers the trader’s real question: did this move the price?
🧭
One pattern everywhere
Route, canal and master-switch modals share the same disable-window control.
🧭
One pattern everywhere
Route, canal and master-switch modals share the same disable-window control.
How I Built It
How I Built It
I worked from the product tickets and feedback rounds on the routing page and mapped every state a route can be in before drawing screens. Then I designed the grid and table views, the Canals bar, the disable-window modals and the price-impact toasts as one system, with notes on every screen for the development team.
I worked from the product tickets and feedback rounds on the routing page and mapped every state a route can be in before drawing screens. Then I designed the grid and table views, the Canals bar, the disable-window modals and the price-impact toasts as one system, with notes on every screen for the development team.
Conclusion
Closing Suez in Lumen is now one switch with a clear end date and a clear answer about price. Analysts can test real-world disruptions in minutes without leaving hidden changes behind in their scenarios.

