17.03.2013 Views

JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES

JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES

JPMORGAN CHASE WHALE TRADES: A CASE HISTORY OF DERIVATIVES RISKS AND ABUSES

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

158<br />

analysis of its risk management structure, risk personnel, and why specific risk metrics in place<br />

at the time of the trades were disregarded.<br />

B. Risk Management Structure at CIO<br />

JPMorgan Chase provides a broad overview of its risk management practices in its<br />

Annual Report. The 2011 Annual Report describes risk management at the firm in the following<br />

way:<br />

“Risk Management operates independently of the lines of businesses to provide<br />

oversight of firmwide risk management and controls, and is viewed as a partner in<br />

achieving appropriate business objectives. Risk Management coordinates and<br />

communicates with each line of business through the line of business risk<br />

committees and chief risk officers to manage risk. The Risk Management<br />

function is headed by the Firm’s Chief Risk Officer, who is a member of the<br />

Firm’s Operating Committee and who reports to the Chief Executive Officer and<br />

is accountable to the Board of Directors, primarily through the Board’s Risk<br />

Policy Committee. The Chief Risk Officer is also a member of the line of<br />

business risk committees. Within the Firm’s Risk Management function are units<br />

responsible for credit risk, market risk, country risk, private equity risk and<br />

operational risk, as well as risk reporting, risk policy and risk technology and<br />

operations. Risk technology and operations is responsible for building the<br />

information technology infrastructure used to monitor and manage risk.” 868<br />

JPMorgan Chase maintained a number of bankwide risk limits as well as risk limits for<br />

each major business unit. Bankwide risk limits were set by the bank’s CEO and CRO, 869 and<br />

were regularly discussed with the Risk Policy Committee of the Board of Directors. 870 The<br />

business unit risk limits were developed by each unit’s head and risk management personnel, 871<br />

in consultation with the bank’s Chief Risk Officer. 872 The CIO’s limits depended on overall firm<br />

risk appetite as well as its own mandate, which required a dialogue between the CIO and firm<br />

managers. 873 Risk limits were a topic of discussion at the CIO’s annual “Business Review,” a<br />

formal meeting attended by top executives of the bank and CIO. 874 The CIO’s 2012 Business<br />

Review was held in February and attended by Mr. Dimon, Mr. Braunstein, Mr. Zubrow, and Mr.<br />

Hogan, as well as Ms. Drew, Mr. Goldman, Mr. Macris, Ms. Tse, and Mr. Wilmot. 875<br />

868<br />

See 3/30/2012, “2011 Annual Report,” JPMorgan Chase publication, at 125,<br />

http://files.shareholder.com/downloads/ONE/1839748086x0x556139/75b4bd59-02e7-4495-a84c-<br />

06e0b19d6990/JPMC_2011_annual_report_complete.pdf.<br />

869<br />

3/2012 presentation prepared by JPMorgan Chase entitled “Market Risk Limits,” at 12, OCC-SPI-00117682.<br />

870<br />

Subcommittee interview of John Hogan and Ashley Bacon, JPMorgan Chase (9/4/2012). See also 3/20/2012<br />

Directors Risk Policy Committee meeting minutes for JPMorgan Chase, JPM-CIO-PSI-0013563.<br />

871<br />

3/2012 presentation prepared by JPMorgan Chase entitled “Market Risk Limits,” at 12, OCC-SPI-00117682.<br />

872<br />

Subcommittee interview of Peter Weiland, CIO (8/29/2012);<br />

873<br />

Subcommittee interview of Michael Cavanagh, JPMorgan Chase (12/12/2012).<br />

874<br />

Subcommittee interview of John Hogan and Ashley Bacon, JPMorgan Chase (9/4/2012).<br />

875<br />

2/2012 presentation prepared by JPMorgan Chase entitled “CIO February 2012 Business review,” at 1, JPM-CIO-<br />

PSI 0000224-267.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!