Introduction
If you are reading this briefing note, you may already have identified a Y2K problem, whether in your business IT systems or some other product whose functionality depends upon in-built micro-processor technology and is date-based (so called "embedded" software). Or you may simply be concerned about suffering such a problem at some point in the near future.
In either case, you may be a user of the product in question or its supplier and you will know that the problem, whether real or hypothetical, is caused by the product’s inability to recognise the year 2000, either at all or as a leap year. Above all, you will be concerned to find out who is to pay for the cost of rectifying the problem, as well as any other costs suffered as a result, and whether any other liability issues need to be borne in mind.
