

|



Sometimes You're the Bug!
by Kristin Johnson
If
you are among the world of the computer literate, you have probably heard
of the millennium bug, also known as Y2K.
Here is the Problem
Many of the world's computers use two digits to represent a year. Using two
digits to keep track of data on January 1, 2000 will cause computers to recognize a double
zero "00" as being year 1900 and not year 2000. When the date changes from
December 31, 1999 to January 1, 2000 systems and equipment that are not Year 2000
compatible will face two problems.
The inability to determine the correct date.
Not knowing the correct date can have serious repercussions such as causing electronic
equipment to stop running, producing erroneous data or producing no data at all.
The inability to tell the number of elapsed
years between two dates. This problem could prove to be fatal in certain instances where
dates are important such as in dealing with medicines and expiration dates.
Who Will Be Effected
Everyone
-- most of the world's economic sectors have become dependant on the electronic
processing and exchange of info. An interruption in computer driven data
systems could mean an interruption in every aspect of life including financial,
health, transportation, and economic growth. The global economy is also
at risk. Any failure -- the inability of a stock market to open, difficulties
with banks processing transactions, slowdowns in commuter traffic due
to malfunctions in traffic signals, power companies unable to provide
power to customers, disruption in food production, food spoilage due to
the failure of computer operated food storage or delivery refrigerated
systems. The nation's food supply is a good example. Food suppliers are
heavily reliant on computerized processing and information exchange. Farmers
and ranchers use electronic equipment to water fields, feed animals, milk
cows, and transport what they produce. Processors rely on automated systems
that help prepare and
package consumer-ready products. Distributors, wholesalers and retailers
rely on computer driven equipment to order, bill, keep inventory counts,
transport, deliver, store, display and sell products. Any interruptions
long this chain could result in a direct loss to those who supply food.
This can result in more expensive, less available food.
What Equipment Will Be
Effected
Equipment that has embedded chips need to be reprogrammed. Examples include:
large mainframe computers like those used by the federal government, banking, insurance,
manufacturing, large agricultural production and processing centers and major food
retailers. Small businesses including small farmers, processors, and grocery stores with
non-Y2K compliant hardware and software are at risk. Equipment with time-dependant
embedded computer chips are vulnerable: harvesting equipment, milking machinery, grain
elevators, plant and truck refrigeration systems, grocery and restaurant cash registers,
telephones, gas and water facilities and plant assembly lines.
What The Federal
Government is Doing
Internally,
the government has been working on their own systems to ensure that their
equipment is Y2K compliant. They are making inventories of all their data
exchanges with outside business partners. For high-risk areas, agencies
are developing contingency plans to ensure that they will be able to conduct
business even if their systems, or the outside services on which they
depend, are not available. Externally, the government is undertaking a
massive outreach program aimed at making private-sector organizations
aware of Y2K problems and solutions. The President's Council of
Year 2000 Conversion has established federal working groups in
key U.S. economic sectors such as finance, transportation and health to
provide this outreach. The Department of Agriculture is leading the government's
outreach effort to the food supply sector, working with the Departments
of Defense, Heath and Human Services and State and the Commodity Futures
Trading Commission. These departments have been asked to coordinate an
outreach campaign in the food sector because all have food sector constituents.
This outreach campaign, coordinated by The Food Supply Working Group has
identified nearly 100 broad constituency categories that are involved in food production
or distribution. It is working closely with industry and other groups to raise awareness
about the Y2K problem and possible solutions.
What You Should Do
The Food
Supply Working Group suggests six steps to ensure readiness for the year 2000. Every plan
should include:
Awareness: Make everyone --
from employees, suppliers and service companies aware of the potential for Y2K problems
and what it is going to take to get your systems compliant.
Inventory: Conduct an
inventory of every automated system in your operation - automatic feeders, irrigation
systems, utilities, communications, accounting, and conveyors. This should include
hardware, software and embedded chips. Any of these systems could be vulnerable to year
2000 problems.
Assessment: After you have
identified your automated systems, write or call the manufacturer and ask if their system
or device is Year 2000 compliant. Ask for written confirmation through an official letter
if the system is compliant, and if not, ask for instructions on how to proceed if it is
not.
Solutions: If you can not get
an official letter of compliance in a reasonable time before the year 2000, you need to
determine which systems are most critical and need immediate attention. Set priorities for
dealing with your systems and address them in that order.
There are three options for addressing systems that are not Y2K compliant:
Upgrade systems to the latest Y2K compliant
version, if available.
Replace systems with systems that are Y2K
compliant.
Fix systems by scanning all systems and
programs to check for date routines or date storage fields and fix them to create
compliance.
Testing: The next step is
testing. To properly test the system, the date on the computers should be reset to
01-01-2000 and run it for an extended period.
Contingency Planning: A good
contingency plan should include ways to back up and protect your business's data, ensure
continued production with limited delay, ensue continued cash and product flow, and make
clear the responsibilities of key employees during any Y2K mishaps.
Y2K impacts not only your operation but has the potential to affect your
interaction with support services, such as banks, supply warehouses, transportation and
more. A solid contingency plan must consider the potential impacts to your business if any
of these systems fail.
Don't be caught off guard when January 1, 2000 rolls around. Remember --
sometimes you're the windshield -- sometimes you're the bug!! Take the steps necessary to
be prepared! For more information on Y2K, point your browser to http://www.year2000.com. |