For the latest roadmap of CME Group technology initiatives:
See the Development Launch Schedule.
Additional Resources:
- Versions of BrokerTec notices dated March 23, 2023, and onward are available from the Notice Search page.
- Archived BrokerTec notices dated July 2019 through March 9, 2023, are available from the BrokerTec Support Portal, which requires a separate login.
Critical System Information
Upcoming Change to Risk Management System Designated Person Form Process - Q1 2025
In Q1 2025, the current nominated Risk Management System Designated Person (DP) for each BrokerTec participant will be migrated to BrokerTec Risk Management System users. This migration will happen automatically so long as each Risk DP has a valid CME Group Login that matches the email address on file in Service Cloud DP.
Each BrokerTec participant is recommended to:
- Review and update its current listing of Risk DPs as required
- Ensure that each Risk DP has a valid CME Group Login
For questions on how to make changes, information regarding the authorized persons or middle office managers for your firm, or any system support, contact CME Global Account Management.
New Process - Expected in Q1 2025
Starting in Q1 2025, BrokerTec will stop onboarding new Risk DPs. New users appointed by the firm’s Middle Office Managers will be onboarded as BrokerTec Risk Management System users and given BrokerTec risk system entitlements. The BrokerTec Risk Managers will be onboarded via this form.
The form must be submitted by a Middle Office Admin Manager who oversees the GFIDs they are requesting. If the firm does not have a Middle Office Manager, the firm will need to work with CME Global Account Management to have one set up by filling out the Self-Service form in Service Cloud.
Current Process
When a BrokerTec participant seeks to nominate a new Risk DP, an existing Risk DP for the participant must complete this form. In the event an existing Risk DP is no longer with the firm, an authorized person of the firm may contact EASE directly rather than completing the form.
When nominating a new Risk DP, only a written request by an authorized person of the firm is considered. As a reminder, BrokerTec participants should keep their Risk DPs current and should make any changes as soon as possible to avoid any delays in trading activity.
When nominating a new Risk DP, only a written request by an authorized person of the firm is considered. As a reminder, BrokerTec participants should keep their Risk DPs current and should make any changes as soon as possible to avoid any delays in trading activity.
If you have compliance questions contact U.S. Compliance.
BrokerTec U.S. Repo Managed Order Enrichment - Q1 2025
Effective Q1 2025, BrokerTec on CME Globex will introduce the new Top of Stack (TOS) priority feature for U.S. Repo instruments. TOS prioritizes the passive managed order of the TOS owner based on the pre-defined TOS requirements.
More details on the TOS functionality are now available in the client impact assessment.
With this launch, BrokerTec U.S. Repo clients can receive the Unsolicited Modify message in a scenario when the passive managed order (i.e. tag 6881-ManagedOrder=1) is reprioritized with quantity adjustment. See Unsolicited Modify Acknowledgment Messages for more information on this type of order modification. Currently, iLink tag 6881 is for internal use only.
The new TOS for products subject to this change are currently available for customer testing in New Release.
Reminder: Notification Required for Changes in MPID or Registration Status
BrokerTec Americas has an obligation to report U.S. Treasury transactions to FINRA's Trade Reporting and Compliance Engine (TRACE). Each report must identify the parties to the transaction using a FINRA assigned Market Participant Identifier (MPID).
As a reminder, participants must notify BrokerTec of their change in entity type, regulatory status, and any changes to MPIDs as soon as possible, if not prior to the change, to ensure complete and accurate trade reporting.
For more information, view the TRACE FAQ.
If you have any questions please contact USCashMarketsCompliance@cmegroup.com.
BrokerTec MDP 3.0 SBE Schema Update - This Week
To support future enhancements for BrokerTec markets on CME Globex, including BrokenDates fields, the MDP 3.0 SBE core schema will be updated to version 13 starting this Sunday, February 2 (trade date Monday, February 3), and conclude Sunday, March 16 (trade date Monday, March 17). The new fields are for future use and will not be populated with the schema launch. More information regarding these enhancements will be published in a future BrokerTec Markets on CME Globex Notice.
All BrokerTec channels on CME Globex are currently utilizing core schema version 11. To ease customer development efforts, the new SBE schema files will support template extension for MDP 3.0 messages. For client systems that do not support template extension, the schema update is not backward compatible, and the MDP 3.0 messages sent from CME Globex cannot be decoded.
CME Group strongly advises to test the readiness of client applications in advance of the schema upgrade in the NR environment.
Please review the client impact assessment for full technical details and launch schedule.
NewiLink 3 On-Demand Party Details Changes - March 30
Starting Sunday, March 30 (trade date Monday, March 31), CME Group will implement the iLink 3 messaging changes to on-demand administrative information on Market Segment Gateway (MSGWs) to return critical information currently only sent on the iLink messages from the customer to CME Globex.
Operator
Tag 1691-PartyDetaiID value on the Operator Party Detail Role (tag 1693-PartyDetailRole=118) on the Party Details Definition Request Acknowledgement (PDDRA, tag 35-MsgType=CY) will reflect the values from the Party Details Definition Request (PDDR, tag 35-MsgType=CX).
| iLink 3 Party Details Definition Request Acknowledgment | |||
|---|---|---|---|
| Tag 1693 - Party Detail Role | Submitted tag 1691-PartyDetailID | Current Return tag 1691-PartyDetailID Value Behavior | New Return tag 1691-PartyDetailID Value Behavior |
| 118 (Operator) |
ABCDE | Not Present | ABCDE |
Please note: In the case of a successful Order Cancel, the PDDRA will reflect the party details from the resting order.
Drop Copy will reflect the Operator value from the iLink message in Drop Copy new tag 129-DeliverToSubID.
| Drop Copy Message Tag | iLink 3 Source Message Tag | |||
|---|---|---|---|---|
| FIX Tag | FIX Name | Binary Tag | Binary Name | Description |
| 129 | DeliverToSubID | 1691 1693 | PartyDetailID PartyDetailRole=118 (Operator) | Represent the individual or team submitting the message |
Memo
Tag 5149-Memo value on the Party Details Definition Request Acknowledgement (PDDRA, tag 35-MsgType=CY) will reflect the party details from an Order Mass Action Request and from an unsuccessful Order Cancel Request.
In the case of a successful Order Cancel, the PDDRA will reflect the party details from the resting order.
| iLink 3 Party Details Definition Request Acknowledgment | ||||
|---|---|---|---|---|
| Message from CME Globex to Client System | Submitted tag 5149-Memo from New Order | Submitted tag 5149-Memo from Cancel Request | Current Return tag 5149-Memo | New Return tag 5149-Memo |
| PDDRA for an successful Mass Order Cancel | ABC123 | XYZ456 | Not Present | XYZ456 |
| PDDRA for an unsuccessful Mass Order Cancel | ABC123 | XYZ456 | Not Present | XYZ456 |
| PDDRA for an successful Order Cancel | DEF789 | UVW001 | Not Present | DEF789 |
| PDDRA for an unsuccessful Order Cancel | DEF789 | UVW001 | Not Present | UVW001 |
On-Demand Order Cancel Requests
In the event of a successful Order Cancel, the Party Details Definition Request Acknowledgement (PDDRA, tag 35-MsgType=CY) will reflect the party details from the resting order.
There is no change to an unsuccessful Order Cancel Request.
| Message from CME Globex to Client System | Party Details Definition Request Acknowledgment | |
|---|---|---|
| CURRENT ACKNOWLEDGE VALUE | NEW ACKNOWLEDGE VALUE | |
| PDDRA for a successful Order Cancel | Values from the resting order, except the following tags will reflect the values from the PDDR for the cancel request
|
All values will be populated from the resting order |
On-Demand Order Cancel Replace
In the event of a successful Order Cancel Replace, the Party Details Definition Request Acknowledgement (PDDRA, tag 35-MsgType=CY) will reflect the party details from the order cancel-replace request.
In the case of an Order cancel-replace request with Negative In Flight Mitigation (IFM) scenario, where IFM cancel/replace quantity is less than that of the filled quantity, CME Globex cancels the order. The PDDRA of an unsolicited Order Cancel will reflect the party details from the resting order.
| Message from CME Globex to Client System | Party Details Definition Request Acknowledgment | |
|---|---|---|
| CURRENT ACKNOWLEDGE VALUE | NEW ACKNOWLEDGE VALUE | |
| PDDRA for a successful Order Cancel Replace | Value from the cancel replace request, except the following tags will reflect the values from the PDDR for the resting order:
|
All values will be populated from the Order Cancel Replace |
| PDDRA for an unsolicited Order Cancel for the negative IFM scenario | Values from the cancel replace request
|
All values will be populated from the resting order |
These changes are only applicable to the on-demand administrative information. There is no change to the Pre-Registered Party Detail Definition Request Acknowledgment (tag 35=CY) messages sent from Order Entry Service Gateway to Client Systems.
More detailed information on party details is available in iLink 3 Party Details Definition Messaging.
Production Launch Schedule
iLink 3 BrokerTec will be phased in as follows:
| iLink 3 On-Demand Party Detail Changes | ||
|---|---|---|
| Market Segment ID | Description | Production Date |
| 46 | BrokerTec EU Repo | March 30 |
| 44 | BrokerTec EGB | |
| 42 | BrokerTec US Repo | April 6 |
| 40 | BrokerTec US Treasury Actives | |
These changes will be available for customer testing in the New Release on Thursday, February 13.
Product Changes
Delisting of BrokerTec Buy-Sell-Back (BSB) LCH SA Cleared Repos and GC Baskets for Spanish Collateral on CME Globex - This Week
Effective this Sunday, February 2 (trade date Monday, February 3) BrokerTec will cease to offer Spanish Buy-Sell-Back products on its European Repo CLOB trading platform, as offered by CME Amsterdam B.V.
| Delisting of BrokerTec Buy-Sell-Back (BSB) LCH SA Cleared Repos for Spanish Collateral on CME Globex | ||||
|---|---|---|---|---|
| PRODUCT NAME | MDP 3.0 Tag 2714- Financial Instrument Full Name | MDP 3.0: TAG 6937-ASSET | ILINK: TAG 55-SYMBOL MDP 3.0 TAG 1151 - SECURITY GROUP | MDP 3.0: TAG 1180-APPLID |
| Spanish Euro CCP Buy Sell Back Bills | SA_BSB_SGLT* | ESBBL | EUBL | 517 |
| Spanish Euro CCP Buy Sell Back Bonds | SA_BSB_SPGB* | ESDBL | ||
| Delisting of BrokerTec Buy-Sell-Back (BSB) LCH SA Cleared GC Baskets for Spanish Collateral on CME Globex | ||||
|---|---|---|---|---|
| PRODUCT NAME | MDP 3.0 Tag 2714- Financial Instrument Full Name | MDP 3.0: TAG 6937-ASSET | ILINK: TAG 55-SYMBOL MDP 3.0 TAG 1151 - SECURITY GROUP | MDP 3.0: TAG 1180-APPLID |
| SPAIN GC SA BSB NO LETRAS SUB 10YR | GC_SA_BSB_SPAIN_SUB_10Y_NO_LTR_LNK | EG10NL | EUBG | 517 |
| SPAIN GC SA BSB | GC_SA_BSB_SPAIN_NO_LINKERS | EGCSA | ||
| SPAIN GC SA BSB SUB 10YR | GC_SA_BSB_SPAIN_SUB_10YR_NO_LINKERS | EGSA10 | ||
| SPAIN GC SA BSB SUB 20YR | GC_SA_BSB_SPAIN_SUB_20YR_NO_LINKERS | EGSA20 | ||
| SPAIN GC SA BSB LETRAS ONLY | GC_SA_BSB_SPAIN_LETRAS_ONLY | EGSALE | ||
| SPAIN GC SA BSB INCL LINKERS | GC_SA_BSB_SPAIN_INCL_LINKERS | EGSALI | ||
| SPAIN GC SA BSB NO LETRAS | GC_SA_BSB_SPAIN_NO_LTRA_NO_LNKR | EGSANL | ||
| SPAIN GC SA BSB SUB 15Y LTR LNK | GC_SA_BSB_SPAIN_SUB_15Y_+_LTR_+_LNK | ES15LL | ||
| SPAIN GC SA BSB SUB 20YR NO LETRAS | GC_SA_BSB_SPAIN_SUB_20Y_NO_LTR_LNK | ES20NL | ||
Front-End Clients
BrokerTec Sync Client 5.0 Upgrade - Now Available
The BrokerTec Sync client version 5.0.1 is now available to download on the BrokerTec Support portal. This new client contains security and stability updates.
This is a mandatory upgrade. BrokerTec Sync clients utilizing versions prior to 5.0.1 will not be able to log in after Friday, May 30.
Network Requirements
As our services migrate to Google Cloud, this new client version requires access to the following URLs over the public Internet from the BrokerTec Sync user’s workstation:
| BrokerTec Sync Portal | |
|---|---|
| Current URLs (Clients version 3.x/4.x) | New URLs (Client version 5.0+) |
| https://sync.brokertec.com https://paging.numecentcloud.com |
https://markets.api.cmegroup.com/brokertec/sync-portal https://paging.numecentcloud.com (no change) |
Installation Requirements
Please note that customers upgrading from a previous version of the BrokerTec Sync client will be prompted to reboot their workstation during the upgrade process. To minimize disruption, we strongly encourage customer support teams to schedule this upgrade at an appropriate time.
Any client inquiries for technical issues or Production support should be directed to the CME Group Global Command Center (GCC) in the U.S. +1 800 438 8616, in Europe at +44 20 7623 4747 or in Asia at +65 6532 5010.
Client Migration to New URL for BrokerTec Preferences Server - May 19
On Monday, May 19, the BrokerTec Preferences Server, used by BrokerTec Global Front End (GFE) clients to store user preferences and application logs, will migrate to Google Cloud.
By May 19, clients must enable the new URL to be accessed from the traders' workstations over the Internet.
| BrokerTec Preferences Server | |
|---|---|
| Current URL | New URL |
| https://www.btec.com | https://markets.api.cmegroup.com/brokertec/preferences/ |
Any client inquiries for technical issues or production support should be directed to the CME Group Global Command Center (GCC) in the U.S. +1 800 438 8616, in Europe at +44 20 7623 4747 or in Asia at +65 6532 5010.
Post-Trade
CME GC Allocator API Migration to Google Cloud - Now Available
The CME GC Allocator API is now available in Google Cloud.
Details on CME GC Allocator API hosted on Google Cloud are below:
| GC Allocator API Endpoints | ||
|---|---|---|
| Environment | Current URL / IP | Google Cloud URL / IP |
| Production (via Internet) | https://api.gcallocator.cmegroup.com/ 205.209.196.176 | https://posttrade.api.cmegroup.com/gca/v2 208.112.128.6 |
| New Release (via Internet) | https://api.gcallocator-nr.cmegroup.com/ 164.74.123.38 | https://posttrade.api.uat.cmegroup.com/gca/v2 208.112.192.6 |
Customers are strongly encouraged to access the CME GC Allocator API over the Internet to leverage Google Cloud automated failover capabilities. Customers requiring access to the CME GC Allocator API over dedicated connectivity can find the required information in the Client Systems Wiki.
GET requests with ‘content-type’ header set to ‘application/json’ will be rejected with a 400 return code when connecting to theCME GC Allocator API - hosted by Google Cloud. To avoid this issue, please remove the ‘content-type’ header from all GET requests targeting the CME GC Allocator API endpoints.
Clients can continue to use their existing OAuth API IDs to access the CME GC Allocator API in Google Cloud.
The current URLs for CME GC Allocator API endpoints will be decommissioned in Q2 2025.
CME STP FIXML on Google Cloud - March 31
Effective Monday, March 31, all client systems must complete a mandatory certification of regional switch processing for CME STP FIXML on Google Cloud.
This certification is not a prerequisite for clients migrating to CME STP FIXML on Google Cloud.
View the client impact assessment for additional information.
CME STP FIX API on Google Cloud - Postponed
Previously announced availability of CME STP FIX API service on Google Cloud has been postponed. A new production date will be announced in a future article.
View the client impact assessment for additional information.
CME STP FIX API on Google Cloud is currenlty available in New Release.
