Account holders are encouraged to routinely monitor their order submissions with the objective of optimizing efficiency and minimizing 'wasted' or non-executed orders. As inefficient orders have the potential to consume a disproportionate amount of system resources. IB measures the effectiveness of client orders through the Order Efficiency Ratio (OER). This ratio compares aggregate daily order activity relative to that portion of activity which results in an execution and is determined as follows:
OER = (Order Submissions + Order Revisions + Order Cancellations) / (Executed Orders + 1)
Outlined below is a list of considerations which can assist with optimizing (reducing) one's OER:
1. Cancellation of Day Orders - strategies which use 'Day' as the Time in Force setting and are restricted to Regular Trading Hours should not initiate order cancellations after 16:00 ET, but rather rely upon IB processes which automatically act to cancel such orders. While the client initiated cancellation request which serve to increase the OER, IB's cancellation will not.
2. Modification vs. Cancellation - logic which acts to cancel and subsequently replace orders should be substituted with logic which simply modifies the existing orders. This will serve to reduce the process from two order actions to a single order action, thereby improving the OER.
3. Conditional Orders - when utilizing strategies which involve the pricing of one product relative to another, consideration should be given to minimizing unnecessary price and quantity order modifications. As an example, an order modification based upon a price change should only be triggered if the prior price is no longer competitive and the new suggested price is competitive.
4. Meaningful Revisions – logic which serves to modify existing orders without substantially increasing the likelihood of the modified order interacting with the NBBO should be avoided. An example of this would be the modification of a buy order from $30.50 to $30.55 on a stock having a bid-ask of $31.25 - $31.26.
5. RTH Orders – logic which modifies orders set to execute solely during Regular Trading Hours based upon price changes taking place outside those hours should be optimized to only make such modifications during or just prior to the time at which the orders are activated.
6. Order Stacking - Any strategy that incorporates and transmits the stacking of orders on the same side of a particular underlying should minimize transmitting those that are not immediately marketable until the orders which have a greater likelihood of interacting with the NBBO have executed.
7. Use of IB Order Types - as the revision logic embedded within IB-supported order types is not considered an order action for the purposes of the OER, consideration should be given to using IB order types, whenever practical, as opposed to replicating such logic within the client order management logic. Logic which is commonly initiated by clients and whose behavior can be readily replicated by IB order types include: the dynamic management of orders expressed in terms of an options implied volatility (Volatility Orders), orders to set a stop price at a fixed amount relative to the market price (Trailing Stop Orders), and orders designed to automatically maintain a limit price relative to the NBBO (Pegged-to-Market Orders).
The above is not intended to be an exhaustive list of steps for optimizing one's orders but rather those which address the most frequently observed inefficiencies in client order management logic, are relatively simple to implement and which provide the opportunity for substantive and enduring improvements. For further information or questions, please contact the Customer Service Technical Assistance Center.
BACKGROUND
INTRODUCTION
US
|
Canadian
|
Equity
|
Equity (short cycle, regular full cycle and long term)
|
Index
|
Index
|
Yield Based
|
Foreign Currency
|
Short Dated
|
|
Flex
|
|
5-character Code
|
21-character OSI Identifier*
|
OSI Data Elements (minimum field size)
|
||||||
Option Root
Symbol [6]* |
Yr
[2] |
Mo
[2] |
Day
[2] |
C/P
[1] |
Dollar
Strike [5] |
Decimal
Strike [3] |
||
SZVXI
|
SPX 111216P01900000
|
SPX
|
11
|
12
|
16
|
P
|
01900
|
000
|
WMFAW
|
MSFT 100116C00047500
|
MSFT
|
10
|
01
|
16
|
C
|
00047
|
500
|
Milestone Date | Action | Issues/Series Impacted | Effective Date |
Friday, March 12, 2010 | Initial group of options representing array of product scenarios to be consolidated (approx 12 classes) | Options associated with a strategic group of underlyings including adjusted and non-standard symbols | Monday, March 15, 2010 |
Saturday, March 20, 2010 | Standard Expiration | ||
Wednesday, March 31, 2010 | Quarterly Expiration | ||
Friday, April 9, 2010 | Consolidation of options whose primary underlying starts with the letters A-C (approx 503 classes) | All options associated with 'A-C' underlyings including adjusted and non-standard symbols | Monday, April 12, 2010 |
Saturday, April 17, 2010 | Standard Expiration | ||
Friday, April 23, 2010 | Consolidation of options whose primary underlying starts with the letters D-I (approx 486 classes) | All options associated with 'D-I' underlyings including adjusted and non-standard symbols | Monday, April 26, 2010 |
Friday, May 7, 2010 | Consolidation of options whose primary underlying starts with the letters J-IR(approx 575 classes) | All options associated with 'J-R' underlyings including adjusted and non-standard symbols | Monday, May 10, 2010 |
Friday, May 14, 2010 | Consolidation of options whose primary underlying starts with the letters S-Z (approx 503 classes) | All options associated with 'S-Z' underlyings including adjusted and non-standard symbols | Monday, May 17, 2010 |