John dealt with this next-to-useless law back when it was passed.
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.
“The problem is very wide and not very deep,” says Steven Ostrowski, a spokesman for Computer Technology Industry Association. “It’s going to cause a lot of little headaches instead of big Y2K-type issues. But people need to be prepared.”
Folks who weren’t involved with the IT side of preventing problems during Y2K think it was no problem — without understanding all that was done to make it no problem. Everything that communicates and is hooked into a corporate network — including phone systems, email servers, etc. — contains time stamps.