What is missing from the RMIS design? : why enterprise risk management is not working

<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" 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">
  <record>
    <leader>00000nab a2200000 i 4500</leader>
    <controlfield tag="001">MAP20071502830</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20080418123517.0</controlfield>
    <controlfield tag="007">hzruuu---uuuu</controlfield>
    <controlfield tag="008">021030e20021001gbr||||    | |00010|eng d</controlfield>
    <datafield tag="040" ind1=" " ind2=" ">
      <subfield code="a">MAP</subfield>
      <subfield code="b">spa</subfield>
    </datafield>
    <datafield tag="084" ind1=" " ind2=" ">
      <subfield code="a">7</subfield>
    </datafield>
    <datafield tag="100" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080087487</subfield>
      <subfield code="a">Warren, Brian</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">What is missing from the RMIS design?</subfield>
      <subfield code="b">: why enterprise risk management is not working</subfield>
      <subfield code="c">Brian Warren</subfield>
    </datafield>
    <datafield tag="520" ind1="8" ind2=" ">
      <subfield code="a">Many risk managers have attempted to take enterprise risk management (ERM) from a slick consulting pitch to a pratical management system.The article offers suggestions for next steps in the evolution of risk management information system (RMIS) design, which will , if adopted, make RMIS an integral part of ERM practices</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080591182</subfield>
      <subfield code="a">Gerencia de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080584771</subfield>
      <subfield code="a">Diseño de sistemas</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080592875</subfield>
      <subfield code="a">Protección de datos</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080594626</subfield>
      <subfield code="a">Análisis de sistemas</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080612580</subfield>
      <subfield code="a">Sistemas de información</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080584344</subfield>
      <subfield code="a">Control de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080613099</subfield>
      <subfield code="a">Análisis costo-beneficio</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080606114</subfield>
      <subfield code="a">Estructura empresarial</subfield>
    </datafield>
    <datafield tag="710" ind1="2" ind2=" ">
      <subfield code="0">MAPA20080459970</subfield>
      <subfield code="a">Risk and Insurance Management Society</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="d">New York</subfield>
      <subfield code="g">October 2002 ; p. 30-34</subfield>
      <subfield code="t">Risk Management</subfield>
    </datafield>
  </record>
</collection>