<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01203nab a2200193   4500</leader>
  <controlfield tag="005">20260520004607.0</controlfield>
  <controlfield tag="008">260224s2018    xxu                 ing  </controlfield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">Ingl&#xE9;s</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Guidelines for Designing Risk Matrices</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">mar. 2018</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">09/10/2020 ; 09/10/2020</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">7 p. ; 49-55</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Risk matrices are used widely in process safety to rate and rank risks posed by processes to help with decision making. For example, commonly they are used in process hazard analysis to rate the risks of hazard scenarios and determine the need for risk reduction. However, there are no standards for risk matrices in process safety. Companies develop their own without the benefit of established industry guidelines. Risk matrices are deceptively simple but their design and use are rife with pitfalls, even for experienced users. Some of these pitfalls are not obvious and invalid risk ratings can result which are unrecognized. Guidelines for constructing risk matrices that address these pitfalls are provided.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">1</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Process safety progress</subfield>
    <subfield code="g"></subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Baybutt, Paul</subfield>
    <subfield code="9">20489</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">193602</subfield>
    <subfield code="d">193602</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">261321</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200065964</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200065964</subfield>
    <subfield code="r">2026-03-06 00:38:34</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
