What is our primary use case?
My use case for Temenos Transact as a program manager from the partner side involves clearing the exams, including the TIM Implementation Methodology, for which I am certified. I work as a program manager in their projects and have rolled out full-scale implementation projects which include Temenos Transact, Infinity, Temenos Payment Hub, and TDH. I am also rolling out another project of the technical upgrade from R10 to R24.
What is most valuable?
The best features of Temenos Transact that I find valuable are its extreme configurability and comprehensive nature.
The open API capabilities of Temenos Transact allow it to be connected with external systems through the APIs, including Iris APIs and microservices APIs.
I have utilized the advanced analytics feature in Temenos Transact in my previous implementation, which was previously unnamed but is now called Outbox.
What needs improvement?
Areas of improvement for Temenos Transact include the GUI which needs further enhancement, as users are still using Classic instead of the UXP Explorer because the UXP is not optimized from a performance and responsiveness perspective.
Temenos Transact needs to be more optimized for other devices, as the Transact Explorer is not performing adequately over the web, causing users to revert to the older version of Temenos Transact.
For how long have I used the solution?
I have approximately three years of experience with Temenos Transact.
What was my experience with deployment of the solution?
There were issues with the microservices between Temenos Transact through DES and Infinity not communicating properly with each other, and they were not properly developed at that time.
What do I think about the stability of the solution?
I believe Temenos Transact is a stable solution.
What do I think about the scalability of the solution?
In my opinion, Temenos Transact is a scalable solution, but its scalability depends on having sufficient hardware behind it, whether in the form of cloud or purely on-premises implementation.
How are customer service and support?
I would rate customer service from Temenos as good, but it depends on whether the contract is tier one, tier two, or tier three and what type of contract Temenos has with the customer itself.
How would you rate customer service and support?
What was our ROI?
I have seen a return on investment for Temenos Transact. However, there are challenges when it is hosted over Azure cloud. If Microsoft experiences problems, Temenos cannot intervene. We encountered this issue in a previous implementation in the Middle East, where the disaster recovery center had no capacity due to Microsoft's limitations. This caused significant concern from the customer about the solution, especially since the standard practice requires the disaster recovery to be at least 50 kilometers outside of the production server.
Additionally, the microservices for smaller customers are not optimized and become difficult to manage. Microservices are most effective when implemented for very large customers with extensive databases, suggesting a monolithic approach would be more suitable for smaller implementations.
What other advice do I have?
The microservices for smaller customers are not optimized and become difficult for customers to manage. Microservices work best when implemented for very large customers with extensive databases, so it should be monolithic instead of microservices.
My clients for Temenos Transact are usually those that have a very small customer base, such as banks with around 5,000 customers, but even then, we were rolling out both digital and Temenos Transact.
The rating depends on how large the customer is and their ability to escalate at the highest level of Temenos. Under optimal conditions, it can achieve a ten out of ten rating.
I rate Temenos Transact as among the top two solutions in the banking domain, being a very significant player alongside Finastra. I have given it a rating of 9 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?