Idle Thoughts on Smart Grids

Musings from the GridWise Architectural Council, Orlando, 2010

After a week at the AHR show, and meeting with ASHRAE, and sitting in on B2G (Building to Grid) summit, I was back in the building zone as I sat in on day one of the GWAC meeting. The GridWise Architectural Council (GWAC) is a voluntary organization of people concerned with the future of energy. The Department of Energy sponsors meetings of the GWAC, a commitment that keeps the group in meeting rooms, coffee, and pastry. The DOE also provides administrative support through Pacific Northwest National Labs (PNL).

The GWAC is immensely influential in the development of the North American approach to smart grids. It draws members from many industries and not just the best thinkers of the utility industry (although its members include those, too). The GWAC often meets at the end of conference or show tied to a different field of energy, to cross-pollinate their approaches. This week, they met after the AHR show. I have never had the time and resources to commit to a GWAC membership; the members make a serious commitment of time. When one of their open meetings is in the same town as me, I always attend if I can.

What follows are mental doodles from my meeting notes, none long enough to warrant their own post.

Is Demand Response the worst marketing phrase ever?

Demand Response is the girlfriend (or boyfriend) who you dated for a while, but dumped because she only talked about her problems. If utilities want to people to care about DR, they have to come up with some better way to talk about it. Until they do, energy suppliers are going to continue to have a hard time engaging their customers.

Is Customer engagement “the disruptive technology”?

The system designs of electrical grids have been defined by deep integration and process interactions. Service integration and service orientation were unknown. The services, both between supplier and consumer, were undefined. Even within the consumer realm, the services were not defined. Rarely does a commercial owner hope to buy electricity on any given day—electricity is not a service. . . Lights, warmth, computing, music, even flushing toilets, now, those are services.

What will it take commercial building owners to embrace energy response

A building owners business is to operate a building efficiently without, at a minimum, annoying his tenants. If he knew a way to use a third less energy without annoying them, he would be doing it already. Annoyed tenants may not renew their leases. It is safer to avoid this risk.

If a building owner could see how each part of his building would respond to DR, and knew which tenants would be annoyed, this risk is removed. I think the killer app of demand response can apply all service degradation only to those tenants who are habitually late on their rent.

Why does the smart grid have no formal architecture?

This was a real challenge when developing the national roadmap. We did not want an architecture, for a good architecture is ultimately an expression of a particular business model. When we developed the national roadmap, we wanted to support any number of business models, both those known today, and those we might find in the future. How would a traditional “architecture”, or perhaps even a TOGAF-style instantiation of Intelligrid, handle, say Google becoming its own virtual utility buying directly in multiple ISOs? We deliberately left architectures undefined.

We had to socialize the services as “reducing the size of interoperation domains” to enable innovation by reducing the requirements to form cross-domain interactions

Why does it seem that there is a fundamental contradiction between the smart grid and new technology?

When integration and interoperation are the biggest challenge, then diversity is the biggest controllable expense, and technical innovation is the biggest controllable risk; it is most easily controlled by preventing the introduction of either. The smart grid must introduce both.

The real question, if properly constructed, is not how we create The Smart Grid™, but how do we define Service Oriented Energy (SOE), of which the Service Oriented Grid is just one arranged subset. The SOG interacts with another entity, with quite different purposes, the Service Oriented Building, The SOB exposes some of its attributes and behaviors through SOE interfaces.

From this, we derived the existence of an Energy Services Interface (ESI). The ESI is the external face of any building or microgrid. What happens behind the ESI is of no concern to the grid other than how it effects how the node behind the ESI comes to market.

Can you really keep your mind on smart grid all the time?

No. During most of an excellent talk on new energy generation from FPL, I was thinking, “It won’t be carbon that destroys the biosphere, but alternative energy, specifically, through the slowing of the Gulf Stream by ocean current generation and slowing of the trade-winds by wind turbines…”

Smart Operations are a necessary part of Smart Energy. Maybe GBXML is, too.

It is easy to think we are playing the end game, but we are really working on the early stages of smart energy.

Smart grids may end at the edges of the grid, they may know no bounds, i.e., ZigBee and SEP, or they may end at the meter. Beyond the meter may be a collection of dumb systems, a minimal collection of defined systems with defined responses, or a micro-grid with its own economy, and own dynamics. I think that every node a microgrid is the future.

I was pulled back to thinking about buildings as I prepared to speak at the AHR show in Orlando next week, and by an announcement about an upcoming seminar on GBXML (GB = Green Building). GBXML is a format designed for the exchange of engineering information, particularly that related to energy use and energy efficiency, during the design process. GBXML may be the key to understanding microgrids in buildings.

The challenge when we treat the end nodes as micro-grids is categorizing and measuring the services they provide. These may be relatively clear in the data center, but even there, understanding HVAC support services is relatively obscure to the IT operator. Going a step further and treating the data center as the district energy center for thermal distribution is hard to understand, harder to account for, and therefore difficult for most enterprises to work with. What are the services in the end nodes?

So, after a building has been partially renovated a few times, and has three EMS (energy management systems), each managing a dozen zones, what effect is there on which part of the business when load is shed in a particular way? Which departments, or tenants, are even affected? Do tenants have QOS agreements, and if so, how are they affected.

Full-fledged BIM (Building Information Model), as defined in NBIMS and BuildingSmart, is too fat, too heavy to use in everyday operations. GBXML is a light-weight one-off of the IFCs in BuildingSmart. It was developed to model energy use, and to exchange energy models within buildings. GBXML includes formal definitions of geometries and spaces, and common models for the components of the energy using systems in buildings. It might just be the map between the design, the operations, and the services. GBXML might just be BIM-Light.

Somewhere between the intriguing, but not yet all that useful Microsoft Hohm and Google Energy, there needs to be a path for buildings as service providers. Understanding services in buildings requires understanding tenants, and their purposes. Perhaps Building Service Profiles link to the spaces in the light-weight BIM (GBXML) and therefore to the tenant services.

Energy profiles linked to the Building Service Profiles, then, become the links between Demand Response and graphical, tenant aware interfaces for building operations.

Last week, I received an announcement of a GBXML seminar in building design (http://www.gbxml.org/events.php). So far, efforts such as LEEDS have not yet delivered on the vision of sustainable energy-efficient high-performance buildings. The unhappy truth today is that most "green" buildings are poor energy performers within a couple years of delivery. Commissioning is a one-time act with no visible links to ongoing operations. Maybe using GBXML to both define the services of buildings and to operate/visualize their operations will not only enable stronger DR, but will lead to better every-day operations.

I am convinced that long term models for distributed energy, and for rapid innovations in energy use, come in this area. All the early incentives of DR, and the early visualizations of Google Energy and Hohm, are merely the tip of wedge for DER and smart energy in the end nodes. We need an interface between design, construction, operations, and smart energy. GBXML may be the most important enabler of net zero, near grid, and off-grid facilities. It may be what we need to apply the facilities capability management approaches pioneered by the Coast Guard to the policy-based net zero security and survivability of the NZ Army base.

I recommend that you check out the seminar on GBXML if you are interested in the real potential of smart energy.

body>

Distributed Energy Grids can use Diverse Energy Storage

But there’s no way to store energy, he said. What he should have said is that there are few ways to store energy at grid scale. Grids, and microgrids, have two approaches to storing energy. They can store it in something that produces electricity, or they can store it in any format that provides a service to its customers. The closer we get to the end users of energy, the more options we have to store energy. The most critical short term goal of smart grids might be to transfer as many incentives for energy storage to the end nodes of the grid as possible as soon as possible.

Very few of us want electricity—we want instead to have a modern life-style. This means we want ready access to sanitary services, whether clean water or working waste disposal. We want light, and heat (or cooling). We want our appliances to provide whatever services we bought them for. Digital electronics provide us with the most direct conversion of electricity to desirable service, but even there we may be able to store services.

Behind every meter there is a microgrid, which exists to supply the wants of its customers. The customers of transmission and distribution grids only want electricity, and they want a lot, so these grids are limited in how they can store energy. Any storage that these grids do use, must be big enough to support the transmission or distribution scale of operations. For example, pump storage, wherein water is pumped up in the air, and used for hydro-generation later, is a very efficient way to store the energy in electricity for later use. Transmission-scale pump storage, though, must be as big as a small lake. There are a limited number of locations to place a lake with a down-hill water supply where filling and draining the lake is an acceptable option. We may have used all of them in North America already.

There are not many more options for distribution scale storage in traditional local microgrids. Non-traditional microgrids, however, distribute more than electrical energy. District energy grids distribute thermal energy, whether in the form of heat (steam) or of cooling (chilled water). These systems can pre-cool (or pre-heat, although this is less common) water for distribution. Thermal storage lets district energy microgrids shift energy use to off-peak hours. In a modern transactive grid, such shifting can be part of demand response. Microgrids with significant thermal storage may be able to run entirely on site-based alternative energy during peak hours. They may be able to store off-peak generation converted to thermal energy.

Non-energy utilities have their own grids supported by the distribution grid. A significant service in cities is the supply of water, and water pressure. This is done by pumping water high into the air, using energy-intensive pumps. Water towers can easily become locations for energy storage, off-loading electrical use until when energy is cheap, and the pumps can run inexpensively. This local pump storage is not used to generate electricity, but within its limits is an effective way to shift energy use to times when energy is cheaper and more plentiful.

When the microgrid gets down to the size of a single commercial building or home, all sorts of energy storage options become available, if only we do not confine ourselves to electrical storage. High rise buildings pump water to so toilets will flush. Thermal storage can be in basements or rooftops. Some data center strategies could even be considered to be storing up business process for use later.

Sharing Energy Information within the End Node

Customers and/or their energy management systems require live energy usage information to help make decisions in response to grid-centric events such as DR, curtailment, and energy market events. Energy sales and purchases are the basic elements of transactional energy; a common shared understanding of each energy use proximate to the operating decisions that influence energy use is essential to collaborative energy on the smart grid.

The target of smart grid communications, particularly in collaborative energy space, should always be the microgrid. Some microgrids may contain a single home, or commercial building, or and industrial site—those are irrelevant details. Microgrids have a number of systems inside them that must work within the economic environment of that microgrid—and I am thinking of old economics, before the distinction of economics and ecosystem arose. Some microgrids may have a single entity inside, say a traditional siloed BAS (Building Automation System), but the unitary microgrid is merely an artifact of the way we have always done it. The energy services interface is the gateway to a microgrid.

Shared responsibility for balancing energy production and consumption requires shared access to information about energy markets and actual use. Shared information on energy use, especially live energy use, is essential to cooperation between the grid and its end nodes. Each end node may have multiple systems. Those systems may have multiple strategies and approaches to managing energy. Each strategy may have unanticipated effects on the other systems. These effects can occur quickly. Unambiguous feedback and continuous monitoring are essential to deliver results while providing services to the building occupants. The official recorder of market transactions is the electrical meter.

Energy use is more than net use for a period. Load shape matters. Multiple systems may each be operating efficiently, but in ways that their aggregate effect requires more energy use than anticipated. Systems within a building should be able to share their energy use, and their anticipated energy us with each other. Load shaping within a building is a critical pre-adaptation for site-based generation and energy storage. Load shaping is necessary for multiple systems to coexist within a minimal fixed energy budgets. The ability to function within a fixed energy budget reduces the risk and thereby increases the value of site based energy sources.

Microgrids contain collections of systems that may not share common technology. Some of these systems are small, self contained, and serve special purposes, such as appliances. Some are large and complex and span significant space, such as HVAC or an industrial line. Some look alike, are built from the same components, but have different missions; the laboratory fume hood and the air conditioning system are run for different purposes and have different constraints. Some may rely on different energy markets to do the same work; heat may come from electricity, gas, or solar thermal in the same building. Some systems may store generate energy used by other systems. All of these coexist in the ecosystem of the microgrid.

Shared energy usage information is essential to interactions between:

• Distribution and the industrial, commercial, and home premise.
• The service provider and the industrial, commercial, and home premise.
• Distributed energy resources and all other domains
• Plug-in electric vehicles and premises and the grid

Any other interactions that will cause, use, or track energy transactions on smart grids.

Building revenue meters and intelligent systems in buildings should share their energy usage information in real time within the end node in a clear, accessible standard.