BUILD IT BETTER · INTEGRATION CONTROL: Your Resilient Systems Challenge now has to work as one system, not a collection of good parts. Lock an architecture, test normal operation, remove the primary power path, apply combined pressure and decide whether the design remains resilient enough to enter next week’s blackout scenario.
ACTIVE OBJECTIVEBUILD IT BETTER · INTEGRATION CONTROL: Your Resilient Systems Challenge now has to work as one system, not a collection of good parts. Lock an architecture, test normal operation, remove the primary power path, apply combined pressure and decide whether the design remains resilient enough to enter next week’s blackout scenario.
Optional: pen + paper for rough working if that helps you think.
HOW TO DO IT
Read or listen to the Briefing + Learn.
Do the interactive mission.
Use facts from the reading and maths parts.
Make your choice and save your project step.
Play the weekly game. Finish Check-in.
WORK YOUR WAY
Short bursts are fine. Use Learning Tools for easier reading, read-aloud, less on screen, stronger contrast, no-rush and quieter-screen options.
If you get stuck, look at the example and try again.
SCIENCE SAFETY: The science investigations in this Senior mission are designed as virtual/screen-based activities unless the page clearly says otherwise. Do not improvise mains electricity, heating or chemical experiments at home.
PROJECT NOTE: Your project can stay digital. Physical making is optional unless you choose that format.
MISSION BRIEFING
BUILD IT BETTER · INTEGRATION CONTROL: Your Resilient Systems Challenge now has to work as one system, not a collection of good parts. Lock an architecture, test normal operation, remove the primary power path, apply combined pressure and decide whether the design remains resilient enough to enter next week’s blackout scenario.
✓Explain feedback, redundancy and trade-offs as properties of integrated engineered systems.
✓Test one unchanged architecture across multiple conditions so differences can be attributed to the pressure or fault rather than a redesign between trials.
✓Compare resilience, performance, energy and design-cost evidence instead of optimising one metric in isolation.
✓Trace how failure can propagate through dependencies between structural, power, sensing and control subsystems.
✓Evaluate an engineering design using performance alongside sustainability, maintainability, accessibility, safety and the consequences of failure.
◈
INTERACTIVE LEARN MODE
No passive video this week.
This mission is deliberately built around its simulator, investigation, decision room or prototype instead of an external video.
INTEGRATION changes the engineering problem. A strong component can still sit inside a weak system if dependencies are poorly designed. FEEDBACK allows information about system state to affect control. REDUNDANCY provides another path or resource when one fails. Both can improve resilience, but they add cost, materials, energy use or complexity. Optimisation therefore means finding a defensible balance across CRITERIA + CONSTRAINTS + FAILURE BEHAVIOUR + TRADE-OFFS. To compare fault responses fairly, lock the architecture and change the test condition rather than redesigning between each trial.
INTEGRATION changes the engineering problem. A strong component can still sit inside a weak system if dependencies are poorly designed. FEEDBACK allows information about system state to affect control. REDUNDANCY provides another path or resource when one fails. Both can improve resilience, but they add cost, materials, energy use or complexity. Optimisation therefore means finding a defensible balance across CRITERIA + CONSTRAINTS + FAILURE BEHAVIOUR + TRADE-OFFS. To compare fault responses fairly, lock the architecture and change the test condition rather than redesigning between each trial.
LEARNING BUILD
Learn it. See it. Try it.
Look at the example. Check another point of view. Then try the task.
Step 1: Choose a starting clueWHAT YOU ALREADY KNOW
This week’s first target:Explain feedback, redundancy and trade-offs as properties of integrated engineered systems.
Which clue is a good place to start?
Choose a source that can directly support part of the investigation. More than one source may be useful, but start with evidence that does not outrun its support.
Need more help? See the teaching
TEACH 1 · CORE MODEL
INTEGRATION changes the engineering problem. A strong component can still sit inside a weak system if dependencies are poorly designed. FEEDBACK allows information about system state to affect control. REDUNDANCY provides another path or resource when one fails. Both can improve resilience, but they add cost, materials, energy use or complexity. Optimisation therefore means finding a defensible balance across CRITERIA + CONSTRAINTS + FAILURE BEHAVIOUR + TRADE-OFFS. To compare fault responses fairly, lock the architecture and change the test condition rather than redesigning between each trial.
TEACH 2 · WHAT TO NOTICE
Explain feedback, redundancy and trade-offs as properties of integrated engineered systems.Test one unchanged architecture across multiple conditions so differences can be attributed to the pressure or fault rather than a redesign between trials.
TEACH 3 · CONNECT + TRANSFER
Compare resilience, performance, energy and design-cost evidence instead of optimising one metric in isolation. Trace how failure can propagate through dependencies between structural, power, sensing and control subsystems. Evaluate an engineering design using performance alongside sustainability, maintainability, accessibility, safety and the consequences of failure.
WORKED EXAMPLE · EVIDENCE
NORMAL OPERATION
A fictional integrated design can score well under normal operation while still depending heavily on one power path or one control pathway. Normal performance alone is not a resilience test.
Reasoning: Start with exactly what the source establishes. Connect it to the relevant concept, then stop before the claim becomes broader than the evidence. Now compare it with WHOLE-SYSTEM EVALUATION: A technically resilient design can still be poor overall if it is excessively resource-intensive, inaccessible, difficult to maintain or unsafe when it fails.
Why caution still matters:This item is useful context, but context is not the same as direct proof. Combine it with stronger evidence before making a broad conclusion.
WORKED EXAMPLE · MATHS / DATA ROUTE
A system’s performance score falls from 88 under normal operation to 66 under a fault. What is the percentage decrease relative to the normal score, rounded to the nearest whole percent?
This week’s maths/data focus:Measurement, performance indices, data comparison, constraints and optimisation.
Name the variable or relationship, keep the units visible, calculate or compare, then interpret the result as evidence about the system. A result can support an explanation without proving every possible cause.
Worked solution:The drop is 88 − 66 = 22 points. Relative decrease = 22 ÷ 88 × 100 = 25%.Answer check:25%. Now return the result to the question and state what it means in context.
WE DO · GUIDED PRACTICE
Which source needs the most caution before it is used to support a broad conclusion?
Choose a source that mainly supplies context rather than direct proof of the whole conclusion.
YOU TRY · INDEPENDENT PRACTICE
For Build It Better, explain one core idea, connect it to one named source or observation and one quantitative/data point from this page, then state an alternative explanation, trade-off or limitation that a strong judgement must consider.
Write at least 30 words. Name the evidence or data you are using and keep the claim inside what it can support.
MISCONCEPTION CHECK
WHOLE-SYSTEM EVALUATION:A technically resilient design can still be poor overall if it is excessively resource-intensive, inaccessible, difficult to maintain or unsafe when it fails.
This item is useful context, but context is not the same as direct proof. Combine it with stronger evidence before making a broad conclusion.
HELP
Try: “If ___ changes, the mechanism predicts ___. Evidence ___ supports/challenges that. An alternative explanation is ___. I would test ___ next.”
STRETCH · OPTIONAL
Build the strongest reasonable counter-argument or alternative explanation. Name one additional piece of evidence that could distinguish between the two positions.
BUILD IT BETTER · INTEGRATION CONTROL⌘
BUILD IT BETTER
Integrate it. Break it. Optimise it.
Design an integrated emergency system with structural, electrical and digital subsystems, then fault-test interactions and optimise resilience under constraints.
SYSTEM INTERACTIONS · 3 LINKS
LINK 1
A backup energy source activates when the primary supply fails.
LINK 2
A position sensor sends information to the controller.
LINK 3
A reinforced frame carries load but increases mass and material use.
INTEGRATED EMERGENCY TRANSFER SYSTEM
Meet the resilience target without ignoring cost, energy or failure interactions.
STANDBY
This is a fictional low-voltage systems model. Scores are deterministic teaching outputs designed for comparison, not real engineering specifications.
Test the same architecture with primary power failure.
COMBINED PRESSURENOT LOGGED
Test the same architecture with combined pressure.
Choose an architecture, test normal operation, then fault-test the same configuration. Changing architecture resets the required test set so comparisons stay valid.
OPTIMISATION
Why is the highest resilience score not automatically the best design?
CASCADE THINKING
Why can a fault in one subsystem affect another subsystem?
SUSTAINABILITY + ETHICS
Which evaluation is most complete?
Classify the three integration links, complete a consistent normal/power-fault/combined-pressure test set, then pass optimisation, cascade and ethics checks.
OPEN THE WEEK 8 EVIDENCE FILES
SOURCE 1
NORMAL OPERATION
A fictional integrated design can score well under normal operation while still depending heavily on one power path or one control pathway. Normal performance alone is not a resilience test.
SOURCE 2
POWER REDUNDANCY
In the teaching model, a backup supply reduces the performance loss caused by a primary-power fault, but it adds design-cost points, material and energy overhead.
SOURCE 3
FEEDBACK CONTROL
A sensor-based controller can improve normal positioning performance, but it also creates a dependency on accurate sensing. A sensor fault can therefore change system behaviour.
SOURCE 4
COMBINED PRESSURE
When more than one pressure is applied, interacting weaknesses can produce a larger performance loss than a single isolated fault. The model simplifies these interactions into deterministic scores.
SOURCE 5
WHOLE-SYSTEM EVALUATION
A technically resilient design can still be poor overall if it is excessively resource-intensive, inaccessible, difficult to maintain or unsafe when it fails.
INVESTIGATE + ENGLISH · EVIDENCE CASE
Integration creates dependencies — and dependencies create both capability and risk
A final engineering system can include a structure, energy supply, drive mechanism, sensors and control logic. Each subsystem may work well alone, but integration creates dependencies. If the controller depends on a sensor and the sensor fails, the control system may lose useful information. If every subsystem depends on one power source, a single power fault can affect the whole system. Redundancy can reduce that vulnerability, but duplicate components also use materials, budget and maintenance effort. A defensible final design therefore compares normal performance with fault behaviour, records constraints and accepts that resilience is one objective among several rather than a licence to add unlimited backup systems.
MAKE THE CALL
Choose the architecture you would carry into System Failure: Blackout. Defend it using resilience, performance, cost and energy evidence, explain the strongest remaining failure pathway, and name one modification you rejected because its trade-off was not justified.
BUILD YOUR CASE CONCLUSION1. Make the call. 2. Use at least two relevant pieces of evidence. 3. Explain one limitation or uncertainty. 4. Finish with what can responsibly be concluded.Strong structure: My judgement is… The strongest evidence is… However, we still do not know… Therefore…
CASE CONCLUSION: Write 240–320 words documenting your Year 8 integrated final build. Define the architecture and criteria, compare the same configuration under normal, power-fault and combined-pressure conditions, explain one dependency or cascading-failure pathway, justify one redundancy or feedback choice, quantify one trade-off and evaluate one sustainability, accessibility, maintenance or ethical consideration.
0/240 words minimum for this writing mission.
CLAIMEVIDENCELIMITATIONCONCLUSION
MATHS + DATA LAB
Check the numbers.
HOW TO SUCCEEDRead the situation first. Estimate what a sensible answer should look like, choose an efficient calculation, then use the feedback to check your reasoning.For data questions, explain what the number shows — and what it does not prove.
A system’s performance score falls from 88 under normal operation to 66 under a fault. What is the percentage decrease relative to the normal score, rounded to the nearest whole percent?
Estimate first, then choose the answer.
MISSION 05 · MATHS + DATA LAB
DATA TRAINING
FRACTIONS + PERCENT · YEAR 8 EXTENSION
6 PROBLEMS
QUICK METHODFRACTIONS + PERCENT
Convert between fractions, decimals and percentages, then calculate from the whole.
GUIDED · Q01–Q03Use the quick method, then check the explanation.
Q01
What is 25% of 200?
25% of 200 = 0.25 × 200 = 50.
Q02
Which fraction equals 50%?
50% means 50 out of 100, which simplifies to 1/2.
Q03
0.25 as a percentage is…
Multiply a decimal by 100 to convert it to a percentage: 25%.
INDEPENDENT · Q04
Which is largest?
0.6 = 60%, which is larger than 55%, 50% and 45%.
INDEPENDENT · Q05
A $80 item is reduced by 25%. What is the discount?
25% is one quarter; one quarter of $80 is $20.
INDEPENDENT · Q06
After a 25% discount on $80, what is the new price?
$80 − $20 discount = $60.
OPTIONAL CHALLENGE · OPEN RESPONSE
A price rises 20%, then falls 20%. Is it back to the starting price? Explain with a numerical example.
0 words · optional
PROJECT HQ · TERM 3 · KEEP BUILDING
PROJECT HQ · PROJECT FILE 08
FINAL BUILD.
Start something real. Build an idea, test it, improve it, and share it. Make your move.
FINAL BUILD your Resilient Systems Challenge as an integrated system. Freeze the architecture, document the strongest evidence and trade-offs, identify the most important remaining cascade pathway and define what must survive next week’s blackout test.
WEEK 8 · FINAL BUILD · Freeze the integrated architecture. Document why this version is defensible across performance, resilience and constraints — including the failure pathway you still cannot remove.
Complete all five fields. Your final build is saved into the Resilient Systems Challenge record.
Project sharing will be optional. A future upload system must keep private submission separate from public-showcase/marketing permission.
CHECK-IN
What changed in your thinking?
26MASTER MODE
YEAR 8 · REMIX · TERM 3 / WEEK 8
PULSE GRID
Read two-hand cues and hold the rhythm as patterns become denser.
02LEARN
03INVESTIGATE
05DECIDE
07PROJECT
08CHECK-IN