Government Technology

    Digital Communities
    Industry Members

  • Click sponsor logos for whitepapers, case studies, and best practices.
  • McAfee

Springing Forward Creates Big Issue for Information Technologies


February 12, 2007 By

There is a little-known glitch on the way that could soon confound computer systems across the United States. In 2005 when the Congress passed legislation to lengthen the U.S. observation of Daylight SavingTime (DST), the move was a benign effort to squeeze a little more light out of each of our days. The legislation moved the start of DST forward in 2007 by three weeks -- it will begin this year on March 11, rather than the traditional first Saturday in April. At the close of the season, DST will not end until November 4, a week later than the traditional last Saturday in October.

The problem is that programs like Microsoft Outlook are programmed to make the time switch on the traditional April and October dates. So when the changes are made according to the new DST schedule, programs that depend on a computer's internal clock-calendaring and scheduling applications, for example-won't align with real time.

In addition, many calendaring applications don't simply use the computer clock; they often set their own time flags to facilitate scheduling in multiple time zones. Simply adjusting the computer clock will cause an appointment that was coded for Eastern Standard Time to show up one hour off after the computer clock is updated with the new DST schedule.

If only the computer clock is updated and not the corresponding calendar items, appointments in the changed DST window for this year and future years are all impacted by one hour.

There could also be complications in applications that use time stamped data. Patches should be applied to applications or application environments to make sure that they will correctly handle the new daylight saving time rules.

The Multi-State Information Sharing and Analysis Center (MS-ISAC) released recommendations for dealing with this issue:

  • Identify all time dependent applications.
  • Update and apply all appropriate patches to applicable systems after appropriate testing.
  • Ensure that your users are aware of the change and pay particular attention to calendar entries during the new daylight saving time periods.
  • Validate that all critical systems have the correct time after each rotation of DST to mitigate any possible issues on those hosts.
The DST change is "a big issue for most Windows users" who will have to update their systems, explains Larry Jeannette, enterprise operations supervisor at e.Rebpublic. "Some OSX users may have to update also. At the very least, if your PC isn't updated then it will not automatically adjust itself on the new dates that DST starts and ends, ... items in your calendar will be off during those 'extended' 3 weeks."

The DST issue goes beyond desktop computer systems and extends to things like mobile phones, security systems, and environmental controls. Modern buildings use computerized heating and cooling and access control that are often programmed around typical working hours, for example to unlock entrances, turn on lighting, or adjust heating. Another example might be sophisticated logistics systems that track just-in-time manufacturing processes into a state where parts deliveries may no longer align with workers' scheduled shifts.


| More

Comments

kirk leon    |    Commented February 21, 2007

Personally speaking, I think the US congress should be concentrating on other legislative issues, rather than DST. This is something that we really have no control over. Seasons have been on a course of their own since the beginning of time. There are more pressing matters that need our immediate attention rather that trying to play the role "CREATOR".

kirk leon    |    Commented February 21, 2007

Personally speaking, I think the US congress should be concentrating on other legislative issues, rather than DST. This is something that we really have no control over. Seasons have been on a course of their own since the beginning of time. There are more pressing matters that need our immediate attention rather that trying to play the role "CREATOR".

kirk leon    |    Commented February 21, 2007

Personally speaking, I think the US congress should be concentrating on other legislative issues, rather than DST. This is something that we really have no control over. Seasons have been on a course of their own since the beginning of time. There are more pressing matters that need our immediate attention rather that trying to play the role "CREATOR".

Anonymous    |    Commented February 21, 2007

I was a kid walking to school in the dark when Carter suspended the end to DST. And today I'd much rather commute to work after sunlight - and have time to go jogging before work too. There is no evidence that this will "save energy" - Congress is solving a problem that didn't exist, while leaving major problems (like H-1b visas that displace U.S. tech workers.) If there is time Congress should revoke this bill and return to the standard dates.

Anonymous    |    Commented February 21, 2007

I was a kid walking to school in the dark when Carter suspended the end to DST. And today I'd much rather commute to work after sunlight - and have time to go jogging before work too. There is no evidence that this will "save energy" - Congress is solving a problem that didn't exist, while leaving major problems (like H-1b visas that displace U.S. tech workers.) If there is time Congress should revoke this bill and return to the standard dates.

Anonymous    |    Commented February 21, 2007

I was a kid walking to school in the dark when Carter suspended the end to DST. And today I'd much rather commute to work after sunlight - and have time to go jogging before work too. There is no evidence that this will "save energy" - Congress is solving a problem that didn't exist, while leaving major problems (like H-1b visas that displace U.S. tech workers.) If there is time Congress should revoke this bill and return to the standard dates.


Add Your Comment

You are solely responsible for the content of your comments. We reserve the right to remove comments that are considered profane, vulgar, obscene, factually inaccurate, off-topic, or considered a personal attack.

In Our Library

White Papers | Exclusives Reports | Webinar Archives | Best Practices and Case Studies
Digital Cities & Counties Survey: Best Practices Quick Reference Guide
This Best Practices Quick Reference Guide is a compilation of examples from the 2013 Digital Cities and Counties Surveys showcasing the innovative ways local governments are using technological tools to respond to the needs of their communities. It is our hope that by calling attention to just a few examples from cities and counties of all sizes, we will encourage further collaboration and spark additional creativity in local government service delivery.
Wireless Reporting Takes Pain (& Wait) out of Voting
In Michigan and Minnesota counties, wireless voting via the AT&T network has brought speed, efficiency and accuracy to elections - another illustration of how mobility and machine-to-machine (M2M) technology help governments to bring superior services and communication to constituents.
Why Would a City Proclaim Their Data “Open by Default?”
The City of Palo Alto, California, a 2013 Center for Digital Government Digital City Survey winner, has officially proclaimed “open” to be the default setting for all city data. Are they courageous or crazy?
View All