3 分でわかる Gottlieb。
架空のステアバイワイヤアクチュエータが、ゲートを通ります。43 種類の文書、ひとつのグラフ、そしてどの文書ペアにも現れず、連鎖の上にだけ潜む一つの指摘。それを後から見つけたとき、何を失うのか。
- 0:04
届くもの
43 種類の文書、8 つの分野。すべてが互いに一致していなければなりません。
- 0:46
検証の流れ
コードが読み、108 のエージェントが判断し、グラフがつなぎ、1 万件のルールで突き合わせる。決めるのは、御社のエンジニアです。
- 1:12
グラフになるまで
どのペアも通る。連鎖は通らない。評価は、すでに存在しない形状で行った試験に基づいています。
- 1:49
出てくるもの
不承認。14 件の指摘すべてに出典ページを付し、5 種類のレポートに。
- 2:07
ナレッジグラフ
すべてのパッケージが、問いに答えるグラフになる。プログラム、工場、サプライヤー、部品。
- 2:22
変更影響
9 つの構成、4 つのキャリーオーバーモジュール、3 つの工場。数分でわかる。
- 2:33
キャリーオーバーの再認定
6 つのモジュールのうち 4 つが、旧アーキテクチャ向けの承認のまま新アーキテクチャに入っていた。
- 2:44
結び
同じ隙間でも、見つかる段階が一つ後ろにずれるごとに、代償は 10 倍になる。
Gottlieb. Engineering AI for the built world.
Before a part is released for series production, your team or a supplier prepares up to forty-three document types, across eight disciplines. From design specifications, to functional safety, and all the way to the production process. Every one of them has to agree with every other one. Three are missing here. And every one of them is dense. A detail drawing: every dimension and tolerance, and one note that makes a radius critical. Seven sheets. A design FMEA: failure modes, causes and controls, nested three levels deep. Twenty-eight sheets. A test report: four hundred measurements against the limit line. Forty-four pages. Every change has to reach every document. That is where gaps can hide.
Here is how we check it. Code pulls out every value. AI reads what code cannot: drawings, scans, prose. One hundred and eight agents judge the facts, across eight lifecycle gates. Code links every fact into one graph. And cross-checks it against ten thousand written rules, in five layers. Director agents set the verdict. A separate check audits it. Your engineer decides. Same package, same answer, every time.
Now the hard part. It starts with the drawing. AI reads it into facts, and the facts become a node. The risk analysis and the fatigue test, read the same way. Three nodes, one graph. The drawing changed in May. The risk analysis still rates it low risk, because the fatigue test passed. Check any two documents against each other, and every pair passes. Walk the chain, and the rating rests on a test of samples built before the change. A geometry that no longer exists. That gap lives on the chain, not on any pair. The graph finds it, with three page numbers.
The result: not approved. Fourteen findings, five critical, three documents missing, and the wrong submission level. Every finding cited to its page, in five reports: for the supplier, the engineer, the auditor, and the board. The engine prepares. The engineer decides.
Next: every package becomes a knowledge graph you can ask. Programmes, plants, suppliers, parts, requirements. Nobody maintains it. It is built from the evidence you just saw checked. Now ask it the questions that matter.
A change comes in on the motor. What does it touch? Nine configurations on a second programme, four carryover modules, three plants. Known in minutes, before the change is released.
Which carryover modules entered the new architecture on an approval written for the old one? Four of six. The parts did not change. Their validity did. Re-qualification computed from what changed underneath.
The same gap costs ten times more at every later stage. Found before the start of production, the part and its production process can be adjusted.
Gottlieb. Engineering AI for the built world.