Friday, June 15, 2007

About the Name...

I suppose I ought to explain some of the background to the name of my blog.

Nailing Jelly to a tree

First of all we can get the Geography a Language bits out of the way.
Jelly in this instance is take to be the English form, that the Americans call Jello and the Germans refer to as Wakkelpuding.
The idea is that this blog provides me with a vehicle that allows me to describe intellectual thought processes which on in the initial instance sound somewhat trivial. Like nailing jelly to a tree. Jelly in the English tradition has a somewhat interesting viscosity problem. When you apply sufficient wobble force to it, it tends to sheer and split.
Nails are traditionally applied with a hammer. This introduces forces and shocks to the shaft of the nail driving it into the tree. Unfortunately, these same forces and shocks will cause the Jelly to split.
This then introduces some intellectual thought processes around how to get the nail into the tree whilst still maintaining sufficient adhesion on the Jelly.

My intention is that this blog will provide me with the means to discuss similarly simple sounding projects that on closer inspection are a lot more complicated than they at first seem. Given that I work in and around the area of Investment Banking, quite a lot of these thought processes will in some way be related to the processes and developments that happen in that environment.

How do you spell MiFID?

I should possibly start off by explaining that I work for a German consulting company. Over the past two years I have been tracking the (lack of) progress towards the implementation of MiFID here in Germany.
The German financial markets are exceptionally conservative, it takes them a few years of sitting back and looking at what the rest of the world does before they even think about adopting new business practices here in Germany. In the specific instance of MiFID, I think that this aversion to change is going to hurt. Let me explain...

During this year I have been to visit a number (most) of the financial institutions who are based in Germany and do not conduct their investment banking activities from somewhere outside of Germany. The approach to MiFID is common to all of them and goes a bit like this.

We are a German Bank, with German customers, who are interested in German financial products. Our experience here in Germany over the past xxx years is that the (pick a regional exchange) has provided the "Best-Execution" for our customers we will therefore continue to send all of our orders to that exchange. It will clearly take some time to establish if any other possible venue is able to offer "Better-Execution" on a regular basis. We will be conducting a review of our Execution Policy in Late 2008 but do not expect that things will change.
Oh, OK so Best-Execution seems not to be an issue then. The various German Exchanges not only offer the best result today but are expected to do so for the foreseeable future.

The way that they plan to address Client Classification is even more interesting. There seems to be two possible approaches to this.

Plan-A: Everyone is a private client. We are a private client institution and see the value that we add is the manner in which we advise and manage our relationships with our customers. We have adopted the global German response to Best-Execution (see above) and do not see that we need to do anything other than the most minimal of changes to the manner in which we deal with our customers.

Plan-B: Everyone is a Qualified Counterparty. We are a huge big investment bank that deals exclusively with professional management and finance executives within or base of corporate customers. Our clients fully understand the implications of their trading decisions. We did read somewhere that the client has the right to opt out of this classification for certain classes of instrument. Quite frankly, if they do not feel sufficiently confident in understanding the structure of Synthetic Collateralised Debt Obligations, and really wanted us to change their classification to Professional or Private Client, then we think it would be best to do this for all instrument classes. Clearly this is not a trivial change and it would take a few months to process all of the paperwork, conduct all of the tests and downgrade their status. We think that when we advise them of the complications that this would cause them, they would see reason and continue to be classified as Qualified Counterparties.
The trick seems to be that MiFID is just another reporting obligation and we need to make certain that we do the absolute minimum to ensure that we comply.

Even more entertaining is a brief look at the Landesbanken and Sparkassen who will be building their own Germanic version of what sounds like project boat in order to meet their Pre and Post trade reporting requirements. Expect this to be built in the throbbing financial metropolis of Köln, using the skills and experience of those nice people from IBM. Big-Blue-M-Q.

I don't normally do financial advice or stock picking but in this instance might I be so bold as to suggest any of the more obvious short strategies?

MiFID did anyone notice yet.

OK, so I am assuming that people reading this know what the Markets in Financial Instruments Directive (MiFID) is. Looking on Google is only going to make things more confusing for you, so if you don't have a clue, just walk away now. Nothing is happening here, move along there.


For those of you who decided to keep reading, this particular post is not really about MiFID directly, it has more to do with the possible after effects of MiFID and what people in the financial services industry might want to start thinking about when they come to do their budgets for next year.

The Boat Project is an exceptionally serious attempt to provide a reporting platform for Pre and Post trade reporting requirements under MiFID. ABN-Amro, Citibank, Credit Susise, Deutsche Bank, Goldman Sachs, HSBC, Merrill Lynch, Morgan Stanley, UBS, Barclays Capital, BNP, DKIB, JP-Morgan and RBS is a suitably heavyweight collection of players. I can imagine that they will manage to produce some suitably large collections of data for the markets to consume and analyse.
Whilst not all of these people are directly involved in Turquoise, I can easily imagine that all of these people will be using the Turquoise platform as a means to generate a lot more tick and quote information for the markets.
We will need to wait and see what kind of a role the Equiduct and Instinet alternatives will offer. There will however be a marketing requirement for all of the new Multilateral Trading Facilities (MTF's) in a post MiFID world. They will need to show the depths of liquidity that their particular facility is able to offer. An easy way to do this is to publish the Tick & Quote data for your particular platfrom.
Obviously, if you want the sub-millisecond latency for your clever little Algo-Trading box, then you will need to pay the overhead that is normally associated with very low latency tick data. If on the other hand you are happy to see 0.5 to 3 second latency, then you might just find that this is a very cheap data source. If you can afford to wait until just after the markets have closed, you might even find that this data is provided "at cost".
Hopefully, you have at this point managed to catch up with the theme here. In 2008 we will be seeing a massive growth in the quantity of tick and quote information and a reduction in the costs associated with the provision of this data.

Being able to aggregate all of these different sources might make sense for reasons other than MiFID.
Most of the Risk Management, Risk Analysis and Risk Reporting applications used in the financial markets (for exchange traded instruments) are based on a snapshot, end of day aggregate data set that tells us the High, Low, Open and Close for a given instrument. This is a somewhat simplistic view but it is based on an assumption that the current data collections are incomplete. Depending on which analyst, report or study you have been reading lately, the London Stock Exchange accounts for just under half the total volume of trades done in London each day. The rest of the trades are done on the phone in the over the counter markets that we sometimes refer to as Dark Liquidity. It makes no sense to look at anything more than HLOC when half the possible data is not available. In a Post-MiFID world, where the light of transparency is shone on the dark liquidity, most of this information will suddenly be available. Looking at HLOC will seem a little simplistic.
It will begin to make sense to have some sensible form of aggregation.
The European exchange based markets currently produce something in the order of 600,000 ticks per second. The 27th of February 2007 was a record for most markets and this number jumped to periods of 800,000 ticks per second. So we can expect to have to deal with 1,200,000 to 1,800,000 ticks per second. In a 9-hour day this would be 16,200,000 on a busy day. That is 81,000,000 in a week, or 324,000,000 in a month and 3,888,000,000 for the year. This looks like it might be a big problem. Those are just the ticks for the underlying instruments. If we add the assorted collections of indexes to this, we can quickly get to a point where we are talking about truly vast time series. This is a field where every tiny little detail is no longer trivial.
It is a bit like nailing jelly to a tree, which is the title of my blog, so lets carry on here.

Analysis of the various different market segments shows that there is not common format for the tick and quote information. It is possible to standardise the format of equity information from each of the current 44 exchanges in Europe. Money Markets, Bonds, Repos, Options and Futures all have different quote conventions and it makes no sense to try to aggregate or massage them into a common format. Initial analysis suggest that there are seven basic forms of quote convention. So I need to have a minimum of seven tables and a total capacity of some 4-Billion rows per year. In a simple snapshot view of static price information it should be possible to model this with just about any of the basic database applications. But we are not talking about a snapshot. We are talking about a truly vast time series with quasi-realtime updates of anything upwards of 1,200,000 updates per second. Some of the bigger database vendors out there are able to sustain these types of loading, just so long as nobody wants to ask us any questions whilst we are busy pumping the constant stream of updates into the system.
Fortunately, there is ONE platform that can cope with the size, the rate of update and the collections of complex queries that users might want to ask. For some years now the nice people at Sybase have been selling something called Sybase-IQ. This is a product that has matured to a point where it is now the right product at the right time in the right market.

Truly Vast Time Series seem to have been designed specifically to take advantage of Sybase-IQ (or was it the other way round?)
As expected, the leading database vendor in the financial markets has not been sitting around waiting for users to realise what a super product this was. For instances where you want something a bit more complex than a big clever bucket, the people at Sybase have put together a collection of interesting Sybase technology that they are calling the Real-Time Analytics Platform (RAP).
At this point I need to point out that I have provided some input to the design of this solution. I am a little biased (actually more than a little biased) but the proof is as they say in the pudding. For anyone that was seriously interested I would be more than happy to arrange a little race where we show just how fast this particular solution is. It should be possible for those people who really are interesting in doing this to find my real-world credentials.

We think that we have a really sensible aggregation platform and would welcome the opportunity to benchmark it with real data. Is anyone up for the challenge?

Are there any risk management professionals who can see the benefit of having access to such a collection of time-series information?

Do we have any interest from the current collection of traditional data vendors who would be interested in being able to apply this solution to their current collections of data?

Perhaps you are an existing exchange that sees the need to be able to offer enhanced data services as a means to offset the reductions in transaction costs the MiFID will bring.

Or, perhaps you are one of the proposed new MTF platforms that sees the merit of being able to offer value added data services based on a rather sensible data aggregation platform.