Nasscom, which just wrapped up an annual conference that drew thousands of people worldwide to Mumbai, has been hit with a nasty blow. Its president faces prosecution for allegedly failing to ensure the safety of a Hewlett-Packard nighttime call-center employee prior to her murder.Som Mittal, president of Nasscom (an organization representing India's IT services industry), was managing director at HP's GlobalSoft unit when a female employee was raped and murdered by a taxi driver en route from her nighttime shift in Bangalore in 2005. Some of India's call center employees work night shifts to service U.S. customers during the day.

The Indian state of Kamataka is prosecuting Mittal under a law governing employee safety, Reuters reports, and the Supreme Court rejected his challenge of the charge in a ruling earlier today. If convicted, Mittal faces a token fine of about $25 and a criminal record, Reuters reports. The government is trying to send a message, particularly since another female citizen working at a nighttime call-center job in Pune was raped and murdered by her driver last year.

This case provides further proof that the practice of employing Indians in nighttime jobs to serve U.S. customers is a faulty and decaying business model in the broader realm of globalization. There are other signs: India's workforce increasingly rejects these jobs because -- hello? -- they want a normal life. And when an Indian accepts a nighttime job, it's usually only until they find something better, creating turnover problems for both the services vendors and their clients. Some customers of U.S. companies, as we know, complain about language barriers and the rigidity of India-based call center reps, many of whom are required to closely follow their scripts. Business 101: Above all else, keep your customers happy.

CIOs also are finding fault with the model. Genworth Financial, for example, observed particularly high attrition rates among nighttime employees of its IT services provider, Genpact. Between 2003 and 2006, the company launched "Project Daylight," which called for transitioning the work done in India from 80% at night to 85% done in that country's daylight hours. That meant pulling some jobs back to the United States, like call center work, and developing new processes that required the easy shift from one time zone to another. In retrospect, "the night shift was designed for short term cost savings, rather than designing your company to be a truly global business," CIO Scott McKay told me in a conversation a few months ago.

India offers a tremendous amount of talent, which is helping to fuel new startups (my colleague Chris Murphy, who attended Nasscom last week, has been doing some great reporting on this topic from India). This substantial talent base also is helping the Indian government meet the demands of its rapidly growing infrastructure, and providing U.S. and global companies with a pool of brilliant technologists and/or PhDs.

But that whole model of chipping away at the operations budget by asking Indians to use fake names like John and Sue and follow customer service scripts at 3 a.m.? It's on its way out, and rightly so. It increasingly appears to be an ineffective way to save money.

And, last but in no way least, let's hope that no more Indian call center employees fall victim to nighttime rapes and murders.