Fact-checked by Grok 2 weeks ago

Functional safety

Functional safety is the aspect of overall that relies on a system or equipment performing its intended safety functions correctly in response to its inputs, thereby reducing risks to an acceptable level. It specifically addresses the correct operation of electrical, electronic, or programmable electronic (E/E/PE) safety-related systems to prevent hazardous events, such as physical injury, environmental damage, or property loss. This concept is foundational in industries where automated control systems manage critical processes, ensuring that safety mechanisms like sensors, logic solvers, and actuators function reliably under all conditions. The primary international standard governing functional safety is , a risk-based framework applicable across sectors including industrial automation, transportation, medical devices, and energy production. Published in its first edition in 1998 and updated in subsequent revisions, IEC 61508 outlines requirements for the full safety lifecycle—from initial concept and through , , , , and eventual decommissioning—to manage both systematic failures (e.g., design errors) and random hardware faults. The standard is structured into seven parts, covering general requirements, hardware and software specifications, definitions, and guidelines for achieving safety integrity. Central to IEC 61508 are Safety Integrity Levels (SILs), which quantify the reliability of safety functions on a scale from SIL 1 (lowest risk reduction) to SIL 4 (highest). These levels are determined by probabilistic measures: for low-demand mode operations, SIL 1 requires a probability of failure on demand (PFD) between 10⁻² and 10⁻¹, escalating to 10⁻⁵ to 10⁻⁴ for SIL 4; in high-demand or continuous modes, dangerous failure rates (PFH) range from 10⁻⁶ to 10⁻⁵ per hour for SIL 1 up to 10⁻⁹ to 10⁻⁸ for SIL 4. Compliance often involves third-party certification, incorporating techniques like failure modes and effects analysis (FMEA), fault injection testing, and rigorous documentation to verify that risks are mitigated to tolerable thresholds. Functional safety standards like have spurred sector-specific derivatives, such as for process industries and for automotive systems, promoting harmonized practices globally. By emphasizing verifiable risk reduction through engineered safeguards rather than alone, these frameworks enhance system resilience in increasingly complex, automated environments.

Fundamentals

Definition

Functional safety is defined as the part of the overall safety of a or piece of that depends on the correct functioning of the safety-related systems to achieve or maintain a safe state, particularly in response to its inputs in order to avoid hazardous situations. This concept focuses on ensuring that electrical, , or programmable systems perform their intended safety functions reliably, thereby mitigating risks of physical or damage to and the environment. A key distinction in functional safety lies between fail-safe and fail-operational approaches. In a system, upon detection of a , the system transitions to a predefined safe state, such as shutting down operations to prevent hazards. Conversely, a fail-operational system is designed to continue performing its safety functions in a degraded but still safe manner after a , maintaining for critical operations like automated . Central terminology in functional safety includes the tolerable hazard rate, which represents the maximum acceptable of a hazardous event occurring under normal operating conditions, serving as a for . Failures are categorized into systematic failures, arising from errors in , , or that can be eliminated through process improvements, and random hardware failures, which are probabilistic events due to component or external factors, addressed through probabilistic and . The concept of functional safety evolved from practices in the 1970s, when began integrating into process control systems, raising concerns about reliability in safety-critical applications. This led to the development of in the 1980s and 1990s as the foundational international standard, finalized between 1998 and 2000 to provide a risk-based framework for safety-related systems across industries.

Objectives and Importance

The primary objectives of functional safety are to ensure that electrical, electronic, or programmable electronic systems perform their intended safety functions correctly under all foreseeable conditions, thereby reducing the risk of physical or to an acceptable level. This involves mitigating random hardware failures through quantitative reliability measures, such as safety integrity levels that specify the probability of dangerous failure, and addressing systematic failures—arising from errors in , , or —via structured processes throughout the system lifecycle. These goals form the foundation of international standards like , which adopts a risk-based approach to determine the necessary of safety functions. Functional safety is critically important for protecting lives and property in high-risk domains, including , , and production, where malfunctions can lead to catastrophic consequences. By minimizing the impact of errors and failures, it enhances overall reliability and prevents accidents; for example, in , functions in advanced driver-assistance s help avert collisions, contributing to efforts that address the global toll of road traffic crashes, which resulted in 1.19 million deaths in 2023. This societal impact underscores functional safety's role in fostering safer environments, particularly as and complexity increase in industrial applications. Beyond human protection, functional safety delivers substantial economic benefits by averting the high costs associated with failures, such as product recalls and legal liabilities; the Takata airbag defect recall, for instance, incurred over $1 billion in direct costs to the supplier and billions more for automakers like due to widespread safety risks. Regulatory drivers further amplify its importance, with mandates like the EU Machinery Directive 2006/42/EC requiring manufacturers to incorporate health and safety protections in machinery design to reduce accident risks and ensure market compliance. These factors collectively drive widespread adoption, yielding long-term savings and promoting innovation in safe technologies.

Core Concepts

Hazard Analysis and Risk Assessment

Hazard analysis and risk assessment (HARA) forms the foundational step in functional safety, involving the systematic of potential associated with a , of their risks, and determination of necessary safety measures to reduce those risks to tolerable levels. This process ensures that safety-related functions are defined based on the potential for harm, aligning with the risk-based approach outlined in international standards for electrical, , and programmable systems. HARA typically proceeds through three main steps: , which catalogs all foreseeable sources of danger under and abnormal conditions; risk , which assesses the combination of likelihood (probability of occurrence) and severity (potential consequences); and the establishment of tolerable risk criteria, where unacceptable risks are flagged for through safety functions. Several established methods support HARA in functional safety. The (HAZOP) is a structured that examines deviations from design intent using guide words (e.g., "no," "more," "less") applied to process parameters, helping to uncover hazards and operability issues in . Failure Modes and Effects Analysis (FMEA) provides a bottom-up approach by systematically reviewing potential failure modes of components, their effects on the , and associated risks, often extended to Failure Mode, Effects, and Diagnostic Analysis (FMEDA) for quantitative fault coverage in safety mechanisms. (FTA), a top-down deductive method, models the logical combinations of faults leading to a top-level hazardous event using , enabling probabilistic risk quantification where data is available. These are selected based on , with HAZOP suited for process-oriented systems and FMEA/FTA for hardware and software reliability assessments. Risk evaluation often employs a qualitative to classify by plotting probability against severity, facilitating without requiring precise numerical data. For instance, probability scales might range from "rare" (occurs less than once in lifetime) to "frequent" (occurs multiple times per hour of operation), while severity scales span "negligible" (no or minor disruption) to "catastrophic" (multiple fatalities or widespread damage). The resulting matrix assigns levels—low, medium, high, or intolerable—guiding decisions on whether existing controls suffice or additional functions are needed.
Severity / ProbabilityRareUnlikelyPossibleLikelyFrequent
CatastrophicHighHighIntolerableIntolerableIntolerable
MajorMediumHighHighIntolerableIntolerable
ModerateLowMediumHighHighHigh
MinorLowLowMediumMediumHigh
NegligibleLowLowLowLowMedium
This matrix example illustrates a common qualitative framework, where intersections determine if risks exceed tolerable thresholds. Tolerable risk is context-specific, often defined by regulatory or organizational criteria, ensuring that residual risks after mitigation are (ALARP). HARA integrates iteratively across the functional safety lifecycle, from and phases—where initial analyses inform safety requirements—to , , and even decommissioning, allowing for updates as design evolves or new emerge. Outputs from HARA, such as identified safety functions, directly inform the assignment of safety integrity levels to quantify required . This ongoing application ensures comprehensive hazard coverage throughout the system's life.

Safety Integrity Levels

Safety Integrity Levels (SILs) provide a quantitative for specifying the required performance of safety functions in functional safety s, as defined in the IEC 61508. These levels range from SIL 1 to SIL 4, with SIL 4 representing the highest degree of risk reduction needed for the most critical safety functions. The SIL indicates the reliability required to prevent failures, ensuring that the safety achieves the necessary reduction in risk from identified hazards. The performance of a safety function is measured differently depending on the mode of operation. In low-demand mode, where the safety function is invoked infrequently (less than once per year), the metric is the average probability of failure on demand (PFDavg), which represents the likelihood that the safety function fails to perform when called upon. In high-demand or continuous mode, the metric is the probability of dangerous failure per hour (PFH), quantifying the frequency of dangerous failures over time. Each SIL corresponds to specific target ranges for these metrics, as outlined in IEC 61508. The following table summarizes the target ranges for PFDavg and PFH according to : Low-Demand Mode (avg):
SILavg Range
1≥ 10-2 to < 10-1
2≥ 10-3 to < 10-2
3≥ 10-4 to < 10-3
4≥ 10-5 to < 10-4
High-Demand/Continuous Mode (PFH, per hour):
SILPFH Range
1≥ 10-6 to < 10-5
2≥ 10-7 to < 10-6
3≥ 10-8 to < 10-7
4≥ 10-9 to < 10-8
In the automotive sector, the standard adapts the SIL concept into Automotive Safety Integrity Levels (ASILs), tailored to vehicle-specific s. ASILs range from ASIL A (lowest integrity requirements) to ASIL D (highest), with an additional QM () level for functions where no specific requirements beyond general quality practices are needed. Unlike SILs, ASILs are determined qualitatively through parameters such as severity, , and , rather than direct probability targets. To calculate these metrics, the probability of on demand () is fundamentally defined as = 1 - , where availability reflects the proportion of time the safety function is operational and capable of performing correctly. For simplified assessments assuming a constant in low-demand mode, the average can be approximated as: \text{PFD}_\text{avg} \approx \lambda_\text{DU} \cdot \frac{T}{2} Here, \lambda_\text{DU} is the of dangerous undetected (in per hour), and T is the interval (in hours), representing the time between periodic tests to detect latent . This formula assumes a single-channel (1oo1) and negligible diagnostic coverage or repair times, providing a conservative estimate for initial design evaluations. Target SIL or ASIL levels are established during the hazard analysis and risk assessment phase, where the severity and likelihood of potential hazards determine the required risk reduction. The selected level must achieve sufficient performance to tolerate residual risks at acceptable levels, while considering practical constraints such as development costs, complexity, and feasibility of implementation. For instance, SIL 4 targets are reserved for rare, high-consequence scenarios like nuclear reactor shutdowns, whereas lower levels suffice for less critical industrial processes.

Implementation Methods

Design and Development Techniques

Functional safety design and development techniques emphasize proactive measures to ensure that safety-related systems perform their intended functions despite faults, aligning with the requirements of standards like IEC 61508. These techniques integrate safety considerations from the outset of the process, focusing on architectures and methods that mitigate systematic and random failures in electrical, electronic, and programmable electronic (E/E/PE) systems. By incorporating and error detection mechanisms, designers aim to achieve the necessary safety integrity levels (SILs) as determined by prior assessments. A cornerstone of functional safety development is the adoption of a structured lifecycle approach, often represented by the V-model, which links requirements specification and design phases to their corresponding verification activities. In this model, safety requirements are defined at the system level and progressively refined through architectural, detailed design, and implementation stages, ensuring traceability and systematic error prevention. The V-model, as outlined in IEC 61508-3 for software development, promotes iterative refinement and integration, reducing the likelihood of introducing faults during coding and assembly. This approach facilitates compliance by embedding safety planning across all phases, from concept to decommissioning. As of 2025, updates such as IEC TR 61508-3-3 provide guidance on object-oriented software techniques, and revisions to Part 2 enhance hardware fault tolerance requirements. Key techniques for achieving fault tolerance include and diversity, which enhance system reliability by duplicating or varying critical components. (TMR) is a widely used where three identical modules perform the same function, and a mechanism selects the output to faults, providing high diagnostic coverage for random failures as required by -2. For instance, TMR is applied in safety instrumented systems (SIS) to tolerate single-point failures without compromising operation. Design diversity complements by employing varied implementations—such as different algorithms, platforms, or programming languages—to avoid common-mode failures, a technique recommended in for higher SILs to address systematic faults. Fault-tolerant designs often combine these, like diverse TMR architectures in programmable logic controllers, ensuring continued safe operation or graceful degradation under fault conditions. Error detection and correction mechanisms are integral to these designs, enabling real-time identification and mitigation of faults. timers, hardware circuits that reset the system if software execution deviates from expected timing, serve as a diagnostic tool for detecting errors, as recognized in IEC 61508-2 for providing against software faults. Cyclic checks (CRC) verify in and communications by appending checksums, detecting transmission errors with high probability and supporting the standard's requirements for testing. Built-in self-tests (BIST) periodically validate components like processors and , ensuring ongoing diagnostic coverage; for example, CRC-based BIST in FPGAs confirms integrity during . These mechanisms collectively contribute to the probabilistic failure analysis in IEC 61508, targeting dangerous failure rates (PFH) below 10^{-8} per hour for SIL 4 systems in high-demand or continuous mode. Advanced tools support these techniques by automating and verifying safety properties. (MBD) uses graphical modeling environments to specify, simulate, and generate code, facilitating early fault detection and compliance with IEC 61508-3's structured . Tools like enable traceable models that align with the , reducing manual errors in safety-critical software. , involving mathematical proofs of system behavior, are highly recommended for SIL 3 and 4 to verify absence of certain faults, such as deadlocks in control algorithms, through techniques like . These methods, supported by tools like nuSMV, provide rigorous evidence of safety properties, enhancing confidence in complex E/E/PE systems.

Verification, Validation, and Testing

Verification in functional safety involves confirming that the developed system, software, or hardware components conform to their specified requirements and design inputs through systematic checks such as reviews, inspections, and static analyses. These activities ensure that safety functions are implemented correctly without unintended behaviors, often employing techniques like walkthroughs, checklists, and automated static code analysis to detect defects early in the lifecycle. For instance, peer reviews verify traceability between safety requirements and design artifacts, while static analysis tools identify issues like data flow anomalies or non-compliance with coding standards. Validation, in contrast, demonstrates that the overall system fulfills its intended safety objectives and user needs in the operational environment, typically through dynamic methods such as simulations, hardware-in-the-loop testing, and scenario-based evaluations. This process confirms the "right product" has been built by assessing performance under realistic conditions, including edge cases and environmental stresses, to verify that safety requirements are effectively realized. Validation activities are traceable to the safety requirements specification and often involve end-user or independent testing to ensure the system achieves the targeted Safety Integrity Level (SIL). Testing forms a core component of both , encompassing unit, , and system-level assessments to evaluate functionality and . Unit testing focuses on individual modules against their interfaces, while examines interactions between components, and system-level testing verifies the complete safety function in context. testing is particularly critical, deliberately introducing errors or —such as bit flips in memory or signal disruptions—to assess detection mechanisms, diagnostic coverage, and safe responses, thereby confirming the system's robustness against systematic and random faults. These tests are documented in plans and reports, ensuring compliance with standards like , where they support of modes and effects (FMEA) predictions. To quantify testing thoroughness, structural coverage metrics are applied, with requirements escalating by SIL to mitigate undetected errors. For software under IEC 61508-3, Annex B, Table B.2 specifies: SIL 1 requires 100% coverage of function/entry points (highly recommended), statements and branches/decisions (recommended), and MC/DC (recommended); SIL 2 requires entry points, statements, and branches/decisions (highly recommended), MC/DC (recommended); SIL 3 and SIL 4 require all of the above (highly recommended). MC/DC, for example, verifies that in a decision like "if (A and B) then action," tests demonstrate cases where changing A or B independently alters the outcome, providing high confidence in logic integrity for high-integrity applications. These criteria, combined with functional black-box testing, provide evidence of sufficient diagnostic coverage (e.g., ≥60% for SIL 2-3) and safe failure fractions to meet SIL targets.

Standards and Certification

Key Functional Safety Standards

IEC 61508 is the foundational international standard for functional safety, providing a generic framework for the functional safety of electrical, electronic, and programmable electronic (E/E/PE) safety-related systems across various industries. Originally published in 1998 with the second edition released in 2010, it establishes requirements for the specification, design, integration, operation, and maintenance of safety-related systems to achieve specified safety integrity levels (SIL 1 to 4), serving as the basis for numerous sector-specific derivatives. The standard adopts a risk-based approach to determine the necessary performance of safety functions, emphasizing lifecycle management from concept to decommissioning to minimize systematic and random failures. ISO 26262, tailored for the automotive sector, addresses functional safety in electrical and electronic (E/E) systems within road vehicles, building directly on principles. First issued in 2011 and revised in 2018, it covers the full lifecycle of item , from to production release and operation, using Automotive Safety Integrity Levels (ASIL A to D) to classify risk reduction requirements based on exposure, severity, and controllability. The standard focuses on hazards arising from malfunctioning E/E systems, including their interactions, and provides guidance for , software, and system-level to ensure safe operation in passenger and commercial vehicles. For machinery safety, specifies requirements for the design, integration, and validation of safety-related control systems (SCS), particularly those using electrical, electronic, or programmable electronic technology. Published in 2005 and updated in 2021, it aligns with by employing SIL for performance evaluation and extends to non-electrical aspects, software, cybersecurity considerations, and testing to reduce hazards in industrial machinery. Complementing this, addresses safety-related parts of control systems (SRP/CS) more broadly, including mechanical and pneumatic elements, through principles for design and integration using Performance Levels (PL a to e) to quantify reliability and . First published in 1999, with subsequent editions in 2006 and 2015, and the latest edition in 2023, it emphasizes validation processes to verify safety functions against failure modes. In , DO-178C provides guidelines for software considerations in airborne systems and equipment certification, focusing on design assurance to ensure software performs its intended functions with an acceptable level of . Released in 2011 by RTCA, it defines objectives for processes across five levels (A to E), with Level A requiring the highest rigor for conditions, and supplements address model-based development and object-oriented technology. This standard is pivotal for certifying flight-critical software in . These standards have evolved through updates to incorporate and threats, including harmonization efforts for integration with cybersecurity, such as ISO/SAE 21434 (2021), which defines cybersecurity engineering requirements for road vehicle E/E systems and aligns with to address risks from cyber threats impacting functional safety.

Certification Processes and Bodies

Certification processes for functional safety involve a structured to verify that systems, products, or personnel meet applicable standards, ensuring the of risks associated with electrical, , or programmable systems. These processes typically begin with a , where organizations assess their current practices against standard requirements to identify deficiencies in design, development, or . This is followed by an conducted by accredited third parties, which includes thorough review to evaluate safety lifecycle activities, such as and risk assessments. On-site audits then occur to inspect implementation, processes, and evidence of compliance, often spanning 1-2 days for focused reviews. While self-certification allows manufacturers to declare compliance based on internal reviews under standards like , third-party certification is preferred for , involving external auditors to provide validation and reduce . Third-party processes emphasize , with certification bodies issuing formal certificates upon successful completion, which are listed in public databases for . In contrast, self-certification lacks this external oversight and may not be accepted by end-users or regulators in high-risk applications. Key certification bodies for functional safety include TÜV SÜD, UL, and exida, which specialize in IEC 61508 assessments across industries. TÜV SÜD has certified over 3,000 products and provides auditing services for safety-related systems. UL offers training and certification programs aligned with IEC 61508, focusing on electrical systems. Exida, an ANSI-accredited agency, conducts SIL verifications for hardware and software, maintaining a Safety Automation Equipment List for certified products. For aviation, the Federal Aviation Administration (FAA) and European Union Aviation Safety Agency (EASA) oversee functional safety through type certification processes, requiring compliance with standards like DO-178C for software in safety-critical systems. Certification schemes, such as the Functional Safety Certification Program (FSCP) offered by SÜD, provide structured personnel qualifications for in automotive applications. The FSCP includes three levels: Functional Safety Engineer (foundational knowledge via exam), Functional Safety Professional (requiring up to six years of experience and project references), and Functional Safety Expert (up to ten years of experience with case studies). These schemes ensure auditors and engineers possess the necessary competence for independent assessments. Similar programs exist through exida's Certified Functional Safety Expert (CFSE) for , emphasizing practical application. Challenges in certification include the need for recertification following any changes, such as software updates, which can trigger full reassessments and delay deployments due to rigorous requirements. Costs represent another barrier, with automotive projects often exceeding $100,000 due to extensive , testing, and third-party audits, particularly under ISO 26262. These expenses and iterative processes underscore the importance of early integration of safety practices to minimize rework.

Industry Applications

Automotive

Functional safety in the automotive sector primarily revolves around ensuring that electrical and electronic (E/E) systems in road vehicles operate without causing unacceptable risks to occupants, other road users, or the environment. The cornerstone standard is , which provides a comprehensive framework for the functional safety of E/E systems throughout the entire , from and to production, operation, service, and decommissioning. This standard addresses potential hazards arising from malfunctions in safety-related E/E systems, including their interactions, and applies to all types with item development assurance levels up to ASIL D, the highest integrity level. Unlike general safety standards, is tailored to the automotive context, emphasizing risk reduction through systematic processes for items ranging from integrated circuits to complete vehicle systems. Key applications of functional safety in automotive systems include advanced driver assistance systems (ADAS) and electric vehicle (EV) components. For instance, Automatic Emergency Braking (AEB) systems, which detect obstacles and apply brakes autonomously to prevent or mitigate collisions, are typically classified at ASIL D to ensure high integrity against failures that could lead to severe harm. In EVs, battery management systems (BMS) monitor and control lithium-ion batteries to prevent thermal runaway, overcharging, or excessive discharge, adhering to ISO 26262 through hazard identification and safety requirement derivation for safe operation under fault conditions. These applications highlight how functional safety integrates into critical functions, prioritizing fault-tolerant designs and redundancy to maintain safe vehicle behavior. Hazard Analysis and Risk Assessment (HARA) under is conducted to identify potential hazards from E/E system malfunctions, assessing risks based on severity, exposure, and controllability, while considering various vehicle operation modes such as normal , maneuvering, or emergency scenarios. This mode-specific tailoring ensures safety goals are derived for representative conditions, like travel or urban intersections, guiding the allocation of ASIL requirements across system elements. Challenges in automotive functional safety include managing over-the-air (OTA) updates and integrating cybersecurity, as these introduce dynamic risks not fully covered by traditional processes. OTA updates, which enable remote software modifications for features like ADAS enhancements, must verify non-interference with safety functions to avoid introducing latent faults during deployment. Cybersecurity integration addresses threats that could compromise E/E systems, requiring alignment with ISO/SAE 21434 to prevent attacks from inducing safety violations, such as unauthorized control overrides. A notable case is the series of incidents starting in 2016, including a fatal crash investigated by the (NHTSA), which highlighted limitations in driver monitoring and system safeguards, prompting software updates and enhanced safety protocols to improve fault detection and response.

Aviation and Aerospace

Functional safety in aviation and aerospace ensures that critical systems perform reliably to prevent catastrophic failures, given the high-stakes environment involving human lives and complex operations. This domain demands stringent assurance processes to mitigate risks from software, hardware, and system malfunctions in and . Regulatory bodies like the (FAA) and (EASA) enforce rigorous to verify compliance with safety objectives. Key standards guide development and assurance in this field. RTCA DO-178C provides objectives for software certification in airborne systems, emphasizing planning, development, verification, and configuration management to achieve required design assurance levels. Complementing this, RTCA DO-254 outlines similar processes for airborne electronic hardware, including design assurance for complex integrated circuits to prevent failures in safety-critical functions. SAE ARP4754A addresses system-level development assurance, integrating safety assessments from requirements to integration while aligning with failure condition classifications. These standards employ Design Assurance Levels (DAL) A through E, where DAL A demands the highest rigor for functions whose failure could cause catastrophic events, scaling down to DAL E for minor effects. In applications, functional safety is integral to systems, which replace mechanical controls with electronic interfaces for precise flight control, certified under to ensure and real-time responsiveness. systems, automating aircraft guidance, adhere to FAA AC 25.1329-1C, which specifies safety criteria for disengagement, failure detection, and crew interface to maintain controllability during faults. In , NASA's Core Flight System (cFS) exemplifies fault-tolerant computing for satellites, featuring a reusable with health and safety applications for monitoring, event detection, and servicing to uphold mission reliability in harsh orbital environments. Certification processes involve comprehensive safety reviews by FAA and EASA, including system safety analyses, fault tree evaluations, and flight testing to validate compliance. Safety Review Boards oversee hazard mitigation, ensuring no single-point failures compromise operations. The Boeing 737 MAX incidents (2018-2019) highlighted MCAS software vulnerabilities, such as reliance on a single angle-of-attack sensor leading to erroneous activations; post-accident reviews by FAA and EASA mandated dual-sensor inputs, activation limits, and enhanced alerting to bolster functional safety and prevent runaway stabilizer commands. Unique to and are real-time constraints, where systems must detect and respond to faults within milliseconds to avoid loss of control, often integrating run-time assurance techniques. In space systems, radiation hardening addresses cosmic ray-induced errors, employing tolerant designs and error-correcting codes to maintain and prevent single-event upsets in satellites and spacecraft electronics.

Industrial and Process Control

Functional safety in industrial and process control systems is essential for mitigating risks associated with , chemical , and heavy machinery operations, where failures can lead to catastrophic events such as explosions, toxic releases, or equipment damage. These systems ensure that automated controls respond reliably to hazardous conditions, maintaining continuous operation while prioritizing worker and . Key to this domain are safety instrumented systems (SIS), which integrate sensors, solvers, and actuators to detect anomalies and initiate protective actions, as defined in international standards for the process sector. The primary standards governing functional safety in this area are for the process industry and IEC 62061 for machinery. provides a lifecycle approach for specifying, designing, installing, operating, and maintaining in sectors like oil and gas, chemicals, and pharmaceuticals, emphasizing risk reduction through safety instrumented functions (SIFs). IEC 62061 focuses on safety-related electrical, electronic, and programmable electronic control systems for machinery, offering requirements for design, integration, and validation to achieve specified performance levels. These standards build on broader functional safety principles, assigning Safety Integrity Levels (SIL) to based on required risk reduction. In applications such as refineries and chemical plants, SIS enable critical functions like emergency shutdown systems (ESD) and pressure relief mechanisms. ESD systems automatically isolate processes or halt operations upon detecting , high temperatures, or leaks, preventing escalation of incidents in high-hazard environments. For instance, pressure relief in refineries often employs high-integrity pressure protection systems (HIPPS), which serve as SIS to block high-pressure sources from low-pressure equipment, avoiding the need for oversized relief valves and reducing flare loads. The 1984 , involving a leak that killed thousands, profoundly influenced these standards by highlighting deficiencies in SIS design and maintenance, prompting global regulatory reforms and the adoption of rigorous . Techniques for ensuring SIS reliability include regular proof-testing to verify undetected failures, with intervals typically ranging from 1 to 5 years depending on the assigned SIL and failure probability data. HIPPS designs often incorporate redundant sensors and partial stroke testing of valves to maintain high diagnostic coverage without full process shutdowns. Challenges in implementing functional safety arise particularly with legacy systems, where retrofitting obsolete controls to meet modern standards involves compatibility issues, lack of , and minimizing in continuous operations. Human-machine interfaces (HMIs) in these environments pose additional risks if not designed for clear fault indication and operator response, potentially leading to delayed interventions during hazards. Addressing these requires phased upgrades and cybersecurity assessments to integrate legacy equipment with compliant .

Medical Devices

Functional safety in medical devices encompasses the measures taken to ensure that equipment operates correctly to prevent to patients, prioritizing the mitigation of risks associated with malfunctions in , software, and interfaces. This is particularly critical in healthcare settings where device failures can lead to direct physiological , such as incorrect dosing or failure to deliver life-sustaining . Key standards like IEC 60601-1 establish requirements for basic and essential performance of medical electrical equipment, addressing hazards including electrical, mechanical, and thermal risks to ensure reliable operation under intended use conditions. Similarly, IEC 62304 provides a lifecycle framework for software, classifying it into safety classes A (no possible injury), B (non-serious injury possible), and C (death or serious injury possible), with escalating development rigor for higher classes to verify through documentation, testing, and risk controls. These standards integrate with processes under to identify and mitigate hazards throughout the device lifecycle. In applications such as infusion pumps and pacemakers, functional safety focuses on precise control and fail-safe mechanisms to avoid overdose or pacing errors. Infusion pumps, used for delivering medications like , incorporate smart features such as drug libraries and dose-error reduction software to prevent programming mistakes, which have historically caused adverse events; for instance, approaches have been applied to develop safety-assured patient-controlled analgesic pumps compliant with class C requirements. Pacemakers, as implantable devices, must withstand and battery depletion risks, with standards like ensuring safe operation in MRI environments at 1.5 without inducing arrhythmias. Cybersecurity has emerged as a vital aspect post the 2017 , which infected over 1,200 devices and disrupted hospital networks, prompting enhanced protections like and secure boot processes in connected devices to prevent remote manipulation of therapy delivery. Processes for achieving functional safety include usability engineering as outlined in IEC 62366-1, which mandates analyzing user interactions to reduce use errors that could compromise safety, such as misconfiguration during high-stress clinical scenarios. This involves , formative evaluations, and summative testing to validate intuitive operation, often integrated with clinical validation studies that simulate real-world use to confirm essential without introducing hazards. Ethical considerations underscore these efforts, emphasizing patient autonomy, equitable access to safe devices, and the to balance with non-maleficence; for example, developers must weigh rapid deployment needs against thorough to avoid prioritizing speed over in life-critical implants. Post-market complements pre-market controls by real-world , as seen in FDA Class I recall of V30, A30, and A40 in August 2025 due to a software fault in the inoperative alarm that risked interruptions and , leading to updated use instructions and reports of 13 injuries and 8 deaths to protect patients. Such , required under regulations like the EU Medical Device Regulation (MDR), involves adverse event reporting and periodic safety update reports to iteratively improve device .

Other Sectors

In the rail sector, functional safety is addressed through a suite of standards that ensure the reliability, availability, maintainability, and () of systems. EN 50126 specifies processes for the specification and demonstration of in railway applications, adopting a risk-based approach to manage hazards throughout the system lifecycle. EN 50128 provides requirements for the development of programmable electronic systems software used in railway control and protection, emphasizing to achieve safety integrity levels (SILs). EN 50129 outlines safety-related requirements for electronic systems in railway signaling, including hardware design, testing, and approval processes to prevent failures in critical operations. These standards are applied in signaling systems such as the (ETCS), which uses continuous supervision of train speed and movement authority to mitigate collision risks, achieving high safety performance through redundant architectures and methods. For plants, functional safety focuses on and (I&C) systems critical to preventing accidents and mitigating their consequences. IEC 61513 establishes general requirements for I&C systems important to , covering architecture, design, and qualification to ensure , , and in safety functions. This standard applies particularly to reactor protection systems, which automatically initiate shutdowns or other protective actions in response to abnormal conditions, such as reactivity excursions or loss of cooling, thereby maintaining the plant within safe operational limits. Compliance involves graded safety classifications and lifecycle management to achieve deterministic behavior and . Emerging technologies present unique challenges for functional safety, particularly in integrating (AI) and (ML) components. ISO/IEC TR 5469 provides guidance on functional safety for AI systems, outlining a three-stage realization principle—concept, development, and operation—that aligns AI usage with established safety standards like , while addressing non-determinism and opacity in ML models. Building on ISO/IEC 22989, which defines AI concepts and terminology, this approach enables safe deployment in safety-related functions by specifying risk factors, validation methods, and assurance levels. In , such as smart home devices, functional safety is ensured through standards like IEC 60730, which specifies requirements for automatic electrical controls in household appliances, including self-testing and fault detection to prevent hazards like overheating or unintended actuation in connected systems. Cross-cutting applications include and defense sectors, where adaptations of core functional safety principles address domain-specific risks. In operations, is adapted for instrumented systems on ships, such as controls and shutdowns, to handle environmental hazards like collisions or fires through risk assessments and SIL assignments. For defense systems, MIL-STD-882E outlines a program that integrates and risk acceptance criteria across the acquisition lifecycle, ensuring that electrical and electronic systems in military equipment, from munitions to autonomous platforms, minimize mishap risks via reviews and verification.

References

  1. [1]
    [PDF] Overview of IEC 61508 & Functional Safety
    Functional safety: part of the overall safety that depends on a system or equipment operating correctly in response to its inputs. From these two definitions, ...
  2. [2]
    IEC 61508: The Functional Safety Standard - Intertek
    IEC 61508 is an international standard that provides a framework for ensuring the functional safety of systems that depend on electrical, electronic, or ...<|control11|><|separator|>
  3. [3]
    IEC 61508 Functional Safety Standard | TÜV SÜD - TUV Sud
    According to the IEC, 61508 provides functional safety standards for the lifecycle of electrical, electronic, or programmable electronic (E/E/PE) systems and ...
  4. [4]
    EN 61508: Functional safety of control systems - Pilz US
    It is the main standard covering the functional safety of control systems. This standard is used to define the requirements of safety systems in plant safety.
  5. [5]
    What is Functional Safety? - The 61508 Association
    Functional safety is the safety relating to the equipment under control and control system that depends on the correct functioning of the safety-related ...
  6. [6]
  7. [7]
    Three Things to Know About Functional Safety - NXP Semiconductors
    Oct 3, 2016 · Fail-safe: the system goes into safe mode when a failure occurs. ... Fail-operational: sometimes also referred to as fault-tolerant, a failure ...
  8. [8]
    Difference Between Fail-safe and Fail-operational Modes: AURIX ...
    Apr 28, 2023 · The main difference is the availability of the function. difference-between-fail-safe-and-fail-operational-modes. Figure 1 Safety-relevant ...
  9. [9]
    Random versus Systematic Failures – Issues and Solutions - exida
    Functional safety standards provide definitions of two different categories of failures: random failures and systematic failures. These were created during the ...Missing: key tolerable
  10. [10]
    Functional Safety Evolution - exida
    Aug 4, 2016 · In 2010, the 2nd edition of 61508 was published. It filled some gaps that had remained in the 1st edition. It enhanced some areas of Functional ...
  11. [11]
    [PDF] An introduction to Functional Safety and IEC 61508
    In the standard a SIL is defined as 'a discrete level (one of 4) for specifying the safety integrity requirements of safety functions'. Thus, a SIL is a target ...
  12. [12]
    Global status report on road safety 2023
    Dec 13, 2023 · The Global status report on road safety 2023 shows that the number of annual road traffic deaths has fallen slightly to 1.19 million.
  13. [13]
    Functional Safety Overview | TÜV SÜD - TUV Sud
    At its core, functional safety is important because its sole purpose is to protect users from harm. Complex technology is an integral part of our day to day ...
  14. [14]
    [PDF] The auto industry's growing recall problem—and how to fix it
    Replacing potentially defective airbags has cost Takata. $1 billion and cost Takata's. OEM clients, such as Honda, billions more. Those scandals overshadowed ...
  15. [15]
    Directive 2006/42/EC - machinery directive - EU-OSHA
    Jun 13, 2024 · Directive 2006/42/EC on machinery lays down health and safety requirements for the design and construction of machinery, placed on the European market.
  16. [16]
    IEC 61882:2016
    Mar 10, 2016 · IEC 61882:2016 provides a guide for HAZOP studies of systems using guide words. It gives guidance on application of the technique and on the HAZOP study ...
  17. [17]
    Integrating FMEAs, FMEDAs, and Fault Trees for Functional Safety
    FMEA, FMEDA, and FTA are linked documents. FMEA links to FMEDA, and FTA can be developed from FMEA, providing consistent fault metrics.
  18. [18]
    Hazard and Risk - Risk Assessment - CCOHS
    The basic qualitative method combines severity and probability parameters to produce a level of risk that is compared against pre-determined risk criteria. This ...What is a risk assessment? · When should a risk... · How is a risk assessment done?
  19. [19]
    Functional Safety FAQ - IEC
    IEC 61508 is concerned with achieving functional safety, where safety is defined as freedom from unacceptable risk of physical injury or damage to the health ...
  20. [20]
    Back to Basics 16 - PFDavg - exida
    Oct 31, 2019 · Target levels for PFDavg are defined in IEC 61508 for each of 4 levels of SIL; PFDavg is defined for low demand mode (for high/continuous demand ...<|control11|><|separator|>
  21. [21]
    Back to Basics 17 - PFH (Probability of dangerous Failure per Hour)
    Nov 19, 2019 · Target levels for PFH are defined in IEC 61508 for each of the 4 levels of SIL; It's one of the 3 design barriers that must be met for ...Missing: ranges | Show results with:ranges
  22. [22]
    Automotive Safety Integrity Level (ASIL) - exida
    Automotive Safety Integrity Level (ASIL) is a risk classification scheme defined by the ISO 26262 - Functional Safety for Road Vehicles standard.
  23. [23]
    ISO 26262-1:2018 - Road vehicles — Functional safety — Part 1
    In stockThis document describes a framework for functional safety to assist the development of safety-related E/E systems.
  24. [24]
    Certified to SIL 4 - Cycle Test Failure Data is Dangerous - IEC 61508
    Apr 7, 2011 · Assuming a proof test interval of one year and using the simple equation for PFDavg: PFDavg = LambdaD X TI/2, they calculated LambdaD. This is ...Missing: formula constant
  25. [25]
    [PDF] Safety Instrumented Function Verification: The Three Barriers White ...
    Thus, SIL determination is significantly more complicated than simply calculating a PFH or PFDavg and performing a table look‐up to establish the corresponding ...
  26. [26]
    Blog - Software Modeling and Functional Safety - IEC 61508 - exida
    Aug 29, 2013 · The IEC 61508 standard has requirements, for certain SIL levels, regarding the use of: “Semi-formal methods”; Computer-aided specification and ...
  27. [27]
    Functional Safety according to IEC61508 - CSA Engineering AG
    The standard strongly recommends development according to the V-model. As a central element, the risk analysis stands at the beginning. Based on this, the ...
  28. [28]
    [PDF] Developing+Safety+Critical+Applications+that+Meet+IEC+61508+ ...
    There are two well-known techniques that are widely utilized: dual modular redundancy (DMR) and triple modular redundancy (TMR). In the case of dual modular ...
  29. [29]
    [PDF] Diverse redundancy used in SIS technology - ABB
    1 Introduction. Diverse redundancy is one of the mechanisms recommended in the IEC 61508 and IEC 61511 standards to increase safety integrity of programmable ...
  30. [30]
    Proper Watchdog Timer Use - Better Embedded System SW
    May 26, 2014 · IEC 61508-2 lists a watchdog timer as a form of test by redundant hardware (pg. 115) (without implying that it provides complete redundancy).
  31. [31]
    [PDF] 8 Reasons to Use FPGAs in IEC 61508 Functional Safety Applications
    Sep 1, 2013 · Another example of a diagnostic IP would be a cyclic redundancy check (CRC) IP core, which could be used to calculate and check CRC values ...<|control11|><|separator|>
  32. [32]
    [PDF] TLIN1431x-Q1 Functional Safety Manual - Texas Instruments
    The response that this safety mechanism takes when an error is detected. Note: For software-driven tests, the Action on Detected Fault may depend on software.
  33. [33]
    [PDF] Model-Based Design for Safety-Related Applications - MathWorks
    This paper discusses workflows for developing safety- related application software components and specific requirements with respect to Model-Based Design. Gen-.
  34. [34]
    [PDF] Formal Methods and their role in Software and System Development
    Formal Methods. Page 20. Examples of Reference Standards. • IEC 61508 - Functional safety of electrical/electronic/ programmable electronic safety-related ...<|control11|><|separator|>
  35. [35]
    [PDF] Understanding Verification and Validation of Software Under IEC ...
    This paper focuses on verification and validation of safety-related software under IEC 61508-3:2010, describing techniques and measures relevant to software  ...
  36. [36]
    [PDF] IEC 61508 Functional Safety Assessment - Emerson Global
    Verification activities include the following: Fault Injection Testing, static source code analysis, FMEDA, peer reviews and both hardware and software unit ...
  37. [37]
    [PDF] IEC 61508 Functional Safety Assessment - exida
    Validation Testing is done via a set of documented tests. The validation tests are traceable to the. Safety Requirements Specification [D36] in the validation ...
  38. [38]
    IEC 61508 Compliant Module Testing: Part 2 - exida
    Oct 19, 2012 · 100% entry point coverage (SIL 1) · 100% statement coverage (SIL 2) · 100% branch coverage(SIL 3) · 100% condition coverage (MC/DC) (SIL 4).
  39. [39]
    IEC 61508-1:2010
    A major objective of this standard is to facilitate the development of product and application sector international standards by the technical committees ...
  40. [40]
    ISO 26262-1:2011 - Road vehicles — Functional safety — Part 1
    ISO 26262 addresses possible hazards caused by malfunctioning behaviour of E/E safety-related systems, including interaction of these systems. It does not ...
  41. [41]
    Keeping safe on the roads: series of standards for vehicle ... - ISO
    Dec 19, 2018 · ISO 26262 defines functional safety for all automotive electronic and electrical safety-related systems, covering their entire life cycle ...
  42. [42]
    IEC 62061:2021
    Mar 22, 2021 · IEC 62061:2021 specifies requirements and makes recommendations for the design, integration and validation of safety-related control systems (SCS) for machines.
  43. [43]
    Updated IEC Standard ensures the functional safety of machinery
    Apr 27, 2021 · This standard provides an approach to achieve the necessary performance of the safety functions in order to reduce the potential hazards ...
  44. [44]
    ISO 13849-1:2015 - Safety of machinery
    ISO 13849-1:2015 provides safety requirements and guidance on the principles for the design and integration of safety-related parts of control systems (SRP/CS).
  45. [45]
  46. [46]
    DO-178C - Software Considerations in Airborne Systems and ...
    This document provides recommendations for the production of software for airborne systems and equipment that performs its intended function with a level of ...Missing: standard | Show results with:standard
  47. [47]
    DO-178() Software Standards Documents & Training - RTCA
    DO-178(), originally published in 1981, is the core document for defining both design assurance and product assurance for airborne software.
  48. [48]
    ISO/SAE 21434:2021 - Road vehicles — Cybersecurity engineering
    In stockISO/SAE 21434:2021 is an international standard that defines engineering requirements for cybersecurity risk management in the context of road vehicles.
  49. [49]
  50. [50]
    [PDF] Functional Safety Certification Scheme Description - exida
    Dec 3, 2020 · When all the process gap issues have been addressed, an audit meeting is scheduled. The meeting is expected to be conducted over 1-2 days.
  51. [51]
    The 5 Functional Safety Assessment (FSA) stages
    FSA are carried out at various stages of a project lifecycle to confirm compliance before moving on to the next stage.
  52. [52]
    Functional Safety Audit vs. Functional Safety Assessment
    Apr 19, 2017 · An FS Audit provides a systematic and independent examination of the particular safety lifecycle phase activities under review. It determines ...<|separator|>
  53. [53]
    IEC 61508 Functional Safety Certificates - To Accept or not to Accept?
    Aug 10, 2017 · The first rule was done because some manufacturers issue their own self-declared “certificates.” And the IEC 61508 standard allows that.
  54. [54]
    [PDF] Det-Tronics-Functional-safety-product-certifiers-and-accreditation ...
    A third- party evaluation of a manufactured product is preferred over self-certification. But which third-party should you select? What matters in certification ...
  55. [55]
    Functional Safety Testing, Certification, and Training | TÜV SÜD
    We have certified over 3,000 products to functional safety standards and have trained over 7,000 engineers. Our Functional Safety Services by Industry: General.
  56. [56]
    IEC 61508 UL Certified Functional Safety Professional Training
    This course is designed for engineers, developers and managers seeking to successfully apply IEC 61508 to their safety-related electrical systems.
  57. [57]
    IEC 61508 Functional Safety Certification - exida
    exida is an ANSI accredited certification agency which assesses and certifies that a product has been designed and developed in accordance with the standard.Exida Certification Benefits · ``exida Is The Clear Market... · Why Choose Exida?
  58. [58]
    ISO 26262: Functional Safety Certification Program (FSCP) - TUV Sud
    TÜV SÜD has decades of experience in functional safety in the automotive industry and offers a special FSCP training program.
  59. [59]
    [PDF] Personnel Functional Safety Certification
    The exida Functional Safety Practitioner (FSP) is a certificate program that addresses a growing need to provide confirmation that an attendee showed competency ...Missing: Scheme FSCC
  60. [60]
    Functional safety and continuous certification on Linux - Red Hat
    Mar 10, 2025 · Benefits of a Continuous Functional Safety Certification. One of the biggest challenges with functional safety is change management.
  61. [61]
    IEC 61508 Updates – What Manufacturers Need to Get Ready For
    Oct 3, 2025 · High cost and effort: Certification requires extensive documentation, testing, and third-party auditing.Missing: recertification | Show results with:recertification
  62. [62]
    Cost model with projections of functional safety certification of...
    If we assume a cost for functional safety certification of each product Cost Cert , the total cost for developing N products in the traditional way and for ...Missing: recertification | Show results with:recertification<|control11|><|separator|>
  63. [63]
    Review and Assessment of the ISO 26262 Draft Road Vehicle
    Apr 15, 2012 · ISO 26262 is the first comprehensive automotive safety standard that addresses the safety of the growing number of electric/electronic and ...
  64. [64]
    Exploring The Intricacies of ISO 26262 Standard Application in ADAS
    Aug 14, 2023 · Starting with basic features like anti-lock braking systems and electronic stability control, ADAS has expanded to include lane keeping assist, ...
  65. [65]
    Compliance of ISO 26262 safety standard for lithium ion battery and ...
    This paper is an application of ISO 26262 functional safety standards for the proper design, development and validation of Lithium ion battery system.
  66. [66]
    HARA by ISO 26262 Standard | Automotive Functional Safety Project
    Apr 17, 2019 · The purpose behind HARA is to identify the malfunctions that could possibly lead to E/E system hazards and assess the risk associated with them.
  67. [67]
    Hazard Analysis and Risk Assessment: The HARA and ...
    Jul 24, 2023 · This is an ISO 26262 requirement. Use ... Perform a HARA analysis of all operating modes on each applicable representative driving segment.
  68. [68]
    [PDF] Functional Safety and Cybersecurity aspects of Over the Air Updates
    For safety risks, ISO 26262 examples did the job. To ensure zero safety and security issues within the OTA feature, our analysis showed that its regular.Missing: challenges | Show results with:challenges
  69. [69]
    ISO/SAE 21434 & ISO 26262: Automotive Security & Safety - Cybellum
    May 1, 2024 · ISO 26262, the international standard for functional safety (FuSa), addresses potential hazards caused by malfunctions in electronic and electrical vehicle ...
  70. [70]
    [PDF] PE 16-007 - DOT NHTSA ODI Document
    Jan 19, 2017 · The investigation was about Tesla's Autopilot and AEB systems, which may not function as designed, increasing crash risk, triggered by a fatal ...
  71. [71]
    [PDF] Final Report for Software Service History and Airborne Electronic ...
    Nov 1, 2016 · RTCA DO-178C “Software Considerations in Airborne Systems and Equipment Certification” and RTCA DO-254 “Design. Assurance Guidance for Airborne ...
  72. [72]
    [PDF] Order 8110.105A - Simple and Complex Electronic Hardware ...
    Apr 5, 2017 · This order explains how Federal Aviation Administration (FAA) aircraft certification staff can use and apply RTCA, Inc. document RTCA/DO-254 ...
  73. [73]
    [PDF] DOT / FAA /TC-16/39
    ARP4754A. AC20-170. DO-297. AC20-115C. DO-178C. AC20-152. DO-254. However, based on lessons learned, it is important to clearly establish the required DA work.
  74. [74]
    What is DO-178B? - AdaCore
    DO-178B, officially RTCA DO-178B / EUROCAE ED-12B is a software certification standard for airborne systems on commercial aircraft.
  75. [75]
    [PDF] AC 25.1329-1C - Federal Aviation Administration
    Oct 27, 2014 · The effects of a failure of the system to disengage the autopilot or autothrust functions when manually commanded by the pilot must be assessed ...
  76. [76]
    core Flight System | Goddard Engineering and Technology Directorate
    Sep 29, 2025 · The core Flight System (cFS) is a platform-independent, reusable software framework designed to expedite flight software development.Core Team · NASA cFS Steering Committee · cFS Catalog · cFS TrainingMissing: functional aviation fly- wire autopilot
  77. [77]
    Core Flight System (cFS) Health & Safety (HS) Application version ...
    The HS application provides functionality for Application Monitoring, Event Monitoring, Hardware Watchdog Servicing, Execution Counter Reporting (optional), and ...Missing: functional aviation fly- wire autopilot
  78. [78]
    [PDF] Boeing 737 MAX Flight Control System Observations, Findings, and ...
    Oct 11, 2019 · The JATR team reviewed the type certification process (per FAA Order 8110.4C, Type Certification, and related guidance) to determine whether ...Missing: lessons | Show results with:lessons
  79. [79]
    [PDF] Summary of the FAA's Review of the Boeing 737 MAX
    This report provides a detailed technical account of the lessons learned since the two fatal accidents involving the Boeing 737 MAX aircraft, ...
  80. [80]
    [PDF] Boeing 737 MAX Return to Service Report - EASA
    Jan 27, 2021 · The EASA flight tests confirmed that MCAS was needed to provide full compliance but also that the loss of this function does not preclude the ...Missing: lessons | Show results with:lessons
  81. [81]
    [PDF] Benefits of Using Functional Safety in Commercial Space Applications
    Thanks to the near-instant detection of any faults, the system can meet very tight real-time requirements as needed in time and mission critical sub-systems ...
  82. [82]
    [PDF] High-Performance, Radiation-Hardened Electronics for Space and ...
    Abstract. The. Radiation. Hardened. Electronics for Space. Environments. (RHESE) project develops advanced technologies needed for high performance.
  83. [83]
    [PDF] Single Event Effects Mitigation Techniques Report
    In assessing the need for radiation-tolerant versus radiation-hard electronic systems, the designer ... The soft error rates are determined from real-time system- ...
  84. [84]
    IEC 61511-1:2016
    Feb 24, 2016 · IEC 61511-1:2016 gives requirements for the specification, design, installation, operation and maintenance of a safety instrumented system (SIS).
  85. [85]
    Back to Basics 04 - Safety Instrumented System (SIS) - exida
    Apr 21, 2019 · A SIS is an implementation of one or more Safety Instrumented Functions (SIF), composed of sensors, logic solvers, and final elements. It ...
  86. [86]
    IEC 61511: Safety instrumented systems for the process industry
    The IEC 61511 series of standards addresses SIS based on the use of electrical, electronic, or programmable electronic technology in the process industry sector ...
  87. [87]
    Emergency Shutdown System (ESD) - Sapientechs.com
    Feb 24, 2025 · An Emergency Shutdown System (ESD) is a dedicated safety instrumented system (SIS) that detects hazardous conditions and automatically initiates protective ...
  88. [88]
    High Integrity Pressure Protection Systems (HIPPS) - ISA Interchange
    High integrity pressure protection systems (HIPPS) are used in the process industries to reduce the risk that a system can exceed its design pressure.
  89. [89]
    The Bhopal tragedy and its impact on process safety - Cogent Skills
    Dec 3, 2024 · The Bhopal disaster had a significant impact on how the global chemical industry approaches process safety. It spurred regulatory change.
  90. [90]
    The Bhopal tragedy: its influence on process and community safety ...
    This tragedy has forever altered the process industry landscape and led to widespread changes in regulations and development of standards and management systems ...
  91. [91]
    Proof-Testing | Emerson US
    The regularity of proof-tests is based on the safety integrity level of the safety loop and probability of a device failure (PFD). To ensure a device continues ...
  92. [92]
    [PDF] What is good practice for the proof testing of safety instrumented ...
    Typically the required PFDavg can be achieved with annual or maybe even 2 yearly testing.
  93. [93]
    [PDF] HIGH INTEGRITY PRESSURE PROTECTION SYSTEMS (HIPPS)
    The HIPPS must be operated, maintained and tested throughout the life of the plant. The high integrity of HIPPS is often achieved through the use of frequent ...
  94. [94]
    Common Issues with Aging Industrial Control Systems
    Jul 1, 2025 · Common issues include obsolete hardware/software, component degradation, electrical failures, lack of documentation, and outdated safety ...
  95. [95]
    Retrofitting Legacy Industrial Equipment with IoT: Protocol Bridges ...
    Jul 14, 2025 · But bringing old systems online is not without challenges: mismatched protocols, missing data granularity, and cybersecurity exposures are ...
  96. [96]
    The challenges of legacy systems and benefits of new technology in ...
    Oct 28, 2025 · A plant needed to migrate from its obsolete 1980s DCS to a modern system to avoid loss of support and improve usability.
  97. [97]
    [PDF] Medical devices Safety and performance - IEC
    IEC 60601-1 facilitates compliance with legal and regulatory requirements specific to the healthcare area. It guides manufacturers in the identification of all ...
  98. [98]
    Safety classes according to IEC 62304 - Johner Institute
    Oct 15, 2025 · IEC 62304 defines three software safety classes (A, B, C) based on the potential risk to patients, with class C having the highest requirements.Significance of safety classes... · Impact of the safety class on...
  99. [99]
    Safety-assured development of the GPCA infusion pump software
    This paper presents our effort of using model-driven engineering to establish a safety-assured implementation of Patient-Controlled Analgesic (PCA) infusion ...
  100. [100]
    Magnetic resonance imaging and cardiac pacemaker safety at 1.5 ...
    The study was done to determine whether patients with pacemakers could safely undergo magnetic resonance imaging (MRI) at 1.5-Tesla (T).
  101. [101]
    Ransomware Attacks on Hospitals Have Changed | Cybersecurity
    For example, the 2017 WannaCry ransomware attack infected 1,200 diagnostic devices, caused many others to be temporarily taken out of service to prevent the ...
  102. [102]
    WannaCry Legacy: Securing Medical Devices - Asimily
    May 12, 2017 · The WannaCry legacy includes continued targeting of healthcare, the use of legacy exploits, and the difficulty of securing medical devices due ...
  103. [103]
    IEC 62366-1:2015 - Medical devices — Part 1 - ISO
    IEC 62366-1:2015 specifies a PROCESS for a MANUFACTURER to analyse, specify, develop and evaluate the USABILITY of a MEDICAL DEVICE as it relates to SAFETY.
  104. [104]
    An Ethical Risk Management Approach for Medical Devices | RMHP
    Jun 3, 2021 · This study has focused on providing a hybrid risk management approach for organizations noting the use of ISO 14971 activities as well as the PMBOK activities.Method · Duty-Based Ethics · Risk Management Framework
  105. [105]
    Ventilator Recall: Philips Removes Certain DreamStation Devices
    Sep 12, 2025 · This recall involves removing certain devices from where they are used or sold. The FDA has identified this recall as the most serious type.
  106. [106]
  107. [107]
  108. [108]
    IEC 61513:2011
    IEC 61513:2011 provides requirements and recommendations for the overall I&C architecture which may contain either or both technologies.Missing: protection | Show results with:protection
  109. [109]
    Functional safety and AI systems - ISO/IEC TR 5469:2024
    In stockThis document describes the properties, related risk factors, available methods and processes relating to use of AI inside a safety related function to realize ...
  110. [110]
    [PDF] department of defense standard practice system safety
    Jul 14, 2025 · 3.1 Systems engineering Functional disciplines “following MIL-STD-882E system safety methodology” shall comply with all of para 4.3 and para 4.4 ...