Y2K problems reach plants, too ...

InTech, Oct 1997

Much has been written about "the year 2000 (Y2K) problem." However, the focus almost entirely has seemed to be on business and accounting systems-those IBM mainframes running mainstream operations whose programming caused the Y2K problem in the first place.

However, the Y2K problem isn't limited to just mainframes and the business accounting department. Engineers on plant and factory floors need to be concerned as well.

The problem, of course, is the fact that, primarily to save programming space, only two-digit designations were traditionally used to designate the day, month, and years during this century (e.g., 10-09-97 for October 9, 1997). It was widely assumed by programmers and systems designers that hardware and software upgrades would eventually make the problem moot by the year 2000.

However, many legacy systems and applications have nevertheless survived. Even PC-based programs developed on older 486 or earlier hardware and Windows 3.x or earlier (i.e., DOS) operating systems are all candidates for potential problems.

The goal is to achieve what's called "Y2K compliance," which, simply put, means using code that includes four-digit year designations or facilitates recognizing them. At least two major SCADA manufacturers, Intellution and Wonderware, have come out with methods to ensure Y2K compliance, as have some control and enterprise-linking software suppliers. Microsoft's latest operating systems also are Y2K compliant.

Although Y2K still is some 800 days away, major business organizations are already spending billions to fix their legacy systems, including those on plant floors. Cathleen C. Judge, a Philadelphia lawyer who specializes in information technology law, reports, for example, that customers at the top of the automotive and pharmaceutical industry supply chains are already requiring their suppliers to certify Y2K compliance on the factory floor as well as in their information systems.

Perhaps, however, Y2K problems can be turned into opportunities. Since some older systems must be overhauled, why not seize the opportunity to consider doing some technology leapfrogging?

After all, it could be another 1,000 years before top management is again so heavily motivated to spend millions of dollars to upgrade computer systems. IT