Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed change to the CDM - Completion Life Cycle Events Implementations #3170

Open
dschwartznyc opened this issue Oct 8, 2024 · 0 comments

Comments

@dschwartznyc
Copy link
Contributor

dschwartznyc commented Oct 8, 2024

CDM's support for life cycle events has limited documentation and seems to be incomplete. These gaps are not aligned with the goals for standardization and are limiting the technology's potential.

Background

Two notable examples of gaps in the OTC derivatives workflow support are the Allocation and Affirmation events. In both cases the workflow implementation is incomplete.

  • For example, Qualify_Allocation is the function provided to confirm that an allocation is appropriately formed but this function does not confirm that the sum of the notionals of the allocated trades is equal to the notional of the unallocated trade.
  • Similarly, while the model includes a data model type to encapsulate an affirmation, it is unclear what function should be used to execute the event.
    If an existing function such as Qualify_ContractFormation is part of the workflow, then shouldn't there be an EventIntentEnum corresponding to affirmation or confirmation?

Proposal

In response, there should be a prioritized review of the events CDM intends to support leading to complete workflow implementation where there are gaps and more comprehensive documentation.

For OTC derivatives, the suggested primary working group is the CDM Derivatives Products and Business Events Working Group.

Gaps in the Collateral Management, if any, should be covered by the CDM Collateral Working Group
Securities Lending and Repo/Reverse may best be supported in the respective Trade Association Working Groups.
Unclear where analysis of the gaps in the documentation workflow should reside.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant