Datenrepräsentation

Die Probleme gezeigt

"Rollover"

Richtige Behandlung: Benutzung des Wertes NotADatum

Struktur-Schaden

Schaltjahr-Fehlberechnung

Die Regel des British-Standards-Instituts

BSI DISC PD2000-1:1998

Betroffene Systeme

• Systeme, die Zeit-Differenzen berechnen;



• sowie Systeme, die offensichtlich nichts mit Zeit-Differenz-Berechnungen zu tun haben

Beispiele

• Ein Aluminium-Sschmelzer in Neu Seeland, der sich um Mitternacht am 30. Dezember 1996 per Notfall ausgeschaltet hat



• Ein Aufzug, dessen Maintenance-System-Speicher rechtzeitig gelesen werden muß - sonst ist das System nicht benutzbar



• Über 50% der von der UK-HSE untersuchten Programmierbaren-Logik-Kontroller (PLC) haben Echtzeituhren und Datumsregister



• Kläranlagen und weitere Beispiele



• Wir schätzen, daß 50%-90% der auf Windows-Rechner-installierte Software nicht vom Hersteller als Jahr-2000-fähig bestätigt worden ist

Sonderprobleme

• Systeme mit "versteckten Uhren"
  
  
• Enormer Ressourcen-Aufwand, um das Problem wirklich zu beiseitigen
  
  
• "Too little, too late"
  
  
• Ignoranz
  
  

Kommentar

• "Dieses Problem ist nicht der Rede wert" (In einem Brief an The Economist)



• "Alle, mit denen ich gesprochen habe, die ihre Jahr-2000-Probleme wirklich untersucht haben, haben ein grösseres Problem gefunden, als sie vorher geschätzt hatten" (Martyn Thomas, ehemaliger Leiter des Global Year 2000 Services der IT-Beratungsfirma Deloitte and Touche, in Konversation mit P. B. Ladkin, July 1998).

Rollover über Zeitfenster

Die RTC ("Real-Time Clock") in PC-Hardware repräsentiert nach IBM das Jahresfeld mit einer zweistelligen Jahreszahl an festen Stelle. Dazu gibt es ein "Century Flag" auf keiner standardisierten Stelle - also keiner festen Adresse.

Es benötigt ein Zeitfenster - eine zweistellige Einzelinterpretation

Allerdings ist bei DOS die Jahreszahl (19)00 kein gültiges Datum - das Datum wird auf 1980 umgestellt.

Gefährliche Daten

Zeitplanung

Der Zeitplan (US Government - General Accounting Office)

Zeitplan der Uni Bielefeld

Capers Jones	-	"Oktober 1997 ist der letzte Zeitpunkt, an dem man ein vernünftigtes Jahr-2000-Programm einsetzen kann"
Schluß	-	Ein Teil der Planung für die Uni-BI muß Schadenskontrollmechanismen beinhalten!

Klassifikation der Problem-Bereiche

Uni-BI-System-Klassifikation

"Assessment"

von
GAO: Year 2000 Computing Crisis - An Assessment Guide

Phase 1: Awareness

• Has the agency defined and documented the potential impact of the Year 2000 Problem?
• Has the agency conducted a Year 2000 awareness campaign?
• Has the agency assessed the adequacy of its program management policies, capabilities, and practices, including configuration management, program and project management, and quality assurance?
• Has the agency developed and documented a Year 2000 strategy?
• Has the agency established a executive management council or committee to guide the Year 2000 program?
• Has a program manager been appointed and a Year 2000 program office been established and staffed?
• Has the agency identified technical and management points of contacts in core business areas?

Phase 2: Assessment

• Has the agency defined Year 2000 compliance?
• Has the agency identified core business areas and processes?
• Has the agency assessed the severity of potential impact of Year 2000-induced failures fore core business areas and processes?
• Has the agency conducted a comprehensive enterprise-wide inventory of its information systems?

  The agency has

  • system inventory listing components and interfaces for each system
  • comprehensive plan to identify and eliminate obsolete code

• Has the agency developed a comprehensive automated system portfolio?

  The agency's portfolio identifies

  • links to core business areas or processes
  • platforms, languages, and database management systems
  • operating system software and utilities
  • telecommunications
  • internal and external interfaces
  • owners
  • the availability and adequacy of source code and associated documentation

• Has the agency established Year 2000 project teams for business areas and major systems?
• Has the agency developed a Year 2000 program plan?

  The agency's program plan includes

  • schedules for all tasks and phases
  • master conversion and replacement schedule
  • assessment and selection of outsourcing options
  • assignment of conversion or replacement projects to project teams
  • risk assessment
  • contingency plans for all systems

• Has the agency identified and mobilized required resources and capabilities?
• Has the agency developed valiation strategies and testing plans for all converted or replaced systems and theis components?
• Has the agency considered implementation scheduling issues?

  The agency's program plan addresses

  • where conversion will take place
  • time needed to place converted systems into production
  • conversion of backup or archived data

• Has the agency addressed interfaces and data exchange issues?

  The agency has

  • analyzed depandencies on data provided by other organizations
  • contacted all entities with whom it exchanges data
  • identified the need for data bridges or filters
  • made contingency plans if no data are received from external sources
  • made plans to determine that incoming data are valid
  • developed contingency plans to handle invalid data

• Has the agency initiated the development of contingency plans for critical systems?
• Does the impact assessmant document identify Year 2000 vulnerable systems and processes outside the traditional information resource management area that may affect the agency's operations?

  The assessment document addresses the impact of potential Year 2000 induced failure of

  • telecommunication systems, including telephone and data networks switching equipment
  • building infrastructure

Renovation

• Is the agency meeting its budget and schedule in the conversion of targeted applications, platforms, databases, archives, or interfaces?
• Is the agency meeting its budget and schedule in the replacement of targeted applicatios and system components?
• Is the agency meeting its budget and schedule in eliminating targeted applications ans system components?
• Is the agency sharing information among Year 2000 projects?

  The agency is disseminating

  • "lessons learned"
  • best practices

Validation

• Has the agency developed and documented a strategy for testing contractor-converted or replaced applications or system components?

Implementation

• Has the agency defined its transition environmant and procedures?
• Has the agency developed and documented a schedule for the implementation of all converted or replaced applications and system components?
• Has the agency resolved data exchange issues and interagency concerns?
• Has the agency dealt with database and archive conversion?
• Has the agency implemented contingency plans?
• Has the agency updated or developed disaster recovery plans?

Program and Project Management

• Has the agency established a Year 2000 program management structure?

  The agency has

  • appointed a Year 2000 program manager and established a Year 2000 program team
  • identified technical and management representatives from each core business area

• Based on the assessment of its program management capabilities, has the agency developed and implemented policies, guidelines, and procedures to manage major program?

  The agency's policies, and procedures include

  • configuration management
  • quality assurance
  • risk management
  • project scheduling and tracking
  • metrics
  • budgeting

Ausgewählte Y2K Links

www.uni-bielefeld.de/y2k/index.html

Offizielle Informationsseiten der Jahr-2000-Taskforce der Universität Bielefeld zum Jahr-2000-Problem.

www.rvs.uni-bielefeld.de/research/Y2K/

Informationen der Arbeitsgruppe Rechnernetze und verteilte Systeme (RVS) zum Jahr-2000-Problem

www.rvs.uni-bielefeld.de/research/Y2K/y2k_links.html

Ausführliche Link-Liste

www.year2000.com

The year 2000 information center

www.y2k.gov

U.S. President's council on year 2000 conversion

www.gao.gov/y2kr.htm

U.S. General Accounting Office - Year 2000 Computing Crisis

www.oecd.org/dsti/sti/it/infosoc/news/y2k.htm

Informationen der "Organisation for Economic Co-operation and Development (OECD) zum Jahr-2000-Problem. Enthält unter anderem den Bericht "The Year 2000 Problem: Impacts and Actions", der die möglichen Auswirkungen des Jahr-2000-Problems auf die (Welt)Wirtschaft betrachtet ("[...]promote global awareness of the Year 2000 problem and its potential economic impact[...]").

www.yardeni.com/y2kbook.html

Edward Yardeni: Year 2000 Recession?

www.faay2k.com

Federal Aviation Administrations's Year 2000 Web Site

www.open.gov.uk/bug2000

Health and Safety Executive: Health and safety and the year 2000 problem

www.iee.org.uk/2000risk

Institution of Electrical Engineers (IEE): The Millennium Problem in Embedded Systems

www.itu.ch/y2k

"Year 2000 Task Force" of the International Telecommunications Union (ITU)

www.ibm.com/IBM/year2000

 

www.digital.com/year2000

 

www.hp.com/year2000

 

www.sun.com/y2000/index.html

 

www.compaq.com/year2000

 

www.microsoft.com/year2000

 

www.utexas.edu/y2k

 

www.ucd.ie/y2k