CCST9016 Chap.7 Evidence-Led Energy Project Design
Evidence-Led Energy Project Design
Problem definition comes before solution selection
An energy project becomes defensible when it begins with a bounded need rather than a preferred technology. Define the users, existing practice, location, energy service, environmental concern and constraints. A statement such as improve campus sustainability is too broad to test.
A better definition identifies a recurring service, a measurable burden and the people who experience or manage it. Early field evidence should change the definition when it contradicts assumptions.
Observations become requirements through interpretation
A raw observation is not yet a design requirement.
Seeing equipment left on after use could indicate missing controls, unclear responsibility, operational necessity or poor feedback. Interview and observational evidence help distinguish these explanations. Translate validated needs into requirements that specify an outcome and, where justified, a threshold.
Keep the source of each requirement in a traceability table so the project can show why it matters.
Generate alternatives before applying criteria
Teams often converge on the first plausible concept and then choose criteria that favour it. Reverse that order. Generate alternatives that intervene at different points: reduce demand, improve conversion, recover waste energy, change controls or substitute supply.
Establish criteria from the problem definition, including performance, cost, safety, environmental impact, usability and implementation constraints. Weighting should be explained rather than hidden inside a total score.
Calculations are claims with assumptions
A project calculation should expose baseline, units, operating time, efficiency, loss and uncertainty.
If an intervention saves power only during active hours, do not multiply it by every hour in a year. If a field observation is a small sample, present a range or scenario rather than false precision. A sensitivity test asks whether the concept remains preferable when an uncertain assumption changes.
The most valuable test targets the variable capable of reversing the decision.
Prototype the riskiest link
A prototype need not reproduce the whole system. It can test a control sequence, user interaction, measurement method, heat-transfer assumption or physical fit. Choose the prototype by asking which unresolved claim threatens feasibility. Define success before testing and preserve unexpected results.
A demonstration designed only to look complete may communicate effort while leaving the core uncertainty untouched.
Team integration is a technical responsibility
Dividing sections among members is efficient only if someone integrates boundaries, units, terminology and evidence. Assign owners for source verification, calculations, figures, requirements and final consistency.
Use shared version control or a clear file protocol, record decisions and review interfaces between sections. Laboratory work should inform the project argument, not sit as a disconnected appendix. Before submission, trace each conclusion backwards through evidence, method and assumption.
What this chapter covers
- 01
Users, service, context and problem boundary
- 02
Field evidence and stakeholder interpretation
- 03
Requirements linked to observed needs
- 04
Alternative concepts and transparent criteria
- 05
Baseline calculations and sensitivity testing
- 06
Prototypes aimed at decision-critical uncertainty
- 07
Team roles, laboratory evidence and final traceability
Worked example · free
Turn an observation into a testable project requirement
- 4Write a problem definition that names the service, users, place and observed burden without prescribing a solution.
- 3Calculate the upper-bound weekly energy associated with the observed period.
- 3Identify a decision-critical uncertainty and an appropriate field test.
Key terms
- Problem Boundary
- The people, place, service, period and system elements included in a project definition.
- Stakeholder
- A person or group affected by, responsible for or able to influence a project.
- Requirement
- A justified condition or outcome that a proposed design must satisfy.
- Baseline
- The reference condition against which a proposed change is evaluated.
- Design Criterion
- A dimension used to compare concepts, linked to project goals and constraints.
- Traceability
- The ability to connect a decision to its evidence, assumption, method and responsible author.
- Sensitivity Test
- An analysis of how a result changes when an uncertain input changes.
- Prototype
- A limited representation built to test a specific design claim or uncertainty.
- Validation
- Evidence that a proposed result serves the intended need in its context.
- Integration Review
- A check that independently developed project sections use consistent boundaries, terms and evidence.
Evidence-Led Energy Project Design FAQ
How narrow should a project problem be?
Narrow enough to identify users, service, place, time and a measurable burden, but not so narrow that it prescribes one technology before investigation. A bounded problem lets the team collect relevant evidence and compare distinct interventions. If every observation supports the first idea, the boundary may have been written around the solution.
What counts as useful field evidence?
Useful evidence changes a requirement, baseline, concept or test. Observation can reveal timing and workflow; interviews can reveal responsibility and unmet needs; measurements can quantify the energy service or environmental condition. Record context and limitations. A photograph or quotation without an identified decision link is documentation, not yet design evidence.
Should the highest decision-matrix score always win?
No. A score organises assumptions; it does not replace judgement. Review whether criteria are independent, weights are justified and any threshold requirement has been hidden inside an average. Run sensitivity analysis on uncertain weights or performance. If a small plausible change reverses the ranking, report that instability and propose a targeted test.
How should laboratory work support the project?
Use laboratory activity to establish a method, parameter or mechanism that the project argument needs. State the tested question, setup, result, uncertainty and how the result changes a design choice. Do not force a laboratory measurement into the project if its scale or conditions are unrelated; explain the transfer boundary instead.
How can a team prevent fragmented writing?
Assign cross-cutting owners as well as section owners. One person verifies units and calculations, another checks source-to-claim links, and another reviews visual and terminology consistency. Schedule an integration review before final formatting. Read the report by following one requirement from field evidence through concept selection, test and conclusion.
Assessment move
Study the project chapter by building a live traceability table rather than memorising a generic design cycle. Use columns for observation, interpretation, requirement, concept response, calculation or test, result and decision. Populate it with one realistic energy service. Challenge every row by asking whether the evidence could support another interpretation.
Generate at least three concepts that act at different system points, then compare them with criteria established before scoring. For calculations, use a baseline and label every assumption about operating time, load, efficiency and adoption. Change the most uncertain assumption across a plausible range and observe whether the preferred concept changes.
For prototypes, write the failure that would make the concept unacceptable and design the smallest test capable of revealing it. Practise a two-minute oral explanation that moves from user need to environmental benefit without skipping the evidence bridge. In team work, rotate the role of integration reviewer so every member sees how inconsistent units, repeated claims or missing sources weaken the whole submission.
The final check is backward: start at the recommendation and trace every important word to a criterion, result and original need. Any word that cannot be traced should be qualified, tested or removed.