Replies: 2 comments
-
It would be great to embed the CDM Object Builder into FDC3, build a CDM collateral representation and show the difference in a human readable way. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Closing discussion in preparation for this years hackathon. Feel free to reopen and update if its still relevant. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Implement features of CDM Collateral model to meet common Collateral Working Group use cases
From @iansloyan (ISDA)
Business Problem
There are 2 suggested use cases for a hacker to download the CDM model and focus on the collateral model specifically and use it to demonstrate the following use cases - additional credit could be given to using FDC3 and/or Morphir to exchange and/or run the basic tests on the data objects.
Using the CDM collateral representation already built, build functionality to test collateral eligibility against multiple jurisdictions’ minimum collateral requirements and specific eligible collateral schedules.
Essentially this is testing different criteria sets built from the EligibleCollateralSchedule root type against each other - e.g., the regulation* says you must at a minimum provide collateral of bonds of 5 years or more from OECD countries vs counterparty says you can only post bonds of from France or Germany which are 7 years and rated AA+ vs internal inventory rule which says can post any bonds you like as long as 5 years or more maturity. The intersection of these criteria sets becomes the effective criteria you need to apply when picking a bond to post to counterparty.
*https://www.isda.org/a/EqxgE/Eligible-Collateral-Comparison-010523.pdf
Using the CDM collateral representation already built, build functionality to compare new and previous eligible collateral schedules and identify changes to be ingested into a collateral management system. Develop a process to run this look, find, change function daily.
This is a different dimension to the above where testing against changing criteria on a daily or regular basis and has many use cases in collateral management.
Expected outcome
JSON files are provided to represent specific criteria for types of bonds that are eligible as collateral under certain regulatory margin rules.
EligibleCollateralCriteria_1_28-04-2023 2.zip
The technical solutions built should be capable of building basic tests like these and be capable of answering some basic questions like these:
Use case 1.
Using the following files for the first use case:
EU 1-5 2%
EU 1-5 15%
US 1-5 2%
US 1-5 4% Corp
US 1-5 4%
US Cash
These objects together specify the collateral eligible to be posted or received in this scenario.
Use case 2.
Compare schedule 1 to schedule 2 and show the variances
The criteria objects in the files need to be put/linked together to create the 2 schedules for you to use in use case 2.
Useful apps, systems, projects, technologies, libraries and datasets
EligibleCollateralCriteria_1_28-04-2023 2.zip
(same as attached zip above)
Beta Was this translation helpful? Give feedback.
All reactions