1 / 17

YEAR 2000 CHALLENGE

YEAR 2000 CHALLENGE. Presented By: Francine Sabourin & Lori Anne Jordan. Objectives. Understand the cause and scope of using dates represented by 2-digit years. Identify problems with programs using 2-digit-year data.

faustus
Download Presentation

YEAR 2000 CHALLENGE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. YEAR 2000 CHALLENGE Presented By: Francine Sabourin & Lori Anne Jordan

  2. Objectives • Understand the cause and scope of using dates represented by 2-digit years. • Identify problems with programs using 2-digit-year data. • Understand the importance of planning for your year 2000 migration today.

  3. Agenda Y2K • Introduction • Cause of the Problem • Scope of the Problem • Myths • Six Steps to the Year 2000 Compliance • Industry Preparedness & Event Horizon Analysis • Conclusion • Questions/Discussion/Evaluation

  4. Introduction The year 2000 challenge is a global phenomenon. It poses a significant challenge to the use of information technology. It brings enormous risk for business and government which increasingly rely on information technology as a substantial element of their operations. The challenge is one of the most significant ever faced by information technology organizations and the businesses they support.

  5. Cause of the Problem • Many computer programs make use of dates represented by only two digits. - ie: 95 rather than 1995 • 2000-January-01 is represented as 01/01/00 and might be interpreted as 1900-January-01 rather than 2000-January-01. • It will yield incorrect results when working with years outside the range of 1900-1999.

  6. Scope of the Problem • Spans the entire IT industry • Can exist in any level of hardware or software - BIOS - Real-time clock - Operating systems - End-user developed applications - Databases and files • Might be present on ANY platform

  7. Scope of the Problem • Itmay cause problems when performing arithmetic operations, comparisons, or sorting of date fields. - Your utility company can cut off their services due to your apparent late bill payments. - Credit card holders are refused transactions because their accounts appear delinquent. - Companies may not be able to process its 1999 end-of-year billing or end-of-year payroll properly.

  8. Scope of the Problem • The year 2000 challenge is not restricted to the computing environment alone. • It extends into any piece of machinery that contains a microchip. - elevators - traffic lights - telephone systems - power supplies - cooling systems - fax machines - security access controls - photocopiers

  9. Although your company may be year 2000 compliant, you may still be affected by this problem. You may deal with other companies that are not year 2000 compliant which will in turn cause problems and interruptions in your everyday activities.

  10. Myths about the Year 2000 Myth 1: This is a problem that occurs only after December 31, 1999. Myth 2: This is just a hardware clock problem. Myth 3: This is a problem that only occurs in mainframe systems and/or legacy applications.

  11. Six Steps to Year 2000 Compliance Step 1: Year 2000 Awareness - employees at all levels should be aware of the problem Step 2: Choose Technology Direction - investigate new directions that supports the year 2000 Step 3: Assess Each Application - review each application software

  12. Six Steps to Year 2000 Compliance Step 4: Set Direction - make a decision about each application Step 5: Keep Your Current Application and Update it -install a year 2000 version Step 6: Choose and Implement New Applications -install new software applications

  13. Year 2000 Pricing Schedule Number of lines Price per line of code of code 0 - 500,000 $0.12 500,001 - 1,000,000 0.11 1,000,001 - 5,000,000 0.10 5,000,001 - 10,000,000 0.09 10,000,001 + 0.08

  14. Industry Preparedness & Event Horizon Analysis Banking/Credit Utilities Package Vendors Retail Petroleum Transportation Insurance Securities Manufacturing Level of Industry Preparedness Health Care Communications Government Small Companies 1996 1997 1998 1999

  15. Industry Preparedness & Event Horizon Analysis Australia, US Israel, UK, Canada South Africa, Japan Rest of Western Europe Middle East, India, Eastern Europe 12 mos 9 mos 6 mos 3 mos

  16. Conclusion Time to take action is now! Establish a program to evaluate and convert your systems if necessary. Make all reasonable efforts to avoid any interruption or disruption of service. Intend to minimize any impact of the year 2000 on the services you provide.

  17. Y2K

More Related