Why Malaysia Must Stop Treating IoT as a Final Year Project Toy

Every year, I meet students who proudly show me their IoT projects, and I can almost predict what will appear on the table before the demonstration even begins. There will be a sensor, a microcontroller, a few wires, a mobile app, and a dashboard showing temperature, humidity, distance, motion, water level, or some other familiar reading. The student will explain how the system works, the lecturer will nod, the evaluator will ask a few questions, and everyone will feel relieved when the demo runs without embarrassment. For a few minutes, the project looks alive, impressive, and full of promise.

Then, after the presentation, something strange happens. The device is switched off. The components are kept in a box. The dashboard is no longer opened. The video may be uploaded somewhere, but after that, the whole thing quietly disappears into the graveyard of final year projects. Nobody continues collecting data. Nobody studies the pattern. Nobody asks whether the system can be deployed in a real site. Nobody asks whether the idea can be improved, commercialised, or connected to an actual industry problem. It simply ends where it started, on the classroom table.

Each time I see this, I ask myself, “Is this what IoT has become in Malaysia? A temporary demo to pass an assessment?”I am not saying this to mock students. Far from it. I respect students who spend sleepless nights trying to make their projects work. I know the pain of troubleshooting something that refuses to behave when people are watching. Anyone who has handled hardware knows that sensors have a strange sense of drama. They work perfectly at midnight, then suddenly become shy during the presentation.

But my concern is bigger than the student project itself. My concern is that Malaysia has treated IoT for too long as something small, experimental, academic, and temporary, when in reality, IoT should already be part of how we manage our cities, farms, buildings, factories, transport systems, utilities, campuses, and public services. IoT is not a toy. It is infrastructure intelligence. Malaysia must start treating it that way.

The Problem Is Not the Students

Let me say this clearly. The problem is not the students. Many of them are creative, hardworking, and eager to learn. They work with limited budgets, limited time, borrowed components, weak WiFi, and sometimes unclear project guidance. They do what they can with what they have, and for that, they deserve encouragement. The issue is not their effort. The issue is the way we have framed IoT in education, industry, and sometimes even government projects.

For many years, IoT has been taught and demonstrated as a sensor to dashboard exercise. Connect the device. Send the data. Show the graph. Done. That is useful as a starting point, but it is a dangerous place to stop. When IoT is presented only as a dashboard project, students naturally assume that the job is complete once data appears on the screen. They do not always ask what happens after the data appears, who will use it, what decision it supports, what action must follow, what happens when the device fails, or whether the system can survive outside the classroom.

Maybe we taught them to build the wrong finish line, I thought to myself. The finish line should not be “the data appears.” The finish line should be “someone makes a better decision because the data appeared.” That is the difference between a demo and a real solution.

A Sensor Is Not a Solution

One of the biggest misunderstandings about IoT is the belief that once a sensor is connected, the problem is solved. This is like saying a thermometer cures fever. A thermometer does not cure anything. It only tells you something is wrong. What matters next is the interpretation, the decision, the treatment, the follow up, and the responsibility of the person who acts on that reading.

IoT works the same way. A temperature sensor in a cold room does not protect vaccines or food by itself. It only provides signals. The real value begins when the system detects abnormal readings, alerts the right person, records the evidence, helps the operator respond quickly, and supports compliance reporting. A water level sensor near a river does not prevent flooding by itself. It becomes useful only when the data is trusted, the alert reaches the correct agency, the response process is clear, and residents receive warnings early enough to act. A vibration sensor on a machine does not prevent downtime by simply producing numbers. It becomes useful when those numbers are analysed, compared against patterns, and linked to maintenance decisions before the machine fails.

That is why I always say the dashboard is not the destination. The dashboard is only the window. The real question is what we do after looking through that window. If we see a problem and nobody acts, then the system has failed quietly. It may still look beautiful on a screen, but it has not changed anything in the real world.

Malaysia Has Too Many Real Problems for IoT to Remain in the Lab

Malaysia does not lack problems that need better visibility. We have floods that still catch people by surprise, buildings wasting energy after office hours, farms that need better monitoring of soil, water, and climate, logistics operators that must prove temperature compliance, factories that want to reduce downtime, public facilities that need better maintenance, and local councils trying to manage waste, traffic, drainage, parking, lighting, and public complaints with limited manpower.

These are not imaginary classroom problems created for a semester project. These are real operational issues that cost money, time, trust, and sometimes safety. Yet many organisations still operate using manual checks, WhatsApp updates, delayed reports, and reactive decisions. Someone must visit the site. Someone must take a photo. Someone must key in data. Someone must send a message. Someone must wait for approval. By the time the information reaches the decision maker, the problem may already have grown bigger.

This is where IoT should become serious. IoT should help Malaysia see earlier, respond faster, and plan better. It should reduce blind spots in operations. It should help people move from guessing to knowing, and from reacting late to acting early. But that will not happen if IoT continues to be treated as a decorative technology for exhibitions, competitions, and one off prototypes.

A smart city is not built from disconnected demos. A smart factory is not built from one sensor reading on a laptop. A smart farm is not built from a project that stops after the student graduates. Real IoT needs continuity, ownership, maintenance, platforms, training, security, and people who care about the outcome, not just the device.

The Final Year Project Mindset Is Too Small

Final year projects are important. They help students learn, test ideas, make mistakes, and gain confidence. I fully support that. But when the final year project mindset becomes the national mindset, we have a problem. The final year project mindset usually asks whether the system can work for the demo, whether the data can appear on a screen, whether the poster looks good, whether the report can be submitted, and whether the panel can be impressed.

A national IoT mindset asks much harder questions. It asks whether the system can solve a real problem, work outside the lab, scale to multiple sites, be maintained for years, protect the data, support daily decisions, reduce cost, reduce risk, improve service delivery, and continue after the project team leaves. These are the questions Malaysia must start asking more seriously.

We cannot keep celebrating prototypes while ignoring adoption. We cannot keep launching pilots that never move into operations. We cannot keep confusing activity with progress. There is a big difference between building something and making it useful. Malaysia has built many IoT things. Now we must make them useful.

Stop Asking Only “Can It Connect?”

One of the most common questions in IoT is, “Can it connect?” Of course, connectivity matters. Without connectivity, the device becomes an island. But connectivity alone is not enough. A connected device that sends meaningless, unreliable, unsecured, or unused data is not a success. It is only a noisy device.

The better questions are more practical. Can it connect reliably? Can it recover when the network fails? Can it send clean and meaningful data? Can it protect that data? Can it trigger the right response? Can it help the user decide faster? Can it reduce manual work? Can it be supported for years, not weeks?

This is where many IoT projects become weak. They focus too much on the first connection and not enough on long term usefulness. I have seen systems where the data appears nicely on the dashboard, but nobody knows what threshold should trigger an alert. I have seen dashboards that look impressive, but no department has agreed who is responsible when something abnormal happens. I have seen projects where the devices were installed, but after a few months, nobody checked whether the data was still accurate.

That is not IoT maturity. That is technology theatre. It looks good from far, but when you stand closer, you realise the system has no operational backbone.

IoT Must Belong to the People Who Own the Problem

Another mistake I often see is when IoT is handed entirely to the technical team. The technical team can connect devices, configure networks, set up platforms, and build dashboards. That part is important. But they cannot define business value alone. Technology people can build the pipe, but the people who face the pain must define what should flow through it and what should happen after that.

If the project is about energy, the energy manager must be involved. If the project is about farming, the farm operator must be involved. If the project is about city services, the relevant local council department must be involved. If the project is about machine maintenance, the maintenance team must be involved. If the project is about cold chain, the operations and compliance teams must be involved.

IoT fails when it becomes a technology project without an operational owner. The people who feel the pain must be part of the design from day one. They know the messy details. They know where problems happen. They know which alerts matter and which alerts will be ignored. They know what kind of information is useful at 8 a.m. on a busy Monday, and what kind of dashboard nobody will ever open after the vendor leaves.

Who owns the pain? That is the question I often ask myself. Because the person who owns the pain should also own the outcome.

Cybersecurity Must Be Built In From the Beginning

When we connect more devices, we also create more openings. This is the side of IoT that many people do not like to talk about during cheerful demos. A connected device can provide visibility, but a poorly secured device can also become a weak door into a larger system. That is why IoT cannot be treated casually, especially when it starts moving into buildings, factories, campuses, farms, utilities, transport systems, and critical services.

Every IoT project should ask security questions from the beginning. Who can access the device? How is the device authenticated? Can the firmware be updated safely? Can the data be altered? Can someone fake a reading? Can unusual device behaviour be detected? What happens when the device is stolen, damaged, or hijacked? How do we separate normal failure from suspicious activity?

AI can help detect abnormal patterns and support faster response, but AI is not a magic shield. A weak IoT architecture with AI added later is still weak. It is like putting a fancy lock on a wooden door that is already cracked. Security must be designed into the system, not sprinkled on top after the project becomes popular.

This is why I often remind people that IoT is no longer just an engineering conversation. It is also a cybersecurity conversation, a governance conversation, and a trust conversation. Once a device is connected to a larger environment, it becomes part of a bigger responsibility.

The AI Conversation Makes IoT More Important

Today, everyone wants to talk about AI. AI is in every conference, proposal, workshop, policy conversation, and almost every company profile. Sometimes it feels as if even the office pantry will soon claim to have an AI powered coffee strategy. I understand the excitement because AI is powerful, but we must remember something very basic.

AI needs data. Not just old data sitting in spreadsheets, but live, real world, operational data. Data from machines, buildings, vehicles, rivers, farms, cold rooms, energy meters, production lines, and public facilities. Where does that data come from? It comes from IoT.

IoT is the bridge between the physical world and digital intelligence. Without IoT, many AI systems are left guessing from outdated, incomplete, or manually entered information. This is why I find it strange when people say IoT is old news and AI is the future. To me, that is like saying the brain is important, but the nerves are no longer needed.

AI may be the brain, but IoT is part of the nervous system that senses what is happening in the real world. If the nerves are weak, the brain receives poor signals. When the signals are poor, the decisions will also be poor. Malaysia cannot build serious AI for real world operations while treating IoT as an afterthought. The two must grow together.

We Need Local Capability, Not Permanent Dependency

There is another issue that we must discuss honestly. Many students and developers in Malaysia still use overseas IoT platforms by default. They use them because tutorials are easy to find, examples are everywhere, and seniors have used them before. I understand this completely. When a student is rushing to complete a project, the easiest path becomes the most attractive path.

But at a national level, we must ask a bigger question. Do we want to remain only users of other people’s platforms, or do we want to build our own capability as well? This is not about rejecting global platforms. There is nothing wrong with learning from global tools. They have their strengths, and they serve many use cases well. But if every university, student, agency, and company only learns using external platforms, then our local ecosystem will remain thin.

We will produce users, not builders. We will produce dependency, not confidence. We will produce projects, not capability. Malaysia needs local platforms, local examples, local documentation, local support, local case studies, and local success stories. We need students who can say they built something using a Malaysian IoT platform like Favoriot, and that project can be extended into a real solution. We need lecturers who can expose students to platforms that understand local industry needs. We need system integrators who can build faster because they are not starting from zero every time. We need government and industry buyers who care about long term ownership, data governance, and local support.

This is how an ecosystem grows. Not through slogans, but through usage, trust, and repeated real deployments.

Pilots Must Stop Dying After the Launch Photo

Malaysia loves pilot projects. We launch pilots with banners, speeches, handshakes, group photos, and sometimes a nice gimmick where someone presses a button on stage. I have nothing against pilots. A pilot is useful when it helps us learn, reduce risk, and prepare for wider adoption. But a pilot becomes wasteful when it ends at the launch photo.

Too many IoT pilots do not answer the most important questions. What did we learn? Did the system solve the original problem? Who used the data? What decision changed? What cost was reduced? What risk was avoided? What process improved? What failed? What should be changed before scaling? Can this model be repeated in another location?

If we cannot answer these questions, then the pilot was not a learning exercise. It was a performance. A good pilot must have a path to adoption. It must be designed with scale in mind, even if the first version is small. It must include training, maintenance, user feedback, support, and measurable outcomes.

Small pilots are fine. Small thinking is not.

Universities Must Raise the Standard

Universities have a major role to play because they are not just producing graduates. They are shaping how the next generation understands technology. If IoT is taught only as a technical connection exercise, students will graduate thinking that connectivity is the main achievement. But if IoT is taught as a complete system, students will begin to think like solution builders.

They will understand sensors, communication, platforms, data quality, cybersecurity, analytics, user needs, operations, and business value. They will learn that the real world is not as friendly as the lab. In the lab, the WiFi usually works. In the field, the signal disappears when you need it most. In the lab, the power supply is stable. In the field, someone may unplug the adapter because they need the socket. In the lab, the sensor is clean. In the field, it faces heat, rain, dust, insects, vibration, curious hands, and sometimes people who have no idea why the device is there.

This is why students need exposure to real problems. Let them work with local councils, farms, factories, hospitals, logistics companies, buildings, and campuses. Let them talk to actual users. Let them understand frustration, constraints, budgets, maintenance, and accountability. A student who has seen real operational pain will build differently. That student will not simply ask whether a value can appear on a dashboard. That student will ask whether the data can help someone act before the problem becomes worse.

That is the kind of graduate Malaysia needs.

Government and Industry Must Demand Outcomes

The responsibility is not only on universities. Government agencies, local councils, GLCs, enterprises, and private companies must also change how they buy and evaluate IoT. Do not buy IoT because it sounds modern. Do not install sensors because other cities have sensors. Do not ask for dashboards because dashboards look impressive in meeting rooms. Ask for outcomes.

Before starting an IoT project, the buyer should ask what decision the system supports, who will respond to alerts, how success will be measured, how the system will be maintained, how the data will be protected, and how the project will continue after year one. They should also ask what happens when the vendor is no longer standing beside the dashboard during a demo. That is where the truth normally appears.

This is where procurement must become smarter. If the tender only asks for devices and dashboards, the result will be devices and dashboards. If the tender asks for operational outcomes, response workflows, security design, data ownership, maintenance, training, and measurable impact, then vendors will have to design more serious solutions.

Malaysia must stop buying gadgets and start buying operational intelligence.

IoT Is a Long Term Commitment

Many people underestimate what happens after installation. The project is not finished when the devices are installed. In many ways, that is when the real work begins. Devices need monitoring. Sensors need calibration. Users need training. Alerts need tuning. Dashboards need improvement. Data needs review. Network issues need troubleshooting. Reports need refinement. Processes need updating. Budgets need planning.

IoT is not a one day event. It is a living system. This is why the final year project mindset is dangerous when applied to real deployments. In a student project, the goal is often to complete and submit. In a real deployment, the goal is to operate, improve, and sustain.

The system must still work after the excitement fades. It must still provide value when nobody is clapping. It must still help the user on an ordinary Tuesday morning when something goes wrong and people need answers fast. That is the true test of IoT. Not the demo. The ordinary day.

From Prototype Pride to Operational Discipline

We should still be proud of prototypes, but we should not stop there. A prototype is a question. A real deployment is an answer. A prototype asks whether an idea can work. A real deployment answers by showing how it improves operations.

Malaysia has enough prototypes. What we need now is discipline. We need discipline in defining problems, designing systems, securing devices, managing data, training users, measuring outcomes, scaling what works, and stopping what does not. This is not glamorous work. It may not look as nice as a launch ceremony, but this is where real progress happens.

Behind every useful IoT system, there are people doing boring but necessary things. They check data quality, fix device issues, improve alerts, train staff, review reports, update workflows, and make sure the system continues to serve the people who depend on it. That is how IoT becomes part of daily operations. Not through magic. Through discipline.

The Malaysia I Want to See

I want to see Malaysian students building IoT projects that do not disappear after final presentations. I want to see lecturers guiding students toward real world problems, not repeated versions of the same safe ideas. I want to see universities using local platforms and building stronger links with industry. I want to see local councils using IoT to manage floods, waste, parking, lighting, and public facilities more intelligently.

I want to see factories using IoT to reduce downtime and improve maintenance. I want to see farms using IoT to improve productivity and reduce waste. I want to see buildings using IoT to cut energy costs and support sustainability goals. I want to see local system integrators building reusable solutions instead of starting from scratch for every customer. I want to see Malaysia take IoT seriously as a foundation for AI, smart cities, and national competitiveness.

Most of all, I want us to stop underestimating our own ability. We have the talent. We have the problems. We have the technology. We have local platforms. We have universities. We have industries that need better data. What we need now is the courage to connect all of these pieces into something bigger.

IoT Was Never Meant to Stay on the Classroom Table

The blinking LED was never the final achievement. It was only the first sign that something could be connected. The real achievement comes when that connection creates awareness, that awareness leads to action, and that action improves lives, services, businesses, and national capability.

Malaysia must stop treating IoT as a final year project toy because the world has already moved on. IoT is now part of infrastructure, cybersecurity, AI, sustainability, smart cities, industrial growth, and operational decision making. If we continue treating it as a small student experiment, we will produce many demos but too few outcomes. That would be a waste, not just of components or project budgets, but of potential.

Maybe the problem is not that Malaysia lacks IoT projects, I thought to myself. Maybe the problem is that too many of them are never allowed to grow up.

So let us allow them to grow. Let us move IoT from the classroom table to the operations room, from assignment marks to measurable outcomes, from dashboards to decisions, from prototypes to platforms, and from toys to infrastructure. Malaysia does not need more blinking LEDs to prove that we can connect things. Malaysia needs connected systems that help us think, act, and build better.

What do you think? Are we ready to treat IoT as serious national capability, or are we still too comfortable celebrating prototypes that never leave the lab? I would love to hear your thoughts in the comments.