SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL - Tuv-fs.com
SAFETY MANUAL - Tuv-fs.com
- No tags were found...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>SAFETY</strong> <strong>MANUAL</strong><br />
2. <strong>SAFETY</strong> PRINCIPLES<br />
2.1 INTRODUCTION<br />
This paragraph provides an overview of generic safety principles with emphasis on<br />
the system integration process. These principles are applicable to all safety-related<br />
systems, including, but not limited to, the 8000 series system.<br />
2.2 <strong>SAFETY</strong> MANAGEMENT<br />
A prerequisite for the achievement of functional safety is the implementation of<br />
procedural measures applicable to the safety lifecycle; these are collectively<br />
referred to as a Safety Management System. The Safety Management System<br />
defines the generic management and technical activities necessary for functional<br />
safety. In many cases, the Safety Management and Quality systems will be<br />
integrated within a single set of procedures. It is highly re<strong>com</strong>mended that the<br />
integrator have a quality management system in accordance with ISO9000.<br />
The safety management system shall include:<br />
• A statement of the policy and strategy to achieving functional safety.<br />
• A Safety Planning Procedure. This shall result in the definition of the<br />
safety lifecycle stages to be applied, the measures and techniques to be<br />
applied at each stage, and responsibilities for <strong>com</strong>pleting these activities.<br />
• Definitions of the records to be produced and methods of managing these<br />
records, including change control. The change control procedures shall<br />
include records of modification requests, the impact analysis of proposed<br />
modifications and the approval of modifications. The baseline for change<br />
control shall be defined clearly.<br />
• Configuration items shall be uniquely identified and include version<br />
information, e.g. system and safety requirements, system design<br />
documentation and drawings, application software source code, test<br />
plans, test procedures and results.<br />
• Methods of ensuring that persons are <strong>com</strong>petent to undertake their<br />
activities and fulfil their responsibilities.<br />
Expansion of these requirements is included within the following sub-paragraphs.<br />
Doc Number P8094<br />
Issue 14 September 2003 Page 27 of 67