I have extracted excerpts from three lead articles from "The Automator" that approach Internet convergence from very separate perspectives. The overall message that the Net is here to stay is extremely clear.
From the article with the most online reads for July and August, "Web-based Control Systems: The Devil is in the Details," by Steve Tom, director of technical information at Automated Logic:
"Manufacturers have forced themselves to develop a complete toolkit for their Web-based system. For them, the question 'Does the user have to do this through a browser?' becomes an edict 'The user will be able to do this though a browser!' Not surprisingly, the Web-based control systems offered by these manufacturers provide a much richer environment than those that are merely intended as an adjunct to a traditional workstation-based system. Trending, scheduling, alarming, reports, program changes, memory downloads - all can be accomplished through a browser. It also follows that these systems provide a better platform to support the new generation of 'gadgets,' such as WAP cell phones, because these devices are also based upon a browser interface."
From the article, "Learning to Deal with IT," by J. Rand Arnold, P.E. and Darrell Matocha of ControlShop, Inc.:
" 'Internet-enabled' is now a requirement for virtually every job. As building automation technology begins to offer the convenience of Web accessibility and open systems, the integrator can offer additional services and gain credibility with the IT forces. Take for instance the situation where the facilities engineer is responsible for hvac requirements of a typical data center or computer room. Delivering cooling and maintaining space temperature is no longer adequate. The enduser is the IT manager. He demands real-time knowledge of the temperatures inside computer cabinets, knowledge of who is accessing the cabinet, and access to every aspect of the operating conditions from any browser, anywhere in the world. After all, he can do this with any of his computer systems."
In a full throttle article on Internet-controlled building automation entitled, "Using Standard Internet Protocols in Building Automation," Mike Donlon, director of research and development at Computrols, Inc. summarizes it this way:
"TCP/IP is the glue that binds the entire Internet and almost every network in the world. It is no longer strictly for large computers. Embedding the TCP/IP protocol into small electronics is not only possible, it is inexpensive and commonplace. Almost every widely accepted, general-purpose networking protocol of the future will ride on top of the TCP/IP architecture. Building a TCP/IP infrastructure into buildings today ensures that they will be ready for the technologies of tomorrow.
At the time that this article was written, some manufacturers of embedded electronics might have asked the question 'Why do I want to include a Web server on my new product?' With such massive acceptance and potential connectivity and interoperability at their fingertips, this question is not even valid. The only valid question is 'Why would I not want to include a Web server on my new product?' Three or four years ago the only answer to that question might have been 'Because it's too expensive.' " But now, with the advent of inexpensive 32-bit microprocessors, networking chips, and software, there is no viable reason not to offer Web capability. Even if http is not the primary protocol used to exchange data, not including a Web page service is inexcusable.
Finally, using TCP/IP connections, protocols like XML will dominate the future of interoperability among embedded devices - even in building automation. This is because XML and other Internet protocols benefit from research and development across industry boundaries. No single building automation protocol will be able to surpass them in terms of complexity, maturity, and acceptance."