Curve Configuration

Top ↑

To have a pricing environment ready to perform valuations in Xplain, you will need to have a curve configuration.

A curve configuration holds the mapping that links a curve group (which will need to be defined first) to preferred data providers (e.g. primary and secondary) on an instrument type basis.

On this page, we will discuss how to:

  • create and define a curve configuration, by selecting a curve group and specifying the mapping to market data providers (primary and secondary, if any) on an instrument type basis
  • add provider mapping exceptions (if any)

Curve Configuration Example

You can use the predefined ‘XPLAIN Default’ or ‘LONDON’ curve configurations, or define your own independently. This page will guide you through the process using an example: defining a ‘NEW CURVE CONFIGURATION’ that replicates ‘LONDON’, which will be used with our ‘NEW CURVE GROUPexample.

Permissible values for curve configuration definitions can be found on the Curve Configuration Permissible Values page.

Curve Configuration Definition

1. Creating a Curve Configuration

Under Curves/Curve Configurations, you can create a curve configuration either manually or by importing the definition data.

Creating a Curve Configuration
Curves/Curve Configurations
Alt for image

Case 1: Manually Creating a Curve Configuration
To manually create a curve configuration, click on Add New (or edit an existing one by double-clicking on the line item). You can then configure the mapping to your chosen market data provider(s) on a financial instrument basis.

Case 1: After clicking on Add New,
setting Name = 'NEW CURVE CONFIGURATION' and Curve Group = 'NEW CURVE GROUP', and
mapping IborFixingDeposit to 'TRADS' as Primary Provider and 'SD' as Secondary Provider
Alt for image

Click on Save to save the changes. In our example, we will not save the curve configuration as we will be using the import functionality instead.

Case 2: Importing a Curve Configuration
To import a curve configuration (or a list of curve configurations), click on and select the relevant curve configuration definition .CSV import file.

You can download the import file template here .

Case 2: After importing the relevant curve configuration list definition import file - Versioning options
Alt for image
Case 2: After clicking on Import
Alt for image

At the curve configuration level (after double-clicking on the line item at the curve configuration list level), you can view the import results after clicking on Edit.

Case 2: After double-clicking on NEW CURVE CONFIGURATION
Alt for image
Case 2: After clicking on Edit
Alt for image
Field Name Description Permissible Values
Name The name of the curve configuration Free text
Curve Group The underlying curve group Any existing curve group
Instrument Type The instrument type  See Instrument Types
Primary Provider The default primary provider for market data for a given Instrument Type (optional) Any existing market data provider
Secondary Provider The default secondary provider for market data for a given Instrument Type (optional) See Data Providers

2. Adding a Provider Mapping Exception

By adding provider mapping exceptions, the default mapping between instrument types and preferred providers can be overridden on an instrument type basis.

Under Curves/Curve Configurations, at the curve configuration level (or also globally at the curve configuration list level when importing), once in Edit mode, you can add provider mapping exceptions either manually or by importing the definition data.

Adding a provider mapping exception
Curves/Curve Configurations/NEW CURVE CONFIGURATION
Alt for image
Adding a provider mapping exception
After clicking on Edit
Alt for image

Case 1: Manually Creating Mapping Exceptions
To manually add a provider mapping exception, click on Add Exception (or edit by double-clicking on the exception number) and set the provider mapping exceptions on a curve basis per instrument type.

Case 1: After clicking on Add Exception
and mapping FixedOvernightSwap to 'TULLETT' as Primary Provider for USD SOFR
Alt for image

Click on Save to save the changes. In our example, we will not save the mapping exception as we will be using the import functionality instead.

Case 2: Importing Mapping Exceptions
To import a mapping exception (or a list of mapping exceptions), click on and select the relevant mapping exception definition .CSV import file.

You can download the import file template here .

Case 2: After importing the relevant configuration override file - Versioning options
Alt for image
Case 2: After clicking on Import
Alt for image
Field Name Description Permissible Values
Curve Name A list of FX rates, curves / volatility surfaces or credit curves, which will be mapped to different providers for a given Instrument Type See list of permissible FX rates
See list of permissible curve names
See list of permissible credit sectors
Primary Provider The exception Primary Provider for market data for a given Curve Name Any existing market data provider.
Secondary Provider The exception Secondary Provider for market data (optional) for a given Curve Name See Data Providers

The curve calibration applied at the start of a valuation process to derive cashflow discounting curves and index projection curves, can also be performed on a standalone basis at the curve configuration level.


Introduction to Xplain
Curves
Portfolios
Data
Valuations
Data Cleansing
Preferences
Admin
Importing and Versioning
XVA Module
TRS Module