An end-to-end decision hub for preparing the need, building a whole-life case, comparing proposals and carrying evaluated commitments into delivery and acceptance.
For: Cross-functional teams preparing a business case or competitive technology procurement.
The four-stage route to an accountable award
1 · Prepare
Define the problem, baseline, stakeholders, constraints, outcomes and evidence plan before a preferred solution shapes the requirement.
2 · Justify
Build the benefits, whole-life cost, uncertainty, risk, funding and accountable outcomes on one transparent boundary.
3 · Compare
Normalize requirements, scope, evidence, assumptions, exceptions and cost before weighted tradeoffs are considered.
4 · Procure
Preserve the evaluated scope, responsibilities, guarantees, tests, data rights, acceptance and remedies in the final agreement.
Award is not the finish line. Delivery, testing, training, measurement and handover must verify the same outcomes and commitments that supported approval and selection.
The decision pathway
Green-technology projects often cross operations, facilities, engineering, sustainability, finance, procurement, legal and information-security teams. The process should make those roles visible early. Late specialist involvement can reveal utility, cybersecurity, contract, data or site constraints after a preferred solution has already shaped the budget and schedule.
| Stage | Core work product | Gate before moving on |
|---|---|---|
| Prepare | Problem statement, baseline, stakeholders, options, constraints and evidence plan. | The need and no-action case are credible; the project is not defined around one vendor. |
| Justify | Benefits, whole-life costs, uncertainty, risks, funding and accountable outcomes. | The case remains viable under realistic downside assumptions. |
| Compare | Common scope, mandatory requirements, weighted criteria, clarifications and due diligence. | Every shortlisted option passes the non-negotiable gates. |
| Procure | Evaluation record, negotiated scope, responsibility matrix and contract commitments. | The selected offer still matches the evaluated and approved basis. |
| Deliver and verify | Design review, approvals, implementation, testing, training, measurement and handover. | Acceptance evidence proves the required outcome and unresolved items have owners. |
Use the guide that matches the next work product
The four guides are connected, but each owns a distinct decision artifact.
| Decision work | Guide | Work product |
|---|---|---|
| Prepare and justify | How to Build a Green Technology Business Case | Need, baseline, options, outcomes, owners, risks and approval gates. |
| Model whole-life value | Total Cost of Ownership for Energy Technology | Comparable acquisition, implementation, operating, replacement, risk and end-of-life effects. |
| Normalize and evaluate | How to Compare Vendor Proposals | Common scope, evidence, assumptions, exclusions, clarifications and commercial terms. |
| Govern award and delivery | Technology Procurement Process | Governance, engagement, due diligence, award, commissioning and closeout. |
Build the baseline before calculating benefits
The baseline should describe the current service, cost, performance and risk that the project intends to change. It may include interval energy use, maintenance, downtime, manual labor, compliance burden, replacement need or capacity constraint. The baseline period should be representative, and known changes—such as planned expansion, tariff revision or equipment replacement—should be visible.
Benefits should follow the same boundary. Avoid counting an energy saving in one model and again as an emissions or operating benefit unless the relationship is explicit. Non-financial outcomes can be important, but they should have an owner, measure and evidence plan rather than being added as unquantified positive language.
Whole-life cost and uncertainty
DOE and NIST life-cycle-cost methods emphasize comparing alternatives over a common period and discounting future costs consistently. A project model should distinguish nominal and real assumptions, show the timing of major replacements and disclose incentives, residual value and tax treatment. Where uncertainty is material, test cases or ranges instead of presenting a single precise return.
GAO cost-estimating guidance stresses scope, assumptions, data, sensitivity and risk analysis. Those principles are useful beyond government programs: a transparent estimate lets decision makers understand what could move the result and what evidence should be improved before commitment.
Proposal evaluation is not merely scoring
Evaluation factors should reflect the decision and distinguish meaningfully between offers. Mandatory safety, capacity, legal, cybersecurity or interoperability requirements should be gates. Weighted criteria can address tradeoffs among technically acceptable options. The evaluation record should preserve evidence, clarifications, exceptions and the reason for the decision.
- Use demonstrations and tests that reflect the intended operating environment, not a generic sales scenario.
- Check references against comparable scope, scale, geography and delivery responsibility.
- Normalize warranties, performance definitions, exclusions, service response and owner obligations.
- Evaluate data rights, software continuity, cybersecurity and vendor exit where the system is connected.
- Carry accepted clarifications and negotiated changes into the final contract and acceptance plan.
Shared tools and records
The Comparison Methodology sets the common logic for gates, criteria, evidence and uncertainty. Use the Technology Evaluation Scorecard for option-level tradeoffs, the TCO Worksheet for screening economics and the Vendor Comparison Worksheet to preserve proposal differences.
Align technical and commercial workstreams
The decision record should show where technical evidence changes the economics and where contract terms change the risk. For example, a storage guarantee should use the same usable-capacity definition as the battery-system specification; a controls demonstration should test the owner rights described in Selecting a Building Automation System. This alignment prevents attractive financial outputs from depending on performance or scope that the contract does not actually deliver.
Scope and limitations
This hub does not provide a final investment decision, approve a supplier or interpret a contract. Public bodies and regulated organizations must follow the rules, delegations and review requirements that apply to them. Qualified financial, procurement, legal, tax, engineering and cybersecurity input may be required.
Sources and evidence
These sources establish the framework and current evidence boundary for this hub. Detailed child guides use additional page-specific evidence.
- Building Life Cycle Cost Programs — U.S. Department of Energy, FEMP
- Life Cycle Costing Manual for FEMP — National Institute of Standards and Technology
- Cost Estimating and Assessment Guide — U.S. Government Accountability Office
- FAR 15.304 Evaluation factors and significant subfactors — Acquisition.gov
- Project Control authority: approved project authority, page map, complete page criteria and page-rules addendum — Future Green Technology
Reviewed and updated 29 June 2026. Organizational author: Future Green Technology, published by Zenith Star Media.