Y2K Site Map | Terms of Use | Problem | Steps | Certification | Briefings | Compliance | Solutions | BIOS | Test & Evaluation | Cost

The following Y2K material has been kept available by MITRE for historical purposes only and has not been updated unless noted.

Year 2000 Remediation Process Flowchart

1. Y2K Project Office, upper left. This is the oversight focal point for the entire process. As the chart indicates, the prime functions are receiving, understanding, and forwarding for appropriate action all Y2K Directives; determining reporting requirements; and understanding, communicating, and coordinating Y2K Compliance Criteria. Further, all Y2K Status reporting to higher authorities should be via this same single focal point.
   
   
2. Programs, center. This set of activities represents the various offices or individuals responsible for developing, testing, fielding and maintaining the company's systems. For Y2K remediation, these individuals will be further responsible for carrying out the actions specified in their respective Transition Plans, producing the Year 2000 Certification Package, coordinating Y2K testing, and fielding their certified systems. Also, each office must make timely Y2K Progress Reports to the oversight Y2K Project Office (above) as required.
   
   
3. Y2K Progress Reports, center-left. The Y2K Progress Reports, as already mentioned, go from the Programs to the Y2K Project Office per the requirements of the Project Office, for compilation, metrics reduction, and formatting for presentation and reporting to higher authorities.
   
   
4. Program Management Plan (PMP), Configuration Management Plan (CMP), Implementation/Renovation, Verification Plan, and Contingency Plans, right. Each Program Office or similar activity must develop an approach, scope the necessary tasking, and set a Y2K schedule which must be strictly followed, since the deadline is immovable. During the remediation efforts, each activity will have to complete a systems inventory, determine the Y2K status of each system component, be capable of stating the basis of each such assessment, develop and pursue renovation plans, develop and pursue test plans and scenarios, and develop post-deployment contingency plans, as applicable.
   
   
5. Certification Tracking Document (CTD), lower-right. Each activity will have to document all test results, including a rationalization of all failed tests, and incorporate all required information, including a completed Year 2000 Compliance Checklist into the Year 2000 Certification Package for each system.
   
   
6. Year 2000 Certification Package, top-center. The Year 2000 Certification Package for each system includes its Transition Plan, all assessment and test documentation, the completed Checklist, and any other required documentation. This is an essential milestone and an absolutely mandatory step before going on to the next activity (dashed line).
   
   
7. Certification Process, lower-left. With coordination among trading partners, suppliers, and other interfacing companies, each system with its completed Certification Package then proceeds to functionality and interface conformance testing. This standard conformance testing is augmented with Year 2000 testing scenarios and data to ensure interface and standards compliance has not been impacted by the Year 2000 remediation efforts. This is the final activity before the system may be deemed compliant and ready for fielding.

   Fielding, bottom. Now certified as compliant, each system is to be fielded and checked out as expeditiously as possible, well before its Time Event Horizon. In this final step, system-of-system testing must be performed, and refinement of operational, site-specific contingency plans must be completed.

   ---

   
   For further information directly related to Year 2000 issues, please contact Year2000@mitre.org