Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Duke Fuqua Trade Report 2.21.11

Duke Fuqua Trade Report 2.21.11

Ratings: (0)|Views: 18|Likes:
Published by Hedgefund Live
Duke Fuqua's report on trades for the week ending Feb. 25, 2011: PFE, BMY, PJP. The Fuqua desk explores pairs trading within the healthcare sector and the pharmaceutical industry in particular.
Duke Fuqua's report on trades for the week ending Feb. 25, 2011: PFE, BMY, PJP. The Fuqua desk explores pairs trading within the healthcare sector and the pharmaceutical industry in particular.

More info:

Published by: Hedgefund Live on Feb 28, 2011
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Report on Trades during week of Feb 21
 HedgeFundLive02-26-2011  Fuqua Team Lead: Larry LevanNeil AdvaniJustin AndrewsSadaf HossainFusheng Li, MD,PhDLina RenZidong Zhang, PhD 
HedgeFundLiveTrading Report Feb21 Page 2 of 4
 As mentioned in the previous report, one of our strategies going forward was experimenting with pairstrading.  There were two types of pairs under consideration: 1. Pair a company with its ETF sector.  Hedge against events of individual companies by pairing it with arespective ETF.2. Find two sectors that would hedge each other-i.e. two sector ETFs. First, we used our industry knowledge to gage potential companies or sectors that may have a reason tooutperform or underperform their ETF or work as a hedge to another sector.  Concerning the hedgingside, this proved to be fairly difficult because as a whole, the health care sectors were trending up withlittle presence of natural hedges.  This meant that there seemed to be continued confidence in thehealthcare sector as a whole rather than if this sector was performing well, a corresponding sector wouldnot. However, the only sector that showed negative growth over the past 3 months was pharma but it wasdifficult to identify what pharma could potentially act as a hedge to on a sector basis.  Due to this recentnegative growth in pharma though, we decided to go beyond sectors and into companies and hencelearning more to option #1 rather than #2 for the time being.  To this end, we began looking atpharmaceutical companies and their respective ETFs.  Part of this strategy would be to look at historicaldata of selected companies and compare them to their sector ETF to see how they correlated especiallygiven a history of company events and if there would be a potential pair. We took a look at a quintessential pharma company, Pfizer, because of a long active history of events ofdrug approvals and drug failures on which to compare the effect on its stock price and its correlation tothe ETF pharma sector.  We also took a look at BristolMyers Squibb because it is a company that willhave an FDA ruling on a new drug soon.  Below we will explain our methodology and some of thelimitations to this approach of trading.  
Discussion on event-based trading strategy 
 As the next step, we try to gain exposure to single health care companies where we take bets on eventoutcomes. To validate this idea, we did the following analysis on key assumptions.
Analysis on Events-Price-Spread relationship 
 For such a strategy to work, the following assumptions need to be true:1. There are enough key events/news for us to bet on, for example drug approvals.2. We can predict some of the event outcomes based on our health care knowledge.3. The market interpretation of these event outcomes drives underlying stock price changes.4. We can predict the direction of underlying stock price changes by interpreting how the marketviews particular event outcomes. To validate this event-based trading strategy, we chose to dig into historical data for Pfizer and BMS inthe past 20 months to examine assumption #3 and #4. 
HedgeFundLiveTrading Report Feb21 Page 3 of 4
  As the above table shows, we took the key events featuring Pfizer in the past 20 months, and assignedratings on those events based on our interpretation on how market would react. The ratings range from -10 to 20. Then we checked weekly Pfizer price changes given these events. In addition, to remove theeffects of industry wide factors and only focus on Pfizer, we also checked changes of Pfizer – PJPspread, which is the difference between Pfizer and PJP(diversified Pharma ETF). The findings are:1. The outcomes of these single events didn’t cause predictable changes in Pfizer’s stock price. Asthe analysis shows, the weekly price changes are not correlated with rated events.2. The outcomes of these single events didn’t cause predictable changes in Pfizer-PJP spread.Again, low correlation observed between the event ratings and the spread we picked. We did the same type of analysis using BMS and got similar results. There are two possible explanations for this result:1. Our interpretations, a.k.a. ratings, of the events are not accurate.2. These events, among all factors that affect Pfizer’s price or spread with industry ETF, are not keydeterminants.  Given that Pfizer and BMS are both big and diversified, their stock price andspread with its industry are even less correlated with single events.The second explanation is more reasonable, and not surprising. Implications:The event-based trading strategy should be used with great caution. In most cases, it might not proveuseful. It might be more useful if the companies being traded are relatively smaller and less diversified;hence the price would be more reactive to single events.  It seems better to take bets on sectors thansingle company events. 
Going forward 
 We are in the process of setting up our own investment process, which include investment ideageneration, forecasting model, portfolio management, trade execution and risk management.  Due to the

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->