Just Write Click

Technical writing with Continuous Integration and docs-as-code

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code
You are here: Home / talk.bmc / How to save money by monitoring closely

April 5, 2006 by annegentle

How to save money by monitoring closely

How monitoring voltage closely can save money… are there parallels for monitoring your systems closely?

On my way in to work the other day, I caught an NPR story, Utility’s ‘Voltage Reduction’ Plan Saves Energy, about how a Washington state public utility is using “conservation voltage reduction” to save energy, and light bulbs. The electric company monitors the amount of voltage they send to customers (the amount of electrical “water pressure” through the “pipes”). In the U.S., they are supposed to send 120 volts +/-5%, which is 114 volts to 126 volts. The way most power companies currently send out power causes the first half mile radius of customers get 125 volts, and then customers in a mile radius get 124 volts, and so on, so they send out more power than they need to ensure the furthest out customers get output that meets the regulation even after reductions due to distance. However, by regulating precisely, they can reduce the initial power send-out to 117 volt, a cut of 2.5%, which buys the average customer 450 kw, and saves the company $3.5 million per year. Now, if you get down to 111 to 112 volts, there’s the risk of damage to appliances, but apparently a sophisticated monitoring system can prevent that type of drop. A voltage regulation startup Microplanet lets power companies use electronic voltage regulators to precisely regulate voltage and deliver more precise electrical “water pressure.” Now that is a great application of precision monitoring technology.

If you’re inclined to take monitoring of electricity usage into your own hands, there’s the nifty “Kill-A-Watt” electrical usage meter. Using a similar device in Australia, a boingboing.net reader found that his computers were surprisingly inexpensive to run, but he now turns off the whole TV-DVD-VCR stack every night, and makes sure the coffee machine is only turned on while it’s making coffee.

This monitoring of electrical power leads me to believe that precisely monitoring server behavior should allow you to make small incremental changes in server behavior that can save time, power, or resources such as disk space. How about closely monitoring application that require a lot of heavy-duty processing power and finding ways to virtualize those servers? You maintain one piece of hardware but have multiple applications running in virtual environments. That’s all I could come up with for now, but there have to be other examples. I do know that making sure all your monitors have a power save mode and use it can definitely cut back on electricity costs. What other ideas do you have for saving money by monitoring?

Related

Filed Under: talk.bmc Tagged With: energy, monitoring, virtualization

More reading

Bubble graph showing sources of developer support data

I’ve been thinking a lot about developer support at Cisco recently, especially for the way the world works today with multiple cloud providers. This post is a re-publish of my talk from over five years ago, but the techniques and tools for listening and helping others are still true today. At Rackspace, we watched several […]

Cisco DevNet is our developer program for outreach, education, and tools for developers at Cisco. From the beginning, the team has had a vision for how to run a developer program. Customers are first, and the team implements what Cisco customers need for automation, configuration, and deployment of our various offerings. Plus, the DevNet team […]

I had a great talk with Ellis Pratt of Cherryleaf Technical Writing consulting last week. Here are the show notes, full of links to all the topics we covered. Podcasts are great fun to listen to and participate in, if a bit nerve-wracking to think on your feet and make sure you answer questions succinctly […]

At the beginning of this year, I worked hard to summarize my thoughts on API documentation, continuous publishing, and technical accuracy for developer documentation. The result is an article on InfoQ.com, edited by Deepak Nadig, who also was forward-thinking in having me speak to a few teams at Intuit about API documentation coupled with code. Always […]

Recently on Just Write Click

  • A Flight of Static Site Generators: Sampling the Best for Documentation
  • Try a GPT about “Docs Like Code” to ask questions
  • Discipline and Diplomacy: Docs in the Open
  • Let’s Find Out: When Do Static Site Generators Do Rendering?
  • GitHub for Managing Tech Docs

Just Write Click in your Inbox

Enter your email address to subscribe to Just Write Click and receive notifications of new posts by email.

Read More

  • Privacy Policy
  • About Anne Gentle, developer experience expert
  • Books by Anne Gentle
    • Conversation and Community
    • Docs Like Code, a Book for Developers and Tech Writers
  • Woman in Tech Speaker Profile
  • Contact

Books

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code

Copyright © 2025 · WordPress · Log in