Aerospace & defense · ITAR · Traceability
Controlled data stays controlled. Every part stays traceable.
Export control and traceability are architecture decisions, not settings you add after go-live. BSP designs NetSuite so controlled technical data reaches only the people allowed to see it, and every serial, lot and revision carries its history from receipt to shipment.
2
Architectures for controlled data: keep it out of NetSuite, or encrypt it inside
0
Decrypted values saved back to NetSuite by BSP Secure Encryption
1
History per serial or lot, from supplier receipt to shipment
22 CFR
Parts 120–130, the ITAR, designed for from the first workshop
Who this is for
Two obligations you can’t bolt on after go-live.
If you hold ITAR-controlled technical data, work under CUI flowed down from a prime, or answer to an AS9100 auditor, your ERP has to prove who saw what and where every unit came from. Retrofitting either means reworking roles, records and data flows that are already in production.
MORE FOR AEROSPACE & DEFENSE
ITAR-registered manufacturers
Defense articles and technical data that foreign persons, including your own employees and contractors, must never reach.
Subcontractors to primes
CUI flowed down through contract clauses, with CMMC requirements arriving on the next award.
Companies with a foreign subsidiary
Assembly, test or sales entities abroad that share the account but must stay walled off from controlled records.
AS9100 and precision component shops
Serial, lot and revision history that a prime’s quality team will audit unit by unit.
Ammunition and energetics producers
Lot-controlled, hazardous production where a quality hold has to trace forward and back through every lot.
Firearms manufacturers and distributors
Serialized production and ATF recordkeeping, covered in depth on our Firearms pages.
A point of view
NetSuite can support ITAR compliance. It can’t decide who sees your technical data.
NetSuite provides infrastructure capable of supporting ITAR compliance. Where controlled data lives, who can reach it and how you prove it afterward are still yours to decide. We settle that in discovery with one of two patterns, then lock down everything around it.
Keep it out. Controlled technical data and CUI stay in a separate, controlled repository. NetSuite holds a reference, not the data, which keeps the account’s compliance surface small.
Lock it down. When controlled data has to live in NetSuite, BSP Secure Encryption stores it encrypted and decrypts it only on an authorized user’s device.
Restrict the rest. Roles, subsidiary restrictions and segregation of duties keep foreign entities and foreign persons out of controlled records, and audit trails show who touched what.
BSP doesn’t certify compliance. That determination belongs to you and your compliance team. We build the architecture it rests on.
BSP SECURE ENCRYPTION
01 YOU CHOOSE WHICH FIELDS ARE ENCRYPTED
02 STORED AND SHOWN ENCRYPTED BY DEFAULT
03 PASSWORD + PERMISSION TO DECRYPT
04 DECRYPTED ONLY ON THE USER’S DEVICE
05 NEVER SAVED IN DECRYPTED FORM
06 RE-ENCRYPTED BEFORE EVERY SAVE
07 BUILT FOR ITAR + CMMC PATTERNS
What the account has to do
Six controls, designed in from day one.
These are the controls an export-control review or a prime’s audit tends to test. In NetSuite, each one is a design decision made during implementation, not a setting someone remembers to turn on.
Access by role, not by trust
Role-based permissions scoped to the records each job actually needs, with sensitive record types restricted rather than merely hidden.
Walls around foreign subsidiaries
Foreign entities share the account and the consolidation, while roles restricted by subsidiary keep their users out of controlled records.
Segregation of duties
No single user creates, approves and releases the same transaction, so the controls hold up when someone tests them.
Controlled documents and revisions
Drawings and specifications linked by reference or encrypted, with item revisions and document change orders so only the current revision reaches the floor.
Approved suppliers only
Purchasing limited to the vendors approved for each item, so controlled parts come only from qualified sources.
A record of who did what
Audit trails and record history for user activity and changes, with electronic signatures wherever an approval has to be attributable.
BSP IP Solutions
01 · CONTROLLED DATA
BSP Secure Encryption
Encryption inside NetSuite for the fields you specify, for regulated data the platform doesn’t natively protect to the standard your program requires.
CUI + CONTROLLED TECHNICAL DATA
ITAR · CMMC PATTERNS
DECRYPTED ON-DEVICE ONLY
02 · TRACEABILITY
Lot, serial and revision control
Extensions built natively in NetSuite that tie every unit to its supplier, its revision and its inspection results.
LOT MANAGEMENT
ITEM REVISION MANAGEMENT
APPROVED SUPPLIERS
INSPECTION ON RECEIPT + WO COMPLETION
03 · QUALITY RECORD
eQMS and history records
The quality suite trusted by FDA-regulated manufacturers, applied to the records an AS9100 audit asks for.
eQMS · NCR, CAPA, DCO
DEVICE + BATCH HISTORY RECORDS
ELECTRONIC SIGNATURES
EQUIPMENT MAINTENANCE + CALIBRATION
SHOP FLOOR TRACKER
Traceability, end to end
Follow one serial number through the account.
Traceability isn’t a report you run when the auditor arrives. It’s the record each step writes as the work happens, so the answer already exists when someone asks for it.
01 · Received
Lot or serial assigned at receipt from an approved supplier, with inspection results attached to the unit.
02 · Built
Consumed against a work order at the current item revision, with shop floor steps captured as they happen.
03 · Inspected
Inspected at work order completion. A failure opens a nonconformance, and a recurring one opens a CAPA linked back to it.
04 · Recorded
A device or batch history record collects the build, the inspections and the signed approvals for that serial.
05 · Shipped
The serial or lot rides on the fulfillment, so any customer traces back to a supplier lot, and any supplier lot traces forward to every customer.
Tell us what your auditor will ask to see.
Controlled technical data, a foreign subsidiary, CUI from a prime or an AS9100 audit. Bring the requirement, and we’ll show you the architecture that answers it.