Search

The Chief risk officer : what does it look like and how do you get there

<?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">MAP20071507545</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20080418125545.0</controlfield>
    <controlfield tag="007">hzruuu---uuuu</controlfield>
    <controlfield tag="008">060116e20050901usa||||    | |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">MAPA20080138493</subfield>
      <subfield code="a">Lee, Charles R.</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="4">
      <subfield code="a">The Chief risk officer</subfield>
      <subfield code="b">: what does it look like and how do you get there</subfield>
      <subfield code="c">Charles R. Lee and Prakash Shimpi</subfield>
    </datafield>
    <datafield tag="520" ind1="8" ind2=" ">
      <subfield code="a">Chief risk officer generally have a set of specific responsibilities that amount to creating a risk-aware culture in the organization.The first is assuring that the organization has processes in place so that it complies with the very much heightened risk management expectatives of shareholders, regulators , and even elected officials. The second is developing and introducing an integrative risk management framework</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080546991</subfield>
      <subfield code="a">Empresas</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080591199</subfield>
      <subfield code="a">Gerentes de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080603038</subfield>
      <subfield code="a">Prevención de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080612177</subfield>
      <subfield code="a">Programas de prevención</subfield>
    </datafield>
    <datafield tag="650" ind1="0" ind2="1">
      <subfield code="0">MAPA20080536534</subfield>
      <subfield code="a">ERM</subfield>
    </datafield>
    <datafield tag="700" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080232986</subfield>
      <subfield code="a">Shimpi, Prakash A.</subfield>
    </datafield>
    <datafield tag="740" ind1="0" ind2=" ">
      <subfield code="a">Risk management</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="t">Risk management</subfield>
      <subfield code="d">New York</subfield>
      <subfield code="g">Vol.52, nº 9, September 2005 ; p. 34-38</subfield>
    </datafield>
  </record>
</collection>