Functional safety technical resource
What Is Systematic Capability (SC)?
Systematic capability (SC) is an IEC 61508 measure of confidence that an element's systematic safety integrity meets the requirements of a stated Safety Integrity Level (SIL). It concerns the avoidance and control of systematic faults in the element's development and use. SC is not a probability of failure, does not describe random hardware integrity, and does not by itself establish the achieved SIL of a complete safety instrumented function (SIF).
Technical resource from Mangan Safety Instrumented Systems (Mangan SIS)
What an SC claim does and does not communicate
An SC claim communicates confidence in the measures used to prevent and control systematic faults for a specific element. It does not state the element's random dangerous failure rate, hardware fault tolerance, or the probability that an assembled SIF will fail. Those other attributes must be evaluated separately, and the lowest applicable limitation in the complete design can constrain what may be claimed for the safety function.
How systematic capability relates to SIL
IEC 61508 grades development techniques and measures against a required systematic capability. The corresponding SC level is therefore connected to a SIL claim, but the labels are not interchangeable. A SIF requires evidence for functional requirements, random hardware performance, architecture, systematic integrity, application programming, installation, testing, and operation. An element marked SC does not transfer a complete SIL claim to an application automatically.
Evidence behind the capability
Review the declared assessment route, certificate scope where one exists, applicable IEC 61508 edition, safety manual, development and validation assumptions, systematic capability level, restrictions on configuration or diagnostics, and required user actions. Marketing language or a product-family label is not a substitute for the exact evidence covering the model, firmware, option set, and safety function being used.
Integration conditions still matter
An integrator can introduce new systematic faults through incorrect selection, configuration, application logic, interfaces, environmental use, installation, proof testing, maintenance, or modification. The SRS and design should identify how the element is used and how every relevant safety-manual constraint is satisfied. Any deviation requires a documented technical disposition; it should not be hidden behind the component's SC label.
Mangan SIS project context
Apply Systematic Capability (SC) to documented SIS decisions
Use SC during device and logic-solver selection, certificate and safety-manual review, application-program planning, and design verification. Keep the SC evidence with the exact hardware and software revision. Then evaluate the complete SIF against its SRS, architectural constraints, random-hardware calculation, integration requirements, and lifecycle controls.
Continue the technical trail
Use these related definitions to follow the specific design or lifecycle relationship: Systematic Failure, Hardware Fault Tolerance (HFT), Prior Use (Proven in Use).
Sources and scope
Use the source type that fits the decision
Standards
IEC 61508 introduces systematic capability for elements and grades measures for avoiding and controlling systematic faults. IEC 61511 is the process-sector SIS standard and requires the complete application to meet its specified functional and safety-integrity requirements; a component SC claim is only one input.
Guidance
IEC 61508 product information and the element's controlled safety manual explain how the systematic-capability claim is bounded. ISA process-sector guidance can help users place device evidence within the SIS lifecycle, but informative guidance and third-party certificates do not override the standards or the approved SRS.
Regulation
OSHA 29 CFR 1910.119 does not assign SC ratings or make an SC-marked device automatically acceptable. For covered processes, applicable process safety information, mechanical-integrity, procedure, training, and management-of-change duties remain separate obligations.
Mangan recommendation
Mangan SIS recommends recording the exact SC claim, revision, assessment route, safety-manual constraints, configuration, and responsible reviewer in the design basis. Verify that integration and application programming preserve the claimed conditions and avoid describing SC as the SIL of the device or SIF.
Primary references
- IEC 61508-1:2010 — general requirements and systematic capability (International standard)
- IEC 61508-2:2010 — E/E/PE system requirements (International standard)
- IEC 61508-3:2010 — software requirements (International standard)
- OSHA 29 CFR 1910.119 — Process Safety Management (U.S. regulation)
Common questions
Clarifying Systematic Capability (SC)
Is systematic capability the same as SIL?
No. SC concerns an element's systematic safety integrity at a stated level. SIL applies to the safety integrity required or achieved for a safety function and also depends on random hardware performance, architecture, integration, and lifecycle evidence.
Does an SC 3 component make a SIF SIL 3?
No. The component claim does not establish the complete SIF result. The SIF must satisfy its functional requirements, systematic and hardware constraints, performance calculation, integration, validation, and operating assumptions.
What should be checked with an SC claim?
Check the exact model and revision, certificate or assessment scope, IEC edition, safety manual, permitted configurations, diagnostic and proof-test requirements, environmental limits, and any restrictions imposed on the user or integrator.
Need lifecycle assurance?
Connect lifecycle requirements, responsibilities, and evidence to your SIS program.
Downloadable term reference
Download: Systematic Capability (SC) - Functional Safety Glossary PDF
Save or share this term-specific reference, including the answer-first definition, engineering review considerations, and primary-source references.
Download the Systematic Capability (SC) PDF