Roles: Safety-Engineer

The purpose of this document is to provide an overview of the documents referenced in the Safety Handbook that are used for the development of functionally safe products within PCP R&D. Some of the guidelines, tools and templates have been created in CTQMS and are retained within PCP R&D Processes for continued support of existing, “brownfield” safety products. This “brownfield” QMS content has been reduced by number and is expected to further reduce over time as CTQMS guidelines, tools and templates are continued to be migrated to PCP R&D Processes solutions and older safety products reach the end of their product lifecycles.

General Introduction

The objective of this guideline is to describe the procedure of how to perform HAZOP analyses for Electrical/Electronic/Programmable (E/E/PE) safetyrelated systems, explain the reasons for performing a HAZOP, give an overview of the process, and explain the terminology and concept. The HAZOP is a recommended technique in IEC 61508.

This guideline aims to describe how to conduct internal Functional Safety Management (FSM) audits in ABB PCP R&D, as well as how to monitor and handle external FSM audits conducted by the Independent Safety Assessor (ISA) for ABB PCP R&D.

This guide describes how to manage documents related to functional safety certifications. It also includes information on how to manage continuous updates of such documents under Details.

Various certifications are applied for in the development of products. This guide covers the ten activities of the general certification flow, and includes specific information regarding marine certifications, certifications for hazardous areas, certification affecting manufacturers, and the order of certification applications.

This document provides guidance on how to handle interferencefree product development for new products and for maintenance of existing products.

The safety engineer (SE) is responsible for ensuring that the R&D organization adheres to the applicable safety standards, such as the IEC 61508 or IEC 61511, and that safety is achieved and demonstrated for all safetyrelated [^1] development and maintenance.

This code review guideline is written for those in the Control organization working with Git and includes the functional safety related aspects to adhere to. The guideline is directed to both source code level as well as feature level.