Project Readiness

There is no determination of the old/new method on customer level needed. FIXML outgoing messages will contain all instrument group information to support both definitions, at least until the old date definition will be supported or is sufficient to identify a contract uniquely. For inbound messages from customers, C7 system has logic to support both definitions as long as the input is sufficient to identify a uniquely contract. Details of this logic are described in FIXML-documentation.

The contract date is used as a key field to identify a uniquely contract, whereas the expiration date is a non-key. Both fields exist in parallel. Dates can be identical for both fields, but can differ for some contracts. Examples are STIR futures (SARON) and some MSCI futures. 

One can either use the functional key fields which are ProdId, Contract Date, Strike, Version No, Call/Put indicator, Settlement method, Exercise style and Contract Type or make use of the numerical non-key field Contract ID.

 Yes, flex contracts will continue to be available. 

Contract ID is a numerical ID that define a uniquely contract as well, but not defined by Eurex as a key fields. The following fields are defined as key fields: ProdId, Contract Date, Strike, Version No, Call/Put indicator, Settlement method, Exercise style, and Contract Type.

The sub-monthly contract follows the rules for a standard contract creation based on product settings. Specially, settlement method and exercise style remain the same for all standard contract within a product. Here flexible contracts can differ from a standard contract. Not all products offer flexible contracts for trading.

There are no plans to introduce additional monthly or weekly maturities for the benchmark future. 
Possible monthly or weekly maturities would only be considered based on market demand.

Last trading day equals the contract date.

The contract date is used as a key field to identify a uniquely contract, whereas the expiration date is a non-key. Both fields exist in parallel. Dates can be identical for both fields, but can differ for some contracts. Examples are STIR futures (SARON) and some MSCI futures.

One can either use the functional key fields which are ProdId, Contract Date, Strike, Version No, Call/Put indicator, Settlement method, Exercise style and Contract Type or make use of the numerical non-key field Contract Id. 

No, tick sizes will not change for the existing contracts. Additionally, there will not be such a thing as multiple tick sizes for one contract.

KOSPI has a different mechanism, the products don't have daily expiries but rather daily delivery cycles. There won't be a change in KOSPI products.

New expiries for futures FI are not in scope.

Currently, there are no plays for daily OESX options or daily options in general.

Each derivative product must be assigned to a partition, and all instruments belonging to that product are assigned to the same partition. Currently, it is not planned to introduce new 
partitions. 

Currently, there are no plans to include the ISIN in the new contract identification. Rather, this information can be found using XXXXXXXXX. 

Each contract is characterized by a contract date complementing the already existing expiration date. This also applies to daily expiring futures contracts. Contracts will be displayed on the T7 Trader GUI depending on the contract display instruction. For daily expiring futures contracts, the contract display instruction will be chosen as “relative contract day” meaning that contract created by a daily expiration cycle are indicated with contract date 

• “TODAY” (or “T0”) expiring on the current business day 
• “TODAY+1” (or “T1”) expiring on the next business day 
• “TODAY+2” (or “T2”) expiring on the next business day after next business day 

On the next business day, the daily expiring contract indicated by “TODAY” was indicated by “TODAY+1” the business day before, and the daily expiring contract indicated by “TODAY+1” was indicated by “TODAY+2” the business day before. Assuming that the daily expiring contracts have a lifetime of 3 business days, the contract indicated by “TODAY+2” is newly created on that business day. However, each of the daily expiring contract has a fixed contract and expiration date but it is not displayed because of the chosen contract display instruction. 

The numerical contract ID concept is used in the same way as the already existing numerical T7 instrument ID concept. It is uniquely mapped to a specific contract / instrument. After its expiration, the corresponding contract ID is consumed and not re-used anymore.