A digital thread in aerospace has to connect one thing: the identity of a single physical part, held steady across every system and every company that touches it. Design intent, the purchase order, the machine that cut it, the inspection that accepted it, the hangar that pulls it off a wing twenty years later. Most thread projects get built as connections between systems. What the thread actually needs is simpler: everyone who handled the part used the same name for it and wrote down what they did. Picture a shop. I have walked through a dozen like it. Forty or so people on the floor, good work, a few primes on the customer list, certificates framed by the door. The quality manager gets a question from one of those primes about a lot that shipped over a year ago. He has the answer in minutes. Two screens, one binder, and a phone call to a machinist who happens to still be there. That is fast and he is right to be proud of it. But the prime believes it has a thread running through that shop, and what it actually has is a binder and one long-serving machinist. Call him Dave. Every shop has a Dave. What is a digital thread in aerospace? A digital thread in aerospace is the connected record of one part or one assembly across its whole life. What it was supposed to be, at which revision. What was actually made, on which machine, by which program. What was measured, by whom, against what. What was accepted, what was deviated and why. What was installed, into which assembly, on which tail. What happened to it in service. The word thread matters here. One line through many places. Not a copy sitting in each of them, which is what most shops have, and copies stop matching each other. That is also the line between a digital thread and a digital twin: the thread is the record, the twin is a model built on it. An aerospace digital thread has a harder job than most for a boring reason. The part outlives the systems. A structural fitting can be in service for thirty years. The software that recorded its inspection gets replaced two or three times over that life, in most shops I have seen. The thread has to survive those changes and at least one merger, and it has to survive them at four or five different companies at once. The five places a thread has to connect Walk any part backwards and you land in the same five places, usually owned by five different people and often by more than one company. The drawing. What the part is meant to be, and which revision was current on the day it was made. The order. What was bought, from whom, against which revision, with which flowdowns attached. The floor. What actually happened. The machine, the program version, the operator, the tool change, the two hours the spindle sat idle. The record. What was measured and by whom, what was accepted, what was deviated, what the certificate says. The field. Where it was installed, what it was installed into, and what happened to it the day it came back off. Every one of those five holds a fact nobody else holds. A thread that skips the third one can tell you the part passed and cannot tell you why the next forty did not. A thread that skips the fifth one is only a manufacturing record, whatever you call it. Where the digital thread breaks Almost never inside a system. Systems are pretty good at keeping their own records straight. The thread breaks in the space between two owners of the record, and there are four of those spaces in a normal supply chain: prime to supplier, supplier to sub-tier, shop floor to quality record, and delivery to the field. The break has the same shape every time. The part changes its name. The prime calls it by the drawing number. The supplier’s planning system calls it by an internal number assigned when the job was quoted. The sub-tier that does the heat treat calls it by the lot they ran it in. The inspection record calls it by the serial. The MRO shop, twenty years on, calls it by the position it came out of. Every one of those names is correct. Nobody wrote down that they refer to the same object. So a person does the translation. Someone reads the customer’s part number, finds it in their own system, pulls the cert from a folder, matches it to a lot, and answers the email. That translation happens every time a customer asks a question, and it is never recorded, because the person doing it does not think of it as work. It is just the job. That is the real state of most threads I see. Not broken exactly. Held together by people, at full cost, every single time, and nobody writes down that it happened. The second break is format. A certificate that arrives as a scan of a signature can be filed and shown to an auditor, and no software can read it. Same with the first article package that gets emailed as a PDF. The facts are in there. Nothing downstream can use them without a human retyping them, and every retype is a new place for an error to get in. A test to run on one part number this week Pick one part number that shipped in the last twelve months. Not your worst one and not your showcase one. Something ordinary. Ask five questions, and time each answer, and write down who you had to call. Which drawing revision was it built to, and can you show that revision was current on the day it was cut? Which machine made it, and which version of the program was loaded? Who inspected it, and where are the measured numbers, not the stamp? What did your supplier call it in their system, and where is that written down? If it comes back off an aircraft in 2041, what will still exist? Any answer that took a phone call is a handoff where a person, not a record, makes the connection. Any answer that took more than a few minutes is a handoff where someone has to go searching for the connection. That list, in order of how long each answer took, is the order to fix them in. It costs an afternoon. Then fix the cheapest one first, which is almost always the naming. A written cross reference between what your customer calls the part, what your system calls it, and what your sub-tiers call it is a spreadsheet. It is also the single highest-value document in the building, because every other connection you ever build depends on it. One caution. This test tells you whether you can answer a question. It does not tell you whether your records satisfy a standard or a contract. The rule text and a compliance professional govern that, and no blog post substitutes for either. Do you need new systems to build a digital thread? Most of the suppliers and repair shops I talk to already hold every fact the thread needs. It is spread across a drawing system, a planning system, the machines, an inspection record, and a filing cabinet, and the connecting is done by people who have been there long enough to know where everything is. A replacement system does not create any of those facts. It moves them, and on the way it usually gives the part one more name. The reason to care has nothing to do with software. A part you make this month will be on an aircraft after the people who made it have retired. Somebody you have never met will call with a question about it, and the answer will either exist or it will have walked out the door with Dave.