Define the site and system boundary
Record production scope, operating period, utility meters, included systems and excluded loads before comparing performance.
Engineering methodology
Trace the conclusion back to the boundary, input and calculation.
kWhScan is a pre-audit decision-support workflow. It separates energy systems, records evidence strength, calculates measures with visible assumptions, controls overlapping savings and states what site data is still required before an investment decision.
Six-stage workflow
From available plant data to a reviewable pre-audit decision.
Validate the baseline
Keep source records, units, time resolution and gaps visible. Normalize only for factors that can be explained, such as production, weather, operating hours or product mix.
Diagnose each system
Separate equipment efficiency, control, distribution, end use and multi-energy interaction so that a whole-site total does not hide the cause.
Calculate each measure
State the formula, input source, operating hours, conversion factors and uncertainty. Representative values are examples, not measured site results.
Resolve overlap
Assign a shared load or saving to one calculation boundary, then show dependent measures and sequence effects before aggregation.
Specify verification
List the meters, trends, production variables and baseline period required to confirm performance after implementation.
Evidence contract
Not every input supports the same level of confidence.
The report should distinguish measured evidence from documents, operator statements and representative assumptions. A confident-looking number does not upgrade weak evidence.
| Level | Typical evidence | Permitted use | Required label |
|---|---|---|---|
| A | Calibrated meter, historian or verified interval data | Baseline and measure calculation when scope and timing match | Measured |
| B | Equipment record, utility bill, controller export or recent test | Calculation with documented period and limitations | Documented |
| C | Operator interview, spot reading or incomplete trend | Screening and data-gap identification | Observed or reported |
| D | Representative example, default or engineering assumption | Method demonstration and sensitivity analysis only | Representative assumption |
Double-counting control
Aggregate measures only after they share one consistent baseline.
Pressure reduction can reduce leakage. Better refrigeration sequencing can change condenser and pump loads. Heat recovery can displace boiler fuel but may not reduce compressor electricity. kWhScan records these dependencies before adding benefits.
Representative examples
Public examples explain the workflow; they are not customer claims.
Unless a page explicitly identifies an authorized customer case, facility names and values are generalized or representative. Replace them with site-specific plant data before making an investment decision. They do not demonstrate achieved savings, customer endorsement or guaranteed payback.
Explain calculation structure, data requirements, decision boundaries, sensitivities and M&V requirements.
Present representative values as measured customer results, imply an unnamed client, or state that a saving has been achieved.
AI-assisted drafting policy
AI can organize language; it does not approve engineering facts.
AI tools may assist research organization, wording, translation, formatting and first-draft structure. A human maintainer must review system boundaries, equations, units, evidence links, representative-example labels, safety constraints and customer facts before publication.
Core public references
Primary sources used to frame the workflow.
Revision record
Material changes are dated.
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-07-15 | Published the evidence, calculation, overlap, representative-example, AI-use and review policy. |