11 Roadmap

The GNU remotecontrol Road Map is planned for and limited by the following boundaries.

11.1 Interoperability

The Future of GNU remotecontrol is a commitment to International standards and protocols for Information Technology to provide availability, relevance, transparency, and maintenance of the GNU remotecontrol framework. The BACnet XML Working Group is an excellent example of these attributes. For more information, See GNU remotecontrol & BACnet.

11.2 HVAC Original Equipment Manufacturer - Feature Addition

OEM’s have not added the feature of IP enablement in the past. The benefits for OEM’s to add IP enablement to their thermostat product offering far outweigh any hindrance from remaining a standalone device. Examples of these benefits include interoperability, furthered Energy Management strategies, and increased customer satisfaction from the new capability of remote access to their thermostat.

11.3 HVAC Aftermarket Equipment Manufacturer - Feature Addition

AEM’s have added the feature of IP enablement in the past with limited success. This is mostly due to the dependency on another piece of proprietary technology to handle translation of some proprietary technology to the data network for the thermostat. The proprietary aspect of the technology will often bottleneck the success of that technology. The success of the thermostat as a complimentary good is well proven. There are hundreds of different programmable thermostats for sale at both the local home supply stores and globally. Proper selection of any aftermarket product or service is critical to the success of the primary product being supplemented. A simple example of this is selecting the different parts to enhance an engine for an automobile, or a boat, or a snow mobile, et cetera. Aftermarket Equipment Manufacturers must demonstrate they have in their offering the capability to not damage the existing primary product. Specifically, a heating and cooling system. There must also be solid proof their offering enhances system performance by adding additional feature/benefit combinations. Finally, their offering must be constructed to meet manufacturing directives, such as RoHS.

11.4 Cost Benefit Analysis

The outcome of your Cost Benefit Analysis will help you see your Return on Investment (ROI). This will probably be the bottom line to the success of GNU remotecontrol for you. The Retro Commission (RCx) of any facility, small or large, is best evaluated by.....is it worth it? Even Testing-Adjusting-Balancing a system is well worth the time and effort, to make sure your system is setup as suitable for your needs and wants. The answer to this ROI question mandates completing several different calculations to make that determination. New construction does not require as many calculations to come to that determination, but often mandates different aspects to be evaluated and then calculated. Don’t forget to add in the cost/saving of Information Technology. This list includes system design, capital expenditures, and system operation. Then, don’t forget to add in your End User cost/saving for training and system operation.

Not every facility must have a complete set of calculations to know what you need to do for your Energy Management strategy. Consider simple advice on best practices offered by your qualified Decision Makers to help you select what is best for you. Regardless of what you choose for your Energy Management strategy, have a plan.....work the plan.....review and revise your plan, as appropriate.

The cost to implement GNU remotecontrol, in comparison with a lesser Energy Management strategy for any HVAC system, justifies the completion of a Cost Benefit Analysis to determine if GNU remotecontrol is appropriate for your circumstances. Most likely, it is.