Friday, April 12, 2013

To outsource or not to outsource… that is the question

We recently learned that one of our partner schools is proposing to hire full time staff for their IT, finance, maintenance, and other services, which had previously been contracted out. Okay, at first glance this seems like a legitimate management decision, but is it?

While I cannot speak to other types of services, we experienced this exact scenario once before with respect to IT services at a K-6 charter school and it was disastrous.

Several years ago in Texas, a Vice-Principal was hired at one of our partner schools. He quickly determined that his expertise was sufficient to supplant ours and within a few months found a way to eliminate our contract to provide IT support on one day each week. This was a school that we had built from the ground up and was operating with a high degree of efficiency.

I will spare you the details, but by the following year the Vice-Principal was fired, the school was in financial distress (which led to the dismissal of the business manager), and the technology had pretty much been re-outsourced to the Regional Service Center (the state). And the terminated Vice Principal had so maligned our service model in the process of making the case for our contract termination, that we were not considered in rebuilding the infrastructure.

The whole process diminished efficiency, caused significant service disruptions, cost significant sums of money, and accomplished nothing of value.

So are there times when it is a good idea to hire a full time IT administrator for your school? Maybe, but in the dozen years or so we have been doing this we have found very few. For starters, the numbers (as in cost) just don’t add up. Furthermore, the administrative oversight of personnel is not significantly better. And the level of expertise is greatly diminished.

Restated, these are three reasons why outsourcing IT is normally a better idea than hiring full-time: Cost, Control, and Expertise.

Cost

According to a January 2011 survey by PayScale, the average high school principal in the United States earned a total salary package between $68,167 and $101,560. The Bureau of Labor Statistics validates those numbers, finding that administrators at elementary and high school receive an average annual salary of $85,220.

On the other hand, a similar study by the BLS for computer administrators employed in the highest-paying industries, computer equipment manufacturing and securities exchanges, salaries averaged $89,840 and $89,340, respectively. The number was less in the academic world, but not by a large margin. Granted there is a wide range of qualifications for Information Workers, but even non-degreed, yet certified Network Engineers earned up to $56,000 on average.

When competent Information Workers can earn nearly as much as School Administrators, it is difficult to understand the justification to hire a full-time Technology Director at most Charter Schools. This is particularly true when very few schools need full-time IT administrators. They rarely even need full-time technical support.

Our standard management model provides 1 day per week of onsite Network Administration, supplemented by the daily support required for the particulars of a school, either by a less qualified support engineer or a faculty member assigned to technology. The best scenario is having a faculty member assigned to support technology and serve as the point person in IT matters.

Let’s do the math, assuming a 50 week annual contract. A network engineer charging $65.00/hr. at 8 hours per week would cost $26,000. A desktop support technician charging $15.00/hr. for 20 hours per week would cost $15,000.  The total cost is $41,000. And this provides the full range of technical services required for most freestanding Charter Schools.

This is about half of the cost of hiring one competent Computer Administrator. I emphasize competent, because like in the experience described above, hiring to the level of your budget may in fact cause you to hire an incompetent Computer Administrator. The unintended costs of doing so can be enormous.

Control

Not long ago we had to let one of our desktop support engineers go. We were informed that he was not a good fit for one of our schools and our coaching him on his work ethic was not going well.  We reluctantly terminated this employee, only to find that the school had decided to rehire him as their employee instead of ours.

The situation went from bad to worse. Now, not only did we have the same HR problem as before, but now we had less supervisory oversight.

You will in all probability always need to have entry level desktop administration support. This is where competent Computer Administrators get started. Managing desktops, while getting training on network administration and specific line of business applications is the common pathway for information workers. And there is always an abundance of desktop administration to be done in a school.

But having administrative control of information workers is a tricky business. It is crucial that those so employed are extremely trustworthy and able to work well with others. After all, they control all of the access to information resources in the school and can without much difficulty view sensitive documents and even your email communication in many cases.

Having an outside entity manage your Information Systems can provide an important element of integrity into your infrastructure.

Expertise

You don’t hire a doctor full time to evaluate a medical condition and treat it. Nor do you typically hire a CPA full time to do your bookkeeping. And most schools only retain legal counsel for specific compliance or legal matters where specialized knowledge is required.

There are reasons, both economic and practical why outsourcing Information Technology is wise. Obtaining the requisite technical expertise is the most important reason. Some technical expertise is only required once, as in the design of your network or major system implementations. Other technical specialization may be required only intermittently when upgrading servers or network infrastructure. And much technical expertise is only required infrequently, such as network administration.

So why would you hire full-time to the highest level of expertise for those rare occasions when needed if the bulk of your technical support requirements exist at the entry level? This is a classic misallocation of resources.

Summary

At the risk of self-serving, it seems that outsourcing Technology Management is a pretty common sense approach. It costs less, provides more control, and delivers a higher level of expertise. And these are all good things.

But alas, a wise individual once told me “Common sense is not so common”. 

Please call if you would like to discuss the right mix of Information Management and Technical Support resources.

Friday, April 5, 2013

What are the practical limits of Windows Multipoint Server?

One of our favorite vendors (hint: starts with an H and ends with a P) recently discontinued a popular line of specifically designed hardware components for Windows MultiPoint server. This included both the Multi-seat server and Zero Client components.

We were very surprised and a bit disappointed!

I called to speak with the HP product champion at our distributor and was told that although the product had been quite popular, the overly optimistic hardware specifications published by Microsoft had caused the unraveling of the product line. Apparently there were too many schools out there attempting to install the maximum allowed zero clients onto an underpowered server at a ratio of 20:1.

And when the system (with 20 students trying to do online gaming) slowed to a crawl, the buyers got upset. Go figure…

As one wise military commander told me many years ago at Officer Training, when asked about the wisdom of doing a particular thing; “You can, but you may not”. This pretty much sums up the wisdom of the aforementioned scenario. Perhaps it is better stated that while you CAN attach 20 Zero Clients onto a modestly provisioned MultiPoint Server, you may in fact not WANT to do so.

For the record, MultiPoint, as of this writing is not going away. Nor has it been an unsuccessful new product, not by a long-shot. It is working very well in the schools we have installed it when a reasonable effort to design the system has been employed.
And not to worry, there are still plenty of vendors supporting the technology and the required Zero Clients that are required to easily roll it out. But you may want to curb your optimism just slightly as you do system design and engineering. A reasonable allocation of server resources, client connections, and bandwidth utilization will help you make MultiPoint the home run in your school.

Here are three specific suggestions that will ensure your project does not get bogged down:
  1. Determine the purpose of the MultiPoint installation
  2. Start with a properly specified server
  3. Calculate the Server/Client Ratio conservatively
Determine the purpose of the MultiPoint Installation
 
There are widely divergent requirements for a MultiPoint installation. Some are managed with the strict control of a well-organized teacher leading a discussion and managing the student sessions. Others are a free-for-all student study hall where anything goes. And on occasion (at least a few times each year) there will be standardized student testing where workstations are configured precisely for a sterile testing environment.
 
As you design you MultiPoint installation, start with the designated purpose. And if you can’t ensure that designated purpose then design conservatively. You will be happier in the long-run (although your financial managers may not share your entusiasm).
 
In our rather unscientific, but thorough testing, we have found that a ratio of 5:1 with a reasonable MultiPoint Server is a very solid place to start. And on the upper end of the scale, we have found that exceeding 10:1 under most conditions is not going to deliver the needed performance for anything more than casual web-browsing.
 
Start with a properly specified server
 
It has been said that “Common sense is not so common”. But it makes sense in this scenario to have a Multi Core processer (more is better), as much RAM as you can afford, and a fast Hard Drive with at least 500GB of space. Additionally, the server needs to have the capability for rendering graphics. This is normally accomplished by installing a graphics card in one of the open slots if it is not built into the mains system board.
 
And while there are many different connection configurations for MultiPoint, we have had the best luck using USB. Accordingly, you will need to have as many USB ports on the server as you plan to have zero-clients. This might require you to purchase a USB card and install it in your server.
 
Some manufacturers design servers specifically for the MultiPoint Server Operating System, but a bare box system is fine. Other than what is mentioned above, there is nothing special about hardware required to run MultiPoint. If it will run Windows7 or Windows Server 2012 standard, it should work fine with MultiPoint Server.
 
Calculate the Client Server Ratio Conservatively
 
The ratio of clients to a single server is the last thing you should determine. We simply call it the client/server ratio. Microsoft advertises a ratio of 10:1 in Windows MultiPoint Standard and 20:1 in Windows MultiPoint Premium. With few exceptions these numbers are (characteristically) hype.
 
For hard core computer lab workstations, keep the ratios low. For occasional browsing of the library collection or standardized testing increase the ratios accordingly.
 
One other aspect of determining ratios is the simple matter of logistics or layout. Depending on how the rows or clusters of workstations are configured in your lab, you may need to adjust your ratios purely based upon space and distance. The USB cables included in the HP Zero Clients were 25’ long. Distances greater than that may not work well. Check with your specific vendor for the lengths of included cabling (if included).
 
Summary
 
Windows MultiPoint Server is a great technology that will dramatically reduce the cost of provisioning a computer lab at your school. Not only do you save tons in buying hardware, but you nearly eliminate one of the more costly components of your technology budget - technical support. And you will see a commensurate reduction in both electrical and heating/cooling costs.
 
You will also have a much, much quieter computer lab (not counting student noise!).
 
But don’t be ridiculous, while you CAN connect 20 clients to a single MultiPoint server, you MAY NOT have a good experience in doing so. Good advice for me back then and for you today…
 
If you need assistance in designing your MultiPoint Server project, give us a call.