Records built by operators as they declare, from raw lot to finished part, with certificates attached at every transformation.
Control plan on the part, measured values captured at the step, qualification documents attached to the order.
Material the customer sends stays theirs, consumed against their program and reconciled whenever they ask.
Long lead times and a single qualified source, netted against every order that depends on them.
Treatment and inspection tracked as steps on your own order, with their lead times and their paperwork.
Affected quantity segregated out of available stock, rework or concession followed through to close-out.
Core modules
Integration engine
No. AS9100 is a certification you hold, not a product you buy, and any vendor selling it as software is selling you something else.
What Bonx does is hold the records an auditor asks to see: the control plan on the part, measured values captured at the step, genealogy from raw lot to finished part, and nonconformance followed to close-out. The evidence exists because production happened, not because someone assembled it the week before the audit.
No, and be careful with anyone who says yes. ITAR is about who may access controlled technical data and where it lives, which is an infrastructure and personnel question before a software one. We've written about what ITAR and CMMC actually ask of a manufacturer.
Same answer, same reasoning. CMMC compliance software is not a category an ERP can occupy on your behalf: the certification covers how your organization handles controlled unclassified information, across systems we don't supply. Where Bonx is relevant is that it's one of the systems in scope, so how it's deployed and who can reach it are part of the conversation.
Yes. The control plan sits on the part, measured values are captured at the step as the work happens, and qualification documents attach to the order, so the pack gets assembled from what production already recorded. Dedicated first article inspection software exists because most ERPs make you rebuild all of that alongside the job. If you produce AS9102 forms, Bonx holds the underlying data those forms are filled from.
Yes, part by part. Each part is its own lot, with its raw material, every transformation, and the certificates attached along the way, resolvable in both directions years later.
Per part, yes. Each article has its qualified sources with their part numbers, prices and lead times, and one is the default, so replenishment proposes an approved source rather than whoever someone remembers, and a purchase suggestion can't be turned into an order against a supplier that isn't on the part.
It stays theirs, and it stays separate. What the customer sends is received into its own location under their program, so it never mixes with material you bought or lands in your inventory value. It's consumed against their parts like any other component, so their material shows up in the genealogy of what you ship back — and what came in, what went into parts, what was scrapped, and what's still on the shelf is there whenever they ask.
Yes, as steps on your own order rather than gaps in it. Each one has a date out, a date back, and the paperwork that travels with the parts, so a delay at a Nadcap-approved processor shows up as a delay on the program.
Bonx invoices natively, including legal gap-free numbering, line-level tax, the PDF, and e-invoicing where it's legally required.
That said, Bonx is not a finance ERP. We think manufacturing ERP and finance ERP should stay separate, and Bonx is built that way on purpose. There is no general ledger, no accounts payable or receivable, no bank reconciliation, and no financial close. The coded invoice goes to your accounting tool, which posts it and keeps the books.
