Formpipe uses cookies to improve how the website works for you as a visitor. To change your settings or for more information about cookies, click on 'Settings'.
Formpipe uses cookies to improve how the website works for you as a visitor. Here you can change and see information about what cookies are used. Turn on and off categories and save your choice. To learn more click 'Cookie policy'.
These cookies are essential for the website to operate correctly and cannot be disabled without ruining the usability of the website. We delete these cookies when you leave the website, where possible.
Name | Retention period | Information about the cookie | Disclosure of information to third party |
ASP.NET_SessionId | Used to maintain an anonymised user session by the server. | 1 session | No. |
cookie-consent-settings | Used to determine if the user has accepted the cookie consent, contains consent choises | 30 days | No. |
lidc | To promote data center selection | 1 day | Yes, LinkedIn |
li_mc | Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side | 2 years | Yes, LinkedIn |
BIGipServer~EPWS~EPWSWEB103_HTTP_Pool | Determine pool | 1 session | Yes, EPiServer |
These cookies are used to track our visitors across our website. They can be used to build up a profile of search and/or browsing history for every visitor, or to better understand how the user uses the website so that we can improve it. Identifiable or unique data may be collected. Anonymized data may be shared with third parties.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
_fbp | Used by Facebook | 90 days | Yes, Facebook |
AnalyticsSyncHistory | Used by LinkedIn | 30 days | Yes, LinkedIn |
bcookie | browser identification | 2 years | Yes, LinkedIn |
lang | Language preference | 1 session | Yes, LinkedIn |
li_gc | Used to store guests' consent to the use of cookies for non-essential purposes | 2 Years | Yes, linkedIn |
lms_analytics | Used to identify LinkedIn Members in the Designated Countries for analytics | 30 days | Yes, LinkedIn |
_guid | Used to identify a LinkedIn Member for advertising through Google Ads | 30 days | Yes, LinkedIn |
_ga | Used by Google Analytics to identify a visit. | 2 years | Yes, Google gains access to the information collected by the cookie. |
_gid | Used by Google Analytics to identify a visit. | 24 hours | Yes, Google gains access to the information collected by the cookie. |
_gat_gtag_[Property-ID] | Used by Google Analytics to identify if a visitor (web browser) is new or recurrent. | 1 minute | Yes, Google gains access to the information collected by the cookie. |
These cookies are used by third party to track and collect data to be used in advertisment. They can be used to build up a search and/or browsing history for every visitor. Identifiable or unique data may be collected.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
ajn | Used by adnxs for marketing | 90 days | Yes, adnxs |
uuid2 | Used by adnxs for marketing | 90 days | Yes, adnxs |
IDE | Used by Google doubelclick | 2 years | Yes, doubleclick |
_gcl_au | Google adsense | 30 days | Yes, Google |
msd365mkttr | Dynamics marketing | 2 years | Yes, Microsoft |
NID | Google ads optimization | 6 months | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 1 year | Yes, Google |
UserMatchHistory | Sync LinkedIn Ads ID | 30 days | Yes, LinkedIn |
lms_ads | Used to identify LinkedIn Members off LinkedIn in the Designated Countries for advertising | 30 days | Yes, LinkedIn |
Support
Whether you're looking for some
assistance or further information
regarding your solution, we're here
to help. Yes, take me there!
Sweden
Headquarters, Stockholm
Formpipe Software AB
Sveavägen 168, Stockholm
Box 231 31, 104 35 Stockholm
SE – Sverige
Tel: +46 8 555 290 60
Email
Linköping
Gasverksgränd 2, 582 22 Linköping
Tel: +46 8 500 072 25
Email
Västerås
Metallverksgatan 6, 721 30 Västerås
Örebro
Engelbrektsgatan 6, 702 12 Örebro
Denmark
Lautrupvang 1
2750 Ballerup
Tel: +45 3325 6555
Email
Germany
Formpipe Lasernet GmbH
THE SQUAIRE 12
Am Flughafen
60549 Frankfurt am Main
Email
UK, Cambridge
First Floor, Block A, Harston Mill,
Cambridge – CB22 7GG
Tel: +44 1223 872747
Email
UK, Nottingham
Unit 1, Isaac Newton Centre
Nottingham Science Park
Nottingham – NG7 2RH
Tel: +44 115 924 8475
Email
USA
Formpipe, inc.
1200 US Highway 22 E Suite 2000
Bridgewater, NJ 08807
Tel : +1 908 200 7937
Email
Formpipe and Temenos discuss why an increasing number of banks are moving to the cloud and how conversations are shifting, in our podcast ‘Beyond the Document’.
Cloud-based solutions are becoming widely adopted by banks and financial institutions as an effective means to simplify processes, improve security and provide more diverse service offerings for customers. The shift has been a slow burn, but confidence in the cloud across the banking industry is now skyrocketing. So, we ask, what are the benefits of cloud banking and is it the future?
We’ve been exploring this subject alongside a leading industry expert in the latest episode of ‘Beyond the Document’ – Formpipe’s official monthly podcast which lifts the lid on Output, Document and Customer Communications Management.
This month, Formpipe’s Ben Saxton sits down with Ermes Dajko, Senior Cloud Solutions Architect for powerhouse global banking platform Temenos. Ermes plays a pivotal role at Temenos in helping banking customers with their journey to the cloud. This includes offering advice and support when it comes to architecture, integration, security, governance, and more.
The pair discuss the benefits that can be recognised by moving to a true open banking cloud.
You’ll learn about the evolution of cloud banking over the past 10 years, the key drivers for banks adopting the cloud, the main benefits of doing so, and Ermes’ predictions for the future.
Here’s what you can expect from this month’s episode:
Evolution of cloud banking
As part of his role, Ermes works with a wide range of stakeholders from technical professionals such as Developers and DevOps Engineers, right through to C-Level Executives within banks.
How have their conversations shifted over the past 10 years when it comes to cloud banking?
Well, it used to be a matter of ‘when’ and now it’s a matter of ‘why not?’.
Previously, it was a vendor’s job to ‘sell the benefits’ of cloud vs on-premise to banks. Now, with most banks already having an opinion on the cloud, these arguments go wider than the importance of it, but also involve addressing factors such as what it means over a PaaS or a SaaS model.
Standardisation and the levelling up of the ‘Model Bank’
Another key consideration for banks moving to the cloud is whether they should run it themselves or work with a vendor to operate banking capabilities as a service.
Standardisation and the ‘Model Bank’ has been one of Temenos’s biggest selling-factors over the past two decades. With the introduction of cloud, vendors such as Temenos have to couple those services with their cloud offering.
Ermes says:
“So it's not just the business functionality, it's how you provide that with security, with governance, with DevOps, with extensibility. So, in my opinion, the banking cloud is like the second gen of the Model Bank.”
In the podcast, Ermes explains why 'The Model Bank' has been such a success for Temenos and how cloud banking is revolutionising this approach.
Cloud = minimising costs
One of the key drivers for banks looking to adopt the cloud is to minimise expenditure. There’s no need to purchase hardware or spend more to monitor and maintain it, the cloud digitises these resources.
Interestingly, Ermes shares that the discussion to move to the cloud is often steered by the CFO, not the CTO or the CIO. In the chat, he explains why this is the case and how it relates to moving from CapEx to OpEx.
Also, as considerations have shifted to PaaS vs SaaS, the second dimension of cost is employing DevOps Engineers to deploy and manage the applications.
How can a SaaS model further reduce expenditure and standardise the 'people' aspect of this process? Ermes gives his take.
The banking cloud as an ecosystem
The banking cloud is evolving and becoming an ‘ecosystem’. Ermes explains: “But it's not just about the banking services, it's also about the ecosystem, because our banking capabilities alone, they need to be complemented with peripheral applications such as Formpipe’s”.
Microsoft Azure has also transformed into a marketplace of services on a PaaS level, where users can deploy databases and third-party solutions. “We see the Temenos banking cloud plus exchange becoming that on the SAS level” says Ermes.
Predictions for the future
Want to know Ermes’ predictions for the future of cloud banking? Listen to the episode to find out. At 20 minutes long, it provides perfect listening for that train ride to work.
Quiz
What piece of IoT does Ermes say could be ‘modernised’ with up-and-coming technologies?
Here’s the link to listen on Spotify, or just hit play at the top of this article.