Time, and Time Again
This Sunday night it's going to be nice and light an hour later than usual, thanks to the Daylight Savings Saving [Ed. note: Thanks, Scott!] ...
This Sunday night it's going to be nice and light an hour later than usual, thanks to the Daylight Savings Saving [Ed. note: Thanks, Scott!] time change. That's not particularly welcome news to government IT staffs. State and local IT employees have been racing against the clock to make fixes to the machinery of government.
This year the time change is occurring three weeks earlier than usual due to a little-noticed -- until relatively recently -- provision stuck into a 2005 federal energy policy bill. Instead of changing the clocks the first weekend of April, as usual, the time change is scheduled for three weeks earlier.
Electronic equipment does as it is told, and it is virtually certain that some applications and systems will be off by anywhere from a day up to the total three weeks. It doesn't seem that bad if we're just talking about missing meetings. (That might even be desirable, in many cases.) But I imagine there might be some very scary possibilities.
Do the gates that keep people off train tracks go up and down according to an internal clock that needs to be changed? Have they all been changed? What critical business processes are at risk out there? Can you fill us in on worst-case scenarios or what you're worried about in your region? Or are you too busy scrambling to make sure they're going to work properly by 2 am Sunday morning?