Blog: My ‘Automation vs Control’ Pet Peeve
Control Panel
Photo courtesy of Somar International Ltd./Flickr
Get with the program: Control is not automation. Automation is not control.
Buyer beware: The terms 'control' and 'automation' are often incorrectly used interchangeably. Our guest blogger explains the difference and why it matters.
By Mark Coxon

with a tool or tools, in this case the stick and the clutch. An automatic transmission shifts the gears without any input or control from the driver, hence it being called ‘automatic.’ The car uses a mechanism like a speedometer or RPM sensor to tell the car when to shift gears.

In a like manner, A/V companies can add great value to clients by creating automated systems that use related queues to automatically control the system without requiring the user to provide input. Using sensors to detect occupancy, light and temperature; or utilizing PC-based systems with daemons installed; or providing power management that not only powers down devices but also switch outlets to avoid phantom power draws all lend to true automation.

When talking about A/V systems, we diminish value when we confuse terminology like automation and control. We build value when we differentiate between the two. There are many systems that may never require automation, and where control will suffice. In other cases, if automation is the goal, a unique approach and component list may be necessary.  Only when we are able to explain the differences coherently can we become the true resources our clients are looking for, which helps all of our businesses in the end.TD End Icon Final 14 px



Comments
Posted by Jeffcmag  on  04/25  at  08:15 PM
"My pet peeve is that most of the ‘automation systems’ sold in the market do not involve automation at all, or they involve very limited automation. Merely adding a Crestron, AMX, Control4, or Savant processor and touch panel to a system is not ‘automation.’" Crestron,AMX,and Control4, certainly are automation systems. They take a set of customizable commands and automatically complete a task. "When a user pushes a button to accomplish a goal, that is not automatic. It is not automation. It is control." To use your corollary, like an automatic transmission, you shift into drive and the transmission shifts automatically, you press a button to turn on your home entertainment system, the Crestron or other system switches on the monitor, the cable box, the audio system, closes the shades, dims the lighting, etc. And just like the automatic transmission there are customizable selections for specific tasks, like park or DVD, reverse or turntable, low or second gear or HD or SD. That is why it is always referred to as automation and control. You are just speaking about the level of automation. If you don't have to get up and walk to the TV to turn it on it is automation. If you use a stick to press the button from your seat it is automation. Control is the cause, automation is the effect.
Posted by Mike G  on  05/01  at  11:35 AM
Jeffcmag, I disagree. The example of using a stick to press a button from your seat is the exact opposite of automation. When you have a standard hand held remote control for your TV, pressing the button on the remote to change a channel does not mean your set is automatically changing channels. It is certainly easier than getting up and walking to the TV stand, but it is not automation. A stick or a remote are both considered tools in that example. Using a tool to accomplish something does not make it automatic. That would be akin to saying using a shovel to dig a hole is an automated process compared to digging it with your hands. While a shovel is certainly preferred, it does not make the process automatic. In addition, having one button perform multiple tasks, is also NOT automation. That is what is called a macro in programming. Automation is something that happens without additional user input. Rain sensing windshield wipers and daylight sensing headlights are automatic. The driver does not have to do anything when the conditions programmed into the system are met. So for an A/V system, having a current sensor installed in a conference room, so that when the system detects a laptop connected to a cable in the system, the projector turns on, the lights dim, the screen and shades come down and the switcher selects the correct input all without the user having to press or adjust anything is automation.
Posted by Jeffcmag  on  05/01  at  12:25 PM
Mike, In your sense, automation does not exist. All automation is a programmed set of responses to an, or a set of, inputs. "In addition, having one button perform multiple tasks, is also NOT automation." "So for an A/V system, having a current sensor installed in a conference room, so that when the system detects a laptop connected to a cable in the system, the projector turns on, the lights dim, the screen and shades come down and the switcher selects the correct input all without the user having to press or adjust anything is automation." The difference is in semantics. There is no difference between a button press and a current sensor. (a switch) That current sensor does the exact same thing as the button except that there must be power to the current sensor, which must be activated by a button.(switch)and then to complete a set of programmed responses. It cannot decide whether you wish to use the projector, the electronic whiteboard, or the video conference system. You must perform some manual task to do what you need the system to do. Without any input there is no output the rain sensor cannot detect rain with the vehicle off. The meeting room cannot do anything without someone plugging in a laptop. It is all a programmed input/output. Unless and until machines can read our thoughts and act upon or, (shudder) what they decide is best, then there will be no true automation.
Page 1 of 1 pages


Commenting is not available in this channel entry.