What the Isaias Strand Lab Demonstrated — and Why It Matters Beyond the Forecast
Jon W. Hansen, FCIPS · Procurement Insights | Hansen Models™ · 13 October 2026
Across more than 2,000 hours of similar-type, live, real-world test labs, output accuracy has averaged 91%. Multiple factors contribute to that result. This post examines one of them: using Strand Commonality™ to think through dependencies before an event.
When Hurricane Isaias was still a tropical depression churning through the Gulf of Mexico, the weather services were doing what they always do. They were tracking the path. They were modeling the wind speed. They were forecasting which counties would see the worst of it.
That is exactly the right information if your job is emergency management or evacuation planning. Weather forecasts are relevant to fuel operations. They are not, on their own, sufficient for the organizations whose job is keeping fuel flowing to a fleet, a cold chain, a manufacturing operation, or a distribution network that depends on Gulf Coast diesel supply.
Those organizations needed a different question. Not where will the storm go, but which connections does your operation depend on — and what happens to those connections when the storm crosses them?
That is the question Strand Commonality™ asks. And on 8 October 2026, one day before Isaias made landfall as a Category 2 hurricane near Destin, Florida, it was the question the Isaias Strand Lab put on the public record.
What Triggered the Lab
On 8 October, supply chain risk specialist David Shillingford posted a map on LinkedIn. It was a Fox Weather image showing the multiple predicted forecast tracks for Tropical Depression 9 overlaid against the position of Gulf oil rigs and diesel refineries. Shillingford shared it because it was the storm track — that is what it was to the source that produced it, and that is how his audience read it.
David Shillingford’s post brought the exposure into view. Reading that image through Strand Commonality™ produced a different question: not simply where the storm might travel, but which operating dependencies its passage could affect.
That is precisely the point. The image did not change. What changed was the lens. It was the Human Orchestrator using Strand Commonality™ — what he brought to that image was a different lens entirely: those converging lines are strand crossings. The outcome will be decided where they meet. Same image. Different question.
That is how Strand Commonality™ works in practice. The domain specialist surfaces the signal. The framework reads it differently. The value is in the reinterpretation, not in any special knowledge either party brought to the image.
Just as an orchestration audit trail exposes how multi-model decisions are composed across hidden seams, Strand Commonality™ exposes how operational outcomes are composed across the dependencies a sequential map would not show. Both reject opacity in favor of inspectable, structured reality.
What the Lab Said on October 8th
The 8 October Procurement Insights post, The Storm Is One Strand. The Outcome Is Decided Where It Crosses the Others, made seven statements before landfall. Six carry documented public provenance — the post itself and the same-day animation on X (@piblogger1) and LinkedIn (Hansen Models). One was an internal corridor estimate recorded by Model 5. Attribution for each statement is recorded in the lab’s baseline.
The post’s central claim was not a price forecast or a track prediction. It was a framework observation: a refinery can come through a hurricane undamaged and still stop shipping — because the grid is down or a terminal is closed.
Alongside that central claim, the lab recorded six statements about the recovery sequence: power restoring in steps before every other dependency, recovery estimates running optimistic, policy growing more active, prices moving, and the offshore feedstock shutdown creating downstream pressure.
The original statements were recorded before landfall. The formal baseline was locked on 10 October — after landfall — so that later corrections and scoring decisions would remain visible and the record could not be altered once outcomes were known. The reckoning happened Monday evening, 12 October, three days after the storm.
What the Lab Found, Day by Day
October 8 — Before landfall: The framework question was on the record. A refinery can survive the storm and still stop shipping. Do you know which connections your fuel supply depends on? That question was available to every buyer, operator, and risk officer who read it. The pre-event window was open.
October 9 — Landfall, Category 2, near Destin: The window for discretionary action began to narrow. The corridor location was consistent with the internal estimate.
October 10 — Day 1 after landfall: The baseline was locked. Power was out for approximately 390,000 customers. Offshore production at 71.5% shut-in — approximately 1.45 million barrels per day offline. Ports at Condition YANKEE. Refinery status: the lab had not yet captured reliable confirmation. The strand everyone could watch — power — was the only one being reported. The strands that decide fuel supply were not yet in the public record.
October 11 — Day 2: Power recovering in county-by-county steps. FPL set a Monday target of 95% restoration. Offshore production beginning to ease. Port status, refinery status, and diesel prices all absent from the record. The lab’s interim finding: the gap in the record is itself a finding. A plan built on rapid recovery was a plan built on a gap, not on evidence.
October 12 — Day 3, the reckoning: FPL downgraded Monday’s target from 95% to 85%. At noon, the reported figure was 70% — against an 85% end-of-day target. By end of day, Okaloosa County was essentially complete; Escambia and Santa Rosa delayed to Tuesday. FPL had revised its estimate before the day closed. Offshore production: MMA official figures confirmed 29.63% still shut in at noon. BP, Shell, and Chevron reported minimal damage and restoring operations.
October 13 — Tuesday morning: David Shillingford posted an update on his original LinkedIn post — the same thread that had triggered this lab. Citing ICIS, he reported: Chevron confirmed Pascagoula refinery weathered the storm without damage and continues to supply customers. Ports from Gulfport to Panama City had reopened Saturday, 10 October. The MMA official figure confirmed less than 30% of oil production and 25% of gas production still shut in.
Chevron’s statement answers one of the questions the 8 October post asked readers to investigate: what was the actual operating condition of the facility and its supporting connections? The refinery survived the storm. Whether supply to specific buyers was disrupted during the period when ports and grid access were restricted remains a question for individual organizations to document. The framework accepts the answer the evidence gives.
What This Means for the People Who Needed It Most
The lab’s value was not equal across all readers, and it was not equal at all points in time. The people who had the most to gain were those who were reading on 8 October, before the storm arrived — and who had the capacity to act on what they read.
Fuel buyers and procurement teams with discretionary capacity had the clearest and most time-sensitive opportunity. On 8 October, the lab named the dependency a sequential map would not show: a refinery can survive the storm and still stop shipping. A buyer with purchasing discretion could have used that question to investigate exposure, confirm continuity of supply, confirm alternate sourcing, or arrange pre-storm positioning before landfall. By Monday morning, the record was full of gaps: refinery status unconfirmed for three days, retail prices unreported, port reopenings not yet in the public record. The pre-event window was worth having.
The lab does not document individual buyer actions or outcomes. What it documents is the question that was available on 8 October — and when it was available.
Fleet operators and logistics managers needed the refinery finding specifically. The lab’s pre-landfall statement — an intact facility does not mean an open supply chain — was addressed by Chevron’s Tuesday confirmation. Pascagoula was intact and continued to supply customers. Whether any specific fleet experienced a supply interruption during the days when ports were closed and grid access was limited is a question each organization can now investigate with the strand map the lab provided.
Cold chain operators and manufacturers with physical restart dependencies needed to know that recovery estimates could run optimistic. FPL’s Monday target was revised before the day closed — from a 95% estimate set before the storm to 85% once damage was assessed, with the hardest-hit areas pushed to Tuesday. A restart plan built around Monday without a contingency window carried a risk the record subsequently confirmed.
C-suite risk officers needed the lab’s central interim finding, which held across all three days: the strand everyone can watch is not a sufficient indicator of supply chain recovery. Power was reported county by county, nearly hour by hour. The strands that decide whether fuel moves were not in the record at all until Tuesday morning. Reading the improving power curve as a proxy for supply recovery was reading the wrong strand. The MMA figures confirmed it: FPL’s revised target was 85% by end of Monday while offshore was still at 29.63% at noon.
Organizations with no alternative sourcing could not change their procurement position before landfall. But the framework question the lab posed on 8 October is the diagnostic they now know they need to answer before the next event. Decisions also remain possible after landfall — what changes is the leverage. Knowing which crossings matter, and knowing that the pre-event window exists, is what the lab was built to demonstrate.
Why the Lens Is Different From the Forecast
On 8 October, there was no shortage of information about Hurricane Isaias. Weather services were tracking the path. Commodity desks were watching the shut-in percentages. Supply chain risk platforms were issuing alerts. Energy analysts were modeling refinery exposure.
All of that information was useful. Our contribution was to make the dependency question explicit and accessible through Strand Commonality™.
Every standard industry source was answering the forecast question: what is going to happen? The Isaias Strand Lab was answering a different one: which connections does your operation depend on, and what happens at those crossings when the storm arrives?
That is not a forecasting question. It is a strand question. It does not require an energy industry expert to ask it. Shillingford shared a Fox Weather graphic because it was the storm track. It was the Human Orchestrator using Strand Commonality™ who read those converging lines as strand crossings and built the lab around that recognition. Same image. Different question.
That is a way of seeing, not a way of forecasting. It asks which strands cross, not which outcome is most likely. And because it begins with the structure of dependencies rather than the probability of outcomes, it identifies the question the buyer needs to ask before the storm arrives — at the moment when the buyer still has room to investigate, choose, and prepare.
That is the operational shift the Hansen Models framework produces. Predicting asks: what is going to happen to us? Thinking in strands asks: how do our dependencies cross, on what clocks do they move, and what leverage do we have before the seam breaks?
What the Lab Illustrates for ARA™ RAM 2025™ Running on SLAP OS™
The Isaias Strand Lab is the first publicly dated, locked-baseline, scored reckoning of the Hansen Models framework applied in an energy disruption context.
The 1998 DND engagement — where the framework was first developed — was a service department, not a procurement department. The observation that shaped the entire operation came from someone examining what the people inside the system could not see because they were each managing their own strand. The technology followed the human observation. It always has.
In 2026, a similar sequence played out in a different setting. The recognition of the strand crossing came before the prediction. The lab was built around that recognition. And the reckoning, scored under locked conditions against publicly dated statements, documented how the method performed outside procurement without prior expertise in energy markets.
Strand Commonality™ is not a procurement tool that scales to other domains. It is a way of seeing that was demonstrated first in a procurement context and has now been illustrated in an energy disruption context, 28 years apart. Whether it scales — meaning whether other practitioners can use the question to identify relevant dependencies, distinguish evidence from assumptions, and improve decisions in their own settings — is the next capability to demonstrate, not an outcome already proved.
ARA™ RAM 2025™ running on SLAP OS™ is the instrument that makes that way of seeing accessible. It cannot replace the Human Orchestrator who recognizes the crossing. It can help anyone who has learned to ask the Strand Commonality™ question apply it more systematically, trace the dependencies more rigorously, and document the reasoning path so that the work can be examined, challenged, and built on.
Scalability is the ability to teach that question. The Isaias Strand Lab is the evidence that the question travels.
The Closing Finding
On Tuesday morning, 13 October, David Shillingford posted an update on the same LinkedIn thread that had triggered this lab five days earlier. The person whose post surfaced the strand crossing supplied the post-event confirmation on the same thread where the crossing was first identified.
The value of the lens is not that every anticipated disruption occurs. It is that people examine the connections they depend on while they still have room to investigate, choose, and prepare — and revise their understanding when the evidence arrives.
The storm is not the risk. The crossings are.
The most valuable capability is not the ability to forecast what the storm will do. It is the ability to see, before the storm arrives, which connections your operation depends on — and to ask the question while you still have room to act on the answer.
Special Note — The Isaias Strand Lab
The complete Isaias Strand Lab record — including the locked baseline, all daily observation records, the full reckoning scorecard, the multimodel panel feedback, and the C-suite lessons — is available to qualifying organizations and practitioners under a signed NDA.
The lab runs 21 pages and documents, in real time and in sequence, exactly how Strand Commonality™ was applied to a live energy market disruption from the pre-event window through the reckoning. It is the kind of record that cannot be reconstructed after the fact — which is the point.
The Storm Is Not the Risk. The Crossings Are.
Posted on October 13, 2026
0
What the Isaias Strand Lab Demonstrated — and Why It Matters Beyond the Forecast
Jon W. Hansen, FCIPS · Procurement Insights | Hansen Models™ · 13 October 2026
Across more than 2,000 hours of similar-type, live, real-world test labs, output accuracy has averaged 91%. Multiple factors contribute to that result. This post examines one of them: using Strand Commonality™ to think through dependencies before an event.
When Hurricane Isaias was still a tropical depression churning through the Gulf of Mexico, the weather services were doing what they always do. They were tracking the path. They were modeling the wind speed. They were forecasting which counties would see the worst of it.
That is exactly the right information if your job is emergency management or evacuation planning. Weather forecasts are relevant to fuel operations. They are not, on their own, sufficient for the organizations whose job is keeping fuel flowing to a fleet, a cold chain, a manufacturing operation, or a distribution network that depends on Gulf Coast diesel supply.
Those organizations needed a different question. Not where will the storm go, but which connections does your operation depend on — and what happens to those connections when the storm crosses them?
That is the question Strand Commonality™ asks. And on 8 October 2026, one day before Isaias made landfall as a Category 2 hurricane near Destin, Florida, it was the question the Isaias Strand Lab put on the public record.
What Triggered the Lab
On 8 October, supply chain risk specialist David Shillingford posted a map on LinkedIn. It was a Fox Weather image showing the multiple predicted forecast tracks for Tropical Depression 9 overlaid against the position of Gulf oil rigs and diesel refineries. Shillingford shared it because it was the storm track — that is what it was to the source that produced it, and that is how his audience read it.
David Shillingford’s post brought the exposure into view. Reading that image through Strand Commonality™ produced a different question: not simply where the storm might travel, but which operating dependencies its passage could affect.
That is precisely the point. The image did not change. What changed was the lens. It was the Human Orchestrator using Strand Commonality™ — what he brought to that image was a different lens entirely: those converging lines are strand crossings. The outcome will be decided where they meet. Same image. Different question.
That is how Strand Commonality™ works in practice. The domain specialist surfaces the signal. The framework reads it differently. The value is in the reinterpretation, not in any special knowledge either party brought to the image.
Just as an orchestration audit trail exposes how multi-model decisions are composed across hidden seams, Strand Commonality™ exposes how operational outcomes are composed across the dependencies a sequential map would not show. Both reject opacity in favor of inspectable, structured reality.
What the Lab Said on October 8th
The 8 October Procurement Insights post, The Storm Is One Strand. The Outcome Is Decided Where It Crosses the Others, made seven statements before landfall. Six carry documented public provenance — the post itself and the same-day animation on X (@piblogger1) and LinkedIn (Hansen Models). One was an internal corridor estimate recorded by Model 5. Attribution for each statement is recorded in the lab’s baseline.
The post’s central claim was not a price forecast or a track prediction. It was a framework observation: a refinery can come through a hurricane undamaged and still stop shipping — because the grid is down or a terminal is closed.
Alongside that central claim, the lab recorded six statements about the recovery sequence: power restoring in steps before every other dependency, recovery estimates running optimistic, policy growing more active, prices moving, and the offshore feedstock shutdown creating downstream pressure.
The original statements were recorded before landfall. The formal baseline was locked on 10 October — after landfall — so that later corrections and scoring decisions would remain visible and the record could not be altered once outcomes were known. The reckoning happened Monday evening, 12 October, three days after the storm.
What the Lab Found, Day by Day
October 8 — Before landfall: The framework question was on the record. A refinery can survive the storm and still stop shipping. Do you know which connections your fuel supply depends on? That question was available to every buyer, operator, and risk officer who read it. The pre-event window was open.
October 9 — Landfall, Category 2, near Destin: The window for discretionary action began to narrow. The corridor location was consistent with the internal estimate.
October 10 — Day 1 after landfall: The baseline was locked. Power was out for approximately 390,000 customers. Offshore production at 71.5% shut-in — approximately 1.45 million barrels per day offline. Ports at Condition YANKEE. Refinery status: the lab had not yet captured reliable confirmation. The strand everyone could watch — power — was the only one being reported. The strands that decide fuel supply were not yet in the public record.
October 11 — Day 2: Power recovering in county-by-county steps. FPL set a Monday target of 95% restoration. Offshore production beginning to ease. Port status, refinery status, and diesel prices all absent from the record. The lab’s interim finding: the gap in the record is itself a finding. A plan built on rapid recovery was a plan built on a gap, not on evidence.
October 12 — Day 3, the reckoning: FPL downgraded Monday’s target from 95% to 85%. At noon, the reported figure was 70% — against an 85% end-of-day target. By end of day, Okaloosa County was essentially complete; Escambia and Santa Rosa delayed to Tuesday. FPL had revised its estimate before the day closed. Offshore production: MMA official figures confirmed 29.63% still shut in at noon. BP, Shell, and Chevron reported minimal damage and restoring operations.
October 13 — Tuesday morning: David Shillingford posted an update on his original LinkedIn post — the same thread that had triggered this lab. Citing ICIS, he reported: Chevron confirmed Pascagoula refinery weathered the storm without damage and continues to supply customers. Ports from Gulfport to Panama City had reopened Saturday, 10 October. The MMA official figure confirmed less than 30% of oil production and 25% of gas production still shut in.
Chevron’s statement answers one of the questions the 8 October post asked readers to investigate: what was the actual operating condition of the facility and its supporting connections? The refinery survived the storm. Whether supply to specific buyers was disrupted during the period when ports and grid access were restricted remains a question for individual organizations to document. The framework accepts the answer the evidence gives.
What This Means for the People Who Needed It Most
The lab’s value was not equal across all readers, and it was not equal at all points in time. The people who had the most to gain were those who were reading on 8 October, before the storm arrived — and who had the capacity to act on what they read.
Fuel buyers and procurement teams with discretionary capacity had the clearest and most time-sensitive opportunity. On 8 October, the lab named the dependency a sequential map would not show: a refinery can survive the storm and still stop shipping. A buyer with purchasing discretion could have used that question to investigate exposure, confirm continuity of supply, confirm alternate sourcing, or arrange pre-storm positioning before landfall. By Monday morning, the record was full of gaps: refinery status unconfirmed for three days, retail prices unreported, port reopenings not yet in the public record. The pre-event window was worth having.
The lab does not document individual buyer actions or outcomes. What it documents is the question that was available on 8 October — and when it was available.
Fleet operators and logistics managers needed the refinery finding specifically. The lab’s pre-landfall statement — an intact facility does not mean an open supply chain — was addressed by Chevron’s Tuesday confirmation. Pascagoula was intact and continued to supply customers. Whether any specific fleet experienced a supply interruption during the days when ports were closed and grid access was limited is a question each organization can now investigate with the strand map the lab provided.
Cold chain operators and manufacturers with physical restart dependencies needed to know that recovery estimates could run optimistic. FPL’s Monday target was revised before the day closed — from a 95% estimate set before the storm to 85% once damage was assessed, with the hardest-hit areas pushed to Tuesday. A restart plan built around Monday without a contingency window carried a risk the record subsequently confirmed.
C-suite risk officers needed the lab’s central interim finding, which held across all three days: the strand everyone can watch is not a sufficient indicator of supply chain recovery. Power was reported county by county, nearly hour by hour. The strands that decide whether fuel moves were not in the record at all until Tuesday morning. Reading the improving power curve as a proxy for supply recovery was reading the wrong strand. The MMA figures confirmed it: FPL’s revised target was 85% by end of Monday while offshore was still at 29.63% at noon.
Organizations with no alternative sourcing could not change their procurement position before landfall. But the framework question the lab posed on 8 October is the diagnostic they now know they need to answer before the next event. Decisions also remain possible after landfall — what changes is the leverage. Knowing which crossings matter, and knowing that the pre-event window exists, is what the lab was built to demonstrate.
Why the Lens Is Different From the Forecast
On 8 October, there was no shortage of information about Hurricane Isaias. Weather services were tracking the path. Commodity desks were watching the shut-in percentages. Supply chain risk platforms were issuing alerts. Energy analysts were modeling refinery exposure.
All of that information was useful. Our contribution was to make the dependency question explicit and accessible through Strand Commonality™.
Every standard industry source was answering the forecast question: what is going to happen? The Isaias Strand Lab was answering a different one: which connections does your operation depend on, and what happens at those crossings when the storm arrives?
That is not a forecasting question. It is a strand question. It does not require an energy industry expert to ask it. Shillingford shared a Fox Weather graphic because it was the storm track. It was the Human Orchestrator using Strand Commonality™ who read those converging lines as strand crossings and built the lab around that recognition. Same image. Different question.
That is a way of seeing, not a way of forecasting. It asks which strands cross, not which outcome is most likely. And because it begins with the structure of dependencies rather than the probability of outcomes, it identifies the question the buyer needs to ask before the storm arrives — at the moment when the buyer still has room to investigate, choose, and prepare.
That is the operational shift the Hansen Models framework produces. Predicting asks: what is going to happen to us? Thinking in strands asks: how do our dependencies cross, on what clocks do they move, and what leverage do we have before the seam breaks?
What the Lab Illustrates for ARA™ RAM 2025™ Running on SLAP OS™
The Isaias Strand Lab is the first publicly dated, locked-baseline, scored reckoning of the Hansen Models framework applied in an energy disruption context.
The 1998 DND engagement — where the framework was first developed — was a service department, not a procurement department. The observation that shaped the entire operation came from someone examining what the people inside the system could not see because they were each managing their own strand. The technology followed the human observation. It always has.
In 2026, a similar sequence played out in a different setting. The recognition of the strand crossing came before the prediction. The lab was built around that recognition. And the reckoning, scored under locked conditions against publicly dated statements, documented how the method performed outside procurement without prior expertise in energy markets.
Strand Commonality™ is not a procurement tool that scales to other domains. It is a way of seeing that was demonstrated first in a procurement context and has now been illustrated in an energy disruption context, 28 years apart. Whether it scales — meaning whether other practitioners can use the question to identify relevant dependencies, distinguish evidence from assumptions, and improve decisions in their own settings — is the next capability to demonstrate, not an outcome already proved.
ARA™ RAM 2025™ running on SLAP OS™ is the instrument that makes that way of seeing accessible. It cannot replace the Human Orchestrator who recognizes the crossing. It can help anyone who has learned to ask the Strand Commonality™ question apply it more systematically, trace the dependencies more rigorously, and document the reasoning path so that the work can be examined, challenged, and built on.
Scalability is the ability to teach that question. The Isaias Strand Lab is the evidence that the question travels.
The Closing Finding
On Tuesday morning, 13 October, David Shillingford posted an update on the same LinkedIn thread that had triggered this lab five days earlier. The person whose post surfaced the strand crossing supplied the post-event confirmation on the same thread where the crossing was first identified.
The value of the lens is not that every anticipated disruption occurs. It is that people examine the connections they depend on while they still have room to investigate, choose, and prepare — and revise their understanding when the evidence arrives.
The storm is not the risk. The crossings are.
The most valuable capability is not the ability to forecast what the storm will do. It is the ability to see, before the storm arrives, which connections your operation depends on — and to ask the question while you still have room to act on the answer.
Special Note — The Isaias Strand Lab
The complete Isaias Strand Lab record — including the locked baseline, all daily observation records, the full reckoning scorecard, the multimodel panel feedback, and the C-suite lessons — is available to qualifying organizations and practitioners under a signed NDA.
The lab runs 21 pages and documents, in real time and in sequence, exactly how Strand Commonality™ was applied to a live energy market disruption from the pre-event window through the reckoning. It is the kind of record that cannot be reconstructed after the fact — which is the point.
To request access, contact: HPT@hansenprocurement.com
Truth Is Believing. Accuracy Is Knowing. Outcome Is Proof.™
-30-
Share this:
Like this:
Related