This section describes how requirements in BCBS 457 are implemented in
Atoti FRTB (Internal Models Approach).
For further details, see the Internal Models Approach.
The formulae and definitions in the BCBS document are not repeated here
– instead, references are provided to the relevant paragraphs, as
appropriate.
Calculation steps
The aggregated internal models-based capital charges for IMA desks in
green or amber PLA zones is given as: [MAR33]
IMAGA=CA+DRC
where
CA=max{IMCCt−1+SESt−1; mc⋅IMCCavg+SESavg}
Expected Shortfall (ES)
BCBS-457 ReferenceThis section refers to [MAR33]
The scaling is applied as defined in
The liquidity horizon tables in [MAR33] and are held in datastores.
The risk capital adjustment defined in
Atoti FRTB can calculate Expected Shortfall (ES). The
Solution requires P&L vectors as inputs that are keyed by the
following attributes:
- AsOfDate
- TradeId
- Dataset (ESrs, ESfc, ESrc)
- Risk Class
- Liquidity Horizon
- Currency
For information, see the input file format for Expected Shortfall PL Trade.
Atoti FRTB allows the ES percentile to be expressed as a
context value with a default setting of 97.5
Atoti FRTB contains measures for the calculation of the
following. The calculation chain exposes the intermediate measures for:
- Raw input data on a drill through panel and / or pivot view
- Conversion of input P&L vectors to a reference currency (if the
source systems provide native currency P&L values)
- Calculation of ES (liquidity adjusted, capital constrained and
capital unconstrained)
- Squared Liquidity Horizon (LH) factor and
- IMCC
Atoti FRTB calculates the three Expected Shortfall values for
ESrs, ESfc and ESrc separately and also
applies the risk capital adjustment.
Atoti FRTB assumes that data for ESrs has been
supplied as an input. For information on how Atoti FRTB can
help with the assessment of the ES period of stress, see Evaluating the ES Period of Maximum Stress.
Internally Modelled Capital Charge (IMCC)
BCBS-457 ReferenceThis section refers to and .
The rho factor in the IMCC calculation is parameterized which allows the
user to configure the factor at query time.
Part of the IMCC calculation for the aggregated charge requires the
weighted average charge per desk over the last 60 days. Atoti FRTB does not calculate this value. It is required as desk-level input data to the Solution.
Stressed Capital Add-On (SES)
BCBS-457 ReferenceThis section refers to .The aggregation of the capitalized Non-Modellable Risk Factors (NMRFs)
is calculated according to this paragraph.
In the IMARiskFactors store, Atoti FRTB uses the
Non-Modellable Risk Factors (NMRFs) and Idiosyncratic fields to
distinguish between three types of risk factors:
- Modellable
- Non-modellable, but not idiosyncratic
- Non-modellable idiosyncratic credit spread risk factors that have
been demonstrated to be appropriate to aggregate with zero
correlation
Default risk charge for IMA (DRC)
BCBS-457 ReferenceThis section refers to .
Atoti FRTB presents a VaR-based approach to DRC for IMA which
is calculated from P&L vectors at trade level. The result is required
at 99.9% which means that the input vectors are typically of size
100,000 or more.
The input vector at the trade level is very sparse (meaning that most of
the million elements are zero). This is because any one obligor is
insensitive to most of the scenarios. Atoti FRTB compresses
the sparse vectors and stores them in off-heap memory so that the trade
level vectors use the minimum possible memory.
Atoti FRTB provides a context value that enables the user to
look at the IMA DRC under different confidence levels. By default, Atoti FRTB computes the IMA DRC at 99.9% but a context value is
provided that enables the user to work with other levels.
Evaluating the ES Period of Maximum Stress
BCBS-457 ReferenceThis section refers to .
Atoti FRTB does not provide the scheduling tasks required to
load the data for this calculation. The vector corresponding to the
stressed period can be written out to a CSV file by Atoti FRTB.
P&L Attribution Tests and Backtesting
BCBS-457 ReferenceThis section is concerned with [MAR32].
There are two cubes:
- The PL Summary Cube for the desk and firm-wide monitoring.
- The PL
Cube for trade level
analytics, including aggregating VaR P&L vectors to the desk level
and calculating the VaR values.
Supported Use Cases
The P&L Attribution Tests and Backtesting have been designed to enable
the following use cases.
- Monitoring historical VaR and P&L values at the desk and firm-wide
levels, as required by regulation.
- Calculating desk and firm-wide VaR values from trade level VaR P&L
vectors.
- Customizing trade level inputs and analytics to support analyzing
recent exceptions/outliers.
PL Summary Cube
The PL Summary Cube collects aggregated data with a long history (at
least the 1 year required by the regulations) at the desk and firm-wide
levels. Including:
- Daily P&L values (actual, hypothetical, and risk-theoretical).
- Daily VaR values at the 97.5% and 99% confidence level.
The cube includes the analytics required for P&L Attribution Tests and
Backtesting. Including:
- The mean of the difference between the risk-theoretical and
hypothetical P&L (unexplained P&L) divided by the standard
deviation of the hypothetical P&L.
- The variance of the unexplained P&L divided by the variance of the
hypothetical P&L.
- A count of the number of exceptions when comparing the Actual P&L
and Hypothetical P&L against the VaR at the 97.5% and 99%
confidence levels.
For more information, see Cubes.
The input data to the summary cube requires the following data fields in
the input data files:
- AsOfDate
- Desk name
- Currency
- Actual PL
- Hypothetical PL
- Theoretical PL
- VaR 99
- VaR 97.5
For information, see the input file format for PL Summary.
PL Cube
The PL Cube collects recent data at the trade (or position) level,
including the VaR P&L vectors.
- Includes VaR calculations, for calculating the desk and firm-wide
VaR values at the 97.5% and 99% confidence level.
- It is expected that this cube will be customized to support
analyzing exceptions/outliers.
For more information, see Cubes.
IMA Multiplier
BCBS-457 ReferenceThis section references
The IMA Multiplier factors are held in a datastore so that they can be
fetched at query time and can be sensitive to jurisdiction. Atoti FRTB provides a post-processor that can take as input the number
of P&L/VaR exceptions (see P&L Attribution Tests and Backtesting) and return a multiplier factor as a measure.