1998-07-23_AgendaPacket - Laserfiche WebLink

Home

¢ III 'S~HRONICLE 2000, continued from page 1 your hardware, custom applications, interfaces, off-the-shelf software packages, and equipment that may rely onembedded computer technology (firmware). Knowing what you have to deal with is a major first step and will help you determine which of your assets are mission-critical. You will find different levels of criticality to your systems: some that you MUST have; some that you should have but can do .without for a short time; some that are nice to have but can do without for a long time, and; some that are not necessary any longer. This is the perfect time to create a library of your systems for future projects and to discard antiquated systems. .~issessment. Make a determination regarding the compliance status of all assets. For computer hardware, packaged software, telephones, fleet vehicles, fax machines, and copy machines, obtain compliance information from your vendor. For custom applications, examine programming code with programming tools and experienced programmers. For tirm~vare, call the manufacturer or maintenance vendor to request compliance information, in writing, about your elevators, security systems, and heating and cooling systems. Be aware that vendors are continually testing their products, so compliance information can and does change. Revisit this aspect routinely. Desi,;n a Project Plan. .-after completing the assessment, the compliance options for each asset must be evaluated and decisions must be made. Five compliance options are available: ~ Renovate-fix the problem,~or reprogram your code. ~ Replace the .information. resource with a Year 2000 compliant asset. ~ Upgrade the information resource, so it is Year 2000 compliant. Retire or discard the system. ~ Keep the status quo--continue using the information resource with the understanding that it is not Year 2000 compliant. Conversion and Itnplementation. Execute and implement the conversion options chosen. Complete the tasks outlined in your Year 2000 Conversion Project Plan. Contingency plans need to be thoroughly formulated. Few major systems renovations are completed on time, so be sure contingency plans are given proper consideration. Plans for those systems whose Year 2000 issues are not being addressed at this time are also important. Manual processes may have to be implemented for the time being. itilake sure that all key players are trained in the changed processes. your business continuation. Big Stone County, for example, is surveying vendors and business partners to assess their Year 2000 readiness and the impact on county operations. START PLANNING OW! This. is an unusual challenge-even for information technology gurus. The entire globe is dealing with the same problem, needing the same resources, and facing the- same deadline. Delays in getting started with your Year 2000 project could mean trouble in finding qualified people to help you resolve the issue, or inability to receive compliant equipment due to shortages. It will definitely mean higher costs due to simple economics. The supply of qualified people and resources dwindles every day as the demand increases. Delays in starting projects will impact your chance for success. Don't delay any longer! ONGOING AWARENESS awareness is an important and ongoing part of the project. Inform your coworkers, councils and elected. officials of the challenge and the consequences of doing nothing. Familiarize the organizations you influence. monitor. regulate, license or audit with the Year 2000 challenge. Make sure your suppliers. service providers and business partners are aware of the challenge. Their lac:: of preparedness could afr"ect Plan carefully, plan thoroughly, but start planning now! See ?000, page S t , `~ ~' ;. . iL ~ { ~~~~ ~~ r << r < r `~ ~'..