Hi Amy. Since you've taken over the responsibility for verbally confirming trades booked to John Arnold, Larry May, Mike Maggie, Dutch, and Andy Zipper, I just wanted to clarify that part of this responsibility includes clearing the trades in Deal Capture/Structure. When you verbally confirm a deal, you have to click on Counterparty and Verify the deal, noting with whom you verballed. If you don't do this, the confirms group has no way of knowing whether or not you've verbally confirmed the deal. Also, in keeping with our global standards for sending out confirmations, verballing should be done on Trade Day - although we give you until noon on T+1 before sending out your deals. At that point, any trades that are not verbally confirmed will be generated and sent. (This does not preclude the need for you to follow up with deals not yet verballed). The exception to this is, of course, if you have identified an economic discrepancy and "Actioned" the deal as such in TAGG - in this case we will wait until the Action has been cleared in TAGG. Me or someone in my group can come over an show you the process in TAGG if you're unfamiliar with it. (or Derek Bailey can show you too) Give me a call if you have any questions or if this deviates from your understanding of the process. Thanks, Diane 3.0443 PS - Also, can you or Errol let me know who in Risk is your backup for this function, as well as the brokered deals you check out? Thanks.
Q: What is a potential subject line for this email?
answer: Verbal confirmation for direct trades
This is where we are today on the VNG releases to ENA. All effective dates are 1/1/2001 - 12/31/2003 unless stated differently. MDQ/MSQ (Storage) Pipeline VNG k# ENA k# MDQ Comment CNG 100007 523666 58352 FT CNG 100104 523664 15225 FT CNG 200088 523667 10000 FT - to be used with Cove Point. Released 1/1/2001 - 2/28/200. CNG 700005 571492 40148 FTGSS. Released 1/1/2001 - 3/31/2001. CNG 300008 530912 53648 / 2791000 GSS CNG 300107 530913 15225 / 761250 GSS CGLF 38070 70198 51479 FTS1 CGAS - we may not release any VNG CGAS capacity to ENA. According to CGAS, we may loose some of our flexibility with the contract. Scott is waiting to hear from CGAS. At this point, we will not release the capacity effective for the 1st. Tenn - I do not have the new contract numbers yet. Per Tenn - Scott will send a letter to Tenn requesting that the VNG discounts be transferred to the new ENA contracts. Trco - Trco has a capacity release "glitch" in their EBB and needs to "temporarily flip a switch" while I do the capacity releases. Since I know Trco well, I've decided to wait until after the 1st to do the releases in case their are EDI issues with the "switch flipping". AND we would not know about any problems until the 31st. Also, VNG has 35,930 dth of telescoped Trco capacity. Williams has 15,930 dth of the VNG capacity because of the FS service. I will release 20,000 dth to ENA. This will eliminate the overlapping problems we have with Williams.
Q: What is a potential subject line for this email?
answer: VNG Capacity Release to ENA
LNG IV 25 and 26 February 2002, The Hatton, London Dear Mr K.L. Lay, I would like to apologise for an error in the last email you received today for the LNG IV SMi conference, taking place in London in February. The conference dates were announced for 18-19 Feb, when it should have read 25-26 Feb. If you have any queries regarding this, please contact me. Regards
Q: What is a potential subject line for this email?
answer: Apology - (LNG IV - SMi's 4th Annual Event)
Larry: According to Steve Kessler (the DB lawyer in New York who is negotiating the ENA ISDA Master), London e-commerce issues are normally handled ty the London lawyer (Conrad Libischer at 44-20-754-52705). If NY trader is also involved, then DB must decide on one lawyer to handle password application, etc. The ENA ISDA Master must first be approved by Frankfurt. I don't know how long this takes. You may want to let the DB trader start the EOL process. Thanks. Sara
Q: What is a potential subject line for this email?
answer:
Deutsche Bank ("DB")