Daylight-savings changes: No Y2K but there could be headaches

January 25 from Network World – “At first blush it may seem like no big deal: clocks will move ahead by an hour three weeks earlier than usual this year. But for today’s networked businesses, the simple change could mean complex problems if IT shops aren’t prepared, industry experts say.

The trouble goes beyond missed meetings and messed-up schedules to errors within time-reliant applications that are critical to a company’s business — processes such as operating room scheduling, billing and contract deadlines and ensuring record compliance, for example, could be at risk. Any applications dependent on timestamps will run into trouble after March 11, the new day for the daylight-saving time change, if actions aren’t taken.

For more than two decades, daylight-saving time has begun on the first Sunday of April and reverted to standard time on the last Sunday in October. But beginning this year, due to the Energy Policy Act of 2005, the daylight-saving schedule will be extended by a month, with the period beginning on the second Sunday in March and ending on the first Sunday in November. Legislators backing the change say it will save some 100,000 barrels of oil a day.

But the change also could throw a wrench in IT systems set up to automatically handle the old daylight-saving schedule. As a result, IT professionals need to take a close look at their systems and applications to determine which could be off when the change occurs and then take the necessary steps to correct them.

180 View – It seems like a reasonable precaution to check this out on your systems.