Profile Business Automation logo

 Bizauto Bulletin


The Business Automation Bulletin has been published since 1981  

Around the Bizauto web site:

A Year 2000 Action Plan Millennium Two: What To Do 


BIZAUTO BULLETIN 98.2

Guest Viewpoint: The Millennium Crisis . . . Time is Running Out 

About John Ritzenthaler 

Crystal Ball Time, '98 


Other Bulletins 

Who is Business Automation? 

Our services 

Consulting projects 

Expert witness projects 

Home 

 

GUEST VIEWPOINT, BY JOHN RITZENTHALER:

THE MILLENNIUM CRISIS . . . TIME IS RUNNING OUT 

The press has been filled with articles about the year 2000 software crisis.  Briefly stated, any software that a two-digit, instead of a four-digit, year designator will "think" that January 1, 2000 happens 100 years before December 31, 1999 instead of one day later.  You can't be sure you're safe, by the way, just by looking at the dates on your screens are reports . . . the software could be using two-digit dates internally and "tacking on" the 19 at the last moment just before the screen display or print out.  In fact, the problem includes nearly all programs written before 1990 and, surprisingly, many written since. 

If not corrected, this error corrupts interest computations, payment aging, and every other date-based calculation. Unfortunately, the problem is easy to describe but difficult to fix.  So difficult that governments, large corporations and software companies that have in- house programming departments have been working on it for some time and most are still a long way from completion. 

The situation is different for companies that buy their corporate software instead of writing it.  Most of them will have to convert to new or upgraded software must be purchased.  That may be expensive but doesn't appear to require years of advanced planning.  Unfortunately, all the companies that don't plan in advance will face an installation crisis.  As an example, here are some statistics for construction accounting software: 

  • There are about 50,000 medium to large construction companies in the US.
  • Those companies purchase about 5,000 systems per year.
  • Construction software vendors have enough installation expertise to install those 5,000 systems, but most are already facing a shortage of qualified trainers and installers.  It takes as long as two years to properly train an installer.
This makes the average system life span about ten years, but that average is misleading.  Many of the systems sold are to new companies.  Other companies change systems frequently, perhaps every four or five years.  At the other end of the scale, many companies (perhaps as much as 30 percent), have not changed systems in fifteen years or more.  If these older systems are still actively supported and enhanced by a software vendor, their age doesn't matter. 

Unfortunately, most of these systems aren't supported.  Companies using these systems usually have contract programmers who spend a few weeks each year to update the system enough to get along.  Changing the software to support year 2000 dates is a huge task.  Most companies will choose to buy new systems rather than spending tens of thousands of dollars perpetuating an obsolete system. All these companies will want to install new software in 1999.  There's the crisis. 

If the estimates above are correct, as many as 20,000 construction companies will want to install systems in 1999 (the usual 5,000 plus 15,000 older systems).  That's FOUR TIMES the installation capacity.  When the software vendors run out of installation capacity, it will be too late to train new installers.  They will only have two choices.  Some will probably raise their prices significantly to reduce demand and limit themselves to their capacity.  Others will overload their installers, and add new, inexperienced installers.  Being on the receiving end of either of these options will be an unpleasant experience, but the companies that wait until 1999 will have no choice. 

This phenomenon isn't limited to the construction industry, that's only an example.  Any business software which requires significant training and installation will be effected.  And the rush may start well before 1999.  Management can easily avoid the crisis by acting now.  The steps are simple: 

  1. Identify the company's critical software and the support resources for it.  Don't confuse user support with software support.  Find the organization that fixes and enhances the software. 
  2. Get specific information on what will be required to reach year 2000 functionality.  A software vendor may have a simple path for users of their current release, but no path for users that are out of date. 
  3. Identify the resources required for conversion.  This will include internal resources as well as purchased software, hardware upgrades, installation and training. 
  4. If updating the current software is a major commitment, consider installing a new system instead.  This analysis takes time and expertise, but is well worth it. 
START NOW!  Selecting a new system takes at least three to six months.  The new system rush starts this year and there isn't much time left. 
 
  
 

ABOUT JOHN RITZENTHALER

John Ritzenthaler is a systems consultant specializing in the construction industry.  From 1979 to 1989, John designed, developed and installed construction accounting and estimating systems.  Since then he has been consulting with both construction companies and construction software vendors.  His offices are in Portland Oregon.   

Talk back to John . . . your opinion is important.
 

 

Back to the top of the page
Copyright ©1998 Business Automation Associates, Inc.
Bizauto and Bizauto.com are trademarks of Business Automation Associates, Inc.