How is the change this year going to impact your bank - are your systems set up to reconize the change on the first weekend of April, or by date specific. Caught a piece on the news this morning that this year DST is extended by 4 weeks starting on March 11 and ending November 4.
I was not aware of this change - any others caught unaware
Don't take my word for it, check this site

Here in Indiana, we're new to the whole Daylight Savings Time thing anyway. (The population was split about 50/50 on the question, and it's been a HUGE political issue.)

I think we're going to see a lot of head-scratching and "But I thought you said we switched on . . ."

I've just checked with a couple of Ops VPs and most of our programs have evidently been set to change on the first Sunday of April and they knew nothing of the new date - Wheeeee!! Thank goodness for the Austin paper having an article today!

I'm surprised that the regulators have not issued regulations mirroring the Y2K requirements

Hey FraudBuster, Ind is now going to follow DST? I hadn't heard.

I wondered about this last October. Perhaps this is a Microsoft plot to sell Vista.

Here's an article that lists 10 things to check:

Prepare Your Systems for the Upcoming Daylight Savings Time Changes
A Web Exclusive from Windows IT Pro
February 01, 2007
Blake Eno
Industry Bytes
InstantDoc #95063
Windows IT Pro


In 2005, the government passed the Energy Policy Act, to extend daylight savings time by four weeks, which means that daylight savings time will start three weeks earlier (second Sunday in March) and will end one week later (first Sunday in November). I spoke to Evolving Solutions' Director of Professional Services and Solutions Sales, Chris Taylor, to learn the 10 steps that businesses need to know to prepare their systems for daylight savings time.

1. Identify what platforms you're using in-house.
2. Look at the OSs on what you have.
3. Check with each of your vendors to find out what changes you will need to make to be in compliance.
4. Depending on your vendor and OS, upgrade to a new level.
5. Depending on your vendor and OS, apply suggested patches.
6. Look at the Java code on the box.
7. Apply upgrades or patches as needed.
8. Look at your individual applications.
a) What code are they using? Is it OS time or embedded Java?
9. Consult with each application vendor to receive upgrades or patches.
10. Look at your storage environment
a) Storage Controllers
b) SAN boxes