proposal for algo brokers

, ,
1

Imported from previous forum

2

[ original email was from John Greenan - john.greenan@alignment-systems.com ]
A simple proposal for all brokers offering Algo products…

Along with all of the sniper/covert/guerilla and so on, why not add in two new ones “Care/Desk/Broker” and “DMA”. That way if a staging platform is used any order routed incorrectly can be routed back to a DMA connection or desk without having to cancel releases and so on.

Not too hard to implement but would make the lives of several folks on the buy-side just a little bit easier.

3

Along with all of the sniper/covert/guerilla and so on, why not add in
two new ones “Care/Desk/Broker” and “DMA”. That way if a staging
platform is used any order routed incorrectly can be routed back to a
DMA connection or desk without having to cancel releases and so on.

Sorry, maybe I misread your message. With regards to incorrect routing from staging to production, it should already covered by tag 464 in the logon message.

If you are talking about something else, could you expand a bit on what you mean?

thanks
Steve Cook
http://www.affine.hk

4

[ original email was from John Greenan - john.greenan@alignment-systems.com ]
Assume that the buy-side dealer has an OMS and a staging system. Imagine say using Charles River or LatentZero and then a staging system such as UL Reach.

After the user has established a session with a staging system the user may incorrectly send an order that should be DMA to the staging system. If the staging system has an algo called “DMA” then the user can send the order on from the staging system without having to cancel and resend from the OMS.

Just a simple way to improve usability.

Sorry, maybe I misread your message. With regards to incorrect routing
from staging to production, it should already covered by tag 464 in the logon message.

If you are talking about something else, could you expand a bit on
what you mean?

thanks Steve Cook http://www.affine.hk