A Tier 1 supplier is introducing an assistance system on three pre-assembly lines. The evaluation went smoothly, the user interface is impressive, and the workers are getting the hang of it. Fourteen months later, an OEM reports a field issue with an assembly. The question isn’t how good the instructions looked. The question is which vehicles are affected. The system can document every assembly step, but only by order, not by serial number. The scope of the recall cannot be properly defined, so it is expanded to cover the entire production period, and the costs end up being many times higher than they would have been with component-specific tracking.
That is the difference between a good operator assistance system and one that is suitable for automotive production. Both guide the operator. Only one stands up to the chain of evidence required by this industry.
This article describes the seven requirements unique to automotive production, compares system classes based on their suitability for assembly line operations, and explains why the requirements profiles of OEMs, Tier 1, and Tier 2 suppliers differ.
KEY POINTS AT A GLANCE
|
IN SHORT
|
The search for the best worker assistance system for automotive production regularly leads to lists of vendors. These lists are of little help for a structural reason: There is no uniform use case in this industry against which systems could be ranked.
A main assembly line at a vehicle manufacturer’s plant operates with cycle times of less than one minute, a high variety of variants, and material supply planned down to the second. A pre-assembly line at a Tier 1 supplier operates with longer cycles, more inspection steps per subassembly, and a requirement to provide proof to the customer, which determines the scope of documentation. A rework station operates without a fixed cycle time but with maximum process variability. The same system may be the right choice in one of these three cases and the wrong one in the other two.
It therefore makes sense to follow the reverse order. First, the requirements profile is determined; then, system classes are ruled out; and only at the end are specific systems evaluated. Four factors determine this profile.
The cycle time determines how much interaction the system may require from the worker. The number of variants determines whether processes are configured or programmed. The required level of documentation determines whether data must be recorded per order, per batch, or per serial number. And the position in the supply chain determines who sets the requirements and how strictly they are verified.
The general selection criteria for operator assistance systems—namely, integrability, configurability, the hardware’s suitability for the workshop, and the auditability of the documentation—apply across all industries and are discussed in detail in the article on how to recognize a good operator assistance system. This article builds on that and focuses exclusively on the additional layer required in automotive production.
In automotive production, what matters is not how well a system guides workers, but how reliably it provides information in real-world situations.
Amadeus Lederle, Chief Technology Executive, CSP Intelligence GmbH
The following seven requirements stem from the industry’s framework of standards and contracts. They are the reason why systems that work well in other industries fail here.
| No. / Requirement | Source | What the system must be able to do |
|---|---|---|
| 1 · Component-level traceability | IATF 16949 Section 8.5.2, OEM specifications | Assign each step to the serial number, not to the order or the lot |
| 2 · Screw-fastening verification by class | VDI/VDE 2862 Part 1 | Tool approval only after correct pre-tightening; recording of torque and angle of rotation; lockout in case of non-conformance |
| 3 · Cycle time capability | Main line cycle time, often under 60 seconds | Guidance without additional confirmation dialogs; status changes occur immediately |
| 4 · Build-to-Order Variant Control | Order-based production at the OEM | Variant retrieved from the production order; no selection required by the operator |
| 5 · Recall delimitation at the push of a button | Product liability, field monitoring obligation | Narrow down the affected serial numbers based on the cause of the defect, not the production period |
| 6 · Auditability in process audits | VDA 6.3, IATF certification audit | Proof of process compliance for each component without having to reconstruct data from multiple systems |
| 7 · Retention period spanning decades | Directive (EU) 2024/2853, IATF 16949 Section 7.5.3.2.1 | Store data in a format that outlasts the assistance system itself |
Three of these requirements deserve closer examination because they are most frequently underestimated in selection projects.
Requirement 1 is the actual exclusion criterion. IATF 16949 requires, in Section 8.5.2, traceability that allows the affected scope to be delineated in the event of a defect. Systems often document data by production order because this information is available from the MES without additional effort. This is sufficient for management purposes. However, it is not sufficient for containment: If an order comprises 2,000 assemblies and the defect affects 20 of them, 2,000 will be quarantined. How to establish robust traceability in production is described elsewhere.
Requirement 3 never appears in presentations. A system that runs smoothly in the conference room behaves differently on a production line with a 50-second cycle time. Every confirmation dialog, every loading process, and every instance of network latency adds up. Expect a strict limit: Anything the worker must operate in addition to the assembly process must not affect the cycle time. Otherwise, it will be bypassed, and a bypassed system documents nothing.
Requirement 7 conflicts with the product lifecycle of software. The new EU Product Liability Directive (EU) 2024/2853, to be implemented by December 9, 2026, extends liability for consequential damages to twenty-five years. No driver assistance system on the market has a documented operational history spanning this period. The implication for selection: The supporting data must not remain in the driver assistance system but must be transferred to a long-term, secure archive. The article on recall management and recall costs illustrates the cost of an uncontained recall.
|
CHECKLIST · FREE How secure are your production processes?A quick self-assessment for quality and production managers: Identify strengths, risks, and opportunities for optimization in just a few minutes. |
Instead of comparing product names, it’s worth comparing system classes. There are five classes used in automotive production, and their suitability varies significantly depending on the manufacturing area.
| System Class | What It Does | Main production line in a continuous cycle | Pre-assembly | Inspection and rework |
|---|---|---|---|---|
| Paper or PDF on screen | Displays the instructions, does not record anything | Unsuitable; no verification and no documentation | Unsuitable for steps requiring documentation | Limited use; for reference only |
| Pick-by-Light and Pick-by-Vision | Ensures material retrieval, not assembly | Suitable as a supplement, not as an assistance system | Suitable for order picking | Not applicable |
| Digital work instructions | Shows steps specific to the variant, documents confirmation | Conditionally suitable; instructions can be skipped | Suitable for a limited scope of verification | Suitable for documented rework |
| Operator assistance with verification | Guides and locks the tool and material; records each step | Suitable when configured for cycle time optimization | Well-suited; this is where the greatest benefit lies | Well suited; inspection dialogs without cycle time pressure |
| MES-integrated operator assistance | As above, with additional bidirectional integration with order and quality data | Well suited; variant comes from the order | Well suited; verification data is fed back | Well suited; rework is assigned to the component |
Two conclusions follow from this. First: The line between digital work instructions and operator assistance is the point that determines suitability for the automotive industry. An instruction shows what needs to be done. An assistance system checks whether it has been done and prevents the task from being passed on if it hasn’t. For safety-critical connections, only the second option is reliable.
Second: The choice is rarely the same across the entire plant. A tiered architecture makes sense: MES-integrated assistance at stations requiring documentation, digital work instructions at non-critical stations, and “pick-by-light” as a supplement in order picking. It is crucial that all areas write to the same database; otherwise, gaps will arise in the audit trail. The article on worker assistance systems with MES integration illustrates exactly what role the MES connection plays in this context.
HOW TO TELL IF A SYSTEM IS NOT AUTOMOTIVE-COMPATIBLE
|
A company’s position in the supply chain significantly affects its requirements profile. Those who overlook this distinction evaluate systems based on the wrong criteria.
| Criterion | OEM | Tier 1 | Tier 2 |
|---|---|---|---|
| Primary Requirement | Variant control on a per-cycle basis | Chain of evidence for the customer | Cost-effectiveness with a high number of variants |
| Typical cycle time | Less than 60 seconds on the main line | One to several minutes per assembly | Highly variable, small batch sizes |
| Traceability depth | Vehicle and serial number reference | Assembly and serial number reference, specified by the customer | Batch- to serial-number reference, depending on the specifications |
| Critical cost factor | Production line downtime due to system failure | Complaint and return costs | Variant management and training |
| Key Selection Criteria | Latency, reliability, redundancy | Level of detail, auditability, archiving | Configurability without a service provider |
| Most Common Selection Mistakes | Prioritizing feature set over cycle time | Customer requirements reviewed only after selection | License price calculated instead of total costs |
For the OEM, system availability is the most critical factor. An assistance system that halts the production line costs more per minute than the annual license fee. Redundancy, local buffering in the event of a network failure, and defined behavior during a malfunction must therefore be included in the specifications, not addressed during the operational phase.
For Tier 1 suppliers, the order is reversed. Here, the customer’s specifications determine what must be documented, and these specifications are negotiated before the system selection process begins. The most common mistake in this group is selecting the system and then realizing that a required level of audit trail cannot be supported. Read the documentation requirements of all relevant customers before writing a requirements specification.
For Tier 2, configurability is crucial. With many variants and small batches, any system that requires a service provider for every change becomes uneconomical. In this case, don’t just calculate the initial purchase cost—consider the cost of managing variants over five years.
Hardly any other area demonstrates an assistant system’s suitability for the automotive industry as clearly as bolting. VDI/VDE 2862 Part 1 classifies bolting scenarios based on the risk posed by a failure of the joint. Class A includes joints whose failure directly endangers people; Class B includes those resulting in functional failure or consequential damage; and Class C includes all others. The minimum requirements for tools, monitoring, and documentation are derived from the assigned class.
For the driver assistance system, this translates to three specific capabilities.
The screwdriver is not released until the previous step has been completed correctly, and the correct program has been selected for the fastening operation. A message on the screen indicating which program to select does not meet this requirement. For Class A joints, physical interlocking is the difference between a safety measure and a recommendation.
Torque, angle of rotation, time, tool ID, and operator ID are part of the documentation, assigned to the component’s serial number and the fastening location. Only this assignment allows for later analysis to determine whether a pattern in the fastening curves indicates a systematic problem.
A failed tightening operation must not end as a mere note. The system must block the release of the component and trigger the defined rework process, documented with the cause and result. Systems that merely log NOK cases create the most uncomfortable of all situations during an audit: a documented error without a documented response.
The detailed requirements and the classification of the categories are broken down in the article on fastening categories according to VDI/VDE 2862.
|
WHITE PAPER · FREE Ready for audits at any time. In minutes instead of weeks.Access the complete production history for any product at the touch of a button, immediately narrow down the scope of the issue in the event of a complaint, and pass audits without a special project. |
The introduction of new products in automotive production differs from other industries primarily in terms of risk: A configuration error doesn’t halt a workbench—it halts an entire production line.
Choosing the Right Pilot Line. The common instinct is to start with the simplest station. This yields quick results but provides little insight. It makes more sense to choose a station of moderate complexity, with at least one screw connection that must be verified and a realistic variety of variants. Only there can you determine whether the system meets the requirements profile.
Plan for parallel operation. During the first phase, the existing process and the assistance system run in parallel. This requires additional effort but prevents a configuration error from leading to a gap in verification. Define in advance which process takes precedence in the event of a conflict.
Rollout across locations. As soon as the second location is added, a configuration project becomes a governance issue. Who maintains the process library? Which processes are globally mandatory, and which can be adapted locally? Without this clarification, variants of the same process will emerge within a year that can no longer be compared.
Language and clarity. In internationally staffed assembly teams, the language version is not merely a convenience feature. Verify whether processes are managed multilingually without creating a separate process for each language. Otherwise, the maintenance effort multiplies with each language.
Involve the works council and data protection officers early on. A system that records worker identification and timestamps for each step is relevant to co-determination. If you wait until after the selection process to begin these discussions, you’ll lose months. The most effective approach is a clear distinction: The data is used for component verification, not performance evaluation, and this intended use is technically ensured.
A realistic timeline allows two to three months for the requirements profile and selection process, and another two to three months for the pilot operation on a single line. The rollout to additional lines proceeds much more quickly afterward because the process library is already in place.
CSP’s Manufacturing OS combines process data management, operator guidance, tool inspection, and long-term archiving into a single platform. The PGX module handles operator guidance within this platform.
PGX guides the operator through the assembly process in a step-by-step, variant-driven manner. The variant is derived from the production order, not from a selection list. Each step is recorded with a timestamp and operator identification and is assigned to the component’s serial number, not the order. Critical steps are interlocked: tools and material containers do not release until the previous step has been correctly completed, and the transfer of a component is blocked in the event of a non-conformance (NOK).
For screw connections, PGX integrates screwdrivers and testing equipment regardless of manufacturer and records torque, rotation angle, and program ID for each screw connection point. Through the shared database with the QST module for tool inspection and CHRONOS for long-term archiving, documentation remains available for the required periods, even if the assistance system itself is replaced at some point.
PRACTICAL TIP: PGX
|
CSP has been working with German automakers and suppliers for over three decades. Users include the BMW Group, MAN Truck & Bus, and Mercedes-Benz AG, among others. The Automotive and Commercial Vehicles page provides an overview of the industry solution.
A product-specific ranking can be misleading in this industry because use cases vary widely. Suitable systems are those that record data by serial number, secure fastening operations according to VDI/VDE 2862 via tool locking, retrieve the variant from the production order, and are bidirectionally connected to the MES and quality data systems. For the main production line, cycle time capability is also a factor; for suppliers, it’s the level of traceability specified by the customer. First determine this profile; then you can make a reliable comparison of systems.
There is no standard that directly regulates operator assistance systems. The requirements they must meet are decisive: IATF 16949 requires, in Section 8.5.2, traceability that allows for isolation in the event of a defect, and, in Section 7.5.3.2.1, the retention of records. VDI/VDE 2862 Part 1 specifies the minimum requirements for bolted joints by risk class. The VDA 6.3 process audit verifies whether process compliance can be demonstrated. In addition, there are customer-specific requirements from the OEMs’ specifications.
A digital work instruction displays the correct work step for the specific variant and, if applicable, documents the operator’s confirmation. An operator assistance system verifies the execution and intervenes before an error is passed on. Specifically, this means: Tools and material containers are released only after the correct step has been completed, and the transfer of a component is blocked if a check step is failed. For safety-critical assemblies in automotive production, only the second approach is reliable, because a visual提示 during the production cycle can be overlooked.
Because it determines the costs in the event of a field issue. If tracking is done per production order and a defect occurs in only a few assemblies, the affected scope cannot be narrowed down. The entire order or the entire production period is then shut down. Section 8.5.2 of IATF 16949 explicitly requires traceability that allows for this differentiation. A system without serial number tracking results in costs many times higher than what could have been avoided in the event of a serious incident.
There is no normative threshold, but there is a practical rule: Interaction with the system must not significantly affect the cycle time. For cycle times under sixty seconds, this means that status changes must occur immediately and no additional confirmation dialogs should be included that do not serve a safety purpose. Test the response time during a pilot run on an actual production line, not in a demo. If a system is perceived as a hindrance, it will be bypassed—and a bypassed system provides no verification.
Yes, under one condition: The processes must be configurable without an external service provider. With a high number of variants and small batches, the main effort lies not in implementation but in ongoing variant maintenance. A system in which every new variant triggers a project becomes uneconomical in this environment. A system in which the company’s own quality or manufacturing department creates new processes independently is where it truly shines.
IATF 16949 requires, in Section 7.5.3.2.1, that records be retained for the duration of active series production plus one calendar year, unless the customer specifies otherwise. OEM specifications regularly exceed this requirement, often requiring retention for fifteen years. The new EU Product Liability Directive (EU) 2024/2853, to be implemented by December 9, 2026, extends liability for delayed damages to twenty-five years. These time periods exceed the service life of most assistance systems. The documentation should therefore be stored in a long-term archive, not in the driver assistance system’s database.
|
LIVE DEMO · FREE Experience PGX operator guidance in the Manufacturing OSSee how serial number tracking, tool locking, and screwdriving case verification work together in real time during a real assembly process. Thirty minutes, no preparation required. |