We had just our folks work on it. We had to send a few people to get trained and then do it in-house. We had two people in London and two in New York with enough knowledge and skills. They were people from market links team, who were looking after our client connectivity and the setting up of cross-connects and the like. They were the people involved in setting up this device and adding networking TAPs to get the device up and running.

Implemented via a mixture of Corvil themselves and in-house. Corvil team was excellent.

The upgrade was very complicated. We had a high dependency on the vendor to assist us with the configuration. It was not easy to configure.

The configuration has a dependency on different message protocols, from an exchange perspective. Also, internally, it needs a lot of bespoke configuration around different languages that we use internally for our systems to communicate. You can't just get the product out-of-the-box and plug it in. There's a lot of configuration work, which had to be done exchange by exchange and client by client. That process took a very long time.

For our upgrade implementation strategy, we prioritized venues and clients. We relied on the vendor a lot to give us time to assist us with the upgrade. I think Corvil probably spent a significant number of man-days (probably a 100 man-days) on this. That amount of time was not necessarily factored into the contract, so they did a lot of pro-bono work for us.

Our experience with them was good. The people are very strong technically and technically aware. They have a strong understanding of their product. We have a good relationship with them. We would like not to depend on them so much. However, part of the reason that we have to depend on them so much is due to the complexity of the product.

For deployment and maintenance, there are probably two to three people from our side, and one to two people from the Corvil side. On our side, there are probably one or two people from a production management perspective, who are actually undertaking the configuration. In addition, there will probably be someone from specialized infrastructure, like a network engineer involved, who would help facilitate things like firewall changes and open up the right ports.

We used our own network deployment team, who handles these type of equipment rollouts. It required two network development engineers.