Why start with the transfer boundary?
The safest production transfer is often smaller than the full aircraft. Moving a complete assembly, subsystem, integration step, inspection flow, or test package can relieve a constraint while preserving final configuration and release authority.
A useful boundary has complete inputs and outputs. It identifies what enters the work package, which revision applies, what process and tooling are required, what evidence is produced, how the result is accepted, and where downstream responsibility resumes.
Controlled transfer map
| Control area | Transfer question | Required definition |
|---|---|---|
| Configuration | What exact product state moves? | Revision, effectivity, software state, and change authority |
| Material | Who purchases, approves, receives, and traces inputs? | Source list, ownership, records, and substitutions |
| Process | How is the work performed consistently? | Released sequence, tooling, parameters, and trained work |
| Inspection | Which characteristics are checked? | Plan, method, equipment, result, and disposition |
| Test | What proves function or acceptance? | Method, asset, configuration, data, and authority |
| Nonconformance | Who contains and decides unexpected product? | Record, segregation, review, disposition, and escalation |
| Release | Who accepts the output and on what evidence? | Acceptance criteria, record packet, and release owner |
Four transfer gates
- 01
Package screen
Confirm the released baseline, missing definitions, source ownership, tool ownership, inspection, test, records, and acceptance basis.
Decision: is the package transferable? - 02
Boundary release
Approve the exact work, interfaces, inputs, outputs, authority, information path, and success criteria.
Decision: what is allowed to move? - 03
Transfer lot
Execute a bounded lot, record deviations, compare results, and verify the complete evidence packet.
Decision: is the new path controlled? - 04
Rate gate
Increase work only when material, process, people, inspection, test, quality, and release support the next rate.
Decision: what evidence releases the next step?
What causes a second source to fail?
The package contains tribal knowledge
The new source receives drawings and a BOM but not the actual sequence, tooling logic, inspection points, test basis, and exception history.
Authority is split but not named
Both sources assume the other controls substitutions, changes, nonconformance, or final acceptance.
Test is treated as downstream
Transferred assembly output accumulates because test equipment, software, data review, failure analysis, or retest capacity was not included.
Rate comes before equivalence
The program asks for production output before the transfer lot demonstrates an accepted, repeatable evidence path.