throbber
DECLARATION OF JAMES J. ZELLINGER
`
`1. James I. Zellinger, declare that:
`
`I am persoually familiar with the facts set forth herein, and, if called as-a witness,
`l.
`[could and would testify thereto of my own personal knowledge.
`I began my career as a
`2.
`I have over 40 years experience in the financial industry.
`runner in the mailro°m at the Chicago Board of Trade working for Merrill Lynch.
`I
`werked in variOus positions at Merrill Lynch for 13-14 years. I left Merrill Lynch to be a
`partner and part-owner in Hennessy & Associates where I was involved in operations and
`sales. Hennessy Was a clearing firm. I worked there for around 13-14 years. During my
`years at Merrill and Hennessy I traded throagh an order desk. When I left Hennessy. I
`traded for a while both from an office and on the floor of the CBO'I‘.
`
`In around 1990, I was doing consulting work on the Globex project for the
`3.
`Chicago MerCantile Exchange (“CME”) when it was first being built. Globex was the
`CME’s electronic trading platform. In 1990-91. I took ajob with the CME to run
`operations for Globex. Iran operations for Globex until 1994.
`In 1994, I returned to
`Merrill Lynch to run the commercial trading office. After working at Merrill for one and
`
`the traders used a variety ofdifferent systems, including the Project A front-end, the
`Globex front-end, Trading Technologies (“TI”) software. EasyScreen software and GL
`software. We also used Espeed software to trade on Espced‘s cash bond market. I was
`also aware ofother front—end systems, including software offered by Patsystems. When I
`left, Transmarket had over 100 traders trading electronically.
`4.
`I first saw TT‘s MD Trader in around the fall of 2000. It became immediately
`apparent that MD Trader was a superior trading tool to the other systems available at the
`time. The reason I know that MD Trader was superior was that the traders insisted they
`have it. We licensed TT's software to get MD Trader despite the fact that it was
`significantly more expensive than the compctiu'on. I recall the CFO of Transmarket at
`
`Page 1 0f3
`
`TRADING TECH EXHIBIT 2046
`
`TD Ameritrade v. Trading Technologies
`
`CBM2014—00133
`
`

`

`because we were having some technical difficulty on our CME cennection and were not
`able to get the TT software up and running quick enough.
`
`At the time, the preexisting screens were not designed for an actiVe trader. MD
`5.
`Trader was the first application designed to be used as a true trading tool by the trader to .
`enhance trading. The preexisting systems were order book type screens that were built so
`that a broker order desk could keep control. of its orders and to limit errors. MD Trader
`was far superior for the active trader because it was fast. It improved the way the trader
`saw the market. This was especially true for spreaders who would put multiple markets '
`up side by side. MD Trader allowed the traders to easily see the movement of the market ‘
`because the market data was displayed dynamically relative to fixed prices on the screen
`so that the data would move up and down on the screen. The preexisting screens
`displayed the best bid and best ask prices in designated locations on the screen (typically
`side by side) such that when the market changed the numbers in these locatiOns changed.
`This required traders to read and mentally interpret changes in numbers to see changes in
`the market. At first, several of our traders demanded that they get MD Trader. Once they
`had it and other traders saw the benefits of MD Trader, it spread like wildfire.
`
`.
`
`In November of 2000, I left Transmarket to join Fuji Futures (a division of Fuji
`6.
`Bank) where I was Executive Vice President of Operations. I was responsible for
`building a local business in Chicago for both floor and electrouic trading. At the time,
`Fuji was providing GL software and exchange provided front-ends to its traders. As part
`of my goal of attracting professional traders to Fuji, I convinCed Fuji to license TT’s
`software in around March or April of 2001. Fuji did this because TT had MD Trader,
`which. was unique at the time to TT. Fuji’s professional trade group chose TT over
`competitors such as RTS, GL, Patsystems and Easyscreen despite the fact that TT’s
`software was more expensive. Fuji became Mizuho Securities in April, 2002 and I
`continued on in the same role until June of 2003.
`I had built the professional trading
`operation up to around 175 traders when I left. Ileft Mizuho to found (along with others)
`Advantage Futures LLC, a clearing firm on the CBOT, CME, LIFFE and Eurex for
`professioaal traders. I am President and COO of Advantage. Advantage currently has
`around 300 traders with approximately 170 focusing on electronic trading. Our primary
`vendor for electronic trading is TT.
`
`In the years following TT’s release of MD Trader, many ISVs have released
`7,
`products that have the same functionality as MD Trader.
`I have been in many meetings
`with representatives of competitive ISVs trying to sell their trading software. Almost all
`of these competitors. if not all, has pitched their product as having a window that “looks
`just like” TT‘s MD Trader and as being cheaper than TT. These competitors needed to
`do this because the MD Trader tool was so important to active traders and provided a
`huge competitive advantage to TT. For example, I have heard these types of pitches from
`reprBSentatives of RTS, Patsystems, GL and Easyscreen.
`
`Around 2 menths ago I met with Steve Brucatol Mr. Brucato is a former
`8.
`employee of TT where he held the position of CTO. Mr. Brucato stated to me that he
`was working to help Espeed develop a new front—end that had similar features to TT’s
`
`Page 2 0f 3
`
`Page 2 of 3
`
`

`

`I also recall him telling me that Espeed might offer its new front—
`product.
`people who were clearing cash bonds through Espced.
`
`end for free to
`
`I declare under penalty of petjury that the foregoing is '1 e an vorrect. Executed on
`August
`"21 ,2004.
`
`
`
`
`Page 3 0f 3
`
`3
`
`Page 3 of 3
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket