Pressure on CTRM/ETRM systems to find arbitrage
https://www.bobsguide.com/guide/news/2019/Jul/22/pressure-on-ctrmetrm-systems-to-find-arbitrage/
For years commodity traders and risk managers depended on legacy systems, spreadsheets and paper documentation. But with commodity markets becoming more complex and fast-paced, the race for efficiency and greater profit margins is becoming increasingly difficult as systems are having to evolve rapidly to stay competitive.
Commodity trading firms will have to start reviewing their business models as gross trading margins have decreased 20% since 2015, according to an Oliver Wyman report published in March. The need to monitor exposure, risk, and international logistics are key differentiating factors between firms in a high-volume, low-margin market.
In the commodities sector, trade wars, Brexit, and geopolitical events as well as possible changes in regulation are creating great uncertainty in the market. Technology has a challenge to assist firms to navigate through market volatility, risk, and complexity.
Commodity and energy trade risk management (CTRM/ETRM) systems are used by those in commodity markets to manage numerous segments of a trading firm’s front to back and risk activities.
The CTRM/ETRM space has seen consolidation over the past five years, with many vendors -Triple Point Technology, Openlink, Aspect Enterprise Solutions and Allegro - being acquired by ION Investment Group.
Regulatory considerations
Since the financial crisis, an avalanche of regulation has increased the reliance on CTRM/ETRM systems – the European Market Infrastructure Regulation (Emir), the second Markets in Financial Instruments Directive (Mifid II) in Europe, and Dodd-Frank in the US. But changes to these regulations could soon take place.
On May 24, the European Securities and Markets Authority (Esma) launched a call on position limits and position management in commodity derivatives as part of a one year review into the Markets in Financial Instruments Directive (Mifid II).
“Esma notes in particular that according to Article 2(1)(30) of Mifid II, the definition of commodity derivatives includes securitized derivatives. However, the notions of spot month and other months, for which position limits are to be set under Article 57(3) of Mifid II are not relevant for securitized derivatives,” the paper stated.
“The concept of open interest does not apply either to those instruments in a straightforward manner and Esma had to find a meaningful approach to position limits in securitized derivatives in Article 15 pf RTS 21,” it continued.
On July 5, Esma published responses to the call for evidence which revealed a potential need for an update to the regulation.
The European Federation of Energy Traders (EFET) said in response to the paper that “the introduction of position limits has increased uncertainty in commodity derivative markets and occasionally discouraged market participants from entering into positions.”
“The lack of clear rules regarding calculation methodologies and the possibility of unexpected changes to the rules increases the risks for market participants and may reduce liquidity or move liquidity to non-EU trading venues,” the response continued.
In the US, the Commodity Futures Trading Commission (CFTC) has yet to complete rules on speculative position limits in agriculture, energy, and metals commodities. The regulator was charged by the US Congress under Dodd-Frank to establish certain position limits within six to nine months back in 2010.
On June 11, Commissioner Berkovitz told the FIA’s inaugural commodities symposium finalizing the rules is “one of the important pieces of unfinished business before us. I hope that we will complete it soon.”
“The question before the Commission is whether, based on our collective experience and knowledge about the markets we regulate, an exceedingly large speculative position has the potential to distort markets, impede price discovery, or facilitate manipulative schemes. The Commission has asked and answered this question before. The record before us demonstrates that the answer is “yes.”
As regulatory considerations around position limits both in the US and EU continue to be discussed having a CTRM/ETRM systems ready to deal with potential changes in regulation will be of increasing importance.
Emerging technologies
With this increasing complexity trading firms are looking to get more out of their CTRM/ETRM systems while limiting the impact on budgetary spending. The use of real-time data and analysis, cloud services, and artificial intelligence (AI) are key to advancing are fast becoming key to staying ahead of the competition.
There has been an increase in the adoption of artificial intelligence (AI) into CTRM systems with firms looking to implement the technology throughout the trading lifecycle, from pre-deal analytics to settlement. According to a report published by Ernest and Young (EY) in December 2018, 11% of vendor solutions said they had artificial capabilities.
The emergence of blockchain-enabled smart contracts is also gaining momentum. The ability to streamline reconciliation securely through an encrypted digital ledger is changing the traditional paper trail process. Replacing firms’ separate databases with a shared ledger of record, the technology has been described by EY as a game changer for the industry.
Also becoming of interest in the commodities and energy trading sector is the use of Robotic Process Automation (RPA). RPA is the use of robots which are introduced into existing software to perform repetitive and simple clerical activities. Although still in its infancy of adoption, RPA has a potential number of use cases such as: data submission, entry of compliance forms, and purchase order issuance, which is expected to reduce errors across the large volume of information proceed in commodity and energy trading operations.
In August 2018, a survey from FIS and the Commodity Technology Advisory reported that 75% of respondents said the cloud technology for commodities trading was seeing the greatest amount of investment and was the area most likely to see investment in the next 12-24 months.
In June 2018, ION said it had seen a 250% increase in cloud engagements across its CTRM/ETRM solutions. As with many other parts of finance cloud technology is growing in adoption as firms attempt to reduce costs while also limiting spend on infrastructure builds. Part of key considerations is the potential for scalability.
With rising amounts of data available and increased progress in the development of artificial intelligence and machine learning, new operational opportunities are beginning to present themselves. Crucial to the implementation of AI is efficient data storage and structuring and as algorithmic trading is beginning to take off in the commodities markets, a move from spreadsheets and legacy software to faster systems is required.
While an increase of data can come with numerous opportunities it also presents a challenge for firms to have processes in place to fully optimize the data. Although the commodity industry has begun to future embrace the benefit of technology adoption, the Oliver Wyman report identified a need by commodity trading firms’ quants and data scientist to work quickly to take advantage of short-lived information strategies. The report suggests main players will go back to their roots and look to gain a competitive advantage by developing operating models to support data analytics as an information advantage to increase profits.
Pressure on CTRM/ETRM systems to find arbitrage的更多相关文章
- 大宗商品交易与风险管理(CTRM)软件产品介绍
https://mp.weixin.qq.com/s/grA8MhryPfDB2PmBqsao4Q 从全球范围来看,大宗商品行业风险管理领域的主流软件产品是CTRM系列.CTRM是Commodity ...
- Disposable microfluidic devices: fabrication, function, and application Gina S. Fiorini and Daniel T
Disposable microfluidic devices: fabrication, function, and application Gina S. Fiorini and Daniel T ...
- Reporting Service 告警"w WARN: Thread pool pressure. Using current thread for a work item"
如果Reporting Service偶尔出现不可访问或访问出错情况,这种情况一般没有做监控的话,很难捕捉到.出现这种问题,最好检查Reporting Service的日志文件. 今天早上就遇到这样一 ...
- Modern Operating Systems(Ⅰ)——2014.12.15
进程 进程模型 进程就是一个正在执行的程序的实例 值得注意的是,若一个程序运行了两遍,则算作两个进程 创建进程 在通用系统中,有四种主要事件导致进程的创建 ①系统的初始化 ②执行了 正在 ...
- LinuxMM--Memory Pressure
Memory pressure定义在操作系统中,用户分配.文件缓存.网卡包缓冲区等等都会消耗内存.一旦出现内存紧张就会导致memory pressure.引发当某个任务需要请求内存时就有可能引发mem ...
- 【转载】Bandits for Recommendation Systems (Part I)
[原文链接:http://engineering.richrelevance.com/bandits-recommendation-systems/.] [本文链接:http://www.cnblog ...
- [No00003D]操作系统Operating Systems信号量的代码实现Coding Semaphore &死锁处理Deadlock
操作系统Operating Systems信号量的代码实现Coding Semaphore &死锁处理Deadlock 可以操刀了—从纸上到实际 从Linux 0.11 那里学点东西… 读磁盘 ...
- [No00003C]操作系统Operating Systems进程同步与信号量Processes Synchronization and Semaphore
操作系统Operating Systems进程同步与信号量Processes Synchronization and Semaphore 进程合作:多进程共同完成一个任务 从纸上到实际:生产者− − ...
- [No00003A]操作系统Operating Systems 内核级线程Kernel Threads内核级线程实现Create KernelThreads
开始核心级线程 内核级线程对多核的支持怎么样? 和用户级相比,核心级线程有什么不同? ThreadCreate 是系统调用,内核管理TCB ,内核负责切换线程 如何让切换成型? − − 内核栈,TCB ...
随机推荐
- 第02组 Alpha冲刺(6/6)
队名:無駄無駄 组长博客 作业博客 组员情况 张越洋 过去两天完成了哪些任务 准备"Alpha事后诸葛亮" 提交记录(全组共用) 接下来的计划 完善接口文档 调动组员积极性 还剩下 ...
- SpringBoot集成Spring Security(7)——认证流程
文章目录 一.认证流程 二.多个请求共享认证信息 三.获取用户认证信息 在前面的六章中,介绍了 Spring Security 的基础使用,在继续深入向下的学习前,有必要理解清楚 Spring Sec ...
- SpringBoot集成Spring Security(1)——入门程序
因为项目需要,第一次接触 Spring Security,早就听闻 Spring Security 功能强大但上手困难,学习了几天出入门道,特整理这篇文章希望能让后来者少踩一点坑(本文附带实例程序,请 ...
- 路径规划基础A*算法
1,Dijkstra’s 算法 一种发散性寻找最短路径算法. 由起点开始向四周开始发散,直到碰到目标点为止.这时就是最短路径.优点:能找到与目标点的最短路径:缺点:搜索花费的时间会比较长. 2,Gr ...
- ShellScript之变量
Shell脚本之变量学习 ##########################ShellScript初学者,文章摘自菜鸟教程################################ 1.She ...
- vue-v-xxx基于 Vue拓展的 v-xxx 库
君问归期未有期,巴山夜雨涨秋池. 何当共剪西窗烛,却话巴山夜雨时. 作为vue轻车熟路的老司机,经常会用到一些指令,vue官方提供的指令又太少,无法满足旺盛的欲望,而每次要写一遍,终日郁郁寡欢,从小就 ...
- Python课程第六天作业
1.以自己的理解总结为什么会出现循环导入,并用代码举例说明 循环导入报错并不是应为相互之间引用而导致报错,实际上是在导入一个模块时发现引用的模块不存在 示例如下: m1.py from m2 impo ...
- 人生苦短,我用Python(目录)
目前Django分类的文章正在整顿中,届时将呈现更加丰富的内容,另外整体排版也将会更改,感谢支持!! 一.Python基础 二.并发编程 三.数据库 四.Web 五.Python Web 框架 六.爬 ...
- golang学习笔记 go 相关命令
go build 命令一些可选项的用途和用法 在运行go build命令的时候,默认不会编译目标代码包所依赖的那些代码包.当然,如果被依赖的代码包的归档文件(*.a)不存在,或者源码文件有了变化,那么 ...
- dotnet验证参数
组长提了一个需求,前端传递过来参数的时候,我们要验证一下参数是否都传递过来了,所以我专门写了一个验证工具类,调用就好了. 第一个参数为 前端传递到Controller封装的实体类,第二个参数为这个实体 ...