Replacing Cube Measures

This page provides a description of how some measures can be replaced to modify the calculation logic.

The measures at the beginning of the calculation chain are now defined using Spring beans. These definitions are designed to be overridden.

For example, this can be used to calculate the SES capital requirement according to the EBA’s RTS on the capitalisation of non-modellable risk factors . This could be done with the following steps:

  1. Customize the input files, datastore, and IMA cube schema to add the additional fields required by these calculations.
  2. Replace the “ES (SES)” measure with a measure that applies the EBA’s formulas using the additional fields.
    The Solution will continue with the IMA ES calculations using this new custom measure.

To replace the “ES (SES)” measure, note that the default implementation is defined in IMAMeasureBeans with the following method signature and annotations:

@Qualifier(NMRF_CAPITAL_REQUIREMENT)
@CoreIMAMeasure
public CopperMeasure nmrfCapitalRequirement(){
	...
}

This measure can be replaced in any Spring configuration class by adding a bean with a different name, using the @IMAMeasure annotation with the same qualifier. If the class you are using is new, be sure to include it in FRTBConfig imports. For example,

@Qualifier(NMRF_CAPITAL_REQUIREMENT)
@IMAMeasure
public CopperMeasure nmrfCapitalRequirementEBA(){
	...
}

note

The diference between the @CoreIMAMeasure and @IMAMeasure annotations is that the latter includes @Primary.

The CopperMeasure objects returned by these methods should not be published to the copper context by these methods.

This new measure definition can include custom logic and make use of custom measures and levels in the cube. The Solution’s IMA ES calculations will use the measure defined by this bean as the underlying measure.

Suggested further reading

Adding New Cube Hierarchies

Adding and Loading New Columns to an Existing File