To: Jeff Mizer who wrote (9531 ) 12/27/1999 3:56:00 PM From: flatsville Read Replies (1) | Respond to of 9818
Picked this up courtesy of a poster to csy2k who found it in another newsgroup-- It it's true...Yikes!...Sounds like a Fortune 1000 company hitting the wall. In article <847psc$3sh$1@nnrp1.deja.com>, TheAlligator <thealligator@my-deja.com> wrote: > As I mentioned many months ago, I've been doing Y2K remediation work, > with a large > midwestern corporation my main focus. They started over 4 years ago on > this huge project. > Replaced mainframe systems with clustered AS/400, 100mbs fiber optic, > upgraded routers and > so on, running IPX/SPX backbone on a group of a rather esoteric brand of > servers in a class > commonly known as superserver. Dozens and dozens of distributed NT > servers, UNIX servers > all running TCP/IP over the backbone. Untold millions of dollars just > for the infrastructure > upgrade. Started installing the major piece of critical application > software immediately after this. > After 1-1/2 years of outrageous fees, software costs and 24/7 shifts of > work, the project was > deemed unworkable, scrapped, all involved forced to sign non-disclosure > agreements, and still > in litigation even as I speak. > Immediately began the new vendor selection process again. To make a > long story short, this project > was finished mid-1999. In November, major Y2K problems began surfacing > in this multi-million > dollar "Y2K-compliant" project. Still unresolved, litigation pending. > Mission-critical system. > > Document imaging system died in November. Work-in-progress new version > slammed into > production. Despite vendor claims, non-compliant. Litigation pending. > > Major multi-million dollar accounting/workflow system, in production > since 1/99. Latest Y2K > upgrade not released until 2nd week of this month. After test > installation, MAJOR year 2000 > issues uncovered, also vendor Y2K fixes introduced major flaw which > disallows system- > generated offset transactions for automated in-flow feeds from all other > corporate systems. > Vendor gave up, now in the hands of Micro$oft. ABSOLUTE MISSION > CRITICAL. > As of today, on 1/3/2000, this company can no longer make payroll, pay > vendors or anything > else. Counting down the hours. Obviously, MAJOR litigation pending if > no fix. Unfortunately > this one is in my hands. > > Enough of the software problems - no need to continue, you get the > picture. > Semi-trailer sized generators are in place, with the building wired to > run the entire company > manually on 2 floors. Lists of people permitted on the premises for a 1 > week rollover generated. > VERY much beefed up armed security presence in place. Diesel and > gasoline tankers in place. > Water truck, food and medical supplies in place. Armed security in 4wd > vehicles with maps to > key employee/consultant residences. Entire corporate security > infrastructure from controls to > cabling to door controls replaced (non-compliant). Phone systems > replaced. > > I have made it clear that if the situation is so dire that > implementation of the emergency plan is > required, I will NOT comply. Think Y2K is no big deal? You're gonna > take the ride of your > life for the next 5 years. God be with you all. By the way, what's the > official corporate PR > statement? "Y2K - We're OK". Sound familiar? Believe it? You're an > idiot. > > > Sent via Deja.com deja.com > Before you buy.