Standards

Six Sigma Solutions don’t work unless you have six sigma problems

Sometimes I wonder if the problem I have talking to the members of the building controls industry is that they have been badly managed for two long. You can tell someone who has been bludgeoned into using one tool for everything, because they want to use that tool for everything. They can lose their judgment and like a two year old with a hammer, decide everything is a nail.

Quality management is a wonderful discipline. It has improved every aspect of our lives while driving down costs. We daily expect quality that was unimaginable just a few years ago. Still, there is a darker side to these movements.

Much has been written of how 3M destroyed its culture of creativity and invention by inappropriate application of Six Sigma methodologies. Manufacturing quality improved. Shipping reliability improved. Yet no one was able to invent in accord with the process management methodology. “Last year we had 2 inventions per month; through careful management we to have expect 2.7 per lab throughout this quarter.” It sounds silly if you say it out loud. And yet, it nearly killed 3M.

All these quality methodologies have a common focus on process. All processes must be defined, and documented, and repeatable. This is great when the controls companies are making the sensors and the controllers that go above my ceiling. It is great when they are shipping them on time. It has nothing to do with how they are installed, or designed, or run in today's market.

As the director of Building Services at UNC said to me last month “You know who designed the control systems – it’s some guy who works for the low bidder standing on a bucket”. And he’s right. This area could use some process and repeatability. It could use design improvements. It would be nice if it was designed at all. If you want to use process optimization, work on that.

But don’t try to make the building owner or tenant focus on your process.

This focus on process lets the self-absorbed product engineer in the large building systems company tell himself that the lousy controls protocols we have today are any good. All of them, and I include oBIX, raise focus on the process, make understanding the process critical to interacting with the system, and thereby reduce the value of their systems.

When I interact with a Six Sigma warehouse, I know the goods will be shipped on time. If my clerk is on a first name basis with each person on the loading dock, I know that there are regular problems. When I interact with a six sigma manufacturer, I do it in part so that I do not need to know the details of their returns policy.

Stop making me know what is going on in your control systems. That is not an enterprise interface. And the sale cycles and upgrade rates of the building systems industry will stay awful until the industry recognizes this.

What Good is LEED Certification?

It’s time to acknowledge that LEED standards, as they exist today, increase cost without increasing value. Without committing to fundamental reform of the building development process, Green points from LEED have little if any effect on the overall project. LEED gives points producing the symptoms of a good development process. Most designers, and most owners, opt to produce the symptoms, and leave the flawed processes intact.

The Leadership in Energy and Environmental Design (LEED) Green Building Rating System is the accepted benchmark for the design, construction, and operation of high performance green buildings. LEED promotes a whole-building approach to sustainability by recognizing performance in five key areas of human and environmental health: sustainable site development, water savings, energy efficiency, materials selection, and indoor environmental quality. A project is a viable candidate for LEED certification if it can meet all prerequisites and achieve the minimum number of points to earn the Certified level of LEED project certification. Projects are awarded Certified, Silver, Gold, or Platinum certification.

Unfortunately, LEED can reward those with existing bad processes more than it can acknowledge existing good ones. If you made bad decisions in the past, you get extra points for not making them again. It is too easy to greenwash a project by adding an energy modeling component that has no intrinsic tie to the construction documents. The routinely incomplete documentation of building systems means that the actual wiring and operations is dependent upon the creativity of the subcontractor rather than the Green design. With incomplete system documents, commissioning is a demanding but ultimately futile function. Innovations in system design are lost in normal maintenance and operations due to the inaccessibility or incompleteness of the documents handed over.

To achieve the results LEED aims for requires not just gaming symptoms, but rather an actual commitment to good processes, for the planning, design, construction, and operation of capital assets. The foundation for these good processes must be a non-transient base of information that is accessible throughout the entire building life-cycle. All process audit functions, whether energy modeling, code compliance checking, or even commissioning must be based directly on that information base. If we used such a process, most of the LEED points would fall automatically from the process, with little extra effort necessary.

When we score LEED points without examining the underlying process, we are summing nonsense. Here are some specifics:

  • At UNC, buildable lots are identified and cleared five to ten years before construction starts. Every clear lot is, as on most campuses, used as a parking lot. Today, we get green points because under LEED, siting buildings on brown fields, such as parking lots, is a best practice.
  • We specify, for reasons that are primarily historical and regulatory, CAD-based designs. To get green points, we require that the designer acquire an energy model. That model has no intrinsic link to the CAD design, and there is no way to determine if value engineering removes the features modeled.
  • Building systems are drafted as crude schematics, with no provable links to actual wiring and control tags. This creates building monitoring systems that cannot be linked back to the design, nor to the energy model. This makes commissioning more arduous and less effective.
  • Practitioners in retro-commissioning, that is the process of re-visiting a building possibly years after initial construction and examining system operations are unanimous; nothing would be worse that returning the building to its initial design state. Even in new buildings with high LEED ratings, the control systems were only partially designed at best.

Without a design process that actually includes the mechanical systems and their controls, there is no underlying operational model for the building. Without an underlying model, ongoing system maintenance is based upon guesses. Without live performance metrics, including instant access to energy metering, linked to that model, than building system operations are based upon experience and guesswork. When the system is green and non-traditional, you can eliminate experience, leaving only guesswork. to operate the building, and to tell if the building is being tuned into or falling out of control.

The solution to these problems is an integrated data model for the building whose life extends as long as the life of the building. The data model starts with the capture of the design intents. Building designs should be models, not drawings, and should be standards-based. The energy model would then run directly off the building model and could be compared to the design goals. Changes to the design, especially during value engineering when many innovative features are eliminated, could be automatically reflected in updated energy models.

The electronic building model should be available electronically to each bidder and used throughout the construction process. The increased accuracy of the bid package and reduction in change orders during construction would reduce costs and result in as-built models that match the initial design. These accurate designs, delivered to the owner, would include full identification of the internal systems, their components, and their performance expectations.

With delivery of the as-built models, using system identifications consistent with the initial design documents, building commissioning becomes validation of performance to the design. In the case of energy systems, commissioning becomes validation to and alignment with the energy model. This, at last, becomes a significant improvement over the traditional standard, described, only half in jest, as “no sparks”.

Under this business model, LEED credit would become relevant. Each LEED point is no longer a game-able item separate from the actual business process, but an intrinsic metric of the quality of the process. Facts necessary to support innovative systems would be available to maintenance and operations throughout the life of the building. Those would be green points worth earning.

Note: I know of and am watching eagerly the development of ASHRAE standard G189P. I think the observations here are aligned with its intent, It will offer some improved structure that will lead to measurable sustainable performance.

Principles of Networked Electronics and Energy Efficiency

I had the pleasure of talking to Bruce Nordman of Lawrence Berkeley National Laboratory (LNBL) this evening. It is always nice to come upon someone who has bear end of the same bone as oneself, coming at some related issues from a completely different perspective.

Bruce is presenting at the International Energy Agency next month. Poor guy, he has to go to Paris when I got to go to Chicago. Bruce is approaching problems from the perspective of the electronics world—and so recognizes some things faster than I.

DC Power? We discussed Galvin, and he leapt immediately to POE (Power over Ethernet) , USB (Universal Serial Bus) and FireWire as the de facto standard DC power plugs. I don’t think that these will handle my microwave or my white boxes (Washing Machine, Refrigerator, etc) but it makes sense that these might be the starting place for DC power connectors. I have long admired the elegance of the Blackberry USB Power Supply.

But what drew me to share this conversation were Bruce’s Guiding Principles, as outlined on the IEA site (see below). Bruce is an advocate of all networked electronics being designed for effective power management. TO this end, he (and his co-authors) have described their guiding principles for design. They make a good set of rules for building systems, or for houses, or for the Grid, as well.

The Guiding Principles are:

  • The existence of one device on a network should not cause another device to stay awake when it might otherwise go to sleep.
  • The network should be designed such that a legacy or incompatible device will not prevent the rest of the network from effectively using power management.
  • Devices should expose their own power state to the rest of the network and be able to report estimated or actual power use levels.
  • Product interfaces — for people or other products — should follow (international) standard principles and designs.
  • Products or devices that influence energy consumption should adhere to (international) standards for behavior and communication appropriate to their function.
  • Products and connections should have the ability to modulate energy use in response to the amount of service required.
  • Energy efficiency efforts should not favor any particular hardware — or even software — technology. All network technologies must be the target for efficiency efforts. Future buildings will include many different technologies; those in any particular building will be diverse, and always changing.
  • Harmonization of basic principles underlying efficient design for networked devices should cross all end uses and be global.

oBIX Standard Update to CABA

As if Connectivity Week were not enough fun, CABA's Intelligent Buildings comittee met on Friday after the conference. CABA was instrumental in the original founding of the oBIX initiative. Below is a summary of my report.

oBIX has been an OASIS Committee Specification since December. Delays in the IP management process as well as the review/comments/response cycle made progress slow last year. It is now in the winter of discontent when all adoption and movement appears glacial.

There are shipping applications with oBIX now. UNC is today running 70 buildings using oBIX. I am told the Department of Defense is using it in high end specialized situations, but things being what they are, I cannot say where or how. Interested parties can download the specification at:

http://www.oasis-open.org/committees/download.php/21462/obix-1.0-cs-01.zip

or can download the open source implementation at:

http://sourceforge.net/project/showfiles.php?group_id=148480

What is more interesting is the interest being shown to oBIX external to the buildings domain. The National Building Information Modeling Standard (NBIMS) and the oBIX committee have met to explore relationships between the standards, focusing on whether Energy Models developed directly against NBIMS models can be compared to live data from control systems read by oBIX to produce live models (or instantaneous commissioning). The Emergency Management Technical Committee, promulgators of the Common Alerting Protocol (CAP) would like invoke oBIX contracts directly from CAP alerts. The Open Geospatial Consortium would like to invoke contracts granting situation and spatial awareness to emergency responders. These conversations are the beginning of enterprise interactions with intelligent buildings.

During the report, I was asked about BACnet-WS and its relationship and competition with oBIX. Today, most implementers are still focused on point-to-point communication between systems using REST. Under REST, the difference between the two standards is small. As applications move toward interactions with systems outside the building system domain, wherein pervasive security, Federated identity management, cross-domain applications, long-running processes, and service orientation become more important, then the value of the SOAP binding offered by oBIX becomes of greater relative value. The applications cited above are good examples.

oBIX is currently recruiting members for the technical committee, both to flesh out errors and omissions (1.1) and to begin defining standard contracts based on the oBIX object model (2.0). oBIX is also considering forming an oBIX implementation committee. CABA members are invited to participate in either or both.