What is an integrated technology project?
One technology alone often cannot solve a real problem. A thermometer only shows a number. A fan only spins. An integrated project joins them so that they work together to meet a need, such as keeping a greenhouse cool.
Integrated means "put together so the parts help each other". The tools can come from different areas: electronics, computing, mechanics, and even biology (the plants).
The four building blocks
- Sensor: measures the world (temperature, light, moisture, distance). It does not decide.
- Controller: a small computer (microcontroller) that follows a rule, such as "if temperature is above 30 °C, fan ON".
- Actuator: the part that acts (fan, pump, valve, motor, light).
- Connection and interface: Wi-Fi or Bluetooth plus an app or screen so people can see readings and change settings.
Power (battery, mains or solar) feeds all parts. Wires or wireless links carry the signals.
Feedback: why the loop matters
After the fan runs, the room cools. The sensor reads the new, lower temperature and the controller turns the fan off. This round trip is a closed loop or feedback control. Without it (an open loop) the fan would run for a fixed time even if the room was already cool.
To avoid the fan switching on and off too fast, controllers often use two limits: switch on at 30.3 °C and off at 29.3 °C. This gap is called hysteresis.
The design process for a project
- Define the need: who needs what, and what counts as success (for example, keep temperature under 30 °C).
- Plan and design: choose sensor, controller, actuator; draw a block diagram; plan power and cost.
- Build a small model first.
- Test: try extreme cases (very hot day, sensor unplugged) and measure results.
- Improve: fix problems, add safety (a manual switch), and write a short guide.
Also think about safety, cost, repair, and the environment (energy use, waste).
Try it: in the 3D, set the outside temperature to 45 and the limit to 26. Does the fan keep up? What would you add?
Key formulas and definitions
- System = Sensor → Controller → Actuator (+ Connection)
- Rule: IF reading > limit THEN actuator ON, ELSE OFF
- Feedback: output is measured again and used to decide the next action
- Design process: Define → Plan → Build → Test → Improve
Worked examples
1. Name the sensor, controller and actuator in an automatic street light.
Sensor = light sensor (LDR). Controller = small circuit that compares light with a limit. Actuator = the lamp switch.
2. A greenhouse rule is "fan ON above 30 °C". The room reads 32 °C, 30 °C and 28 °C. Which readings turn the fan on?
Only 32 °C is above 30, so the fan is ON. At 30 and 28 the fan stays OFF.
3. Why is a loop with feedback better than running the fan for exactly 10 minutes every hour?
The feedback loop reacts to the real temperature. The timed fan wastes energy on cool days and may not run long enough on very hot days.
4. A student plans a smart plant waterer. List the design process steps with one action for each.
Define: keep soil above 40% moisture. Plan: moisture sensor, microcontroller, small pump. Build: a model with one pot. Test: dry and wet soil. Improve: add a water-level alarm.
Common mistakes
- Thinking the sensor makes the decision. The sensor only measures; the controller applies the rule.
- Forgetting the feedback. Without re-checking, the system cannot know when to stop.
- Skipping the test step. Real use finds problems that a diagram cannot show (heat, dust, unplugged wires).
- Planning only the technology and ignoring cost, power, safety and who will maintain it.