Name of Proponent: James Christopher Anderson Email: slug@fast.co.za Organisation: Y2K CINDERELLA PROJECT
Essential aspects are:
1. Simplicity 2. Speed 3. Practicality 4. Minimum cost
Government resources for Communications and Media campaigns appropriate to scope of effort.
Email and Internet access, appropriate Admin and Communiications facilities.
Project must be set up within 3 months. July 1 1998 is "drop dead" date to support mainframes. First milestone: Awareness campaign (start latest June 1998) Second milestone: Critical Risk Status (after 6 months) Third milestone: Plannned activities on target (ongoing) Final milestone: Readiness (Mid 1999)
1. Committment. The potential for economic damage and and factual existance of the problem is known. However, there is a severe lack of awareness and total lack of committment.
2. Time. The technical constraints imposed by the problem imply that immediate action must be taken. July 1 1998 is probably the last date by which an effective plan can be mounted. After that, Triage and action by Priority will be necessary.
3. Mixed environment. Mainframes and PC/Lan systems have totally different problem sets and must be handled separately.
4. Budget. The lateness of the approach may cause difficulties with budgeting. Budgetary allocations for the next 18 months have already been made.
5. Skills. Y2k skills are not readily available in the affected areas. A communications network will be necessary to provide remote support for technical issues.
6. Staffing. Skilled resource will be difficult to obtain in light of existing world-wide shortages and escalating rates
7. How to "Sell" this concept. The "Marketing" or "persuasive" aspects of "selling" any solution to affected governments must be addressed.
- reporting to Cabinet - six weekly report back to Government - own discretionary budget - competent to manage a National Emergency - powers to compel testimony
1. to identify and monitor Risks to Infrastructure
2. to promote awareness of Y2k across all economic sectors
3. to identify and report back on Problem Situations
4. to coordinate a master plan (timetable) for Government
departmental remediation
5. to recommend Strategic action plans to avoid disasters
6. to investigate and recommend Contingency Plans
7. to develop Competence and disseminate Information
8. to man a "Hotline" and National Support Centre
9. to assess and if necessary Certify Compliance
10. To coordinate a National Risk Assessment Document, by
Economic Sector
2. This coordinating body to liase with the Y2k Centre to identify special Y2k problems and risks within the industry sector and assist in the Awareness campaign and compilation of the National Risk Assesment Document.
CENTRAL GOVERNMENT REGIONAL GOVERNMENT LOCAL GOVERNMENT ELECTRICITY WATER TRANSPORT TELECOMMS HEALTH ACRICULTURE RETAIL PETROCHEMICAL MANUFACTURING LEGAL ACCOUNTING GENERAL PUBLIC
1. Introduction to the Y2k Competence Centre Methodology 2. Year 2000 Tutorial 3. Year 2000 Solutiuons for Small Business 4. Skills for Y2k 5. Effective Systems Testing
AWARENESS ASSESSMENT REMEDIATION VALIDATION TESTING IMPLEMENTATION
List of Y2k-related Articles List of Y2k-related Websites Consolidated Compliance Statements Database Consolidated Embedded Systems Database Consolidated Medical Equipment Database List of Authorised Business Analysts List of Authorised Remediation Service providers List of Current Y2k-related Tenders
Standards Evaluation of Tools Glossary of Terms
Local Definition Local Contract Warrant Wording
Immediate Start: 470 working days
Late start: 394 working days
Drop Dead date: 1998-07-01
Support for Y2k Life Cycle:
Early Start Late Start Target Milestone
1998-03-17 1998-05-01 2000-01-03 AWARENESS
1998-03-17 1998-05-01 2000-01-03 ASSESSMENT
1998-03-17 1998-07-01 2000-01-03 REMEDIATION
1998-03-17 1998-07-01 2000-01-03 VALIDATION
1998-03-17 1998-07-01 2000-01-03 TESTING
1998-03-17 1998-07-01 2000-01-03 IMPLEMENTATION
OPTIONAL MILESTONES
1999-03-17 1998-07-01 1999-01-01 Year End Testing
1998-03-17 1998-07-01 1999-01-01 Euro compatibility
CONSTRAINTS
Project must be set up within 3 months.
July 1 1998 is "drop dead" date to support mainframes.
First milestone: Awareness campaign (start latest June 1998)
Second milestone: Critical Risk Status (after 6 months)
Third milestone: Plannned activities on target (ongoing)
Final milestone: Readiness (Mid 1999)
Task the National Medical Council to certify Medical Devices.
Fitness and completeness (at planning stage) Viability (on Project setup) Effectiveness based on Mesurement against Objectives (every 3 months)