<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Paul Salmon on Medium]]></title>
        <description><![CDATA[Stories by Paul Salmon on Medium]]></description>
        <link>https://medium.com/@paulrobertsalmon?source=rss-f93de0da4b8f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dZt3B_62R0mXPvdk6PlPSw@2x.jpeg</url>
            <title>Stories by Paul Salmon on Medium</title>
            <link>https://medium.com/@paulrobertsalmon?source=rss-f93de0da4b8f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:04:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paulrobertsalmon/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From Logistikos to Logistics: Why Supply Chains Must Become More Scientific]]></title>
            <link>https://medium.com/@paulrobertsalmon/from-logistikos-to-logistics-why-supply-chains-must-become-more-scientific-d4e7bb55d9f0?source=rss-f93de0da4b8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4e7bb55d9f0</guid>
            <dc:creator><![CDATA[Paul Salmon]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 06:09:30 GMT</pubDate>
            <atom:updated>2026-04-24T06:09:30.582Z</atom:updated>
            <content:encoded><![CDATA[<p>By Paul R Salmon FCILT</p><p>The word logistics is widely believed to trace back to the Greek term logistikos (λογιστικός), meaning skilled in calculation, practical reasoning, and the art of reckoning. It is closely associated with logos – logic, order, structured thought.</p><p>That origin should give every modern supply chain leader pause.</p><p>Because if logistics was born from the language of reasoning, mathematics, and structured judgement, why do so many organisations still treat it as a reactive support activity rather than a disciplined science?</p><p>Why, in an age of artificial intelligence, predictive analytics, automation, and digital twins, are too many supply chains still being run on instinct, habit, and spreadsheets held together by hope?</p><p>This is not merely a philosophical question. It is a commercial, operational, and national resilience issue.</p><p>We Mistook Movement for Mastery</p><p>Across many sectors, logistics is still narrowly interpreted as:</p><ul><li>transport management</li><li>* warehousing</li><li>* procurement chasing</li><li>* stock counting</li><li>* dispatch activity</li><li>* expediting shortages</li><li>* firefighting delays</li></ul><p>All of these functions matter. But they are outputs of logistics – not the full discipline itself.</p><p>True logistics is the science of synchronising resources, time, capacity, demand, risk, and flow under constraints.</p><p>It should be as analytical and evidence-led as finance, engineering, or operations research.</p><p>Yet many organisations continue to manage supply chains through fragmented ownership models, legacy processes, and decisions based more on experience than evidence.</p><p>Experience matters. But experience without data can become nostalgia.</p><p>What Scientific Supply Chains Look Like</p><p>A scientific supply chain does not rely solely on gut feel. It uses measurable inputs, tested assumptions, and repeatable methods.</p><p>That means asking better questions:</p><ul><li>What service level are we trying to achieve, and at what cost?</li><li>* What probability of stockout is acceptable?</li><li>* Which suppliers create the greatest systemic risk?</li><li>* Where is inventory actually needed versus historically held?</li><li>* What is the true cost of delay to the end customer?</li><li>* Which 20% of SKUs create 80% of operational pain?</li><li>* How resilient is the network under disruption scenarios?</li></ul><p>These are not theoretical questions. They are board-level questions.</p><p>Where Science Should Already Be Standard</p><p>Demand Forecasting</p><p>Forecasting should use statistical methods, pattern recognition, seasonality modelling, and scenario planning.</p><p>Instead, many organisations still anchor forecasts on optimism, politics, or last year plus 5%.</p><p>Inventory Management</p><p>Stock levels should be based on variability, lead time uncertainty, criticality, and target availability.</p><p>Instead, inventory is often set by precedent:</p><p>“We’ve always carried six months of stock.”</p><p>Warehousing and Flow</p><p>Warehouse design should consider slotting science, travel paths, ergonomic data, pick velocity, and throughput modelling.</p><p>Instead, layouts often reflect historical convenience rather than engineered flow.</p><p>Supplier Risk</p><p>Supplier assurance should measure financial health, geopolitical exposure, capacity constraints, dependency risk, and recovery capability.</p><p>Instead, risk reviews can become annual paperwork exercises.</p><p>Performance Management</p><p>Metrics should reveal root causes, not hide them.</p><p>Measures such as:</p><ul><li>perfect order rate</li><li>* forecast accuracy</li><li>* fill rate</li><li>* right condition fulfilment</li><li>* damage rates</li><li>* logistics delay time</li><li>* supplier OTIF</li><li>* expedite spend</li><li>* cash-to-cash cycle time</li></ul><p>should be core management tools, not dashboard wallpaper.</p><p>Why We Still Lag Behind</p><p>If the case for scientific logistics is so obvious, why does progress remain slow?</p><ol><li>Success Is Quiet</li></ol><p>When supply chains work, nobody notices. Products arrive, shelves stay full, operations continue.</p><p>Because success is invisible, investment is often delayed until failure becomes public.</p><p>2. Functions Remain Siloed</p><p>Planning, procurement, warehousing, transport, finance, engineering, and customer operations often operate with different priorities and disconnected data.</p><p>Science struggles in fragmented systems.</p><p>3. Data Quality Is Poor</p><p>Even advanced analytics fail when master data is inaccurate, lead times are fictional, or stock records cannot be trusted.</p><p>Garbage in, garbage out remains undefeated.</p><p>4. Professional Status Has Lagged</p><p>Many organisations still view supply chain as a support function rather than a strategic profession.</p><p>That mindset suppresses investment in capability, chartership, analytical training, and leadership development.</p><p>5. Firefighting Feels Productive</p><p>A team resolving daily crises can appear busy and committed.</p><p>But constant expediting is often evidence of system failure, not operational excellence.</p><p>Defence and National Resilience Lessons</p><p>The consequences become even clearer in national defence.</p><p>Equipment often spends less time unavailable due to engineering faults than leaders assume. Delays can stem from:</p><ul><li>awaiting spare parts</li><li>* poor demand signals</li><li>* slow approvals</li><li>* repair queues</li><li>* transport bottlenecks</li><li>* data mismatch</li><li>* contract lag</li><li>* misplaced stock</li></ul><p>That means operational weakness may be created not on the battlefield, but in the supply chain.</p><p>The same lesson applies commercially.</p><p>Retailers lose customers through stockouts. Manufacturers lose output through shortages. Hospitals lose capacity through delayed consumables. Infrastructure firms lose time through missing components.</p><p>Supply chain science is not optional efficiency – it is performance assurance.</p><p>What Needs to Change</p><p>To honour the true spirit of logistikos, organisations should pursue five practical shifts.</p><ol><li>Elevate Supply Chain as a Strategic Discipline</li></ol><p>Give supply chain leadership a stronger voice at executive level.</p><p>2. Invest in Analytical Capability</p><p>Build skills in statistics, modelling, forecasting, optimisation, and systems thinking.</p><p>3. Improve Data Foundations</p><p>Without trusted item, supplier, inventory, and demand data, transformation stalls.</p><p>4. Measure What Matters</p><p>Replace vanity metrics with decision-grade indicators.</p><p>5. Simulate Before Crisis</p><p>Use scenario modelling and digital twins to test resilience before disruption occurs.</p><p>A New Definition for a New Era</p><p>Perhaps it is time to redefine logistics for the modern boardroom:</p><p>Logistics is applied reasoning that turns uncertainty into availability.</p><p>That is far more powerful than the outdated image of trucks and warehouses alone.</p><p>Final Thought</p><p>The Greeks gave us a clue thousands of years ago.</p><p>If logistikos meant calculation, judgement, and reasoned action, then logistics was always intended to be scientific.</p><p>We simply forgot.</p><p>The organisations that rediscover that truth first will not just move goods faster.</p><p>They will outperform competitors, withstand shocks, and win where others stall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*FwjCSKAaIPEXEQuLK5gnoQ@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4e7bb55d9f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“If a Relationship Is to Work, There Must Be Transparency — And in Defence, That Transparency Must…]]></title>
            <link>https://medium.com/@paulrobertsalmon/if-a-relationship-is-to-work-there-must-be-transparency-and-in-defence-that-transparency-must-494aefa77ff3?source=rss-f93de0da4b8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/494aefa77ff3</guid>
            <dc:creator><![CDATA[Paul Salmon]]></dc:creator>
            <pubDate>Thu, 07 Aug 2025 22:34:19 GMT</pubDate>
            <atom:updated>2025-08-07T22:37:17.805Z</atom:updated>
            <content:encoded><![CDATA[<h3>“If a Relationship Is to Work, There Must Be Transparency — And in Defence, That Transparency Must Come in the Form of Data”</h3><p>Posted by</p><p><a href="https://supplychaincouncil.org.uk/author/admin/">Paul Salmon</a></p><p>August 5, 2025</p><p>Introduction: The Foundations of Trust</p><p>In every relationship — whether between individuals, organisations, or governments — the foundation is trust. And trust, particularly in complex operational environments, is built on transparency.</p><p>In the world of Defence logistics and supply chains, this transparency doesn’t come through speeches or strategic intent alone. It comes through data.</p><p>Data is the language of modern partnerships. It drives decision-making, informs risk, enables planning, and allows stakeholders to align. Without data, trust becomes assumption. Without shared data, collaboration becomes friction.</p><p>In Defence, where readiness and responsiveness are paramount, we can no longer afford that friction. And yet, despite years of progress, too many of our relationships between Defence and industry remain transactional. Contracts over communication. Delivery over dialogue.</p><p>It’s time for that to change.</p><p>Where the Blame Often Falls</p><p>When supply chain performance dips — when spare parts don’t arrive, when lead times extend, when costs spiral — the instinctive response is to ask: What went wrong? Often followed closely by: Who’s to blame?</p><p>More often than not, attention turns to the supplier.</p><p>“They failed to forecast.” “They didn’t anticipate demand.” “Their lead times have slipped.”</p><p>But blaming the supplier misses the point. Because more often than not, the root cause isn’t poor performance — it’s poor visibility.</p><p>And that raises a far more important question:</p><p>How much of the right data have we actually shared with them?</p><p>Did we provide accurate, up-to-date usage data?</p><p>Did we share operational patterns, surge plans, or demand volatility?</p><p>Did we flag known obsolescence timelines or maintenance bottlenecks?</p><p>Did we model the effects of right-sizing fleets, or forced availability rates?</p><p>If the answer to any of those is “no” or “not reliably,” then we have to be honest: the fault might not lie with the supplier. It might lie with us.</p><p>Flying Blind: When Industry Doesn’t Have the Data</p><p>Industry partners are not mind-readers. They’re not embedded in every squadron, unit, ship, or depot. They don’t see what happens to platforms on exercise, or know when short-notice surge operations throw inventory plans off-course.</p><p>They rely on Defence to provide that insight.</p><p>And yet, despite that dependency, many suppliers are still expected to operate with outdated, incomplete, or non-existent data from their customer — UK Defence.</p><p>Without that data, forecasts become guesswork. Inventory buffers become bloated — or too thin. Availability becomes fragile. Readiness suffers.</p><p>And when readiness suffers, people suffer.</p><p>This isn’t an abstract issue. This is about ensuring critical equipment is available for our people when they need it. Not delayed. Not broken. Not stuck in transit.</p><p>Forecasting Failure Is a Symptom, Not the Root Cause</p><p>It’s important to recognise that poor forecasting isn’t always a result of bad practice — it’s often a result of bad data. Or no data. Or data that Defence had, but didn’t share.</p><p>When suppliers don’t have access to:</p><p>Demand drivers, Repair loop feedback, Usage profiles, Force generation plans, Stock policies or batch run-downs,</p><p>… then forecasting becomes impossible.</p><p>And when forecasting becomes impossible, you don’t get availability — you get variability. That’s not resilience. That’s risk.</p><p>What Shared Data Actually Looks Like</p><p>So, what does good data transparency look like in practice?</p><p>It means a culture shift — from hoarding to helping. From control to collaboration.</p><p>Specifically, it means Defence sharing:</p><p>Planned fleet utilisation (hours flown, miles driven, duty cycles), Obsolescence forecasts and product lifecycles, Operational demand surges (and their likelihood), Maintenance planning schedules, Historical usage trends, and Failure rate data by component and configuration.</p><p>And in return, industry sharing:</p><p>Lead time variability, Supplier chain risk indicators, Parts availability trends, Production planning constraints, Repair turnarounds, and Early warning of shortages or disruption.</p><p>This is a two-way street.</p><p>The Cost of Secrecy</p><p>Defence often withholds data under the banner of security, competition, or risk aversion. But the real risk isn’t in sharing — it’s in not sharing.</p><p>When industry doesn’t have the data, they can’t deliver. So Defence spends more money, buys too much stock, increases buffers, and wastes effort firefighting issues that could’ve been solved with foresight.</p><p>This lack of data transparency leads to:</p><p>Excessive inventory buffers, Double ordering, Increased downtime, Slower readiness response, Reduced trust between stakeholders.</p><p>In contested, coalition-led environments like NATO operations or multi-national exercises, this isn’t sustainable. Secrecy costs lives, not just money.</p><p>From Transactional to Transformational Relationships</p><p>To solve this, we need to move from transactional relationships to transformational partnerships.</p><p>Transactional relationships are based on contracts.</p><p>Transformational ones are based on shared goals, shared risk, and shared accountability.</p><p>It’s no longer enough to define success in narrow KPIs or delivery metrics. Success must mean:</p><p>Platform availability, Operational readiness, Life-cycle performance, Cost through life.</p><p>That means building partnerships where data is shared proactively, not reactively. Where forecasting is co-developed, not contractually demanded. Where failure is investigated jointly, not weaponised.</p><p>Why Now?</p><p>The urgency is real.</p><p>Geopolitical instability is increasing. The Defence budget is under pressure. Readiness is now a strategic currency. And we are operating in environments that are more agile, contested, and data-driven than ever before.</p><p>We cannot afford to operate in silos. We cannot afford duplication. And we cannot afford not to know.</p><p>NATO operations. Five Eyes interoperability. Coalition logistics. None of these can be successful without data transparency across organisational boundaries.</p><p>And industry is ready. They want this. What they need is for Defence to match that intent — with culture, capability, and commitment.</p><p>Leading by Example: Modelling the Behaviour We Expect</p><p>If we want transparency, we must demonstrate it. If we expect collaboration, we must enable it. That starts with leadership — at all levels.</p><p>We need to create the conditions where Defence and industry don’t just exchange contracts, but exchange insight. Where the default setting is to share, not shield. Where joint ownership of outcomes replaces transactional finger-pointing.</p><p>This isn’t just about new tools or data platforms — it’s about behaviour.</p><p>It’s about leaders having:</p><p>Honest, open conversations when forecasts are wrong. The discipline to plan based on evidence — not assumptions. The courage to share risk and own outcomes together.</p><p>And above all, it’s about consistency. Because transparency isn’t a one-off — it’s a culture.</p><p>As leaders across Defence, industry, and the wider logistics profession, we must model the behaviours we expect others to follow. The change starts with us.</p><p>A New Model: Shared Goals, Shared Risk, Shared Data</p><p>At its heart, the solution is simple:</p><p>If we want availability, we must share data. If we want resilience, we must forecast together. If we want trust, we must be transparent.</p><p>This means creating shared data environments — whether through platforms, policy, or process — where both Defence and industry operate off a common picture.</p><p>We need to shift from:</p><p>Blame →</p><p>Alignment</p><p>Secrecy →</p><p>Sharing</p><p>Forecasting in isolation →</p><p>Forecasting in partnership</p><p>One-sided contracts →</p><p>Joint success models</p><p>This isn’t just modern logistics. It’s mission-critical logistics.</p><p>Practical Recommendations</p><p>Here’s what Defence leaders can do now:</p><p>Mandate data-sharing clauses in all new sustainment and support contracts. Create joint forecasting platforms between DE&amp;S and suppliers. Fund supplier access to demand modelling tools where needed. Invest in Defence data literacy to ensure information is understood and trusted. Include transparency and co-ownership metrics in performance frameworks. Champion success stories that show data-driven partnerships in action.</p><p>Final Thought: The Accountability Question</p><p>So the next time availability slips or the forecast misses the mark, don’t just ask:</p><p>Why didn’t the supplier get it right?</p><p>Ask instead:</p><p>What didn’t we share?</p><p>What data did they need but didn’t receive?</p><p>What behaviours or policies stopped transparency from working?</p><p>Because if a relationship is to work, there must be transparency — and in Defence, that transparency must come in the form of data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H2qv69EPVk-D-Ln73ftL7Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=494aefa77ff3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supply Chain Council]]></title>
            <link>https://medium.com/@paulrobertsalmon/supply-chain-council-e1a717be22fe?source=rss-f93de0da4b8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1a717be22fe</guid>
            <dc:creator><![CDATA[Paul Salmon]]></dc:creator>
            <pubDate>Thu, 07 Aug 2025 20:42:03 GMT</pubDate>
            <atom:updated>2025-08-07T22:39:14.112Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*E3KhVomchf_vhPeY.jpeg" /></figure><p>By Paul R Salmon, FCILT Supply chains are evolving faster than ever. Digitalisation, geopolitical volatility, environmental mandates, and shifting customer expectations are reshaping not only what supply chains deliver-but how…</p><p><em>Originally published at </em><a href="https://supplychaincouncil.org.uk/"><em>https://supplychaincouncil.org.uk</em></a><em> on August 7, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1a717be22fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Guesswork to Ground Truth: Why DE&S Must Accelerate Forecasting Adoption — Now]]></title>
            <link>https://medium.com/@paulrobertsalmon/from-guesswork-to-ground-truth-why-de-s-must-accelerate-forecasting-adoption-now-fc8def3c3f21?source=rss-f93de0da4b8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc8def3c3f21</guid>
            <dc:creator><![CDATA[Paul Salmon]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 09:06:54 GMT</pubDate>
            <atom:updated>2025-08-07T22:41:00.372Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Guesswork to Ground Truth: Why DE&amp;S Must Accelerate Forecasting Adoption — Now</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/32/0*hmuWQi6HwEChQZHs" /></figure><p>Posted by</p><p>-</p><p>In the high-stakes world of defence logistics, the ability to accurately forecast demand is more than a planning convenience — it’s a strategic imperative. Whether maintaining complex equipment fleets, deploying urgently needed spares, or ensuring readiness across multiple domains, demand forecasting is the quiet engine behind operational availability.</p><p>Yet, despite this, demand forecasting remains underutilised across Defence Equipment and Support (DE&amp;S). Adoption rates for forecasting tools and practices are inconsistent, data remains siloed, and forecasts are too often based on gut feel rather than robust evidence. The result? Missed availability targets, unspent budgets, urgent buys, and lost opportunities for operational advantage.</p><p>If DE&amp;S is to deliver support at the speed of relevance, then demand forecasting can no longer be optional. It must become business-as-usual. This article sets out a clear, structured approach to improving forecasting adoption across DE&amp;S — turning it from a patchy practice into a professional discipline.</p><p>The Case for Change: Why Forecasting Matters</p><p>Forecasting in a defence context is not just about predicting how many bolts or batteries we might need. It is the critical first step in ensuring that the right item is at the right place, at the right time — and at the right cost. Without it, supply chains become reactive, inefficient, and prone to failure under stress.</p><p>In DE&amp;S, poor forecasting has wide-reaching consequences:</p><p>In-year budget underspend due to a lack of forward demand visibility Stockouts or overstocking of critical components Costly last-minute procurement, sometimes via Urgent Operational Requirements (UORs) Lost trust from front-line commands and operational units Weak decision-making at support boards, capability reviews, and investment panels</p><p>And most crucially: a degraded ability to assure equipment availability.</p><p>Forecasting isn’t a spreadsheet exercise — it’s operational resilience in numeric form.</p><p>In-Year Operating Plans: Where Forecasting Meets Funding</p><p>A key reason why forecasting must be embedded within DE&amp;S is its direct link to In-Year Operating Plans (IYOPs).</p><p>IYOPs are the backbone of short-term planning across DE&amp;S Delivery Teams. They outline what will be procured, repaired, delivered, or consumed within the financial year. Critically, they are also used to justify funding drawdowns and project approvals.</p><p>Without a reliable demand forecast underpinning them, IYOPs become speculative, resulting in:</p><p>Budget allocations based on outdated assumptions Mid-year budget rebalancing that disrupts support delivery Fragmented planning across inventory, engineering, and commercial functions</p><p>Forecasting, therefore, must be the foundation of IYOP development — not a bolt-on.</p><p>Ten Must-Do Actions to Improve Forecasting Adoption in DE&amp;S</p><p>1. Mandate Forecasting as a Core Function, Not a Side Task</p><p>Forecasting must become a formal requirement across DE&amp;S planning processes. This means:</p><p>Requiring forecast data to underpin all IYOPs and support strategy submissions Making forecasting a non-negotiable step in spares planning, repair scheduling, and procurement Treating forecast quality as a performance metric — not just quantity</p><p>2. Upskill the Workforce in Forecasting Principles</p><p>Lack of forecasting capability is a core barrier to adoption. Many staff — particularly those new to inventory or commercial roles — simply don’t feel confident producing or interpreting forecasts.</p><p>To address this:</p><p>DE&amp;S should roll out training on forecasting methods, from basic historical averaging to more advanced statistical and AI-based techniques. Forecasting should be included in core learning pathways for all roles in inventory, support, and engineering. A network of “forecasting champions” should be created to support local delivery teams and embed good practice.</p><p>The goal: forecasting becomes a core professional skill, not a niche specialism.</p><p>3. Move to a Central DE&amp;S Forecasting Team — In Line with Civilian Best Practice</p><p>Most leading commercial organisations — from FMCG to automotive — now rely on a centralised demand forecasting function. These teams are responsible for producing high-quality, standardised forecasts, supported by data science, domain knowledge, and tool expertise.</p><p>DE&amp;S should follow suit by:</p><p>Creating a Central Forecasting Team (CFT) to produce, assure, and manage forecasts across all platforms and categories Embedding CFT liaisons into Delivery Teams to ensure local context is incorporated Ensuring the CFT is responsible for forecast accuracy tracking, model maintenance, and continuous improvement</p><p>Benefits of this approach include:</p><p>Consistency of methodology and tools Improved accuracy through specialisation and data centralisation Reduced duplication across Delivery Teams Faster response to changes in operational tempo or funding availability</p><p>This shift would professionalise forecasting across DE&amp;S and bring us in line with proven civilian supply chain models.</p><p>4. Integrate Forecasting into Existing Workflows</p><p>Forecasting must be frictionless. If it feels like a bolt-on or extra burden, it won’t be adopted. DE&amp;S should:</p><p>Integrate forecasting modules directly into the IYOP toolset and ERP platforms Prepopulate forecast templates using live feeds (e.g., usage data from MJDI, repair rates from JAMES, and lead times from CRaFT) Develop simple dashboards to visualise forecast data and enable better decision-making</p><p>Forecasting should be something the system helps you do — not something you do to the system.</p><p>5. Automate the Baseline, Humanise the Exceptions</p><p>Automation can solve the adoption burden for the bulk of demand. For the 80% of inventory that follows predictable usage patterns, DE&amp;S should:</p><p>Use AI and machine learning to generate auto-forecasts based on historical demand and reliability data Link automated forecasts to warehouse replenishment and repair planning Free up human experts to focus on complex, high-risk, or emergent demands (e.g., rapid capability insertion, obsolescence scenarios)</p><p>This division of labour maximises efficiency while retaining professional oversight where it matters.</p><p>6. Track and Report Forecast Accuracy</p><p>What gets measured gets managed. DE&amp;S currently lacks a standardised way to assess the quality of forecasts. This must change.</p><p>A centralised dashboard should be developed to:</p><p>Track forecast accuracy (e.g., MAPE, forecast bias) across all categories and platforms Flag high variance forecasts for review Connect forecast error to IYOP variance, availability impact, and urgent buys</p><p>Transparency is key. Forecast performance should be visible from the front line to the investment board.</p><p>7. Link Forecasting to Operational Outcomes</p><p>Forecasting must be connected to why it matters — operational availability. This means:</p><p>Demonstrating how inaccurate forecasts lead to availability drops, urgent buys, or operational delays Building use cases that show how good forecasting improved readiness (e.g., spares available pre-deployment) Including forecasting impact in After Action Reviews and availability reporting</p><p>This elevates forecasting from a technical task to a strategic enabler.</p><p>8. Align Roles Across Inventory, Engineering, and Commercial</p><p>Forecasting fails when it is done in isolation. Demand is shaped by multiple factors — platform reliability, usage tempo, lead times, obsolescence — that sit across functions.</p><p>DE&amp;S should:</p><p>Set up cross-functional planning reviews to co-own forecast assumptions Require engineering to share failure rates, obsolescence curves, and usage expectations Require commercial to feed in supplier capacity, minimum order quantities, and contract constraints</p><p>Forecasting must be a shared responsibility — and a shared outcome.</p><p>9. Reframe Forecasting as Strategic Advantage</p><p>There is still a perception in parts of the organisation that forecasting is a “backroom” task. That must change. Forecasting should be reframed as:</p><p>A tool of operational advantage — especially in contested, coalition-led, or expeditionary contexts A contributor to readiness, resilience, and affordability A signal of professional maturity across the DE&amp;S enterprise</p><p>Forecasting isn’t just support — it’s strategy.</p><p>10. Make Forecasting a Leadership Priority</p><p>No transformation will succeed without senior buy-in. Forecasting must be on the leadership agenda.</p><p>That means:</p><p>Including forecasting as a requirement in all IYOP, Category Strategy, and Business Case templates Holding Delivery Teams accountable for forecast accuracy and adoption Including forecasting performance in team scorecards and Portfolio reporting</p><p>Forecasting adoption must be led from the top — and lived from the front line.</p><p>Conclusion: Forecasting Is the Foundation of Readiness</p><p>Defence support is becoming faster, more dynamic, and more contested. Forecasting is no longer a back-office exercise — it is the front end of resilience.</p><p>DE&amp;S must treat demand forecasting as a core professional capability. This means embedding it in every IYOP, upskilling the workforce, automating where possible, aligning roles across functions, and linking it directly to readiness outcomes.</p><p>And crucially, it means moving towards a centralised DE&amp;S forecasting function, modelled on the best of civilian supply chain practice — where accuracy is a profession, not a part-time task.</p><p>If we want to move from reactive to predictive, from waste to efficiency, and from guesswork to assurance — then forecasting must lead the way.</p><p>It’s not a luxury. It’s a must-do.</p><p>Author:</p><p>Paul Salmon FCILT is the Chair of the CILT Defence Forum, Lead Data Steward at DE&amp;S, and a strong advocate for professionalising defence logistics through data-driven decision-making and cross-functional collaboration.</p><p><em>Originally published at </em><a href="https://supplychaincouncil.org.uk/2025/08/02/from-guesswork-to-ground-truth-why-des-must-accelerate-forecasting-adoption-now/"><em>https://supplychaincouncil.org.uk</em></a><em> on August 2, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc8def3c3f21" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>