Every PPAP element and quality document — drawings, DFMEAs and PFMEAs, control plans, MSA studies, dimensional results, work instructions and the PSW — lives on the platform's document subsystem. Each is uploaded, versioned, served and moved through the Accepted / Rejected / Deviation lifecycle, and linked to the item it belongs to. That turns a PPAP "folder" into a managed, auditable, ISO-controlled package — not a loose set of files on a shared drive.
Document control has two jobs: hold every PPAP element and quality document, and move each through a controlled approval lifecycle. On the shared platform both are the same subsystem — the drawing you upload, the FMEA a change re-versions and the PSW you submit are one linked package, not files scattered across drives and mailboxes.
Because every quality document sits on the same subsystem, each element attaches to the item the next step reads. The drawing, the FMEA, the control plan and the PSW are all reachable from the part they belong to.
Every item below is a native part of the shared document engine — the drawing, the FMEA, the control plan and the PSW are the same linked documents read across the quality system, not files copied into a separate archive.
Fast Quality doesn't keep a bolt-on file store. Drawings, DFMEA/PFMEA, control plans, MSA studies and the PSW all upload through the platform's document subsystem — the same upload and download handlers as every document — and each attaches to the record it belongs to. A drawing lives against its item, an MSA study against its gauge, and a control plan stays reachable from the FMEA and control plan it came from. Every change makes a new version.
A controlled document isn't live because someone uploaded it — it's live because it was approved. Every PPAP element and quality document is moved through the Accepted / Rejected / Accepted-Under-Deviation lifecycle: an element is only released at Accepted, a rejected one is sent back for correction, and one accepted under an approved deviation is time- or quantity-bound. It's the same status decode inspection and rejection use, so the whole quality system speaks one status language.
When drawings sit on a drive, FMEAs in a mailbox and the PSW in a folder, the package is only as good as the person who remembers where things went — and the customer or auditor always asks for the one element no one can find. On the shared document engine there is no side archive: the drawing, the FMEA, the control plan, the MSA study and the PSW are the same linked documents, reachable from the item. The document-status view shows the package is complete, and because it's version-controlled, the element served at audit is exactly the one that was approved. It's ISO 9001 clause 7.5 controlled-document management without a separate system.
Every PPAP element from design record to PSW is a controlled document on the subsystem, linked to the item — a managed package, not a folder.
Item drawings, DFMEA/PFMEA, control plans, MSA studies and work instructions upload through the same handlers and attach to the item or gauge.
Every controlled document is moved through Accepted, Rejected or Accepted-Under-Deviation — the same status decode the quality system uses.
The Part Submission Warrant summarises the package at its submission level — ready only when the elements are Accepted.
A change or CAPA re-versions the affected document and re-approves it, triggering re-PPAP where required.
A per-item view shows which elements are present, current, open or rejected — so a package's completeness is visible before submission.
In a 30-minute demo we'll upload PPAP elements against a part, version them, move each through Accept / Reject / Deviation, and submit the PSW — all as one auditable, version-controlled package.
