Energy Management Fundamentals and Program Development
Core concepts
Energy management is a continuous cycle, not a one-time project. Understand the distinction between energy (kWh, therms) and demand (kW), and how load factor (average load divided by peak load) reveals whether a facility's cost is driven by peaks or by total consumption. Candidates must know the standard program architecture: establish baseline, set goals, identify opportunities, implement, verify savings, and recommit. Familiarity with ISO 50001's Plan-Do-Check-Act structure and with the concept of an energy management team with an executive sponsor is expected.
Traps to watch
Questions often confuse strategic planning with tactical implementation, or ask which step comes first in a program. A common trap is assuming energy audits alone constitute a program; audits are one input. Another trap: treating energy intensity metrics (kWh per unit of production, per square foot, per degree-day) as interchangeable. Choose the metric that normalizes for the dominant driver of consumption. Be careful with avoided cost versus average cost - programs justifying projects should use marginal/avoided cost.
Worked rule of thumb
To screen opportunities, rank by simple payback = implementation cost / annual savings. A facility spending $500,000 per year on electricity with a 10% reduction opportunity saves $50,000. If the measure costs $150,000, payback is three years. Use this as a first filter, not a final decision - lifecycle cost and non-energy benefits matter.
Program development essentials
Define scope and boundaries, assign accountability, build a baseline with at least 12 months of data normalized for weather and production, and create a reporting cadence. Track both energy and demand savings, and document assumptions so Measurement and Verification can later confirm them.