Saturday, February 27, 2010

IT Support Meltdown!

I couldn’t help but empathize with Bob Turley, CIO of our iPremier in our case study this week. Last year we hosted an employee survey for a client that led to a couple long, sleepless nights. The survey was hosted by a web hosting provider here in Atlanta who we’ve been doing business with for several years. By and large, our experience has been very positive, including good reliability, low costs, and solid local customer service and support. However, our experience was very different this time around.

During the first week of the administration, things seemed to go very smoothly. Data was coming in steadily and the phone was quiet (that’s a good sign!) On Saturday night I thought I’d check in to see how the survey was going and was greeted with a “fatal system error” message. My blood pressure spiked momentarily, but I didn’t panic because this sometimes occurs when the server goes down momentarily for updates, maintenance, or whatever. I waited a couple of hours, but still no activity. I called my programmer, who helped set up the site, to see what he could make of it. He suggested that we call the company to see what’s going on. To our surprise, no support was available locally so we ended up dealing with client support in the Philippines. They spoke broken English, and we had a hard time getting a clear connection. So we ended up having to repeat things over an over again. Sound familiar? After talking to a number of technicians our problem was finally escalated to the next level of service. You can guess what happened next.

Early Sunday morning I checked in and the system was still down. Tried to call the help desk again (can’t repeat what I said), and still got the run around that they were doing everything they could to fix the problem. Again, I felt we weren’t making any progress and getting the run around. I finally resigned myself that this problem could only be fixed locally and that the only hope we had was waiting until Monday morning to get a hold of the Atlanta staff (if they still existed). Early Monday morning the system was still down. I called the help desk and told them that we only wanted to speak to the local staff in Atlanta. After some delay, they connected us to their Atlanta staff. Yea!!! We tried to explain things once again, and the person we talked with said he would get on it right away, informing us that the problem may have been caused when the company migrated to their new server over the weekend. Of course this is the first time we had heard this explanation. Surprisingly, he called me back about an hour and half later and told me the problem was fixed and the site was back up. Found out that when they migrated to the new server, the new plan I had signed up for a few months earlier had not transferred over. The new server was still pointing to the old plan.

What frustrates me more than anything else is all the time and energy that was spent to resolve an issue that could have been fixed in a relatively short period of time had the right people been available to fix the problem. For two days, all we kept getting were broken promises and unwarranted delays. You feel completely out of control, but there is hardly a thing you can do about it without the right kind of support and service. We found out later that the company had merged with another firm and the management and support staff had all changed – obviously for the worst! As you can imagine, we’re evaluating other web hosting service providers for our next online survey. Hopefully our next experience will end up a little more positively and with a fewer number of gray hairs. Stay tuned!

Friday, February 19, 2010

O Do I Need ERP!

We’re in the process of wrapping up the results for an employee opinion survey we administered for a client last year. It’s been a long drawn-out project, beginning last August with the development of the survey, the setup of the administration (online and paper) and now the analysis of about 1300 on responses, 800 written comments, and creation of 70 manager reports. This survey is quite a bit longer than many of the other surveys we do, consisting of 79 questions, 2 open text boxes for comments, and background and demographic information of the respondent. Currently, we use SPSS to crunch the numbers, ACCESS to transcribe and produce the comment reports, and EXCEL to generate the summary reports (includes graphs, tables, charts, and text). The reports include descriptive statistics, historical information from previous administrations, and highlighting of significant differences.

After our readings and discussions on ERP (and CRM), I’m convinced more than ever that my process is completely out-of-date, time consuming, and prone for error (if you have not already guessed). None of our systems are integrated or even partly integrated. Information has to be constantly saved and imported manually from one system to the next, with a lot of checking and rechecking of data on the back end. Surprisingly (and thankfully), we’ve never released information that has been in error, but we spend a lot of long hours reviewing and validating the results before delivering them to the client. You get the picture!

I realize that I’m going to have to figure out a way to simply this “monster” by either buying or developing a system that can house the data in preferably one place, and be easily retrievable to analyze findings and produce reports. I recognize that the customization and flexibility we give clients to tailor the results to their specific taste may need to change, but the potential cost savings, speed and potential quality, and accuracy may increase. After I finish up this job in the next couple of weeks, I will take a short breather and then begin exploring what current technology is available to make my job a whole lot easier.

Thursday, February 11, 2010

Quick Access to Business Information?


Financial Times Press, a unit of Person, has just introduced two series of short, digital-only books for professionals who want a condensed version of the text. Timothy Moore, publisher of FT Press, says “It’s a good idea to be able to provide people with shorter, more expedient, more time-sensitive content.”

Its Element series is for already published works, stripped down to 1000-2000 word versions, and sells for $1.99. Its Shorts series is based on newly published works, with about 5,000 words, and priced at $2.99. FT Press has begun marketing these works through Kindle electronic bookstore on Amazon, and through Barnes and Noble’s e-book store. To spur sales, Amazon has already discounted the price of Shorts to $2.39 and Elments to $1.39. Barnes and Noble has kept the publisher’s pricing.

Some of the business titles include “Reengineering the Rules of Management,” by James Champy, “Keeping it Honest, from Kitchen to Coca-Cola,” by Seth Goldman. FT Press has already published 242 titles and plans to have 500 by the end of the year. Specifics about publishing fees and royalties are not available. Some fear that these condensed versions of the texts could cannibalize sales of traditional books. However, Mr. Champy says there are some individuals who only want access to certain elements of your work, and don’t have the appetite to read a long, serious business book.

I don’t know about you, but it certainly sounds like something worth exploring, given its low cost, easy access, and digital interface. I’ll be interested to see what business book titles and information will be available.

(New York Times, "Kindle Books in Snack Size,” article, 2/8/10)

Friday, February 5, 2010

Fond Memories of Those IBM Punch Cards


I had a moment of déjà vu while working on this week’s research assignment on the history of Information Systems. While growing up, my mom worked as a key punch operator for United Airlines during the 1960’s and 1970’s. A key punch operator’s job was to manually keystroke the data into punched cards by punching holes in designated locations on the card. The cards were then fed into a mainframe computer to record employee and customer information. A key punch station consisted of a small desk with a keyboard similar to a typewriter, with hoppers for blank cards and stackers for punched cards. As you could imagine, everyday there were hundreds of punch cards that would be discarded due to improper entry. Employees were oftentimes encouraged to take home any cards that were not useable. I remember my mom coming home with boxes, containing hundreds of IBM punch cards in a wide variety of colors -- red, blue, green, and yellow. As kids, we couldn’t wait to leaf through them, sorting them by size, color, punch count, and more importantly figuring out what we could make out of them.

I know this doesn’t sound very exciting by today’s standards, but back then anything in color was a novelty. Almost everything was in black in white, printed documents, photographs, and TV’s. I remember using them around the house as note cards, to decorate our bikes for parades, to make paper airplanes, to build a house of cards, and yes, even to make Christmas ornaments. Today the cards are a pretty much obsolete, and the mainframe has been replaced with high-speed networks, LAN’s, and the internet. Every once in a while I stumble upon a punch card while rummaging through some old box in my mom’s attic or happen to see one lying around at a flee market. I fondly remember the fun and excitement we all had mixing, matching, and manufacturing works of art from those old IBM punch cards.