A customer has filed a complaint about a component from this past spring. The first question comes to mind immediately: Which serial numbers were produced using the same screw-fastening program, at the same station, during the same shift? The quality manual explains how to handle such a case. The answer itself, however, is not listed there.
It lies in the process data, spread across the control system, the test bench, and the ERP system. This is precisely where it becomes clear whether QMS software was built for manufacturing or for document storage.
THE MOST IMPORTANT POINTS AT A GLANCE
|
IN A NUTSHELL
|
What is a quality management system (QMS), and what does QMS software do in manufacturing?
A quality management system, or QMS for short, encompasses the processes, responsibilities, and documentation that a company uses to ensure its products meet customer requirements and standards. ISO 9001:2015 is divided into ten sections. The actual requirements are outlined in sections 4 through 10, ranging from the organizational context to improvement.
QMS software is the tool that keeps this system running on a day-to-day basis. In many companies, this means that document control, audit planning, complaints, and corrective actions are stored in a database rather than in folders. In manufacturing, this is rarely sufficient. There, much of the quality evidence is generated directly on the production line—such as torque values, test results, operator confirmations, and material batches. QMS software for manufacturing must capture this data or import it accurately and assign it to the individual component.
The standard does not prescribe a specific software solution. However, it requires, in Section 7.5, controlled documented information; in Section 8.5.2, identification and traceability where required; and in Section 10.2, a regulated process for handling nonconformities and corrective actions. The more variants, stations, and serial numbers a manufacturing process has, the more difficult it is to meet these requirements without integrated software. The article on traceability in production demonstrates how traceability is implemented in practice.
| Value | Meaning | Source |
|---|---|---|
| 10 | Sections make up ISO 9001:2015; the requirements are outlined in sections 4 through 10 | ISO 9001:2015 |
| plus 1 year | Retain records beyond the duration of production and spare parts requirements | IATF 16949:2016, 7.5.3.2.1 |
| At least 2 years | Retain records from the date of approval, but for at least the service life of the medical device | ISO 13485:2016, 4.2.5 |
| December 9, 2026 | Implementation deadline for the new EU Product Liability Directive | Directive (EU) 2024/2853, Art. 22 |
How does a document-based QMS differ from a production-oriented QMS?
There are two different approaches on the market that fall under the same term. The document-centric QMS stems from the administration of the management system. It governs procedural instructions, schedules audits, tracks corrective actions, and manages training records. The production-oriented QMS operates at a deeper level: It records what actually happened at the workstation and links this data to the part’s serial number.
| Criterion | Document-Centered QMS | Production-oriented QMS |
|---|---|---|
| Core Object | Document, audit, action | Component with serial number or batch |
| Data source | Inputs from QM and functional departments | Control systems, screwdriving systems, test benches, operators |
| Typical question | Has the work instruction been approved? | What torque was used to fasten part X? |
| Strengths in the audit | System audit according to ISO 9001 | Product and process audit, complaint analysis |
| Limit | No information provided on the individual part | Does not replace document control |
The two approaches are not mutually exclusive. Many manufacturers use an existing system for manuals and audits and supplement it with a production-oriented data layer. Problems arise when a company purchases a document-centric tool and expects to achieve traceability at the part level with it. Such systems usually lack the necessary connection to the production line for this purpose.
|
Common mistake: The selection process begins with a list of features found online. Instead, review three actual customer complaints from the past twelve months and note which data was missing to resolve them. These gaps constitute your actual requirements specification. |
What features does QMS software for manufacturing really need?
The following matrix maps each function to what it must accomplish in mass production and which standard it addresses. It serves as a basic framework for a requirements specification.
| Function | What it must accomplish in manufacturing | Standard Reference |
|---|---|---|
| Document Control | Approval, versioning, and distribution of work instructions all the way to the workstation | ISO 9001, 7.5 |
| Traceability | Assigning process, inspection, and material data to the serial number or lot | ISO 9001, 8.5.2; IATF 16949, 8.5.2.1 |
| Process data acquisition | Automatically import measured values from control systems, screwdriving systems, and inspection systems | IATF 16949, 8.5.1.1 |
| Complaints and Corrective Actions | Contain the affected scope, analyze causes, and verify effectiveness | ISO 9001, 10.2; IATF 16949, 10.2.3 |
| Test Equipment Management | Monitor calibration status; lock out test equipment upon expiration | ISO 9001, 7.1.5 |
| Statistical Process Control | Maintain control charts, calculate process capability, issue warnings when trends are detected | IATF 16949, 9.1.1.1 |
| Archiving | Retain data in an audit-proof manner for the required period | IATF 16949, 7.5.3.2.1; ISO 13485, 4.2.5 |
| Audit Trail | Log changes to data and parameters with a timestamp and user identification | 21 CFR Part 11, § 11.10 (U.S. Medical Devices) |
There are many proven solutions for document control and corrective action management. In manufacturing, two factors make all the difference: traceability and process data acquisition. This is where it becomes clear whether the software can provide a response within minutes in the event of a complaint, or whether someone has to manually gather the data from the screwdriver control system, test bench, and ERP system.
Process Data as the Basis for Forecasts
Once process data is accurately and completely associated with the component, it can also be used for predictive purposes. Instead of merely documenting defects, the system identifies patterns that precede a defect. The article “What Is Predictive Quality” explains how this works. Without a reliable data foundation, however, this step remains theoretical.
How does QMS Software integrate with MES and ERP?
The roles can be clearly distinguished. The ERP system plans orders, materials, and costs. The MES controls and documents production execution. The QMS evaluates quality and directs the response to deviations. In practice, the systems overlap because many ERP systems include their own quality modules, and some MES systems manage inspection characteristics.
For the three systems to jointly address a customer complaint, they need a common identifier. In mass production, this is the serial number; in the process industry, it is the batch. If this key is missing, manual reconciliations in spreadsheets are required, and these are difficult to justify during an audit. The article on the data model for traceability describes which required fields a robust data model needs.
| System | Provides | Provides to the QMS software |
|---|---|---|
| ERP | Orders, materials, suppliers | Order number, material batch, supplier |
| MES | Work sequences, stations, times | Station, timestamp, operator, work step |
| Control and inspection system | Process parameters and measurements | Torque, Angle, Measured Values, Test Result |
Open protocols such as OPC UA and MQTT have become established for connecting to machines, while REST interfaces are typically used for communication with ERP and MES systems. For each data source, ask whether the provider supports one of these standards or if a custom project will be necessary. For more information on the architecture, see the article on MES and ERP integration in quality management.
Can the ERP system handle quality management?
ERP quality modules are often sufficient for incoming goods inspections, inspection plans, and quality reports. Things get more complicated when it comes to high-frequency process data from the production line. CSP customer projects show that screw-tightening curves, measurement series, and operator confirmations per component quickly generate volumes of data for which an ERP system is neither designed nor licensed. It therefore makes sense to divide the work: The ERP system remains in charge of orders and materials, while production-oriented QMS software manages the process and inspection data.
Which standards must QMS software cover (ISO 9001, IATF 16949, ISO 13485)?
Which standards are relevant depends on the industry. The table summarizes the requirements that directly affect software and data.
| Regulatory Framework | Scope | Software-Related Requirement |
|---|---|---|
| ISO 9001:2015 | Across all industries | Controlled documented information (7.5), traceability where required (8.5.2), corrective actions (10.2) |
| IATF 16949:2016 | Automotive industry and suppliers | Retention for production and spare parts requirements plus one calendar year (7.5.3.2.1), traceability (8.5.2.1), problem solving (10.2.3) |
| ISO 13485:2016 | Medical Devices | Validation of software used in the QMS (4.1.6), retention for at least the product’s service life, but not less than two years from release (4.2.5) |
| VDI/VDE 2862 Part 1 | Screw fastening technology | Classification of fastening applications into risk classes A, B, and C, with corresponding requirements for monitoring and documentation |
| Directive (EU) 2024/2853 | All manufacturers in the EU market | Software is considered a product; obligation to disclose evidence; implementation by December 9, 2026 |
For medical device manufacturers, there is an additional consideration that can easily be overlooked during the selection process: ISO 13485 requires, in Section 4.1.6, that manufacturers validate the software they use for their QMS on a risk-based basis. Therefore, be sure to request the vendor’s validation documentation as early as the selection phase. The article on software in medical technology explains how audit-proof archiving is implemented in the medical technology sector.
Product liability is a new requirement. Directive (EU) 2024/2853 replaces the 1985 regulation and must be transposed into national law by December 9, 2026. It applies to products placed on the market after this deadline and explicitly treats software as a product. For quality management, disclosure is particularly relevant: If a manufacturer fails to provide requested evidence, the product is presumed to be defective. Process data that no one can find thus becomes a liability risk.
The articles on the audit trail in manufacturing and on audit reports for auditors describe exactly what auditors want to see. You can find a four-week plan for establishing the audit trail in the article on audit readiness in manufacturing.
In an audit, a QMS is only as good as the answer it can provide regarding a single component.
How do you choose the right QMS software?
A comparison of quality management software provides an overview of vendors and their areas of focus. Before comparing vendors, it’s worth following a seven-step selection process. This ensures that you evaluate systems based on your own requirements rather than on brochures.
- Walk through complaint cases. Take three real-world cases and note which data was missing and how long it took to narrow down the cause.
- Review the data model. Ask which key links components, processes, inspections, and materials, and have the provider demonstrate this using one of your own parts.
- Clarify interfaces. List control systems, screwdriving systems, test benches, MES, and ERP. For each source, check whether the vendor connects to it as standard.
- Evaluate vendor independence. Many production lines use tools from multiple manufacturers. Software that only supports one brand leaves gaps.
- Define archiving. Clarify how the software retains data over the years without causing the production database to grow and slow down.
- Request proof of validation and an audit trail. Ask for validation documentation and an example of a change log.
- Agree on a pilot with acceptance criteria. Define measurable criteria in advance, such as the time required to resolve a complaint.
How much does QMS software cost, and when does it pay for itself?
There is no standard flat rate. The costs depend on how many stations and data sources are connected, which modules are needed, and whether validation is required. It’s more helpful to look at the individual cost components than to rely on a list price.
| Cost Category | Drivers | What to Look For |
|---|---|---|
| License or Subscription | Users, Workstations, Modules | Is billing based on users or connected stations? |
| Interfaces | Number and type of data sources | Standard protocols reduce the effort per station |
| Implementation | Process assessment, configuration | Agree on a fixed price for the pilot line |
| Validation | Regulated industries such as medical technology | Utilize the supplier’s existing validation documentation |
| Operation | Hosting, updates, archive storage | Include storage costs for the entire retention period |
To assess cost-effectiveness, it’s best to use your own figures: costs for rework and scrap, hours per complaint analysis, effort required for audit preparation, and blocked inventory as long as the affected scope remains unclear. If a complaint currently requires two days of data searching, this can be directly expressed in hours and tied-up inventory. The article on KPI Design for Quality Managers describes which metrics are suitable for this purpose. The article Quality Control in Manufacturing provides an overview of methods and the costs of defects in quality control.
How can the implementation be successful in 90 days?
The following breakdown is a process model for a pilot line. It assumes that the software has been selected and that the line provides its data electronically. For lines with many legacy systems lacking interfaces, the integration process takes longer.
| Timeframe | Objective | Result |
|---|---|---|
| Days 1 through 30 | Current State Assessment and Data Model | List of all data sources, defined keys, acceptance criteria |
| Days 31 through 60 | Integration and Configuration | Stations connected, inspection characteristics and limit values defined, roles set up |
| Days 61 through 90 | Parallel operation and acceptance | Claim process simulated in the new system; training completed; decision made regarding the rollout |
Be sure to plan for parallel operation. During this phase, old documentation and new software run side by side, and discrepancies between the two reveal where data points are missing or incorrectly assigned. Involve the operators early on. If a workstation suddenly requires a confirmation that no one needed before, an explanation is needed as to why. You can find more insights from digitization projects in the article on digital quality assurance in manufacturing.
How does CSP’s Manufacturing OS implement quality management in manufacturing?
CSP’s Manufacturing OS focuses on the production-related aspects of quality management. It integrates machines, processes, and quality data into a single system and works in conjunction with existing solutions for manuals and audits. The modules can be used individually or together.
- IPM for process data management: MES functions, ERP interfaces, and QMS workflows based on a shared database, with the serial number serving as a unique identifier, and connectivity via OPC UA and REST. Learn more on the IPM page , which covers modular quality management.
- QST for quality assurance and tool inspection in screwdriving technology.
- PG for digital operator guidance: step-by-step and variant-driven, with deviation logging including timestamps and operator IDs.
- CHRONOS for audit-proof long-term archiving with GoBD, MDR, and IATF-compliant storage. Departments can access archived data without an IT ticket.
CSP has specialized in manufacturing software since 1991 and operates independently of manufacturers, working with tools and controls from various suppliers. Users include the BMW Group, MAN Truck & Bus, and Stadler Rail. The case study from rail vehicle manufacturing shows how Stadler Rail ensures bogie assembly with digital operator guidance.
|
NEXT STEP Ensuring Audit-Ready Quality Data Before comparing providers, it’s worth taking a look at your own data. This white paper covers the entire process—from data collection at the workstation to archiving—and explains which questions your QMS software must answer during an audit. |
Frequently Asked Questions
What is a quality management system (QMS) in manufacturing?
A QMS in manufacturing encompasses the processes, responsibilities, and documentation that a manufacturer uses to ensure that its products meet the requirements. In addition to documents and audits, this includes the process and inspection data generated on the production line for each component.
What is the difference between QMS software and MES?
An MES controls and documents the execution of manufacturing—that is, work sequences, stations, and times. QMS software evaluates quality, manages inspection characteristics, and directs the response to nonconformities. Both systems require a common identifier, such as a serial number, so that they can jointly provide a response in the event of a customer complaint.
Which QMS software is suitable for the automotive industry?
For automotive suppliers, the software must meet the requirements of IATF 16949, particularly traceability as specified in Section 8.5.2.1, problem-solving as specified in 10.2.3, and the retention of records as specified in 7.5.3.2.1. In fastening technology, the classification according to VDI/VDE 2862 Part 1 also applies. In practice, a direct connection to fastening systems and test benches is important.
Is QMS software required for ISO 9001?
No, ISO 9001 does not prescribe any specific software. It requires controlled, documented information; traceability where required; and a regulated approach to corrective actions. However, in manufacturing operations with many variants and serial numbers, these requirements can hardly be met economically without software.
How long must quality data be retained?
That depends on the standards. IATF 16949 requires retention for the duration of production and spare parts requirements plus one calendar year, unless the customer or regulatory authority specifies otherwise. ISO 13485 requires retention for at least the service life of the medical device, but no less than two years from the date of approval.
Can an ERP system handle quality management?
ERP quality modules are often sufficient for incoming goods inspections, inspection plans, and quality reports. However, an ERP system is generally not designed to handle high-frequency process data from the production line, such as screw-tightening curves and measurement series for each component. A division of labor between the ERP system and production-oriented QMS software has proven effective.
How long does it take to implement QMS software?
For a pilot line whose equipment provides data electronically, a three-phase approach spanning approximately 90 days is a realistic plan: current state assessment, integration, and parallel operation with acceptance testing. Legacy equipment without an interface extends the integration process.
How does the new EU Product Liability Directive affect quality management?
Directive (EU) 2024/2853 must be implemented by December 9, 2026, and applies to products placed on the market after that date. It treats software as a product and provides that a defect is presumed if a manufacturer fails to disclose requested evidence. Process data that can be quickly retrieved thus becomes part of liability preparedness.
Sources and Standards
- ISO 9001:2015, Quality Management Systems—Requirements, Sections 7.1.5, 7.5, 8.5.2, and 10.2
- IATF 16949:2016, Requirements for Quality Management Systems for Automotive Production and Replacement Parts, Sections 7.5.3.2.1, 8.5.1.1, 8.5.2.1, 9.1.1.1, and 10.2.3
- ISO 13485:2016, Medical Devices—Quality Management Systems, Sections 4.1.6 and 4.2.5
- VDI/VDE 2862 Part 1, Minimum Requirements for the Use of Fastening Systems and Fastening Tools
- U.S. FDA, 21 CFR Part 11, Electronic Records; Electronic Signatures, § 11.10
- Directive (EU) 2024/2853 on Liability for Defective Products, Art. 2 and Art. 22 (EUR Lex, CELEX 32024L2853)
