Lesson objective
Mark every point on a plant workflow map where export-controlled technical data, controlled unclassified information or trade-secret process knowledge crosses a boundary, and stop any crossing whose status is undetermined.
Plain-language explanation
Why this matters now
A workflow map usually shows people and steps. For an AI-assisted plant workflow it must also show data movement, because the most serious legal exposure in manufacturing AI is not a wrong answer. It is a file going somewhere it should not.
Level 1 taught what controlled technical data is, and Level 2 taught the decision one person makes at the moment of use. At the operations tier the question is different: across a whole workflow, run by many people on many shifts, where does data cross a boundary, and who decided that it may?
Three bodies of law matter most here, and each works differently.
Law / rule (federal, export control): under the Export Administration Regulations, 15 CFR 734.13(a)(1), an export includes "An actual shipment or transmission out of the United States, including the sending or taking of an item out of the United States, in any manner." Under 734.13(a)(2), export also includes "Releasing or otherwise transferring 'technology' or source code (but not object code) to a foreign person in the United States (a 'deemed export')." Under 734.13(b), any such release in the United States "is a deemed export to the foreign person's most recent country of citizenship or permanent residency." These rules bind persons subject to the EAR. Three limits matter. First, the definition alone creates no licence requirement: whether a licence is needed depends on the item's classification and the destination. Second, object code is expressly outside the deemed-export definition, so do not stretch the rule to all software. Third, this lesson does not define who counts as a foreign person; that definition sits elsewhere in the regulations, and your plant's export authority, the person or function your company has made responsible for export decisions, applies it.
Law / rule (federal, reaching the plant by contract): 32 CFR Part 2002 establishes the Controlled Unclassified Information programme under Executive Order 13556, for unclassified information that requires safeguarding but does not meet the criteria for classification. It distinguishes CUI Basic from CUI Specified, which carries handling controls that differ from CUI Basic, so not all CUI is handled alike. For nonfederal information systems, 32 CFR 2002.14 points to NIST SP 800-171 as the source of requirements to protect CUI Basic. The part binds executive branch agencies. A manufacturer's obligation arises from its contract, which is why the map must know which contracts flow CUI into the plant.
Law / rule (federal, trade secrets): 18 U.S.C. 1839(3) defines a trade secret as "all forms and types of financial, business, scientific, technical, economic, or engineering information," which on its face covers process data, tooling parameters, yields, formulations and cost models. Protection requires that "the owner thereof has taken reasonable measures to keep such information secret," and that the information derives independent economic value from not being generally known or readily ascertainable. The statute does not say that entering data into any particular software destroys trade-secret status. Whether the plant took reasonable measures is a question of fact about the controls it actually applied. State trade-secret law is separate and is not covered here.
A question to sit with
Your engineering team wants an AI tool to summarise every customer drawing package when it arrives. The tool's service is hosted outside the plant, and the vendor's support staff can view uploaded files. Nobody has determined which of your programmes carry export-controlled drawings. Where on your map does the drawing cross a boundary, and who, by name, decided it may?
What goes wrong
The map shows steps but not data. A file moves from the customer portal to the engineering share, into an AI tool, out to a supplier, and back. None of those crossings appears on the map, so none is decided.
A crossing is treated as internal because the people are internal. Deemed export follows the data, not the border. A release of technology to a foreign person inside the United States can be an export, so "it never left the building" is not an answer. Who qualifies is for the export authority, not for the map-maker.
A tool's storage and support are forgotten. Uploading a file to a hosted service is a transmission. Where the service stores it, and who at the vendor can see it, are crossings too.
CUI is treated as all alike. A plant learns one handling rule and applies it everywhere, when CUI Specified categories carry their own controls and the contract says which apply.
Process knowledge leaks by convenience. A process engineer pastes tooling parameters into a public chatbot to reformat them. The statute does not say that act destroys protection, but the plant must later show reasonable measures, and a map with no controls at that crossing is weak evidence.
Undetermined is treated as probably fine. When nobody knows whether a drawing is controlled, the path of least resistance is to proceed. That is the wrong default.
The practical answer
Add a boundary-crossing element at every data movement. Walk the map and mark every point where data leaves one system, building, customer programme, company or country for another, including into any AI tool, its storage or its vendor's support.
Record each crossing in a register.
| Field | What to write |
|---|---|
| Crossing | From where to where, including any AI tool, its storage and its support access |
| Data | The document or record, the part and customer programme |
| Export status | Controlled, not controlled, or undetermined, as decided by the export authority, with the date |
| CUI status | Whether a contract designates it CUI, and whether Basic or Specified, as the contract states |
| Process secret | Whether it contains process knowledge the plant treats as confidential |
| Who can receive it | People and systems at the destination, including vendor staff |
| Control | The measure applied at this crossing |
| Decided by | The named person and date |
Eight fields. A crossing with any status marked "undetermined" is shown on the map in red and does not operate.
Route every export question to the export authority. The map-maker never decides whether data is controlled or whether a recipient is a foreign person. Best practice: write the export authority's name on the map legend, so every crossing marked "undetermined" has an owner.
Take CUI status from the contract. The register records what the contract and its markings say. If a contract flows down CUI handling and the plant's systems have not been assessed against what the contract requires, the crossing into an AI tool is not decided by the operation. The markings belong to the originating agency or customer, not to the plant.
Treat each crossing as a reasonable-measures question. For process knowledge the plant treats as a secret, the control at each crossing is part of the factual record of what measures the plant applied. The map, with a control and a decision at every crossing, is how the plant knows what it did.
Re-check crossings when anything changes. A new customer programme, a new vendor feature, a change of hosting location or a new support arrangement changes a crossing. The operation owner re-opens the register row, and the export authority decides again.
Remember this
- Mark every data crossing, including into an AI tool, its storage and its vendor's support access.
- A release of technology to a foreign person inside the United States can be a deemed export; who counts is for your export authority.
- CUI obligations reach the plant through its contract, and CUI Specified carries its own controls.
- Trade-secret protection turns on reasonable measures actually applied, a question of fact; the map records them.
- Undetermined stops the work until the named owner decides.
Manufacturing example
Kestrel Precision Machining is a fictional job shop with three customer programmes: a commercial pump line, an automotive bracket family and a defence subcontract. Engineering manager Ruth Calder wants an AI tool, hosted by a vendor, to summarise incoming drawing packages. Before any trial, she adds boundary crossings to the as-run map of the quoting workflow and finds six: customer portal to engineering share; engineering share to the AI tool; the tool's storage at the vendor; the vendor's support staff; engineering to an outside heat-treat supplier; and a translation feature a buyer uses on supplier emails. She records each in the crossing register. For the defence subcontract, the contract flows down CUI handling, and the drawings carry markings from the customer; export status is recorded by the company's export authority, operations director Felix Harlan, as controlled. For the automotive brackets, Felix records export status as undetermined because nobody has reviewed the latest package. For the pump line, he records the drawings as not controlled, dated. Ruth also marks the pump line's tooling parameter sheets as process knowledge the shop treats as confidential. The register then decides the design. The AI tool will receive pump-line drawings only, with support access limited as the vendor contract states. The defence drawings never cross into the tool. The automotive crossing is marked red and does not operate until Felix decides. The tooling sheets do not cross at all. Two weeks later Felix classifies the automotive package, and Ruth re-opens that row with his decision and date rather than assuming it.
Responsible-use warning
Do not decide at the map whether data is export-controlled, whether a person is a foreign person, or whether a contract makes data CUI; route every such question to your export authority or the named data owner. Do not treat undetermined as probably fine: undetermined stops the work. Do not forget vendor storage, support access, meeting recorders and translation features as crossings. And do not claim that any tool setting by itself preserves or destroys trade-secret protection.
Human-review requirement
The company's export authority decides the export status of every crossing and records the decision and date. The officer or owner who signs any export representation remains personally responsible for it. The named data owner for each contract confirms what the contract says about CUI handling. The operation owner keeps the crossing register, marks undetermined crossings as stopped, and re-opens rows when a programme, feature, hosting location or support arrangement changes. Counsel is consulted where the export authority asks.
Practical exercise
Use a fictional plant, fictional customers and fictional programmes only.
- Take an as-run map of a workflow that handles customer drawings or process data.
- Walk it and mark every boundary crossing, including uploads to any AI tool, the tool's storage, vendor support access, meeting recorders and translation features.
- For each crossing, fill in the eight fields of the crossing register with invented details.
- Write the name of the fictional export authority on the map legend.
- Mark any crossing with an undetermined status in red, and write what the operation does instead while it waits.
- For one fictional contract, write what the register would record about CUI status, and where that information would come from.
- Identify one crossing involving process knowledge the plant treats as confidential, and write the control applied there.
- List three changes that would re-open a register row, and who would decide again.
- Write one sentence explaining why "it never left the building" does not settle an export question.
- Write the one-line instruction a buyer or engineer on any shift would follow on finding a crossing that is not yet in the register, including whom to tell.
Knowledge check
-
What does 15 CFR 734.13 say about releasing technology inside the United States?
Answer guidance: Releasing or otherwise transferring technology or source code, but not object code, to a foreign person in the United States is a deemed export to that person's most recent country of citizenship or permanent residency.
-
Who decides whether data at a crossing is export-controlled or whether a recipient is a foreign person?
Answer guidance: The company's export authority, the person or function made responsible for export decisions, not the map-maker. If the status is undetermined, the crossing does not operate.
-
How does a CUI obligation reach a manufacturer?
Answer guidance: Through its contract. 32 CFR Part 2002 binds executive branch agencies; the contract flows the obligation to the plant, and it says whether data is CUI Basic or CUI Specified with its own controls.
-
What does 18 U.S.C. 1839 say about putting process data into software?
Answer guidance: It does not say that entering data into any particular software destroys trade-secret status. Protection requires reasonable measures to keep the information secret, which is a question of fact about the controls the plant actually applied.
Sources and further reading
- Bureau of Industry and Security (U.S. Department of Commerce) — 15 CFR 734.13 - Export. Accessed 2026-09-15.
- National Archives and Records Administration, Information Security Oversight Office (via eCFR API) — 32 CFR Part 2002 - Controlled Unclassified Information (CUI). Accessed 2026-09-15.
- United States Congress (via U.S. Government Publishing Office, govinfo) — 18 U.S.C. 1839 - Definitions (Defend Trade Secrets Act / Economic Espionage Act). Accessed 2026-09-15.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.