1 / 22

XTP Changes in 2.57

This update includes transaction and data changes, overview of price checks and circuit breakers, reference prices, revised validation of price checks, mid-price matching, and trade action and cancellation of trade report external.

michellewwilliams
Download Presentation

XTP Changes in 2.57

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XTP Changes in 2.57 SAXESS 5.0.0 Speaker Sebastian.Tomac@omxgroup.com Title XTP Changes in 2.57 Version 1.0

  2. Areas • Transaction and data changes • Overview Price Checks and Circuit Breakers • Reference Prices • Circuit Breakers • Revised validation of Price Checks • Mid-price matching • Trade Action and Cancellation of Trade Report External • Deferred trades in Average Price • Turnover List Structure Revision • Trade id • Other data – Certified Advisor • Documentation

  3. Price Checks Price Circuit Breaker RefPrice Circuit Breaker Last Paid Last paid Circuit Breaker Last Paid 2% 10% Circuit Breaker RefPrice 15% Price Checks Time

  4. Reference Prices Why: • The reference price is used by both Price Checks and Circuit Breakers. Design/Implementation: • The TID_MC_OrderbookRefprices contains the Reference price. • The Price check/circuit breaker price update method is mandatory – Last Paid or explicitly disseminated FID_MC_OrderbookRefprices.

  5. Revised validation of Price Checks Why: • Price checks of orders with last paid as reference price • Price checks of orders with relative price updates. Design/Implementation: • The price checks have been moved to the central system. Hence an order that i rejected due to a price check result in a TID_UC_ErrorMsg. • Intraday changed limits are disseminated in TID_MC_OrderbookRefPrices/FID_OrderbookPriceChecks. • TID_MC_OrderbookRefPrices/FID_BaseDataChg/Operation code indicates intraday insert/update/delete of a orderbook price check.

  6. Circuit Breakers (1) • Why: • Circuit breakers are automatic measures for trading suspension in the event of unwanted market volatility. A circuit breaker initializes a call auction for the security in question, facilitating price discovery in preparation for trading resumption. Design/Implementation:

  7. Circuit Breakers (2)Price update method Reference Price • Based on a Reference price • Reference Price: - equilibrium price from last call auction - a call auction can be the morning call auction, a call auction that occurs during the continuous trading or an evening call auction - if no equilibrium price was formed in the morning call auction, the previous day’s closing price will be used as a reference price • Breach of a static circuit breaker will lead to a trading interruption and a call auction where a new equilibrium price will be formed

  8. Circuit Breakers (3)Price update method Last Paid • As a reference price the last paid price will be used • Active only during continuous trading • Breach will lead to a trading interruption and call auction, where a new reference price for the static circuit breaker will be formed

  9. Circuit Breakers (4) Design/Implementation: • TID_QrySubMarketFID_SubmarketCircuitBreaker contains the submarket circuit breaker limits. One FID per Circuit breaker price update method. • FID_MC_OrderbookCircuitBreaker contains intraday changes of the orderbook circuit breaker limits. • The Circuit breaker price update method what price is used as reference – Last Paid (FID_MC_Trade/updates last paid) or as explicitly disseminated FID_MC_OrderbookRefprices. • More than one circuit breaker may be active during continues trading.

  10. Circuit Breakers (5) Design/Implementation: • A Circuit breaker call is indicated by Call purpose CircuitBreaker. • Orders deleted due to a circuit breaker will have Order delete reason circuit breaker.

  11. Mid-price matching (1) • Continuous Midprice matching – each trade in the Midprice orderbook will be executed at the round lot spread Midprice in the order book • Midprice matching possible also at scheduled occasions (Auctions) – a submarket event will trigger matching • Midprice is (best bid + best ask)/2 • Midprice orders are fully anonymous & hidden (cannot be seen by other trading participants) • Midprice order criteria's • Match multiple = Midprice lot size • Total volume = multiple of the Midprice lot size • Midprice spread • Percentage from the bid side price

  12. Mid-price matching (2) Design/Implementation: • FID_AnsSubMarket and FID_AnsOrderbook contains; • Midprice matching • Maximum midprice spread. • FID_AnsOrderbook contains; • Midprice auction • Midprice allotment • FID_MC_SubMktEvent Submarket event type indicates a scheduled mid-price matching.

  13. Cancellation of Trade Report External • Why: • Enable cancellation of trade report external Design/Implementation: • External trade report maybe cancelled with TID_TradeReportExternalCancel. Upon cancellation a TID_UC_TradeReportExternalCancel is sent. Originator indicates by user or system. • Timestamp, trade report is used as key.

  14. Trade Action Why: • Generic XTP transactions for operating on Trades. Design/Implementation: • The TID_ExternalTradeCancel has been replaced by TID_TradeAction with Trade action code “Cancel trade”.

  15. Deferred trades in Average Price Why: • At the time of trade the trade information is not available on the multicast flow for deferred trades. Information systems that provide real time calculation of the average price needs the Trade price at the time of trade. Design/Implementation: • TID_MC_AveragePrice is disseminated whenever a trade notification is sent for a trade that updated average price is created or cancelled. Only sent to information systems.

  16. Turnover List Structure Revision Why: • A turnover list heading may to belong to several lists. Design/Implementation: • TID_QryTurnoverListHeading for two different lists may yield responses with duplicate Turnover list id.

  17. Trade Id (1) Why: • Provide protocol wide unique Trade identifier. Design/Implementation: • TradeId is a system unique Trade identifier • TradeId is unique over several trading days. • TradeId is a valid Clearing Reference for the Trade.

  18. Trade Id (2) • Old way (still valid) • TradeNo unique per trading day. • Used to identify a published Trade • TradeNotificationNo unique until trade publication. • Used to identify a deferred not yet published Trade • To identify for a Trade over several trading days a key has to be constructed by combining OrderbookId, Time and TradeNo.

  19. Other data Design/Implementation: • TID_QryOrderbooks/FID_AnsOrderbook • Certified advisor. • TID_QryInstrument/FID_Bonds • Yearly Coupon Frequency • First Installment Date • TID_QryTrades and TID_UC_Trade • user name

  20. Documentation • XTP chapter reorganization. • Appendix Trade Reporting Flow has been updated with TID_TradeReportExternal and TID_TradeReportExternalCancel example. • XTP specification available as XML Schema.

  21. Questions? Sebastian.tomac@omxgroup.com • Help us get better… • What are you missing in the protocol? • How may we improve the support? • What are unclear in the documentation?

More Related