Page review information
Edition covered
ISO 13849-1 — 2023 (Ed. 4)
Content status
Reviewed
Coverage
Clauses 4-7 plus Annex A and CCF; worked example included. PLr attribution, PL e band and validation-method claims corrected July 2026. Numeric PL/PFH bands still to be checked against the published Table 2
Last reviewed
August 2026
Primary reference
The official published standard — required for final decisions

Confirm the governing edition, jurisdiction, and project-specific requirements before applying anything on this page.

Quick Start


Standard Overview

| Field | Value | |——-|——-| | Standard ID | ISO 13849-1 | | Edition | 2023 | | Publisher | International Organization for Standardization (ISO) | | Jurisdiction | Global; harmonized under EU Machinery Directive and Machinery Regulation 2023/1230 | | Scope | Safety-related parts of control systems — PL determination and verification | | Repository | rag/international/functional_safety/iso_13849_1/ | Purpose: ISO 13849-1 provides requirements for design and validation of safety-related parts of control systems (SRP/CS). The standard uses Performance Levels (PLa–PLe) to quantify the ability of a safety-related control system to perform a safety function. It covers electromechanical, electronic, and programmable electronic systems, as well as pneumatic and hydraulic safety elements (via ISO 13849-2 for validation methods).


PLr Determination — ISO 13849-1 Annex A Risk Graph

PLr (required Performance Level) is determined from the risk graph in ISO 13849-1 Annex A — this standard, not ISO 12100 — using three parameters: S (severity), F (frequency/exposure), P (possibility of avoidance).

Carry out the machinery risk assessment per ISO 12100 first: it identifies the hazards and supplies the risk estimation the S/F/P parameters encode. ISO 12100 does not itself output a PLr. (Designs taking the IEC 62061 route determine a required SIL by that standard’s own method instead.)

S F P PLr
S1 (reversible) F1 (seldom) P1 (possible) PLa
S1 (reversible) F1 (seldom) P2 (scarcely possible) PLb
S1 (reversible) F2 (frequent) P1 (possible) PLb
S1 (reversible) F2 (frequent) P2 (scarcely possible) PLc
S2 (irreversible) F1 (seldom) P1 (possible) PLc
S2 (irreversible) F1 (seldom) P2 (scarcely possible) PLd
S2 (irreversible) F2 (frequent) P1 (possible) PLd
S2 (irreversible) F2 (frequent) P2 (scarcely possible) PLe

Note: This table represents the ISO 13849-1 Annex A risk graph. The normative source is the graph itself — borderline cases may permit one-step adjustment with documented justification. PLr cannot be assumed or guessed; it must be derived from a documented risk assessment.


PL Levels and PFHd

PL PFHd Range Typical Application
PLa ≥ 10⁻⁵ /hr to < 10⁻⁴ /hr Very low risk; auxiliary functions, simple indicators
PLb ≥ 3×10⁻⁶ /hr to < 10⁻⁵ /hr Low–medium risk; simple single-channel protections
PLc ≥ 10⁻⁶ /hr to < 3×10⁻⁶ /hr Medium risk; infrequent-access guarding, basic interlocks
PLd ≥ 10⁻⁷ /hr to < 10⁻⁶ /hr High risk; E-stop, light curtains, guard interlocks on most industrial machinery
PLe ≥ 10⁻⁸ /hr to < 10⁻⁷ /hr Highest risk; collaborative robot nearest-person zones, some specialized press guarding

PLd is the level most industrial machinery designers target. PLe adds significant architecture cost (Category 4) and should be confirmed by risk assessment before committing.


Design Parameters

Parameter Definition Levels / Values How to Determine
Category (B, 1–4) Architecture type — defines fault tolerance and detection capability B, 1, 2, 3, 4 Selected based on PLr and fault tolerance needed (Clause 6)
MTTFd Mean Time To Dangerous Failure — per channel reliability Low (<10 yr), Medium (10–30 yr), High (30–100 yr) From manufacturer B10d datasheet data; or Annex C/D default tables
DC Diagnostic Coverage — fraction of dangerous failures detected None (<60%), Low (60–90%), Medium (90–99%), High (≥99%) From diagnostic measures implemented; Annex E reference values
CCF Common Cause Failure resistance — scored 0–100 Must score ≥ 65 for Categories 2, 3, 4 Annex F scoring: separation, diversity, environment, competence

Critical notes:


Category Architecture

Category Architecture Fault Tolerance DC Required Max Achievable PL Typical Use
B Single channel, basic safety principles None None PLb Very low risk; auxiliary functions
1 Single channel, well-tried components None None PLc Infrequent access, low severity hazards
2 Single main channel + periodic test function Detected at next scheduled test Low–Medium PLd Periodic-demand safety functions; lower frequency access
3 Dual channel with cross-monitoring Single fault tolerated; detected at or before next demand Low–High PLd Most industrial guarding, E-stop, light curtains — the standard PLd choice
4 Dual channel, high DC throughout Single fault detected before or at next demand; accumulation ruled out by design High (≥99%) PLe Highest risk applications; cobot nearest-person safety; specialized press guarding

For Category 2: test frequency must be ≥ 100× the demand rate. For Categories 3 and 4: both channels must be independent with no shared single-point failure that defeats both channels.


Worked Example: E-Stop for Robot Cell

Scenario: Industrial robot cell with operator loading/unloading parts every production cycle.

Hazard: Robot arm contact — potential for serious crushing or fracture injury.

PLr determination (ISO 13849-1 Annex A risk graph):

Result: PLr = PLd (S2 / F2 / P1 → PLd)

Architecture to achieve PLd:

Design Decision Selection Rationale
Category 3 (dual-channel) Fault tolerance required; PLd ceiling at Cat 3 with High MTTFd + Medium DC
MTTFd per channel High (≥30 yr) Select E-stop device with published B10d data; calculate MTTFd ≥ 30 yr
DC Medium (90–99%) Cross-monitoring by safety relay detects cross-channel faults
Achieved PL PLd Category 3 + MTTFd High + DC Medium → PLd (Clause 5 table)
CCF ≥ 65 points Separate cable routing (15 pts) + diverse input devices (20 pts) + independent supplies + competence records

Validation: validation methods must suit the design and its safety requirements — for this example, fault analysis of the subsystem, functional test of E-stop initiation, cross-fault detection testing, and a documented PFHd/PL calculation retained in the Technical File. SISTEMA is a convenient tool for that calculation, not a requirement; any documented and validated calculation satisfies the standard.


PL vs SIL — When To Choose This Standard

Aspect ISO 13849-1 (PL) IEC 62061 (SIL)
Metric PLa–PLe SIL 1–SIL 3
Equivalent levels PLd ≈ SIL 2, PLe ≈ SIL 3 SIL 2 ≈ PLd
Best for Mechanical and electromechanical safety devices; most typical industrial machinery Complex SRECS with programmable logic; safety instrumented systems
Software handling Limited — prefers proven components and well-tried designs; complex software needs additional evidence Full software integrity requirements (SIL-rated development process)
Quantitative basis Category + MTTFd + DC combination table PFHd sum across subsystems
Tools SISTEMA (free, published by IFA/TÜV) SISTEMA or custom spreadsheet calculation
Scope Includes mechanical, pneumatic, hydraulic elements (via ISO 13849-2) Electrical/electronic/programmable only

Both standards can be used in the same machine: ISO 13849-1 for electromechanical elements (E-stop device, safety relay), IEC 62061 for the programmable safety controller. The PFHd outputs from each are summed to produce the overall safety function PFHd.

See IEC 62061 for the SIL path.


Common Mistakes

  1. Specifying PLd without running ISO 12100 S/F/P analysis — guessing PLr based on what “sounds right” or what a competitor used. PLr must be derived from a documented risk assessment; an undocumented PLr cannot be defended in a CE audit or after an incident.

  2. Using Category 3 without achieving 65 CCF points — implementing dual-channel hardware and cross-monitoring relay, then failing to score and document CCF. The dual-channel architecture is not considered valid without the Annex F score. Most common root cause: routing both channel cables in the same duct (loses 15 separation points) and using same-manufacturer devices on both channels (loses 20 diversity points).

  3. Confusing MTTFd with MTBF — using MTBF from a datasheet or manufacturer’s MTBF claim directly in SISTEMA or hand calculations. MTBF counts all failures; MTTFd counts only dangerous failures. A component with high MTBF may still have a low MTTFd if most failures are dangerous.

  4. Ignoring DC — high MTTFd with zero DC only achieves PLb at best — a single-channel design (Category 1) with very high-reliability components still tops out at PLc; without diagnostics, no amount of component reliability reaches PLd. DC is what separates Category 3/PLd from Category 1/PLc.

  5. Missing that software in the safety path needs additional validation per Clause 7 — if a safety PLC, configurable safety relay, or other programmable device is in the SRP/CS, Clause 7 validation must address the software configuration. The safety PLC itself must be a validated safety device (IEC 61508 SIL-rated); the application program must be validated per the device manufacturer’s safety manual.

  6. Not repeating PL verification after design changes — modifying component types, changing wiring routes, updating firmware versions, or substituting equivalent components without re-running the SISTEMA calculation and CCF score. Any design change that affects the SRP/CS requires re-validation of the affected safety functions.


Practical Checklist


Lifecycle Application

Stage ISO 13849-1 Activity
Risk Assessment ISO 12100 risk assessment performed; ISO 13849-1 Annex A risk graph then applied to output PLr for each safety function
Safety Function Specification Clause 4: specify initiation event, response, PLr, response time for each function
Safety Architecture Design Clause 6: select Category (B, 1, 2, 3, or 4) based on PLr and fault tolerance needed
Detailed Design Clause 5: select components (MTTFd), implement diagnostics (DC), design CCF measures
PL Verification Clause 5: confirm achieved PL ≥ PLr by documented calculation (SISTEMA or equivalent); iterate if not
Validation Planning Clause 7: establish validation plan before testing; define scope, methods, acceptance criteria
Validation Execution Clause 7: validation by analysis and testing, using methods appropriate to the design; CCF score sheet completed
Documentation Clause 7: validation report assembled; Technical File prepared for CE marking
Commissioning Final validation test on installed machine; confirm response times and reset behavior
Maintenance Periodic re-validation per validation plan; re-verification after any design change

Trust Boundary — Engineering Judgment Required

This site is an independent educational reference for industrial automation standards. It paraphrases and organizes guidance in original language; it is not a substitute for the official published standards, professional engineering judgment, or legal review, and content has not been independently verified against current published editions.

Items marked Review pending await technical review against the identified edition. Items marked Planned have no reviewed source material behind them. Do not rely on this site for compliance determinations, safety-critical design decisions, or legal interpretation.