Embedded systems and IoT technology are foundational to connected products and industrial automation. They bring together computing hardware, software, communications, sensors, and integration services to make equipment capable of sensing, processing, and exchanging information. For automation engineers and technical decision-makers, understanding this ecosystem helps clarify how factory systems relate to wider developments in vehicles, machinery, robotics, and connected devices.
Embedded systems and IoT technology span multiple industries
The market overview in the ET/IoT Technology material illustrates how embedded technologies reach well beyond conventional factory equipment. Its 2016 figures include automotive, smartphones, medical instruments, multifunction printers, precision machine tools, aircraft equipment, robots, car navigation systems, programmable logic controllers (PLCs), and digital cameras. Each category depends on some combination of processors, software, interfaces, and control or communication functions.
The figures also show different patterns of Japanese participation across sectors. The overview reports Japan’s share at 28% for automotive, 20% for precision machine tools, and 50% for robots. It lists 10% for PLCs and 45% for multifunction printers. These are historical figures, not current market estimates, but they illustrate the range of industries in which embedded technology and related suppliers have a role.
For industrial automation, the important point is the overlap between these sectors. A machine tool, robot, vehicle, or PLC may rely on embedded processors and software, while connected applications add communications and data handling. The same broad technology building blocks therefore serve different products and operating environments.
Automotive supply chains show the scale of the ecosystem
The source describes automotive as a large global market and highlights the layered supplier structure around vehicle manufacturers. Tier 1 and Tier 2 suppliers provide components and systems, creating a broad supply chain that includes companies working in areas such as electronics, motors, and control technology. The listed suppliers include DENSO, Aisin, JTEKT, NTN, Renesas Electronics, and others.
That supply-chain model is relevant to automation professionals because complex products are rarely built by a single organization. Hardware, software, and subsystems must come together across company boundaries. Industrial IoT projects can involve a similar mix of device makers, component suppliers, software providers, and system integrators. Coordination between these participants is central to delivering a working system.
Connected products depend on hardware, software, and interfaces
The material’s discussion of connected cars provides a useful example of how embedded technology and IoT fit together. It identifies connectivity modules and computing components, including CPUs or MPUs and GPUs, alongside onboard systems and operating systems. It also lists navigation systems, connected mobile devices, communications modules, and human interfaces such as voice user interfaces and haptic devices.
This component view helps clarify that connectivity is not a standalone feature. It depends on embedded computing, communications hardware, software, and a way for people or other systems to interact with the product. In industrial settings, a comparable assessment can help teams map the elements of a connected machine or production system, from device-level hardware through communications and user-facing applications.
Edge computing changes where data is processed
Cloud and edge computing offer different locations for processing data. In a cloud model, information travels over a network to remote computing resources. With edge computing, processing takes place closer to the device or system generating the data. This reduces reliance on sending every task to a remote cloud service and can shorten the network path for processing.
For automation teams, the distinction is useful when deciding how to structure connected systems. Device-level processing, network connectivity, and cloud resources have different roles; the appropriate arrangement depends on the application. The source’s comparison emphasizes network connection and time lag as considerations, rather than presenting edge and cloud as interchangeable terms. Engineers should therefore treat processing location as part of system architecture, alongside the embedded device and its communications.
What historical event figures say about the technical community
The ET/IoT Technology 2018 show report recorded 403 exhibitors across 781 booths, 26,607 visitors over three days, and 123 conference sessions. It reported 13,744 conference attendees. The visitor profiles included software, hardware, and system designers, while the listed industry segments included factory automation, automotive, and communications.
The exhibitor categories reflected the breadth of the field: semiconductors and intellectual property, board computers and modules, operating systems and middleware, design and verification tools, and IoT technologies. The event materials also described embedded technology offerings such as processors, FPGA and PLD devices, real-time operating systems, drivers, firmware, debugging tools, and measurement equipment. IoT categories included sensors, M2M technology, remote monitoring and control, wireless networks, IoT platforms, security, and integration services.
These historical details are not a current event schedule or a measure of today’s market. They do, however, show how embedded engineering and IoT bring together disciplines that automation projects often need: device design, software development, connectivity, measurement, security, and systems integration.
Practical implications for automation decision-makers
When evaluating an industrial IoT or embedded-system initiative, teams can use this ecosystem perspective to ask practical questions:
- What needs to be integrated? Identify the relevant hardware, software, communications, and interfaces.
- Where should processing occur? Consider the respective roles of device-level, edge, and cloud computing.
- Which disciplines and suppliers are involved? Map responsibilities across component providers, software vendors, and system integrators.
- What is the application context? Requirements can differ across factory automation, automotive, machinery, and other sectors.
Embedded systems and IoT technology connect industrial automation to a diverse, cross-industry supply chain. The historical market and event information highlights the range of components, services, and technical roles involved, while the edge-computing discussion underscores the importance of architecture decisions. For plant leaders and engineering teams, the practical takeaway is to evaluate connected systems as integrated solutions—not simply as devices with network access.