-
Services
- Consulting Services
-
Support
- Training
- Premium Support
- Support Portal
-
Success Stories
- Aboitiz Power
- Commercial Bank of Africa
- Delware North Companies
- US Coast Guard
-
Featured Resources
- Whitepapers
- Analyst Reports & Product Reviews
- Press Releases
- Case Studies
- Blogs
- Webinars
-
Customers
- Customers
- Case Studies
-
Partners
- Partner Program
- Become a Partner
Home > Resources > Case Study > World's second-largest Bank
World's second-largest Bank deploys Fiorano for Enterprise Agility
With headquarters in London and a network comprising of approximately 10,000 offices in 82 countries across the world, the bank is one of the largest in the world. It is committed to providing their customers with a global banking experience.
World's second-largest Bank deploys Fiorano for Enterprise Agility
With headquarters in London and a network comprising of approximately 10,000 offices in 82 countries across the world, the bank is one of the largest in the world. It is committed to providing their customers with a global banking experience.
USE CASE
Automating Business Workflows; Bond Trading.
BENEFITS
Optimal returns on technology investments
INDUSTRY
Banking
KEY PRODUCT COMPONENTS
Fiorano MQ, Fiorano SOA platform
Business Challenge
The IT infrastructure had grown with the bank over time. It was built and developed on multiple technologies including multiple vendor products and applications designed using varying methodologies. Over time, the bank's IT managers realized that if they were to get optimal returns from their technology investments they needed a flexible and agile IT infrastructure to respond quickly and effectively to the ever growing business demands. As a result, they established strict architectural disciplines vowing to overcome the followings:
Transport-vendor Dependency - The bank infrastructure has, over time, implemented multiple transport systems, including MQ Series, Tibco and others. Seamless switching among transport vendors should be available.
Hosting Environment - There should be a reliable, high performance and 'high available' component hosting environment.
Componentization- Business logic locked within various applications should be extracted and aligned with other applications for reusability.
Well Defined Development Model - Software applications supporting the business processes were developed in an ad-hoc manner with a diverse and undefined architecture.
Black-Box Integration - Most of the time when contract programmers left the organization, the applications tend to become black boxes, making it difficult to incorporate business logic changes.
Event Driven Architecture - Provide a uniform event driven, component architecture for applications across global operations for transport independence and maximum reusability.
Reusability - No rip-n-replace approach to the existing infrastructure, choosing instead a gradual approach that allows maximum reuse of existing resources.
10,000
Offices across 82 countries
Different Financial Centers in different locations are now managed and routed appropriately
Business Challenge
The IT infrastructure had grown with the bank over time. It was built and developed on multiple technologies including multiple vendor products and applications designed using varying methodologies. Over time, the bank's IT managers realized that if they were to get optimal returns from their technology investments they needed a flexible and agile IT infrastructure to respond quickly and effectively to the ever growing business demands. As a result, they established strict architectural disciplines vowing to overcome the followings:
Transport-vendor Dependency - The bank infrastructure has, over time, implemented multiple transport systems, including MQ Series, Tibco and others. Seamless switching among transport vendors should be available.
Hosting Environment - There should be a reliable, high performance and 'high available' component hosting environment.
Componentization- Business logic locked within various applications should be extracted and aligned with other applications for reusability.
Well Defined Development Model - Software applications supporting the business processes were developed in an ad-hoc manner with a diverse and undefined architecture.
Black-Box Integration - Most of the time when contract programmers left the organization, the applications tend to become black boxes, making it difficult to incorporate business logic changes.
Event Driven Architecture - Provide a uniform event driven, component architecture for applications across global operations for transport independence and maximum reusability.
Reusability - No rip-n-replace approach to the existing infrastructure, choosing instead a gradual approach that allows maximum reuse of existing resources.
10,000
Offices across 82 countries
Different Financial Centers in different locations are now managed and routed appropriately
"Fiorano facilitated in creating a system which allows user to buy a bond, by specifying the quantity and asking price. Based on the ISIN, the request is then routed to the appropriate centre."
Chief Technology Officer, Bank
"Fiorano facilitated in creating a system which allows user to buy a bond, by specifying the quantity and asking price. Based on the ISIN, the request is then routed to the appropriate centre."
Chief Technology Officer, Bank
Solution
The solution leverages Fiorano SOA Platform which is based on Event Driven Business Component (EDBC) Architecture. The architecture is a perfect fit for the above requirements. There exists a one to one mapping between their specifications and Fiorano's EDBC architecture.
Fiorano Event Driven Business Components can be used to create process flows designed by using the Fiorano Event Process Orchestrator (Fiorano Studio) with a simple drag and drop approach. With the Event Process Orchestrator, the logical application design is mapped directly to the physical implementation, allowing the development process to become less complex and more intuitive than conventional integration suites. The end result is workflow applications that mimic the business workflows making it easier for business analysts and developers to work together in a common logical easy to understand environment.
The bank developed a miniature platform called LASER using Fiorano SOA platform directly for component development. LASER acts as a bridge on which the bank will convert all its existing applications into components using the bank APIs. The LASER platform will in turn auto-generate Fiorano components from the LASER components. More than anything, LASER is one of the tools relied on to promote the event driven component architecture of Fiorano within the bank infrastructure.
The event process flow allows components to communicate with each other through messages. These messages adhere to the JMS specifications allowing components to interoperate with any standard messaging platform. The components have input ports to accept messages and output ports to send messages. The components can have more than one input and output ports allowing true event based processing. The rich set of adapters and pre-built services readily allowed integration of vendor products and black box applications. The peer to peer architecture combined with robust messaging support provided an ideal hosting environment which was stable and reliable.
Solution
The solution leverages Fiorano SOA Platform which is based on Event Driven Business Component (EDBC) Architecture. The architecture is a perfect fit for the above requirements. There exists a one to one mapping between their specifications and Fiorano's EDBC architecture.
Fiorano Event Driven Business Components can be used to create process flows designed by using the Fiorano Event Process Orchestrator (Fiorano Studio) with a simple drag and drop approach. With the Event Process Orchestrator, the logical application design is mapped directly to the physical implementation, allowing the development process to become less complex and more intuitive than conventional integration suites. The end result is workflow applications that mimic the business workflows making it easier for business analysts and developers to work together in a common logical easy to understand environment.
The bank developed a miniature platform called LASER using Fiorano SOA platform directly for component development. LASER acts as a bridge on which the bank will convert all its existing applications into components using the bank APIs. The LASER platform will in turn auto-generate Fiorano components from the LASER components. More than anything, LASER is one of the tools relied on to promote the event driven component architecture of Fiorano within the bank infrastructure.
The event process flow allows components to communicate with each other through messages. These messages adhere to the JMS specifications allowing components to interoperate with any standard messaging platform. The components have input ports to accept messages and output ports to send messages. The components can have more than one input and output ports allowing true event based processing. The rich set of adapters and pre-built services readily allowed integration of vendor products and black box applications. The peer to peer architecture combined with robust messaging support provided an ideal hosting environment which was stable and reliable.
Fiorano Deployment Architecture at World's Second Largest Bank
Bond Trading scenario
One such instance where the previously discussed benefits of the Fiorano solution were leveraged is within the Bond Trading scenario.
Prices of bonds change at a fast rate. Buyers keep track of these changes and depending on the current price may request a quote from a trading centre. Based on the availability of the Bond at the requested price, the centre can send an appropriate response to the buyer.
In this particular case, there are three financial centers located in London, Singapore and Boston. They each publish their Bonds identified by unique ISINs. The Bond details are then viewable using Graphical User Interfaces which allow users to keep track of the changing prices. The GUI also allows user to buy a bond, by specifying the quantity and asking price. Based on the ISIN, the request is then routed to the appropriate centre.
For example, market data originated from data sources that publish on Tibco RV subject. Fiorano provides Tibco RV connectivity to publish and subscribe on such subjects.
Also certain applications relied on IBM MQ series for their transport. Fiorano's IBM MQSeries connectivity comes handy to talk to these applications.
Pre Fiorano bond trading process
Fiorano Deployment Architecture at World's Second Largest Bank
Bond Trading scenario
One such instance where the previously discussed benefits of the Fiorano solution were leveraged is within the Bond Trading scenario.
Prices of bonds change at a fast rate. Buyers keep track of these changes and depending on the current price may request a quote from a trading centre. Based on the availability of the Bond at the requested price, the centre can send an appropriate response to the buyer.
In this particular case, there are three financial centers located in London, Singapore and Boston. They each publish their Bonds identified by unique ISINs. The Bond details are then viewable using Graphical User Interfaces which allow users to keep track of the changing prices. The GUI also allows user to buy a bond, by specifying the quantity and asking price. Based on the ISIN, the request is then routed to the appropriate centre.
For example, market data originated from data sources that publish on Tibco RV subject. Fiorano provides Tibco RV connectivity to publish and subscribe on such subjects.
Also certain applications relied on IBM MQ series for their transport. Fiorano's IBM MQSeries connectivity comes handy to talk to these applications.
Pre Fiorano bond trading process
Results
Flexibility of Development:
Business Components are easier to develop because the semantics of each independent business component is significantly simpler than the overall complexity of a single, (relatively large) monolithic application. Different Business Components can be developed by a different teams, each team can focus only on their component without having to know the details of work done by others.
Reuse:
Since each Business Component has well-defined interfaces, each component can be developed, tested and debugged independent of the other components. This not only speeds up project implementations but, in the case of well-designed business components, also leads to significantly enhanced reuse.
Dynamic Deployment and Runtime Modification/Replacement:
Business components can be dynamically deployed to remote nodes at runtime, and components within a process can be easily replaced by new or updated components, further reducing the time taken to modify or change an existing process in response to business requirements.
Configuration Management and Version Control:
Business components facilitate version control and dynamic configuration management, allowing fine-grained control over deployments across the enterprise.
Results
Flexibility of Development:
Business Components are easier to develop because the semantics of each independent business component is significantly simpler than the overall complexity of a single, (relatively large) monolithic application. Different Business Components can be developed by a different teams, each team can focus only on their component without having to know the details of work done by others.
Reuse:
Since each Business Component has well-defined interfaces, each component can be developed, tested and debugged independent of the other components. This not only speeds up project implementations but, in the case of well-designed business components, also leads to significantly enhanced reuse.
Dynamic Deployment and Runtime Modification/Replacement:
Business components can be dynamically deployed to remote nodes at runtime, and components within a process can be easily replaced by new or updated components, further reducing the time taken to modify or change an existing process in response to business requirements.
Configuration Management and Version Control:
Business components facilitate version control and dynamic configuration management, allowing fine-grained control over deployments across the enterprise.
Subscribe For Updates
© 2019 Fiorano Software and Affiliates. All Rights Reserved. Privacy Statement | Terms of Use
© 2020 Fiorano Software and Affiliates. All Rights Reserved. Privacy Statement | Terms of Use