Printer-friendly version
English version of VDA dictionary


Browse the glossary using this index

Special | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ALL

Page:  1  2  (Next)
ALL

R

R-parts

Reference to a VDA publication (if the definition is specific to a particular publication, different from it, or complementary to an applicable standard): Robust manufacturing process.

Range of performance levels

Reference to a VDA publication (if the definition is specific to a particular publication, different from it, or complementary to an applicable standard): VDA volume 13 .

Record

Document stating results achieved or providing evidence of activities performed.

Regulatory (feedback) circuit

Reference to a VDA publication (if the definition is specific to a particular publication, different from it, or complementary to an applicable standard): Robust manufacturing process.

Release

Permission to proceed to the next stage of a process.

Remedy action

See Corrective action.

Repair

DIN EN ISO 9000:2005. Reference to a VDA publication (if the definition is specific to a particular publication, different from it, or complementary to an applicable standard): VDA volume 6.2 .

Repeated defect (0 km)

Reference to a VDA publication (if the definition is specific to a particular publication, different from it, or complementary to an applicable standard): Standardised complaint process.

Repeated defect (site/operation)

1. A complaint has already been filed for the same part (base: customer's part number). 2. The complaint has been filed with the same supplier (base: contractual relations between a customer and a supplier). 3. Both complaints demonstrate the same symptoms (base: customer's description of a defect). 4. The first complaint regarding presented combinations has already been closed. 5. The date of part production (not vehicle approval date) where the defect has been identified is later than an implementation date of an action in stage D6-action.

Repeated use

Reference to a VDA publication (if the definition is specific to a particular publication, different from it, or complementary to an applicable standard): VDA volume 13.

Reporting

Regular, formalised reporting across interfaces (hierarchical) of various levels is used to inform both the management and employees. Especially, the actual performance, deadlines, costs and potential or actual issues need to be reported and monitored.

Requirement

Need or expectation that is stated, generally implied or obligatory.

Responsibility for product

Obligation of a manufacturer or other subject to remedy damages, both to property and others, caused by a product to people.

Review

Activity undertaken to determine the suitability, adequacy and effectiveness of the subject in matter to achieve established objectives.

Rework

Action on a nonconforming product to make it conform to the requirements.

Rinse liquid

Analysis-relevant testing liquid used to remove and collect particles potentially caught on the tested object or equipment during extraction.

Risk

Possibility that an event will occur resulting in human or material loses or damages, or jeopardising the achievement of an objective. When considering a risk, such matters as the likelihood of the occurrence of an event resulting in damages or loses are considered, as well as timely identification and expected extent of the damages. The risks associated with software design are significant project or process risks that shall be monitored, assessed and controlled in duration of the project.

Risk estimation/management

Risks shall be forecasted and estimated (based on the likelihood of the occurrence and extent of damages, often expressed in possible costs). Technical, economical, political and social/cultural risks are assessed. It is important to try avoiding risks, minimise them or a decision needs to be made as to which risks are acceptable. Methods such as FMEA or checklists are used to do that.

Root cause (causes)

Root cause is a cause that upon repeated questioning: “Why did the nonconformity/unexpected event occur?” leads to no other lower-level structure; it is often perceived as the “root” of nonconformity (fault).

Run@rate

Reference to a VDA publication (if the definition is specific to a particular publication, different from it, or complementary to an applicable standard): Robust manufacturing process.

Page:  1  2  (Next)
ALL