| At 7 AM EST Dec. 31st, one of the most important events in the
history of humanity, will
take place . As the clock strikes midnight on the international date line, we will enter not only the 2000 series of years; we will start to see the results of the first "global" technological effort to mitigate a problem. A few aren't going to make it.The questions are:
We do know that some companies will try to fix on failure. The problem with this approach is that some businesses will not be able to survive after the failure, before the fix; or for long after the fix. The vast majority of industries have already applied corrections. Still, some percentage of those corrections may fail. The rate of failures will vary across industry groups and across political borders. We can't know the absolute extent of the problem at this time. If we had begun work on the problem 10 years ago, we might have. We have now reached the point in time in which it serves little purpose to cast about for recriminations. If everything goes well, then well; but, if things go badly, blaming individuals or groups will serve no productive purpose. Later, there will be time to study the issue of why things went the
way they did, and how
we could do it better in the future.
It is only when people feel that they have been betrayed, that civil
disobedience occurs.
We don't know what will happen. The best, most intelligent thing we can say is that we believe that most major industries and most industrial countries will be largely unaffected. This is the "official" view. Financial institutions and all major corporations have been taking the
problem seriously.
The United States Government has more legacy computers, computer software and hardware than any five governments in the world, yet it spent around 9 Billion Dollars in five years to fix it's Y2K problem, out of a budget of around 6,000 Billion Dollars that was spent in those years. We do know enough about the problem of remediation to know that there
will be some
failures. There are several different types of failures possible
with the Year 2000 problem.
Most of the problems caused by Y2K failures will occur for a period of time after the New Years. Some corporations and governments do not like it to be known when they are experiencing a problem. Some problems, however, can not be hidden. Disruptions in critical infrastructure are likely to be reported immediately and widely. Yet, most Y2K related problems will not be reported. On December 31st companies in some industries will be playing it safe. They will shut down for a period of time and restart their operations after the New Years celebration, just to make sure. When they bring their systems back online, they will test them, to see if they can be safely operated. The operators of our critical infrastructure systems have contingency plans to facilitate the operation of the whole system, if there are break downs in parts of the system. Yet, there can be failures, that could cause cascading affects through out the whole of a critical infrastructure. The risk of this kind of failure varies greatly among industries and among nations. Every day there is some risk of these types of failures. The risk is very small, but the consequence of the risk is a large enough so that people should take actions to prepare for the possibility. How much reason we have for preparing, because of the Y2K problem, is unknown; but we do know, that the consequence of risks before us every day, is justification enough for preparedness, without Y2K. What we at The Disaster Center know is that most families are not prepared
for disasters
of any type. We are advocates of preparedness, mitigation, response
and recovery from all
possible disasters.
We invite you to stop by our site at 7 AM EST on New Years Eve day as
we monitor the
events around the world. Consider stopping by our chat room and
use our message
boards to share your observations. This is our first Global effort to mitigate a potential technological disaster, we hope that this leads to future cooperation around the world. One of the most important results could be a new unity, which will lead to other global efforts to mitigate technological and natural disaster risks; and greater cooperation for sound technological and environmental development. Christopher Effgen
Happy Holidays,
|
World Year 2000 Information Directory
FEMA a Guide for Emergency Managers PDF
Y2K Contingency Planning --
Overview, Initiation,
Business Impact Analysis, Contingency
Planning
Testing
Year 2000 Program and Project Management
Organization Year 2000 Program Phase or Activity Questions:
Awareness
Assessment
Renovation
Validation
Implementation
Program
Management
Executive Order 13073
Year 2000 Conversion
Organizations Year 2000 Program Phase or Activity
-- Processes:
Awareness -- Assessment
-- Renovation -
- Validation -- Implementation
-- Program Management
Sen. Bob Bennett's
Year 2000 Page
The Disaster Center Index Page
Gartner
Group -- Hot Content
Nuclear Utility
Year 2000 Readiness
Nuclear Regulatory Commission
Year 2000
CSB - Y2K and Chemical Safety
National Guard Bureau Year 2000
Suggested Steps of Y2K Community Preparedness
Gary North's Y2K Links and
Forums
Microsoft Windows 98 Year 2000 update
Individual Preparation For Y2k
Some Free PC tests will identify problems that are not likely to cause you problems in operating your PC's.
While technicaly failure of the RTC to perform a live Y2K roll over does indicate a problem, virtually all computer programs
use time as reported by the PC's BIOS, not by the computers RTC. Use your own judgment..
Norton 2000 BIOS Test/Fix
Other PC Y2K tests
Is Your Mental Software Year 2000 Compliant?
Food And Drug Admin
Year 2000
GSA's Telecom Y2K Testing
and Validation...
FAA
Year 2000
The Information Technology
Association of America Year - 2000
DCI Year - 2000
Cap Gemini America’s - Year 2000
U.S.A. Dept. of Labor - Year 2000 page
U.S.A. Dept. of Energy - Year 2000 page
U.S.A.D.A. - Y2K and food supply
FEMA Year 2000 page
U.S. Postal Service Y2K
FDA Year 2000 Impact on Biomedical Equipment
Federal Government's Gateway for Year 2000 Info.
CDC and the Year 2000
Vendor 2000 -- Product Compliance
ITAA Year 2000 Vedor
Directory
Year 2000 Information Center
Global Year 2000 Crisis
Rep. Horn's
YEAR 2000 Progress Reports
Embedded systems
and Y2K
Embedded systems and
Year 2000
SIM Year 2000 Working Group
Y2K for Women
Dr. Ed Yardeni's Year 2000
Site
Insurance Information
Institute's Y2K page
Chief Information Officer's
Y2K Site
Usenet: comp.software.year-2000
Building Owners and Managers
Association Y2K
UK's CITU Action 2000 Website
Sanger's Review of Y2K News Reports
2000 and You -- news reports
Year 2000 Press Clippings
is Y2KNET
Washington D.C. Year 2000 Group - The oldest local Y2K Group
U.S. Coast Gaurd and Y2K
Maritime -- Ship2000.com/
U.S. Dept. of Transportation Year 2000
Maritime -- Safety Issues
The Energy Plan
The Year 2000 (Y2K) Computer Problem --
A computer programmer's view
Year 2000 Bulletin
Board: For the latest related news and notices
Volunteer opportunities
through the Disaster Center
Disaster Center
Bulletin Board Directory
Computer Information Center
Y2K
National Crisis Response Institute
Y2K
UN -- The Year 2000 Problem (Y2K) and Developing Countries
The National Communications System -- Y2K
FAA Y2K
FAA Y2K and Airports
Compliance information sources: Use with care! They and We do
not assume any responsibility for the information!
Vendor 2000 Compliance
database
Y2K Consumer Information
1984 Y2K Magazine Article
DISA
Product Compliance Catalog
Federal Year 2000 COTS Product
Database
Hardware &
Software Year 2000 Compliant
Year 2000 Software
Tool Vendors
Year 2000 and Visual
Basic
Westergaard Year 2000
Y2K Emergency Management
Alaska Year 2000 Group
Software Manufacturers Year 2000 sites: If you know of any not
listed here send us an E-Mail! year2000@disastercenter.com
Not all these Manufacturers have Year 2000 problems or so they Say!