Widgets Magazine

Cost Savings In Daylight Savings

2014 has flown by as we find ourselves with just two short months before we start with a fresh calendar. This also means that the AV industry is preparing for that last minute rush that comes with the need to resolve budgets in order to retain similar funds for the year to follow. As we begin to plan out the next two months and budget our resources accordingly we do have one last meddling inconvenience to get through: Daylight Savings Time coming to an end.
This year the change happens in the early hours of Sunday November 2nd. Daylight savings time, in the past, was either a source of irritation or a source or money-making service calls. Systems weren’t connected to networks or didn’t have global clocks that triggered the time change which meant that each time the clock sprung forward or fell back a technician was required to go on site to reprogram the system clocks.
I recall many support calls from schools that were utilizing TOA intercom solutions, walking support staff through the proper numerical dialing sequence on the master station in order to get the clock back to where it should be. We have been able to move away from this with the continued push to have more and more equipment linked to the network, which gives it the potential to have a head end clock system in order to get the required information.
However, just because a unit has the ability to be connected to a network does not necessarily mean that it always is. I can think of an instance where a DSP system is currently in use and the primary function is for the calendar to move through presets at specific hours of the day, every day of the week. Having this device connected to the network with VPN access would be ideal, but it just wasn’t an option in the circumstances. This means that the internal calendar stands alone and any slippage of the time clock or failure to recognize when daylight savings time occurs would require someone to go on site, connect, and reset the clock.
This leads to the question that plagues integrators twice a year: how do you handle daylight savings time changes when the equipment in question requires clock operations but is not synchronizing with any other clock system? Is this a call for a programmer? A field technician? A troubleshooting call to the client in order to walk them through the system updates?
We at AVNation want to know what your plans are for this change and how you’re working with clients to ensure that their legacy, stand-alone systems are prepared for the changes. Leave your suggestions, thoughts, and comments below. Perhaps your company’s ideas can lead others to a more efficient and effective way of maintaining legacy equipment.

About Author

No Comments

Leave A Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.