This topic includes release notes about enhancements and updates to CME Optimizer Software versions.  

Optimizer Version 19.1 Release Notes

This section details Optimizer version 19.1, an optional patch release. Users testing the Rule-based Offset Engine (RBOE) to facilitate the FICC Cross-margin program (see the RBOE user guide) should review changes below and may choose to take this build.

Users who do not use the RBOE functionality in the Optimizer program are not impacted by this build.

Version Number: 19.1

Release Date: January 17, 2024

Mandatory Build: N

Release window:

• This version can be installed in production anytime after January 22, 2024.

1.1.       Technical Changes

There are no changes to the minimum system requirements. 

1.2.       Enhancements

Additional logging has been added for account validation of FICC cross-margin accounts. The logging does not impact program processing or any other output file.

1.3. Fixes

This patch release fixes an issue which prevented non-front month contracts (normally referred to as "back months") from being considered for allocation into the FICC cross margin account when one or more of the following conditions were present. These conditions are only presented when the user has engaged the "UseBackMonthContracts": true configuration.

• Front month contract for a given instrument is not present.
• Front month contract for a given instrument is excluded (for instance during treasury roll).
• Front month contract for a given instrument nets to zero.

1.4. Configurations

There are no changes to configurations in scope in this build.

1.5.       Testing Considerations

Please perform testing of the Rules-based Offset Engine, consistent with earlier builds.

1.6.       Out of Scope

There are no changes to the IRS portfolio margin logic in this build. Users not testing the RBOE FICC Cross margin logic may choose not to take this build.

Optimizer Version 19.0 Release Notes

This release note details Optimizer version 19 enhancements scheduled for release on November 17, 2023. This build, version 19, is mandatory and must be integrated by January 22, 2024 to prevent subsequent Optimizer failures. Optimizer version 19 users can choose to integrate any time during the release window described below. Release notes are in draft form for discussion purposes only.

This build supports several enhancements at a high level:

• Supports new PLN and MXN currency OTC cleared interest rate swap products.
• Supports bug fixes to Treasury Roles-based Offset Engine (RBOE) feature supporting the CME/FICC Cross-margin program.
• Several input files which supported cleared Swaptions are being deprecated and users should remove them from their input set and configuration file at the earliest convenience. 

Version Number: 19.0

Release Date: November 20, 2023

Mandatory Build: Y

Release window:

• Initial Cutover Cycle Date: December 11, 2023
  • Note this is the earliest date from which users can begin running Optimizer version 19 in production.
• Final Cutover Date: January 22, 2024

1.1.       Technical Changes

There are no changes to the minimum system requirements. 

1.2.       Enhancements

1.2.1.     PLN and MXN

CME will support MXN Overnight TIIE Funding Rate (F-TIIE) and PLN Warsaw Interest Rate Overnight (WIRON) swap clearing in the New Release environment on Wednesday, November 01, 2023 - please see the advisory here for more details. The Production support date is early 2024, please see CME's production advisories for more details. The New

Optimizer version 19 supports the curve data necessary for trading these new contracts. Users who do not trade these contracts are also required to support Optimizer version 19.

1.3. Fixes

1.3.1.     Treasury Rules-based Offset Engine (CME/FICC Cross Margin Program) Logic

This build fixes an issue observed in the Treasury Rules-based Offset Engine (RBOE) logic which allowed options positions to be transferred to  the FICC cross margin account if provided by a user in their FICCPositions.csv input file.  Options are not eligible for the FICC XM Program and this release adds additional validation to ensure that transfers can not be generated. It further prevents a scenario that a user of both IRS Portfolio Margining and FICC XM does not have options transfer between IRS PM and FICC if provided in the positions.csv file.

Additionally, this build improves upon the logic to allocate back-month contracts to the FICC cross margin account to ensure Optimizer always chooses the back months in closest to expire order.

The RBOE logic was implemented in Optimizer version 18, is optional and supports the CME and FICC cross margin program going live in early 2024. For more details on the Treasury Rules-based Offset engine, please see the RBOE user guide here.

1.3.2.     Margin Approximation during Optimization

Margin approximation within the optimization process was updated to solve for more accurate margin approximation which is expected to address some scenarios where user portfolios may not be fully optimized.

1.4.       Configuration Changes

1.4.1.     Deprecated Configuration Settings

The following configuration properties are no longer required by version 19 and have been deprecated. Note there is no impact to version 19 if these properties are present within the configuration file, though it is recommended that they be removed. These files will be decommissioned on a future date in 2024, more details are forthcoming. 

1.5.       Testing Considerations

As with all Optimizer test periods, it is recommended to test using a combination of input files:

• New Release (NR) environment version of the Optimizer Market Data Archive (MDA) file
• Production environment version of all other input files.

1.6.       Out of Scope

All other IRS products remain unchanged by this release. 

There are no new futures or options products supported for cross-margining in this release.

Optimizer Version 18.0 Release Notes

This release note details Optimizer version 18 enhancements scheduled for release by September 30, 2022. This build, version 18, is mandatory and must be integrated by December 12, 2022 to prevent subsequent Optimizer failures. Optimizer version 18 users can choose to integrate any time during the release window described below. Release notes are in draft form for discussion purposes only.

This build supports several enhancements at a high level:

• Supports SOFR and Treasury Options in the Portfolio Margin program.
• Supports Eurodollar fallback margining.
• Supports interest rate spread curve methodology changes.
• Supports a new Treasury Rules-based Offset Engine (RBOE) feature.

Version Number: 18.0

Release Date: September 30, 2022

Mandatory Build: Y

Release window:

• Initial Cutover Cycle Date*: October 31, 2022
• Final Cutover Date*: December 12, 2022

*This build allows users to choose to integrate any time from October 31 – December 12, 2022, where the first possible EOD cycle using the new build is Monday, October 31, 2022 and the last possible cycle using the old build is Friday, December 9, 2022.

1.1.       Technical Changes

Version 18 of optimizer contains updates to the minimum system requirements:

• Windows Server 2019 or higher^††
  • Prior versions of Optimizer supported Windows 2016 and higher.
• Quad-core Processor
  • No change from prior.
• 16 GB of available memory (32 GB is recommended) – note users who have 8 GB of memory must upgrade to 16 or higher.
  • Prior versions included support for 8 GB memory, which is no longer supported.
• 15 GB of available storage (~5GB installation / ~10GB daily data files^†).
  • Prior requirement was 2 GB and 4 GB respectively.
• Microsoft .NET 6.0 Runtime x64 (6.0.6 or higher).
  • Prior version was .NET Framework 4.7.2.
• Microsoft Visual C++ 2015-2022 Redistributable (x64) (14.32.31326.0 or higher)
  • Prior requirement was Visual C++ Redistributable 14.10.27024.

^† Daily estimate only. Market/firm data file sizes will vary on a firm-by-firm basis. It is recommended that you allocate up to 1 GB per day for storing data files.

^†† Note that CME Optimizer 18 can run on earlier version of Windows Server (including Windows Server 2012 R2 and Windows Server 2016). However, in accordance with CME guidelines and industry best practices, discontinued, insecure or unsupported operating systems are no longer supported as of EOY 2020, this includes both Windows Server 2012 R2 and 2016.

1.2.       Enhancements

1.2.1.     SOFR and Treasury Options Support

This build of optimizer software incorporates new portfolio margin-eligible contracts SOFR and Treasury Options, pending all relevant CFTC regulatory review periods. The supported product scope include:

• U.S. Treasury Quarterly and Serial Options, Clearing Codes: 17, 21, 25, 26, UBE, TN
• SOFR Quarterly, Serial and Mid-curve Options, Clearing Codes: SR3, S0, S2, S3, S4, S5
• Out of scope contracts are in 1.6 below

With this build, SOFR and Treasury Options contracts specified above are eligible to transfer to or from an OTC portfolio margin account to achieve risk offsets. This build will generate transfers for and consider these contracts during Optimization by default. Users who do not want to support these new contracts will have to turn off support for SOFR and Treasury options explicitly in the configurations file, details below.

Prior versions of Optimizer software recommended users include all interest rate futures and options contracts, including SOFR and Treasury options, in the positions.csv file. Firms who have not included these contracts in the positions.csv input file should add them as soon as possible, regardless of whether they plan to exclude these contracts from Optimization. Firms need not wait until version 18 is live to make these changes to the positions.csv file as these contracts are supported for margining in the current build of Optimizer (v17).

A full list of eligible portfolio margin contracts, including contracts which are ineligible but should be included in the positions.csv file, is available here.

Exclusions

See Configuration Changes below.

Input File Changes

• “cme_optimizer_marketdata_yyyymmdd.zip” file changes

The addition of SOFR and Treasury options is expected to increase the total size of the CME-produced Optimizer input file “cme_optimizer_marketdata_yyyymmdd.zip” by at least 2 times. Within the zip file, CME has designed a more efficient group of smaller inputs to minimize impacts to memory consumption. As a result, users may notice the Optimizer displays a larger set of input files while starting up and start up takes more time than in prior builds. This is viewable in the Optimizer Log output file or while running the Optimizer via command line. This is expected and working as designed.

It is recommended users test transferring from the secure FTP and running Optimizer with the updated zip input file during the test window. Please note the updated system requirements above, specifically the updated memory requirements, are related to this change.

• “Positions.csv” file changes

Users are expected to include SOFR and treasury options contracts supported above in the firm-produced “Positions.csv” input file. There are no changes to the “Positions.csv” file format.

1.2.2.     Eurodollar Options LIBOR fallback margin methodology enhancement

Given the USD LIBOR cessation on June 30, 2023, this enhancement will provide additional capital efficiencies for ED vs SOFR options portfolios for any options with underlying futures expiring after June 30, 2023. There are no Optimizer interface changes associated with this enhancement.

1.2.3.     IRS curve Spread model enhancement

Enhancement to represent the USD curve zero rate risk factor as a spread on top of overlapping Base Curve zero rate risk factor. This enhancement is only implemented for USD curves. There are no Optimizer interface changes associated with this enhancement.

1.2.4.     Treasury Rules-based Offset Engine (RBOE)

Optimizer version 18 supports a new Treasury Rules-based Offset Engine (RBOE) for offsetting CME treasury contracts against related FICC cash positions.

This document serves to provide high level changes to Optimizer software. Users who are interested in running this program must review the RBOE user guide page here.

The first iteration of the rules-based offset engine (RBOE) allows CME treasury futures contracts to offset treasury cash positions in a new sequestered FICC position account. Similar to the existing portfolio margin program, the Optimizer software facilitates the generation of transfers to and from this new FICC position account. 

Input File Changes

Users interested in this feature are expected to provide two new input files to the Optimizer software. The specifications for these files is available in the RBOE user guide.

• csv – expressing positions residing in the FICC position account or account mapping, should no positions exist.
• A new equivalent position report from firm secure FTP /F[firm id]FTP/cme/ftp/[firm id]/Outgoing directory

Firms supply these two new files to Optimizer at runtime.

Users not participating in this new program need not supply new inputs to Optimizer.

Configuration Changes

Note the RBOE feature is turned off by default in the Optimizer’s configuration file. Users interested in participating should update the configuration per the Configuration Changes section of this guide.

Output File Changes

The output file csvTransfersyyyymmdd_X.csv is being enhanced to include a new TransferOrigin of “FICCXM” for transfers that are generated as a result of RBOE optimization. All transfers which are generated through normal netting and exclusion process, even if transferring from the FICC position account, will continue to use the existing TransferOrigin Exclusion and Netting.

All other outputs, aside from the log file which highlights the RBOE process, are the same. Note the margin approximation reports are not expected to include positions in the FICC position account within the margin calculations.

1.3. Fixes

None.

1.4.       Configuration Changes

This build of Optimizer requires users to update the default configuration.json file used during runtime. There are several changes in this build which require attention, notably for clearing firms who have an automated process of generating this file.

1.4.1.     Treasury and SOFR Options in PM Configuration Changes

This section illustrates changes to specific sections of the Optimizer’s configuration.json file to support treasury and SOFR option exclusions. Please see also configuration.json file specifications here.

Option Lifecycle Exclusions

Though excluding options contracts during exercise and assignment events is not operationally required by CME, it is understood that users may prefer to exclude these contracts during E&A processing. As a result, the default configuration in the “TradeEvents” sections has been updated to reflect options exclusions during E&A events for all newly supported contracts (list above). The “EarlyExercise” section has not changed and will continue to be enabled by default, thereby excluding all options contracts in scope during early E&A.

• Example of default “TradeEvents” section with SOFR and Treasury Options last trade day exclusion added. Users can update to meet their use case.

\\ . . . other sections omitted for brevity\\ 
"TradeEvents": {
      "Enabled": true,
      "Events": [
        {
          "Enabled": true,
          "Name": "First Position Date - Treasury Roll",
          "BeginEventType": 17,
          "DaysBefore": 0,
          "EndEventType": 7,
          "DaysAfter": 0,
          "Type": "FUT",
          "Exchange": "CBT",
          "Codes": [ "17", "21", "25", "26", "TN", "UBE" ]
        },
        {
          "Enabled": true,
          "Name": "Last Trade Date - MAC DSF",
          "BeginEventType": 7,
          "DaysBefore": 0,
          "EndEventType": 14,
          "DaysAfter": 0,
          "Type": "FUT",
          "Exchange": "CBT",
          "Codes": [ "F1U", "B1U", "T1U", "N1U" ]
        },
        {
          "Enabled": true,
          "Name": "Last Trade Date - CME Option Expiration",
          "BeginEventType": 7,
          "DaysBefore": 1,
          "EndEventType": 999,
          "DaysAfter": 0,
          "Type": "OOF",
          "Exchange": "CME",
          "Codes": [ "ED", "E0", "E2", "E3", "E4", "E5", "SR3", "S0", "S2", "S3", "S4", "S5" ]
        },
		{
          "Enabled": true,
          "Name": "Last Trade Date - CBT Option Expiration",
          "BeginEventType": 7,
          "DaysBefore": 1,
          "EndEventType": 999,
          "DaysAfter": 0,
          "Type": "OOF",
          "Exchange": "CBT",
          "Codes": [ "17", "21", "25", "26", "TN", "UBE" ]
        }
      ]
    }
  }
}

• Example of “EarlyExercise” default section. No changes to this section, it continues to be enabled by default and will exclude all options, including newly supported contract, undergoing early E&A.

\\...other sections omitted for brevity\\  
    "EarlyExercise": {
      "Enabled": true
    },

Product Exclusion Examples

The addition of Treasury and SOFR options will be turned on by default on December 12, 2022. This is also true by default for Eurodollar options. Users who wish to exclude these contracts from Optimization can using the below product configuration as an example. For a user to successfully exclude these contracts, they must update the configuration.json file to include the below sections. For more details on using product exclusion configurations, please see the Optimizer user guide here or contact CME support for other exclusion combinations.

Note: excluding any portfolio margin-eligible contract from Optimization is not recommended because it can result in lower overall program efficiency. Firms are encouraged to use product exclusions sparingly.

• Example product exclusion for CBT treasury options contracts:

    "Product": {
      "Enabled": true,
      "Exclusions": [        
	  {
          "Type": "OOF",
		  "Exchange": "CBT",
          "Codes": ["17", "21", "25", "26", "UBE", "TN"] 
        }

• Example product exclusion for CME SOFR options contracts:

    "Product": {
      "Enabled": true,
      "Exclusions": [        
	  {
          "Type": "OOF",
		  "Exchange": "CME",
          "Codes": ["SR3", "S0", "S2", "S3", "S4", “S5”] 
        } 

1.4.2.     Fallback Margining Configuration Changes

None.

1.4.3.     Interest Rate Spread Curve Methodology Configuration Changes

None.

1.4.4.     Treasury Rules-based Offset Engine Configuration Changes

Several configurations have been added to support the new RBOE workflows. If enabling any settings described within this section please refer to the RBOE user guide for configuration specifications.

• New “Ficc” configuration section

The new RBOE (sometimes referred to as “Ficc”) workflows are disabled by default and users must update the below configuration to enable. 

"Ficc": {
    "Enabled": true,
    "ExecutionMode": "BeforeIrsOptimization",
    "OptimizeMoveDecision": "LIFO",
	"UseBackMonthContracts": true,
     "FiccPositionsFilename": "FICCPositions_",
    "FiccEquivalentPositionsFilename": "*XMFICCPOSN_*.csv"
  },

• New IncludeBaselineInOptimalState config:

Allows user to define whether the 'baseline' margin case will be used during Optimizer's solution decision. Baseline margin can be impacted by exclusions for FICC processing and may become less meaningful. This config is false by default to capture this edge condition. This new config falls at the top of the exclusions section:

 	"Exclusions": {
	"IncludeBaselineInOptimalState": false,
    "EarlyExercise": {
      "Enabled": true
    }, 

• New “FiccPbAccount” configuration section

Users will also notice a new configuration under the “Exclusions” section “FiccPbAccount”. This configuration allows an RBOE user to exclude specific accounts from the RBOE workflow. It is present but disabled by default and users must update the below to enable:

  "FiccPbAccount": {
      "Enabled": false, 
      "Exclusions": [
        {
          "Enabled": false,
          "Type": "FUT",
          "Accounts": [""]
        }
      ]
    },

1.5.       Testing Considerations

The Samples files, located in the Optimizer at [local dir]\Samples will be updated to include new features. Users are also encouraged to test:

• File download time from CME secure FTP.
• Optimizer run time.
• Adding SOFR and Treasury Options to the positions.csv file.
• SOFR and Treasury Options savings analysis using Optimizer margin reports.
• Exclusions for SOFR and Treasury options (early exercise and standard exercise events).
• End to end workflows, including transfers.
• The Rules-based Offset Engine, if using, is defined in significantly more detail, including testing considerations, at the RBOE User Guide page.

It is recommended to use the following combination of input files to test Optimizer during the test window. Note the CME New release (NR) environment is not a production copy environment and does not require a full back office account setup to process transfers produced by Optimizer.

• The "cme_optimizer_marketdata . . ." file from the new release (NR) test environment.
• A positions.csv file generated in the test environment (unless SOFR and Treasury options are already in your production file, in which case, use production).
• All other input files from the production environment.

1.6.       Out of Scope

Treasury and SOFR options not in 1.2.1 above, including:

• U.S. Treasury weekly options
• SOFR SR1 serial options
• SOFR weekly options

Optimizer Version 17.0 Release Notes

Version: 17.0.0.0

Release Date: September 27, 2021

Mandatory Build: Y

Mandatory Cutover Date: November 15, 2021

Enhancements

• Incorporates new portfolio margin eligible products Eris SOFR-based swap futures, targeted for production go-live soon (advisory forthcoming).
  • List of Eris SOFR-based swap futures Globex/Clearing Codes: YIA, YIB, YIC, YIT, YIW, YIY, YIL, YID, YII, YIO, YIE.
    • See all eligible products here.
  • These products are eligible to transfer to OTC accounts to achieve risk offsets.
  • This build of Optimizer will generate futures transfers in the above products and consider them during Optimization.
  • Users who do not include Eris SOFR-based Swap futures in the positions.csv file today should add these contracts to achieve optimal results.
• Incorporates support for Bloomberg Short-Term Bank Yield Index (BSBY) – based USD interest rate swaps, scheduled for production go-live November 15, 2021.
• Incorporates support for Singapore Overnight Rate Average (SORA) – based SGD interest rate swaps, scheduled for product go-live November 15, 2021.
• Supports limited forwards-compatibility for future Optimizer releases by introducing a multi-version support inside Optimizer's  interpretation of compatible market data sets.
  • This change is internal only and should not impact firm workflows.
• Reduced installation footprint:
  • Installer file (MSI) approx. 75 MB
  • Installation folder (post-installation) approx. 450 MB
  • Note that the sample market data has been significantly reduced and only supports a limited set of contracts. If you require a full market data set to facilitate testing prior to NR launch dates, then please reach out to posttradeservices@cmegroup.com for further information.
    • Date of samples file is August 20, 2021.

Fixes

• Optimizer version 17 adds validation logic for invalid dates in the position.csv input file TradeDate field. Prior Optimizer versions defaulted transfer output to an un-tradable 1/1/0001 date when an improper TradeDate format was supplied. The TradeDate field is now expected to be in date format: yyyymmdd, mm/dd/yyyy, or m/d/yyyy. Optimizer version 17 produces an error at the portfolio level if the TradeDate field is not in these formats. The new expected error is:

  Invalid trade date format detected: '<<invalid format>>'. Expected yyyyMMdd or MM/dd/yyyy or M/d/yyyy

  
  

Configuration Changes

• Due to firm feedback on preferred default trade exclusions, Optimizer version 17 incorporates updates the default configurations in the EventExclusions section of the configuration.json file. Please note these configurations are suggestions only and firms can update exclusion configurations to meet their use cases. To better understand exclusion configurations please refer to the User Guide here.
  • For treasury products:
    • Changes the BeginEventType exclusion attribute to be first position/intent date (enum = 17).
    • This was previously first notice date. Delivery for treasuries can begin as early as First Intent Day, one day before first notice day.
    • Example updated config: 

{

  "Enabled": true,

  "Name": "First Position Date - Treasury Roll",

  "BeginEventType": 17,

  "DaysBefore": 0,

  "EndEventType": 7,

  "DaysAfter": 0,

  "Type": "FUT",

  "Exchange": "CBT",

  "Codes": [ "17", "21", "25", "26", "TN", "UBE" ]

  },

• • For MAC swap futures products:
    • • Changes the BeginEventType exclusion attribute to be last trade date (enum = 7) and the EndEventType to be last delivery date (enum=14).
      • This was previously beginning at First Intent Date, which is about a week prior to delivery for these products.

      • Example updated config:

{

  "Enabled": true,

  "Name": "Last Intent Date - MAC DSF",

  "BeginEventType": 7,

  "DaysBefore": 0,

  "EndEventType": 14,

  "DaysAfter": 0,

  "Type": "FUT",

  "Exchange": "CBT",

  "Codes": [ "F1U", "B1U", "T1U", "N1U" ]

  },

• • For Eurodollar options:
    • Changes the DaysBefore exclusion attribute to be 1 day.
    • This was previously 0 days before LTD which was identified as too close to E&A.
    • Example updated config:

{

  "Enabled": true,

  "Name": "Last Trade Date - ED Option Expiration",

  "BeginEventType": 7,

  "DaysBefore": 1,

  "EndEventType": 999,

  "DaysAfter": 0,

  "Type": "OOF",

  "Exchange": "CME",

  "Codes": [ "ED", "E0", "E2", "E3", "E4", "E5" ]

  }

• There are no default additions to the TradeEvents section of the configuration.json file to support new Eris product trade event exclusions, however, users who want to exclude these products for any valid trade event can create a new custom exclusion based on the logic defined in the User Guide here.
  • Eris products are cash-settled, hence, no exclusions were deemed necessary by default.
• Removes span.ini and orgmast.xml from the Plugins/Optimizer directory. These file is now supplied in the market data zip file and users will not need to specify their locations.
• Removes the following configurations which were deprecated or made redundant in this or a prior version:
  • "ShowTransferOrigin"
  • "ShowTotalSavings"
  • "MaxNumberOfIterations"
  • "SpanIniFilesFolder" (see above note)
  • "RiskManagerConfigIsEncoded"

Testing Considerations

• Please note Optimizer version 17 is a bundled release, meaning multiple CME product enhancements are covered in a single release. The delivery dates for updated sets of market data in the New Release (NR) environment are:
  • September 27, 2021: Optimizer software delivery – includes sample inputs.
    • Firms can begin their test by installing the latest build and testing to ensure sample data runs without error.
  • October 13, 2021 (EOD): Updated Optimizer inputs including BSBY and SORA swaps in New Release environment available via secure FTP.
    • Firms should test BSBY/SORA swaps beginning this date.
  • October 20, 2021 (EOD): Updated Optimizer inputs including Eris SOFR-based swap futures in New Release environment available via secure FTP.
    • Firms should test Eris SOFR-based futures beginning this date.

Out of Scope

• Required Optimizer input files. 
• Exclusion logic in the configuration.json for the new Eris SOFR-based swap futures. Users who want to exclude these products for any valid trade event can create a new custom exclusion in the configuration.json file based on the logic defined in the User Guide here.

Optimizer Version 16.0 Release Notes

Version: 16.0.0.0

Release Date: March 4, 2021

Mandatory Build: Y

Mandatory Cutover Date: April 26, 2021

Enhancements

• Incorporates new portfolio margin eligible products SR1 (SOFR 1-month futures) and SR3 (SOFR 3-month futures). 
  • SR1 and SR3 products eligible to transfer to OTC accounts to achieve risk offsets.
  • This build of Optimizer will generate SR1 and SR3 futures transfers and consider SR1 and SR3 during Optimization.
  • Users who do not include SR1 and SR3 in the positions.csv file today should add these contracts to achieve optimal results.
  • See all eligible products here.
• Updates to liquidity add-on computations for SOFR exposure.

Fixes

• None

Configuration Changes

• Updates the default configuration for options eligibility.
  • This build assumes Eurodollar options are eligible to optimize by default.
  • Firms who wish to exclude all options may utilize the standard Exclusions → Product configuration in the configuration.json file described here or simply carry forward their version 15 config file.
• Reverts change to default location for program files span.ini and orgmast.xml from the 'Inputs' directory to the 'Plugins/Optimizer directory. This is consistent with all builds of Optimizer prior to Version 15.
• See Configuration Changes in version 15.1 below (if not already installed). 

Optimizer Version 15.2 Release Notes

Version: 15.2.0.0

Release Date: December 16, 2020 

Mandatory Build: N

Notes: Firms must take v15 (described below), v15.2 is optional but recommended

Enhancements

• Minor updates to logging which improves the logged warnings for products which cannot be validated.
• Updates the header fields in the MarginSummaryYYYYMMDD.csv file to read "Span for all Futures and Options" instead of "Span for all Futures."
• See Enhancements in version 15.1 below (if not already installed).

Fixes

• Fixes an issue related to complete account close-out/netting:

  • Overview: If a portfolio is NettingEligible = Y (netting is enabled) and all positions net to zero, then Optimizer is generating an error instead of generating the appropriate netting transfers.

  • Example:

    • Account A is 100 long Dec 10-year treasury, which is optimized in OTC account

      • No other positions in this account

    • Account A closes out; i.e. 100 short position is booked in the futures side account
    • EOD position is 0,0 for Account A
    • Optimizer generates an error for this account, processes other accounts
  • Out of scope:
    • Standard netting logic for accounts not undergoing a completed close-out of positions.
• This build fixes the above by allowing netting transfers to occur for accounts undergoing a complete close-out and does not generate an error for this use case.
• Interim workaround: Firms experiencing this issue can monitor their log files for the condition "SUCCESSwithERRORS” and work with their back office staff to treat the close-out are they would today if the Optimizer failed to run on the day of a close-out. This may be a manual T+1 action to close out the position in FEC.
• See Fixes in version 15.1 below (if not already installed).

Configuration Changes

• None
• See Configuration Changes in version 15.1 below (if not already installed) 

See also: Pre-installation Checklist and Installation Instructions in version 15.0 release notes below.

Optimizer Version 15.1 Release Notes

Version: 15.1.0.0

Release Date: November 11, 2020 

Mandatory Build: N

Notes: Firms must take v15 (described below), v15.1 is optional

Enhancements

• Configuration support for Net Option Value (NOV) capping/SPAN flooring (see configuration notes below).

Fixes

Optimizer v15.1 addresses two issues with transfer records generated for options. Both changes impact attributes which are not required by CME clearing to clear options transfer records and therefore have no impact on front end clearing of options trades. Firms must evaluate if either issue presents any impact to their back office processing. If so, it is recommended firms use Optimizer v15.1 (in place of Optimizer 15) on the December 7, 2020 production date.

• Optimizer v15.1 removes the optional FIXML attribute "CFI" from the fixmlTransfersyyyyymmdd.txt file for all transfer records. In prior versions of Optimizer, this attribute was a fixed value expressed as CFI="FXXXXX for both futures and options on futures, but this value is is not relevant for options. This attribute is produced correctly in clearing confirmation/trade acknowledgment messages from CME and therefore was not required for Optimizer transfer records, hence its removal.
• Optimizer v15.1 fixes an issue which incorrectly described the SecType attribute in the Undly block (underlying security type) for options as "OOP." The correct value for underlying security type for options on futures is "FUT." Optimizer v15.1 describes the underlying security type for options as "FUT" as expected. This attribute is optional for inbound trade messages to CME and has no impact on clearing confirmation/trade acknowledgment messages, which do not include this field.

Sample updated option transfer record:

<FIXML v="5.0 SP2" xv="109" cv="CME.0001" s="20090815">
	<TrdCaptRpt RptID="900003" TrdID="900003" TransTyp="0" RptTyp="0" TrdTyp="3" TrdHandlInst="8" OrigTrdDt="2020-06-03" LastQty="10" LastPx="0" TrdDt="2020-11-11" MLegRptTyp="1" TxnTm="2020-11-11T10:52:38.0654511" MsgEvtSrc="API">
		<Hdr SID="1Z9" TID="CME" SSub="CME" TSub="CME" Snt="2020-11-11T10:52:38.0654511"/>
		<Instrmt ID="E3" SecTyp="OOF" MMY="202012" StrkPx="97.5" PutCall="0" Exch="CME"/>
		<Undly Src="H" SecTyp="FUT" MMY="202312"/>
		<RptSide Side="2" ClOrdID="PM001" InptDev="API" CustCpcty="4" SesID="RTH" SesSub="X" OrdTyp="M">
			<Pty ID="CME" R="22"/>
			<Pty ID="CME" R="21"/>
			<Pty ID="1Z9" R="1"/>
			<Pty ID="OPTMZ5" R="24">
				<Sub ID="1" Typ="26"/>
			</Pty>
			<Pty ID="973" R="17"/>
			<Pty ID="CME123" R="48">
				<Sub ID="1" Typ="26"/>
				<Sub ID="4" Typ="4000"/>
			</Pty>
		</RptSide>
	</TrdCaptRpt>
</FIXML>

Configuration Changes

Please note technical details about this configuration can be found in the Optimizer User Guide.

• Optimizer v15.1 adds a new configuration property to control net option value capping/SPAN flooring in the Optimizer solution decision. 
  • Property Name: FloorSpanForFinalMarginCheck
  • Type: Boolean
  • Default Value: True
  • A value of "true" means that Optimizer caps NOV.

  • A value of "false" means that Optimizer does not cap NOV (same behavior as prior builds)
    
    

    "FloorSpanForFinalMarginCheck": true

  • Background: 
    • Optimizer iterates through multiple solution states to find the best account savings. At the end of the Optimizer software workflow, it reviews possible solutions and selects one based on the lowest margin.
    • Net Option Value can act as a credit against computed market risk, and can lead to a SPAN Margin less than 0.
    • During margin settlement, total available net option value for a given portfolio is capped at the total Risk Maintenance Requirement using this formula:
      • If Risk Maintenance Requirement (RRM) is > or = total Net Option Value, then Total Requirement = RRM – NOV
      • If Risk Maintenance Requirement (RRM) < total Net Option Value, then Total Requirement = 0 due to NOV capping
      • For example, if an account’s computed risk factors are:
        • RRM = $1,000,000
        • NOV = $1,200,000
        • Then total requirement = $0, ANOV was capped to $1,000,000
  • Optimizer v15.1 allows users to specify whether the Optimizer should cap the net option value similar to the above when it makes its solution state decision.
    • For a given account, example 1: "FloorSpanForFinalMarginCheck": true
      
      • Optimized solution 1: IRS margin: 5,000,000; SPAN margin: 0 (capped); Total margin: 5,000,000
      • Optimized solution 2: IRS margin: 0; SPAN margin: 0 (capped); Total margin: 0
      • Optimizer chooses solution 2 with capping logic on
    • For the same account example 2: "FloorSpanForFinalMarginCheck": false
      
      • Optimized solution 1: IRS margin: 5,000,000; SPAN margin: -15,000,000 (uncapped); Total margin: -10,000,000
      • Optimized solution 2: IRS margin: 0; SPAN margin: -9,000,000 (uncapped); total margin: -9,000,000
      • Optimizer chooses solution 1 with capping logic off
      • Prior versions of Optimizer also choose this solution

Optimizer Version 15.0 Release Notes

Version: 15.0.0.0

Release Date: October 28, 2020 (see adoption timeline below)

Enhancements

This version of Optimizer support listed options in portfolio margining.

1. Updates to System Requirement (see User Guide)

2. Updates to Optimizer input files

   • Input File Contents/Number of Required Files
     • Optimizer version 15 requires 9 input files to run
       • All inputs will be required
     • Updated input file set is larger in size than prior versions of Optimizer
       • Version 15 input file set is ~ 700 MB in size, including one compressed file containing both existing and new input (details in grid below)
         • Uncompressed size is ~2.2 GB
       • Optimizer software will decompress the new zip automatically - not user intervention will be required.
       • Optimizer v14 previously required 13 files to run with a much smaller file size footprint
       • Firms with good network connectivity (dedicated circuits, 10 MB/s or higher) should expect reasonable (observed ~1 minute) transfer duration from FTP whereas firms connecting via internet should consider direct connectivity
   • There are no impacts to the firm-produced Positions.csv input file
     • Firms should continue to include options in the positions.csv file as normal. Firms not included options in the input file should add options.
   • Input File Publishing Timeline
     • New Optimizer input zip file will be published by 6 pm CT. The file latency is driven by increased computation load when CME Clearing produces options market data.
     • Timeline details for both ITD and EOD files is in the grid below.

Optimizer 15 Input File Impacts (all times CT)

*New Files

**Files being decommissioned or replaced

***All test region (NR) file names are the same but include “.nr” at the end.

  3. Updates to Optimizer output files 

• Optimizer will produce options transfer records in both Optimizer transfer output file formats (.csv and .txt)
• Options will be transferred at 0 price to mitigate movement of premium for Optimizer’s post-trade allocations.
• Output impact detail:
  • csvTransfersyyyymmdd_[run number].csv
    • File describes Optimizer transfer records in csv format
    • File will be updated to include options transferred at 0 price.
    • Similar to futures transfer records, options transfer records can generate with TransferOrigin = Optimizer, Netting, or Exclusion
    • Please note there are no new fields in the report
    • Sample:
  • fixmlTransfersyyyymmdd_[run number].txt
    • File describes Optimizer transfer records in fixml format. Firms typically use this file to transmit transfer records to CME via standard message queue channels.
    • File will be updated to include options transferred at 0 price.
    • Sample updated transfer record with highlighted additional fields for options:

<?xml version="1.0" encoding="UTF-8"?>
<FIXML v="5.0" s="20111206">
	<TrdCaptRpt RptID="900000" TrdID="900000" TransTyp="0" RptTyp="0" TrdTyp="3" TrdHandlInst="8" OrigTrdDt="2020-05-21" LastQty="1000" LastPx="0" TrdDt="2020-06-16" MLegRptTyp="1" TxnTm="2020-06-16T09:38:29.4090611" MsgEvtSrc="API">
		<Hdr SID="010" TID="CME" SSub="CME" TSub="CME" Snt="2020-06-16T09:38:29.4090611"/>
		<Instrmt ID="ED" CFI="FXXXXX" SecTyp="OOF" MMY="202009" StrkPx="99.5" Exch="CME" PutCall="1"/>
		<Undly SecTyp="FUT" Src="H"></Undly>
		<RptSide Side="1" ClOrdID="PM001" InptDev="API" CustCpcty="4" SesID="RTH" SesSub="X" OrdTyp="M">
			<Pty ID="CME" R="22"/>
			<Pty ID="CME" R="21"/>
			<Pty ID="010" R="1"/>
			<Pty ID="SEGACCOUNT" R="24">
				<Sub ID="1" Typ="26"/>
			</Pty>
			<Pty ID="0S0" R="17"/>
			<Pty ID="PMACCOUNT" R="48">
				<Sub ID="1" Typ="26"/>
				<Sub ID="4" Typ="4000"/>
			</Pty>
		</RptSide>
	</TrdCaptRpt>
</FIXML>

Fixes

• No fixes in this release.

Configuration Changes

Optimizer version 15 re-imagines the Optimizer’s existing exclusion configurations. Please note technical details about the new configurations can be found in the Optimizer User Guide.

Optimizer’s standard exclusion logic will be updated to include:

• Exclusions by performance bond account (PBAccount / margin account):
  • When Enabled = true, Optimizer users can specify an account identifier or a string of identifiers as well as a product type (i.e. options) from the positions.csv which Optimizer will exclude from Optimization.
  • To be used when a specific account owner would like to limit Optimization, for instance to prevent options from Optimizing. Users can simply remove an account from the positions.csv input file if no Optimization should occur.
  • The default is Enabled = false
  • See more in Optimizer User Guide

• Exclusions by product exchange:
  • When Enabled = true, Users can specify a product exchange (CME, CBT, etc.) or a string of product exchanges and Optimizer will exclude all line items in the positions.csv file which contain products found in that product exchange from Optimization.
  • The default is Enabled = false
  • See more in Optimizer User Guide

• Exclusions by product type alone or product type and product code:
  • When Enabled = true, Users can specify a product type (FUT, OOF, etc.) or a string of product types and Optimizer will exclude all line items in the positions.csv file with that product type from Optimization.
  • Users can specify a product type and a product code (41, TN, etc.) or a string of product codes and Optimizer will exclude all line items in the positions.csv file with that product type and product code from Optimization.
  • The default is Enabled = true and excluded products = OOF
    • Note: options in portfolio margining is pending regulatory approval, hence options will be disabled by this flag by default. 
  • See more in Optimizer User Guide

• Exclusions by trade event:
  • When Enabled = true, users can specify a trade lifecycle event (First Intent Date, Option Expiration date, etc.) and a window of days prior to that trade lifecycle event to establish an exclusion window for a product or string of products and Optimizer will exclude all products inside the exclusion window specified for that product.
  • The default is Enabled = true
  • See more in Optimizer User Guide

In addition to the standard exclusion logic above, Optimizer version 15 supports exclusion of options undergoing early exercise and assignment. Please note technical details about this configuration can be found in the Optimizer User Guide.

•  Non-standard exclusion logic: early exercise

  • When Enabled = true, Optimizer will exclude any options strikes which experienced an early exercise based on the clearing POS699C file (option exception summary report)
  • POS699C is included in the new cme_optimizer_marketdata zip file
  • Exclusion impacts short and long options positions and for excluded strikes, including those which are not assigned in the random assignment process
  • CME expects clearing firms to use this exclusion logic for the day 1 go live only. This exclusion logic should be turned off when firms are ready to go live with performing exercise and assignment in OTC accounts.
  • Firms not using this flag should make sure to be familiar with the other standard exclusion flags, described previously in this document.
  • The default is Enabled = true (v15 only)

Pre-installation Checklist

1. Please ensure that your system adheres to the minimum system requirement as described in the CME Optimizer Software User Guide.
2. CME Optimizer 15 is designed to install side-by-side with existing CME Optimizer installations.
3. If you have a prior version of CME Optimizer installed, please ensure that the application is not running.

Installation Instructions

To install CME Optimizer 15.0.0.0 perform the following steps:

1. Download CME Optimizer 15.0.0.0. It is available to download from CME CORE. Detailed instructions can be found in the CME Optimizer Software User Guide, 'Downloading Optimizer' section.
2. Log onto the system where the software is to be installed. You should log on as an administrative user.
3. Double-click on the Optimizer 15 installer (filename: Optimizer.15.0.0.0.msi), this will start the installation process.
4. Follow the on-screen instructions:
5. You must accept the End-User License Agreement (EULA) to install Optimizer 15:
6. Accept the default installation location or optionally change it:
7. You can choose to automatically run the Optimizer 15 Samples once the installation completes:

Troubleshooting

If you run into issues during the installation, please refer to the guidance below. Alternatively, reach out to our posttradeservices@cmegroup.com for further assistance:

1. Verify that you have the correct privileges to install software on the target system and that security software/policies are not preventing software from being installed
2. Verify that you have the minimum system requirements for hardware and operating system
3. Verify that you have installed the software prerequisites and that a system reboot has been performed
4. If the installer starts, but fails to complete, try running the MSI with logging enable from the command-line e.g. PowerShell:
   
   .\Optimizer.15.0.0.0.msi /log installer.log
   
   
5. If the installer log does not point to a localized issue, then forward the log to posttradeservices@cmegroup.com for further investigation (see below).

Suggested Test Cases

Below is a set of suggested tests for Optimizer 15 adoption. The test cases and acceptance criteria here are suggestions only. Clearing firms are responsible for Optimizer on their own infrastructure. Please review above impacts prior to running test scenarios. Additional tests should be devised to understand the impacts of options in portfolio margin accounts - those can be decoupled from Optimizer tests.

Operational Clearing Changes Related to Optimizer 15

•   ITD/EOD Clearing Cycle/File Impacts

  See impacts to Optimizer input files above, this section describes changes to files which are published by the clearing system but are not used as impacts to Optimizer software. 

  • EOD listed derivatives in cleared swap account report impacts:
    • POS542, describing listed derivatives in cleared swap accounts, will be enhanced to include options fields describing option strike and put/call indicator
      • New fields will be present at the end of the file
    • EOD IRS Margin file impacts
      • IRSMR3 and MR files will be expanded to include one new field: Available Net Option Value
        • Field will be present at the end of the file
      • CME will publish two versions of the EOD IRSMR3 file:
        • Existing IRSMR3 file will be considered the preliminary file
          • File name: IRSMR3_[firm id]_yyyymmdd.csv (no change)
          • SLA: 9 pm CT (no change)
            • File generally publishes earlier than SLA (~8 pm CT)
          • Firms who have no options in OTC accounts can continue to interact with this file
        • New final IRSMR3 file, capturing EOD E&A activity, will also be published
          • Proposed new file name: IRSMR3_FINAL_[firm id]_yyyymmdd.csv
          • SLA: 10 pm CT
            • File may publish earlier than SLA
          • Firms with options in OTC accounts should begin using this version of the file
        • Sample reports provided upon request
      • CME Clearing EOD timeline (portfolio margin program and daily E&A) is below.

  

Adoption Timeline (TBC)

• New Release, October 28, 2020
• Production, December 7, 2020

CME Core Impacts

• CME CORE will be enhanced to allow for options in MarginType = OTC / Cross-margin flag on
• Because existing workflows allow users select ‘Optimize’ for accounts which include options, there are no changes to portfolio inputs
• CME CORE Optimizer report output will contain options which are selected by Optimizer to move to a cleared swap OTC account
  • Note options fields Strike, Put/Call and Und. Period Code already exist in CORE’s User-Defined Optimization report, so no new fields are required

Margin API Impacts

• The Margin API will be enhanced to allow for options in MarginType = OTC
• Because existing workflows allow users to send accounts with options to the Optimize feature, there are no changes to portfolio inputs
• Margin results from the Optimize feature will contain options which are selected by Optimizer to move to a cleared swap OTC account
  • Here is a sample report including options.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:optimizerRpt xmlns:ns2="http://cmegroup.com/schema/core/1.2" status="SUCCESS">
    <margin portfolioId="12345678" id="1234567" createTime="2019-11-21T19:56:42+00:00" updateTime="2019-11-21T19:56:45+00:00">
        <amounts conc="3531.75158986107" init="1033754.24448408" maint="1037285.99607394" optVal="48125">
            <portfolio futCurrAmt="230415" futPreAmt="260000" futPostAmt="1300" otcCurrAmt="623627.825051428" otcPreAmt="1547449.14988385" otcPostAmt="1035985.99607394" diffAmt="770163.15380991"/>
        </amounts>
    </margin>
    <transaction portfolioId="12345678" type="TRADE" id="1234567">
        <payload encoding="STRING" format="FIXML">
            <string><?xml version="1.0" encoding="UTF-8" standalone="yes"?><FIXML xmlns="www.cmegroup.com/fixml50/1" v="5.0 SP2" xv="109" cv="CME.0001" s="20090815"><TrdCaptRpt LastQty="100" SettlCcy="USD"><Instrmt ID="ED" Src="H" SecTyp="OOF" MMY="202009" StrkPx="99.5" Exch="CME" PutCall="1"/><Undly SecTyp="FUT" Src="H"/><RptSide Side="2" InptDev="API"><Pty ID="TEST" R="4"/><Pty ID="CME" R="21"/><Pty ID="1234" R="24"><Sub ID="2" Typ="26"/></Pty></RptSide></TrdCaptRpt></FIXML></string>
        </payload>
    </transaction>
</ns2:optimizerRpt>

Optimizer Version 14.0 Release Notes

Version: 14.0.0.0

Release Date: 28th May 2020 (see adoption timeline below)

Enhancements

• Supports €STR discounting curve - more information about the discounting transition at CME is here
• Netting behavior updated to net the positions with the net quantity closest to zero
• Added support for an optional pass-through 'memo' field in the positions.csv file
  • Header and field values are firm-defined and entirely optional
• Updates to field TrdHandlInst in output transfer record from TrdHandlInst="2" to TrdHandlInst="8"
  • This change is related to an FECPlus change described here. 

Fixes

• Fixes a bug which prevented ERIS positions from being margined properly

Configuration Changes

• No configuration changes in this release.

Pre-installation Checklist

1. Please ensure that your system adheres to the minimum system requirement as described in the CME Optimizer Software User Guide.
2. CME Optimizer 14 is designed to install side-by-side with existing CME Optimizer installations.
3. If you have a prior version of CME Optimizer installed, please ensure that the application is not running.

Installation Instructions

To install CME Optimizer 14.0.0.0 perform the following steps:

1. Download CME Optimizer 14.0.0.0. It is available to download from CME CORE. Detailed instructions can be found in the CME Optimizer Software User Guide, 'Downloading Optimizer' section.

   1. Note users do not need to uninstall the prior version of Optimizer (v13). Optimizer 14 can be installed and run side by side with Optimizer 13 for users who install in production prior to the mandatory production deadline.

2. Log onto the system where the software is to be installed. You should log on as an administrative user.
3. Double-click on the Optimizer 14 installer (filename: Optimizer.14.0.0.0.msi), this will start the installation process.
4. Follow the on-screen instructions:
5. You must accept the End-User License Agreement (EULA) to install Optimizer 14:
6. Accept the default installation location or optionally change it:
7. You can choose to automatically run the Optimizer 14 Samples once the installation completes:

Troubleshooting

If you run into issues during the installation, please refer to the guidance below. Alternatively, reach out to our posttradeservices@cmegroup.com for further assistance:

1. Verify that you have the correct privileges to install software on the target system and that security software/policies are not preventing software from being installed
2. Verify that you have the minimum system requirements for hardware and operating system
3. Verify that you have installed the software prerequisites and that a system reboot has been performed
4. If the installer starts, but fails to complete, try running the MSI with logging enable from the command-line e.g. PowerShell:
   
   .\Optimizer.14.0.0.0.msi /log installer.log
   
   
5. If the installer log does not point to a localized issue, then forward the log to core@cmegroup.com for further investigation (see below).

Operational Changes for Optimizer 14

• No new files
• Changes to existing files:
  • €STR curve details will publish in existing Optimizer input files: "Base_Curves . . .", "IRSDL . . .", "cme_rloptimizercfg . . ."

Adoption Timeline

• New Release: May 28, 2020
• Production: July 27, 2020

Optimizer Version 13.1 Release Notes

Version: 13.1.0.46

Release Date: 13th December 2019

Fixes

1. SNT date not applied to transfers generated from treasury rolls.
2. Single net transfers not generated in FIXML and CSV transfers when MoveDecision and/or NettingMoveDecision was set to SNT.
3. Transfers showing negative transfer amount.

Enhancements

• New transfer origin 'Exclusion' for CSV transfers. Applicable to transfers generated from product and/or treasury roll exclusions.
• New configuration property added to configuration.json called "ExclusionMoveDecision" which can be used to control exclusion transfer behavior (see matrix and sample below).

Configuration Changes

Pre-installation Checklist

1. Please ensure that your system adheres to the minimum system requirement as described in the CME Optimizer Software User Guide.
2. During the installation, the installer will remove any prior versions of CME Optimizer 13 and install the latest version.
3. If you have a prior version of CME Optimizer 13 installed, please ensure that the application is not running.
4. If you use the default configuration or input/output directories in "C:\Program Files\CME Group\CME Optimizer 13", then it is recommended that you backup these assets before installing this update.

Troubleshooting

If you run into issues during the installation, please refer to the guidance below. Alternatively, reach out to our posttradeservices@cmegroup.com for further assistance:

1. Verify that you have the correct privileges to install software on the target system and that security software/policies are not preventing software from being installed
2. Verify that you have the minimum system requirements for hardware and operating system
3. Verify that you have installed the software prerequisites and that a system reboot has been performed
4. If the installer starts, but fails to complete, try running the MSI with logging enable from the command-line e.g. PowerShell:
   
   .\Optimizer.13.1.0.46.msi /log installer.log
   
   
5. If the installer log does not point to a localized issue, then forward the log to posttradeservices@cmegroup.com for further investigation (see below).

Configuration Sample (fragment)

{
	"Defaults": {
		"ExclusionMoveDecision": "LIFO"		// New Property
	}
}

Optimizer Version 13.0 Release Notes

Mandatory Production Release target date August 26, 2019

See also new Optimizer User Guide.

New features for Optimizer 13 include:

1. Fully integrated CME IRS margin model. Prior versions approximated IRS risk using delta ladder inputs.
2. Some users may see additional efficiencies compared to prior versions.

Operational Changes for Optimizer 13 include:

1. New Optimizer input files will be required to run version 13, summarized below:
   1. csv is being decommissioned and will no longer be available for download
   2. xml will no longer be an input to Optimizer 13, but it is not being decommissioned.
2. The Configuration file is migrated from XML to JSON format.
3. The output log file is updated to reflect the re-written Optimizer architecture.
4. The output margin reports references to HVaR are replaced by VaR.

Adoption Timeline (TBC):

Dissimilar to prior installations, users can keep Optimizer 12 installed while installing version 13 in order to run either version under the new plug-in architecture.  Due to the large quantity of changes, a new Optimizer User guide has been published here. For general details about the Portfolio Margin program, see here. For detailed release notes please see here.

CME CORE Impacts

CME CORE Rates User Interface will be impacted in the following ways:

• Deprecation of the Ideal Optimizer Report in the ‘Optimize’ feature
  • This report provided a list of futures not present in the account which would reduce total IRS-based risk to its maximum efficiency.
  • Other standard Optimize feature reports will continue to be available.
• ‘Optimize’ feature will be available in the test region in August.