ManufactureDronesComponent manufacturing

POLICY / COMPONENT DATA

Keep protected information out of email.

What belongs in the first component-RFQ email, what must stay out, and how a later technical exchange should be approved.

What information is safe for the first email?

Only the component, quantity, material or process, need-by date, and high-level program context. Email begins the review; it is not a technical-data exchange.

Appropriate for the first email

  • Business contact information
  • Component needed
  • Requested quantity
  • Known material or process
  • Need-by date
  • High-level program context

Keep protected design data out

  • Files, drawings, CAD, source code, or credentials
  • Controlled or classified information
  • Export-controlled technical data
  • NDA-protected or customer-restricted content
  • Proprietary design, architecture, or security details
  • Sensitive personal information

HANDLING SEQUENCE

How a later exchange should be established

  1. Confirm program fit.Determine whether a technical exchange is necessary.
  2. Identify information type.Classify contractual, customer, export, security, and confidentiality restrictions.
  3. Assign responsible owners.Confirm who approves disclosure, access, storage, use, and deletion.
  4. Approve the exchange path.Select a system and process appropriate to the verified handling requirements.
  5. Share only the minimum.Transfer the least information necessary for the defined decision.