EN 50126 / EN 50128 / EN 50129: every control, and what you already have

210 controls 0 frameworks share controls with it European Union (CENELEC), applied internationally verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

Code	Control	Also in
`50126-1:5`	Railway RAMS	0
`50126-1:5.6.3`	Derivation of railway-specific influencing factors	0
`50126-1:5.6.4`	Human factors	0
`50126-1:5.7.2`	RAMS specification	0
`50126-1:5.8`	Risk based approach	0
`50126-1:5.9.2`	Reduction of risks related to safety	0
`50126-1:5.9.3`	Reduction of risks related to RAM	0
`50126-1:6`	Management of railway RAMS: general requirements	0
`50126-1:6.2`	Life cycle for the system under consideration	0
`50126-1:6.3`	Risk assessment	0
`50126-1:6.4`	Organisational requirements	0
`50126-1:6.4.2`	Organisational requirements	0
`50126-1:6.5`	Application of this standard and adaptability to project scope and size	0
`50126-1:6.5.1`	General requirements and tailoring	0
`50126-1:6.5.2`	Complex systems with different hierarchical levels	0
`50126-1:6.5.3`	Renewal within existing systems	0
`50126-1:6.5.4`	Re-use or adaptation of a system with previous acceptance	0
`50126-1:6.6`	General requirements on RAMS documentation	0
`50126-1:6.7`	Verification and validation	0
`50126-1:6.7.2`	Verification	0
`50126-1:6.7.3`	Validation	0
`50126-1:6.8`	Independent safety assessment	0
`50126-1:6.8.2`	Independent safety assessment activities	0
`50126-1:7`	RAMS life cycle	0
`50126-1:7.1`	Life cycle general requirements and modification impact analysis	0
`50126-1:7.10`	Phase 9: System validation	0
`50126-1:7.11`	Phase 10: System acceptance	0
`50126-1:7.12`	Phase 11: Operation, maintenance and performance monitoring	0
`50126-1:7.13`	Phase 12: Decommissioning	0
`50126-1:7.2`	Phase 1: Concept	0
`50126-1:7.3`	Phase 2: System definition and operational context	0
`50126-1:7.3.2.2`	RAM plan	0
`50126-1:7.3.2.3`	Safety plan	0
`50126-1:7.4`	Phase 3: Risk analysis and evaluation	0
`50126-1:7.4.2.2`	Hazard log	0
`50126-1:7.5`	Phase 4: Specification of system requirements	0
`50126-1:7.5.4`	Phase 4 specific validation tasks	0
`50126-1:7.6`	Phase 5: Architecture and apportionment of system requirements	0
`50126-1:7.7`	Phase 6: Design and implementation	0
`50126-1:7.7.4`	Phase 6 specific verification tasks	0
`50126-1:7.8`	Phase 7: Manufacture	0
`50126-1:7.9`	Phase 8: Integration	0
`50126-1:7.9.4`	Phase 8 specific verification tasks	0
`50126-1:8.1`	Purpose of a safety case	0
`50126-1:8.2`	Content of a safety case	0
`50126-1:A`	Annex A (informative): RAMS plan	0
`50126-1:B`	Annex B (informative): RAMS parameters	0
`50126-1:C`	Annex C (informative): risk matrix examples	0
`50126-1:D`	Annex D (informative): system definition guidance	0
`50126-2:10.1`	Deriving and apportioning system safety requirements	0
`50126-2:10.2.1`	Deriving functional safety requirements for electronic systems	0
`50126-2:10.2.10`	Demonstration of quantified targets	0
`50126-2:10.2.11`	Requirements for basic integrity	0
`50126-2:10.2.12`	Prevention of misuse of SILs	0
`50126-2:10.2.2`	Apportioning safety requirements	0
`50126-2:10.2.3`	Safety integrity factors	0
`50126-2:10.2.4`	Functional safety integrity and random failures	0
`50126-2:10.2.5`	Systematic aspect of functional safety integrity	0
`50126-2:10.2.6`	Balanced requirements controlling random and systematic failures	0
`50126-2:10.2.7`	The SIL table	0
`50126-2:10.2.8`	SIL allocation	0
`50126-2:10.2.9`	Apportionment of TFFR after SIL allocation	0
`50126-2:10.3`	Safety integrity for non-electronic systems: application of codes of practice	0
`50126-2:11.2`	Causal analysis	0
`50126-2:11.3`	Hazard identification (refinement)	0
`50126-2:11.4`	Common cause analysis	0
`50126-2:5.1`	Risk assessment and hazard control	0
`50126-2:5.2.2`	Conducting risk assessment	0
`50126-2:5.3`	Outcome of the risk assessment	0
`50126-2:5.4`	Hazard control	0
`50126-2:5.5`	Revision of risk assessment	0
`50126-2:5.6`	Responsibilities	0
`50126-2:6.2`	Safety demonstration and safety acceptance process	0
`50126-2:6.3`	Responsibility in managing the safety case	0
`50126-2:6.4`	Modifications after safety acceptance	0
`50126-2:6.5`	Dependencies between safety cases	0
`50126-2:6.6`	Relationship between safety cases and system architecture	0
`50126-2:7.2`	Early phases of the life cycle (phases 1 to 4): independence of roles	0
`50126-2:7.3`	Later phases of the life cycle (from phase 5): independence of roles	0
`50126-2:7.4`	Personnel competence	0
`50126-2:8.2.2`	The risk model	0
`50126-2:8.2.3`	Techniques for the consequence analysis	0
`50126-2:8.2.4`	Expert judgement	0
`50126-2:8.3.1`	Use of code of practice	0
`50126-2:8.3.2`	Use of a reference system	0
`50126-2:8.3.3`	Use of explicit risk estimation	0
`50126-2:8.4.1`	Quantitative approach	0
`50126-2:8.4.2`	Variability using quantitative risk estimates	0
`50126-2:8.4.3`	Qualitative and semi-quantitative approaches	0
`50126-2:9.3.2`	Functional safety requirements	0
`50126-2:9.3.3`	Technical safety requirements	0
`50126-2:9.3.4`	Contextual safety requirements	0
`50128:0`	Introduction and status: EN 50128:2011 superseded by EN 50716:2023	0
`50128:3`	Terms, definitions and abbreviations	0
`50128:4`	Objectives, conformance and software safety integrity levels	0
`50128:5`	Software management and organisation	0
`50128:5.1`	Organisation, roles and responsibilities	0
`50128:5.2`	Personnel competence	0
`50128:5.3`	Lifecycle issues and documentation	0
`50128:6`	Software assurance	0
`50128:6.1`	Software testing	0
`50128:6.2`	Software verification	0
`50128:6.3`	Software validation	0
`50128:6.4`	Software assessment	0
`50128:6.5`	Software quality assurance	0
`50128:6.6`	Modification and change control	0
`50128:6.7`	Support tools and languages	0
`50128:7`	Generic software development	0
`50128:7.1`	Lifecycle and documentation for generic software	0
`50128:7.2`	Software requirements	0
`50128:7.3`	Architecture and design	0
`50128:7.4`	Component design	0
`50128:7.5`	Component implementation and testing	0
`50128:7.6`	Integration	0
`50128:7.7`	Overall software testing / final validation	0
`50128:8`	Development of application data or algorithms: systems configured by application data or algorithms	0
`50128:8.4.1`	Application data or algorithms development process	0
`50128:8.4.2`	Application requirements specification	0
`50128:8.4.3`	Application architecture and design	0
`50128:8.4.4`	Application data or algorithms production	0
`50128:8.4.5`	Application data or algorithms integration and testing / acceptance	0
`50128:8.4.6`	Application data or algorithms validation and assessment	0
`50128:8.4.7`	Application data or algorithms preparation procedures and tools	0
`50128:8.4.8`	Development of generic software	0
`50128:9`	Software deployment and maintenance	0
`50128:9.1`	Software deployment	0
`50128:9.2`	Software maintenance	0
`50128:A`	Annex A (normative): criteria for the selection of techniques and measures	0
`50128:A.1`	Table A.1: lifecycle issues and documentation (5.3)	0
`50128:A.10`	Table A.10: software maintenance (9.2)	0
`50128:A.11`	Table A.11: data preparation techniques (8.4)	0
`50128:A.12-A.23`	Annex A.2 (normative): detailed tables A.12 to A.23	0
`50128:A.2`	Table A.2: software requirements specification (7.2)	0
`50128:A.3`	Table A.3: software architecture (7.3)	0
`50128:A.4`	Table A.4: software design and implementation (7.3, 7.4 and 7.5)	0
`50128:A.5`	Table A.5: verification and testing (6.2 and 7.4)	0
`50128:A.6`	Table A.6: integration (7.3 and 7.6)	0
`50128:A.7`	Table A.7: overall software testing (6.2 and 7.2)	0
`50128:A.8`	Table A.8: software analysis techniques (6.3)	0
`50128:A.9`	Table A.9: software quality assurance (6.5)	0
`50128:B`	Annex B (normative): key software roles and responsibilities	0
`50128:C`	Annex C (informative): documents control summary	0
`50128:D`	Annex D (informative): bibliography of techniques	0
`50129:0`	Introduction and status: EN 50129:2018, its corrigendum and the 2025 revision	0
`50129:3`	Terms, definitions and abbreviations	0
`50129:4`	Overall framework of this document	0
`50129:5`	Requirements for developing safety-related electronic systems	0
`50129:5.1`	Introduction: the conditions for safety acceptance	0
`50129:5.2`	The quality management process	0
`50129:5.3`	The safety management process	0
`50129:5.3.10`	Safety verification	0
`50129:5.3.11`	Safety validation	0
`50129:5.3.12`	Safety qualification tests	0
`50129:5.3.13`	Safety-related application conditions	0
`50129:5.3.14`	Safety justification	0
`50129:5.3.15`	Independent safety assessment	0
`50129:5.3.2`	Guideline for structuring documentation	0
`50129:5.3.3`	Safety life cycle	0
`50129:5.3.4`	Safety organization	0
`50129:5.3.5`	Safety plan	0
`50129:5.3.6`	Hazard log	0
`50129:5.3.7`	Safety requirements specification	0
`50129:5.3.8`	System design for safety	0
`50129:5.3.9`	Safety operation and maintenance plan	0
`50129:6`	Requirements for elements following different life cycles	0
`50129:6.2`	Use of pre-existing items	0
`50129:6.3`	Safety-related tools for electronic systems	0
`50129:6.4`	Physical security and IT-security	0
`50129:7`	The Safety Case: structure and content	0
`50129:7.1`	The Safety Case structure	0
`50129:7.2`	The Technical Safety Report	0
`50129:7.3`	Generic and Specific Safety Cases	0
`50129:7.4`	Provisions for the Specific Application Safety Case	0
`50129:7.5`	Dependencies between Safety Cases	0
`50129:8`	System safety acceptance and subsequent phases	0
`50129:8.1`	System safety acceptance process	0
`50129:8.2`	Operation, maintenance and performance monitoring	0
`50129:8.3`	Modification and retrofit	0
`50129:8.4`	Decommissioning and disposal	0
`50129:A`	Annex A (normative): safety integrity levels	0
`50129:A.2`	Safety requirements	0
`50129:A.3`	Safety integrity	0
`50129:A.4`	Determination of safety integrity requirements	0
`50129:A.4.2`	Risk assessment	0
`50129:A.4.3`	Hazard control	0
`50129:A.4.4`	Identification and treatment of new hazards arising from design	0
`50129:A.5`	Allocation of SILs	0
`50129:A.5.1`	General aspects	0
`50129:A.5.2`	Relationship between SIL and associated TFFR	0
`50129:B`	Annex B (normative): management of faults for safety-related functions	0
`50129:B.2`	General concepts	0
`50129:B.2.1`	Detection and negation times	0
`50129:B.2.2`	Composition of two independent items	0
`50129:B.3`	Effects of faults	0
`50129:B.3.1`	Effects of single faults	0
`50129:B.3.2`	Influences between items	0
`50129:B.3.3`	Detection of single faults	0
`50129:B.3.4`	Action following detection (retention of safe state)	0
`50129:B.3.5`	Effects of multiple faults	0
`50129:B.3.6`	Defence against systematic faults	0
`50129:C`	Annex C (normative): identification of hardware component failure modes	0
`50129:C.2`	General procedure	0
`50129:C.3`	Procedure for integrated circuits	0
`50129:C.4`	Procedure for components with inherent physical properties	0
`50129:C.5`	General provisions concerning component failure modes	0
`50129:D`	Annex D (informative): example of THR/TFFR/FR apportionment and SIL allocation	0
`50129:E`	Annex E (normative): techniques and measures for the avoidance of systematic faults and the control of random and systematic faults	0
`50129:F`	Annex F (informative): guidance on user programmable integrated circuits	0
`50129:G`	Annex G (informative): changes compared to EN 50129:2003	0
`50129:ZZ`	Annex ZZ (informative): relationship with the essential requirements of Directive 2008/57/EC	0

Tell me when EN 50126 / EN 50128 / EN 50129 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for EN 50126 / EN 50128 / EN 50129, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition