|
Richard, My apologies, I have been called into
another meeting and will not be able to attend today. Best regards…Tom Thomas L. Brown Jr. | Senior
Manager Standards & Market
Practice Cell: 617 283 5200 From:
owner-colwg@xxxxxxxx [mailto:owner-colwg@xxxxxxxx] On Behalf Of richard.barton@xxxxxxxxxxxxxxxx Please
find the minutes from the April 7 meeting. Please let me know if
any points missed. Participants 1. Anil Panchal (Globeop) 2. Charles Miller (JPMorgan) 3. Harry McAllister (BNP Paribas) 4. Irina Yermakova (ISDA) 5. Jesse Nolan (UBS) 6. John Straley (DTCC) 7. Kaizad Bhathena (Globeop) 8. Nicole Jolliffe (Swift) 9. Richard Barton (Algorithmics) 10. Sammy Lee (Globeop) 11. Simone Milani-Foglia (LCH Clearnet) 12. Vivian Wu (Goldman Sachs) Apologies 1.
Lyteck Lynhiavu (SWIFT) 2. Marc Gratacos (SWIFT) Notes Logistics à
Irina presented the draft roadmap for FpML 5.1 à
This release is scheduled for Dec 2010 and the intention is
to include Collateral Messaging into this standard à
The first working draft of FpML is due in May, second draft
July, Last Call Aug. Therefore there is a lot of work to do to be able to
meet these timelines MC1 à
We went back to MC1 and using the SWIFT Margin Call Request
example started to compare this to the original Messaging Working Group
requirements using the mapping definition provided à
During the meeting we discussed the up to and
including the totalUpfrontMargin. à
The following changes were recommended and
comments made by the group ·
TotalMarkToMarket split to ExposedAmountPartyA,
ExposedAmountPartyB and Exposure Convention. The split provides a
differentiation as to who the exposed party was and complies with FpML approach
to avoid ambiguity and avoid use of +/- signage. Exposure Convention is
to support Gross treatment of Mark to Market. The group saw this as a
nice to have feature and there was a question as to whether we should or should
not support standard agreements terms. This generated a question as to
what was deemed standard. It was suggested that the standard should
be able to support a wide range of margin call types but that the more standard
representations should be simple to implement and use so as not to impede
takeup. ·
Remove IndependentAmountConvention ·
Change InitialMargin to PortfolioMargin. This was
to differentiate Independent Amount from Portfolio Level Margin requirement
like VaR. This recommendation is to simplify and dispute resolution.
·
Remove InitialMarginConvention Action Items à
Group to send examples of margin call notices
that could be used to evaluate the suggested message formats à
Group to review the remainder of the suggested
setup and provide input for next meeting Next Meeting à
The goal is to continue through the MC1
message so that we can then tackle the rest of the margin call messages à
Wednesday 14th April 10am ET/3pm
BST Attachments None The information contained in either this
email and, if applicable, the attachment, are confidential and are intended
only for the recipient. The contents of either the email or the attachment may
not be disclosed or used by anyone other than the addressee. If you are not the
intended recipient(s), any use, disclosure, copying, or distribution is
prohibited and may be unlawful. If you have received this communication in
error, please notify us by e-mail at isda@xxxxxxxx
<mailto:isda@xxxxxxxx> then delete the
e-mail and all attachments and any copies thereof. This communication is part
of an ISDA process and is not intended for unauthorized use or distribution. This email and any files transmitted with it are
confidential and proprietary to Algorithmics Incorporated and its affiliates
("Algorithmics"). If received in error, use is prohibited. Please
destroy, and notify sender. Sender does not waive confidentiality or privilege.
Internet communications cannot be guaranteed to be timely, secure, error or
virus-free. Algorithmics does not accept liability for any errors or omissions.
Any commitment intended to bind Algorithmics must be reduced to writing and
signed by an authorized signatory. This email and any files transmitted with it are
confidential and proprietary to Algorithmics Incorporated and its affiliates
("Algorithmics"). If received in error, use is prohibited. Please
destroy, and notify sender. Sender does not waive confidentiality or privilege.
Internet communications cannot be guaranteed to be timely, secure, error or
virus-free. Algorithmics does not accept liability for any errors or omissions.
Any commitment intended to bind Algorithmics must be reduced to writing and
signed by an authorized signatory. |