Daylight Saving Time will begin three weeks earlier than it has in the past.
Are you prepared for the issues that may result?
Not only may employees be an hour off schedule for a meeting during those
three weeks, but other potential problems exist as well:
- Credit card transactions that don't process properly
- Time clocks that incorrectly determine lateness and overtime hours
- Scheduling software that doesn't get people or equipment to the right place,
at the right time
- And many, many others.
So why are we facing these issues?
The U.S. Energy Policy Act of 2005,
passed by the U.S. Congress in July, 2005, extended Daylight Saving Time
(DST) in the U.S. by approximately four weeks. As a result, beginning in 2007, DST
will start three weeks earlier on March 11, 2007, and end one week later
on November 4, 2007, resulting
in a new DST period that is four weeks longer than previously observed.
However, the issue is not only a United States based problem, as Canada
and other countries are conforming to the U.S.-mandated change.
While many people are aware that a change is needed for the operating system
of their personal computer, if you're not considering your software applications
and other equipment that operate on a time sensitive basis, you may be exposing
yourself to problems that could cost you valuable time and money.
And, depending
on whether you are updating a single computer or a whole network, the actions
you need to take may be simple or complex.
For example, if you're using a computer with Windows XP Service Pack
2, this link will
take you to a patch that can be downloaded to update your machine. In fact,
if your computer is set to receive and apply automatic updates, your machine
probably has been already updated. But, you will still want to verify it.
However, what if your business still has machines with Windows 2000 or Windows
XP prior to Service Pack 2? Well, unfortunately, those operating system versions
are no longer supported, and no patch is available. This doesn't mean that
you can't correct the time on the machine, you'll just need to do so manually.
And you'll need to remember to do so again in November, due to the extra
week on the back end of DST.
If your computer is attached to a network running Microsoft Exchange, patches
must be applied to the server(s), as well as to the Outlook client, in a
specific sequence. In fact, Microsoft has advised that "Users should
view any appointments that fall into these date ranges as suspect until they
communicate with all meeting invitees to make sure that the item shows up
correctly on everyone's calendar both internally and externally."
Although we have been using Microsoft products as an example so far, does
that mean that the problem is limited strictly to them? Of course not.
Whether you are using applications from Apple, Sun, Oracle or any other computer
provider, you need to apply the same types of updates and due diligence
for them as well.
And don't stop at the operating system. The software applications themselves
may also have DST considerations. In general, if you utilize programs that
are sensitive to time, you should verify any updates that need to be applied
directly to that program software.
Also, don't
limit your efforts to your PCs and networks. You need to consider the
effect on your handheld PDAs, credit card processing equipment, time clocks
and even the automated thermostat. Again, any piece of equipment that is
affected by time needs to be verified.
Many people are making comparisons to "Y2K". Except in this case, there
is not so much a question of "if" something will happen, as much as "what" is
going to happen. It's safe to say that every business does need to address
this issue. The harder question to answer is, what exactly do you need to
do about it?
We've tried to help you identify the places where you need to look. You'll
probably find that most companies have created a fix that handles the problem,
whether it be a software update or a manual set of procedures. Unfortunately
though, the burden of making sure that every instance is addressed falls
to you.
For our part, if you have questions on what we have provided you, please
let us know. We will be happy to address your particular situation. Please
contact
Alan Ogilvie at info@computerworks.bc.ca
or for more information
604-552-4008.
