× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Outsourcing vs Inhouse
  • From: "Gallagher, Debbie (CA - Toronto)" <dgallagher@xxxxxxxxxxx>
  • Date: Mon, 8 May 2000 21:49:17 -0400

At a previous employer I was very involved with an outsourced data centre,
after the outsource decision was made (I wasn't involved in the decision).
The outsourcer was a very big name and price but delivered poor service.
Some things to consider: 

*       Your company needs to continue to have someone (or more than one, if
your requirements are great) that will manage this agreement and the
relationship with the outsourcer. If there is no one "minding the store"
there is no way to tell is the outsourcer is doing a good or poor job.
*       Your own company should keep the responsibility for strategy related
to IT, and have the outsourcer do only the tactical work. E.g. you would
keep responsibility for determining the IT direction to go but the
outsourcer would do the scheduling of jobs, backups, etc.
*       Make sure you negotiate a good service level agreement (SLA). Think
about how you want this relationship to work, and try to include some
related measurements. For example, if end user satisfaction is important,
include survey results as one of your measurements in the SLAs. Keep in mind
that SLAs need to be measurable and develop the data elements needed to
support the agreement.
*       Invest the time to figure out who you think should do what before
you negotiate the deal. How much input do you want to have into what types
of decisions. What controls do you need? How will you figure out whether
there are any problems? Document the way you think the relationship should
work, and make sure your company and the outsourcer build the concept into
the contract.
*       Think about how you will determine responsibility when there are
more parties involved. For example, where I worked, there was the software
vendor, the outsourced data centre, IBM, and the client (user). So, when the
system doesn't perform up to scratch, who's responsible for assessing the
problem, determining the solution, and paying for the resolution. The answer
may not be obvious - for example, if you leave _all_ of this up to the
outsourcer, you may not find that there are ever any problems that they
caused themselves!

Best of luck - if you have other questions you want answered privately, you
may contact me directly if you want.

Debbie Gallagher
dgallagher@deloitte.ca

----------------
Original Message
-----------------
Hi there I wonder if anyone has recently done an exercise to argue against
Outsourcing AS/400's  and keep it inhouse eg a management summary


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.