Daylight Saving Time change = mini y2k?
Although this sounds like a simple change, it has forced many organizations to assess the impact of Daylight Saving Time on their business that reminds me of the global y2k worry about the change from December 31, 1999 to January 1, 2000.
Any system that is dependent on timestamp-based data (airline reservations, hotel and car rental, ATM machines, shipping, appointments, etc.) will have to be assessed to gauge the impact of the time zone change. This could lead to a lot of late nights and crossed fingers as operating systems, databases, and application code are patched to address timezone-related issues. As an IT consultant, I have seen both ends of the spectrum with this issue. I have one client that has already addressed the DST issue, and I have another client that didn't even consider investigating impact of the DST issue on their business until I mentioned it.
In my opinion, this DST change will probably cause some minor disruptions, but nothing along the lines of the y2k scare. Even so, I will probably be checking out my bank and brokerage accounts on March 11th just in case...