June 1, 2009. Current Status Technical Details Current Releases Issues Potential Use Cases Position Reporting Portfolio Reconciliation Cash Flow Matching.

Slides:



Advertisements
Similar presentations
ISDA FpML 5.0 Overview Andrew Jacobs (UBS)
Advertisements

FpML REPORTING WORKING GROUP Copyright © 2010 International Swaps and Derivatives Association, Inc. JANUARY 2010 – SLIDE 1 ISDA FpML Update Brian Lynn.
April 12, SLIDE 1 Copyright © 2011 International Swaps and Derivatives Association, Inc. FpML Reporting WG FpML Representation for Public Price.
FpML version 5.0 An introduction FpML version 5.0 An introduction Sept Karel Engelen, ISDA Andrew Jacobs, Handcoded Marc Gratacos, ISDA Brian Lynn,
Messaging Patterns Proposal to change FpML Messaging.
Messaging Patterns Proposal to change FpML Messaging.
Proposals to change FpML Messaging. Correlation Acknowledgements Exception modelling Advice vs. Notification Corrections On behalf of Trade Roles Trade.
Messaging Patterns Proposal to change FpML Messaging.
FpML Versioning An AWG Discusion Document. Namespace URIs & Versions An XML parser locates the schema for a document based on its namespace URI To be.
April SLIDE 1 Copyright © 2011 International Swaps and Derivatives Association, Inc. FpML Reporting WG FpML Representation for Public Price Transparency.
FpML Versioning An AWG Discusion Document. Versioning in FpML To Date Based on major.minor numbering –Major increments to indicate a breaking change –Minor.
Credit Baskets Proposal CD-FpML Working Group John Weir.
February 7, SLIDE 1 Copyright © 2011 International Swaps and Derivatives Association, Inc. FpML Reporting WG FpML Reporting Working Group ® ISDA.
2006 International Swaps and Derivatives Association, Inc Standards Committee Offsite Business Process Working Group Update.
1 Proposals to change FpML Messaging. 2 Correlation Acknowledgements Exception modelling Advice vs. Notification Corrections On behalf of Trade Roles.
FpML REPORTING WORKING GROUP Copyright © 2010 International Swaps and Derivatives Association, Inc. JANUARY 2010 – SLIDE 1 ISDA FpML Update Brian Lynn.
DC8 Registries Breakout. Goals of the session Discuss and clarify : Requirements for registry Framework for policy Relate issues raised to EOR prototype.
Registry breakout group DC-8, National Library of Canada 5 October 2000.
A service of Maryland Health Benefit Exchange MHBE IAC System Update July 17, 2014.
CIS 375—Web App Dev II SOAP.
Vision Document for Project Green Light Accurate, Complete and Efficient Risk Measurement and Reporting 10 September 2001 DRAFT FOR DISCUSSION ONLY.
Global Business Blueprint Summary Presenters: Laurie Dempsey, CBP Lois McCluskey, eCP January 28, 2004.
Customizing Outlook. Forms Window in which you enter and view information in Outlook Outlook Form Designer The environment in which you create and customize.
Chapter 9 THE ACQUISITION CYCLE— PURCHASING AND RECEIVING.
IRS XML Standards & Tax Return Data Strategy For External Discussion June 30, 2010.
©© 2013 SAP AG. All rights reserved. Product Engineering Scenario Overview Creating Product Design Information and Materials in External System Maintaining.
MidQORT Automated middle-office. Principal Functions 1 ̶ Online evaluation and monitoring of positions ̶ Risk-management by customers ̶ Own position risk-management.
GJXDM Information Exchange Package Methodology Naming & Design Rules (MNDR) John Ruegg County of Los Angeles Information Systems Advisory Body GJXDM User.
15 November 2005Linking Outside the Box1 Cross referencing between XML documents Bob Stayton Sagehill Enterprises
Project “European CDDA and INSPIRE”: scope, transformation workflow and mapping rules INSPIRE Conference 2014 Workshop: Implementing Existing European.
Portfolio Swap Standardisation Andrew Parry
 Copyright 2001 Perot Systems Europe. All rights reserved Architecture Model Introduction Tim Taylor.
Session 21-2 Session 11 Common Origination and Disbursement (COD) & Commonline: Dispel the Myths.
Course # PEMS Version 2.0 Upgrades. Unit 8 PEMS Version 2.0 Upgrades Several improvements to PEMS application  Improvements based on: - Change.
Requirements Traceability: Planning, Tracking and Managing Requirements Presenter: Paula R. Maychruk, BV/TEd., CAPM, CBAP.
Conceptual Framework for Financial Accounting
AIA RFID Data Exchange Guideline Status AIA / Electronics Enterprise Integration Committee May 10, 2005.
Programming Logic and Design Using Methods. 2 Objectives Review how to use a simple method with local variables and constants Create a method that requires.
Chapter 10 THE ACQUISITION CYCLE— PURCHASE INVOICES AND PAYMENTS.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
Data Strategy  Status Update  SSIM  RID  Technology Strategies.
MISMO Trimester Meeting June 4 - 7, 2012 Santa Ana, CA Extensions in 3.2 Greg Alvord RealEC June 4, 2012.
CASRAI Consortia Advancing Standards in Research Administration Information David Baker, Executive Director.
Electronic Submission of Medical Documentation (esMD)
1 Exchange Network Shared Schema Components. 2 Shared Schema Components Topics: Introduction to Shared Schema Components Purpose/value of using Shared.
1 ILE Project Integrated Logistics Environment Kickoff Meeting NPDI Project & SCIM Summary & Status Presented by: Rick Lobsitz (NGTS)
1 Agenda What is XML? XML Jargon Why XML? Why Now? Advantages Disadvantages of XML What is FIX? What is FIXML? What other standards are available? How.
WISE Working Group D September 2009, Brussels Jon Maidens.
Technical Steering Committee La Jolla, January 2003 Paul Kiel, HR-XML.
AutoDESA Presentation Project Documentation October 2005.
ISA 95 Working Group Process Centric Exchanges Gavan W Hood July 23, 2015 GWH 2.1.
IBM Global Services © 2005 IBM Corporation SAP Legacy System Migration Workbench| March-2005 ALE (Application Link Enabling)
Team Skill 3: Defining the System The Vision Document (16) 1.
Techniques for List Creation (2) Data formatting and control level processing Basics for Interactive Lists Detail lists The Program Interface Interactive.
PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.
Electronic Exchange of Social Security Information (EESSI)
Financial Statement Presentation EFRAG – ASB outreach 1 December 2010.
Sauder Unlimited presents… Corporate Development 101 Corey Wong President of BizTech ( )
M-PEDD Technical Working Group
IPDA Registry Definitions Project Dan Crichton Pedro Osuna Alain Sarkissian.
January 31, SLIDE 1 Copyright © 2011 International Swaps and Derivatives Association, Inc. FpML Reporting WG FpML Reporting Working Group ® ISDA.
Experiences and Status
Product Engineering Scenario Overview
Project Nexus Workgroup
FpML version 5.0 An introduction
FpML Version 5, Working Draft 4 ISDA FpML Update
Project Nexus Workgroup
Feasibility Report.
Retail Energy Code - Data Access Schedule
Presentation transcript:

June 1, 2009

Current Status Technical Details Current Releases Issues Potential Use Cases Position Reporting Portfolio Reconciliation Cash Flow Matching Others? Next Steps Business Justification Implementations

FpML maintains a single master schema Master schema contains annotations with view-specific details, make this optional in view X put this only in view Y FpML publishes separate view- specific schemas, one per view Each view is generated from the master prior to publication Each view has documentation and examples Each view-specific schema will have its own namespace, e.g., 5/pretrade End users will use a view- specific schema, not the master

FpML 5.0 Working Draft 2 published 3 views Pretrade Very loose product representation Things like parties, notionals, and dates are optional Everything in confirmation view is available (maybe optional) Reporting Intermediate representation Key economics are required (notionals, key dates, parties) but details are not (e.g. date adjustments) Everything in confirmation view is available (maybe optional) Confirmation As current 4.x product representation Prototype to show technical capabilities Pretrade and Reporting view not validated by business experts

FpML 5.0 Working Draft 3 is going to publish 2 views Reporting As current 4.x product representation Contains business processes such as position reporting, portfolio reconciliation, cash flow matching, etc. Confirmation As current 4.x product representation Prototype to show technical capabilities Reporting view not validated by business experts

Pretrade and Reporting views havent been validated by business experts Validation rules have been defined for the Confirmation view only Some of them applicable to other views too, but others not Documentation needs to be improved Lots of duplicated information Single documentation with view variations within it?

Potential Use Cases Position Reporting Portfolio Reconciliation Cash Flow Matching Others?

The Data Standards Working Group (DSWG), a group of U.S. hedge funds, developed a message type based on FpML to send daily position reports Some FpML required fields were using default values FpML incorporated the message type in version 4.2 but without defaults The FpML schema was not relaxed Should the reporting view use the DSWG analysis as input to made some of the required elements optional?

FpML has defined a set of message exchanges for portfolio reconciliation They reuse the Position definition based on the DSWG work Changes in the product definition for reporting will impact these messages

FpML has defined a set of message exchanges for cash flow matching A trade identifier and an optional set of trade identifying items (trade date, effective date, termination date,…) must be provided to reference the trade Would a more relaxed product definition have some use with these messages?

Collateral Management

Business Justification Whats the business case for the Reporting View (if any)? Scope Purpose Users Timing and Development Implementations Future implementations that would benefit from using the Reporting View