POLICY / PRODUCTION DATA

Keep protected production data outside email.

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

What production information is safe for the initial request?

Only the component, quantity, material or process, need-by date, and high-level production constraint. The quote request begins the review; it is not a production-data exchange.

Appropriate

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

Keep protected production data out

  • Files, drawings, source code, credentials, or detailed process data
  • Controlled or classified information
  • Export-controlled technical data
  • NDA-protected or customer-restricted material
  • Proprietary product, supplier, test, quality, cost, or security data
  • Sensitive personal information

LATER EXCHANGE

Establish the boundary before transferring information.

  1. Confirm fitDecide whether technical data is necessary.
  2. Classify scopeIdentify contractual, customer, export, security, and confidentiality controls.
  3. Assign responsible peopleConfirm approval, access, storage, use, and deletion responsibility.
  4. Approve a systemSelect an exchange path appropriate to the verified handling requirements.
  5. Minimize transferShare only what the defined decision requires.

Website measurement

We use Google Analytics only when you select Allow analytics. It counts page views, quote-button clicks, on-page tool starts and completions, and successful quote submissions. We also receive the referring page, campaign tags, device and browser category, and coarse geography. Advertising storage stays denied. Your choice is stored in this browser, and the quote form’s name, email, and project description are never sent to Analytics.