Y2K COMPLIANCE IN JUDICIARY

The Judiciary is committed to tackling the Y2K compliance issue. All mission-critical computer systems, embedded systems and line communication systems were confirmed Y2K compliant by 30 June 1999.

A Y2K Contingency Plan Working Group was established to co-ordinate the formulation of an overall Y2K Contingency Plan for the Judiciary. Local Y2K co-ordinators - section heads operating in the various buildings and computer system administrators - are fully involved in identifying the possible impact of Y2K-induced disruption on daily business and formulating contingency measures for their respective offices/systems. This involvement has been invaluable as the whole of the Judiciary considers that the Y2K problem is a management problem as much as a technical problem.

The Judiciary has prepared contingency plans to cope with Y2K-induced failure of the embedded systems (Security and Burglar Alarms, Access Control, surveillance cameras and lifts) and line communication systems (Private Automatic Branch Exchanges (PABX), Key Telephone Systems (KTS), Voice Messaging Systems (VMS) and Interactive Voice Response Systems) in each building devoted to major judicial functions and mission-critical computer systems listed at Appendixes I and II respectively.

For each of the Judiciary buildings, the possible disruptions are power failure (including lift failure), security access system failure, telecommunications services failure and transportation failures (MTR; KCR). Contingency plans to cope with these possible disruptions include the deployment of sufficient manpower at public counters to advise the public of the contingency measures in place to cope with Y2K-induced disruptions.

As for the Judiciary's computer systems, they are relatively new. Y2K validation tests have been carried out and during the tests all Y2K critical dates were tested and no adverse impact was found. Nonetheless, contingency plans have been devised to combat any Y2K-induced failure.

The Judiciary has also conducted Disaster Recovery Drills for our CASEMAN, Judiciary Information Systems Strategy Phase I and Phase II projects between July and August 1999. These drills determined that the system and database recovery procedures are workable. The experience gained from such drills has assured us that should system failures occur our current contingency procedures are adequate.

A "wellness check" of our mission-critical systems was undertaken on 9 September 1999, the latest of the Y2K critical dates, and the Judiciary was pleased to report no incidents of system failure. Similar "wellness check" will be conducted on 1 January 2000.

Appendix I

Appendix II