FAQ DMS-Q / DIRECT ANSWERS

Questions Before Production Transfer

These answers explain the control logic behind a build-to-print transfer. Program-specific price, schedule, process, facility, credential, and acceptance commitments require a scoped review.

Name the part, quantity, controlling material or process, and required date. Specification fit is reviewed before capacity or timing is stated.

What does build-to-print mean for a UAV?

The customer supplies and controls the product definition while the manufacturer executes approved sourcing, fabrication, assembly, inspection, testing, documentation, and release requirements within an agreed scope. Design authority and approval thresholds must remain explicit.

Which records belong in a complete production package?

The package may include controlled CAD, drawings, BOMs, specifications, approved-source information, software or firmware identification, assembly instructions, workmanship criteria, tooling, inspection plans, test methods, packaging, labeling, serialization, records, and acceptance criteria. The exact set depends on the product and contract.

May a transfer begin from a golden unit and partial files?

A review may begin there. Repeat production should not be represented as controlled until missing definitions, authority, inspections, test methods, and acceptance basis are identified and closed to the level required by the program.

How are material or component substitutions controlled?

Define approved alternates, evidence requirements, engineering-review thresholds, customer approval, effectivity, work-in-process disposition, and record updates before use. A purchasing choice should not silently become a design change.

Who is allowed to release an engineering change?

The governing agreement and configuration plan should name design authority, approval roles, notification requirements, effectivity, affected records, and treatment of existing inventory and work in process.

How are inspection and acceptance requirements established?

Each inspection or test should map to a drawing, specification, workmanship requirement, functional condition, or contractual acceptance basis. The plan should define method, sampling where allowed, equipment, record, disposition, and release authority.

Which traceability records can follow a unit or lot?

The agreed chain may include supplier and purchase records, material lots, serials, processes, software state, calibration, operations, inspection results, nonconformance, deviation, test, and release evidence.

Can an incumbent production package be transferred?

The review should examine controlling files, suppliers, tooling, inventory, work in process, open changes, quality history, test assets, acceptance records, and undocumented knowledge. Scope depends on what can be obtained and verified.

Can production continue while engineering changes are active?

It can be evaluated when the current baseline, approval authority, effectivity, work-in-process disposition, and closure path remain controlled. Fundamental design instability may require engineering closure before release.

How are required quality credentials confirmed?

Verify the issuing body, certificate or registration, legal entity, facility, scope, status, relevant dates, exclusions, and applicability to the proposed work before publication or award.

May export-controlled or NDA-protected files be sent in the first email?

No. The initial RFQ email accepts only high-level fit information. Data classification, export, confidentiality, account, access, storage, facility, and exchange conditions must be established before protected technical data is shared.