IT-Infrastructure in Banks

Hi Guys,

I was a active member of this forum. I am currently doing MBA in IT-MAnagement.

I would like to know the primary reasons for the Banks to ask for application packaging and the various IT-Infrastructure problems banks face and money they spend on it.

I am doing a study on this and will produce the results in this forum so that it can benefit who are looking to expand their business in various geographical locations

I am looking forward for some white papers from all of you


0 Comments   [ + ] Show comments

Answers (3)

Posted by: ArnoldM 9 years ago
Yellow Belt
I think white papers nowadays aren't free even if it's for your study. A lot of professionals have copies of their white papers but even if it's just a copy, they won't give it to you for free. You may need to check out for some [url=http://personalmoneynetwork.com/payday-loans/]personal loan[/url] if you wanted to have copies of your own.
Posted by: jmcfadyen 9 years ago
5th Degree Black Belt
banks typically have numerous desktops and applications that need to be distributed immediately.

a typical bank has 10k to 50k pc's. If you need an app deployed overnight or even tighter timeframes (as expected in most big banks). Can you imagine the logistics of visiting 50,000 pc's and for that matter creating 1000cd's for 500 cd's for 500 techies and distributing them over vast geographic regions in order to manually install 100 pc's each.

packaging removes these issues (assuming you do it right). I expect getting someone to write you an entire white paper for you is likely to get little response.

you could goto realtime publishers and lookup desktop publishing which will get you an old yet relevant white paper.
Posted by: Arminius 9 years ago
Second Degree Green Belt
I can't speak for banks, but I can tell you why the mdeical firms I have worked for have done packaging.

let's say you have 1000 nodes on your network and they all need something installed - call it Bob. Bob takes 20 minutes to install.

so you give 2 techs each a CD, thumb drive, or path to the server to do the install. That's 20,000 minutes they spend at PCs, not to mention time scurrying around to each PC. Assuming that the PC is available to use when they arrive and they don't get sent away (like that happens), you can see that they will spend 333 hours (20000 minutes/60 minutes per hour) of labor doing the install. If it's not scripted, that's a lot of variation that can happen on each install.

Now you take a packager and have them spend 40 hours on Bob. It goes out, consistently, and correctly, to all 1000 nodes. Oops! Mistake! 5 hours to fix, another hour to push, and the problem is solved everywhere. You've saved around 280 hours of labor that can be spent on troubleshooting or other non-repetitive tasks.

The biggest challenge you face is infrastructure, primarily from your Networking team. they don't like all that bothersome traffic on their network, especially if it isn't prioritized. And if you span the WAN with a large app, someone's going to be in your cube with a red face. Storage isn't too much of an issue any more, as long as you don't duplicate your packages all over the same storage space.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ