The Safety Lifecycle According to IEC 61508: A Blueprint for Functional Safety

 

In today’s increasingly automated world, the safe operation of industrial processes and systems is paramount. From chemical plants and power stations to complex machinery and transportation systems, the potential for catastrophic failures necessitates a rigorous and systematic approach to safety. This is where the international standard IEC 61508 comes into play. It provides a comprehensive framework for the functional safety of electrical, electronic, and programmable electronic (E/E/PE) systems. At the heart of this standard lies the concept of the safety lifecycle, a structured engineering process that guides organizations from the initial concept of a safety system to its eventual decommissioning.

This blog post will delve deep into the intricacies of the IEC 61508 safety lifecycle, providing a 2000-word guide complete with conceptual block diagrams to illuminate each phase. By understanding this lifecycle, organizations can not only ensure compliance with the standard but also cultivate a robust safety culture that protects people, the environment, and their assets.

 

The Foundation: What is Functional Safety and IEC 61508?

 

Functional safety is the part of the overall safety of a system or piece of equipment that depends on the correct functioning of its safety-related systems. These systems are designed to automatically prevent or mitigate the consequences of hazardous events. For example, a pressure sensor in a chemical reactor that triggers an emergency shutdown sequence when a dangerous pressure level is detected is a functional safety system.

IEC 61508, titled “Functional safety of electrical/electronic/programmable electronic safety-related systems,” provides a generic, risk-based approach to designing, implementing, and maintaining these safety systems. A key principle of the standard is that safety must be designed into a system from the very beginning and managed throughout its entire life. The safety lifecycle is the roadmap for achieving this.

The lifecycle is typically represented as a series of phases, often grouped into three main stages:

  • Analysis Phases (Phases 1-5): Understanding the hazards and defining the required safety measures.

  • Realisation Phases (Phases 6-13): Designing, building, and installing the safety systems.

  • Operation Phases (Phases 14-16): Ensuring the ongoing integrity and performance of the safety systems.

Let’s explore each of these phases in detail.


 

Part 1: The Analysis Phases – Laying the Groundwork for Safety

 

The initial phases of the safety lifecycle are crucial for establishing a solid foundation for functional safety. Mistakes or omissions in this stage can have significant and costly repercussions later in the project.

 

Phase 1: Concept

 

Objective: To define the equipment under control (EUC), its intended purpose, and the potential for hazards.

Inputs:

  • A high-level idea or need for a process or system.

  • Initial understanding of the operational environment.

Outputs:

  • A documented description of the EUC.

  • A preliminary assessment of potential major hazards.

  • The initial decision on whether a safety-related system is likely to be required.

Block Diagram Description: Concept Phase

A simple block diagram for this phase would show an input box labeled “Initial Idea/Requirement” leading to a central process box “Concept Definition.” From this central box, three output boxes emerge: “EUC Description,” “Preliminary Hazard List,” and “Initial Safety Assessment.” This visually represents the transformation of a high-level concept into tangible initial documents.

 

Phase 2: Overall Scope Definition

 

Objective: To clearly define the boundaries of the EUC and the scope of the hazard and risk analysis.

Inputs:

  • EUC Description from Phase 1.

  • Preliminary Hazard List from Phase 1.

Outputs:

  • A detailed definition of the EUC boundaries.

  • The scope and plan for the hazard and risk analysis.

  • Identification of any relevant legal and regulatory safety requirements.

Block Diagram Description: Scope Definition

This diagram would start with the “EUC Description” and “Preliminary Hazard List” as inputs. These feed into a process block called “Scope Definition and Planning.” The outputs from this block would be “Detailed EUC Boundary,” “Hazard and Risk Analysis Plan,” and “List of Applicable Regulations.”

 

Phase 3: Hazard and Risk Analysis

 

Objective: To systematically identify all credible hazards associated with the EUC and to analyze the associated risks.

Inputs:

  • Detailed EUC Boundary from Phase 2.

  • Hazard and Risk Analysis Plan from Phase 2.

  • Process and system design information.

Outputs:

  • A comprehensive list of identified hazards and hazardous events.

  • An analysis of the sequence of events leading to each hazard.

  • An estimation of the likelihood and consequences of each hazardous event.

  • A determination of the “as-is” risk for each hazard.

Block Diagram Description: Hazard and Risk Analysis

This diagram illustrates a cyclical process. “System Information” and the “Hazard and Risk Analysis Plan” feed into a loop. The first step in the loop is “Hazard Identification (e.g., HAZOP, FMEA).” The output, “Identified Hazards,” then feeds into “Risk Estimation (Likelihood & Consequence).” The result is an “Unmitigated Risk Profile.” This entire process is iterated until all foreseeable hazards are analyzed.

 

Phase 4: Overall Safety Requirements

 

Objective: To specify the safety functions required to reduce the identified risks to a tolerable level.

Inputs:

  • Unmitigated Risk Profile from Phase 3.

  • Tolerable risk criteria for the organization or industry.

Outputs:

  • A set of overall safety functions.

  • The required Safety Integrity Level (SIL) for each safety function.

  • A clear statement of what each safety function is intended to achieve.

Safety Integrity Level (SIL): A Quick Primer

SIL is a discrete level (1 to 4) for specifying the required risk reduction provided by a safety function. SIL 1 represents the lowest level of risk reduction, while SIL 4 represents the highest. The determination of the required SIL is a critical outcome of the risk assessment process.

 

Phase 5: Safety Requirements Allocation

 

Objective: To allocate the specified safety functions and their SILs to designated safety-related systems.

Inputs:

  • Overall safety functions and their SILs from Phase 4.

  • A high-level architecture of the overall control and safety systems.

Outputs:

  • A clear allocation of safety functions to specific E/E/PE safety-related systems, other technology safety-related systems (e.g., mechanical trips), and external risk reduction facilities (e.g., dikes, blast walls).

  • The safety requirements specification for each safety-related system.

Block Diagram Description: Safety Requirements Allocation

This diagram would show the “Overall Safety Functions & SILs” as the primary input. This feeds into a central process block called “Allocation of Safety Requirements.” From this block, multiple arrows point to different output boxes representing the various layers of protection: “E/E/PE Safety-Related Systems,” “Other Technology Safety-Related Systems,” and “External Risk Reduction Facilities.” This demonstrates how the overall safety is distributed among different technologies.


 

Part 2: The Realisation Phases – Bringing Safety Systems to Life

 

With a clear understanding of what needs to be protected against and how, the realisation phases focus on the design, engineering, and implementation of the safety systems. This is often represented by the “V-model,” where the design and development steps on the left side of the “V” are mirrored by testing and validation steps on the right side.

 

The V-Model in IEC 61508

 

The V-model is a graphical representation of the system development lifecycle. It highlights the relationships between each phase of the development life cycle and its associated phase of testing. In the context of IEC 61508, it emphasizes that verification (checking that a phase has been correctly implemented) and validation (confirming that the overall system meets the safety requirements) are not one-time events but are performed throughout the lifecycle.

Block Diagram Description: The V-Model for IEC 61508

The V-model diagram would have the design and development phases on the left, descending, and the integration and testing phases on the right, ascending.

  • Top Left: Overall Safety Requirements Specification

  • Descending Left:

    • E/E/PE System Design

    • Hardware Design

    • Software Design

  • Bottom of the V: Module Implementation (Hardware and Software)

  • Ascending Right:

    • Module Testing

    • Integration Testing (Hardware and Software)

    • System Integration Testing

  • Top Right: Overall Safety Validation

Horizontal arrows connect corresponding levels of the “V,” representing the verification activities that ensure the outputs of each design phase meet their requirements.

 

Phase 6: Overall Operation and Maintenance Planning

 

Objective: To develop a plan for the operation and maintenance of the safety-related systems to ensure their integrity throughout their operational life.

Inputs:

  • Safety requirements specification from Phase 5.

  • Information about the E/E/PE systems to be used.

Outputs:

  • A comprehensive operation and maintenance plan.

  • Procedures for proof testing of safety functions.

  • Training requirements for operations and maintenance personnel.

 

Phase 7: Overall Validation Planning

 

Objective: To develop a plan for the validation of the overall safety-related systems.

Inputs:

  • Overall safety requirements specification from Phase 5.

  • Design documentation for the safety-related systems.

Outputs:

  • A detailed validation plan, including the test procedures, environment, and acceptance criteria.

  • This plan will be used in a later phase to confirm that the safety systems meet all their specified requirements.

 

Phase 8: Overall Installation and Commissioning Planning

 

Objective: To develop a plan for the installation and commissioning of the safety-related systems.

Inputs:

  • Design and engineering documentation for the safety systems.

  • Site-specific information and constraints.

Outputs:

  • A detailed installation and commissioning plan.

  • Procedures for site acceptance testing.

 

Phase 9: E/E/PE System Realisation

 

Objective: To design and build the E/E/PE safety-related systems in accordance with the safety requirements specification.

Inputs:

  • Safety requirements specification for the E/E/PE systems from Phase 5.

  • The V-model development plan.

Outputs:

  • Detailed hardware and software design.

  • The implemented and tested hardware and software modules.

  • Verification records for each design and development step.

This phase is a microcosm of a full development lifecycle and is often broken down into further sub-phases for hardware and software development, each with its own lifecycle as prescribed in Parts 2 and 3 of IEC 61508 respectively.

 

Phase 10: Other Technology Safety-Related Systems & External Risk Reduction Facilities Realisation

 

Objective: To design and implement the non-E/E/PE safety systems and external facilities.

Inputs:

  • Safety requirements specification for these systems from Phase 5.

Outputs:

  • The designed and built mechanical safety devices (e.g., pressure relief valves).

  • The constructed external risk reduction facilities (e.g., bunds).

 

Phase 11: Overall Installation and Commissioning

 

Objective: To install and commission all the safety-related systems according to the plan.

Inputs:

  • The realized safety-related systems from Phases 9 and 10.

  • The installation and commissioning plan from Phase 8.

Outputs:

  • The fully installed and commissioned safety systems.

  • Installation and commissioning records.

  • Site acceptance test reports.

 

Phase 12: Overall Safety Validation

 

Objective: To validate that the installed safety-related systems meet the overall safety requirements.

Inputs:

  • The installed and commissioned safety systems.

  • The validation plan from Phase 7.

  • The overall safety requirements specification from Phase 4.

Outputs:

  • A validation report confirming that the safety functions perform as specified and achieve the required SIL.

  • A documented statement that the system is safe to operate.

Block Diagram Description: The Realisation and Validation Flow

A flowchart for these phases would show a progression from planning to implementation and finally to validation. “Operation & Maintenance Planning,” “Validation Planning,” and “Installation & Commissioning Planning” are parallel activities. Their outputs, along with the “Realised E/E/PE Systems” and “Other Safety Systems,” all converge on the “Overall Installation and Commissioning” phase. The output of this phase, the “Installed System,” is the input to “Overall Safety Validation,” which ultimately produces the “Validated Safety System” ready for operation.


 

Part 3: The Operation Phases – Maintaining Safety Over Time

 

The job is not done once the system is up and running. The operational phases of the safety lifecycle are critical for ensuring that the safety integrity of the systems is maintained throughout their service life.

 

Phase 13: Overall Operation, Maintenance, and Repair

 

Objective: To operate and maintain the safety-related systems in a way that sustains their required safety integrity.

Inputs:

  • The validated safety system.

  • The operation and maintenance plan from Phase 6.

Outputs:

  • Ongoing operational records.

  • Maintenance and proof test records.

  • Analysis of failure data.

This phase is a continuous loop of operating, monitoring, testing, and repairing the safety systems. Regular proof testing is particularly important to detect hidden failures that could prevent a safety function from working when required.

 

Phase 14: Overall Modification and Retrofit

 

Objective: To manage any changes to the safety-related systems in a way that does not compromise safety.

Inputs:

  • A request for modification.

  • The original safety lifecycle documentation.

Outputs:

  • An impact analysis of the proposed change.

  • A revised safety lifecycle documentation.

  • The re-validated safety system after modification.

Any modification, no matter how small, must trigger a return to the relevant phases of the safety lifecycle to ensure that the change is properly assessed, designed, implemented, and validated.

 

Phase 15: Decommissioning or Disposal

 

Objective: To safely take the safety-related systems out of service at the end of their life.

Inputs:

  • A decision to decommission the EUC or the safety system.

  • The safety lifecycle documentation.

Outputs:

  • A decommissioning plan.

  • A safe state of the EUC after the safety system is removed.

  • Records of the decommissioning process.

Even the end of a system’s life needs to be managed to avoid introducing new hazards.

 

Phase 16: Verification and Functional Safety Assessment

 

This is not a sequential phase but an ongoing activity that spans the entire safety lifecycle.

Verification: The process of confirming that the output of a particular phase of the lifecycle meets the requirements of its input. For example, verifying that the detailed software design meets the requirements of the software requirements specification.

Functional Safety Assessment (FSA): A systematic and independent review to judge the functional safety achieved by the safety-related systems. IEC 61508 requires FSAs to be carried out at various stages of the lifecycle to provide an independent judgment on the adequacy of the safety measures.

Block Diagram Description: The Continuous Nature of Verification and Assessment

Imagine the entire safety lifecycle diagram enclosed in a larger box. Two continuous arrows run alongside the lifecycle phases. One is labeled “Verification,” with smaller arrows pointing to the interfaces between each phase, indicating that verification is performed at each step. The other continuous arrow is labeled “Functional Safety Assessment,” with arrows pointing to key milestones within the lifecycle (e.g., after the analysis phases, after the realisation phases, and during operation), signifying periodic independent reviews.


 

Conclusion: A Culture of Safety

 

The IEC 61508 safety lifecycle is more than just a set of mandatory steps; it’s a philosophy for managing risk in a complex world. By providing a structured and auditable framework, it helps organizations to move beyond a reactive approach to safety and to proactively design and maintain systems that are inherently safer.

The journey through the 16 phases, from the initial spark of a concept to the final decommissioning, is a comprehensive one. The emphasis on analysis, the rigor of the realisation process as depicted in the V-model, and the ongoing vigilance required during operation all contribute to a holistic approach to functional safety. The block diagrams presented conceptually illustrate the flow of information and activities, providing a mental model for navigating this crucial standard.

Ultimately, embracing the IEC 61508 safety lifecycle is an investment in the long-term safety and sustainability of any operation. It fosters a culture where safety is not an afterthought but a core value, ensuring that as our technology advances, our commitment to protecting lives and the environment keeps pace.

Leave a Reply

Your email address will not be published. Required fields are marked *