Skip to main content
This page provides an overview of ETL for SBM Delta, including the following breakdowns:
  • Table showing you the fields included in each “SBM” row of a Delta Sensitivity CSV Input Data file, indicating which stores these fields are copied to during the ETL process.
  • Key fields for vector creation and the fields that have the potential to be populated with vectors, as opposed to always containing scalar values.

Vectorization

The following table provides information about the vectors employed within the CSV Input files for each risk class:

Un-Vectorization

Vectors within the input are split into several scalar lines by the RiskClassTuplePublisher. For each SensitivityDate in the vectorized input, the corresponding index of DeltaSensitivities is used to create scalar tuples under the scalar risk factor. The scalar risk factor is the concatenation of the input RiskFactor and the SensitivityDate, using a space as a delimiter. If SensitivityDates is not provided, a default of “0Y” is used.

Normalization

Delta-relevant stores

The stores that are relevant for Delta are:  

Mapping of SBM Delta CSV file fields onto the stores that they populate

Column Calculators and Tuple Publishers

RiskFactorColumnCalculator

If Risk Factor is not provided, RiskFactorColumnCalculator will create one based on risk class the table below explains how Risk Factors are derived.
If sbm.risk-factor.always-append-tenor is set to true, then tenor will also be added to Risk Factor.

The Tuple Publisher and Publisher classes

The function of the TuplePublisher and its associated Publisher classes is to separate data in the incoming file row according to its relevance to particular stores and apply ETL logic to the incoming rows: