The JEDI Story
Just-in-time Execution and Distribution Initiative — real-time decision support for Ford stamping plants.
JEDI was built to attack Enemy #1: premium freight. In stamping plants, the schedule on paper and the plant floor in reality were often two different worlds. JEDI’s job was to bridge them — combining customer demand, real-time production status, and actual manufacturing variability into something operators and schedulers could use before the crisis hit.
What JEDI Was
A Scheduling System for the World as It Actually Exists
Production control in stamping had to hit due dates while keeping inventory lean. In practice, quality problems, downtime, fluctuating yields, die-set variability, and shifting customer demand turned “build-to-schedule” into a fast-moving target. Firefighting became normal, and premium freight followed.
JEDI was designed as a plant-floor MES decision-support layer — not just another planning tool. It pulled together MRP demand, real-time counts, cycle rates, yields, and operational reality so decision-makers could react before shortages became shutdowns.
“Simple systems are made complex by unbounded variability.”
The Problem
Lean Meets Chaos
The plants were expected to operate lean while living with rejected parts, unscheduled downtime, obsolete cycle rates, and highly variable die-set performance. The result was overtime, confusion, and expensive freight.
The Insight
Data Before Features
Fancy turnkey MES products fail when they optimize the wrong thing first. Reporting, UI, collaboration, and algorithms are secondary. If the data is wrong, the whole system is theater.
The Lesson
Operators Carry the Truth
Managers often know how the system should work. Distribution and scheduling people know how it actually works. JEDI explicitly recognized that undocumented human knowledge was part of the architecture.
Why Off-The-Shelf Fails
Roadblock #1: Product Before Process
One of the document’s strongest arguments is that companies often buy “professional, feature-rich” MES products before understanding their own data, workflows, and internal architecture. That inversion guarantees disappointment.
Realtime production data must be collected and organized
Critical manufacturing resources must be consistently visible
Enterprise systems must be integrated efficiently
Everything else comes after that.
Why Off-The-Shelf Fails
Roadblock #2: The Missing Tribal Logic
The report flat-out says a second major roadblock is not knowing how the business actually operates. Critical knowledge lives in the heads of scheduling and distribution people who keep the place running. Ignore them, and the configuration is wrong before the first screen loads.
“Valid data must drive our MES effort. Features have no value without data integrity.”
The Building Blocks
What JEDI Was Actually Built to Do
The Woodhaven prototype broke the system into seven layered functions:
Customer Requirements Summary — prioritize end-item demand from corporate MRP
Blanker/Press Requirements — cascade demand into make-part needs
Realtime / Integrated Production Monitor — connect live counts with requirements
Supply Chain Event Management — detect likely premium freight before it happens
Global Plant / Customer Status — show what matters now
Planning / Scheduling 14-Day View — build realistic production schedules
Optimization Tools — only after the first six layers are solid
The report draws a clean line between prescriptive functions and mere monitoring. JEDI wasn’t supposed to tell you what went wrong yesterday. It was meant to help prevent tomorrow’s miss.
Current Status in 2001
Prototype, Functional, and Already Proving the Point
At the time of the report, JEDI had been in part-time development for about four months at Woodhaven Stamping Plant. The product was described as fully functional, with data informally verified, and realtime counts plus cycle-rate history being added to improve prediction accuracy.
It was still a prototype — but already strong enough to stand as both an operational scheduling tool and a model for how core-business IT solutions should be built.