Safety and Hazards

Safety engineering is about showing, with evidence, that the hazards a system could create have been found, reduced as far as is reasonable and kept under control through design, construction, handover and operation. It draws on hazard identification, safety requirements, integrity targets and a clear legal test for when risk is low enough.

This hub is for systems, safety and project engineers who need to run a hazard log, write safety requirements or build an assurance case. It starts with the core ideas, then covers safety integrity levels and progressive assurance, residual risk and its transfer at handover, safety on construction projects, and the growing overlap between safety and cyber security in connected systems.

Start here

  • What is a hazard log? — the purpose and contents of a hazard log, and best practice for keeping it live
  • Safety requirements — what makes a requirement a safety requirement and how it links to hazard control
  • Safety assurance step by step — how to monitor, record and evaluate safety performance within a Safety Management System
  • SFAIRP vs ALARP — how the two risk-reduction principles differ in law and practice, and what that means

Safety integrity and progressive assurance

Integrity targets say how reliable a safety function must be, and progressive assurance builds the evidence as the project goes.

Residual risk and risk transfer

Some risk always remains, and it has to be handed from builder to operator knowingly.

Construction safety

Construction sites carry their own hazards and their own expectations for safety assurance.

Safety and security

In connected systems a security breach can become a safety failure, so the two must be engineered together.

Related hubs: reliability, availability and maintainability (RAMS), requirements engineering, systems engineering. See also: RAMS and safety, FMECA, operational readiness and handover.