WW/PROCUREMEN
Capital Project Procurement Gap: A Framework Claiming Eight-Figure Savings
A procurement veteran claims eight-figure savings and 33-50% cycle-time cuts from a DEEK readiness gate linking engineering and supply chain before RFQs go out.
- By
- Elena Vasquez
- Filed
- Length
- 933 words
- Read
- 5 min
Key points05
- Contract and sourcing cycle times fell roughly one third to one half when scope and market realities were aligned before RFQ, per field outcomes across $5B+ of capital projects
- The DEEK readiness gate walks packages through Design, Engineering, Estimating and Kickoff phases with a Go/No-Go decision on RFQ release
- Portfolios using the framework posted double-digit percentage gains in contracting efficiency and eight-figure savings on projects from hundreds of millions to multiple billions of dollars
- Authors are Moin Uddin Jewel of T1 Energy and Md. Muzaffer Hosen Akanda of Texas State University, formerly Tesla
- Evidence is before-and-after portfolio comparison, not a controlled head-to-head study, the authors acknowledge
Capital projects worth a combined $5 billion or more have produced a consistent failure pattern, according to an 18-year procurement veteran: long-lead items surface three months late, suppliers cannot meet engineering specifications, and change orders trace back to decisions made before procurement entered the room. In a newly published paper, Moin Uddin Jewel, Senior Category Manager at T1 Energy, argues the problem is not process discipline but a missing structural bridge between engineering and supply chain — and claims portfolios that built one have delivered eight-figure savings.
The field outcomes Jewel reports are concrete: contract and sourcing cycle times fell by roughly one third to one half when scope, technical requirements and market realities were aligned before a request for quotation rather than discovered during it. Portfolios running the framework posted double-digit percentage gains in contracting and procurement efficiency across projects ranging from several hundred million to multiple billion dollars in value. The figures come from before-and-after comparisons within the same portfolios, not a controlled study — a limitation Jewel himself acknowledges.
Where does the gap actually live?
Strip a capital project to its simplest form and the flow looks linear: engineering defines it, procurement sources it, suppliers build it, construction installs it. In practice, engineering sets technical requirements without knowing what the supply market can deliver — realistic lead times, manufacturing capacity, cost drivers, viable alternatives. Procurement often discovers those constraints only after the design has hardened, when changing anything becomes expensive and slow.
The breakdown runs in reverse as well. Supply chain may spot a better material, a faster supplier or a smarter commercial structure, but the insight arrives too late for engineering to act. Jewel defines the gap as the distance between what a project technically requires and what the market can realistically deliver inside the project's cost, schedule and execution constraints. It rarely appears as one dramatic failure, he writes, but as a hundred small ones: a schedule slip, a rework order, an award that looked competitive on paper until hidden costs surfaced three months in.
What are the five moves?
The framework operates at two levels — one project-level move and four package-level moves, each backed by a working template the authors have made freely downloadable via Zenodo.
- Bring supply chain into FEED. Front-end engineering design sets both the design basis and the package-splitting strategy for the whole facility. Supply chain needs a seat at project level during FEED to flag long-lead exposure, thin supplier bases and market realities before package boundaries lock in sourcing problems.
- Run a DEEK workshop before going to market. DEEK — Design, Engineering, Estimating, Kickoff — is a readiness gate, not a status meeting, walking each package through four phases with checklists. Packages carry a gate status: Not Ready, Pending Review or Approved.
- Structure follow-up with a READ matrix. Recognize the requirement, Evaluate what the market can deliver, Anticipate disruptions, Develop the action — four steps that convert cross-functional conversation into documented decisions.
- Assign ownership at two levels. A project-level RACI covers governance decisions such as FEED scope freezes and change-order authority; a package-level Materials/Package Responsibility Matrix names owners for individual deliverables, from technical evaluation to shortage resolution.
- Balance the scorecard. Built on Kaplan and Norton's four-perspective structure with two added columns — the trade-off each goal creates for another function, and the agreed boundary resolving it. One example: procurement may accept up to 5% higher component cost if it guarantees zero line shutdowns, with inventory capped at 30-day turns.
Jewel credits co-author Md. Muzaffer Hosen Akanda, a lecturer in industrial engineering at Texas State University and former equipment engineer at Tesla, with refining the DEEK process, RACI framework and MRM template through application on active Tesla projects.
How strong is the evidence?
Jewel is explicit about the limits. The reported outcomes are observed field results measured against each organization's own baseline before the framework was introduced — not a formal head-to-head comparison of the same package type run with and without the framework on the same project. He identifies that controlled comparison as the next step, naming the metrics: post-RFQ engineering changes, change-order frequency and value, procurement cycle time, supplier lead-time variance and Total Installed Cost variance, measured on framework packages against conventional ones run in parallel.
Why now?
Capital projects in energy, critical minerals and advanced manufacturing face more schedule and cost pressure than most organizations have encountered in a decade, the paper argues, citing the IEA's Global Critical Minerals Outlook 2025 among its references. Reshoring, electrification and supply chain security demands are compressing timelines that once carried slack. Most organizations already possess engineering discipline and procurement discipline; what they lack is the connective tissue between the two, at exactly the moment when catching a gap is still inexpensive.
The underlying idea compresses into one line: procurement should not start the day engineering finishes. The two functions should work together early enough to know whether what is being designed can actually be built, sourced and delivered inside the constraints the project really faces — a prescription Jewel says requires one disciplined checkpoint, DEEK into READ, rather than a rebuild of project delivery.
For shippers and forwarders managing capital-project logistics, the implication is direct: clients that adopt readiness gates of this kind will bring suppliers and logistics providers into scope earlier, with named package-level owners and pre-agreed trade-off boundaries — likely compressing RFQ-to-award cycles and shifting lead-time discussions to the design phase, where alternatives still exist.
Source: scmr.com
More from Elena Vasquez
Show full bio
News editor covering people, launches and day-to-day practice in Ocean and air freight, container shipping at Waybill Wire.
929 articles
Related05
Mineral Buyers Face a 2027 Contract Test as Supply Promises Pile Up
90% of Logistics Leaders Hit AI ROI Targets — But 62% Want Faster Payback
GlobalFoundries commits $21B to New York fabs under US-Japan trade deal
JPMorganChase Puts Names to $1.5tn Shipbuilding Push
Maritime tech's scale problem: 4,900 suppliers, $3bn VC and a buyout endgame