1. INTRODUCTION 
2. GOAL 
3. STRATEGY 

1. Top to Down
2. Down to Top

4. ACTION 

1. Y2K Project Organization
2. Y2K Project Management Procedure
3. Y2K Project Contents
   1. Inventory
   2. Risk Assessment
   3. Recovery Plan and Executing
   4. Contingency Plan
   5. Testing
   6. Internal Auditing
4. Y2K Project Progress
5. Y2K Initial Budget
   

5. APPENDIX: High Risk Date Tests  

1. INTRODUCTION

   the Information Technology Division presents this proposal to be the solution that may solve the Millennium Bug existing in FOXCONN systems. Included in this document are goals and strategies of this project, methods adopted, and the contingency plan measurement.

2. GOAL

1. This project proposes solutions and contingency measures to each division and department, helping them to solve the Millennium Bug in schedules, and to minimize the inconvenience and impact.
2. In addition to computer systems, the embedded systems also need to be investigated in detail.

3. STRATEGY

1. Top to Down

Awareness of Y2K
Education & Training of Y2K
Y2K Project Plan
FOXCONN Y2K Project One-Page
Audit Plans

2. Down to Top

Detail the Responsibility of Facility Management
Y2K Organization
Propose Y2K Test Schedule and Tool and Methodology
Inventory & Assessment Report
Risk Evaluation & Budget
Recovery Plan
Emergency Plan
Y2K Commitment from Vendors

RETURN TO TOP

4. ACTION

1. Y2K Project Organization

   

   RETURN TO TOP
    
2. Y2K Project Management Procedure

   

   RETURN TO TOP
    
3. Y2K Project Contents
   1. Inventory

      

   The most important and basic step for the Y2K Project, is to control all internal software & hardware systems in the office, including information & non-information systems. The more complete inventory of these systems, the easier its future risk assessment & and subject recovery. It will also help to substantiate the problem range of Y2K.

   RANGE

   Information systems

   Systematic documents (or detailed lists): Most brochures & records of recovery are included. Referring to risk assessment. All lists have to be filled in its document title & published date as well.

   Systematic environment: As much as information facilities & operation systems should be completely evaluated instead of ignoring them, ex: PC, Server, voice mail system, Database, WAN, LAN, telephone exchange, accumulating system, Monitors…etc.

   Applied system (concerned with dates): All software in sets, operation software, self-designed ort their names, manufactures & issued dates.

   Available labor resources: All contact details and telephone numbers should be well kept, including the chiefs from all systems, specialists from Y2K Project, full-time & part-time employees.

   Business clients: offering help to our clients if they have any problem of Y2K, ex: EDI, Mail system, Fax Server…etc.

   Non-information systems

   Manufacture, produce, storage and equipment: Manufacturing systems, control of manufacturing programs, robot, auto-controlled production, package, transfer stops and systems of central-control are included.

   Instruments for inspecting products: Various analytic or measured instruments & experiment ones are included.

   Adjacent environment: Fire alarm system, security system, electric-power control, lightening, parking-lot system, elevator, material-control, waste water, environmental protection…etc are included.

   Development of new equipment and system: Designed assistance by computer, project analytic system, inspection system: & instrument for demonstration.

   Products: Referring to our guarantee of products for clients, all products are under testing.

   Substantial steps

   To label as an identification while passing through Y2K test.

   

   
   RETURN TO TOP
    

   1. Risk Assessment

      Analyzing business impact and rate of break down by assessment from the inventory & rank them by influence on production. Their ranking will be done in time in order to keep business on as usual.
      Take out the items with date problem from inventory: They are classified into 3 as follows:

      1. The items without clear dates at all
      2. The dated items without Y2 K problem
      3. The dated items with some problems of Y2K problem.  (This is the main task for us to complete)
      
      Document the items with date problem: First of all we must know the influent degree of the items with date problem, the put its influence on production on record. Its influence will be measured by 5 degrees accordingly from original vendors to update programs or substituted for others.

      

   2. Recovery Plan and Execution

      All office resources will be available for recovery plan. Which are handled by central information. The departments only need to follow their operation. About the rest part which have to be repaired, we may ask help from other departments or try to get some similar information from network to shorten our working time. All necessary labor resources will be available from the inventory. Labor resource is part of recovery plan too.

      Recovery plan is concluded to be elimination, renew, recovery, amendment, accordingly. The steps for recovery plan are:
      According to the data Risk assessment, Recovery plan is arranged by risk ranking to help vendor’s complete recovery.
      Do our best to repair those that are still workable. Any renew or elimination shall be followed company’s plan & cost.
      Some independent facilities can be changed on time if necessary. The prerequisite is to know Y2K influence from original vendors and have Recovery plan first, then follow company’s decision to make any amendments if needed.

   3. Contingency Plan

      Emergency plan is executing together with Y2K Project, but based on not influencing business operation. Standard operation process, training & substituted equipment are included in emergency plan.

      Steps:

      1. Confirming the failures : Controlled and executed by Recovery plan, we pick out those which cannot be repaired right away or still under recovery.
      2. The influence of failure assessment: We’ll complete this failure assessment according to prior influent assessment & the percentage of well-done recovery, except those which have been 100% repaired to be workable.
      3. Emergency substitute: The following will be taken if necessary: changing auto-controller into hand-made. Managing stocks of raw materials and products, substituting products, labor assisting etc. consideration. All’s completed by documentation.

   4. Testing

      The computer will imitate future dates to set up a separate testing system, ex: Checking the input date over the year of 2000 or not. Updating automatically or not. No matter the guaranty of products from vendors is available or not, the testing proposal should be presented. The details of testing will be put on record to make sure their appropriate testing process and results. They also can be sent to our clients for identifying Y2K test ready. Here are 3 steps:

      1. Non-information system: product information should be gotten from vendors first. All testing & possible results should be confirmed as well. Then the date will be set in peril of Y2K for testing if the internal system is with timing or mercury battery. The detail of testing will be recorded. In order to get better solution any difference will be reconfirmed with vendors.
      2. Systematic environment: The purpose of testing aims to make sure all hardware & software without any Y2K problem. The data exchange will be able to continue under such an environment while the year of 2000 comes. Testing is in 3 steps as follows:
         1. All works at present set-up dates.
         2. Test computers on and off under dangerous dates of Y2K.
         3. Test systems in the interim of Y2K (ex: 1999/12/31 23: 55) wait and see after 10 minutes if the system environment changes.
      3. Applied system
      4. Set-up of data testing: Take out some trade records from old files & modify their operation flow with dangerous dates of Y2Kfor testing Notice that its interim should be between the years of 1999 & 2000.

         Test Operation  Flow: Non-It System

         

         Test Operation Flow: Systematic Environment

         

         Test Operation Flow:  Application System

         

   5. Internal Auditing

Executive: Team of Central Y2K

(1-1) The Purpose of Y2K Project.

Surely to promote & put Y2K Project in action through internal operation in order to make all organizations & their additional departments discover blind spots while working and offer the solutions to guide all departments to complete company’s well.

(1-2). The Objects of Y2K Project.

All organizations and their additional departments, including the factories and selling site in TAIWAN, Mainland China, America, Singapore …etc.

(1-3). The Proposals of Internal Audit.

(1-3-1). The organization and job distribution of internal audit team:

President: Executive secretary from Central Y2K, who’s in charge of audited objects and items.

Committee: Members from Central Y2K, who are in charge of confirmation of audited dates upon attendance, the data-searching from audited departments & audited reports,

(1-3-2). Internal audit process

(1-3-3). Internal audit details

(1-3-3-1). The tasks being executed from central Y2K

(1-3-3-2). All listed tasks on controlled form of Y2K Project

(1-3-4). Internal audit procedures

(1-3-4-1). Paper audit: The confirmation of the data from all organizations and its departments one punctual and completed.

(1-3-4-2). Attendance audit:

(1-3-4-2-1) Monthly audit: Once a month punctually.

(1-3-4-2-2) Casual audit: available at any time if necessary.

(1-4). The Correspondence between All Organizations & Departments. All audited items must be identified and well-informed to audited authorities, including all necessary documents & time. Attendance participates have to be applied in advance if necessary.

(1-5). The Relative forms.

Controlled procedure forms of Y2K project, internal audit records & inspection forms.

4. Y2K Project Progress

   

5. Y2K Initial Budget

Initial budget --- NO LIMIT

RETURN TO TOP