Agenda Packets - 1999/02/01 - Laserfiche WebLink

Home Browse Search

COPING WITH THE YEAR 2000 PROBLEM: A CHECKLIST TECHNICAL RESPONSES What is a Y2K-Compliant Community? A Y2K-compliant community is one in which all functions, ❑ Inventory systems. both privately and publicly operated,within a local com- ❑ Test for compliance. munity will be operating and interacting normally into the Hardware year 2000 and beyond. Operating systems An automated system is Y2K-compliant when it will Custom code process normally,as it was designed,(i.e.without any Applications Data interfaces extra processing, procedures,or other manual interven- tion) before,during and after January 1,2000. ❑ Analyze results. ❑ Prioritize. Critical systems that don't involve traditional data processing:traffic control, water-systems controls,etc. Critical data processing systems: accounting,human resources,etc. Systems whose loss would disrupt operations. Systems whose loss would create minor inconvenience. Systems that are extraneous and/or candidates for replacement. ❑ Fix or replace hardware. Fix: requires appropriate technical skill. Replace with compliant hardware: replacement is an expensive option,but it may be the only realistic one for many systems. It also becomes riskier as we get closer to 1/1/2000. ❑ Fix or replace software. Fix the code: requires access to code and appropriate technical skills. Replace with compliant custom or off-the-shelf software. Outsource(at least temporarily)the process to a service bureau whose system is compliant. Live with cosmetic problems or minor inconveniences until they can be finally fixed. ❑ Fix or replace embedded systems and interfaces. Make sure that the same efforts to identify problems, prioritize them,and then fix or replace systems as appropriate are directed to automated systems in elevators,water systems,and building security systems. Don't overlook interfaces with outside business partners. -8-