What shops here make and for whom
A typical San Diego job shop quotes parts for several very different customers: a drone airframe subassembly, a surgical instrument housing, a lab instrument bracket. Volumes are often low to medium, tolerances tight, and documentation expectations vary sharply by customer.
Shipyard suppliers behave differently, producing fabricated structures and repair parts under tight availability windows. Cross-border assemblers in Tijuana add a further layer, with parts crossing the border for assembly or testing.
Quoting and estimating realities
High mix, low volume work makes quoting heavy on setup and programming. Medical device quotes need to include validation, cleaning, inspection and documentation costs, while defense quotes add traceability and sometimes government source inspection. San Diego labor and facility costs are high, so wasted quote time and rework matter more here than in lower-cost regions.
Quoting from similar past parts is the common shortcut. It works only if past quotes and actual costs are searchable and tied to the same part families.
- Tag past quotes by material, process and customer type
- Capture actual versus quoted setup time per part family
- Flag quotes that need export control review before sending
Try it here, free
FDA 21 CFR 820 to ISO 13485 Clause Crosswalk
Map each 21 CFR 820 quality system topic to the corresponding ISO 13485 clause to speed up QMSR gap assessments and procedure rewrites.
ERP and systems seen in these shops
Contract machine shops in the area frequently use JobBOSS, E2, ProShop ERP or Global Shop Solutions. Device and biotech manufacturers tend to run NetSuite, Epicor Kinetic, SAP Business One or Plex alongside a separate quality management system. Defense electronics suppliers may use Infor SyteLine or other manufacturing ERP.
The regular gap is between the ERP and the quality system: device history records, nonconformances, supplier approvals and training records live elsewhere. Retrieval over those records helps with audits and complaints, as long as controlled documents are indexed with their current revision and status.
Compliance, data handling and where private AI fits
Regulated life sciences and defense customers both have good reasons to keep data in-house. Device records may include product design and supplier information, and defense data may be export controlled or covered defense information. Running open-weight models on-prem or in a private cloud lets the customer apply its own access control and logging.
AI can answer questions over ERP data and documents and help draft summaries, but regulated decisions such as batch release, CAPA closure or design approval stay with qualified people. Any use inside a validated system should follow the company's own computer system validation process.
Frequently asked questions
Who supports small manufacturers in San Diego County?
California Manufacturing Technology Consulting (CMTC), the state's NIST MEP affiliated center, provides consulting and training to small and mid-sized manufacturers. The San Diego Regional EDC and Biocom California also support local companies in industry and life sciences.
What standards apply to medical device suppliers in San Diego?
Device manufacturers work under FDA 21 CFR Part 820 and commonly ISO 13485. Suppliers are held to the customer's supplier controls, which often include audits, material certifications and change notification. Requirements vary by device class and customer, so check each purchase agreement.
How do cross-border Tijuana operations affect ERP needs?
Companies moving parts across the border need to track inventory under Mexico's IMMEX program and customs documentation on both sides, and often run multiple legal entities. Your ERP needs to handle multi-entity inventory, currency and transfer documentation. Confirm program details with a customs specialist.
Is private AI practical for a defense electronics supplier?
Yes, when the model runs inside your controlled environment and you have clear access rules. It suits document search and ERP questions. It does not remove your obligations under DFARS, NIST SP 800-171 or ITAR, so involve your compliance lead before loading controlled data.