Resources and advice for managing IT issues related to Daylight Savings Time changes

How to prevent business continuity problems linked to the new DST start date.

This page will be updated as more resources become available. Refresh your browser to make sure you are reading the latest version.

IBM press release and list of affected applications
In 2007, US Daylight Saving Time (DST) is changing and will begin on the second Sunday in March and end on the first Sunday in November.

The US Energy Act of 2005 drove this change, aimed at reducing energy consumption. The new schedule will make US Daylight Saving Time four weeks longer and will have implications for certain technology products.

The DST change will affect computers and applications with date and time processing functions in the US, as well as Canada and Bermuda where start/end DST dates conform to the US change. You may be affected, for example, if you use calendar or scheduling functions, if you are dependent on date and time stamps, or if you process or manipulate dates or times. Organizations in countries not implementing the DST changes could be affected if they support users, transactions or applications originating in the countries that are changing DST. For example, applications or systems that interact with the US involving calendar notices should be updated.

It is important that you assess your IT environment and develop plans for a smooth transition to the new DST schedule. While this is an industry-wide issue, rather than specific to a particular company or technology, many IBM products will be affected by the new schedule.

Information about the IBM products affected and the DST rule changes are posted on the IBM support site here.

Sun Developer Network
US Daylight Savings Time Changes

Novell SUSE LINUX
US Daylight Savings Time Changes

Microsoft resources:
http://support.microsoft.com/kb/914387
http://support.microsoft.com/kb/931667
http://support.microsoft.com/kb/923953
http://blogs.zdnet.com/microsoft/?p=250

SIFMA resource center

If you have not yet prepared for DST, below are a few tips to help you start preparing for DST.

1. Create a checklist of hardware, software, applications and other IT systems vendors used by your organization. Be in contact with each one to get the most up-to-date information. Keep a running list so that you’ll know which items are taken care of and which you’ll need to manually update. 2. Notify your staff of the DST issue, so that they will be prepared for any minor glitches that might occur on March 11th.

3. Remember the DST end date, November 4th, so that you are properly preparing your system to handle the start as well as the end of DST.

4. Test your system in advance of March 10th so you know in advance which glitches you might face, and which you can solve before the DST change.

5. Work with your firm to create contingency plans in the event that any disruptions might occur.
Gartner recently issued DST implementations, they include the following: NEW
* After applying patches or manual fixes, conduct tests to verify that the proper times and dates are produced.
* Review all applications and their interactions with other applications for DST change compliance.
* Check with external service providers to ensure that they are modifying their own systems to comply with the changes so your systems are not negatively affected.
* Have IT personnel scheduled to be available during the DST change on March 11 so they can repair any problems that arise, and give them well-defined escalation procedures to deal with any circumstances.
* IT departments should schedule twice-yearly reviews prior to DST shifts to confirm that systems are working smoothly and to correct any problems that occur.

What to Watch Out For
While there are many areas of your IT system that need to be reviewed, some issues to pay close attention to include:
- Batch processes
- Backup windows
- Time stamps when trade books are hand-over between geographic locations
- Messaging systems time stamps and workflow
- Applications using hard coded calendars
- Global applications outside of the US which US users use

As well as the checklist above, SIFMA has published a very useful list of patches, updates and support services offered by software vendors. View this at http://www.sia.com/business_continuity/html/dst.html

Gartner advice:

Gartner warns of potential global business continuity implications of US changes to Daylight Saving Time dates

General articles on this subject:

Wake up and patch the OSes

Get out of the dark with looming Daylight Savings Time changes

Where Did the Time Go?

Springing forward earlier may cause glitches

Prepare Your Systems for the Upcoming Daylight Savings Time Changes

Daylight Savings Time Comes Early: Are You Ready?

Daylight Savings Bug

DST threatens computer stability in 2007

Prepare Your Systems for the Upcoming Daylight Savings Time Changes

•Date: 9th Feb 2007• Region: US/World •Type: Article •Topic: IT continuity
Rate this article or make a comment - click here
UPDATED 14TH FEBRUARY