K compliance is also a lengthy and exhaustive process. A whole gamut of testing must be run against each element to insure that problems do not occur later. One of the biggest problems is that it is not safe to test on a live production system. Thus, resources to create a test environment need to be allocated. This includes powering down the system before a date change and then powering the system up after the change to insure the date rolled over correctly.
Many computers employ a hardware clock which interfaces directly to memory.
These clocks usually have a battery backup. Now is a good time to also change the battery and test your hardware clock. This will also require powering down your entire platform. In many instances this can create a real problem as critical systems must remain on-line all the time . Taking your systems down to implement your new software and hardware fixes can result in a substantial outage of your operation.