Third Party Software - IT Governance help 2

[LonnieJohnson]

We build most of our stuff in house. From time to time we get a department that goes out and buys a third party software or service without our knowledge then asks us to support it at some time down the road. A couple of examples...

1) A billing system that has a sql server back end. The company charges a lot to do adhoc reports so they ask us to do it. We have access to the back end but it is more time working with a structure we did not develop.

2) A druple websiste that is costing too much to maintain by the builder so they want us to do presentations.

Does anyone have any IT Governance that controls this?


ProDev, Builders of Affordable Software Applications
Visit me at ==>

http://www.prodev.us

May God bless you beyond your imagination!!!

 

[BNPMike]

Most companies do. They stop business departments loading any software onto anything, anywhere.

That works.

 

[LonnieJohnson]

Thanks. That is where we want to go. The part I am wanting to stop is the purchasing of it. Once it is bought we end up having to install and support if they don't know how.

ProDev, Builders of Affordable Software Applications
Visit me at ==>

http://www.prodev.us

May God bless you beyond your imagination!!!

 

[BNPMike]

Large compainies just make that difficult. You make people go through complex procedures (security review, infrastructure design, vendor profiling etc etc). I recently bought a product that saved Word docs as pdfs. I had to get a statement from the vendor (in California) about their CO2 reduction policy!!

Or of course you can look at it a different way. The Business is bringing in work for you so you don't find yourself redundant in a few months time. Don't knock it. Some work might look inconvenient. Not having any work at all is even more inconvenient.

 

[PDQBach]

Larger companies have policies that restrict users to software that has been approved (usually by the IT department). This is enforced by locking down PCs so that user signon brings them to a non-administrative account (only administer-type accounts can install software).

There is a policy in place allowing user departments to request non-authorized software. If the software is reviewed then it is usually assessed at one of four levels:

1. Not permitted. Infrastructure demands, security issues, etc., etc., are such that the IT support organization will not allow the software in the organization. Think "Primavera" when your company is using "MSProject Server".

2. Not supported. Just what it says: you bought it, you'd better buy a support contract from the vendor because IT will not provide any support of any kind.

3. Supported - standard "load". Think "MS Office" ... every machine in the company has it.

4. Supported - non-standard load. Think "MS Project" ... if you can provide a business case for using it then you will be charged for licences and on-going monthly support costs. You will be given access to an install location for the software.

If you're trying to implement this in a company that does not currently have a policy, you are in for a world of hurt. The "mindset" change from an open machine to a locked down machine will be fought by power users with a vehemence and tenacity you cannot begin to image. You'll see all sorts of justification for specials cases, exemptions, etc., etc. You *must* -- *ABSOLUTELY* *MUST* -- have full, total, complete, unbending commitment from the highest levels of the organization or you'll get a partial implementation and that will seriously frustrate those who don't have the same level of privileges as the others.

 

[LonnieJohnson]

Thanks PDQBach,

That was enlightening. I like the four categories. I will use those in my proposal.

Thanks again.

ProDev, Builders of Affordable Software Applications
Visit me at ==>

http://www.prodev.us

May God bless you beyond your imagination!!!