![]() |
![]() |
| Governor's Task Force on Year 2000 Readiness |
Q: What is Y2K?
Y2K stands for Year 2000. It is an issue regarding the way dates, specifically year information is stored and manipulated by computer systems and specialized devices that rely on calculations that involve dates.
Q: Why is Y2K a problem?
Two digit storage. During the 50's, 60's, 70's and even into the 80's, computer chips and software applications identified the value for the year with just the last two digits. This means that 1969, 1978, 1985 and 1999 are stored as 69, 78, 85, and 99. When date calculations are performed on dates within the same century, the calculations are accurate (ie. 1999-1985=14). But what if the date is actually 1885 or 2085? Then 1999 - 1885 =104, but 99-85 still equals 14.
A lot of information processed by a computer can be accurate when using the two-digit date representation. The concern is that systems may fail or provide incorrect information resulting in the delay of shipping of critical components for manufacturing or delivering incorrect amounts or on the wrong date.
Leap year calculations. The Year 2000 is a special case leap year that only happens every 400 years. Leap years are calculated in computers by a simple set of rules, but not all of the rules programmed noted the special 400 year case. So, there are systems that do not recognize the year 2000 as a leap year. This may cause all dates following February 29, 2000 to be offset incorrectly by one day.
Q: Can't we just switch computer codes from two to four digits?
The conversion from two to four digits is only the tip of the Year 2000 iceberg; The problem begins with finding all the places where two digit year codes are used in computer applications and extends to careful testing of systems after conversion has been completed. The problem is further complicated by the thousands of devices with embedded chips that control everything from building environmental systems to personal computers.
Q: What is the scope of this problem?
It is the scope of the Year 2000 issue and all the affected systems and business processes that makes the problem so large and challenging, not its technical nature.
Every piece of hardware, software and every embedded computer system must be taken into account, from Colorado's central tax accounting systems, to desktop PC applications, to air conditioner thermostats in public buildings. They must all be examined for date-handling and how those dates might affect Colorado state business.
Q: Is all of the hype about the Y2K problem justified?
Various experts have issued widely differing opinions about the potential impact of Y2K. The fact is that nobody really knows what will happen on January 1, 2000. But the major fear is that a non-compliant device or application in one location will cause other devices or applications to fail.
For example, even a Year 2000 compliant computer application could be corrupted by non-compliant data from an outside source. Likewise, the failure of an embedded chip in one part of a complex system could cause a chain reaction failure in other parts of the system. Thus, while predictions of widespread economic and social chaos seem unjustified, it is important to do as much as possible in the remaining months to avoid more serious complications later.
Q: Have we already experienced Y2K problems?
Year 2000 problems have already been detected in many businesses that deal with long-range dates (life insurance, mortgages, etc.) as well as shorter- range items like credit cards. The problem is real and must be addressed.
Q: How serious is the Y2K problem for Colorado state government?
Colorado has a large number of computer programs and systems to be checked and remediated. From March 1997 to May 1997, nearly 850 different items were inventoried and of that number, 714 had potential Y2K problems. The problem is massive, but, with aggressive leadership, it is manageable.
Q: We've heard a lot about embedded chips. What will happen if non-Y2K- compliant chips fail?
Nobody really knows how big this problem is without looking; between 5 and 50% of factory system devices have chips that may fail in some way. Significant time and energy has been and will be devoted by Colorado's agencies to setting up testing mechanisms to verify that systems dependent on embedded chips will continue to operate normally following the millennium.
The same processes used in other Y2K efforts also work with the embedded chip problem.
Q: What is Colorado's state government doing to address the problem?
Colorado has taken extensive and aggressive steps to address the Y2K problem. Colorado's new Governor, Bill Owens, has moved swiftly to address the Y2K problem by convening the Governor's Task Force on Year 2000 Readiness. Created by executive order, the Task Force includes members of the Owens Administration; state legislators; and representatives from the public, private and non-profit sectors. Task Force members are addressing the Y2K challenge on three basic levels:
Within state government, Governor Owens has recently taken an important new step to accelerate our Y2K efforts: He has created a single Statewide Year 2000 Project Office within the Colorado Department of General Support Services (GSS) to address all computer networks and embedded systems in state departments and agencies. Previously, this responsibility was split between two governmental entities, with GSS handling computer networks and the Office of State Planning and Budgeting (OSPB) responsible for embedded systems - that is, equipment and appliances with computer microprocessing chips.
Q: What is the Governor's Task Force on Year 2000 Readiness?
Recognizing the need for a statewide forum to coordinate the private and public sector's preparations for the Y2K problem, Governor Owens issued an Executive Order establishing the Governor's Task Force on Year 2000 Readiness.
Governor Owens selected some of the best-qualified public and private sector people for the Task Force. Areas covered by the Task Force include:
Q: What can we expect from the Governor's Task Force?
In the coming months, the Task Force will assess the progress of state government and different areas of the private sector. The Task Force will make recommendations for Y2K compliance. And, perhaps most important, we will communicate this information to the public.
Q: What's the cost to fix Y2K?
The current figures (Oct 1998) estimate US costs to be about $150-$225 billion; with worldwide costs about $1-$2 trillion (Gartner Group, 7 Oct 1998). For Colorado State Government, we estimate the costs to be around $33 million.
Q: Why is this figure less than other states?
This is a dynamic calculation and at this point, this figure does not include the embedded chip issue, nor does it include higher education.
Q: What about some specific systems? For example, will the traffic lights work? How about the prisons? What about our income taxes?
Traffic lights. Colorado's Department of Transportation has assured us that the traffic lights that the State controls have been assessed, tested and will work correctly. However, remember that some traffic signals are managed by counties and local jurisdictions, so be careful when you are driving after the New Year in 2000.
Prisons. The Departments of Public Safety and Corrections are working hard to ensure that all of its systems are ready, including its criminal justice information systems and the security and control systems for its correctional facilities. They will be extra diligent after the New Year to be sure systems are working correctly.
Taxes. Citizens should plan to pay their income taxes just as they do every year.
Q: Will Colorado's state agencies be converted and tested in time for January 1, 2000?
State government has set an aggressive schedule of deadlines and benchmarks in order to ensure that we are ready for the millennium.
Q: Many of Colorado's state services depend on federal programs. What is the federal government doing to address Y2K issues?
Many of Colorado's citizens depend on federal systems for services such as social security, air traffic safety and national defense. Colorado's state agencies are working closely with their counterparts at the federal level to ensure a smooth transition to 2000.
For more information of the federal government's progress with Y2K issues, contact the President's Council on Y2K information line at 1-888-USA-4-Y2K or visiting the website at http://www.y2k.gov.
Q: What about the utilities like electricity and telephones?
Information about Public Service Company's Y2K efforts can be obtained by calling their Y2K information line at 303-294-2000 or visiting their website at http://www.psco.com/Y2K.
Information about U S West's Y2K efforts can be obtained by calling their Y2K information line at 1-800-800-0811 or visiting their website at http://www.uswest.com/year2000.
Q: Should we stock up on food and water?
We can't guarantee that there won't be any problems, but doomsdayers out there are off base. As a matter of fact there is an entire cottage industry in our country that is cashing in on Y2K fears.
We recommend following the guidelines set forth by the American Red Cross. More information about emergency preparedness can be obtained by calling the Mile High Chapter of the American Red Cross at 303-722-7474 or visiting the American Red Cross website at http://www.redcross.org/Y2K.html.
Q: Is there a Colorado emergency contingency plan in case of widespread Y2K failure?
We know we cannot be 100% certain that every system, or even every critical system will be fixed. In the event of problems, we have worked with the Office of Emergency Management and other state agencies to develop contingency plans.
Q: Where can we learn more about the state's Y2K efforts?
For more information about Colorado's Y2K efforts call the Y2K hotline at 303-620-4281 or visit the Colorado web site at http://www.state.co.us/Y2K.