LogoLogo
  • Ellipse Overview
  • Phases of Ellipse
  • Background
    • Challenges of Regulatory Reporting
    • Possible Solutions
    • Digital Reporting and Granular Data
    • Understanding Data Needs of Stakeholders
  • Ellipse Phase 1: Proof of Concept
    • Two Jurisdictions, One Common Data Model
    • Cross-Border Data Model using Retail Mortgage Loans
    • Data Components for Retail Mortgages
    • Data Attributes
    • Data Definitions
    • Using the Common Domain Model (CDM)
    • Normalising Common Components
    • CDM Mortgage JSON
    • Programmable Reporting Logic and Machine Executable Reports
    • VIDEO: Demonstration of the Mortgage CDM
    • Our Findings
    • Next Steps
  • Annex
    • Terminology & Acronyms
    • References
  • About
    • Contact the Ellipse Team
  • LEGAL
    • Terms and Conditions of Use
    • Privacy Notice
    • Cookies Notice
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Ellipse Phase 1: Proof of Concept

Programmable Reporting Logic and Machine Executable Reports

PreviousCDM Mortgage JSONNextVIDEO: Demonstration of the Mortgage CDM

Last updated 3 years ago

Was this helpful?

Using the CDM, executable code automatically generated from the model definitions enabled us to simulate the re-creation of the retail mortgage reports for Singapore and the UK referencing the same model.

We took dummy mortgage transactions with the following parameters:

  • New / first retail mortgage loans

  • Owner-occupied

  • One main borrower

  • A 25-year loan, fixed rate for first 5 years

  • Reversion to the firm's standard variable mortgage rate after 5 years

Taking these data feeds and generating the functional logic code based on each jurisdictional requirement that referenced the Ellipse mortgage model, we were able to execute the regulatory “reports” that we derived the attributes from, namely PSD001 and MAS 645.

Links to the technical documentation associated with the CDM can be found in the Annex under .

References [3]