Complete safety engineering services

Safety Engineering works to assure that safety concerns are methodically addressed in every phase of a product’s life cycle. To do this, a safety engineer plans and incorporates a structured safety program, often based on MIL-STD-882 requirements, for each development project. The safety program includes the development of a detailed plan specifically tailored to each project, preparation of safety-related checklists for each life cycle phase, audits to assess compliance to the safety plan, and preparation of hazard analyses.

Always important but now essential

A hazard analysis is a structured technique used to assess actual and potential hazards associated with virtually any kind of product. Hazards, or safety hazards, are conditions that may adversely affect people, equipment or the environment. Different safety hazards are often associated with different phases of a product’s life cycle, which may include development, test, transportation, installation, operation, maintenance, repair and disposal.

Hazard analysis can be applied to practically every product because even simple objects can cause injury if misused. The approach is straightforward but requires understanding and know-how.

  • Identify all possible hazards
  • Assess each hazard’s severity
  • Determine criticality of hazard
  • Determine acceptability of hazard’s criticality
  • Mitigate or elimination of hazard
  • Analysis product improvements

Button Text

Free Whitepaper Download
Improving System Safety with Message-Level Software FMEA

What’s Inside: System reliability and safety can be improved by applying failure modes and effects analysis (FMEA) to system software. Performing software FMEA at the message level – an examination of data and control messages exchanged between software configuration items – can give an excellent assessment of system robustness and safety because many kinds of failures cause unexpected message contents and timing. FMEA at the message level can assess effects of many problems caused by low-level faults such as coding errors, timing problems, hardware failure, and unexpected input data.