When LNG Spreads Undercut SRMC: Acting Inside the 45–60 Day Window

Opening Insight

LNG margins are shifting from a capacity game to a spread game, defined by differentials to short‑run marginal cost (SRMC) inside a 45–60 day notice window. As TTF/JKM–Henry Hub converges toward the ~$1.0–$1.5 per MMBtu SRMC band, a sustained sub‑$1.0 signal across that horizon inverts cancel/divert economics. If actions trail the clock, contractual lags hard‑code negative netbacks into realized P&L. The broken assumption is that high run rates equal steady netbacks. The emerging reality is a Henry Hub‑tethered global price stack with moving demand floors, tighter optionality, and firmer balances as U.S. linkages deepen and power demand (including data centers) rises. This post quantifies the cost of missing SRMC triggers across scheduling, hedging, credit/collateral, compliance, data, and operations; then shows how a rules‑based, Differential‑Driven Operating Model turns spread signals into on‑time throttle/divert/cancel and maintenance choices. We outline Arcelian’s control‑plane blueprint—canonical SRMC data, rules‑as‑software, ETRM/credit integration, governance, KPIs—and a pragmatic modernization path with event‑driven interoperability and agentic AI under strict controls. The outcome is auditable execution that synchronizes utilization, P&L timing, and exposure with the underlying economics. We start with mechanics and the operative 45–60 day trigger in Context and Analysis.

Costs of Ignoring SRMC Triggers

If you ignore SRMC versus hub differentials—and the 45–60 day notice clock—the market moves first and your utilization moves late. A clean trigger like TTF/JKM–Henry Hub < ~$1.0 for 45–60 days becomes hard cost once the window closes.

• LNG scheduling: Missed notices lock in unprofitable liftings for 45–60 days; even volumes above the ~80% floor stay on the water, so throttle/divert hits late—the same lag dynamic that preceded >150 U.S. cancellations in 2020.
• Derivatives: Hedges follow stale spreads; VaR/stress underweights the Henry Hub linkage, so basis risk spikes as TTF/JKM–Henry Hub compresses toward SRMC.
• ETRM and risk: Optionality lives outside ETRM; diversion rights, $0.15 cancel/$0.05 divert fees, and notice rules aren’t captured, distorting P&L that later snaps back when flows shift 45–60 days later.
• Credit/collateral: Models ignore floors and notice‑period risk; collateral lags spread shocks, stressing liquidity when netbacks flip (e.g., $0.80 vs $1.20 SRMC = −$0.40; −$0.55 after penalty).
• Compliance/surveillance: Cancellation governance isn’t codified; price‑basis rationales and approvals go thin, leaving audit trails incomplete.
• Data/IT: No canonical SRMC view; feedgas, liquefaction fuel/use, freight, and regas aren’t reconciled, obscuring the ~$1.0–$1.5 per MMBtu signal.
• Commercial/operations: Maintenance isn’t pulled into soft‑spread windows; schedules chase outdated

economics; roles and thresholds don’t reflect the 45–60 day lag. Bottom line: every day between signal and action leaks margin into P&L and collateral.

Results of a Rules‑Based Model

When SRMC, hub differentials, and contract mechanics operate in one rules‑based model, trading shifts from intuition to controlled execution. Teams act inside the 45–60 day notice window on codified triggers—like TTF/JKM–Henry Hub < ~$1.0 versus SRMC ≈ $1.0–$1.5 per MMBtu—so utilization, risk, and cash align with the economics. The effect is faster, safer, more profitable, and more resilient operations.

• Accelerate throttle, divert, cancel, or maintain as soon as Netback = hub price − SRMC turns negative across the 45–60 day horizon, preventing missed notices and landing actions in P&L on time.
• Convert marginal‑cost clarity into lower operating spend by prioritizing lanes with positive netbacks and advancing maintenance into soft‑spread windows when differentials compress below SRMC.
• Align scheduling to contractual lags so physical utilization adjusts predictably with issued notices, cutting schedule drift and cargo rework as spreads move.
• Clarify P&L and risk as ETRM captures diversion rights, utilization floors (~80% of ACQ), and fees (e.g., $0.15 cancel, $0.05 divert), replacing spreadsheet optionality and reducing misattribution.
• Strengthen credit and collateral by linking spread thresholds and utilization floors to exposure, trimming collateral whiplash when markets shift inside the notice window.
• Integrate the front–middle–back with event‑driven workflows and cleaner trade capture, reducing settlements variance and eliminating swivel‑chair handoffs.

Differential‑Driven Operating Model

Adopt the Differential‑Driven Operating Model. It marries SRMC‑versus‑hub signals with the 45–60 day notice window so throttle, divert, cancel, or maintain decisions are issued on time and show up in P&L and operations when utilization adjusts. Anchored on SRMC ≈ $1.0–$1.5 per MMBtu and a trigger band where TTF/JKM–Henry Hub sits below ~$1.0 for 45–60 days, it replaces guesswork with codified control.

• SRMC‑to‑spread control plane: compare forward TTF/JKM–Henry Hub to SRMC within the 45–60 day window; when spreads stay <$1.0 for 45–60 days, queue cancel/divert/maintain within ~80% ACQ floors.
• Rules‑as‑software with notice windows: encode thresholds, diversion rights, penalties, and 45–60 day lags; lock notices so actions meet laycans.
• Canonical SRMC data layer: fuse feedgas curves, liquefaction fuel/use (~10–15%), freight (~$0.5–$0.9), regas/port (~$0.1–$0.3), and hub marks; standardize netback math.
• Event‑driven integration across ETRM/risk/credit/settlements: stream decisions into trading, shipping, risk, finance, and settlements; trigger credit limit recalcs on counterparty changes and cut P&L drift.

Forecasting, Optimization, and Agentic AI

• Forecast differentials and demand response.
• Agents watch spreads, freight, and weather.
• Flag soft‑spread windows .
• Draft maintenance/diversions.
• Simulate P&L and collateral.

Governance and Decision Rights

• Clarify who calls throttle/divert/cancel.
• Run a 24/7 cadence on thresholds and 45–60 day windows.
• Tie KPIs to SRMC‑versus‑hub execution.

Arcelian Control Plane Blueprint

Arcelian turns SRMC‑versus‑hub signals and 45–60 day notice mechanics into a rules‑driven control plane that protects margins and aligns utilization.

By standardizing SRMC and contract terms, and codifying the trigger band ( TTF/JKM–Henry Hub < ~$1.0 for 45–60 days), actions become predictable and land in P&L when cargoes move. Throttling, diversions, and maintenance are synchronized to the notice lag and utilization floors, not left to ad‑hoc judgment.

Architecture and Control Plane

• A canonical SRMC/data model fusing feedgas curves with basis ($0.1–$0.3), liquefaction fuel/use (10–15%, often modeled as ~115% of feedgas), freight ($0.5–$0.9), and regas/port ($0.1–$0.3), yielding ~$1.0–$1.5 per MMBtu while excluding sunk tolling (~$2.5).
• Rules‑as‑software encode thresholds ( TTF/JKM–Henry Hub < ~$1.0 for 45–60 days ), diversion rights, notice windows, and ~80% utilization floors.
• Contract intelligence refactors trade capture in ETRM so optionality and lags flow through P&L, risk, and settlements.
• API/event‑driven integration streams decisions into ETRM, shipping, risk, and finance, and triggers credit limit recalcs when ownership changes alter counterparty risk; outputs route to risk, credit, shipping, and settlements for execution.

Decision Sequence and Governance

• Calculate Netback ≈ Hub price − SRMC on forward spreads inside the notice horizon.
• Apply penalties/fees (e.g., $0.15 per MMBtu for cancels, $0.05 for diversions) and check the ~80% volume floor and laycan constraints.
• Verify duration across the 45–60 day window.
• Choose cancel/divert/maintain where effective netbacks and floors allow.
• Lock by issuing notices so utilization reflects decisions with the contractual lag.
• Model governance challenges spread forecasts and rule parameters; compliance and surveillance provide audit‑ready trails of thresholds, overrides, and actions.

Roadmap

• Run a 6‑week Differential Readiness Diagnostic.
• Map SRMC data sources.
• Extract the top 10 clauses (diversion, penalties, cancellation) into executable rules.
• Stand up streaming integration to ETRM and credit.
• Execute a stress scenario: TTF/JKM–Henry Hub < $1.0 for 60 days to validate cancel/divert timing and collateral impacts.

Operating Model and Roles

• Establish clear decision rights across front–middle–back office—trading, scheduling, risk, and credit own throttle/divert/cancel choices; settlements, data/IT, and compliance ensure capture, lineage, and surveillance.
• Run a 24/7 cadence where ops, risk, and trading review.

thresholds and 45–60 day windows together; align training and incentives to optionality management, not just throughput.

KPIs and Trade‑offs

Track and manage performance using the following LNG optionality KPIs:

• P&L tied to SRMC‑versus‑hub execution
• Utilization alignment to the notice lag
• Credit/collateral responsiveness to spread shocks
• Settlements variance
• Risk attribution clarity as ETRM reflects true optionality

Manage explicit trade‑offs with discipline:

• Optionality versus ~80% utilization floors
• Basis/hedge alignment to avoid amplifying basis risk
• Freight volatility that can swing effective SRMC—ensuring rules stay disciplined even as bunker costs jump

Executive LNG FAQs

What triggers cancel/divert notices?

Watch TTF/JKM–Henry Hub vs SRMC inside the 45–60 day notice window. If the spread stays below ~$1.0 for 45–60 days and Netback ≈ Hub price − SRMC is negative across that horizon, issue cancel or divert notices so utilization adjusts with the lag. Prioritize throttle, diversion, or cancellation based on physical constraints and destination options.

How should we set SRMC and netback guardrails?

Use a live SRMC band of roughly $1.0–$1.5 per MMBtu (feedgas, liquefaction fuel/use, freight, regas; tolling excluded). Compute forward netbacks in the notice window and act when they turn negative; update freight with live quotes. Encode the trigger band—TTF/JKM–Henry Hub < ~$1.0 for 45–60 days—so decisions are automatic.

How do floors and fees change the action?

Respect utilization floors around 80% of ACQ; only volumes above the floor can be canceled. Include penalties and admin fees: for example, $0.15 per MMBtu to cancel and $0.05 for a diversion, and select the path with the best effective netback. When Asia netback is positive after fees, diversion beats canceling where shipping and laycans allow.

What are the ETRM, credit, and governance moves?

Capture diversion rights, penalties, and notice windows in ETRM so P&L, risk, and settlements reflect optionality and lags. Link spread thresholds and utilization floors to exposure to avoid collateral shocks when utilization trails prices. Set clear decision rights and a 24/7 cadence across trading, scheduling, risk, and credit to manage the 45–60 day lag.

Operationalize the $1.0 Trigger

As spreads compress, the business depends on whether decisions track SRMC and the TTF/JKM–Henry Hub signal inside the 45–60 day notice window.

When the spread sits below the ~$1.0 per MMBtu SRMC trigger across that horizon, netbacks go negative, cancel/divert economics flip, and utilization only adjusts with the contractual lag—raising the risk of hedging errors, schedule drift, and collateral strain.

The fix is

operational, not heroic: a rules‑based control plane that encodes SRMC, notice windows, and utilization floors; reflects optionality in ETRM; and pushes coordinated throttle/divert/cancel/maintain actions so P&L lands when cargoes move, not just when markets move.

Strategic takeaway: adopt a Differential‑Driven Operating Model that codifies the ~$1.0 trigger and 45–60 day lag into cancel/divert/maintain decisions across trading, risk, scheduling, credit, and settlements.

Implement the Control Plane

Arcelian operationalizes the differential‑driven control plane that links SRMC, TTF/JKM–Henry Hub, and contract mechanics so actions align with economics despite the 45–60 day lag.

• SRMC‑to‑Spread Control Plane: real‑time thresholds for cancel/divert/maintain, embedding 45–60 day notice logic and ~80% utilization floors.
• Contract Intelligence and ETRM Modernization: extract diversion rights and penalties; embed rules‑as‑software so optionality and lags flow through P&L, risk, credit, and settlements.
• Decision Optimization and Forecasting: forecast TTF/JKM–Henry Hub and demand response; optimize routing, freight, and maintenance when spreads compress below SRMC.

Next step: ask us for a 6‑week Differential Readiness Diagnostic—we’ll map your SRMC data sources, extract your top 10 contractual clauses into executable rules, stand up a streaming integration to ETRM and credit, and run a stress scenario—TTF/JKM–Henry Hub < $1.0 for 60 days—so you know exactly when to throttle, divert, or cancel before spreads force the issue.

Process Optimization & Automation: Digital integration & interoperability for the SRMC control plane

A pragmatic modernization strategy starts with a canonical SRMC data product and a rules‑as‑software layer that can drive event‑driven workflows across ETRM, shipping, risk, credit, and settlements. Encode commercial optionality and obligations—notice windows, utilization floors, penalties—so the control plane can translate SRMC‑versus‑hub spread signals into contract‑aware actions that settle cleanly and appear in P&L in sync with physical utilization.

From an ETRM architecture perspective, prioritize an externalized orchestration tier with APIs and streaming (e.g., pub/sub) over point‑to‑point integrations; wrap legacy systems with API façades rather than forcing a full replacement to unlock interoperability early in the roadmap. Key trade‑offs: place the rule engine outside the ETRM for independence and version control, but enforce strong data contracts, schema versioning, idempotency, and replay. Balance latency and determinism—intraday optimization requires sub‑second propagation, yet risk and credit checks must remain authoritative. Maintain a contract‑aware event taxonomy (nominations, curtailments, demurrage, imbalance) so actions can be simulated, approved, and then executed with consistent reference data.

As argued throughout this post, the core move is establishing a control plane that turns SRMC‑versus‑hub signals

into coordinated, auditable actions across front, middle, and back office.

• Sequencing: (1) Canonical SRMC and contract term model; (2) Event broker and reference data services; (3) Rules deployment with shadow mode and A/B testing; (4) Closed‑loop P&L and settlement reconciliation.
• Decision criteria: end‑to‑end latency targets (<500 ms for intraday), 99% STP for eligible events, 100% encoding of contract notice/utilization terms, deterministic rule outcomes, and full lineage/replayability.
• Risks and controls: segregation of duties for rule changes, kill‑switches and circuit breakers, pre‑trade simulation sandboxes, variance monitors for SRMC vs realized margin.
• Role of Agentic AI: propose and test rule changes, enrich events (counterparty risk, credit exposure), and triage exceptions—always mediated by policies and audit, never bypassing the control plane.

Frequently Asked Questions

How do we know when to cancel or divert LNG cargoes under tightening spreads?

Track TTF/JKM–Henry Hub against SRMC inside the 45–60 day notice window. If the spread holds below about $1.0 per MMBtu for 45–60 days and forward Netback = hub price − SRMC is negative across that horizon, issue cancel/divert/maintain notices so utilization adjusts on time. Respect ~80% ACQ floors, include fees (~$0.15 cancel, ~$0.05 divert) and laycan constraints, and choose the path with the strongest effective netback—diversion often wins if Asia/Europe netbacks are positive after fees.

What belongs in a canonical SRMC and netback model for U.S. LNG?

Fuse feedgas curves with liquefaction fuel/use (10–15%, often modeled as ~115% of feedgas), basis ($0.1–$0.3), freight ($0.5–$0.9), and regas/port ($0.1–$0.3). This yields SRMC ≈ $1.0–$1.5 per MMBtu and excludes sunk tolling (~$2.5). Use forward TTF/JKM/Henry Hub marks to compute netbacks within the 45–60 day notice horizon, and keep freight updated with live quotes. Standardize this data so risk, credit, scheduling, and settlements share the same signal.

Where should the rules engine sit relative to ETRM, and how do we integrate without a rip-and-replace?

Place the rule engine outside the ETRM for independence and version control, wrap legacy systems with API façades, and use event streaming (pub/sub) for orchestration. Encode diversion rights, penalties, utilization floors (~80%), and 45–60 day lags as rules that drive cancel/divert/maintain actions. Enforce strong data contracts, schema versioning, idempotency, and full lineage/replay; target <500 ms intraday latency and ~99% STP, with closed-loop P&L and settlement reconciliation.

Trend Watch

SRMC‑driven interoperability is moving from aspiration to operating standard. As the TTF vs Henry Hub spread

and the JKM spread oscillate around the ~$1.0–$1.5 short‑run marginal cost (SRMC) band, firms that digitize notice rules and optionality protect LNG netback economics before P&L gravity takes hold.

The pattern is persistent: TTF/JKM–Henry Hub spread compression inside the 45–60 day notice window pressures LNG utilization rates; without a programmable layer, decisions drift into reactive LNG cargo cancellations and collateral strain.

What’s working now blends technology modernization with process discipline:

• Build a canonical SRMC data product that normalizes feedgas, fuel/use, freight, and regas, so netback equals hub price minus SRMC is computed identically across trading, risk, and credit. This foundation reduces basis risk and anchors credit collateral management to objective triggers.
• Externalize decision logic as rules‑as‑software and stream event‑driven workflows into ETRM modernization via APIs. The SRMC control plane issues cancel/divert/maintain when spreads breach thresholds, creating auditable, deterministic actions that settle cleanly.
• Deploy agentic AI to watch the TTF vs Henry Hub and JKM spreads, freight and bunker volatility, and weather; draft actions and test scenarios, but gate execution through policy and approvals.

Strategic signal: interoperability is a margin defense .

Firms that encode the 45–60 day mechanics, utilization floors (~80% ACQ), and penalty math into an integrated control plane translate spread compression into timely, auditable execution—stabilizing netbacks, dampening basis shocks, and turning modernization into measurable cash protection.

Closing Insight

Compression is no longer a headline risk; it’s an operating condition. Advantage now accrues to LNG portfolios that industrialize SRMC‑versus‑hub decisioning inside the 45–60 day notice window—encoding utilization floors, penalties, and diversion rights as rules that flow through ETRM, risk, and credit.

With a canonical SRMC data product and an externalized control plane, basis and collateral shocks are contained, maintenance is pulled into soft‑spread windows, and agentic AI can surveil TTF/JKM–Henry Hub, freight, and weather without bypassing governance. The strategic move is clear: treat interoperability as a risk asset—codify the ~$1.0 trigger , simulate netbacks and collateral, and lock notices on cadence—so spread volatility becomes monetizable optionality rather than P&L drift. Firms that execute this blueprint won’t just defend margins; they’ll set the pace for resilient, AI‑enabled LNG operations as U.S. linkages deepen.

Partner with Arcelian

Volatile TTF/JKM–Henry Hub spreads and the 45–60 day notice clock reward operators who turn SRMC signals into codified, contract‑aware actions. Arcelian partners with LNG leaders to stand up the differential‑driven control plane—canonical SRMC data, rules‑as‑software for diversion/cancel thresholds, and ETRM/credit integration—so

Audit-Grade Readiness for Utilization, P&L, and Collateral

utilization, P&L, and collateral respond on time and with audit-grade discipline .

Connect with our team to explore a focused, 6‑week Differential Readiness Diagnostic for your portfolio: we’ll

• benchmark SRMC accuracy
• encode priority clauses
• pressure‑test a <$1.0 spread scenario
• quantify cash and risk impacts

—so you can decide where AI and modernization deliver measurable protection in the next operating quarter.