It's a scenario that would be perfect for InfoWorld's "Off the Record" column (or a "Dilbert" comic): An executive committee dictates a seemingly minor change to the company - but it requires the IT staff to invest hours in tweaking and patching and prepping systems. Shortly thereafter, the higher-ups decide the change isn't worthwhile -- something they might have predicted with a little research -- and all of In this case, the executive committee would be the U.S. Congress, and the seemingly minor change is the forthcoming extension to Daylight Saving Time (DST), for which IT folks across the country have been scrambling to prepare. (If you’re behind, here are some tips on where to start.)An alert reader (to borrow from Dave Barry’s vernacular) cited an article on LiveScience.com in which a Department of Energy spokesman is quoting saying that the extended DST “might be a one-year deal” if the energy savings don’t prove significant (whatever that means).As I noted previously, there’s already been one study suggesting that, indeed, energy savings from the longer DST will be, at best, negligible, and at worst, detrimental. Of course, at this point, all we can do is hope that all the system-prepping IT’s been doing proves successful, and that somehow, the longer Daylight Saving does put a dent in the country’s energy consumption. Technology Industry