For informational/historical purposes only.

N E W S W I R E

ohio department of transportation internet news release

FOR IMMEDIATE RELEASE: February 24, 1999
Division of Information Technology

ODOT's Year 2000 Response Letter

Thank you for your inquiry regarding the Ohio Department of Transportation, the State of Ohio, and the Year 2000. I would like to take this opportunity to update you regarding the Ohio Department of Transportation and the State of Ohio's position on possible Year 2000 issues. In an age that is dependent upon technology and computer systems, the State of Ohio's agencies, boards and commissions are very aware of the issues surrounding the Year 2000 problem and are taking steps to ensure that state government systems and processes are in place to address these issues.

The "Year 2000 problem," as you are aware, arises when software and embedded systems have been written to store, manipulate or display dates using only two digits for the year (e.g., 98), assuming that the first two digits of the year are 19.  This assumption was regarded as a necessity in the early days of commercial computing because of the limitations of computer memory. Many organizations may need to make changes to parts of their information technology and process systems to ensure that their business will continue to be reliable into the next century. The Ohio Department of Transportation is aware of the Year 2000 problem, and, as a provider and regulator of critical services to the citizens of Ohio, we are endeavoring to minimize the impact of any Year 2000 problems.

Ohio is working to ensure that its systems function correctly and can deal with the coming century date change. State agencies are focusing on the following:

1. Conducting internal calculation of dates on software and systems
2. Initiating storage of date/time information on machine readable media (e.g., tape and disc)
3. Reviewing date entries made by users and how software/systems interpret date entries
4. Analyzing storage of dates and how dates are displayed
5. Examining vendors, service providers, and customers' efforts to address the problem
6. Maintaining awareness of the problem internally and with the customer base
7. Reviewing agency regulatory oversight responsibilities


ODOT's overall Y2K status includes five major categories; Legacy/Enterprise Systems, Networks & PCs, Dependencies, Facilities, and Data Interfaces.  The overall completion percentage for the five categories is 97%.  To see a complete chart click here. More specifically the category Legacy/Enterprise Systems(Critical Applications) that attracts the most interest is 98% complete.

Simply stated, Ohio's goal is to ensure that state government systems and business processes are Year 2000 ready.  The Ohio Department of Transportation fully expects to be Y2K compliant by November 1999. 

A good resource for information on the Year 2000 problem and the State of Ohio is the Ohio Year 2000 Competency Center's Web site: http://www.oy2k.state.oh.us/. This site includes information concerning the Y2K problem as well as links to other Y2K sites.