Reference · VDA Guidelines, 3rd edition (PAM 4.1)
How a rating is reached
Scope first
Org-unit boundaries · processes · target level per process · process context (releases, components, inclusions). Ratings stay inside the context.
The assessment purpose is not part of the scope; the scope is defined to cover it.
No "not applicable" without the sponsor. Missing evidence is no reason to exclude a process; usually it means N.
Evidence
Sample along a path through the lifecycle; the assessor picks.
Plausibility: a work product created just before the assessment is not considered without a plausible reason; its history should match its update cycle.
Content: not a checklist; read for the right content, judged in context.
Each process on its own
A process is downrated only for its own weaknesses. Only BPs that refer to another process (consistency and traceability) carry weakness across. GEN.RL.1
Aggregation
| 1 | Rate each instance. |
| 2 | N0 P1 L2 F3; mean, or an explained weighted mean. |
| 3 | Round to nearest; exactly .5 rounds up. |
L,F → 2.5 → F · P,L → 1.5 → L · N,P,F → 1.33 → P
Rating rules
Three patterns: "shall not be downrated" · "shall be downrated" (≥ 1 step) · "not rated higher than". No rule algebra. A deviation needs a documented justification.
Traceability: TAC.RL.1 clusters OK · RL.2 manual OK · RL.3 no formal review record needed if pair work, spot checks or commit notes exist.
Weakness statement
What is missing · the traceable evidence · the process risk. Rules alone make a report invalid.
Sources
Guidelines Part 1, pp. 26–44; traceability rules pp. 58–60. Taught in Lesson 8.