SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?


To: John Mansfield who wrote (3017)12/23/1998 5:04:00 PM
From: John Mansfield  Read Replies (2) | Respond to of 9818
 
'IBM hit by Y2K suit

asked in the TimeBomb 2000 (Y2000) Q&A Forum

IBM hit by Y2K suit By Lisa M. Bowman 12/22/98 07:53:00 PM

excite.com
/news/19981222/2178905.inp

Firm that sued Microsoft last week seeks class-action status in IBM suit.

IBM Corp. is the latest major company to find itself in the cross hairs of a Y2K liability fight.

Oakbrook, Ill., gynecologist Mario C. Yu has filed suit seeking class-action status on behalf of those
who bought bundled software and hardware products from IBM (NYSE:IBM) and Raleigh,
N.C.-based Medic Computer Systems Inc. -- specifically IBM's RISC 6000 computer running AIX
4.1 and version 7.0 of Medic's software. Medic makes products that track patient appointments and
test results. The suit -- filed in the U.S. District Court for the Northern District of Illinois -- claims health
care providers could experience significant problems that could harm patients as a result of the
non-compliant products. Attorneys called the problems related to the so-called Millennium Bug a
"potential time bomb."

According to the suit, Yu bought the products on Dec. 10, 1996, and had them installed in 1997 for a
total of $19,336. Yu did not become aware of a potential Y2K problem until November 1998, and two
weeks ago, he was notified that he could have the problem fixed -- for $2,410, the suit claims.

Seeking injunction

Yu is seeking compensatory and punitive damages and is asking a judge for an injunction requiring the
company to notify all licensees of pending problems and issue a patch. According to the suit, about
60,000 health care providers use Medic's software, but it's unclear how many of those use it on an IBM
machine. Neither IBM nor Medic officials were immediately available for comment.

Yu is being represented by Chicago-based Gold & Rosenfeld and Gogel, Phillips & Garcia. Last week,
the firms filed suit against Microsoft Corp. (Nasdaq:MSFT) on behalf of a Naperville, Ill., consultant,
claiming that its FoxPro development tool isn't Y2K compliant.

Companies increasingly fearful

Companies are becoming increasingly fearful of Year 2000 litigation, as the problem date looms closer.

Because many older systems read only the last two digits of the date, some may read "2000" as "1900"
and malfunction. During a meeting with analysts earlier this year, Microsoft warned that upcoming Y2K
suits could affect the company's stock in the coming quarters. Meanwhile, another medical company last
week settled a Y2K suit filed against it. Medical Manager agreed to provide a Y2K-compliant upgrade
for free to the plaintiffs.

And a high-profile Y2K contract dispute was settled Monday, when retailer J.Baker dropped its claim
against Andersen Consulting involving a non-compliant system the consulting firm had recommended
nearly 10 years ago.

=====================================================================
guess this will be happening more and more, especially after 12/31/98.

Mike ==================================

-- Michael Taylor (mtdesign3@aol.com), December 23, 1998

Answers

You know, it's really the suit itself that is troubling - I don't like the fact that somebody had to sue, but I
know it happens.

Rather - consider that this is one application in one industry (health care) from one vender - on a
product (health care, and billing too?) that is highly date dependent - for a fairly recent product release
by a big company - and 60,000 small companies are affected.

It's starting......

-- Robert A. Cook, P.E. (Kennesaw GA) (cook.r@csaatl.com), December 23, 1998. Sorry - "it's not really the lawsuit that's ...."

-- Robert A. Cook, P.E. (Kennesaw GA) (cook.r@csaatl.com), December 23, 1998.

I don't know about IBM and its software, but I do know Microsoft products. Microsoft sucks. I hope
someone is able to stick it big to Microsoft and make it stick.

There is NO EXCUSE for a company like Microsoft, putting out basic products like operating systems,
word processors, spreadsheets, and databases to not have at least the basic date function stuff squared
away. They have had years to do it. And they haven't. All they have is lame potentially incompatible
"windowing" of two-digit dates (assumes two digit dates before some arbitrary "pivot" date is 21st
century, and the rest 20th century) for various products.

Microsoft spends more time trying to figure out how to kill the competition than in getting its stuff to
work smoothly and reliably. They add more "features" (featuritis) before they even get the old features
straightened out. Anyone that has tried to use Access for more than anything than what you might find in
"Access for Dummies" knows what I'm talking about.

-- Poffed (POd@microsoftsucks.com), December 23, 1998.

Anybody want to join me in a class action against the bottom feeding scumbag Lawyers in this country
who are exacerbating the y2k calamity with their phoney legalise and shackles on full disclosure. They
sure are *NOT* part of the solution.

Case in point, Mr. and Mrs. prez.

-- Andy (2000EOD@prodigy.net), December 23, 1998.

Robert, I agree. I think this was a calculated move to be one of the first on the books before the "wave"
really hits and the bottleneck breaks the system.

I'm truly worried about how any company, regardless of size, will manage to work through y2k when
litigation threatens their very existance. What is the incentive to continue if it means that you'll be out of
business because of legal exposure?

Yep, it's starting...

Let the march begin.

Mike ===============================================================

-- Michael Taylor (mtdesign3@aol.com), December 23, 1998.

Contribute an answer to "IBM hit by Y2K suit"

greenspun.com



To: John Mansfield who wrote (3017)12/23/1998 5:06:00 PM
From: John Mansfield  Respond to of 9818
 
'The Window Of Opportunity Factor

asked in the TimeBomb 2000 (Y2000) Q&A Forum

When any mission critical system breaks down, there is a finite window of opportunity in which to fix the
system. To use a stark example mentioned in an earlier thread, if the 'heating system' in New York City
breaks down in the middle of winter, how long before telephone poles are converted to BTUs by a
freezing population? At some point, fixing the problem becomes much more difficult or impossible
because you just didn't have the time to do the things you would normally do to solve such problems.

Many businesses who seem to have opted for 'fix on failure' will end up being done in not by the
problem itself, but by missing their window of opportunity to fix the problem. In simple terms, it does
you little good if you can fix the problem in 20 days if you've lost a critical share of your customer base
after 15 days.

Or to take a real (but not Y2K-related) example. The recent UPS strike drove a lot of UPS's former
customers to their competition. I'm certain that one of the things the UPS execs considered was "How
long of a strike can we endure before we've lost too much of our customer base to recover?". Well,
they did loose some customers but they apparently settled the strike well within their window to do so.

Most of us are quite familiar with this concept and yet, we seem to have trouble applying it to
Y2K-related failures.

Professional marketers deal with this issue every day. They know, for example, that it will do you little
good if you can buy 30,000 Furbies today if you can't take delivery until December 26th. You've lost
your window of opportunity.

For military planners, understanding the concept of 'window of oppotunity' is critical to the successful
completion of an assigned task.

NASA deals with 'launch windows'.

Emergency medical technicians talk about 'the golden hour' (it is a window of opportunity for saving the
critically injured.)

As important as it is to Y2K related failures and for as many folks as there are who have to deal with
the concept daily, I just don't see 'window of opportunity' being factored into many of the discussions of
contingency planning. It is virtually non-existant with the Y2K pollyanna crowd. And even with the folks
who take Y2K seriously, it is often assumed that standard 'windows' will apply. They will not.

We have already missed our window of opportunity for a technical fix to many Y2K problems.
Preparation and contingency planning on a personal, business and community level is all about
maximizing that last window of opportunity.

-- Arnie Rimmer (Arnie_Rimmer@usa.net), December 23, 1998

Answers

Arnie:

An excellent and thoughtful comment. Small businesses (such as the one I work for) seem to have
trouble with the fact that when/if failures occur, everyone will be scrambling for the same resources at
the same time. Your computer contractor will have 50 emergencies to deal with, and still only 3 techs
(assuming telecom is working so you can call for help in the first place). How many fax/copy machines
does the average office supply store keep in stock at any one time? How long to get more? How much
does your business depend on them? How long can you last if 50% or more of your customers and
suppliers are having similar problems? Delayed payments and bankrupt customers can put you out of
business in a heartbreakingly short time.

All of this is assuming a very low level of trouble. If there are any serious infrastructure breakdowns, the
situation worsens very quickly. How long until buildings are burning down from makeshift fires in
January if electric and/or gas service is interupted?

Anyway, again, thanks for a thoughtful post.

-- Jon Williamson (pssomerville@sprintmail.com), December 23, 1998.

greenspun.com