Cloud solution provider of the year: Murex

Asia Risk Awards 2021

Anthony Harel
Anthony Harel, Murex

Banks have started to embrace the benefits of cloud technologies, but current regulatory fragmentation, particularly in the Asia-Pacific (Apac) region, means that cloud adoption and implementation remain a challenge.

For example, local regulators are still stringent on data sovereignty in Malaysia and Indonesia, according to Anthony Harel, director of client services technology for Apac at Murex. However, Amazon Web Services and Microsoft Azure have recently opened data centres in Jakarta, which should encourage further migration to the cloud.

While in Japan, thanks to the government’s support of cloud adoption with tax and accounting benefits, the cloud is the go-to option for banks, particularly for total cost of ownership (TCO) optimisation. A large Japanese corporation recently finished a project to lift and shift its MX.3 instance from on-premises data centres to Murex’s software-as-a-service (SaaS) offering powered by AWS.

MX.3 is Murex’s flagship platform, which supports trading, treasury, risk and post-trade operations, helping clients meet regulatory requirements, manage risk and control IT costs.

Despite being at different stages in the cloud journey, Murex finds that clients still look to the cloud to accelerate the pace of change, while maximising the return on their technology investment.

The fragmentation in expectations and constraints that financial institutions in the Apac region face convinced Murex to offer a hybrid solution.

Harel says the functional coverage of MX.3 is 100% ready for the cloud: “Being able to do a standard lift-and-shift of MX.3 to the cloud using a standard IaaS [infrastructure-as-a-service] offering didn’t really require any tweak to the software itself.”

Being able to do a standard lift-and-shift of MX.3 to the cloud using a standard IaaS offering didn’t really require any tweak to the software itself

Anthony Harel, Murex

Instead, the adaption has more to do with reviewing how MX.3 connects to the surrounding systems of the bank, which may still be on-premises, and reviewing the installation’s security to adapt to cloud standards.

Firms dealing with various calculations such as value-at-risk, standardised and internal model approaches, standard initial margin model, stress-testing, and any other market risk figures, often need large infrastructure because such workloads are computer-intensive. Also, the calculations must be completed in a limited timeframe.

Murex proposes a solution that enables the just-in-time provision of cloud resources needed for the risk calculation, meaning that firms only pay for infrastructure when it is used. Harel says cost estimates show that the savings, depending on existing on-premises costs, can exceed 90%.

The firm has built specific tooling via the Murex Continuous Delivery Suite to combine the cloud with the productivity of agile and DevOps (development and operations) principles to handle configuration, automated tests, test data and infrastructure as code.

Using MXpipeline, the Murex configuration builders can automate, creating a brand-new installation of MX.3 on the cloud within minutes.

“Once they have finished their development work, they can switch off this newly created MX.3 instance and stop paying for the infrastructure, thanks to the pay-as-you-go model of the cloud,” says Harel.

With the SaaS offering, Murex takes ownership of all technical tasks required to run MX.3 securely and with maximum availability, so customers can focus on their business.

Murex also proposes a business process-as-a-service (BPaaS) offering. New applications can run on the cloud and connect to a customer MX.3 instance through a native integration layer that transfers the necessary data.

Harel says this ensures a fast time-to-market and optimised TCO for solutions that could otherwise be costly and complex to implement, as they would require heavy investments in infrastructure.

Using this model, Murex takes care of the technical tasks to run the software. It also doesn’t require any installation, administration, configuration, upgrading and integration effort on the customer’s side.

Singapore-headquartered OCBC Bank uses MX.3 across all asset classes for front office, middle office, VAR, initial margin, limit control, back office with confirmation, payments and accounting. The bank is also running MX.3 on a private cloud for test and production usage.

Photo of Frederick Shen
Frederick Shen, OCBC Bank

Frederick Shen, head of business management for global treasury at OCBC Bank, says the bank has now migrated the entire platform to cloud-based technology. One of the benefits of that is enhanced processing and performance capabilities on the platform.

“This is critical for us as we develop increasingly bigger volumes in our business, and with the cloud technology, we were able to actually run with the business … And with that cloud deployment, what we see is enhanced performance – not only on the trading and sales front of the business, but also on the risk management platform,” says Shen.

Pavilion Energy, a subsidiary of Temasek Holdings in Singapore, also uses Murex’s trading platform solution with risk management to support its growing trading activities and long-term growth strategy.

Murex has relationships with cloud vendors AWS and Microsoft Azure, which enables them to propose to customers the tools and best practices that are well adapted to the MX.3 domain and architecture.

Looking ahead, Murex is working on going further with elastic computing, leveraging containers and serverless computing. It also plans to certify additional databases to offer more IaaS options to clients.

  • LinkedIn  
  • Save this article
  • Print this page  

Only users who have a paid subscription or are part of a corporate subscription are able to print or copy content.

To access these options, along with all other subscription benefits, please contact [email protected] or view our subscription options here: http://subscriptions.risk.net/subscribe

You are currently unable to copy this content. Please contact [email protected] to find out more.

You need to sign in to use this feature. If you don’t have a Risk.net account, please register for a trial.

Sign in
You are currently on corporate access.

To use this feature you will need an individual account. If you have one already please sign in.

Sign in.

Alternatively you can request an individual account here: