It is no longer the case that directors can sit back passively and ignore an issue like the Y2K bug unless and until management raises the issue. Reports from employees or experts with relevant expertise need to be sought, and acted on in a timely way. The difficulty in making computers and machinery Y2K compliant is not so much the complexity of the task, but the time and resources required to eliminate the Y2K Bug. Businesses which rely on the use of future dates may encounter problems with their software when entering data that contain dates in the year 2000 and beyond. Making your system Y2K compliant may involve reviewing hundreds of thousands, if not millions, of lines of source code.
Experts recommend that a large company allows itself one year to test rewritten code.
You may have to obtain more than one consultant to cover all of your technology. To ensure that your system and office equipment is Y2K compliant, you should first conduct a full system audit. You may also wish to seek confirmation of Y2K compliance directly from your IT supplier. The relevant documents may include supply agreements, licences, maintenance agreements, and correspondence. If your IT supplier is responsible for rectifying the Y2K Bug, then you should seek to have the problem sorted out immediately.