SWIFT upgrades and our traditional wisdom

Out of people’s wisdom:
‘The way you prepare it, you get to use it’


SWIFT announcements abstract:
In 2011, SWIFT users will have to pass 2 upgrades

After a several years experience, all SWIFT users have the same opinion: no matter the geo-political conditions, stock fluctuations or times authorities, no matter if we come out of the crisis or not, the moment SWIFT announces upgrades and deadlines for accomplishing these, each SWIFT user is bound to act accordingly.

What’s this all about this time? It’s about the two upgrades SWIFT announced for 2011:

SWIFT connectivity upgrade:
from Dial-up, Dual-I/Single-I/Single-P, Dual-P
to Alliance Connect Bronze, Silver or Gold
deadline: 31.12.2011;


SWIFTNet interfaces upgrade:
from SNL, SAG/SAS, SAB, SAA/SAE, SAW rel. 6.x
to rel. 7.0, optional installing Alliance Web Platform 7.0
deadline: 31.03.2012.


Why should we think about these unpleasant things, now, when summer of 2010 is just beginning and December 2011/March 2012 seem so far away?Because we can’t even think of leaving SWIFTNet interfaces upgrade to be done in the last 3 months of the migration window (you never know the barriers that may occur and to what extent could they obstruct ongoing activities within the SWIFT’s deadline) and we’ll do our best to go through it within 2011.

Even so, why should we talk about these things now?
Because it might be too late at the beginning of 2011.

Because each of the two announced upgrades involves additional costs (a bigger or smaller amount) and, at the beginning of 2011, it will be too late to add these in the budget.

Wise people prepare themselves since summer for the coming winter (a Romanian saying).

Leave a Reply

We use cookies to deliver a cosy experience on our website.

The website is built over Wordpress and it uses plugins to display content as intended.

By accepting this notice, you consent to cookies on this device as per our Cookie Policy.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “%SERVICE_NAME%” uses cookies kept disabled. To view this content or use this functionality, please enable cookies: click here to open your cookie preferences.