Ensuring consistency and reliability in production parts

PPAP (Production Part Approval Process)

Coordinate supplier submissions, customer requirements, document revisions, and review decisions in one PPAP package.

PPAP module icon
Bring PPAP Requirements and Evidence Together
Trackmedium eQMS helps teams organize production-part approval around the requirements for each submission. Build reusable requirement and type profiles, select submission levels when needed, and assign internal or supplier contacts to prepare the evidence. Keep part versions, engineering-change details, uploaded files, review decisions, and corrections together from initiation through completion.

Reusable Requirements and Submission Levels
Define Requirement Profiles with clear names and help text, then group them in PPAP Type Profiles. Use level-specific requirements or one common requirement set. Load the selected requirements into each submission and add customer-specific instructions where needed. Profile settings control whether owners can change the requirement selection.
Internal and Supplier Submission Ownership
Choose an internal department or an external manufacturing supplier and assign the responsible contact. Use enabled supplier access for direct participation, or assign a company associate to coordinate on the supplier's behalf. Keep the submission owner responsible for reviewing the package.
Part Versions and Engineering-Change Context
Record part number, name, version, engineering change level, customer part number, drawing references, related parts, and additional engineering changes. Select material and customer profiles when those modules are enabled. Keep the reason for submission and the part context with the approval evidence.
Requirement-Linked Evidence and Revisions
Associate each uploaded attachment with one or more submission requirements. Keep the uploader, upload date, and revision number visible. Replace files while retaining revision history, and view removed attachments when needed so supporting evidence can be reviewed in context.
Document Review and Correction Cycles
Review individual attachments and record Accepted, Rejected, or Cancelled outcomes. Return the package to its responsible contact for corrections and resubmission. The package cannot move to Completed while any attachment remains Open; editing during correction follows the attachment's status.
Submission Results and Final Package History
Record the reviewed results, design-requirement decision, sample shipment information, and overall comments. Capture restricted-substance responses and IMDS references where applicable. Finalized submissions become read-only, while assigned-work and submission views keep open and completed packages visible.
Supports industry standards logo
Supports industry standards logo
Supports industry standards logo
Supports industry standards logo
Supports industry standards logo
Supports industry standards logo
Supports industry standards logo
PPAP Lifecycle at a Glance
These six activities include profile setup and the correction loop. The standard submission progresses through Initiated, In Progress, Under Review, and Completed, with Under Correction for returned packages and cancellation where available.
Define the Requirements Set up requirement guidance and type profiles, with submission levels where needed. Define the Requirements Set up requirement guidance and type profiles, with submission levels where needed.
Initiate the Submission Identify the part, source, owner, responsible contact, and reason for submission. Initiate the Submission Identify the part, source, owner, responsible contact, and reason for submission.
Prepare the Evidence Upload supporting documents and associate them with the selected requirements. Prepare the Evidence Upload supporting documents and associate them with the selected requirements.
Review the Package Evaluate attachments, record their decisions, and capture submission results. Review the Package Evaluate attachments, record their decisions, and capture submission results.
Correct and Resubmit Return the package for permitted corrections, then send it back for review. Correct and Resubmit Return the package for permitted corrections, then send it back for review.
Complete and Retain History Finalize the package after attachment decisions and retain the read-only submission. Complete and Retain History Finalize the package after attachment decisions and retain the read-only submission.
Built for Product and Process Quality Teams
Trackmedium's eQMS PPAP module helps product and process teams connect assigned work, part details, review evidence, and quality decisions.
Manufacturing and Supply Chains
Retain project or submission records, supporting files, part details, and decisions to support customer requirements and quality reviews.
  • Automotive and Tier Suppliers
  • Industrial Equipment
  • Electronics Manufacturing
  • Components and Subassemblies
  • Contract Manufacturing
Quality Planning Use Cases
Connect work across departments and suppliers with clear ownership and evidence your team can review in context.
  • Internal Part Submissions
  • Supplier Submissions
  • Customer-Specific Packages
  • Changed Part Versions
  • Correction and Resubmission
Why Trackmedium eQMS?
Trackmedium eQMS helps teams centralize quality data, automate work, and keep decisions traceable across the full quality system.
Make Submission Expectations Clear
Use repeatable profiles, requirement help text, levels, and additional instructions to explain the evidence expected for each package.
Keep Reviews and Corrections Accountable
Give preparation and review clear owners. Retain attachment outcomes and the correction loop so decisions and follow-up remain visible.
Preserve Part and Evidence Traceability
Keep part versions, engineering-change details, requirements, file revisions, and submission results together through completion.
Frequently Asked Questions
Can we define different PPAP requirements for each customer?
Yes. Requirement Profiles provide reusable names and guidance. PPAP Type Profiles group them into submission-level-specific lists or one common list. Submissions can include additional customer-specific instructions. Your team maintains these profiles to reflect the requirements for the customer, part, and submission.
Are submission levels mandatory?
No. A PPAP Type Profile can use submission levels or one common requirement set. When levels are enabled, selecting the level loads that profile's defined requirements. The profile also controls whether owners may change the requirement selection in created submissions.
Can internal teams and suppliers prepare submissions?
Yes. An internal submission names a department and responsible company contact. An external submission names a supplier and responsible contact. When supplier contacts do not have system access, a company associate can coordinate the submission on their behalf. Direct supplier participation depends on enabled access and permissions.
Can we attach FMEAs, control plans, and submission warrants?
Yes. Define these deliverables as submission requirements and associate the relevant uploaded files with them. Keep each file connected to the requirements it supports, preserve its revision history when replaced, and record the reviewer's decision alongside the submitted evidence.
How are document revisions and review decisions retained?
Attachments record the uploader, upload date, and revision number. Replacing a file retains its revision history, and removed files can be viewed with Show Removed. During review, the owner assigns Accepted, Rejected, or Cancelled outcomes. No attachment may remain Open when the submission moves to Completed.
What happens when corrections are required?
The owner can return the submission from Under Review to Under Correction, assigning it to the responsible contact. Attachments with Open status can be updated in that step; other attachment statuses remain protected. The contact then resubmits the package to the owner for another review.
Can we record material-declaration information?
Yes. During review, record restricted or reportable-substance responses, an IMDS submission reference, and details of other customer formats. Keep this information, explanations, and the supporting evidence with the package's review results.
What is the standard PPAP submission workflow?
The standard submission moves through Initiated, In Progress, Under Review, and Completed. Under Review can return it to Under Correction for resubmission, and cancellation is available at the supported steps. Completed submissions are read-only, preserving the finalized package and review results.
See more questions See less questions
Ready to Bring PPAP Evidence Together?
Keep requirements, supplier submissions, document revisions, and review decisions connected in Trackmedium eQMS.