- 1 — Name the input, process and output of a simple table lamp.
- 2 — Explain the defining difference between open and closed loop.
- 3 — Give two K345 open-loop examples.
- 4 — Give three K345 closed-loop examples.
- 5 — Explain feedback in a water cistern.
- 6 — Explain temperature feedback in an air conditioner.
- 7 — Name the kit-sensing categories specified in outcome 30.
- 8 — Explain why counting needs an event definition.
- 9 — Describe a plausible test of an invented light indicator.
- 10 — Give one sensor-placement error.
- 11 — Explain why the user interface matters.
- 12 — State one safety and one coursework-integrity rule.
Answer guide: (1) switch, enabling circuit, illumination. (2) output-related feedback informs subsequent action. (3) lamp, thermometer, stapler or can opener. (4) hot-water dispenser, water cistern, air conditioner. (5) float level influences valve. (6) measured temperature influences cooling. (7) light, moisture, temperature plus counting. (8) prevent duplicates and missing counts. (9) compare expected indication under two known fictional conditions. (10) sensor beside heat or in shadow. (11) accessibility and clarity. (12) supervised suitable kit work and authentic candidate journal.
64. Frequently asked questions
Do D&T students need to design custom transistor circuits?
The 2027 syllabus requires practical understanding and adaptation of available electronics kits, not a separate advanced transistor-design qualification.
Does a temperature display make an appliance closed loop?
Not by itself. The measured temperature must influence control of the output toward a desired condition.
Can a water cistern be closed loop without a microcontroller?
Yes. A mechanical float can provide feedback based on the level of water.
Should a beginner modify a household air conditioner?
No. Use block diagrams and school-approved kits instead of opening mains-powered equipment.
Can an adult write the assessed design journal for a pupil?
No. General coaching is appropriate, but the Design Project is assessed as authentic individual coursework.
65. Official K345 and linked reading
The primary examination document is SEAB 2027 SEC G3 Design & Technology K345, Section 2, learning outcomes 28–30. It names open and closed loop, inputs, process, output, feedback and available counting and sensing kits. Refer to the 2027 school-candidate syllabus directory for any changes.
Previous: Reference 347 — POA Correction of Errors. Next: Reference 349 — Business Ownership. Design foundations: Reference 335 — Design Prototyping and Reference 158 — Testing. Related science: Reference 340 — Measurement and Reference 286 — Physics Potential Dividers and Sensors. Browse the MOE V3.0 hub and immutable Clementi teaching standard.
Editorial review: 26 October 2026, Singapore. All Meridian sensor examples are fictional paper tests, not electrical operating instructions. The transferable habit is to identify the controlled variable, draw the information path and ask whether feedback actually changes operation.
63. Independent twelve-question checkpoint
- 1 — Name the input, process and output of a simple table lamp.
- 2 — Explain the defining difference between open and closed loop.
- 3 — Give two K345 open-loop examples.
- 4 — Give three K345 closed-loop examples.
- 5 — Explain feedback in a water cistern.
- 6 — Explain temperature feedback in an air conditioner.
- 7 — Name the kit-sensing categories specified in outcome 30.
- 8 — Explain why counting needs an event definition.
- 9 — Describe a plausible test of an invented light indicator.
- 10 — Give one sensor-placement error.
- 11 — Explain why the user interface matters.
- 12 — State one safety and one coursework-integrity rule.
Answer guide: (1) switch, enabling circuit, illumination. (2) output-related feedback informs subsequent action. (3) lamp, thermometer, stapler or can opener. (4) hot-water dispenser, water cistern, air conditioner. (5) float level influences valve. (6) measured temperature influences cooling. (7) light, moisture, temperature plus counting. (8) prevent duplicates and missing counts. (9) compare expected indication under two known fictional conditions. (10) sensor beside heat or in shadow. (11) accessibility and clarity. (12) supervised suitable kit work and authentic candidate journal.
64. Frequently asked questions
Do D&T students need to design custom transistor circuits?
The 2027 syllabus requires practical understanding and adaptation of available electronics kits, not a separate advanced transistor-design qualification.
Does a temperature display make an appliance closed loop?
Not by itself. The measured temperature must influence control of the output toward a desired condition.
Can a water cistern be closed loop without a microcontroller?
Yes. A mechanical float can provide feedback based on the level of water.
Should a beginner modify a household air conditioner?
No. Use block diagrams and school-approved kits instead of opening mains-powered equipment.
Can an adult write the assessed design journal for a pupil?
No. General coaching is appropriate, but the Design Project is assessed as authentic individual coursework.
65. Official K345 and linked reading
The primary examination document is SEAB 2027 SEC G3 Design & Technology K345, Section 2, learning outcomes 28–30. It names open and closed loop, inputs, process, output, feedback and available counting and sensing kits. Refer to the 2027 school-candidate syllabus directory for any changes.
Previous: Reference 347 — POA Correction of Errors. Next: Reference 349 — Business Ownership. Design foundations: Reference 335 — Design Prototyping and Reference 158 — Testing. Related science: Reference 340 — Measurement and Reference 286 — Physics Potential Dividers and Sensors. Browse the MOE V3.0 hub and immutable Clementi teaching standard.
Editorial review: 26 October 2026, Singapore. All Meridian sensor examples are fictional paper tests, not electrical operating instructions. The transferable habit is to identify the controlled variable, draw the information path and ask whether feedback actually changes operation.
- Every powered product is closed loop — check whether actual output affects later action.
- A table lamp with one switch always measures brightness — simple models do not.
- A thermometer automatically controls room temperature — it can simply report.
- A sensor is the same as an actuator — one measures, the other changes output.
- Feedback is any indicator light — look for a returned measurement influencing control.
- Open-loop products are always inferior — simplicity may fit the user.
- Closed-loop systems never fail — sensor and actuator problems remain.
- Counting means recording every millisecond a button is held — define an event.
- A moisture sensor certifies food or water safety — it does not.
- An LED lighting means the full user need is met — evaluate purpose and visibility.
- All student prototypes must use a programmable chip — K345 focuses on adapting available kits.
- A perfect-looking design journal can contain invented data — genuine records are required.
- Mains-powered appliance changes are safe school experiments — do not attempt them.
- More electronic parts always make a product sustainable — consider energy and repairability.
63. Independent twelve-question checkpoint
- 1 — Name the input, process and output of a simple table lamp.
- 2 — Explain the defining difference between open and closed loop.
- 3 — Give two K345 open-loop examples.
- 4 — Give three K345 closed-loop examples.
- 5 — Explain feedback in a water cistern.
- 6 — Explain temperature feedback in an air conditioner.
- 7 — Name the kit-sensing categories specified in outcome 30.
- 8 — Explain why counting needs an event definition.
- 9 — Describe a plausible test of an invented light indicator.
- 10 — Give one sensor-placement error.
- 11 — Explain why the user interface matters.
- 12 — State one safety and one coursework-integrity rule.
Answer guide: (1) switch, enabling circuit, illumination. (2) output-related feedback informs subsequent action. (3) lamp, thermometer, stapler or can opener. (4) hot-water dispenser, water cistern, air conditioner. (5) float level influences valve. (6) measured temperature influences cooling. (7) light, moisture, temperature plus counting. (8) prevent duplicates and missing counts. (9) compare expected indication under two known fictional conditions. (10) sensor beside heat or in shadow. (11) accessibility and clarity. (12) supervised suitable kit work and authentic candidate journal.
64. Frequently asked questions
Do D&T students need to design custom transistor circuits?
The 2027 syllabus requires practical understanding and adaptation of available electronics kits, not a separate advanced transistor-design qualification.
Does a temperature display make an appliance closed loop?
Not by itself. The measured temperature must influence control of the output toward a desired condition.
Can a water cistern be closed loop without a microcontroller?
Yes. A mechanical float can provide feedback based on the level of water.
Should a beginner modify a household air conditioner?
No. Use block diagrams and school-approved kits instead of opening mains-powered equipment.
Can an adult write the assessed design journal for a pupil?
No. General coaching is appropriate, but the Design Project is assessed as authentic individual coursework.
65. Official K345 and linked reading
The primary examination document is SEAB 2027 SEC G3 Design & Technology K345, Section 2, learning outcomes 28–30. It names open and closed loop, inputs, process, output, feedback and available counting and sensing kits. Refer to the 2027 school-candidate syllabus directory for any changes.
Previous: Reference 347 — POA Correction of Errors. Next: Reference 349 — Business Ownership. Design foundations: Reference 335 — Design Prototyping and Reference 158 — Testing. Related science: Reference 340 — Measurement and Reference 286 — Physics Potential Dividers and Sensors. Browse the MOE V3.0 hub and immutable Clementi teaching standard.
Editorial review: 26 October 2026, Singapore. All Meridian sensor examples are fictional paper tests, not electrical operating instructions. The transferable habit is to identify the controlled variable, draw the information path and ask whether feedback actually changes operation.
54. Meridian Sensor Studio: sixteen fictional design cards
Every design case is an original paper-only simulation, not a live electrical test or candidate Design Project submission. Any practical adaptation must follow the school’s kit instructions and supervision.
A — Basic switch lamp
Original fictional design case: A fictional lamp turns on only when the user presses a switch.
Input or sensing step: Human switch action.
Decision or process: Enable power to a lighting output.
Output and feedback: Light switches on; no automatic brightness comparison.
Design diagnostic: Does the function require feedback?
Evidence and safety boundary: No electrical build is described.
B — Temperature-reading instrument
Original fictional design case: A display shows room temperature but controls no device.
Input or sensing step: Ambient temperature sensing.
Decision or process: Convert measurement to displayed value.
Output and feedback: A reading, not active temperature regulation.
Design diagnostic: Is this closed loop?
Evidence and safety boundary: Sensor precision is unspecified.
C — Air-conditioning example
Original fictional design case: A conceptual air conditioner aims for a chosen temperature.
Input or sensing step: Measure room temperature.
Decision or process: Compare with user-set condition.
Output and feedback: Cooling changes the temperature and measurement repeats.
Design diagnostic: Identify the feedback arrow.
Evidence and safety boundary: Not a guide to alter real appliances.
D — Water cistern
Original fictional design case: An imagined float rises as water enters.
Input or sensing step: Water-level input through float.
Decision or process: Mechanism changes the inlet valve state.
Output and feedback: Flow adjusts as level changes, giving feedback.
Design diagnostic: How is this closed loop without electronics?
Evidence and safety boundary: Real plumbing requires professional work.
E — Hot-water dispenser
Original fictional design case: A school diagram shows controlled heating around a chosen temperature.
Input or sensing step: Temperature measurement.
Decision or process: Compare against the desired heating condition.
Output and feedback: Heating operates accordingly, with repeated reading.
Design diagnostic: What failure occurs if the sensor lies?
Evidence and safety boundary: Do not modify mains/water heaters.
F — Display counter
Original fictional design case: Ten presses are deliberately recorded in a hypothetical kit.
Input or sensing step: Button event input.
Decision or process: Register one event per valid press.
Output and feedback: Expected count ten.
Design diagnostic: What if display shows eleven?
Evidence and safety boundary: The exact kit is unspecified.
G — False repeated count
Original fictional design case: A held-down button creates several increments.
Input or sensing step: Duration differs from a single discrete press.
Decision or process: Define a valid event and test repeat handling.
Output and feedback: Incorrect count indicates a design issue.
Design diagnostic: Where should the event rule be placed?
Evidence and safety boundary: No component-level circuit is given.
H — Low light condition
Original fictional design case: An imagined reading falls below a fictional practice threshold.
Input or sensing step: Light sensor.
Decision or process: Compare with selected threshold.
Output and feedback: Indicator appears.
Design diagnostic: Does the indicator improve accessibility?
Evidence and safety boundary: Not an actual classroom lighting standard.
I — Sensor facing wrong way
Original fictional design case: A light sensor is enclosed under the product.
Input or sensing step: It measures local darkness, not the work surface.
Decision or process: Reposition conceptually to represent user condition.
Output and feedback: The alert may be misleading.
Design diagnostic: Which orientation should the model test?
Evidence and safety boundary: No empirical readings are available.
J — Moisture monitoring
Original fictional design case: A hypothetical potted-plant alert responds to dry medium.
Input or sensing step: Moisture-sensing kit.
Decision or process: Compare with a defined practice state.
Output and feedback: Simple indicator suggests user inspection.
Design diagnostic: Should it automatically water the plant?
Evidence and safety boundary: Not a soil agronomy or water-safety certificate.
K — Temperature near a heater
Original fictional design case: A sensor next to an imaginary heat source reads above ambient.
Input or sensing step: Local thermal input is biased.
Decision or process: Evaluate position and measurement purpose.
Output and feedback: Wrong placement causes misleading output.
Design diagnostic: How would a fair comparison be organised?
Evidence and safety boundary: Real safety limits cannot be inferred.
L — An inaccessible alarm
Original fictional design case: A visual indicator is too small for its intended user.
Input or sensing step: Output visibility is a user constraint.
Decision or process: Compare interface design options.
Output and feedback: System functions electronically but fails usability.
Design diagnostic: What accessible alternative is appropriate?
Evidence and safety boundary: User testing is hypothetical.
M — Overcomplicated stationery holder
Original fictional design case: A student adds sensors to a product only needing stable storage.
Input or sensing step: No environmental measurement is required.
Decision or process: Remove unnecessary electronics.
Output and feedback: A passive structure may meet the need better.
Design diagnostic: How is this good design rather than reduced ambition?
Evidence and safety boundary: The evaluated product is fictional.
N — Closed-loop assumption
Original fictional design case: A device flashes whenever temperature rises but does not change the environment.
Input or sensing step: Temperature monitoring.
Decision or process: Process threshold into warning.
Output and feedback: Alert is produced; temperature is not automatically regulated.
Design diagnostic: Is this truly a temperature-control loop?
Evidence and safety boundary: No feedback into heating/cooling is specified.
O — Repeated switching
Original fictional design case: A conceptual indicator flickers repeatedly around a threshold.
Input or sensing step: Noisy or varying sensor signal.
Decision or process: Review decision robustness.
Output and feedback: Repeated toggling undermines usability.
Design diagnostic: What conceptual change might reduce this?
Evidence and safety boundary: No specific electronics solution is mandated.
P — Journal integrity
Original fictional design case: A fictional candidate produces immaculate final sketches but invents prior tests.
Input or sensing step: The claimed input/output observations were not measured.
Decision or process: Keep genuine dated evidence of work.
Output and feedback: Fabrication undermines the assessment.
Design diagnostic: What would authentic iteration show?
Evidence and safety boundary: The case is not a real student.
55. Worked block diagram: low-light indicator
Input: light level as measured by an appropriate kit. Process: compare with an explicitly defined practice threshold. Output: indicator status. If the device only reports low light, it is not automatically a closed-loop room-brightness regulator.
The diagram helps separate monitoring from control. An actual light-regulating system would require an appropriate output that changes illumination and a feedback route measuring the result.
56. Worked block diagram: cistern level control
Input: actual water level as represented by float position. Process: mechanical comparison with desired level. Output: inlet valve opening or closing. Feedback: changes in water level move the float and influence the next valve state.
This illustrates K345’s closed-loop concept without a sensor chip or code. A practical plumbing installation remains outside school-paper guidance.
57. A fair prototype evaluation
A suitable test table can record input condition, expected output, observed output, discrepancy and proposed change. For a fictional counter, deliberately create five separate events and compare the indicated count with five.
Tests should cover failure conditions as well as expected conditions. Only real school-authorised observations may appear as actual assessed journal data.
58. A strong written examination answer
Describe the user need, correctly classify open or closed loop, name input/process/output and show whether the result is fed back to adjust operation. Evaluate one benefit and one limitation relevant to the product.
Avoid generic claims such as ‘all smart devices save electricity’ or ‘sensors make it safe’. The data and mechanism must support the answer.
59. How parents and tutors can practise ethically
Use drawings of simple appliances and ask the pupil to label functional blocks. Then describe a missing input or failed indicator and ask what evidence would discriminate its cause.
This teaches the syllabus without building unsafe circuits or producing a candidate’s coursework for them.
60. Fencing Method for D&T electronics
Fence one: user need. Fence two: input versus output. Fence three: sensing versus actuation. Fence four: open versus closed loop. Fence five: measuring feedback. Fence six: prototype evidence and safe refinement.
Only after those distinctions are secure should a pupil compare multiple sensors or discuss energy and repairability.
61. Depth–Load–Transfer diagnostic
Depth: can the learner explain why an air conditioner uses feedback while a simple lamp does not? Load: can they keep sensing, processing, interface, output and user context separate in a longer case? Transfer: can they classify an unfamiliar product with only a functional description and avoid guessing its internal components?
A pupil who equates every thermometer with closed-loop control needs a return-path diagram. One who treats all electronics as complex programming needs available-kit scope correction.
62. Common misunderstandings and repairs
- Every powered product is closed loop — check whether actual output affects later action.
- A table lamp with one switch always measures brightness — simple models do not.
- A thermometer automatically controls room temperature — it can simply report.
- A sensor is the same as an actuator — one measures, the other changes output.
- Feedback is any indicator light — look for a returned measurement influencing control.
- Open-loop products are always inferior — simplicity may fit the user.
- Closed-loop systems never fail — sensor and actuator problems remain.
- Counting means recording every millisecond a button is held — define an event.
- A moisture sensor certifies food or water safety — it does not.
- An LED lighting means the full user need is met — evaluate purpose and visibility.
- All student prototypes must use a programmable chip — K345 focuses on adapting available kits.
- A perfect-looking design journal can contain invented data — genuine records are required.
- Mains-powered appliance changes are safe school experiments — do not attempt them.
- More electronic parts always make a product sustainable — consider energy and repairability.
63. Independent twelve-question checkpoint
- 1 — Name the input, process and output of a simple table lamp.
- 2 — Explain the defining difference between open and closed loop.
- 3 — Give two K345 open-loop examples.
- 4 — Give three K345 closed-loop examples.
- 5 — Explain feedback in a water cistern.
- 6 — Explain temperature feedback in an air conditioner.
- 7 — Name the kit-sensing categories specified in outcome 30.
- 8 — Explain why counting needs an event definition.
- 9 — Describe a plausible test of an invented light indicator.
- 10 — Give one sensor-placement error.
- 11 — Explain why the user interface matters.
- 12 — State one safety and one coursework-integrity rule.
Answer guide: (1) switch, enabling circuit, illumination. (2) output-related feedback informs subsequent action. (3) lamp, thermometer, stapler or can opener. (4) hot-water dispenser, water cistern, air conditioner. (5) float level influences valve. (6) measured temperature influences cooling. (7) light, moisture, temperature plus counting. (8) prevent duplicates and missing counts. (9) compare expected indication under two known fictional conditions. (10) sensor beside heat or in shadow. (11) accessibility and clarity. (12) supervised suitable kit work and authentic candidate journal.
64. Frequently asked questions
Do D&T students need to design custom transistor circuits?
The 2027 syllabus requires practical understanding and adaptation of available electronics kits, not a separate advanced transistor-design qualification.
Does a temperature display make an appliance closed loop?
Not by itself. The measured temperature must influence control of the output toward a desired condition.
Can a water cistern be closed loop without a microcontroller?
Yes. A mechanical float can provide feedback based on the level of water.
Should a beginner modify a household air conditioner?
No. Use block diagrams and school-approved kits instead of opening mains-powered equipment.
Can an adult write the assessed design journal for a pupil?
No. General coaching is appropriate, but the Design Project is assessed as authentic individual coursework.
65. Official K345 and linked reading
The primary examination document is SEAB 2027 SEC G3 Design & Technology K345, Section 2, learning outcomes 28–30. It names open and closed loop, inputs, process, output, feedback and available counting and sensing kits. Refer to the 2027 school-candidate syllabus directory for any changes.
Previous: Reference 347 — POA Correction of Errors. Next: Reference 349 — Business Ownership. Design foundations: Reference 335 — Design Prototyping and Reference 158 — Testing. Related science: Reference 340 — Measurement and Reference 286 — Physics Potential Dividers and Sensors. Browse the MOE V3.0 hub and immutable Clementi teaching standard.
Editorial review: 26 October 2026, Singapore. All Meridian sensor examples are fictional paper tests, not electrical operating instructions. The transferable habit is to identify the controlled variable, draw the information path and ask whether feedback actually changes operation.
- 1 — Describe the actual user and the practical need.
- 2 — Identify the condition to monitor or change.
- 3 — Decide whether the task needs open-loop command or closed-loop regulation.
- 4 — Specify input and the appropriate sensing or human action.
- 5 — Explain the process or comparison logic.
- 6 — State the physical or informational output.
- 7 — For feedback systems, identify the measured controlled condition and return path.
- 8 — Choose only available, school-approved components or kits.
- 9 — Test mock-up placement, reach and interface clarity safely.
- 10 — Compare expected and observed outputs under more than one condition.
- 11 — Record genuine evidence, limitations, maintenance and sustainability issues.
- 12 — Revise the design against the brief and specifications without inventing results.
54. Meridian Sensor Studio: sixteen fictional design cards
Every design case is an original paper-only simulation, not a live electrical test or candidate Design Project submission. Any practical adaptation must follow the school’s kit instructions and supervision.
A — Basic switch lamp
Original fictional design case: A fictional lamp turns on only when the user presses a switch.
Input or sensing step: Human switch action.
Decision or process: Enable power to a lighting output.
Output and feedback: Light switches on; no automatic brightness comparison.
Design diagnostic: Does the function require feedback?
Evidence and safety boundary: No electrical build is described.
B — Temperature-reading instrument
Original fictional design case: A display shows room temperature but controls no device.
Input or sensing step: Ambient temperature sensing.
Decision or process: Convert measurement to displayed value.
Output and feedback: A reading, not active temperature regulation.
Design diagnostic: Is this closed loop?
Evidence and safety boundary: Sensor precision is unspecified.
C — Air-conditioning example
Original fictional design case: A conceptual air conditioner aims for a chosen temperature.
Input or sensing step: Measure room temperature.
Decision or process: Compare with user-set condition.
Output and feedback: Cooling changes the temperature and measurement repeats.
Design diagnostic: Identify the feedback arrow.
Evidence and safety boundary: Not a guide to alter real appliances.
D — Water cistern
Original fictional design case: An imagined float rises as water enters.
Input or sensing step: Water-level input through float.
Decision or process: Mechanism changes the inlet valve state.
Output and feedback: Flow adjusts as level changes, giving feedback.
Design diagnostic: How is this closed loop without electronics?
Evidence and safety boundary: Real plumbing requires professional work.
E — Hot-water dispenser
Original fictional design case: A school diagram shows controlled heating around a chosen temperature.
Input or sensing step: Temperature measurement.
Decision or process: Compare against the desired heating condition.
Output and feedback: Heating operates accordingly, with repeated reading.
Design diagnostic: What failure occurs if the sensor lies?
Evidence and safety boundary: Do not modify mains/water heaters.
F — Display counter
Original fictional design case: Ten presses are deliberately recorded in a hypothetical kit.
Input or sensing step: Button event input.
Decision or process: Register one event per valid press.
Output and feedback: Expected count ten.
Design diagnostic: What if display shows eleven?
Evidence and safety boundary: The exact kit is unspecified.
G — False repeated count
Original fictional design case: A held-down button creates several increments.
Input or sensing step: Duration differs from a single discrete press.
Decision or process: Define a valid event and test repeat handling.
Output and feedback: Incorrect count indicates a design issue.
Design diagnostic: Where should the event rule be placed?
Evidence and safety boundary: No component-level circuit is given.
H — Low light condition
Original fictional design case: An imagined reading falls below a fictional practice threshold.
Input or sensing step: Light sensor.
Decision or process: Compare with selected threshold.
Output and feedback: Indicator appears.
Design diagnostic: Does the indicator improve accessibility?
Evidence and safety boundary: Not an actual classroom lighting standard.
I — Sensor facing wrong way
Original fictional design case: A light sensor is enclosed under the product.
Input or sensing step: It measures local darkness, not the work surface.
Decision or process: Reposition conceptually to represent user condition.
Output and feedback: The alert may be misleading.
Design diagnostic: Which orientation should the model test?
Evidence and safety boundary: No empirical readings are available.
J — Moisture monitoring
Original fictional design case: A hypothetical potted-plant alert responds to dry medium.
Input or sensing step: Moisture-sensing kit.
Decision or process: Compare with a defined practice state.
Output and feedback: Simple indicator suggests user inspection.
Design diagnostic: Should it automatically water the plant?
Evidence and safety boundary: Not a soil agronomy or water-safety certificate.
K — Temperature near a heater
Original fictional design case: A sensor next to an imaginary heat source reads above ambient.
Input or sensing step: Local thermal input is biased.
Decision or process: Evaluate position and measurement purpose.
Output and feedback: Wrong placement causes misleading output.
Design diagnostic: How would a fair comparison be organised?
Evidence and safety boundary: Real safety limits cannot be inferred.
L — An inaccessible alarm
Original fictional design case: A visual indicator is too small for its intended user.
Input or sensing step: Output visibility is a user constraint.
Decision or process: Compare interface design options.
Output and feedback: System functions electronically but fails usability.
Design diagnostic: What accessible alternative is appropriate?
Evidence and safety boundary: User testing is hypothetical.
M — Overcomplicated stationery holder
Original fictional design case: A student adds sensors to a product only needing stable storage.
Input or sensing step: No environmental measurement is required.
Decision or process: Remove unnecessary electronics.
Output and feedback: A passive structure may meet the need better.
Design diagnostic: How is this good design rather than reduced ambition?
Evidence and safety boundary: The evaluated product is fictional.
N — Closed-loop assumption
Original fictional design case: A device flashes whenever temperature rises but does not change the environment.
Input or sensing step: Temperature monitoring.
Decision or process: Process threshold into warning.
Output and feedback: Alert is produced; temperature is not automatically regulated.
Design diagnostic: Is this truly a temperature-control loop?
Evidence and safety boundary: No feedback into heating/cooling is specified.
O — Repeated switching
Original fictional design case: A conceptual indicator flickers repeatedly around a threshold.
Input or sensing step: Noisy or varying sensor signal.
Decision or process: Review decision robustness.
Output and feedback: Repeated toggling undermines usability.
Design diagnostic: What conceptual change might reduce this?
Evidence and safety boundary: No specific electronics solution is mandated.
P — Journal integrity
Original fictional design case: A fictional candidate produces immaculate final sketches but invents prior tests.
Input or sensing step: The claimed input/output observations were not measured.
Decision or process: Keep genuine dated evidence of work.
Output and feedback: Fabrication undermines the assessment.
Design diagnostic: What would authentic iteration show?
Evidence and safety boundary: The case is not a real student.
55. Worked block diagram: low-light indicator
Input: light level as measured by an appropriate kit. Process: compare with an explicitly defined practice threshold. Output: indicator status. If the device only reports low light, it is not automatically a closed-loop room-brightness regulator.
The diagram helps separate monitoring from control. An actual light-regulating system would require an appropriate output that changes illumination and a feedback route measuring the result.
56. Worked block diagram: cistern level control
Input: actual water level as represented by float position. Process: mechanical comparison with desired level. Output: inlet valve opening or closing. Feedback: changes in water level move the float and influence the next valve state.
This illustrates K345’s closed-loop concept without a sensor chip or code. A practical plumbing installation remains outside school-paper guidance.
57. A fair prototype evaluation
A suitable test table can record input condition, expected output, observed output, discrepancy and proposed change. For a fictional counter, deliberately create five separate events and compare the indicated count with five.
Tests should cover failure conditions as well as expected conditions. Only real school-authorised observations may appear as actual assessed journal data.
58. A strong written examination answer
Describe the user need, correctly classify open or closed loop, name input/process/output and show whether the result is fed back to adjust operation. Evaluate one benefit and one limitation relevant to the product.
Avoid generic claims such as ‘all smart devices save electricity’ or ‘sensors make it safe’. The data and mechanism must support the answer.
59. How parents and tutors can practise ethically
Use drawings of simple appliances and ask the pupil to label functional blocks. Then describe a missing input or failed indicator and ask what evidence would discriminate its cause.
This teaches the syllabus without building unsafe circuits or producing a candidate’s coursework for them.
60. Fencing Method for D&T electronics
Fence one: user need. Fence two: input versus output. Fence three: sensing versus actuation. Fence four: open versus closed loop. Fence five: measuring feedback. Fence six: prototype evidence and safe refinement.
Only after those distinctions are secure should a pupil compare multiple sensors or discuss energy and repairability.
61. Depth–Load–Transfer diagnostic
Depth: can the learner explain why an air conditioner uses feedback while a simple lamp does not? Load: can they keep sensing, processing, interface, output and user context separate in a longer case? Transfer: can they classify an unfamiliar product with only a functional description and avoid guessing its internal components?
A pupil who equates every thermometer with closed-loop control needs a return-path diagram. One who treats all electronics as complex programming needs available-kit scope correction.
62. Common misunderstandings and repairs
- Every powered product is closed loop — check whether actual output affects later action.
- A table lamp with one switch always measures brightness — simple models do not.
- A thermometer automatically controls room temperature — it can simply report.
- A sensor is the same as an actuator — one measures, the other changes output.
- Feedback is any indicator light — look for a returned measurement influencing control.
- Open-loop products are always inferior — simplicity may fit the user.
- Closed-loop systems never fail — sensor and actuator problems remain.
- Counting means recording every millisecond a button is held — define an event.
- A moisture sensor certifies food or water safety — it does not.
- An LED lighting means the full user need is met — evaluate purpose and visibility.
- All student prototypes must use a programmable chip — K345 focuses on adapting available kits.
- A perfect-looking design journal can contain invented data — genuine records are required.
- Mains-powered appliance changes are safe school experiments — do not attempt them.
- More electronic parts always make a product sustainable — consider energy and repairability.
63. Independent twelve-question checkpoint
- 1 — Name the input, process and output of a simple table lamp.
- 2 — Explain the defining difference between open and closed loop.
- 3 — Give two K345 open-loop examples.
- 4 — Give three K345 closed-loop examples.
- 5 — Explain feedback in a water cistern.
- 6 — Explain temperature feedback in an air conditioner.
- 7 — Name the kit-sensing categories specified in outcome 30.
- 8 — Explain why counting needs an event definition.
- 9 — Describe a plausible test of an invented light indicator.
- 10 — Give one sensor-placement error.
- 11 — Explain why the user interface matters.
- 12 — State one safety and one coursework-integrity rule.
Answer guide: (1) switch, enabling circuit, illumination. (2) output-related feedback informs subsequent action. (3) lamp, thermometer, stapler or can opener. (4) hot-water dispenser, water cistern, air conditioner. (5) float level influences valve. (6) measured temperature influences cooling. (7) light, moisture, temperature plus counting. (8) prevent duplicates and missing counts. (9) compare expected indication under two known fictional conditions. (10) sensor beside heat or in shadow. (11) accessibility and clarity. (12) supervised suitable kit work and authentic candidate journal.
64. Frequently asked questions
Do D&T students need to design custom transistor circuits?
The 2027 syllabus requires practical understanding and adaptation of available electronics kits, not a separate advanced transistor-design qualification.
Does a temperature display make an appliance closed loop?
Not by itself. The measured temperature must influence control of the output toward a desired condition.
Can a water cistern be closed loop without a microcontroller?
Yes. A mechanical float can provide feedback based on the level of water.
Should a beginner modify a household air conditioner?
No. Use block diagrams and school-approved kits instead of opening mains-powered equipment.
Can an adult write the assessed design journal for a pupil?
No. General coaching is appropriate, but the Design Project is assessed as authentic individual coursework.
65. Official K345 and linked reading
The primary examination document is SEAB 2027 SEC G3 Design & Technology K345, Section 2, learning outcomes 28–30. It names open and closed loop, inputs, process, output, feedback and available counting and sensing kits. Refer to the 2027 school-candidate syllabus directory for any changes.
Previous: Reference 347 — POA Correction of Errors. Next: Reference 349 — Business Ownership. Design foundations: Reference 335 — Design Prototyping and Reference 158 — Testing. Related science: Reference 340 — Measurement and Reference 286 — Physics Potential Dividers and Sensors. Browse the MOE V3.0 hub and immutable Clementi teaching standard.
Editorial review: 26 October 2026, Singapore. All Meridian sensor examples are fictional paper tests, not electrical operating instructions. The transferable habit is to identify the controlled variable, draw the information path and ask whether feedback actually changes operation.
Did you know that an ordinary table lamp with an on/off switch and an air conditioner that measures room temperature are fundamentally different kinds of control system? The lamp responds to the user’s input but does not check whether a desired brightness level has been reached. An air conditioner can monitor temperature and adjust cooling using feedback. Both contain input, processing and output in some form, yet the second has a route for comparing actual performance with a target.
Ministry of Education V3.0 Reference 348 develops the 2027 Singapore–Cambridge SEC G3 Design & Technology K345 syllabus, Section 2 Technology, learning outcomes 28–30. It explains open-loop and closed-loop control systems, input–process–output–feedback, examples such as a thermometer, table lamp, stapler, can opener, hot-water dispenser, water cistern and air conditioner, and appropriate adaptation of available electronic kits for counting and sensing light, moisture and temperature. The original Meridian Sensor Studio helps learners link user need, controls, safe low-voltage prototyping and purposeful evaluation.
This is an independent eduKateSG study resource, not an official MOE/SEAB document or an approved electrical wiring guide. The 2027 syllabus is centred on practical adaptation of available kits and safe, suitable technology; it does not separately specify designing complex transistor amplifiers, mains switching circuitry or microcontroller firmware from scratch. Do not open appliances, wire mains voltage, use unsupervised heaters or modify actual building control systems. Use school-approved low-voltage kits and teacher supervision where practical work is permitted.
1. A control system links inputs to useful outputs
A control system receives an input, uses a decision or mechanical process and produces an output. Its purpose is to perform a useful function under the conditions identified by the designer.
A complete explanation names the user, the system’s desired result and what physical change the system creates. Saying only ‘the circuit works’ does not show whether the user’s actual need is satisfied.
2. The exact syllabus boundary
K345 learning outcome 28 names open-loop examples including thermometer, table lamp, stapler and can opener, and closed-loop examples including hot-water dispenser, water cistern and air conditioner. Outcome 29 requires input, process, output and feedback. Outcome 30 covers adapting available kits for counting and sensing light, moisture and temperature.
Because the course includes 22-week individual project work assessed through authentic design journals, this guide teaches general principles and fictional cases rather than supplying an assessed student’s finished design or fabricated test record.
3. Inputs may be human actions or environmental signals
A person pressing a button, a measured light level or a detected water level can supply a system with information or an instruction. The nature of the input affects how the design responds.
A switch does not automatically measure the environment; it simply tells the system whether the user has requested an action under the simplest design.
4. Processing is the decision or mechanical transformation
A process may involve a simple physical mechanism, a switch path, a comparator built into an approved kit or another appropriate way of determining the response. It converts the input into meaningful action.
The syllabus’s conceptual framework does not require a custom computer program for every design. The processing route should be appropriate to the user and the available school technology.
5. Output is the system’s visible or functional result
Outputs include illumination, a sound indication, movement, recorded count or changed heating/cooling operation, depending on the application. A good specification names what successful output looks like.
A loud alarm is not a successful design if the user needed a quiet indicator. Output must be judged against purpose, accessibility and the relevant environment.
6. Feedback supplies information about actual performance
Feedback reports or represents what the system is doing or the state it has produced. In a closed-loop system, that information is used to adjust operation towards a desired condition.
A blinking light indicating that power is on is not automatically closed-loop feedback about performance. The important question is whether measured output influences the next action.
7. Open-loop control does not correct itself using output feedback
An open-loop system responds to its set input or command without continuously checking the achieved output and correcting it against a target. A straightforward table lamp controlled by a switch is a familiar example.
A lamp can become dimmer as conditions change without the basic switch-only system automatically increasing brightness to restore a desired measured level.
8. A table lamp shows input and output clearly
A user operates the switch, an electrical path is enabled and the lamp produces light. Under the simple syllabus example, it does not measure ambient brightness to maintain a constant light level.
Modern smart lamps may include sensors and closed-loop functions, so identify the precise model described rather than generalise from the word lamp.
9. A stapler shows that control is not always electronic
The user pushes the stapler handle, the internal mechanism translates the force and the staple is driven into suitable paper. This fits an open-loop mechanical example.
No temperature or light sensor is needed simply to define input–process–output. K345 integrates mechanical and electronic ways of controlling an outcome.
10. A can opener is another basic open-loop device
A manual can opener responds to applied handle motion through its mechanism to cut the lid. The user’s observation and skill are part of operation, but the simple device does not measure a programmed output target and self-correct.
The distinction concerns the control structure, not whether a human can watch and adapt their own actions.
11. A thermometer is a sensing and indicating example
A simple thermometer senses temperature through a physical response and presents a reading. In the K345 example, it does not itself adjust the temperature of the room to a target.
The display of a measurement does not create automatic closed-loop temperature control. A separate control mechanism would be required.
12. Closed-loop control compares actual and desired states
A closed-loop system receives feedback about output or a controlled variable and adjusts its action according to the comparison with a target or desired condition.
For a thermostat-based system, the measured temperature can influence whether cooling operates. The implementation varies; use only the syllabus-level feedback model unless specific data are supplied.
13. Air conditioning illustrates temperature regulation
A suitable air-conditioning control uses a temperature sensor, a desired setting and a decision to operate or change cooling. The surrounding temperature is measured again, feeding back into subsequent control.
An air conditioner may involve more complex behaviour and safety systems than a simple diagram. A school response should focus on temperature feedback, not detailed refrigeration design.
14. Water cisterns can regulate water level mechanically
A cistern mechanism may sense water level through a float arrangement, changing the inlet valve state as the level rises or falls. This is a closed-loop control example that does not depend on an electronic computer.
The float provides feedback linked to actual water level. The system must also be designed against leaks and overflow risks, which are not guaranteed by a sketch.
15. Hot-water dispensers use temperature feedback
A suitable hot-water dispenser can monitor water temperature and adjust a heating element’s operation toward a desired range. The feedback relates to the temperature actually reached.
Heating water and mains electricity can cause serious injury. The article offers conceptual explanation only and does not provide wiring or bypass instructions.
16. A sensor needs a clear measured variable
A light sensor responds to illumination, a moisture sensor to an appropriately defined moisture condition and a temperature sensor to a thermal variable. Each input must be connected to a relevant user requirement.
A design that measures temperature when the user needs to know light level has gathered the wrong data, even when the sensor is high quality.
17. Light sensing can support everyday accessibility
An approved kit could indicate when a school display is unusually dim under a stated threshold, helping a user decide whether more lighting is needed. The output can be visual or another suitable accessible signal.
A student must not assume the classroom’s measured illumination meets any official occupational standard from one fictional sensor value.
18. Light sensors cannot diagnose every visibility problem
Brightness at one point does not capture glare, contrast, reflections or a user’s visual needs. A sensible prototype test should focus on its defined aim.
A sensor reading needs calibration, position and environmental context. A design that reports ‘bright’ without criteria is not meaningfully evaluated.
19. Moisture sensors can monitor suitable conditions
A school-approved moisture-sensing kit might help a designer indicate whether a small plant-growing medium is relatively dry according to a chosen test condition. The output can alert a user to inspect the plant.
Moisture readings are not universal water-volume measurements without calibration, and they cannot certify safe drinking water or diagnose mould hazards.
20. Moisture conditions differ among materials
A sensor that responds clearly in one soil type may behave differently in another because of conductivity, composition or placement. This should be accounted for in testing.
A single number is not evidence that every pot, material or plant has the same needs. Keep the user’s actual environment in view.
21. Temperature sensors can inform control decisions
A kit may show that a fictional storage box has warmed outside a desired range and activate an indicator. Such examples connect sensing to a practical user need.
The output does not certify real food storage safety or medical refrigeration. Such uses demand professional standards and verified monitoring.
22. Counting systems recognise events
A counting kit may register a button press or another suitable safe event and update a display. Its function is to track events, which can support classroom mock-ups such as visitors entering an imagined exhibition.
The count is valid only if each event is detected once. Double triggers, missed events and reset behaviour affect accuracy.
23. A counter needs an event definition
Before building a counter, define what constitutes one count. Does a button being held register once or repeatedly? What happens when power is interrupted?
Without such a specification, the designer cannot know whether a demonstration succeeded.
24. Every sensor design needs a threshold or condition
A useful indicator should say what input condition causes an output and why. ‘When the fictional temperature reading exceeds the chosen practice threshold, turn on an indicator’ is clearer than ‘the sensor makes it work’.
The threshold must not be presented as an actual medical, industrial or food-safety limit unless a qualified source provides it.
25. Input–process–output diagrams can be simple
A descriptive sequence can read: ambient light → available light-sensing kit → compare with chosen threshold → visual indicator. For a closed-loop system, add measured result returning to influence operation.
Label functional stages rather than pretend to know internal semiconductor circuitry where no circuit specification was supplied.
26. A diagram must distinguish a sensor from an actuator
A sensor gathers information about a condition; an actuator or output component changes or indicates something. A temperature sensor does not itself cool a room without a system that drives cooling.
This distinction prevents the common phrase that ‘the sensor changes the temperature’ when it actually informs the controller.
27. Power is necessary but not proof of control
A powered circuit may illuminate an indicator without measuring any relevant condition. It is a functioning electrical output, but the desired control logic must be demonstrated separately.
An LED lighting up is not sufficient evidence of a correct moisture-control system if no appropriate moisture input was tested.
28. Open-loop control can be suitable and inexpensive
A simple user-operated table lamp may be sufficient where the user can choose when lighting is needed. Adding automated sensors could increase cost, power use or complexity unnecessarily.
Closed-loop control is not automatically better for every product. Select according to the intended function and risk.
29. Closed-loop control can maintain conditions
Feedback can help a system respond to changing environmental conditions and reduce manual intervention. This is valuable when the controlled condition should remain within a useful range.
Sensors can drift, fail or produce incorrect readings. Feedback improves control only when the loop is reliable and properly designed.
30. Feedback may cause unwanted cycling
If a control system responds too aggressively to tiny reading changes, an indicator or actuator might switch repeatedly. The user may need a practical design that avoids distracting, unnecessary oscillation.
Detailed controller equations are beyond the basic K345 outcome. The student can still describe a reasonable test for unwanted switching.
31. Hysteresis is a useful conceptual extension
In some practical controls, switching-on and switching-off conditions differ slightly to prevent rapid repeated toggling near a threshold. This is one way designers manage a noisy or varying sensor signal.
It is a wider design idea, not a named mandatory technical formula in the syllabus. Use it to explain a problem rather than memorise unrequested equations.
32. Sensor position affects what is measured
A temperature sensor next to a lamp may measure local heating rather than the general room condition. A light sensor hidden beneath the product may not represent the user’s workspace.
A test must document position and environmental conditions. A precise display does not compensate for measuring the wrong location.
33. Sensor repeatability and calibration matter
Repeated readings under comparable conditions help reveal consistency, while checking against a suitable reference helps assess accuracy. Different instruments can share a numerical display and still have different uncertainty.
A school prototype does not require professional certification, but it should not make unsupported accuracy claims.
34. An accessible user interface matters
A control may be technically functional but hard to operate if buttons are too small, displays are unclear or warnings are inaccessible. Human-centred design should consider visibility, reach and clarity.
A designer should ask the actual intended user what information they need, rather than assume every person prefers the same flashing light.
35. Visual signals should not be the only possible communication
Where a product must be usable by people with varied sensory abilities, designers may consider suitable sound, tactile or textual alternatives depending on the brief.
Do not require a loud alarm in a quiet library simply because sound is available. Suitability depends on the user and environment.
36. Design specifications guide the circuit decision
A brief that requires counting button presses needs repeatable event detection; a brief that requires indicating low light needs a relevant sensing threshold. A circuit should be evaluated against those separate purposes.
Without a measurable specification, the pupil cannot know whether the electronic feature improved the design.
37. Mock-ups can test layout without electricity
Cardboard models can show where a sensor, switch, screen or indicator would be placed. This helps assess reach and visibility before building an authorised low-voltage kit.
Testing physical arrangement is valuable even when no electrical hardware is connected. It can reveal problems early and safely.
38. Available kits limit the appropriate scope
K345 asks students to adapt existing electronic kits. The challenge is to understand their functions and integrate them purposefully into a design, rather than invent complex circuits from first principles.
The student should follow school instructions and documentation for the kit actually supplied. Unverified wiring diagrams from the internet may be unsuitable or dangerous.
39. Feedback can be represented without coding
Use a flowchart or block diagram: sensor input → comparison with desired condition → controlled output → updated measurement. This illustrates feedback conceptually.
No claim about particular chip pins or voltages is needed to explain the general process.
40. Count validation requires a baseline
A fictional visitor counter can be tested with ten deliberate presses and a displayed count. If only nine are registered, the prototype needs investigation; if eleven appear, repeated triggering may be occurring.
The score does not prove the cause. The test should isolate button behaviour, event definition and reset conditions.
41. Comparison against specifications is essential
A light indicator that responds correctly but is invisible in daylight fails the practical user goal. A moisture alert that triggers too often may annoy the user or encourage improper action.
Evaluate the whole interface and context, not only whether the sensor element responds.
42. Safe low-voltage practice is still supervised practice
Approved educational kits may use low-energy supplies, but batteries, terminals, tools and components still require appropriate handling. Unsafe short circuits and damaged cells can cause heat or injury.
This article intentionally does not give wiring directions, improvised soldering steps or instructions for altering mains appliances.
43. Heat and water need particularly clear boundaries
Combining a water-sensing kit with actual powered water heaters or mains systems can introduce serious hazards. Keep practice conceptual or use authorised classroom kit conditions.
Never extrapolate a working cardboard prototype to real water or electrical infrastructure without professional engineering review.
44. Prototype iteration should be documented honestly
A pupil should record which input condition was tested, what output occurred, what failed and what change was made. Genuine dated results support the Design Journal’s purpose.
Adults may teach methods, but must not fabricate a candidate’s assessed results, data, diagrams or personal project work.
45. A monitoring product is not always a regulating product
A thermometer reports temperature, while a thermostat-based controller changes heating or cooling depending on readings. This distinction separates sensing and feedback control.
Do not assume a display implies automatic regulation. Follow the information flow and look for a controlled output.
46. The simplest system may best meet a modest need
If a pupil needs a portable desk light, a reliable switch may be more understandable and robust than an elaborate ambient-light algorithm. If the brief genuinely requires maintaining a target condition, feedback may be justified.
Design quality concerns fitness for purpose and evidence rather than component count.
47. Feedback needs an actual path back
A sound system diagram should show the measured controlled condition influencing a later decision. If an output indicator merely displays the current input but nothing adjusts, the feedback mechanism is absent or limited.
Make the return path visible with a labelled arrow or sentence. This prevents empty use of the word feedback.
48. Controls and sensors connect to other subjects
Physics helps explain sensors and electric circuits, while Mathematics helps compare thresholds and measurements. Design & Technology integrates those concepts with user needs and material choices.
K345 does not become an advanced electronics syllabus solely because another subject contains circuit equations. Respect the depth and purpose of the assessed design task.
49. Efficiency must not override reliability
A sensor might save user effort, but faulty alerts or inaccessible controls can introduce new difficulties. A prudent designer weighs maintenance, error consequences and usability.
A large number of functions cannot compensate for an unreliable essential function.
50. Sustainability should be included at design time
Energy consumption, material use, battery replacement, repairability and unnecessary electronics affect environmental cost. A passive mechanical solution may sometimes meet the need more simply.
Do not assert that electronics are always greener because they are newer. Compare actual functions and lifecycle costs.
51. A product can combine mechanical and electronic control
A device may use a simple mechanical float and an electronic indicator, or mechanical actuation controlled by a sensor. The designer must explain what each component contributes.
Combining systems increases integration complexity and should be done only when the user requirement justifies it.
52. The most valuable evidence is a failed condition explained
A prototype light indicator that works in a dark room but not under daylight has revealed a meaningful design weakness. The next step is to identify whether the issue is sensor threshold, output visibility or placement.
It is better to explain the failed test and refine a real prototype than invent a perfect result in an assessed record.
53. Twelve-stage control-design audit
- 1 — Describe the actual user and the practical need.
- 2 — Identify the condition to monitor or change.
- 3 — Decide whether the task needs open-loop command or closed-loop regulation.
- 4 — Specify input and the appropriate sensing or human action.
- 5 — Explain the process or comparison logic.
- 6 — State the physical or informational output.
- 7 — For feedback systems, identify the measured controlled condition and return path.
- 8 — Choose only available, school-approved components or kits.
- 9 — Test mock-up placement, reach and interface clarity safely.
- 10 — Compare expected and observed outputs under more than one condition.
- 11 — Record genuine evidence, limitations, maintenance and sustainability issues.
- 12 — Revise the design against the brief and specifications without inventing results.
54. Meridian Sensor Studio: sixteen fictional design cards
Every design case is an original paper-only simulation, not a live electrical test or candidate Design Project submission. Any practical adaptation must follow the school’s kit instructions and supervision.
A — Basic switch lamp
Original fictional design case: A fictional lamp turns on only when the user presses a switch.
Input or sensing step: Human switch action.
Decision or process: Enable power to a lighting output.
Output and feedback: Light switches on; no automatic brightness comparison.
Design diagnostic: Does the function require feedback?
Evidence and safety boundary: No electrical build is described.
B — Temperature-reading instrument
Original fictional design case: A display shows room temperature but controls no device.
Input or sensing step: Ambient temperature sensing.
Decision or process: Convert measurement to displayed value.
Output and feedback: A reading, not active temperature regulation.
Design diagnostic: Is this closed loop?
Evidence and safety boundary: Sensor precision is unspecified.
C — Air-conditioning example
Original fictional design case: A conceptual air conditioner aims for a chosen temperature.
Input or sensing step: Measure room temperature.
Decision or process: Compare with user-set condition.
Output and feedback: Cooling changes the temperature and measurement repeats.
Design diagnostic: Identify the feedback arrow.
Evidence and safety boundary: Not a guide to alter real appliances.
D — Water cistern
Original fictional design case: An imagined float rises as water enters.
Input or sensing step: Water-level input through float.
Decision or process: Mechanism changes the inlet valve state.
Output and feedback: Flow adjusts as level changes, giving feedback.
Design diagnostic: How is this closed loop without electronics?
Evidence and safety boundary: Real plumbing requires professional work.
E — Hot-water dispenser
Original fictional design case: A school diagram shows controlled heating around a chosen temperature.
Input or sensing step: Temperature measurement.
Decision or process: Compare against the desired heating condition.
Output and feedback: Heating operates accordingly, with repeated reading.
Design diagnostic: What failure occurs if the sensor lies?
Evidence and safety boundary: Do not modify mains/water heaters.
F — Display counter
Original fictional design case: Ten presses are deliberately recorded in a hypothetical kit.
Input or sensing step: Button event input.
Decision or process: Register one event per valid press.
Output and feedback: Expected count ten.
Design diagnostic: What if display shows eleven?
Evidence and safety boundary: The exact kit is unspecified.
G — False repeated count
Original fictional design case: A held-down button creates several increments.
Input or sensing step: Duration differs from a single discrete press.
Decision or process: Define a valid event and test repeat handling.
Output and feedback: Incorrect count indicates a design issue.
Design diagnostic: Where should the event rule be placed?
Evidence and safety boundary: No component-level circuit is given.
H — Low light condition
Original fictional design case: An imagined reading falls below a fictional practice threshold.
Input or sensing step: Light sensor.
Decision or process: Compare with selected threshold.
Output and feedback: Indicator appears.
Design diagnostic: Does the indicator improve accessibility?
Evidence and safety boundary: Not an actual classroom lighting standard.
I — Sensor facing wrong way
Original fictional design case: A light sensor is enclosed under the product.
Input or sensing step: It measures local darkness, not the work surface.
Decision or process: Reposition conceptually to represent user condition.
Output and feedback: The alert may be misleading.
Design diagnostic: Which orientation should the model test?
Evidence and safety boundary: No empirical readings are available.
J — Moisture monitoring
Original fictional design case: A hypothetical potted-plant alert responds to dry medium.
Input or sensing step: Moisture-sensing kit.
Decision or process: Compare with a defined practice state.
Output and feedback: Simple indicator suggests user inspection.
Design diagnostic: Should it automatically water the plant?
Evidence and safety boundary: Not a soil agronomy or water-safety certificate.
K — Temperature near a heater
Original fictional design case: A sensor next to an imaginary heat source reads above ambient.
Input or sensing step: Local thermal input is biased.
Decision or process: Evaluate position and measurement purpose.
Output and feedback: Wrong placement causes misleading output.
Design diagnostic: How would a fair comparison be organised?
Evidence and safety boundary: Real safety limits cannot be inferred.
L — An inaccessible alarm
Original fictional design case: A visual indicator is too small for its intended user.
Input or sensing step: Output visibility is a user constraint.
Decision or process: Compare interface design options.
Output and feedback: System functions electronically but fails usability.
Design diagnostic: What accessible alternative is appropriate?
Evidence and safety boundary: User testing is hypothetical.
M — Overcomplicated stationery holder
Original fictional design case: A student adds sensors to a product only needing stable storage.
Input or sensing step: No environmental measurement is required.
Decision or process: Remove unnecessary electronics.
Output and feedback: A passive structure may meet the need better.
Design diagnostic: How is this good design rather than reduced ambition?
Evidence and safety boundary: The evaluated product is fictional.
N — Closed-loop assumption
Original fictional design case: A device flashes whenever temperature rises but does not change the environment.
Input or sensing step: Temperature monitoring.
Decision or process: Process threshold into warning.
Output and feedback: Alert is produced; temperature is not automatically regulated.
Design diagnostic: Is this truly a temperature-control loop?
Evidence and safety boundary: No feedback into heating/cooling is specified.
O — Repeated switching
Original fictional design case: A conceptual indicator flickers repeatedly around a threshold.
Input or sensing step: Noisy or varying sensor signal.
Decision or process: Review decision robustness.
Output and feedback: Repeated toggling undermines usability.
Design diagnostic: What conceptual change might reduce this?
Evidence and safety boundary: No specific electronics solution is mandated.
P — Journal integrity
Original fictional design case: A fictional candidate produces immaculate final sketches but invents prior tests.
Input or sensing step: The claimed input/output observations were not measured.
Decision or process: Keep genuine dated evidence of work.
Output and feedback: Fabrication undermines the assessment.
Design diagnostic: What would authentic iteration show?
Evidence and safety boundary: The case is not a real student.
55. Worked block diagram: low-light indicator
Input: light level as measured by an appropriate kit. Process: compare with an explicitly defined practice threshold. Output: indicator status. If the device only reports low light, it is not automatically a closed-loop room-brightness regulator.
The diagram helps separate monitoring from control. An actual light-regulating system would require an appropriate output that changes illumination and a feedback route measuring the result.
56. Worked block diagram: cistern level control
Input: actual water level as represented by float position. Process: mechanical comparison with desired level. Output: inlet valve opening or closing. Feedback: changes in water level move the float and influence the next valve state.
This illustrates K345’s closed-loop concept without a sensor chip or code. A practical plumbing installation remains outside school-paper guidance.
57. A fair prototype evaluation
A suitable test table can record input condition, expected output, observed output, discrepancy and proposed change. For a fictional counter, deliberately create five separate events and compare the indicated count with five.
Tests should cover failure conditions as well as expected conditions. Only real school-authorised observations may appear as actual assessed journal data.
58. A strong written examination answer
Describe the user need, correctly classify open or closed loop, name input/process/output and show whether the result is fed back to adjust operation. Evaluate one benefit and one limitation relevant to the product.
Avoid generic claims such as ‘all smart devices save electricity’ or ‘sensors make it safe’. The data and mechanism must support the answer.
59. How parents and tutors can practise ethically
Use drawings of simple appliances and ask the pupil to label functional blocks. Then describe a missing input or failed indicator and ask what evidence would discriminate its cause.
This teaches the syllabus without building unsafe circuits or producing a candidate’s coursework for them.
60. Fencing Method for D&T electronics
Fence one: user need. Fence two: input versus output. Fence three: sensing versus actuation. Fence four: open versus closed loop. Fence five: measuring feedback. Fence six: prototype evidence and safe refinement.
Only after those distinctions are secure should a pupil compare multiple sensors or discuss energy and repairability.
61. Depth–Load–Transfer diagnostic
Depth: can the learner explain why an air conditioner uses feedback while a simple lamp does not? Load: can they keep sensing, processing, interface, output and user context separate in a longer case? Transfer: can they classify an unfamiliar product with only a functional description and avoid guessing its internal components?
A pupil who equates every thermometer with closed-loop control needs a return-path diagram. One who treats all electronics as complex programming needs available-kit scope correction.
62. Common misunderstandings and repairs
- Every powered product is closed loop — check whether actual output affects later action.
- A table lamp with one switch always measures brightness — simple models do not.
- A thermometer automatically controls room temperature — it can simply report.
- A sensor is the same as an actuator — one measures, the other changes output.
- Feedback is any indicator light — look for a returned measurement influencing control.
- Open-loop products are always inferior — simplicity may fit the user.
- Closed-loop systems never fail — sensor and actuator problems remain.
- Counting means recording every millisecond a button is held — define an event.
- A moisture sensor certifies food or water safety — it does not.
- An LED lighting means the full user need is met — evaluate purpose and visibility.
- All student prototypes must use a programmable chip — K345 focuses on adapting available kits.
- A perfect-looking design journal can contain invented data — genuine records are required.
- Mains-powered appliance changes are safe school experiments — do not attempt them.
- More electronic parts always make a product sustainable — consider energy and repairability.
63. Independent twelve-question checkpoint
- 1 — Name the input, process and output of a simple table lamp.
- 2 — Explain the defining difference between open and closed loop.
- 3 — Give two K345 open-loop examples.
- 4 — Give three K345 closed-loop examples.
- 5 — Explain feedback in a water cistern.
- 6 — Explain temperature feedback in an air conditioner.
- 7 — Name the kit-sensing categories specified in outcome 30.
- 8 — Explain why counting needs an event definition.
- 9 — Describe a plausible test of an invented light indicator.
- 10 — Give one sensor-placement error.
- 11 — Explain why the user interface matters.
- 12 — State one safety and one coursework-integrity rule.
Answer guide: (1) switch, enabling circuit, illumination. (2) output-related feedback informs subsequent action. (3) lamp, thermometer, stapler or can opener. (4) hot-water dispenser, water cistern, air conditioner. (5) float level influences valve. (6) measured temperature influences cooling. (7) light, moisture, temperature plus counting. (8) prevent duplicates and missing counts. (9) compare expected indication under two known fictional conditions. (10) sensor beside heat or in shadow. (11) accessibility and clarity. (12) supervised suitable kit work and authentic candidate journal.
64. Frequently asked questions
Do D&T students need to design custom transistor circuits?
The 2027 syllabus requires practical understanding and adaptation of available electronics kits, not a separate advanced transistor-design qualification.
Does a temperature display make an appliance closed loop?
Not by itself. The measured temperature must influence control of the output toward a desired condition.
Can a water cistern be closed loop without a microcontroller?
Yes. A mechanical float can provide feedback based on the level of water.
Should a beginner modify a household air conditioner?
No. Use block diagrams and school-approved kits instead of opening mains-powered equipment.
Can an adult write the assessed design journal for a pupil?
No. General coaching is appropriate, but the Design Project is assessed as authentic individual coursework.
65. Official K345 and linked reading
The primary examination document is SEAB 2027 SEC G3 Design & Technology K345, Section 2, learning outcomes 28–30. It names open and closed loop, inputs, process, output, feedback and available counting and sensing kits. Refer to the 2027 school-candidate syllabus directory for any changes.
Previous: Reference 347 — POA Correction of Errors. Next: Reference 349 — Business Ownership. Design foundations: Reference 335 — Design Prototyping and Reference 158 — Testing. Related science: Reference 340 — Measurement and Reference 286 — Physics Potential Dividers and Sensors. Browse the MOE V3.0 hub and immutable Clementi teaching standard.
Editorial review: 26 October 2026, Singapore. All Meridian sensor examples are fictional paper tests, not electrical operating instructions. The transferable habit is to identify the controlled variable, draw the information path and ask whether feedback actually changes operation.