EDGE projected resource gains: build the method

EDGE projected resource gains should come from the company’s measured baseline, the proposed solution and a transparent operating forecast. A percentage supplied by a vendor is not enough. Management should be able to explain the units, activity level, implementation date and evidence that will later test the projection.

Begin with the approved resource boundary

The current resource management and optimisation activity page covers energy, carbon, waste, water and materials. Select the resource and operating boundary that match the project. Do not mix a whole-company utility bill with a solution used by one production line unless the allocation is supportable.

Use the EDGE resource baseline guide to prepare the historical baseline. This article starts after the baseline is stable. Keep the same units, sites, process boundary and activity driver in the projection so the before-and-after comparison remains meaningful.

Build the engineering change

Describe what physically or operationally changes. It may be equipment efficiency, process control, heat recovery, material yield, water reuse or another measurable mechanism. Link the change to an input value such as rated power, operating hours, throughput, loss rate or recovery percentage.

Separate manufacturer data, consultant calculations and company observations. State the source and uncertainty for each input. Where a value comes from a test at ideal conditions, adjust it for the company’s expected load and environment or show it as a sensitivity rather than a certain result.

Forecast the activity level

Resource use may rise even when efficiency improves because production grows. Forecast the relevant activity driver for one year after project completion, such as units produced, floor area, operating hours or tonnes processed. Use an approved business forecast and explain seasonal or ramp-up effects.

Show both absolute use and intensity. Absolute use answers what the company may consume. Intensity answers how much resource is used per unit of activity. A project can improve intensity while total use rises, and the application should not hide that outcome.

Calculate EDGE projected resource gains

Use a simple bridge: baseline intensity multiplied by forecast activity gives expected use without the project. Revised intensity multiplied by the same activity gives expected use with the project. The difference is the projected resource gain. Convert to money or carbon only after the physical units are clear.

For example, a process using 12 kWh per unit at 100,000 units has a 1,200,000 kWh counterfactual. If the supported design is expected to use 9.5 kWh per unit, projected use is 950,000 kWh and the gain is 250,000 kWh. Keep price and emissions factors in separate dated fields.

Use scenarios instead of false precision

Create low, central and high cases for the inputs that matter most. These may include operating hours, utilisation, degradation, yield and production volume. Explain why the central case is reasonable. Do not average unrelated assumptions merely to obtain a preferred payback period.

Identify the break-even input. Management should know how far utilisation or savings can fall before the project no longer meets its commercial requirement. Grant support may improve cash flow, but it does not remove operating risk or guarantee the technical result.

Design the verification method

The activity page requires an implementation report detailing current resource consumption and actual projected gains from one year of implementation, or up to claim submission if one year is unavailable. Decide meter, sample, production record, calculation owner and review period before installation.

Record commissioning, downtime, maintenance and material changes that affect the result. Use the same boundary and units as the forecast. If actual data covers a shorter period, label it and explain the extrapolation. Do not present a partial period as a full year without adjustment.

Connect resource and financial results

The activity page also requests projected revenue growth and cost savings for one year after project completion. Keep these claims separate. Resource savings may reduce variable cost, avoid disposal fees or support capacity. Revenue needs its own sales and capacity assumptions.

Prepare one management summary showing capital cost, supported and unsupported amounts, operating cost, physical gain, estimated cost saving, payback and main sensitivities. Link it to the business support decision guide and the enterprise support hub so the project is reviewed as an operating investment, not only a grant application.

A credible projection can be recalculated by someone who did not build it. Keep the physical mechanism, activity forecast and later measurement aligned, and the result will remain useful even when actual conditions differ from plan.

Build the projection from operating drivers

Start with the activity that consumes the resource. For electricity this may be machine hours, cooling load or production volume. For water it may be batches, cleaning cycles or occupancy. Record the baseline quantity, unit rate and operating period. Then state exactly which driver changes after implementation. EDGE projected resource gains should explain the engineering or process relationship instead of applying a general percentage to the annual bill.

Separate savings caused by the project from changes in price, production volume, weather or operating hours. Where uncertainty is material, present a conservative case and a management case using documented assumptions. Do not add benefits that cannot occur together. Keep supplier calculations as supporting evidence, but reproduce the logic in a company-owned worksheet that management can understand and challenge.

Design the one-year measurement file

Choose a reporting interval, source meter or invoice, responsible person and normalisation method before installation. Preserve baseline readings and photograph or export the relevant meter identifiers. If several projects affect the same bill, define how each contribution will be separated. Record downtime, production changes and exceptional events so they are not mistaken for efficiency gains.

The implementation report should reconcile approved equipment, commissioning, operating settings and observed results. Compare the measured result with the original projection and explain any variance. Management can then decide whether to tune the system, change behaviour or revise the business case. This method creates useful operational evidence even when the actual saving differs from the estimate.