Try it
Not a video and not a guided tour — the real application, already populated with a fictional organization so there's something to look at. Click every tab. Open a nonconformance, read a PEAR, change a due date. It's yours for as long as the tab is open.
Pick the one that looks like you
Each demo is a different aerospace business with its own process map, its own people, and its own scope. The differences aren't cosmetic: a distributor excludes clauses a machine shop can't, and a design house carries a whole clause the other two legitimately scope out.
Machines and assembles precision parts to the customer's drawing. Takes no design responsibility, so clause 8.3 is excluded with its justification on file. Purchasing is an activity inside Operations, because there's no purchasing manager.
Buys, stores and resells without altering the product. Purchasing is its own process with its own owner and metrics, and the scope excludes the design and production clauses it doesn't perform — each exclusion justified in the scope statement.
Designs and builds flight-control actuation components. Employs engineers, so Design & Development is a process of its own — and clause 8.3 is fully exercised, down to a released project with a fracture-critical output and a post-release change the customer was notified of.
What you're looking at
The application stores nothing in your browser — no accounts, no cookies, no local storage. Change whatever you like; a refresh puts it all back exactly as it was, and nothing you do is visible to us or to the next visitor.
The organizations, people, part numbers, suppliers and findings are all made up. No real customer's data appears anywhere on this site, and none ever will.
You're seeing the build as it stands, not a curated slice. A few clause areas aren't built yet and the site says which. If you find a hole, that's a real hole — tell us and it'll go on the list.
Each demo is a single file of about 1.3 MB and runs entirely in your browser, so it may take a moment on a slow connection — and works fine with no connection at all once it has loaded.
Where to start
Most evaluators go looking for the same records, so here's where they are. These are the ones that tend to separate a real aerospace QMS from a generic tool with the word aerospace in its name.
The landing tab, and the map every other module hangs off. Open a process and take its turtle diagram and SIPOC — a standing view, not an audit snapshot.
The real Form 3, with inputs, activities, outputs, interfaces and KPIs pre-filled from the process map rather than retyped, and effectiveness scored on the standard's own grid.
On First Article Inspection: one accepted, and one rejected after a tooling change with reverification required. The rejected one is what an auditor asks to see.
On Organizational Context: the clauses a distributor doesn't perform, each one excluded against a justification that gets written into the scope statement.
On Design & Development: planning against the standard's a–j list, categorised inputs, a critical design review authorizing progression, a fracture-critical output, and a change the customer was notified of.
On NCR / CAPA: containment, root cause, corrective action and the effectiveness check afterwards — the step most systems quietly skip.
Pilot program
Twenty-eight modules are already built and working. Pilot organizations get the system at no cost during development, direct input on what gets built next, and a migration path when the IA9100 revision lands.