A Feb. 1 graphic on the change to daylight saving time contained incorrect times for sunrise and sunset in the Washington region on March 11. Sunrise will be at 7:26 a.m., not 7:04 a.m., and sunset will be at 7:11 p.m., not 6:46 p.m.
Clocks' Early Spring Forward May Bring About a Few Falls
Thursday, February 1, 2007
It seemed so simple and familiar: Spring forward, fall back. For 20 years, that's what Americans -- and their technology -- have done with their clocks on the first Sunday in April and the last Sunday in October.
No longer. When few people were paying attention in August 2005, Congress lengthened daylight saving time by four weeks in the name of energy efficiency.
The change takes effect this year -- on March 11 -- and it has angered airlines, delighted candy makers and sent thousands of technicians scrambling to make sure countless automated systems switch their clocks at the right moment. Unless changed by one method or another, many systems will remain programmed to read the calendar and start daylight saving time on its old date in April, not its new one in March.
It's one thing to arrive an hour late for church on the first day of daylight saving. It's another for a security system to log the wrong time of crucial events, for pilots to misunderstand their takeoff times or international communications components to stop synchronizing. But such scenarios are possible without the fix to vast numbers of the nation's technical systems .
As IBM notes on its Web site: "Any time-sensitive functions could be impacted by this change. . . . It is important for users to assess their environments and develop appropriate plans for applying the necessary changes."
The challenge carries faint echoes of the Y2K scare, when governments and corporations feared computer systems would go berserk the instant that 1999 flipped to 2000. But it has received nothing near the same level of attention. In fact, large swaths of private and corporate America seem oblivious to the approaching change, according to analysts and technicians who track Web sites and swap information with colleagues nationwide.
"After building bunkers in the desert for Y2K, we're not even talking about this, and it's happening in less than two months," said Matthew Kozak, an information technology specialist at Rutgers University who monitors numerous sites and discussion groups.
Even in the banking industry, where ATMs time-stamp every customer transaction, awareness of the March 11 change is limited.
"I haven't heard about it," said Barry Koling, spokesman for Atlanta-based SunTrust Banks. "It seems to me, we managed to get through Y2K. If we can accomplish the change of the millennium, we can handle a change in daylight saving time."
For many widely used devices, automatic updates should be easy. Cellphones should flash the correct date and time because they get such information from their service providers' networks. Similarly, the Internet will automatically update clocks on many personal computers that use relatively up-to-date software.
But Microsoft cautions that some of its older products -- including Windows XP SP1 and Windows NT4 -- will require manual updates. The company's Web site provides detailed instructions on how to update various products, although it is pushing against the deadline in some cases. Updates and tools "are being developed and tested," the Web site says, and some will "be released through early March 2007."
As a fallback, Microsoft urges customers to double-check meetings scheduled during the four weeks being added to daylight saving time this year.