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

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Ken who wrote (8330)8/23/1999 8:56:00 PM
From: John Hunt  Read Replies (1) of 9818
 
Weekend Y2K Newswire Citizen Reports

y2knewswire.com

I was just reading the archived Y2K Newswire Citizen reports from the weekend and these stuck out so far.

(There is not room to display all reports daily on the main site page)

*****

8/23/99 Washington DC Area

My friend works for the phone company so I asked him about Y2K. He said all the employees have been told they are responsible to make sure everything is Y2K-compliant in their areas. A piece of equipment was off-line and my friend suggested to his boss that he go ahead and test it. The boss said, "No, let's wait until January and let it break down so we can get the overtime." My friend decided he would go ahead and check it out anyway once his boss left. He said though since the equipment piece polls the mainframe to get the time, he could not test the date change without changing the mainframe. He said if he changed the time on the mainframe and it crashed he would not be able to bring it back up, so in the end he left it alone and was not able to test it. The attitude of the boss represents a short-sighted and selfish viewpoint which I hope is not too prevalent out there.

*****

8/21/99 Long Island, NY.

I work at a water supply facility on Long Island, NY. We have not done one thing to make sure that the water will continue to flow in 2000. The billing computers will be up and running but nobody knows what will happen at the well sites or booster stations. Our backup systems are a composite of 1960-1999 technologies and never worked correctly as designed in the first place. All of our chemical safeties are controlled by programs that were installed around 1985-86. We have made no system checks and have no plans to do so in the near future. The people in charge have no water pumping experience, they are all paper pushers. Their only concern seems to have been with the billing computers. On the operations end nobody has done a thing. The person scheduled to work New Year?s Eve has already asked for my assistance that night.

P.S.: Put up some extra water on New Years Eve, and fill the bath tub. (Posted by Citizen gussage)

*****

8/21/99 Detroit Michigan

Y2K non-compliant business/financial infrastructure computer systems with ($50,000,000) replaced with DYSFUNCTIONING (unified) DRMS System in APRIL 1999. It was not reported in context of having anything to do with Y2K, although it is. Detroit City Council approved $28,000,000 for IT contractors to use for DETERMINING WHAT THE PROBLEMS ARE. It was also reported that another $50,000,000 may be required to "fix" the system. Final cost... ~$128,000,000! The City of Detroit will be in a "dire financial" situation if the system is not "fixed" in September, 1999. Many of the City of Detroit's 5,000 vendors/suppliers have not been paid and/or have had problems with "bad" computer generated purchase orders. Some vendors have stopped doing business with the City of Detroit for self-preservation. The implications of incompetent management by the City of Detroit are self-evident! The capability of the City of Detroit government to function after September 1999 jeopardizes the HEALTH and SAFETY of ~1,000,000 unwitting citizens. Report broadcast by WDIV-TV, Ch. 4 Detroit, I-TEAM Investigation Wed., August 3 and 4. (Posted by Citizen Robert Mangus.)

*****

The US Navy was all wet with their first report ... NOT!
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext