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.

294<br />

temporary VaR limit increase, Mr. Dimon told the Subcommittee that he did not recall the CIO’s<br />

change to its VaR model and that he became aware of the issue only after “things blew up.” 1627<br />

He told the Subcommittee that he had relied on his risk management staff to inform him about<br />

VaR model issues and provide additional details if there were a problem. 1628 Mr. Braunstein told<br />

the Subcommittee that he, too, despite receiving the emails, was not sure if he was aware in<br />

January that a new CIO VaR model had been adopted that month. 1629<br />

In February 2012, the CIO’s VaR model change was again addressed during a CIO<br />

1630<br />

February Business Review meeting attended by both Mr. Braunstein and Mr. Dimon. Prior<br />

to the meeting, Mr. Braunstein and Mr. Dimon each received a presentation, reprinted below,<br />

which included a section entitled, “VaR Highlights,” describing the CIO’s new VaR model.<br />

Reporting, JPMorgan Chase, to Jamie Dimon, JPMorgan Chase, Douglas Braunstein, JPMorgan Chase, and others,<br />

“JPMC Firmwide VaR – Daily Update – COB 01/23/2012,” JPM-CIO-PSI 0003715 (noting that the CIO’s<br />

“improved VaR model” will reduce the CIO’s VaR “by 44%”).<br />

1627 Subcommittee interview of Jamie Dimon, JPMorgan Chase (9/19/2012).<br />

1628 Id.<br />

1629 Subcommittee interview of Douglas Braunstein, JPMorgan Chase (9/12/2012).<br />

1630 2/2012 “CIO February 2012 Business Review,” JPM-CIO-PSI 0000289, at 290 (“Today’s Attendees, Operating<br />

Committee, Jamie Dimon, Doug Braunstein,” and others.).

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

Saved successfully!

Ooh no, something went wrong!