Machinery
The delivery date you promised
You promised a customer a date. The Machinery Scan asks, for each critical supplier: if it failed today, would you see it, decide and recover before that date slips?
The clock: Days of slack before the delivery date
Playbook: fictional demo
A late part becomes a late machine
One source, no second.
Some parts come from one supplier with nothing qualified behind it.
Checked once a week.
A supplier checked weekly can be a week late before anyone knows.
Nobody owns it.
A critical supplier with no watcher and no owner.
The customer hears last.
When a date cannot be held, someone has to tell the customer. That is a decision, and it needs a name.
The rule is the automotive rule with one word changed: the slack before the delivery date must cover the days to see, decide and recover.
Machinery · fictional
Muster Maschinenbau, taken through the Scan
An invented machine builder. Of 7 critical suppliers, 1 is safe.
Run the Machinery Scan- Too slow, 3. The gear units supplier is 5 days short: 12 days of slack, 17 needed. The machine-bed castings need 102 days and have 20.
- Not routed, 1. Credit monitoring sees the hydraulic units supplier after 30 days, and nobody decides.
- Unseen, 1. The control cabinet build has no watcher and no owner.
- Unknown, 1. Nobody has stated how long the slewing bearings take to recover.
- Safe, 1. The servo drives supplier: 25 days of slack, 20 needed, second source qualified.
Every supplier not in time gets one of four decisions with a name and a date: second source, pull forward, re-plan, or tell the customer.
What the Scan settles
The same engine, one word changed: slack before the delivery date instead of stock. 1 of 7 critical suppliers win the race.
Machinery · fictional
- Critical components with their slack, owner and watcher
- The race for every committed delivery
- Which supplier would make you miss a promise, and who would know
- A decision per supplier: second source, pull forward, re-plan or tell the customer
What it does not do
- It does not re-plan your projects. It shows which promise is at risk and who decides.
- It assumes no Catena-X connection.
- It has only run on an invented company. The decision logic is the same as in the automotive Scan; only the clock changes.
What changes in every industry
Know what you protect
Every Scan starts with the thing that must not stop: a line, a delivery date, a regulated service. Then it counts the days you have.
Owners, not dashboards
Every warning gets a named owner and a deadline. A tool that sees a risk nobody is bound to act on is a finding, not a control.
Proof the CFO signs
A value floor in your own numbers, signed before anything is built. Then scale or stop on what was measured.
Questions
We build to order. Does this fit?
It was built for that. The clock is the slack before each committed delivery, not a stock level.
Does the system tell our customer?
No. Telling the customer is one of the decisions. The Scan makes sure it has a name and a date.
Is this an AI product?
It is a method with an engine. AI can shorten the days it takes to see a warning; a person always decides.
What data do you need?
Your own register: critical suppliers or AI use cases, the tools that watch them, and who owns them. A spreadsheet is enough to start.
What does it cost?
The Scan has a fixed price between €15,000 and €25,000, set by ten published drivers. You see the rule before you sign.
Has this been used with clients?
Every case on this page is fictional and labelled so. Each industry shows how far it is proven, and that only changes with a paid Scan.
Other industries
Insurance & asset management
AI pilots that reach the daily work, inside the AI Act and DORA
Open the industry pageAutomotive suppliers
The running line
Open the industry pageElectronics
Your allocation
Next: not built yetStart with what you protect.
A short self-check first. Then, if it fits, a fixed-price Scan with the people who can say no in the room.