There are many terms for the issue, Year 2000 virus, Millennium bug, or Y2k challenge. Whatever you choose to name it, the problem spans the entire IT industry and includes any system, equipment or software application that uses 'date' data. While an industry standard does not exist for Y2k compliance, it is generally accepted that Y2k compliant means that systems are capable of normal operation into the 21st century. There are three main areas of concern:

• malfunction in any way related to the year roll over from December 31, 1999, to January 1, 2000
• malfunction in any way related to dates after the year 1999
• incorrect handling of leap years, meaning non-conformity to the rule: "every 4th year is a leap year, excluding century years, but including every 4th century year". Making the year 2000 a leap year on the final clause.

At enSpire we have addressed the problem and taken every precaution possible to ensure that we are Y2k compliant. This includes are internal system, facilities and our suppliers.