Study the CEA by practicing decisions, not just definitions. Work paper scenarios where you must pick the right audit level, apply the correct rate component, evaluate an ECM with the right financial metric, and sanity-check a savings claim against its baseline. After each scenario, write one sentence naming the concept you used and one naming the tempting wrong turn. Scenario practice trains exactly the matching judgment that memorizing formulas alone cannot, because it forces you to select the right tool under the constraints each case supplies.
Choosing the right audit level instead of defaulting to the deepest one
Audit levels differ in depth, cost, and the confidence of their findings. Match the level to the decision the client must make, rather than assuming a detailed audit is always the correct or best answer.
A preliminary or walk-through audit identifies obvious savings opportunities, rough load inventories, and low-cost actions, using brief site observation and utility bill review. A targeted or general audit quantifies major systems with measurements and split loads by end use. A detailed or investment-grade audit supports capital decisions with metered data, engineering calculations, and firm cost estimates.
A tempting shortcut in scenario practice is recommending the most thorough level in every case. If the scenario asks whether a client should commission a costly capital project, investment-grade depth is justified because the decision carries financing risk. If the client only needs to know whether an audit program is worth starting, a walk-through with bill analysis answers that at a fraction of the effort. Tie your recommendation to the decision at stake, and state what data the chosen level will and will not produce.
- Walk-through: brief site visit, bill review, list of visible opportunities, rough savings ranges
- General/targeted: end-use load estimates, spot measurements, moderate confidence for most ECMs
- Investment-grade: metering or logging, calibrated calculations, firm cost data suited to financing decisions
Rate structures: separating energy charges from demand and power factor charges
Commercial bills usually combine an energy charge per kWh with a demand charge per kW and sometimes a power factor penalty. Savings calculations must credit the right components or they overstate or understate value.
Energy charges reward consumption reductions; demand charges reward peak load reductions. A measure that trims kWh spread across off-peak hours saves only the energy component, while a measure that flattens or shifts on-peak load can also cut demand charges. Power factor penalties, where present, are reduced by correcting reactive power, typically with capacitor banks, not by reducing real energy use.
Worked scenario: an office cuts its lighting connected load and the result lowers every hour of the month, including its peak. The tempting mistake is crediting only the kWh times the blended rate. The better analysis also checks whether the peak kW dropped; because the lighting operated during the peak window, the demand charge falls too, and the measure's value rises. Contrast this with a schedule change that moves a chiller restart to after the demand window: consumption barely changes, but the demand charge drops. Naming which bill component each measure touches is the core skill.
Lighting retrofit math: burned hours, connected load, and the coincidence trap
Lighting savings equal the change in connected watts multiplied by actual burned hours, adjusted for controls and coincidence. Using nameplate data or assumed hours without checking operation produces inflated savings estimates.
Connected load is fixture wattage times quantity; annual energy is connected load times burned hours divided by 1000 for kWh. Demand impact depends on coincidence: only the fraction of the load operating at the bill's peak window contributes to peak demand. Occupancy sensors and daylight controls reduce effective burned hours, but their savings depend on existing operating patterns, so log or interview before assuming a fixed percentage.
Worked scenario: an auditor replaces 100 fixtures at a 20-watt reduction and assumes 4,000 annual hours from a handbook default. The site actually operates 2,500 hours, verified by logging. The mistake is presenting handbook-hour savings to the client; the better decision is to base the calculation on measured or well-evidenced hours and report a lower but defensible figure. Why it matters: an overstated estimate damages the audit's credibility, undermines the client's financial model, and falls short of the documentation a professional audit requires, whereas the measured figure supports a trustworthy investment decision.
Motors and VFDs: applying affinity laws only when the physics allows
Variable frequency drives save energy on centrifugal loads following the affinity laws, roughly power varying with the cube of speed, but only when flow and pressure actually vary. Throttled or fixed-duty systems do not deliver cube-law savings.
For centrifugal fans and pumps, flow varies with speed, pressure with speed squared, and power approximately with speed cubed. This makes VFDs attractive where loads vary widely across the year. But if a damper or valve is already near fully open, or the process needs constant flow and pressure, slowing the motor changes the delivered service and the savings model collapses. Constant-torque loads also follow different, much flatter relationships.
Worked scenario: a pump runs at full flow continuously to maintain loop pressure, with a bypass valve dumping excess flow. The tempting mistake is applying cube-law savings to a VFD retrofit anyway. The better sequence is to recognize the bypass as the real inefficiency: control the pump speed to the process demand with the VFD, estimate savings from the actual operating profile, and check minimum speed limits, motor cooling at reduced speed, and power quality. The improved answer credits real reduced power at each operating point, not a generic curve, and notes where the simplified relationship stops applying.
Evaluating ECMs: when simple payback misleads and lifecycle measures serve better
Simple payback shows how fast an investment returns its cost but ignores cash flows after payback, time value of money, and equipment life. Lifecycle metrics compare measures with different lifetimes and cash-flow patterns fairly.
Simple payback equals installed cost divided by annual savings. It is quick and familiar, which makes it the default answer, but it cannot rank a long-life measure against a short-life one, and it says nothing about value created after the payback year. Net present value, internal rate of return, savings-to-investment ratio, and lifecycle cost each account for cash flows across the measure's life with a discount rate.
Use the metric that matches the decision. For screening a long list of small measures, payback is a fast filter. For choosing between a compressor replacement and a controls upgrade with different lifetimes, use lifecycle cost or savings-to-investment ratio, because payback would favor the cheap short-lived option even when the durable one creates more value. Worked scenario: measure A costs little and pays back in two years but lasts five; measure B costs more, pays back in five, and lasts twenty. Presenting only payback steers the client to A. The better recommendation reports both metrics and shows B's lower lifecycle cost, because the client is committing capital, not just recovering it.
Measurement and verification: checking savings claims against their baseline
Reported savings are the difference between a baseline and post-retrofit consumption, adjusted for conditions. Always ask what the baseline represents, how adjustments handle weather and production, and whether the method matches the measure.
A baseline is not simply last year's bill; it is a model of what consumption would have been without the retrofit under current conditions. Weather normalization, occupancy changes, and production levels must be handled consistently. Verification approaches range from metering the isolated measure to analyzing whole-facility bills, and the choice depends on how large and how interactive the measures are.
Worked scenario: a retrofitted chiller plant reports large savings, but the summer after the retrofit was mild and production fell. The tempting mistake is comparing raw monthly kWh to last year and crediting the whole difference as savings. The better analysis rebuilds the baseline with the reporting-period weather and production, then attributes only the adjusted difference to the retrofit. Why it matters: unadjusted comparisons can show savings during a down year or hide real savings during a busy one, and the audit's recommendations, guarantees, and client trust all ride on that distinction. In scenario answers, state the baseline, the adjustment variables, and the verification boundary explicitly.
| Metric | What it answers | Strengths | Limits |
|---|---|---|---|
| Simple payback | How fast the cost is recovered | Fast screening, easy to explain | Ignores life after payback and time value of money |
| Net present value | Total value created over the measure's life | Accounts for all cash flows and discount rate | Needs a discount rate and longer inputs |
| Savings-to-investment ratio | Value delivered per dollar invested | Good for ranking measures of different sizes | Still needs lifetime cash flow estimates |
| Lifecycle cost | Total cost of owning and operating | Compares options with different lifetimes | Sensitive to assumptions about service life |
Documentation, safety awareness, and a self-check exercise with rubric
A defensible audit documents assumptions, data sources, and calculations so a reviewer can reproduce every number, and treats site safety as a precondition for field work. Use the exercise below to test whether your reasoning holds up on paper.
Professional standards for energy auditing call for transparent documentation: measured values with their instruments and dates, assumed values labeled as assumptions, calculation methods identified, and recommendations tied to the data. Safety in this credential's context means recognizing hazards such as energized electrical equipment, confined spaces, and roof access, and knowing that the auditor observes and coordinates rather than performing hazardous tasks unsupervised.
Practical exercise: take one paper case, such as a small commercial building with twelve months of bills, a lighting schedule, and one constant-speed pump with a bypass valve. Produce (1) an EUI by dividing annual energy by floor area, (2) a lighting retrofit estimate using logged hours, (3) a VFD recommendation with an operating-point power estimate, and (4) a recommendation of audit level with justification. Self-check rubric: two points if the rate components affected are named for each measure; two points if every number shows its source; two points if the baseline or operating profile is stated before savings; two points if the audit level matches the client's decision; two points if one assumption is labeled and its effect on the estimate is described. Eight or more suggests you are reasoning like an auditor; below six, redo the case naming concepts aloud before recalculating. A suggested sequence across several weeks: week one, audit levels and one walk-through case; week two, rate structures and bill decomposition; week three, lighting and motor measures with calculations; week four, financial metrics and an ECM comparison; week five, M&V reasoning and a full case from baseline to recommendation; then repeat one case under time pressure. For question-style practice, use the free practice materials on this site, and confirm all administrative requirements directly with the Association of Energy Engineers, the credential's issuer.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.