Certainly, TCP/IP and HTML are great examples of standards that changed our world. Usually, companies get this. It's pretty clear, for example, that society benefits when there's a limited range of outlets into which you can plug appliances. But it's not just at a level so mundane. When compatibility and cost stifled the wireless communications market, clever vendors formed the Wi-Fi Alliance and brought the technology to the masses.
Open standards are so important that their mere existence has created some of the biggest and most influential companies in our industry. None is larger or owes more to open standards than Cisco. It's this history that makes Cisco's announcement of its EnergyWise initiative particularly disappointing, at least so far. Cisco's goal with EnergyWise is commendable: Use existing standards such as Power over Ethernet to manage the power consumption of network-attached devices now, expanding to other devices such as PCs by summer, and finally achieving broad automation of building-level systems by early next year.
The problem is that Cisco's doing this work in conjunction with a relatively small group of partners rather than bringing the idea to a proper standards body in an early stage. Its partners include SolarWinds for overall management, Verdiem for non-PoE device agents, and Schneider Electric for HVAC management. So if you happen to be a Cisco, Schneider, SolarWinds, or Verdiem shop--lucky you! You may be able to save 20% or more on your power usage with EnergyWise. The rest of us, not so much.
The ITU is exactly the place for this specification, and it's where Cisco should have started. In the short run, we can reduce carbon emissions far more by conserving energy than by increasing use of renewable energy sources. If Cisco had taken the idea straight to the ITU three years ago, we'd probably have a road map for universal EnergyWise compliance about now. But, hey, there was a buck to made, so Cisco decided not to go that route, and in a year we can start the ITU process from scratch, putting us four years behind where we could have been.
Art Wittmann is director of InformationWeek Analytics, a portfolio of decision-support tools and analyst reports. You can write to him at firstname.lastname@example.org.
To find out more about Art Wittmann, please visit his page.
Register to see all reports at InformationWeekAnalytics.com.